Allow setting RtpEncodingParameters for individual encodings #173
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
t-mullen
changed the title
|
In Firefox encodings are in the reverse order comparing to other browsers, this doesn't seem to account for that. |
|
After some discussion elsewhere, going to reopen with an a slightly different API. #174 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds an optional second parameter to
Producer::setRtpEncodingParametersthat allows applications to specify the index of the encoding to modify. Not providing this second parameter will modify all encodings just like before.Usecases
I have a few uses for this - just some examples:
setMaxSpatialLayerbut reversed).scaleResolutionDownBydepending on the current source resolution of the track.