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

Set a priori codec preferences #359

Closed
martinthomson opened this issue Oct 29, 2015 · 3 comments
Closed

Set a priori codec preferences #359

martinthomson opened this issue Oct 29, 2015 · 3 comments

Comments

@martinthomson
Copy link
Member

Agreed at TPAC that an ordered list of codecs can be set on RTCRtpTransceiver. This only determines the ordering of the codecs on the corresponding media section generated by createOffer or createAnswer. Respecting these is down to the normal SDP rules for codec preferences.

Note that the values that are set should persist. However, we won't provide an accessor for this.

@juberti notes that we might also want to push certain codecs to the bottom: CN, telephone-event, and all FEC payload types. That might be best to avoid accidental interoperability issues.

@aboba
Copy link
Contributor

aboba commented Nov 25, 2015

One thing that needs to be nailed down is whether only one codec in the codec list can be sending at a time (e.g. whether encodings[i].active can be set to true for only one value of i).

We've already seen differing interpretations of this within the ORTC API.

@martinthomson
Copy link
Member Author

@aboba, I think that's a separable issue.

@elagerway
Copy link
Contributor

Closing this as PR #361 was merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants