W3C home > Mailing lists > Public > public-xg-audio@w3.org > February 2011

Re: Web Audio API is now available in Chrome

From: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Date: Thu, 3 Feb 2011 22:21:05 +0200
Message-ID: <AANLkTik8KyCtJNxDjXOZeBBeey4Z4Uaq=pDevb0iftt4@mail.gmail.com>
To: Chris Rogers <crogers@google.com>
Cc: srikumarks@gmail.com, Alistair Macdonald <al@bocoup.com>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, "Tom White (MMA)" <lists@midi.org>, public-xg-audio@w3.org
Hi Chris!

I did? Great! I couldn't tell myself, yet! (Thanks to Kumar for helping out
with that) That must also mean that audiolib.js works as well (
https://github.com/jussi-kalliokoski/audiolib.js ), I recommend you guys and
gals check it out, I gathered most of the audio code I've done for JS in a
single library, which I guess should now be working with both the existing
audio APIs.


On Thu, Feb 3, 2011 at 9:46 PM, Chris Rogers <crogers@google.com> wrote:

> Hi Jussi, I see you got simplesynth to work - sweet!
> On Wed, Feb 2, 2011 at 9:10 AM, Jussi Kalliokoski <
> jussi.kalliokoski@gmail.com> wrote:
>> Can someone here test http://niiden.com/simplesynth/simplesynth.html if
>> it works with AudioContext enabled Chrome? I can't test myself since I have
>> no mac. I'm thinking it should, because it's designed to work with both
>> APIs.
>> As for the web workers, it would be pretty cool if Moz got it working. I
>> did an experiment few months ago, which does the processing in a worker,
>> then passes it to back to the script, but it couldn't handle realtime
>> without pops and clips (and thus the whole thing was pretty unsafe as I did
>> some bad coding, and when those were combined I'd get a buffer underflow,
>> and a serious memory leak).
>> Thanks,
>> Jussi
Received on Thursday, 3 February 2011 20:21:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:38:00 UTC