-
Notifications
You must be signed in to change notification settings - Fork 46
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
how to describe the relationship of codec and fec mechanisms #610
Comments
What's in the SDP? |
abbreviated:
payload type on the wire is 124 |
What is happening in stats? curious about what is being reported on the payloadType and mimeType? The endpoint is receiving PT 124 but the stats are reporting that PT is 96? |
I don't see any association between 96 and 124 in the SDP. Is that just "declared by being in the packet"? |
@alvestrand this isn't done "properly" in chrome's SDP at all (see question on the decade old bug) |
when using chrome to make a call on
https://webrtc.github.io/samples/src/content/peerconnection/constraints/
the
inbound-rtp
codecId stat is pointing to RTCCodec_1_Inbound_96 which resolves to VP8.However, Chrome actually wraps this in RED (historically, see https://bugs.chromium.org/p/webrtc/issues/detail?id=1467)
But this is impossible to detect using stats.
What is the proper way to deal with this? Should the codecId point to video/RED which then has an underlying codecId?
The text was updated successfully, but these errors were encountered: