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. 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. 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. And, you can very nicely use it for central discoverability of available sessions, simply by users (automatically or manually) joining rooms.I wanted to add local recording to my own Jitsi Meet instance. Jitsi integration isn't as mature as MS Teams' Video call, but it has way less hardware problems. Element is a Slack-equivalent chat client (minus the Giphy integration) for Matrix, sooooo much better than MS Teams. If you want more, something like a MS Teams system for your own company completely hosted within the confines of your own network, with the option to integrate your own or an external video/screen/voicecall server: Matrix is the way to go there. It looks like the 1990s had a lovechild with questionable UX choices, though. Personally, I've run mumble as voice chat client (with its on-premise murmur server), and it works nicely. That would also solve the discoverability issue: a user in need of assistance would connect to the server, you'd see them and call them (or they'd call you) and then instruct them to start the desktop sharing (probably a good idea to have some inter-personal protocol in place for that – I hear windows "hotline" scams are a big thing right now "my admin guy says I mustn't open remote desktop if the other side cannot do XYZ" is a good thing). I'd like to point out that a few kilobit/s of audio probably won't hurt too much if they go to a central server, within or outside your own network. Windows comes with the server, and there's multiply RDP clients for Linux (remmina is probably a good choice), and it really works smoothly.įor the audio call thing: there's nothing peer-to-peer built into Windows, so you need to install something, and it needs to open a network socket, and then you need to find each other.Ĭonsidering that, some run-of-the-mill voicechat option is probably a good idea. Windows remote desktop for the screen share it's actually really good, in many ways. If you want a self-hosted jitsi, go for it: not impossible to set up, essentially a single docker container.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |