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: Peter van der Noord <peterdunord@gmail.com>
Date: Mon, 16 Jul 2012 20:21:03 +0200
Message-ID: <CAL9tNz8ejhtwTXFN=t8ABQjvM9LDS=f5H5UJ7Kgta_nKPHNdUA@mail.gmail.com>
To: Raymond Toy <rtoy@google.com>
Cc: public-audio@w3.org
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

Peter

2012/7/16 Raymond Toy <rtoy@google.com>

>
>
> On Mon, Jul 16, 2012 at 11:03 AM, Peter van der Noord <
> peterdunord@gmail.com> wrote:
>
>> I'm not very aware about the different states of modules, but it
>> shouldn't matter if a module is connected or not. It just plays all the
>> time. You get very strange and unexpected results when you're live playing
>> (connecting/disconnecting) with the different nodes and some of them are
>> producing old data.
>>
>
> If you have some short examples that illustrate these problems, I'd like
> to know.  Or, if you're using chrome, file a bug report at
> bugs.chromium.org.
>
> Ray
>
>
Received on Monday, 16 July 2012 18:21:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 16 July 2012 18:21:32 GMT