Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

webrtchacks.com

Post reply on HN
Print view View original

61–70 of 115 posts

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#61

Post by zajio1am »

moron4hire wrote: post #22

I've been playing with a custom install of Jitsi Meet for the last few days. It was very easy to setup. I'm kind of fearing trying to deploy it in my company. This has nothing to do with Jitsi Meet and everything to do with the shitshow that is WebRTC in browsers. I can't find any desktop browsers that use the available GPU for hardware accelerated video encoding. Chromium (Google and Edge) says it's "only available…

I also had very bad experience with WebRTC in browsers. Just several days ago i tried videoconference with Jitsi Meet. Although it was receive only (no camera or mic), so no encoding, and received video was pretty low-res, it generated enough load on all my cores that after a while it triggered thermal throttling.

Considering that i can play Full-HD H.264 videos with minimal load then this seems ridiculous.

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#62

Post by iknowstuff »

toohotatopic wrote: post #37
SparkyMcUnicorn wrote: post #23

Earlier quoted context omitted.

The Jistsi team says the server needs roughly 5.5Mbps per Chrome user. Firefox uses a lot more bandwidth, system resources, and degrades the room capacity. Just something to keep in mind, and after some testing I saw the same results. My AWS bill was projected to be over $1k/month, so I put it on Linode where it'll cost between $100-200/month. Just about any decent VPS provider would be good options compared to AWS d…

Is there cheaper bandwidth available than Hetzner's 1.19euro +vat per TB? (Linode seems to be at 10$ / TB).

OVH doesn't limit it afaik.

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#63

Post by KingFelix »

gidam wrote: post #40

Jitsi-meet is very easy to install and to setup. "apt install jitsi-meet" and you have almost all done. The documentation is very good. It works great and it is super userfriendly. You have no excuses.

Once I heard about it I gave it a go, just to look at how easy it is to setup.

Super easy, + SSL!

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#64

Post by quadrangle »

moron4hire wrote: post #22

I've been playing with a custom install of Jitsi Meet for the last few days. It was very easy to setup. I'm kind of fearing trying to deploy it in my company. This has nothing to do with Jitsi Meet and everything to do with the shitshow that is WebRTC in browsers. I can't find any desktop browsers that use the available GPU for hardware accelerated video encoding. Chromium (Google and Edge) says it's "only available…

Does this explain why I get poor Jitsi experience on my laptop and better using the Android app on my phone??

I suspect you are hitting on the exact issue I'm having. I have a Thinkpad with just the Intel 5500 GPU, nothing superb. So, how do I figure out if at least that is being used or not?

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#65

Post by moron4hire »

oever wrote: post #32
moron4hire wrote: post #22

I've been playing with a custom install of Jitsi Meet for the last few days. It was very easy to setup. I'm kind of fearing trying to deploy it in my company. This has nothing to do with Jitsi Meet and everything to do with the shitshow that is WebRTC in browsers. I can't find any desktop browsers that use the available GPU for hardware accelerated video encoding. Chromium (Google and Edge) says it's "only available…

What's the setting for hardware video encoding in Firefox? media.webrtc.hw.h264.enabled or media.webrtc.platformencoder?

on closer inspection it looks like media.webrtc.hw.h264.enabled is for decoding and media.webrtc.platformencoder is for encoding on Android :(

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#66

Post by moron4hire »

quadrangle wrote: post #64
moron4hire wrote: post #22

I've been playing with a custom install of Jitsi Meet for the last few days. It was very easy to setup. I'm kind of fearing trying to deploy it in my company. This has nothing to do with Jitsi Meet and everything to do with the shitshow that is WebRTC in browsers. I can't find any desktop browsers that use the available GPU for hardware accelerated video encoding. Chromium (Google and Edge) says it's "only available…

Does this explain why I get poor Jitsi experience on my laptop and better using the Android app on my phone?? I suspect you are hitting on the exact issue I'm having. I have a Thinkpad with just the Intel 5500 GPU, nothing superb. So, how do I figure out if at least that is being used or not?

Windows Task Manager will show you GPU utilization on the Performance tab. Start Task Manager, then start your browser and see if there is an uptick. Then start a meeting to see if there is another one. There probably won't be. Then, disable the software rendering override in your browser: (Firefox: https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drive...) (Chrome: https://superuser.com/questions/836832/how-can-i-enable-webg...) and test again. Probably need to restart the browser after the change in settings.

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#70

Post by hyperluz »

ygra wrote: post #43
hyperluz wrote: post #33

Too bad, like most other solutions, Jitsi, by default, shares screen at 5 FPS.

Is that possible to change, perhaps if self-hosting? Video quality of screen sharing and frame rate are absolutely atrocious, to the point that you have to wait ten seconds until text becomes readable.

Apparently, yes: https://community.jitsi.org/t/screen-sharing-fps/25132
Post reply on HN