-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
codec + configuration #19
Comments
Response by Magnus:
|
So let's check how Chrome Canary M51 and Firefox Nightly 48 offer "codecs":
|
As I commented in the AVT ML:
|
Regarding H264 https://tools.ietf.org/html/rfc6184#section-6
So valid values are 0 (default if not set), 1 and 2. Mandatory for WebRTC are 0 and 1. |
Chrome 50 with H264 support (enabled in
Just that. No /cc @saghul |
If the attribute is absent the default is used: 420010. |
Wow, so indeed Firefox and Chrome do not interop at H264 level... |
Moving comments form #18 here: UPDATE: After a good chat with @jmillan, the room will be provided with mandatory Still we need an internal list of "valid" audio/video codecs in mediasoup. The list (to be completed) would start with:
@saghul said:
@ibc said:
@saghul said:
@ibc said:
@saghul said:
|
Not necessarily. One of them could just accept the offer and use the supplied profile-level-id. Here they both use the same profile (42, baseline) and different level (1f == 31 == 3.1 vs 10 == 1.0). Different levels could cause problems, but more importantly, different profiles could (42 == baseline vs 4d == main), for example. |
Interesting.... so what? XD |
At the end I need specific and separate "codec configurations" to be thread as the "same codec+configuration". Note however that codec parameters given by each peer will be properly indicated to each receiver peer (so Chrome will be the H264 params of Firefox and vice-versa), but still I need a proper list of "codec + configurations". |
no vp9 codecs? |
mediasoup is a SFU so it does not encode/decode codecs. This means that any codec will be supported. |
I have an issue where But using the default codecs as explained here fails locally, does anyone know what config the demo server is running? Fails for Web (Chrome)
|
mediasoup needs to hold a map of
payloadType
and codecs+configuration. So I need to know what "codec+configuration" means (note that some codecs have their own configuration parameters...).Mail sent to AVT WG: https://www.ietf.org/mail-archive/web/avt/current/msg17068.html
https://en.wikipedia.org/wiki/RTP_audio_video_profile
The text was updated successfully, but these errors were encountered: