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

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

From: <bugzilla@jessica.w3.org>
Date: Thu, 26 Jul 2012 12:57:58 +0000
Message-Id: <E1SuNde-000874-Cp@jessica.w3.org>
To: public-audio@w3.org

--- Comment #50 from Philip J <philipj@opera.com> 2012-07-26 12:57:57 UTC ---
Grant, it seems to me that there are at least two options for main-thread audio
generation even if there's no JavaScriptAudioNode.

1. Generate your audio into AudioBuffers and schedule these to play
back-to-back with AudioBufferSoruceNodes. (I haven't tried if the WebKit
implementation handles this gapless, but I don't see why we shouldn't support
this in the spec.)

2. Generate your audio into AudioBuffers and postMessage these to a
WorkerAudioNode. If ownership of the buffer is transferred it should be cheap
and there's no reason why this should incur a large delay, particularly not
half a second like you've seen. That sounds like a browser bug to be fixed.

In both cases one will have one new object per buffer to GC, in the first case
it's a AudioBufferSourceNode and in the second case it's the event object on
the worker side.

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 Thursday, 26 July 2012 12:58:02 UTC

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