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

Re: New issue: switching sources

From: Peter Thatcher <pthatcher@google.com>
Date: Tue, 20 May 2014 09:05:44 -0700
Message-ID: <CAJrXDUE5opAb3cTvxNWb-CTL1d4t6ZpkYb=y+b016N8A8jrO0A@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Jim Barnett <1jhbarnett@gmail.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Ah, good point.  So via setLocalDescription and setRemoteDescription, the
JS tells the browser to send codec X, but then tells it to send from source
Y with hardware codec Z.  Well, in that case, I'd say do what the JS told
the browser to do: send with codec X (without hardware encoding).  Yes,
that is a danger and we should document it clearly if we decide to support

On Tue, May 20, 2014 at 7:58 AM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 20 May 2014 07:27, Peter Thatcher <pthatcher@google.com> wrote:
> > What do you mean by "understand the dangers"?  What dangers are there?
> Like the one where you have negotiated codec X and you switch in a
> stream that is attached to a hardware encoder with only codec Y.
Received on Tuesday, 20 May 2014 16:06:52 UTC

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