Time to move Jibri from ALSA to Pulseaudio?

Super nice work guys! Huge thanks, all is working!

1 Like

For what is worth, we ended up installing the alsa module in our cluster that runs in AWS EKS. We did not pursue the pulse solution, since this required little work on our part and is the standard for jibri.

Thanks for your help @kpeiruza!

1 Like

Can someone provide the steps to create Jibri.jar with pulseaudio patching? @kpeiruza

Hi @kpeiruza thanks for sharing your stack details. I would try to deploy docker image you shared.

Meantime, it would be great if you could share samples of your kubernetes manifest files also. Thanks :slight_smile:

@kpeiruza Nice, I’m using your docker image v13 to test. But getting a few errors.

Kindly help in fixing.

2021-02-22 12:32:06.364 SEVERE: [19] org.jitsi.retry.RetryStrategy.log() org.jivesoftware.smack.s
asl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
Feb 22 12:32:06 node99609-env-4865786.nl.realcloud.in launch.sh[242]: org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
Feb 22 12:32:06 node99609-env-4865786.nl.realcloud.in launch.sh[242]: at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java
:292)

Please advise.

Thanks