- From: Srikumar Subramanian <srikumarks@gmail.com>
- Date: Tue, 19 Mar 2013 19:21:23 +0530
- To: Peter van der Noord <peterdunord@gmail.com>
- Cc: "public-audio@w3.org" <public-audio@w3.org>
Received on Tuesday, 19 March 2013 13:51:56 UTC
This is a long standing bug in the webkit implementation with a known workaround. If you keep around a *global* reference (in the window object itself) to either the onaudioprocess function or the script processor node itself, the arbitrary stopping won't happen. Best, -Kumar On 19-Mar-2013, at 4:40 PM, Peter van der Noord <peterdunord@gmail.com> wrote: I may be doing something wrong here, it's been a while since i created a script-processor node, but my event-handler for a scriptprocessor seems to stop firing pretty quickly. Fiddle here: http://jsfiddle.net/7LZAJ/ Strangely, the fiddle sometimes runs fine the first time, but when i refresh after that it does what happens locally here as well: the eventhandler does not get called anymore (and the remaining noisebuffer is repeated). The writing of the noise into the buffer has nothing to do with it, if my eventhandler only logs something to the console it will just stop shortly after starting (always after the same number of repetitions). Am i overlooking something? Peter
Received on Tuesday, 19 March 2013 13:51:56 UTC