W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2018

Re: [webrtc-pc] Using codecPayloadType with addTransceiver()

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Sun, 21 Oct 2018 18:09:57 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-431690661-1540145391-sysbot+gh@w3.org>
@henbos Perhaps we can describe two potential approaches with pros/cons and get feedback from the WG?

* Approach 1: Make `codecPayloadType` read-only.  `sendEncodings` passed to `addTransceiver` apply to any codec.  To discover what encodings an codecs are actually set, call `getParameters` after negotiation is complete. Chances of surprise can be minimized using `setCodecPreferences`. 

* Approach 2: Add `preferredPayloadType` to `RTCRtpCodecCapability` and allow `codecPayloadType` to be set. `sendEncodings` is validated based on the codec specified, which must be in the list of codecs returned by `getCapabilities`.  To discover what encodings are actually set, call `getParameters` after negotiation is complete. If the negotiated codec is not the same as in `codecPayloadType` then the specified encodings are not set.  The chance of this can be minimized using `setCodecPreferences`. 

-- 
GitHub Notification of comment by aboba
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2008#issuecomment-431690661 using your GitHub account
Received on Sunday, 21 October 2018 18:10:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:07 UTC