Eyes Above The Waves

Robert O'Callahan. Christian. Repatriate Kiwi. Hacker.

Sunday 16 September 2012

Web Audio In Firefox

Let me clear up any confusion about what our plans are for audio APIs in Firefox.

Some MediaStream support has landed in Firefox 17. We have the ability to create MediaStreams containing the output of media elements and use them as a source for other media elements. I need to make some changes to those APIs based on feedback we start evangelizing them for real. We can also create MediaStreams via getUserMedia (when that feature is preffed on in about:config).

The work on MediaStreams Processing that I did as an alternative to the Web Audio API is on the back-burner. Our priority is to implement Web Audio. Our plan is to implement AudioNodes using the same infrastructure as MediaStreams under the hood --- to reduce code duplication and to ensure that Web Audio/MediaStreams integration is perfect. Some core infrastructure for MediaStreams that are produced by processing inputs to outputs --- ProcessedMediaStreams --- already landed, to support the features above. Currently Ehsan is working on the IDL/DOM API side and I have some more work to do on the MediaStreams infrastructure side. We don't have a specific date set for Web Audio support, but it is a high priority.

At some point we will revisit MediaStreams Processing to get the features that Web Audio is missing, e.g., seamless stitching together of an audio and video playlist from a series of clips. That is lower priority.


my major issue with ff webaudio is just like the h264 one. many websites stream patent-encumbered audio ONLY, and I gotta load chrome for that. example: http://html5.grooveshark.com
Manoj Mehta
Rob, Please don't allow FF to take the idealistic stance on Web audio only to backtrack as you had to with Web video. Firefox is a mainstream browser, and people use their browsers more and more to consume media - view video and listen to audio. Please create a browser that supports as many codecs and formats as possible. This becomes particularly important in the B2G context; if B2G users are to listen to grooveshark on their mobile, their browser has to support whatever format the audio is encoded in. Users will *not* stop using the websites; they will stop using Firefox and switch to Chrome or Safari. Everyone I know would much rather their browser stream a patent-encumbered file than have to use Flash to load that *exact*, same file. The Flash workaround defeats the philosophical position on patents. Manoj P.S. I cannot post comments to your blog with the latest x64 Nightly on Windows.
The Web Audio spec has nothing to do with codecs.
Manoj Mehta
Let me ask the question that matters most to me as a Firefox user. Will grooveshark's HTML5 page work in Firefox on Android, on my Mac, and my Windows PC? It does not today.
Ask Grooveshark why they don’t support Firefox or Opera.
That means that Web Audio is becoming *the* HTML5 audio API, right? How does all of this relate to the Audio Data API?
The Audio Data API is obsolete and should not be used. Some of its features, in particular the ability to play sample buffers on the main thread, might be retained as an extension to the Web Audio API.
Ah, great to see a single standard emerge!
Thank you for all your support provided at the Mozilla's Bugzilla site. I appreciate all your efforts to improve Firefox!
Could you give us a rough estimate of when we might expect basic web audio support in FF?