gstreamer <-> pulseaudio <-> chromium, ALSA weirdness?
-
- Offline
- 2 weeks 3 days ago
- 2018-03-12
Hi,
I ported my Docker image from Ubuntu, things went pretty well, I got all the packages relocated to their `apk` equivalents. Things were good, I had chrome, pulse, gstreamer up and sending out content and it looked great, just like in my Ubuntu image, there was one problem, no audio! I spent a day or more debugging, I noticed from differences between how Ubuntu is setup with alsa/pulseaudio configs, one to note that Ubuntu showed `/sbin/alsa` where alpine packages did not, so I assume that's a provided with the kernel? I'm not sure, another is there were a few different/missing configs (/usr/share/alsa/pulse-alsa-conf). I had tested gstreamer with audiotestsrc, and audio would come out fine, so no problem there. The issue seems to be in capturing from chromium (output to pulse or gstreamer capturing pulse). I noticed gstreamer was able to connect as a client to pulse, where chromium wouldn't regardless of how things were configured.
Can any one help, it would be much appreciated!
After much battle, I finally managed to get pulseaudio, chromium and gstreamer to work together. I had to disabled a few things in `/etc/pulse/default.pa` and most importantly switched to using `tcp` and `auth-anonymous=1`.
After however, I compared pipelines to my ubuntu build, which has almost identical configurations. `alpine` ran at %140, while `ubuntu` could keep a steady %95-105. `alpine` also appeared to grow in memory more continually.
All in all, it was an interesting challenge but did not yield desired results.