Closed ghost closed 12 years ago
Hello there. I am well aware of the WebAudio API as I have used it quite a lot in the recent past. However, it does not fit into the HTML5 Audio specification we are testing here. It is a totally different specification and technology. If this makes sense to you, please close the issue. Otherwise I'd be glad to hear your arguments.
It's very relevant to any web app that wants to apply effects in real time to the audio stream. It also can generate real time audio, so web apps will make much use of it, as you feed in the HTML5 audio into the Web Audio API. I'll close this bug, as this API extends past the "basic" HTML5 audio api.
There still should be a test suite, even if separate. Should we start a new github repo for that?
@grantgalitz I am not so up to date with the Chrome implementation of the WebAudio API. Are there so many bugs and inconsistencies that justify a third party test suite?
There are minor issues, but mostly it would be for when other browsers implement it.
Would help keep in line all the browsers that are starting to adopt this API as it takes off. It's been enabled by default in Google Chrome for a couple of versions already, and is coming to Safari very soon (Desktop AND mobile (iOS 6 beta supposedly supports it)). Some Firefox devs want to implement it too.
https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html http://chromium.googlecode.com/svn/trunk/samples/audio/index.html