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
Opus and other codec specific parameters #258
Comments
The text states that the capabilities and parameters are the same. |
Is this always true that they are identical? |
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. |
VP8 is currently a capability parameter, should also be a codec parameter (just like Opus) i.e. COPY them to codec parameters, and make it sender/receiver labelled |
#258 Changes: Removed stereo and spropStero settings (can be handled by channels) Removed maxAverageBitrate (can be handled via maxBitrate)
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)...
The text was updated successfully, but these errors were encountered: