W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2016

Re: maxHeight and maxWidth

From: Adam Roach <abr@mozilla.com>
Date: Fri, 12 Feb 2016 21:20:52 -0600
To: Bernard Aboba <Bernard.Aboba@microsoft.com>, Peter Thatcher <pthatcher@google.com>
Cc: Adam Roach <adam@nostrum.com>, Randell Jesup <randell-ietf@jesup.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <56BEA114.1000601@mozilla.com>
On 2/12/16 19:23, Bernard Aboba wrote:
> On Feb 12, 2016, at 3:15 PM, Peter Thatcher <pthatcher@google.com 
> <mailto:pthatcher@google.com>> wrote:
>
>> If you want glitch-free scale down and scale up, I believe we already 
>> have the controls you need: clone the track, apply constraints, and 
>> make 2 RtpSenders. It's not as convenient as using encoding 
>> parameters but it works.
>
> [BA] That's what bugs me about this - the only reason to add another 
> attribute to RTCRtpEncodingParameters is if it enables developers to 
> do something they cannot already accomplish with track cloning.
>
> But so far, we haven't considered a scenario that cannot be 
> accomplished with what we already have.

The clone/constrain/send solution has the same flaws in this case as it 
does in the general case. We already rejected that approach.

-- 
Adam Roach
Principal Platform Engineer
Office of the CTO
Received on Saturday, 13 February 2016 03:21:27 UTC

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