Re: Web Audio API is now available in Chrome

Yes Olli, this is a good point. More information and examples on the Audio
Data API (the cross-platform Firefox4 audio implementation) can be found
here: https://wiki.mozilla.org/Audio_Data_API

<https://wiki.mozilla.org/Audio_Data_API>In case this is not clear to
anybody, the Audio Group are currently in Incubation mode at the W3C, and
all the specs to this point are, by nature: "suggestions". I am excited that
we have browser developers so far ahead in implementing their ideas already,
this puts us in a great strategic position for the future, as we can already
begin to identify what works, how people will use the API, and so on.

I am looking forward to seeing the Webkit API land cross-platform, as it
will allow for greater community based research/feedback that can be
utilized in the coming Audio Working Group / official Audio Spec. of the
future.

I would be particularly interested to talk to those in the wider proximity
of the group, who would be interested in working with both existing vendor
implementations/specs to write reviews/guides or simply collect their
thoughts on the work thus far. If that sounds like you, please get in touch.

-- Al


On Tue, Feb 1, 2011 at 11:17 AM, Olli Pettay <Olli.Pettay@helsinki.fi>wrote:

> On 02/01/2011 02:03 AM, Chris Rogers wrote:
>
>> Hi Everybody,
>>
>> I'd like to announce that Google Chrome now supports the Web Audio API.
>>
>
> I could remind that the other web audio API is available
> in Firefox 4 ;)
>
>
>
>
> -Olli
>
>
>
>   For now, it needs to be enabled in "about:flags" and runs on Mac OS X
>> (Windows and Linux are nearly ready!).  I've updated the demo page with
>> a link to the binary:
>>
>> http://chromium.googlecode.com/svn/trunk/samples/audio/index.html
>>
>> In addition to the downloadable binary I've provided, the code has made
>> its way into the Chrome 10 release branch, and will be available in the
>> Chrome developer channel (updated weekly).
>>
>> As a side note, the Apple Safari binary is built from the same audio
>> engine code in WebKit.  Not surprisingly, the experience in both the
>> browsers is very similar when using the audio API.  But I'm interested
>> in any browser-specific bugs which people find.
>>
>> Here are some of the next things I plan to do:
>> * Work on the final Windows and Linux porting work for Google Chrome
>> * Take a vacation!
>> * Develop comprehensive layout tests for the Web Audio API in WebKit.
>>  This will result in a more stable and robust implementation, and can
>> help the standardization process move further along.
>>
>> Cheers,
>> Chris
>>
>>
>
>