- From: Jonathan Baudanza <jon@jonb.org>
- Date: Tue, 24 Jul 2012 12:38:30 -0400
- To: Audio Working Group <public-audio@w3.org>
- Message-ID: <CAP26MZvo2tO2bj9pF0uW4_qD0XKLcai_Qi7oNJwhLWmW0=CnOQ@mail.gmail.com>
On Tue, Jul 24, 2012 at 11:40 AM, Adam Goode <agoode@google.com> wrote: > > I essentially want to have a callback for getting new control data, to > keep the event pipeline filled without overflowing any noteOn buffer or > falling behind. Is the javascript node appropriate for this? I feel like > there could be something more explicit, like a setInterval off of the audio > context. > > I've run into the same issue, and this has been discussed on the list before. http://lists.w3.org/Archives/Public/public-audio/2011OctDec/0080.html AFAIK, either using setTimeout or a JavaScriptNode is the currently the best solution. There is an issue in the webkit issue tracker to create a callbackAtTime() method on audio context. https://bugs.webkit.org/show_bug.cgi?id=70061 I'm not sure if a similar issue exists on the Web Audio API issue tracker, but there probably should be one. I don't think window.requestAnimationFrame() is a solution, because the callback is only called when the browser frame is visible.
Received on Tuesday, 24 July 2012 16:39:04 UTC