-
Notifications
You must be signed in to change notification settings - Fork 42
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
Payload Type #147
Comments
This does not appear to be an API issue, as noted by Robin: However, it might be worth clarifying getCapabilities() behavior as noted here: |
Potential clarification to Section 9.4.1 is to add the following text to the definition of preferredPayloadType: preferredPayloadType of type payloadtype |
Proposed revision for clarity: "The preferred RTP payload type for the codec denoted by RTCRtpCodecCapability.name. This attribute was added to make it possible for the sender and receiver to pick a matching payload type when creating sender and receiver parameters. When returned by RTCRtpSender.getCapabilities(), RTCRtpCapabilities.codecs.preferredPayloadtype represents the preferred RTP payload type for sending. When returned by RTCRtpReceiver.getCapabilities(), RTCRtpCapabilities.codecs.preferredPayloadtype represents the preferred RTP payload type for receiving. To avoid payload type conflicts, each value of RTCRtpCodecCapability.name should have a unique value of RTCRtpCodecCapability.preferredPayloadtype." |
👍 |
…3c#146 Address questions about RTCRtpCodecCapability.preferredPayloadType, as noted in: Issue w3c#147 Address questions about RTCRtpSender.setTrack() error handling, as noted in: Issue w3c#148 Partially address 'automatic' use of scalable video coding (in RTCRtpReceiver.receive()) as noted in: Issue w3c#149 Renamed RTCIceListener to RTCIceGatherer as noted in: Issue w3c#150 Added text on multiplexing of STUN, TURN, DTLS and RTP/RTCP, as noted in: Issue w3c#151 Address issue with queueing of candidate events within the RTCIceGatherer, as noted in: Issue w3c#152 Clarify behavior of RTCRtpReceiver.getCapabilities(kind), as noted in: Issue w3c#153
From Iñaki Baz Castillo [[email protected]]:
When I create a RTCRtpSender instance and add a track and
then get the RTCRtpCapabilities.codecs, would them indicate the
sending RTP payload? or the payload to expect in the incoming RTP
packets in the same transport?
IMHO it makes lot of sense that those payload values are the sending
ones (given that this is not SDP O/A party and thus there is no need
to negotiate incoming RTP when we send), but in the case of "SDP O/A
emulation", does it mean that I should "manually" override those
"payload" values with the remote info once I've initiated my
RTCRtpSender and received the remote "description"?
The text was updated successfully, but these errors were encountered: