102439 2012-11-15 15:15:11 -0800 Audio graph nodes stuck in "scheduled" state 2012-11-16 13:13:06 -0800 1 1 1 Unclassified WebKit Web Audio 528+ (Nightly build) Mac (Intel) OS X 10.8 RESOLVED DUPLICATE 97369 http://jsfiddle.net/alnitak/pUBLm/13/ P2 Normal --- 0 ray crogers crogers oldest_to_newest 768553 0 ray 2012-11-15 15:15:11 -0800 In the linked code, an Oscillator used as a source in a side chain used to control a filter's cutoff frequency remains stuck in the "scheduled" state. The code works correctly in Chrome 25, but doesn't work in Chrome 23 or Safari 6.0.2. This second oscillator (running as an LFO in this demo) is connected to a GainNode so that the amplitude of the change to the filter cutoff can be controlled. I've verified that the problem persists if I remove that GainNode, although at that point the +/- 1 output from the LFO is insufficient to make the cutoff modulation audible. If the LFO is also connected to the primary oscillator's frequency AudioParam then it correctly starts up. 768555 1 ray 2012-11-15 15:18:00 -0800 NB: this code is cut down as much as I could to still demonstrate the problem. The real use case in my own code is that I'm trying to use that side chain to emulate a VCF envelope generator, but in the earlier WebKit builds that are in the released versions it appears to be impossible to use an AudioNode to modulate a BiquadFilterNode's cutoff frequency. 769588 2 crogers 2012-11-16 12:48:54 -0800 Ray, thanks for the example. I can't see from your code how the test is "passing" or "failing". In other words how are checking that it's "stuck" or "unstuck". Can you please update your test to explain more fully the problem you're seeing. 769591 3 ray 2012-11-16 12:51:29 -0800 Look in the console - the value of 1 being printed in the setTimeout callback on Chrome 23 indicates "scheduled" (i.e. it never ran) whereas Chrome 25 shows 2 ("running"). 769594 4 ray 2012-11-16 12:52:47 -0800 jsfiddle updated 769606 5 crogers 2012-11-16 13:06:42 -0800 Ray, thanks for updating the test. It looks like it's simply this bug which was fixed here: https://bugs.webkit.org/show_bug.cgi?id=97369 Chrome 23 and Safari 6 have not yet picked up this change. But Chrome Canary and WebKit nightly builds will have the fix. *** This bug has been marked as a duplicate of bug 97369 *** 769611 6 ray 2012-11-16 13:11:04 -0800 Is there any known workaround? 769614 7 crogers 2012-11-16 13:13:06 -0800 (In reply to comment #6) > Is there any known workaround? I don't think so, we just have to wait for the fix to percolate into the stable shipping browsers. Chrome 24 may get this fix.