W3C home > Mailing lists > Public > www-tag@w3.org > July 2013

Re: "ScriptProcessorNode is Unfit For Purpose" issue

From: Chris Rogers <crogers@google.com>
Date: Fri, 26 Jul 2013 13:11:54 -0700
Message-ID: <CA+EzO0=iUZyOG-JpMCEQFhAcAxHoWXQxecNvVqkRYh63CzuTRA@mail.gmail.com>
To: Chris Wilson <cwilso@google.com>
Cc: "Robert O'Callahan" <robert@ocallahan.org>, Alex Russell <slightlyoff@google.com>, "public-audio@w3.org" <public-audio@w3.org>, "www-tag@w3.org List" <www-tag@w3.org>, Olivier Thereaux <Olivier.Thereaux@bbc.co.uk>
On Fri, Jul 26, 2013 at 8:35 AM, Chris Wilson <cwilso@google.com> wrote:

> On Thu, Jul 25, 2013 at 4:50 PM, Robert O'Callahan <robert@ocallahan.org>wrote:
>> ...The reality is that a lot of the things you might want to do when
>> generating audio data (e.g. implement a game emulator) can only be done on
>> the main thread today, so for many applications audio-generating Workers
>> would not be immediately useful.
> I'm not sure I understand why that statement is true, outside of the
> fairly narrow "emulate a single-threaded hardware platform" scenario.  For
> all of the uses I've considered for ScriptProcessor, workers would be much
> better.

I agree with Roc's position here.  It's useful to be able to use
ScriptProcessor in the main thread, as well as a worker thread.
Received on Friday, 26 July 2013 20:12:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:58 UTC