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

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

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:35 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/69/24244200@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=22723#10) by Ehsan Akhgari [:ehsan] on W3C Bugzilla. Fri, 19 Jul 2013 22:25:44 GMT

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.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/69#issuecomment-24244200
Received on Wednesday, 11 September 2013 14:33:46 UTC

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