- From: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
- Date: Sun, 24 Mar 2019 09:28:53 +0000
- To: public-webrtc-logs@w3.org
murillo128 has just created a new issue for https://github.com/w3c/webrtc-pc: == Missing specification on how to drop bandwidth between encodings and/or drop simulcast layers == During the IETF hackaton we have found a weird situation in chrome with latest simulcast implementation via addTransceivers in which the ordering of the encoding affects how the bandwidth is allocated to the different simulcast encoding: https://bugs.chromium.org/p/webrtc/issues/detail?id=10469 If the reverse order of encodings is used on the addTransceiver call, all of the bandwidth will be assigned to the lower layers while the higher layer (the 720p one) will almost no bandwidth assigned. While this is not the expected behavior there seems to be no clear specs on what should be the correct behavior. In previous discussions we have decided that this may be an implementation detail, but after having to deal with it, I definitively think we need a consistent behavior across browsers. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2141 using your GitHub account
Received on Sunday, 24 March 2019 09:29:00 UTC