> I don't see a call to OscillatorNode.noteOn() Did you scan my code, or is there a way to see all calls that are being made to the API (and its objects)? If so, i'd like to know :) Op 17 jul. 2012 om 21:49 heeft Chris Wilson <cwilso@google.com> het volgende geschreven: > It doesn't work for me either. I expect, though, that this is a coding bug hidden by a version issue - I'm using Chrome 21 (beta channel), and I don't see a call to OscillatorNode.noteOn() - which wasn't necessary in Chrome 20, IIRC, but is in 21+ (and in the spec) in order to make noise. > > On Tue, Jul 17, 2012 at 12:25 PM, Raymond Toy <rtoy@google.com> wrote: > > > On Mon, Jul 16, 2012 at 11:21 AM, Peter van der Noord <peterdunord@gmail.com> wrote: > I was actually referring to how the situation shuold be (in my opinion), not to a particular case, but having said that...these artefacts do seem to happen in my chrome (20.0.somewhat) > > http://petervandernoord.nl/patchwork_js > > - add an oscillator > - add a destination > - move the upper slider of the oscillator all the way up > - connect osc to destination > - you hear the tone go up > > > And that's all you need to do? If so, then I'm getting strange results because I hear nothing using Chrome 22.x. > > Ray > >
Received on Tuesday, 17 July 2012 20:23:31 UTC