- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Dec 2019 14:38:17 +0000
- To: public-webrtc-logs@w3.org
aboba has just created a new issue for https://github.com/w3c/mst-content-hint: == degradationPreference is under-specified == Moved from https://github.com/w3c/webrtc-pc/issues/2248 `degradationPreference` appears to have been implemented differently between browsers, but the differences are not being picked up in the WPT test, which [only tests getting and setting values. ](https://github.com/web-platform-tests/wpt/blob/master/webrtc/RTCRtpParameters-degradationPreference.html) Currently Section 5.2.2 says: "When bandwidth is constrained and the `RTCRtpSender` needs to choose between degrading resolution or degrading framerate, `degradationPreference` indicates which is preferred." In the current Edge implementation, `degradationPreference` is interpreted as providing a content-hint to the encoder, allowing it to differentiate between applications desiring a bias toward "detail" (a `degradationPreference` of "maintain-resolution" or "motion" (a `degradation-preference` of "maintain-framerate"). However my understanding is that other browsers don't implement `degradationPreference` this way. Please view or discuss this issue at https://github.com/w3c/mst-content-hint/issues/33 using your GitHub account
Received on Thursday, 5 December 2019 14:38:18 UTC