Opus and other codec specific parameters #258

Closed
robin-raymond opened this Issue Oct 25, 2015 · 4 comments

Projects

None yet

2 participants

@robin-raymond
Contributor

We have codec specific capabilities listed (e.g. opus, vp8, H264):
http://ortc.org/wp-content/uploads/2015/10/ortc.html#opus-codec-capabilities*

But we have no such table(s) for codec parameters...

We need to list out exact parameters that an engine is expected to support.

Also for RTX / FEC codecs too (if applicable)...

@aboba
Contributor
aboba commented Oct 25, 2015

The text states that the capabilities and parameters are the same.

@robin-raymond
Contributor

Is this always true that they are identical?

@robin-raymond
Contributor

A: No, they are not the same always thus capabilities and settings should be distinct entries. Also important to define is this is a sender cap/receiver cap and/or sender param/receiver param for each.

@robin-raymond
Contributor

VP8 is currently a capability parameter, should also be a codec parameter (just like Opus)
H264 ^^^^

i.e. COPY them to codec parameters, and make it sender/receiver labelled

@aboba aboba added a commit that referenced this issue Dec 8, 2015
@aboba aboba Cleanup of Opus settings
#258

Changes: 
Removed stereo and spropStero settings (can be handled by channels)
Removed maxAverageBitrate (can be handled via maxBitrate)
8d0f394
@aboba aboba closed this Dec 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment