Jitsi Meet VS galene

This seems to be related but I'm not quite sure: https://github.com/jitsi/jitsi-meet/issues/11442

I'm surprised I didn't see Jitsi Meet listed here. It's even FOSS. https://github.com/jitsi/jitsi-meet

According to this issue comment no browser can capture the screen on Wayland: https://github.com/jitsi/jitsi-meet/issues/6389#issuecomment...

Jitsi Meet : https://github.com/jitsi/jitsi-meet

Thanks for highlighting this, the jitsi team have been made aware and deployed a change: https://github.com/jitsi/jitsi-meet/pull/11040

2. Jitsi Meet

If you're looking for just good open source web UI/UX, I would add these to the list: * https://github.com/grafana/grafana * https://github.com/vector-im/element-web * https://github.com/jitsi/jitsi-meet

I'm not 100% sure it can work completely offline but worth a try: https://github.com/jitsi/jitsi-meet

I found Jitsi: https://github.com/jitsi/jitsi-meet but is a very big projects and not easy to understand.

I need some other alternative solutions, with much fewer codes, that has features like:

- webcam streaming

I would like to recommend Galene: https://github.com/jech/galene

Runs in my raspberry pi, a single small executable, like in the old good times.

> Do you happen to know of others by any chance.

There's Galene, <https://galene.org>. It's easy to deploy, uses minimal server resources, and the server is pretty solid. The client interface is still a little awkward, though. (Full disclosure, I'm the main author.)

galene - basically selfhosted zoom/jitsi

What latency are you trying to do? Will the professor being communicating with the students while doing this? Will the students all have the same bandwidth, or will you want multiple renditions (low, med, high quality levels)?

If you want AV1 you will not be able to use RTMP. The protocol is orphaned/deprecated, so avoid if possible!

If I was building it this is what I would do, and my reasoning.

* For capture + encoding I would use OBS. You will want to use something that is easy for users to install configure. Professors will also have lots of custom requirements when it comes to layout etc... it will be tempting to do a ffmpeg command directly, but it will fall apart quick I believe.

* To get AV1 out of OBS I would use FFMPEG output. I would have it send RTP. RTP is used to carry video in a sub-second manner. This is the same protocol that WebRTC uses. You know have AV1 + low latency.

* Then for users to watch I would use WebRTC. That will allow them to watch in their web browser. Conceptually it will be like this https://github.com/pion/webrtc/tree/master/examples/rtp-to-w... this takes the RTP packets and puts them in the browser.

Lots of great projects exist that you could use for 'RTP -> WebRTC' like https://galene.org/ and https://livekit.io/ I would suggest checking them all out!

If you have more questions/want to talk to people in the video space always happy to chat on https://pion.ly/slack :)

galene

The most lightweight all-inclusive central solution for video conferences I know is Galene. It runs in under 200 MB RAM.

Even though the default UI is extremely simplistic, I very much like galene. It bundles all the components you need in a single binary. Even a TURN server so you don't have to fiddle with coturn. Not to mention that it's very resource efficient.