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 this. 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