- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Sat, 5 Dec 2015 04:29:10 +0100
- To: Adam Bergkvist <adam.bergkvist@ericsson.com>, Dan Burnett <dburnett@voxeo.com>
- Cc: "public-webrtc-editors@w3.org" <public-webrtc-editors@w3.org>
Den 04. des. 2015 21:04, skrev Adam Bergkvist:
> Hmm.. After taking an other look at the MediaTrackCapabilites dictionary
> again I noted that it looks like:
>
> (double or DoubleRange) frameRate;
>
> So it's not a ConstrainDouble (where exact lives).
>
> So I guess it needs to be same max and min for now.
Actually "double or DoubleRange" means that you need to show:
aspcectRatio: 1.33333333333
to show that there can be a naked value in capabilities (and you need to
show it to the limit of precision of a double).
In capabilities, it means "can only do this exact value", not "want
something like this".
>
> /Adam
>
> On 2015-12-04 18:28, Dan Burnett wrote:
>> +1 to Adam's answer and to Harald's.
>>
>> -- dan
>>
>> On Dec 4, 2015, at 10:04 AM, Harald Alvestrand wrote:
>>
>>> Den 04. des. 2015 10:59, skrev Adam Bergkvist:
>>>> Hi
>>>>
>>>> In Example 11 we have a MediaTrackCapabilites structure with:
>>>>
>>>> aspectRatio: {
>>>> min: 1.3333333333,
>>>> max: 1.3333333333
>>>> }
>>>>
>>>> Setting min and max to the same value is the old syntax for saying
>>>> "exact" right? So now we could actually say:
>>>>
>>>> aspectRatio: { exact: 1.3333333333 }
>>>>
>>>
>>>
>>> Yes, that's what we should say.
>>>
>>> We should also have an exacmple with min: 1.3333 max: 1.7778 (has to be
>>> between 4:3 and 16:9).
>>>
>>
>>
>>
>
Received on Saturday, 5 December 2015 03:29:42 UTC