The mission of the Audio Working Group, part ofthe Rich Web Client Activity, is to define a client-sidescript API adding more advanced audio capabilitiesthan are currently offered by audio elements. TheAPI will support the features required by advancedinteractive applications including the ability toprocess and synthesize audio streams directly inscript.The HTML5 specification introduces the <audio>and <video> media elements, including an API toplay back prerecorded audio and video files and toget limited information about the media, such asduration. The Audio Working Group will build uponand expand that basic functionality.
2010 2011 2012 W3C Audio W3C Audio Incubator Group Working Group 12 May 2010 ~ 28 March 2012 25 March 2011 ~ http://www.w3.org/2005/Incubator/audio http://www.w3.org/2011/audio firstname.lastname@example.org ( Chromium ) W3C MIDI Device Web Audio API Web Audio API Communication API 1 June 2010 ~ 18 July 2011 18 July 2011 ~ MediaStream Mozilla Processing API http://chromium.googlecode.com/svn/ Audio Data API trunk/samples/audio/index.html http://www.w3.org/TR/webaudio 14 May 2010 ~ Mozilla Google https://wiki.mozilla.org/Audio_Data_API Firefox 4 Chrome 14 22 March 2011 16 September 2011@humphd 2010-08-26 nightly builds 2011-01-31 nightly builds email@example.com firstname.lastname@example.org May 2010 ~ December 2011 March 2011 ~ http://lists.w3.org/Archives/Public/public-xg-audio http://lists.w3.org/Archives/Public/public-audio
UC 1 Video ChatUC 2 HTML5 game with audio effects, musicUC 3 Online music production toolUC 4 Online radio broadcastUC 5 writing music on the webUC 6 wavetable synthesis of a virtual music instrumentUC 7 Audio / Music VisualizationUC 8 UI/DOM SoundsUC 9 Language learningUC10 Podcast on a flightUC11 DJ music at 125 BPMUC12 Soundtrack and sound effects in a video editing toolUC13 Web-based guitar practice serviceUC14 User Control of AudioUC15 Video commentary
MIDI Device Communication APIThe MIDI API specification defines ameans for web developers to enumerate,manipulate and access MIDI devices.Having an API for MIDI gives a means tomake various applications using existingsoftware and hardware synths, as well aslight systems and other mechanicalapparatus controlled by MIDI, along witha method of communication with existingDAW (Digital Audio Workstation), trackersand other music software on the userscomputer. https://dvcs.w3.org/hg/audio/raw-file/tip/midi/specification.html
The mission of the Web Real-Time CommunicationsWorking Group, part of the Ubiquitous WebApplications Activity, is to define client-side APIs toenable Real-Time Communications in Webbrowsers.These APIs should enable buildingapplications that can be run inside a browser,requiring no extra downloads or plugins, that allowcommunication between parties using audio, videoand supplementary real-time communication,without having to use intervening servers (unlessneeded for firewall traversal, or for providingintermediary services).
DemosHere are a couple of demo sites. Most of them were sent to us via thediscuss-webrtc list. Please remember that the same disclaimer as aboveapplies:Justin Uberti (Chrome-webrtc team member) has sent in a App Engine based1:1 video calling app.http://apprtc.appspot.com/ sourcecode: http://code.google.com/p/webrtc-samples/source/browse/trunk/apprtc/Justin Uberti (Chrome-webrtc team member) has sent in a App Engine basedface detection apphttp://apprtc.appspot.com/html/face.htmlPaul Neave sent in a great video effectsapp. http://neave.com/webcam/html5/Greg Miernicki was officially the first to send in ademo: http://miernicki.com/cam.htmlEric Bidelman sent in an additional photo effects demos: http://html5-demos.appspot.com/static/getusermedia/photobooth.htmlAnd another lets have fun with WebGL sent in by JéromeÉtienne: http://webglmeeting.appspot.comAn HTML5 SIP client http://www.sipml5.org/call.htmIf you find another demo app, please send it to email@example.com /the discuss list or our Google+ Page. We will try to put it up!