Re: [chromium-html5] Android Chrome Beta 25.0.1364.108

[Peter Beverloo]

The Web Audio API is not yet available in Chrome for Android.  You can star the following issue if you'd like to be informed about updates:

https://code.google.com/p/chromium/issues/detail?id=166003

Peter

On Tue, Feb 26, 2013 at 2:16 PM, Tom Ardern <toma...@gmail.com> wrote:

Hi,

I've been recently wanting to use the Web Audio API in Android Chome Beta 25.0.1364.108. 

On the ChromeStatus site (http://www.chromium.org/developers/web-platform-status). It mentions the following:

Web Audio API
Availability: dev channel since m12. stable channel in m14. m24 adds the ability for live mic input (enable in about:flags). m25 updated API calls to the latest spec.
Spec: W3C Audio Incubator Group Proposal
Notes: enable via about:flags. Also, Mozilla has an alternative Audio Data API proposal. M20 included
support for oscillator nodes.
Demo: spec samples
Dev Contact: Chris Rogers (crogers)

As I am using M25, I would presume the following would work:

try {

context = new webkitAudioContext();

try {

osc = context.createOscillator();

}

catch(e) {

alert('Oscillator is not supported in this browser');

}

}
catch(e) {

alert('Web Audio API is not supported in this browser');

}

However, both errors are being catched as the webKitAudioContext() is undefined.

Is the documentation wrong? Am I doing something incorrect (The above works fine in Chrome Desktop)? Is there a roadmap/milestone when the Web Audio API will be enabled for android?

Thanks for your help,

Regards,

Tom

--
You received this message because you are subscribed to the Google Groups "Chromium HTML5" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-html...@chromium.org.
To post to this group, send email to chromiu...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-html5/?hl=en.
For more options, visit https://groups.google.com/a/chromium.org/groups/opt_out.
 
 

[PhistucK]

I corrected the information on chromestatus.com. Sorry.

☆PhistucK