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

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

From: Chris Wilson <cwilso@google.com>
Date: Tue, 12 Aug 2014 08:23:10 -0700
Message-ID: <CAJK2wqV4PY6TatZLMbO6Hwqzh=FxwF+15aM79BU1a=wTMegSHA@mail.gmail.com>
To: "Robert O'Callahan" <robert@ocallahan.org>
Cc: Olivier Thereaux <olivier.thereaux@bbc.co.uk>, Audio WG <public-audio@w3.org>
On Mon, Aug 11, 2014 at 7:47 PM, Robert O'Callahan <robert@ocallahan.org>

> I don't think we should remove anything from the spec until we're
> confident that we can drop support.

OK.  I can mark it as deprecated for now.

> Furthermore, I think there are two use-cases where the current main-thread
> API is actually OK:
> -- Capturing and analyzing audio data, i.e., a pure sink.
> -- Generating audio data, i.e., a pure source.
> The current main-thread API only really sucks when you're trying to take
> input and produce output. Is there disagreement about that?

Actually, in both of those cases it's still sub-optimal due to its design.
 There will always be latency introduced due to the thread-passing, and
you'll always have to continually alloc and dealloc new Buffers to prevent
races.  Its only benefit is simplicity in implementation (namely, that you
don't have to use postmessage to transfer parameters).
Received on Tuesday, 12 August 2014 15:23:42 UTC

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