- From: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
- Date: Tue, 13 Mar 2012 20:49:53 +0200
- To: Chris Lowis <chris.lowis@bbc.co.uk>
- Cc: public-audio@w3.org
- Message-ID: <CAJhzemX+UyYyOFqc08ksU=McR=N6GO1-YZaby-qOGvmsAo5QYQ@mail.gmail.com>
Hey there, Chris! Just thought I'd let you know that here's [1] an adaptation of the Oscillator class in audiolib.js made for specifically for the Web Audio API, as I think I promised a long while ago. It behaves almost like a native citizen of the graph, initialized with context.createOscillator(), responding to connect() and disconnect(), but it doesn't have access to AudioParams, which would make it possible to have smooth transitions, automations etc. (*wink wink* I think I'm repeating myself here), especially useful for things like fm. Chris (Rogers): While at it I noticed that Chrome bug 82795 [2] is still not fixed. Cheers, Jussi [1] http://labs.avd.io/WebAudioAPI/oscillator.html [2] http://code.google.com/p/chromium/issues/detail?id=82795 On Tue, Mar 13, 2012 at 6:05 PM, Chris Lowis <chris.lowis@bbc.co.uk> wrote: > On 13/03/2012 15:59, Chris Lowis wrote: > >> but I'm wondering if there's a simpler >> place for me to start. >> > > Apologies for the reply to self, but I found this: > http://0xfe.blogspot.com/2011/**08/generating-tones-with-web-** > audio-api.html<http://0xfe.blogspot.com/2011/08/generating-tones-with-web-audio-api.html> > > which looks like a good place to start. I'd still be interested in any > comments or suggestions though! > > Best, > > Chris > >
Received on Tuesday, 13 March 2012 18:50:26 UTC