W3C home > Mailing lists > Public > public-media-capture@w3.org > August 2014

Re: [Bug 26526] Fix aspect ratio constraint

From: cowwoc <cowwoc@bbs.darktech.org>
Date: Tue, 19 Aug 2014 10:57:52 -0400
Message-ID: <53F365F0.1010606@bbs.darktech.org>
To: public-media-capture@w3.org
On 19/08/2014 10:40 AM, Harald Alvestrand wrote:
>> You also seem to assume that people will specify constant values as 
>> opposed to calculating the desired value programmatically. That's not 
>> necessarily true. I may very well decide to create a dynamic viewport 
>> depending on what is going on in my application at a given time and 
>> its aspect ratio might change across runs (this is even more true in 
>> the context of desktop web browsers where the window size changes on 
>> a regular basis).
>
> In that case, it's even more important that the user (programmer) be 
> trained to give the system the chance to make approximations - if 
> aspect ratios are dynamic, they will very often be impossible to hit 
> exactly, due to things like granularity of codec macroblocks 
> (typically 16 pixels).
>
> And it's even less likely that the epsilon will matter in practice.

Discussing this in more detail, how does the API enable developers to 
implement this use-case? Certainly a developer will want the biggest 
video box smaller than [X, Y] and then he might have preferences in 
terms of the aspect ratio. For example, one developer might prefer 
widescreen aspect ratios while another might prefer 4:3 (depending on 
say ... whether they are broadcasting multimedia or screen sharing a 
remote desktop). How does the API allow the developer to express such 
constraints?

Gili
Received on Tuesday, 19 August 2014 14:59:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:29 UTC