[ansible]

> I would venture that the problem with Google's products is that they run in the browser and in spite of all the improvements in browsers these days its just not ready yet when you need the kind of quality and performance that huge meetings demand.

Disclaimer: I have not investigated how Zoom and other video conference apps work, but I do work with real-time video.

I don't see why the browser would be the limiting factor in performance / quality for videoconferencing.

What is the local client doing? Recording video and audio, and playing a real-time video stream. Sure, you want it to be low-latency, which involves its own bag of tricks.

But native-code libraries and/or hardware are doing all the heavy lifting (like H.264 encoding or whatever they use), the browser (and Javascript) is just the UI.

[jcelerier]

You have much more leeway if you can tune ffmpeg decoding settings manually, skip frames whenever you want, etc than if restricted to what webrtc gives you. Also Zoom is built with Qt which is pretty efficient :-)

[ansible]

So it seems the limitation is more the API for recording video, is this correct?