- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Sat, 13 Feb 2016 15:15:06 +0000
- To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- CC: Peter Thatcher <pthatcher@google.com>, Adam Roach <adam@nostrum.com>, Randell Jesup <randell-ietf@jesup.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Feb 13, 2016, at 06:38, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote: > > Just a small note (without the ambition to interfere with the > discussion): I think the above is also valid for maxFramerate that we > recently introduced. [BA] Where maxFramerate is combined with resolutionScaleDownBy there are benefits beyond what is possible with cloning (e.g. not possible to generate identical simulcast streams). That is not the case when maxHeight/maxWidth/maxFramerate are the sole controls - because there no longer is explicit instruction to the browser about how the simulcast encodings are to relate to each other.
Received on Saturday, 13 February 2016 15:15:39 UTC