Show HN: Zoom Redirector

(github.com)

279 points arkadiyt | 1 comments | 22 Mar 20 22:11 UTC | HN request time: 0.206s | source

Show context

michaelrkn ◴[23 Mar 20 00:17 UTC] No.22660082[source]▶

I once used Zoom's web interface and the video quality was horrible. When I switched to the downloaded app, it was much better. Not sure if this was a one-off problem or an underinvestment in their web interface.

replies(2): >>22660316 #>>22661842 #

dbrgn ◴[23 Mar 20 07:09 UTC] No.22661842[source]▶

>>22660082 #

The web version will be using WebRTC with whatever codecs your browser ships while the native version is able to use custom codecs.

replies(1): >>22662082 #

padenot ◴[23 Mar 20 08:18 UTC] No.22662082[source]▶

>>22661842 #

This is incorrect. Zoom doesn't use webrtc audio and video channels, only data channels, and has reimplemeted audio and video channels on top of that, doing the decoding in js and probably wasm.

They also limit the resolution to 480p for the web app, probably because of performances. Browsers and zoom both use h264, but browsers usually use vp8 instead.

There is no reason webrtc cannot offer the same quality (or better) than zoom, at the same bit rate, but it all comes down to the actual implementation of browsers and web apps. webrtc-based apps work well, these days.

replies(1): >>22727240 #

1. dbrgn ◴[30 Mar 20 11:54 UTC] No.22727240[source]▶

>>22662082 #

Thanks for the information, I also realized that a while after writing the comment. No wonder the experience is worse than in their native client, data channels are still terribly unoptimized (sometimes even broken in some aspects).

Edit: https://bloggeek.me/when-will-zoom-use-webrtc/

↑