W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2014

Re: Call for Consensus: retire current ScriptProcessorNode design & AudioWorker proposal

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 13 Aug 2014 15:01:35 +1200
Message-ID: <CAOp6jLY2npxdCuMS5xwXtxuo_jC_AwU5GvkJMT85cSBSaEz4Ug@mail.gmail.com>
To: "Srikumar K. S." <srikumarks@gmail.com>
Cc: Alan deLespinasse <adelespinasse@gmail.com>, Chris Wilson <cwilso@google.com>, Joseph Berkovitz <joe@noteflight.com>, Raymond Toy <rtoy@google.com>, Olivier Thereaux <olivier.thereaux@bbc.co.uk>, Audio WG <public-audio@w3.org>
On Wed, Aug 13, 2014 at 2:59 PM, Srikumar K. S. <srikumarks@gmail.com>

> > On 13 Aug 2014, at 8:09 am, Robert O'Callahan <robert@ocallahan.org>
> wrote:
> > Another option that we've talked about before is having an API for
> OfflineAudioContext that lets you tell it to produce N samples
> (asynchronously) and then pause, firing a notification callback when it's
> paused. I think that's a pretty good solution for many use-cases, including
> dynamic graph reconfiguration.
> Agreed.  That would solve the problem of having to create all nodes
> involved throughout an offline render at one shot.

Yes. This would also be a good API if you want to generate batches of N
samples and do something with those batches, e.g. stream them somewhere.

oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo
owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo
osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo
osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o
oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo
osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro
otohoeo ofoioroeo ooofo ohoeololo.
Received on Wednesday, 13 August 2014 03:02:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:14 UTC