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

[webrtc-pc] sendEncodings in "create an RTPSender" should reflect platform capabilities

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Wed, 16 May 2018 10:07:13 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-323554304-1526465227-sysbot+gh@w3.org>
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc:

== sendEncodings in "create an RTPSender" should reflect platform capabilities ==
At the moment, the "create an RTPSender" steps says:

If sendEncodings is given as input to this algorithm, and is non-empty, set the [[SendEncodings]] slot to sendEncodings.
Otherwise, set it to a list containing a single RTCRtpEncodingParameters with active set to true.

This does not inform about the ability of the sender to accept multiple encoding layers.

Suggested replacement:

Initialize the [[SendEncodings]] slot to a list of RTCRtpEncodingParameters with "active" set to false. The length of the list reflects the UA's ability to send simulcast encodings.
If sendEncodings is given as input to this algorithm, copy the content of the sendEncodings into the first slots of the [[SendEncodings]] array. If sendEncodings is longer than [[SendEncodings]], discard the last values of sendEncodings.
If sendEncodings is not given, set "active" of the first element in [[SendEncodings]] to true.


Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1872 using your GitHub account
Received on Wednesday, 16 May 2018 10:07:21 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:44 UTC