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:47 -0700
Message-ID: <CAJK2wqUfwQUeWiYh6JN8ZBACTyG31+A4o1vWv63o_KY3iG4Acg@mail.gmail.com>
To: Peter van der Noord <peterdunord@gmail.com>
Cc: Raymond Toy <rtoy@google.com>, public-audio@w3.org
I think Ray meant "I don't hear any sound" - because I don't either.  You
need to call noteOn().

On Tue, Jul 17, 2012 at 12:46 PM, Peter van der Noord <peterdunord@gmail.com
> wrote:

> I assume that by "I hear nothing using Chrome 22.x" you mean that you
> don't hear the artefact, but do hear sound?
>
> And yes, that's all i have to do. It doesn't matter how long i wait after
> twiddling the slider (which directly sets the value on the audio-param)
> before connecting it to the destination, i always hear the frequency jump
> quickly to the final value (seems to be always in the same amount of time,
> less 0.25s).
>
> But if you hear nothing with a newer version (i run 20.x) then there's no
> problem right? I should just update.
>
> Peter
>
>
> 2012/7/17 Raymond Toy <rtoy@google.com>
>
>>
>>
>> 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:50:10 GMT

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