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

[webrtc-pc] Using codecPayloadType with addTransceiver()

From: Florent Castelli via GitHub <sysbot+gh@w3.org>
Date: Thu, 18 Oct 2018 14:53:26 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-371570836-1539874405-sysbot+gh@w3.org>
Orphis has just created a new issue for https://github.com/w3c/webrtc-pc:

== Using codecPayloadType with addTransceiver() ==
The `codecPayloadType` values come from a sender's `getParameters()` call. It seems to me that it isn't then possible to have a `addTransceiver()` call with `sendEncodings` specifying a codec to use (and possibly a scalability mode later).

To force a single codec to be used, I imagine it's possible to use `setCodecPreferences()` with a single entry, but it would prevent negotiation of other codecs, which is less than ideal.

Would the recommended usage be then to:
- Create a generic transceiver with no forced codec in sendEncodings
- Do the negotiation
- Call getParameters() to retrieve the codecPayloadType values
- Call setParameters() to set the codecPayloadType (and possibly the scalability mode)
- Call replaceTrack() to finally start the transmission with the right settings

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2008 using your GitHub account
Received on Thursday, 18 October 2018 14:53:27 UTC

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