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

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

Another point I wondered about is whether the "back and forth" between the audio processing thread and the main thread to process a script node will force sub-realtime rendering for offline audio contexts in current browser architectures. 

Currently, it is not unreasonable to expect a delay of 4ms between event firing and callback invocation. That limits the number of calls that can be made to a script node to 250 calls per second. If a block size of 128 is used, that might limit the rate of generating audio samples to 32KHz. The longer the event->callback delay, the worse this gets.

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