W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

[Bug 17415] (JSWorkers): JavaScriptAudioNode processing in workers

From: <bugzilla@jessica.w3.org>
Date: Tue, 12 Jun 2012 14:59:53 +0000
To: public-audio@w3.org
Message-Id: <E1SeSZV-0004iy-Sx@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #6 from Philip J <philipj@opera.com> 2012-06-12 14:59:53 UTC ---
(In reply to comment #5)

> expensive tricks like sending the audio data to the worker with
> postMessage and maintaining the callback system themselves

That's not how a worker-based AudioNode would work, it would be a callback in
the worker that can read directly from the input and write directly to the
output.

There are things on the main thread that are not interruptible (layout and
event handlers being the most obvious) so it's only luck if one is able to run
the callback often enough. I can't speak for any other implementors, but I'm
fairly certain it would fail horribly in Opera, as other pages running in the
same process can't be expected to write code to avoid long-running scripts or
expensive re-layouts.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 12 June 2012 15:00:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 12 June 2012 15:00:05 GMT