- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Sat, 20 Oct 2018 08:56:43 +0000
- To: public-webrtc-logs@w3.org
Actually RTCRtpCodecCapability does not seem to cut it either, the only requires fields are mimeType and clockRate. That does not cover all the special configurations. There's sdpFmtpLine that is 'The "format specific parameters" field from the "a=fmtp" line in the SDP corresponding to the codec, if one exists.' but "if one exists" implies this is only after negotiation. Also part of the "a=fmtp" line is the codec payload type, and per [comment](https://github.com/w3c/webrtc-pc/issues/2008#issuecomment-431421369), codec payload types vary between m= sections. Not sure how this is supposed to work. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2008#issuecomment-431562545 using your GitHub account
Received on Saturday, 20 October 2018 08:56:44 UTC