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:52:46 +1300
Message-ID: <CAOp6jLaKwT6whOzGxO7JrDAu1VXvmX4VN8rdbkCUgGnGv1DGyg@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On Tue, Feb 4, 2014 at 11:39 AM, Cullen Jennings <fluffy@iii.ca> wrote:

> Thought on how to dynamical sense what frequency ranges work? seems hard
> to differentiate from a quiet room.

Generate a test signal through the browser? Have the user do a first-run
check that things are working? It seems like you'd want to do one of these
anyway, even if the browser thinks things are OK.

Having said that, we should certainly expose what the browser knows about
the sample rate of an audio track.

Anyway I meant to stick to talking about MediaRecorder and your examples
have lured me away from that.

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:53:14 UTC

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