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

Re: Resolution changes

From: Harald Alvestrand <harald@alvestrand.no>
Date: Mon, 14 Sep 2015 20:20:25 -0700
To: Jan-Ivar Bruaroey <jib@mozilla.com>, Martin Thomson <martin.thomson@gmail.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <55F78E79.5090302@alvestrand.no>
On 09/14/2015 07:20 PM, Jan-Ivar Bruaroey wrote:
> On 9/14/15 9:17 PM, Harald Alvestrand wrote:
>> On 09/14/2015 02:38 PM, Martin Thomson wrote:
>>> What happens when MediaStreamTrack changes resolution to something
>>> outside of the negotiated envelope of the session?  There is no
>>> language in the spec.  Presumably if the resolution can be reduced,
>>> reduce it.  Increasing resolution might be the only option we have in
>>> the case that the session has a resolution floor.
>> Section 5:
>>
>> Let's look at a slightly different situation starting from the same
>> point. In this case, instead of the first track attempting to apply a
>> conflicting constraint, the user physically locks the camera into a
>> mode where the fill light is on. At this point the source can no
>> longer satisfy the second track's mandatory constraint that the fill
>> light be off. The second track is transitioned into the muted state
>> and receives an |overconstrained|
>> <http://w3c.github.io/mediacapture-main/getusermedia.html#event-mediastreamtrack-overconstrained> event.
>>
>> More info in section 11.1.1.
>
> Constraints are properties of the application, not the browser, and no
> constraints were violated here.

I don't even know what this means, but if it has meaning, I think you're
wrong.
the "light must be off" constraint is violated whenever the light is on.
Received on Tuesday, 15 September 2015 03:20:59 UTC

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