W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2012

Re: Thoughts and questions on the API from a modular synth point of view

From: Chris Wilson <cwilso@google.com>
Date: Tue, 17 Jul 2012 12:49:18 -0700
Message-ID: <CAJK2wqVzcJ71XLZM_75WUpQumHU56dx=jKk2Cc6r83i67EY1MQ@mail.gmail.com>
To: Raymond Toy <rtoy@google.com>
Cc: Peter van der Noord <peterdunord@gmail.com>, public-audio@w3.org
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 19:49:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 17 July 2012 19:49:47 GMT