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

Re: Constraints and MediaRecorder

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 4 Feb 2014 11:37:10 +1300
Message-ID: <CAOp6jLbvuFpOMBRpQf4N_Ds7e=yE4+84BeOV+gwFtUU=h-KTtw@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Cc: Martin Thomson <martin.thomson@gmail.com>, Harald Tveit Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On Tue, Feb 4, 2014 at 8:05 AM, Cullen Jennings <fluffy@iii.ca> wrote:

> app: get me a 48KHz recorder
> browsers: thinks to itself that it can’t do but decides that the browser
> know better than the app developer what the app app really needs and
> decides to say just take the app data from 22KHz recorder and pretend it it
> was from a 48KHz recorder
>
> I agree that an application could solve this problem with settings, or
> with capabilities, or with constraints. I’m just saying that you need one
> of those three.
>

I agree that we should provide introspection APIs when necessary for the
app to tell what it's actually getting.

Rob
-- 
Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w
Received on Monday, 3 February 2014 22:37:37 UTC

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