I’ve been using a modified Jibri with Pulseaudio for 5 weeks. So far, it has recorded and streamed more than 300 meetings (avg 2h) without issues. A 10th even exceeded 4h.
Why is migrating from ALSA to Pulseaudio a big deal? because most Kubernetes providers don’t allow you to load kernel modules unless you select “standard OS based nodes”. In my particular case, one of our providers doesn’t allow to select the base system, and they’ve a custom kernel without that module.
So, we modified Jibri as stated on another post, and we were able to get several pods running on the same server without needing to reconfigure anything at all. It just works.
I only needed to install 3 additional packages to the Jibri Docker Image and a Script to run Pulseaudio as Jibri user, but the Jibri.jar on it was compiled by myself, so it’s not as neat as I’d wish in order to share it with 3rd parties.
Any plans on making Pulseaudio officialy available for Jibri? if so, I’ll be glad to share the Docker image changes so we can all use official jitsi/jibri images