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 21:32:32 +0000
Message-Id: <E1SvxZo-000055-JI@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #84 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> 2012-07-30 21:32:31 UTC ---
(In reply to comment #83)
> Can we add callbacks for when a buffer is done playing?

No, because they will fire too late for you to queue the next buffer and get
seamless playback.

(In reply to comment #82)
> I seriously don't like the idea of using setInterval callbacks to drive the
> callback procedure instead of an actual callback derived from the audio clock.

You're going to have to schedule timeouts early anyway to maximise the chance
that your callback runs in time to schedule the next buffer seamlessly, so
accuracy doesn't matter, so using the audio clock instead of the system clock
doesn't matter since there will be negligible drift over the intervals we're
talking about.

-- 
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 21:32:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 July 2012 21:32:34 GMT