-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
change-codecs: move codec selection to the receiver #1640
change-codecs: move codec selection to the receiver #1640
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the sample log what codec is actually being used?
transceiver.setCodecPreferences(codecs); | ||
console.log('Preferred video codec', selectedCodec); | ||
} | ||
} | ||
codecPreferences.disabled = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still reasonable? (I assume it's turned back on after negotiation finishes)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is going to be turned until the end of the call until we support @Orphis' cool stuff
While using setCodecPreferences on the sending side works because the answerer will match the sender's order, using it on the receiving end is more semantically correct. See this comment w3c/webrtc-encoded-transform#186 (comment)
ff61251
to
cb5943b
Compare
follow-up to webrtc#1640 which got copy-pasted quite a bit.
follow-up to webrtc#1640 which got copy-pasted quite a bit.
While using setCodecPreferences on the sending side works because the answerer will match the sender's order, using it on the receiving end is more semantically correct.
See this comment
w3c/webrtc-encoded-transform#186 (comment)