W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > September 2017

[webrtc-pc] new commits pushed by burnburn

From: Daniel Burnett via GitHub <sysbot+gh@w3.org>
Date: Thu, 14 Sep 2017 14:15:51 +0000
To: public-webrtc-logs@w3.org
Message-ID: <push-dc29eef7cab9a25dfaf85edf10ee25c43ebb4d8d-1505398540-sysbot+gh@w3.org>

The following commits were just pushed by burnburn to https://github.com/w3c/webrtc-pc:

* Select sent codec via "codecPayloadType" field rather than reordering.

Fixes #1207.

Instead of selecting a codec by reordering the list from
`getParameters`, an application will now pick the payload type of
its preferred codec and set it in `RTCRtpEncodingParameters`. This
matches ORTC, and fixes the linked issue, because as long as the
selected codec is still present in a new offer/answer exchange, it will
stay selected.

If the selected codec is *not* present in a new offer/answer exchange,
the implementation will go back to its normal policy, which is the same
behavior as before this PR.

Note that this PR puts the `codecPayloadType` field on
`RTCRtpEncodingParameters`, which means the codec may be different
per-encoding, which wasn't possible before. If this is an issue, it
could be moved to the `RTCRtpParameters` level instead.
  by Taylor Brandstetter

* Change payload type fields to octet.
  by Taylor Brandstetter

* Codec params don't have "name" in WebRTC 1.0, they have "mimeType".
  by Taylor Brandstetter

* unsigned short -> octet for codecPayloadType in table
  by Bernard Aboba

* Merge pull request #1592 from taylor-b/issue_1207_add_codecpayloadtype

Select sent codec via "codecPayloadType" field rather than reordering.
  by Daniel Burnett
Received on Thursday, 14 September 2017 14:15:44 UTC

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