It is also less resource intensive since you are using your local computer to save media it is already receiving vs. Local recording is more secure by nature as you are not leaving unencrypted media on a server somewhere. Local RecordingĪnother approach is to just record locally. I really just wanted a quick way to record a session and share it afterwards and this was all getting very complex. On top of that, you also need to build a mechanism to transfer the files someplace after they are recorded or setup the Dropbox integration. If you want to record multiple sessions you can set it up to launch multiple Docker containers, which starts getting complex. It also only handles a single recording at time. This approach is fairly resource intensive, which forced me to upgrade my server from $5/mo to $20/mo. Jibri loads a headless browser that acts as a silent participant in the call, grabbing the audio and saving it to disk.
#Lib jitsi meet install#
The Jibri setup and configuration is more complicated to install than the base Jitsi Meet, but one can struggle through it in hours or less if you’re familiar with the underlying system. Jitsi has a module called Jibri used for recording. This sounds like a simple feature to add, but… Jitsi Cloud Recording Challenges On the surface, my requirements here are simple – record my audio and the audio and video of the Jitsi Meet session on demand and save the file locally. I often do demos and recording the session for others and future reference. However, one feature I really wanted to implement is recording.
#Lib jitsi meet how to#
There are a billion posts/videos on how to set up Jitsi Meet, and I don’t have anything new or interesting to add to the technosphere there. I built a Jitsi Meet server a few months ago with the intention of updating my Build your own phone company with WebRTC and a weekend post. My result is located in this repo.Įditor’s note: see the comments section for some very relevant commentary and caveats from Jan-Ivar at Mozilla. Read on for plenty of details and some reference code. Adding your own HTML/JavaScript to Jitsi Meet is pretty simple.mediaRecorder for media recording has some of its own unexpected limitations, and.getDisplayMedia for screen capture has many quirks,.That lead me down the road to discovering that: The feature wasn’t built in the way I wanted, so I set out on a hack to build something simple. desktopSharingChromeDisabled and desktopSharingFirefoxDisabled will no longer be supported.I wanted to add local recording to my own Jitsi Meet instance. (#1284)įeat(JitsiConnectionErrors): remove unused constant (#656)įix(RTCUtils): Cannot read property 'find' of undefinedįeat(sanity): axe IE and Temasys plugin support ???įix(caps): add event to notify when caps version for a user is changedĬleanup: Get rid of the chrome extension related code for screensharing - Use getDisplayMedia on browsers where it is supported. Ref: Moves xmpp logs to be accessed from connection. Use the centralized jitsi eslint config (#623)īuild: add integration with webpack-bundle-analyzerįeat(stats): Add the ability to enable callStats only on a certain % of conferences Remove all participants and tracks when leaving the roomĮ2ee: use a separate bundle for the worker Ref(sdp): Add a more generic option for codec preference Use 'preferredCodec' and 'disabledCodec' under videoQuality config.js settings for setting codec preferences.
#Lib jitsi meet update#
Remove jitsiRegionInfo from lib-jitsi-meet (#490)įix: update token doc for tenant details, new prosody (#1316) Ci: add GH actions for checking the linter