- From: Peter van der Noord <peterdunord@gmail.com>
- Date: Tue, 17 Jul 2012 21:46:14 +0200
- To: Raymond Toy <rtoy@google.com>
- Cc: public-audio@w3.org
- Message-ID: <CAL9tNz9s0oTqdmn-_ecfPRuACBMedOCKC+QLbUv8CA4Tg04qRQ@mail.gmail.com>
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:46:41 UTC