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: Mon, 30 Jul 2012 00:49:42 +0000
Message-Id: <E1SveB4-0005YE-Cu@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #81 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> 2012-07-30 00:49:41 UTC ---
(In reply to comment #59)
> AFAICT, the noteOn & AudioParam interfaces were designed for making it possible
> to schedule sample accurate audio actions ahead of time. I think that it
> *should* be possible to use it for providing gap-less audio playback (typically
> using a few AudioBuffers in a multi-buffering manner and scheduling them with
> AudioBufferSourceNodes). The problem, as it seems, is that you need to
> accommodate for possible jittering and event drops, possibly by introducing a
> latency (e.g, would it work if you forced a latency of 0.5s?).

I think a solution that uses setInterval() to schedule frequent JS callbacks,
checks AudioContext.currentTime to measure the progress of the audio clock, and
uses AudioBufferSourceNodes to queue playback of generated audio buffers,
should work as well as any other, providing the Web Audio implementation is
adequate. Incremental GC might also be required.

-- 
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 Monday, 30 July 2012 00:49:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 July 2012 00:49:44 GMT