W3C home > Mailing lists > Public > public-xg-audio@w3.org > February 2011

Re: Web Audio API is now available in Chrome

From: Kumar <srikumarks@gmail.com>
Date: Thu, 3 Feb 2011 00:07:00 +0800
Message-ID: <AANLkTimTS5KDzJpojEfbvNJ0URQd+XYgbeTFWnJq0QfM@mail.gmail.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Cc: Chris Rogers <crogers@google.com>, "Tom White (MMA)" <lists@midi.org>, public-xg-audio@w3.org
On Wed, Feb 2, 2011 at 5:33 PM, Silvia Pfeiffer
<silviapfeiffer1@gmail.com>wrote:

> You can hand over the audio data into the thread (i.e. web worker) and
> then have the web worker execute all the hard work on it.


Indeed. But in the case of realtime processing with JS code,
the main thread will have to wait for the response from the worker
which defeats the purpose of passing it to the worker in the first
place. That's ok for offline processing though.


> We've already had a discussion in the WHATWG about whether
> it might make sense to give web workers direct access to image and
> video data. This probably also makes sense for audio. I think we just
> have to show some use cases / good examples and that can move forward.
>

Oh yes! Access to media data in workers will be great! .. and spirit
of the patches pointed out by Olli (thanks!) aligns with what I have in
mind.
I'm a bit late into the discussion, but this is all interesting.
Received on Wednesday, 2 February 2011 16:08:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:38:00 UTC