PulseAudio instead of ALSA

PulseAudio works in userspace and it doesn’t require a kernel module. It makes Jibri work nicely within Docker with Xorg and IceWM manually started, without passing any host devices.

part of my script for patching Jibri

# application
sed -i -e 's/alsa/pulse/g' \
  src/main/kotlin/org/jitsi/jibri/capture/ffmpeg/executor/Commands.kt
sed -i -e 's/hw:0,1,0/default/g' \
  src/main/kotlin/org/jitsi/jibri/capture/ffmpeg/executor/Commands.kt

# test
sed -i -e 's/alsa/pulse/g' \
  src/test/kotlin/org/jitsi/jibri/capture/ffmpeg/FfmpegCapturerTest.kt

part of my script for creating a virtual sink, based on this answer https://stackoverflow.com/questions/43312975/record-sound-on-ubuntu-docker-image#43368617

apt-get -y install pulseaudio socat
pulseaudio -D --exit-idle-time=-1
pacmd load-module module-virtual-sink sink_name=v1
pacmd set-default-sink v1
pacmd set-default-source v1.monitor

It would be great if you consider using PulseAudio instead of ALSA or make it configurable.

Additionally. It isn’t relevant to this particular issue and I’m not sure whether it’s a bug. 6.X versions don’t report a correct status to Jitsi from the stable repository. After connecting it immediately goes offline. 5.1 version works though.

[mishurov]

Yet another issue connected to Docker and quite possibly it was the cause of my previous issue. Chrome doesn’t work within a docker container without the --no-sandbox flag, it seems a common issue.

I was fixing it by creating a script which overrides the chrome executable. E.g. echo '/usr/bin/google-chrome --no-sandbox $@/' > /usr/local/bin/google-chrome

And it appears to be wrong. The problem is that since Selenium runs my script instead of the original executable, it can’t kill chrome’s process correctly, it throws an exception and Jibri becomes unavailable, and there’re also unhandled chrome processes remain hanging around in the system.

I’ve added the --no-sandbox to src/main/kotlin/org/jitsi/jibri/selenium/JibriSelenium.kt, and now it works fine.

Thus, I think, if you allow to add extra arguments for Chrome through the json, it will make life easier as well.

[mishurov]

@bbaldino, ok, thank you for the explanation. I’m not in power to set priorities in the project we working on. When Jibri comes to the question, I’ll create a bug on that with more detailed data if the problem arises again.

UPD: Jicofo 1.0-443-1 from the unstable repository and a compiled (and patched for pulse) Jibri from current master b6b7b9c424e1cde150b6698037747a50295e425b doesn’t have this problem. Thanks.