W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > March 2019

Re: [webrtc-pc] Missing specification on how to assign bandwidth between encodings and/or drop simulcast layers (#2141)

From: Iñaki Baz Castillo via GitHub <sysbot+gh@w3.org>
Date: Sun, 24 Mar 2019 14:43:22 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-475965753-1553438601-sysbot+gh@w3.org>
> I agree, but we need to know when a layer should be dropped first, that's why I proposed the `minBitrate` (and it could be always set to 0). I would be happy with any other mechanism that produces reproducible and predictable results about when a layer should be paused/resumed.

I will delete my previous comment about the `minBitrate` proposal since I did not properly understand it. Anyway:

> `minBitrate` : bellow this threshold the encoding/layer will be dropped (i.e. will not be sent until there is enough bandwidth to start sending it again). Default: 0

If there are three encodings with `minBitrate': 1000, `minBitrate`: 2000 and `minBitrate`: 3000, and the TOTAL BWE is 3500, what should happen? the browser may send streams 1 and 2, or just 3. IMHO this does not fix the problem. A explicit `dropOrder` looks much better.

GitHub Notification of comment by ibc
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2141#issuecomment-475965753 using your GitHub account
Received on Sunday, 24 March 2019 14:43:23 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:46 UTC