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

Re: Configuring codecs

From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 12 Oct 2015 22:04:05 -0700
Message-ID: <CAJrXDUF-DfG6CXHDdZQWNkPzSoaea0GFW3H+9Kwz+yVaTgvjrg@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
A few questions:

1.  This will work with createAnswer, correct?

2.  Does this applies to all RtpSenders?   What if the app wants different
codecs for different RtpSenders?

3.  If {codecs: ...} is not provided in a subsequent createOffer, does it
use the last given value or revert to the default?

4.  Did you consider put {codecs: ...} on addTransceiver or addTrack?  It
might make sense there as a per-RtpSender option that is set once rather
than for each call to createOffer.  On the other hand, it's not as easy to
use that for controlling what happens in createAnswer.

On Mon, Oct 12, 2015 at 3:08 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> We now have a tool for configuring the codecs that we use once they
> are negotiated.  However, we don't have a way to guide the negotiation
> part.  Until:
>
>    https://github.com/w3c/webrtc-pc/pull/326
>
> Now, all you need to do is acquire some capabilities...
>
> var codecs = RTCRtpSender.getCapabilities().codecs;
>
> ...filter and reorder...
>
> codecs = codecs.filter(isCodecGood);
> codecs.sort(whichCodecIsBetter);
>
> ...and then
>
> pc.createOffer({codecs: codecs})
>   .then(profit)
>
>
Received on Tuesday, 13 October 2015 05:05:13 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:46 UTC