Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What does minQuality do, exactly? #351

Closed
aboba opened this Issue Jan 14, 2016 · 0 comments

Comments

Projects
None yet
1 participant
@aboba
Copy link
Contributor

aboba commented Jan 14, 2016

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

@aboba aboba added the 1.1 label Jan 14, 2016

aboba added a commit that referenced this issue Apr 25, 2016

Remove minQuality
Fix for Issue #351

@aboba aboba referenced this issue Apr 25, 2016

Merged

Remove minQuality #513

@aboba aboba added the PR exists label Apr 25, 2016

@aboba aboba closed this Apr 25, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.