3 ms·

AFAIK Google Hangouts uses non-standard WebRTC functionality. Found a decent write-up: https://webrtchacks.com/hangout-analysis-philipp-hancke/ https://webrtch

AFAIK Google Hangouts uses non-standard WebRTC functionality. Found a decent write-up: https://webrtchacks.com/hangout-analysis-philipp-hancke/ https://webrtchacks.com/hangout-analysis-philipp-hancke/ Can't tell you whether or not that's the real reason. But I can definitely confirm that the lack of widely supported 'Plan B multiplexing' is (was?) a real pain point for WebRTC devs.

Hydraulix989 9y ago
Vanilla WebRTC in its current form is still too unstable to actually be usable for production video chat applications. Its limitations affect all of the leading commercial providers: Tokbox, Twilio, Agora, etc. For example, on MacOS, there is a severe breaking CoreAudio bug in WebRC that hasn't been fixed for over 3 years which affects 8% of users by causing unmuted microphones to not transmit any audio [1]. We've never seen this problem come up with Hangouts though. iOS builds for Google's WebRTC libjingle_peerconnection library have been broken for over 2 months, too [2]. It's no surprise that there is some core Hangouts team within Google building something else. Even Google's own AppRTC "reference" application implementation has some seriously questionable design decisions in its code (such as sending signaling messages to Google App Engine to forward over websockets). Google needs to figure out how to bridge the gap between both organizations so that everyone can benefit from the stability gains made by the Hangouts team. [1] https://bugs.chromium.org/p/webrtc/issues/detail?id=4799 https://bugs.chromium.org/p/webrtc/issues/detail?id=4799 [2] https://github.com/pristineio/webrtc-build-scripts https://github.com/pristineio/webrtc-build-scripts
gsnedders 9y ago
AIUI, they're also relying on some parts of WebRTC that aren't interoperably implemented yet, like the statistics model.

3 ms·

AFAIK Google Hangouts uses non-standard WebRTC functionality. Found a decent write-up: https://webrtchacks.com/hangout-analysis-philipp-hancke/ https://webrtch

by auganov 9y ago

Hydraulix989 9y ago
Vanilla WebRTC in its current form is still too unstable to actually be usable for production video chat applications. Its limitations affect all of the leading commercial providers: Tokbox, Twilio, Agora, etc. For example, on MacOS, there is a severe breaking CoreAudio bug in WebRC that hasn't been fixed for over 3 years which affects 8% of users by causing unmuted microphones to not transmit any audio [1]. We've never seen this problem come up with Hangouts though. iOS builds for Google's WebRTC libjingle_peerconnection library have been broken for over 2 months, too [2]. It's no surprise that there is some core Hangouts team within Google building something else. Even Google's own AppRTC "reference" application implementation has some seriously questionable design decisions in its code (such as sending signaling messages to Google App Engine to forward over websockets). Google needs to figure out how to bridge the gap between both organizations so that everyone can benefit from the stability gains made by the Hangouts team. [1] https://bugs.chromium.org/p/webrtc/issues/detail?id=4799 https://bugs.chromium.org/p/webrtc/issues/detail?id=4799 [2] https://github.com/pristineio/webrtc-build-scripts https://github.com/pristineio/webrtc-build-scripts
gsnedders 9y ago
AIUI, they're also relying on some parts of WebRTC that aren't interoperably implemented yet, like the statistics model.