- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Jul 2020 12:40:08 +0000
- To: public-webrtc-logs@w3.org
Isn't the preference different depending on if this is during negotiation or if this is which layers should be active? For example, if I successfully negotiate 4:2:1 I would want 1 to be dropped first if BW does not support it. However, if I attempt to negotiate 4:2:1 but only two layers are supported, then truncation according to preference order results in 4:2. This means that I will never send the highest resolution layer because it doesn't exist. Perhaps it would make sense to shift the layers by the number of layers removed, so that we end up with 2:1 instead. However, it may be up to the application if which resolution makes more sense to prioritize, and if a custom scaleResolutionDownBy then we shouldn't be doing any guessing. Perhaps the solution should be to truncate according to spec and if an application's layers get truncated it is up to the application to adjust scaleResolutionDownBy if it wants HD. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2537#issuecomment-655493783 using your GitHub account
Received on Wednesday, 8 July 2020 12:40:11 UTC