- From: Iñaki Baz Castillo via GitHub <sysbot+gh@w3.org>
- Date: Sun, 24 Mar 2019 18:12:42 +0000
- To: public-webrtc-logs@w3.org
Ok. It looks good but IMHO too complex (finally those are 3 new fields!). But indeed if we remove the `minBitrate` field the browser would keep sending all layers even in bad circumstances. However, you know that current implementations assume they can stop a layer without too much rationale (they just do it). Would that be the effective behavior if `minBitrate` is not given? I've also some doubts regarding the `weight` parameter. It looks like it may conflict with `scaleResolutionBy`, `maxFramerate` and `maxBitrate`. IMHO the browser should be able to estimate the "weight" of a layer/stream based on those already defined values. This is, I assume that your suggested `weight` field tells the browser how much percentage of BW it must allocate for each stream. IMHO we don't need that. The encoder should know that better than us based on `scaleResolutionBy`, `maxFramerate` and `maxBitrate` (and I'd love to introduce as less new parameters as possible). -- GitHub Notification of comment by ibc Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2141#issuecomment-475984747 using your GitHub account
Received on Sunday, 24 March 2019 18:12:44 UTC