Bug 33938 - Audio Data API
Summary: Audio Data API
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P5 Enhancement
Assignee: Nobody
Depends on:
Blocks: html5test
  Show dependency treegraph
Reported: 2010-01-20 20:46 PST by Matt Bierner
Modified: 2012-05-22 10:27 PDT (History)
8 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Matt Bierner 2010-01-20 20:46:33 PST
Currently, browsers rely on Flash to analyze, modify, and even create audio data online. Given that rich media seems to be of ever increasing importance, I feel that a set of methods to access audio data would be extremely useful. Creating and modifying audio would also be a nice feature but my primary concern is just audio access.

These concepts were originally suggested under an 'Audio Canvas' concept by Dave Singer in this list: http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2008-July/015334.html

More recently, some of these features have been discussed and added experimentally over at Mozilla, which also served as the inspiration for this request: https://bugzilla.mozilla.org/show_bug.cgi?id=490705
Comment 1 Bertrand Presles 2010-05-08 01:10:45 PDT
Mozilla has issued a Draft specifications on their Audio Data API work:
Comment 2 Eric Carlson 2010-07-18 08:46:40 PDT
W3C has an Incubator Group working on web audio processing: http://www.w3.org/2005/Incubator/audio. The group is considering a proposal from Chris Rogers at Google for a node-based JavaScript procession and synthesis API: http://chromium.googlecode.com/svn/trunk/samples/audio/specification/specification.html
Comment 3 Peter Beverloo 2012-05-22 09:06:04 PDT
Chris, should we close this now that (a) the Media Processing API would supersede this, and (b) the working group has adopted the Web Audio API?