- From: docfaraday via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Aug 2024 16:12:37 +0000
- To: public-webrtc-logs@w3.org
> I'm currently working in this area (coming in from PT assignment, but "are these equal" comes in a lot there). Codec capabilities are what one wants to receive, and the PT assignment in the two directions is, in theory, independent, so that this: a -> b: rtpmap:97 vp8; max-fr=60 b->a: rtpmap:97 vp8; max-fr=30 > > means that A can receive vp8 at 60 fps, and B can receive vp8 at 30 fps, and they just happen to use the same PT number. But the idea of "negotiating" codecs kind of doesn't match with that. Sure, but .codec is explicitly about what we should send; it will be matched against whatever is in the remote SDP. If we set .codec based on a RTCRtpSender.getCapabilities call (which the spec explicitly allows for), and the fmtp in the capabilities differs even slightly from what the remote puts in its SDP, we won't try to honor that .codec setting because it doesn't match. That's the issue here. -- GitHub Notification of comment by docfaraday Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2987#issuecomment-2307394462 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 August 2024 16:12:38 UTC