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 13:56:54 +1200
Message-ID: <CAOp6jLZbMw=GKtiXVcmTD1n9QmqW41ZsidaTxYxozBC6YzkvVA@mail.gmail.com>
To: adelespinasse@gmail.com
Cc: "Srikumar K. S." <srikumarks@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 1:33 PM, Alan deLespinasse <adelespinasse@gmail.com>

> What about synchronous graph manipulation? Is there a consensus on that,
> and will that be part of the new spec?
> That is, the ability to modify the node graph (add/remove nodes or
> connections, modify parameters) from the script node callback. Or maybe
> from another timed callback that doesn't produce or consume audio samples
> (presumably also in the worker thread).

For normal AudioContexts, I don't think we need a special callback for
graph modification.

For offline AudioContexts, we do need a synchronous callback that fires
when a certain number of samples have been processed and guarantees that
more progress is not made until the callback returns.

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 01:57:22 UTC

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