- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Mon, 24 Mar 2014 09:46:27 -0700
- To: "Mandyam, Giridhar" <mandyam@quicinc.com>
- Cc: Jan-Ivar Bruaroey <jib@mozilla.com>, Harald Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Rolling back up the thread a little...
On 24 March 2014 07:31, Mandyam, Giridhar <mandyam@quicinc.com> wrote:
> For instance, say that getNativeSettings() returns {“frame rate”: 30.0, …}.
> However, a MediaStream was successfully created with {“mandatory”:{“frame
> rate”: 60.0} …}. Then the developer could have an indication as to whether
> the UA is applying post-processing in trying to meet the mandatory
> constraint, and may choose to adjust the constraint back to 30 fps to avoid
> any UA-introduced processing delay.
I recall that on numerous occasions we have had discussions where
everyone violently agrees that no information should be constructed to
meet a constraint. That means no interpolation to increase frame rate
or resolution and probably a few other things I'm to fried to think of
right now.
Received on Monday, 24 March 2014 16:49:38 UTC