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: Fri, 27 Jul 2012 03:04:45 +0000
Message-Id: <E1Suar7-00019K-Gq@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #56 from Grant Galitz <grantgalitz@gmail.com> 2012-07-27 03:04:44 UTC ---
(In reply to comment #55)
> What frequency do you need to run the code at? With setInterval you should be
> able to get 4ms.

I use a ms setInterval as the base driver. The rate of the setInterval is not
the problem. The problem lies with the fact that setinterval was designed,
rightfully so, to skip a call if there was a buildup of delays. Audio gen by
this method should never be conducted without audio clok heurisitics as a
result of this. Proper audio gen should always check to see the respective
buffering levels, as a system can skip a setInterval callback due to unexpected
latency. Also some browsers, like google chrome, have A LOT of jitter in their
setInterval and skip an unnecessarily large amout of setInterval calls. If I
disabled audio clock input, we would be hearing a lot of crackles and pops
across the board in every browser if we simply just timed by setInterval.

-- 
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 Friday, 27 July 2012 03:04:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 July 2012 03:04:47 GMT