You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Currently the ORTC API includes parameters.encodings[j].minQuality, which is defined as follows:
minQuality of type double, defaulting to 0
Never send less than this quality. 1.0 = maximum attainable quality. For scalable video coding, this parameter is only relevant for the base layer. This parameter is ignored in an RTCRtpReceiver object.
Can an application use parameters.encodings[j].minQuality to advise the browser when to drop a simulcast or SVC stream? How does this relate to parameters.degradationPreference?
Currently the ORTC API includes parameters.encodings[j].minQuality, which is defined as follows:
minQuality of type double, defaulting to 0
Never send less than this quality. 1.0 = maximum attainable quality. For scalable video coding, this parameter is only relevant for the base layer. This parameter is ignored in an RTCRtpReceiver object.
Can an application use parameters.encodings[j].minQuality to advise the browser when to drop a simulcast or SVC stream? How does this relate to parameters.degradationPreference?
This issue was discussed at the W3C WEBRTC WG meeting on January 14, 2015. Slides and minutes:
https://www.w3.org/2011/04/webrtc/wiki/January_14_2016
The text was updated successfully, but these errors were encountered: