jitsi / jibri

Jitsi BRoadcasting Infrastructure
Apache License 2.0
600 stars 314 forks source link

Jibri Multiple Record Settings #519

Closed alkanpolat closed 6 months ago

alkanpolat commented 9 months ago

Hello, I have been working on installing Jitsi and Jibri for a few days. It is really difficult to find an up-to-date and stable installation guide. As far as I saw from an installation video of an Indian friend, this situation can be corrected by multiplexing the Jibri container. For now I will explain how to do this manually. I am planning to publish a video featuring jitsi docker deployment in the coming days.

sudo docker ps After run the Jitsi and Jibri containers, you should see an output like this. image

You can then multiplex the jibri container by running these commands respectively. Note: If your docker container names differ, edit the commands below according to your own container names.

sudo docker exec -it docker-jitsi-meet_jibri_1 bash
apt-get update
apt install nano
nano home/jibri/.asoundrc

Go to the file and edit its content like this

...
slave.pcm "hw:Loopback,1,1"
...
slave.pcm "hw:Loopback,1,0"
...
slave.pcm "hw:Loopback_1,0,0"
...
slave.pcm "hw:Loopback_1,0,1"
...
slave.pcm "hw:Loopback_1,1,1"
...
slave.pcm "hw:Loopback_1,1,0"
...
slave.pcm "hw:Loopback_2,0,0"
...
slave.pcm "hw:Loopback_2,0,1"
...
slave.pcm "hw:Loopback_2,1,1"
...
slave.pcm "hw:Loopback_2,1,0"
...
slave.pcm "hw:Loopback_3,0,0"
...
slave.pcm "hw:Loopback_3,0,1"
...
slave.pcm "hw:Loopback_3,1,1"
...
slave.pcm "hw:Loopback_3,1,0"
...
slave.pcm "hw:Loopback_4,0,0"
...
slave.pcm "hw:Loopback_4,0,1"
...
slave.pcm "hw:Loopback_4,1,1"
...
slave.pcm "hw:Loopback_4,1,0"
...
exit
sudo docker exec -t docker-jitsi-meet_jibri_1 sed -i 's/Loopback/0/g' /home/jibri/.asoundrc
sudo docker restart docker-jitsi-meet_jibri_1
sudo docker-compose -f docker-compose.yml up -d --scale jibri=2
sudo docker exec -t docker-jitsi-meet_jibri_2 sed -i 's/Loopback/0/g' /home/jibri/.asoundrc
sudo docker restart docker-jitsi-meet_jibri_2

You can create as many jibri containers as you want using this method. Like this

sudo docker-compose -f docker-compose.yml up -d --scale jibri=3
sudo docker exec -t docker-jitsi-meet_jibri_3 sed -i 's/Loopback/0/g' /home/jibri/.asoundrc
sudo docker restart docker-jitsi-meet_jibri_3

sudo docker ps

In the last case, when you check, you should get an output like the following. Note: The jitsi/whiteboard container should not appear on your screen. image

Indian friend's video with Jibri multiple record explanation and many more customizations https://www.youtube.com/watch?v=5zANUyjAXPg&ab_channel=HC

and document file https://drive.google.com/file/d/1SWi9m7XOivJjitj8ufgBDZB8XZHvLcpY/view

saghul commented 9 months ago

Those instructions are outdated, the Jibri container no longer needs an audio device.

You can just use different names and you're good to go.

alkanpolat commented 9 months ago

Those instructions are outdated, the Jibri container no longer needs an audio device.

You can just use different names and you're good to go.

Is there a way to do this automatically as per need?

saghul commented 9 months ago

Depends on how you orchestrate your containers. With Compose you can just copy the Jibri file and that's it.

talalgujjar100 commented 6 months ago

Hi Is there any clear documentation or guide if i want to record multiple meetings at the same time using jibri hosted on digital ocean without dockers

saghul commented 6 months ago

There isn't. You need 1 Jibri instance to record 1 meeting, so Docker is the simplest way.

You no longer need to do anything with ALSA devices on the host, as PulseAudio takes care of it.