- From: <bugzilla@jessica.w3.org>
- Date: Fri, 19 Jul 2013 22:08:49 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22723 --- Comment #9 from Srikumar Subramanian (Kumar) <srikumarks@gmail.com> --- 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. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 19 July 2013 22:08:50 UTC