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

Re: Constraints and MediaRecorder

From: Jan-Ivar Bruaroey <jib@mozilla.com>
Date: Mon, 03 Feb 2014 14:55:14 -0500
Message-ID: <52EFF422.80204@mozilla.com>
To: Harald Alvestrand <harald@alvestrand.no>, Martin Thomson <martin.thomson@gmail.com>, Cullen Jennings <fluffy@iii.ca>
CC: Robert O'Callahan <robert@ocallahan.org>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 2/3/14 2:35 PM, Harald Alvestrand wrote:
> On 02/03/2014 06:32 PM, Martin Thomson wrote:
>> These are all fine, but this offers little material support for the
>> use of constraints in this specific use case.  Is there anything wrong
>> with:
>>
>> app: get me a 96kHz recorder
>> browser: can't do that
>>
>> Because that's what is being suggested.
> It seems to me more complex to do:
>
> app: get me a 96khz recorder
> browser: can't do that
> app: get me a 80khz recorder
> browser: can't do that
> app: get me a 48khz recorder
> browser: can't do that
> app: get me a 44.1khz recorder
> browser: ok, here's one
>
> than to do
>
> app: get me a recorder absolutely above 40 khz, prefer one above 80 khz
> browser: ok, here's an 88.2khz recorder

The first one is simpler because the second one is a new language.

I prefer:

app: get me a 96khz recorder
browser: keep dreaming, here's 48khz, best I can do.

.: Jan-Ivar :.
Received on Monday, 3 February 2014 19:55:37 UTC

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