33938 2010-01-20 20:46:33 -0800 Audio Data API 2012-05-22 10:27:19 -0700 1 1 1 Unclassified WebKit Media 528+ (Nightly build) All All RESOLVED INVALID P5 Enhancement --- 40829 0 contact webkit-unassigned bpresles bugs crogers eoconnor eric.carlson eric mjs peter oldest_to_newest 183064 0 contact 2010-01-20 20:46:33 -0800 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 222854 1 bpresles 2010-05-08 01:10:45 -0700 Mozilla has issued a Draft specifications on their Audio Data API work: https://wiki.mozilla.org/Audio_Data_API 252959 2 eric.carlson 2010-07-18 08:46:40 -0700 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 630421 3 peter 2012-05-22 09:06:04 -0700 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?