Re: [web-audio-api] OfflineAudioContext and ScriptProcessorNodes (#69)

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=22723#11) by Srikumar Subramanian (Kumar) on W3C Bugzilla. Fri, 19 Jul 2013 22:40:00 GMT

(In reply to [comment #11](#issuecomment-24244200))
> The 4ms delay is probably with relation to setTimeout(), right?  That is
> enforeced artificially by browsers in order to prevent web pages from
> spamming the main thread in exactly this way, it is not the actual delay of
> event delivery.  In reality, the event delivery delays really depend on a
> lot of factors invisible to the web application, such as how busy the event
> loop is.  But it should be *much* lower than 4ms under most circumstances.

Not entirely. With the realtime script processor nodes, I've needed a buffer size of at least 1024 to avoid glitches due to UI events. Since that amounts to 23ms, I thought I was being rather optimistic in picking 4ms :)

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/69#issuecomment-24244205