Comments on: Can a native media engine beat WebRTC’s performance? https://bloggeek.me/can-a-native-media-engine-beat-webrtcs-performance/ The leading authority on WebRTC Mon, 08 May 2023 05:21:23 +0000 hourly 1 By: Tsahi Levent-Levi https://bloggeek.me/can-a-native-media-engine-beat-webrtcs-performance/#comment-162700 Mon, 08 May 2023 05:21:23 +0000 https://bloggeek.me/?p=73582#comment-162700 In reply to Roni.

That progress over time is always the case, especially with technologies that are constrained by both network and compute.

]]>
By: Roni https://bloggeek.me/can-a-native-media-engine-beat-webrtcs-performance/#comment-162698 Mon, 08 May 2023 04:38:12 +0000 https://bloggeek.me/?p=73582#comment-162698 Another advantage of a media engine is handling scenes with fast movement. The typical video conferencing is talking heads with not much movement. But you can test the quality even by moving your hands fast and see how it looks on the receiving side. I think that what you can call the webRTC is good enough quality implementation that will progress over time.

]]>
By: Tsahi Levent-Levi https://bloggeek.me/can-a-native-media-engine-beat-webrtcs-performance/#comment-161869 Sun, 02 Apr 2023 15:56:55 +0000 https://bloggeek.me/?p=73582#comment-161869 In reply to Jernej Jerin.

Zoom web already leverages these technologies 🙂

]]>
By: Jernej Jerin https://bloggeek.me/can-a-native-media-engine-beat-webrtcs-performance/#comment-161268 Wed, 08 Mar 2023 16:10:07 +0000 https://bloggeek.me/?p=73582#comment-161268 Great post Tsahi!

I think the costs associated with developing something akin to WebRTC should be mentioned. I think Google already spent $1B+ in development, so it's hard too see how developing it in house would justify this, unless it would be constrained to run on a specific platform and without many features.

WebTransport, WebCodecs andWebAssembly are interesting technologies. I suppose we might see one day a Zoom version for the browser leveraging these technologies?

]]>