3 ms·
If they don't release it as part of webrtc, they won't be able to use it in browser based videoconferencing. Google Meet/Hangouts on desktop rely on that. Wh
by londons_explore 6y ago
If they don't release it as part of webrtc, they won't be able to use it in browser based videoconferencing. Google Meet/Hangouts on desktop rely on that.
While it is theoretically possible to process audio with something compiled with webassembly, data can't be marshalled into/out of a webassembly worker without the main browser threads help, and that tends to be too janky to use for realtime audio on most platforms.
That pretty much forces googles hand - if they want to use it in their web-based products, it must be opensource and available to all competitors.
They might say this feature only works with their mobile apps though.
- lankalanka 6y agoIt would take some time to see how it goes. It's possible to run on browsers without being a member of WebRTC codec family. The codec can be deployed as a WebAssemble module and WebRTC acts as a data channel for it. Zoom used to deploy a similar approach while staying on its proprietary codec.