Welcome to the collaborative web space for the W3C Audio WG - the group chartered to work on next-generation standards for audio processing and synthesis on the web.
Nov/Dec 2012: The group is focussing its efforts on both the Web Audio API and Web MIDI API drafts - the latter was recently published as a first public working draft and reviewed positively. Meanwhile, the Use Cases and Requirements has received some feedback after its publication, and we expect to republish it as a note soon.
As several members of the group endeavour to implement the web audio specification, many issues are being raised and fixed in Bugzilla, where most of our work takes place these days. See #Issues Tracking for details.
For a detailed breakdown of deliverables and milestones, see the W3C Audio Publications and Milestones wiki page.
How we work (and how you can contribute)
The working group operates in public, mainly through discussion on the email@example.com mailing-list.
Contributing to the work (everyone welcome)
Anyone is welcome to participate on the list by sending e-mail. Subscribing to the mailing-list (which can be done by sending a mail to firstname.lastname@example.org with subject "subscribe") is strongly recommended if you want to effectively contribute to the conversation.
Here are a few ways to contribute:
- Help us refine our Use_Cases_and_Requirements
- Review our draft specifications
- Write to us about your experience implementing the technology. What worked, what did not, how would you improve the APIs?
- Try the demos (mediastream processing, web audio API) and build more demos using the APIs - then send feedback
Joining the Working Group (W3C members only)
The core of the work on requirements, specification and testing is done by the members of the working group, which are either W3C members or "invited experts". W3C member organisations are welcome to participate in this effort by assigning representative(s) to the group. Please get in touch with the chair (Olivier Thereaux) then join the group. Working group members are meeting weekly by phone, and once to three times a year face-to-face.
A lot of our work is related to raising, tracking and solving issues on our draft specifications.
As of June 2012, we are using W3C Bugzilla as our issues tracker. Our issues list is currently as follows:
|MIDI API||New or Unconfirmed||Assigned or Reopened||Resolved||Verified or Closed||All|
|Web Audio API||New or Unconfirmed||Assigned or Reopened||Resolved||Verified or Closed||All|
|Use Cases and Requirements||New or Unconfirmed||Assigned or Reopened||Resolved||Verified or Closed||All|
|All specs||New or Unconfirmed||Assigned or Reopened||Resolved||Verified or Closed||All|
If you wish to catch up with recent activity, the view of issues changed in the past week or in the past month can be useful. Or you may want the short-and-sweet list of issues recently resolved by the editors, complete with links to changesets in the specs.
The group held its latest face-to-face meeting on January 23rd and 24th 2012 at the Google offices in Venice Beach, California.
The group will NOT be meeting at the upcoming TPAC in Lyon. Another face-to-face meeting, possibly in January-February 2013 on the American continent, is being discussed.
The group was on hiatus for most of summer 2012, and is restarting its calls. We have calls on Wednesdays at Noon Boston time approximately every 2 weeks. An iCal calendar is published for group members' convenience. Next call Wednesday 17th October 16:00-17:00 UTC.
- Conference code: 28346 ("AUDIO")
- Bridge US: +1-617-761-6200 (Zakim)
- Europe: +33.4.89.06.34.99, +44.117.370.6152
… or use a SIP Client to connect to the bridge.
Please remember to log in to the Audio IRC channel prior to the meeting.
- Server: irc.w3.org
- Port: 6665
- Channel: #audio
Summaries, Meeting Minutes and Resolutions
- 17 October 2012: http://lists.w3.org/Archives/Public/public-audio/2012OctDec/0174.html
- Publishing FPWD of MIDI spec
- Channel handling (and layouts) in web audio API
- Re-joining the Audio WG
- Agreement to publish Web MIDI API First Public Working Draft
- Adding a (readonly) attribute for channel layout in webaudio destination nodes
- 26 September 2012: http://lists.w3.org/Archives/Public/public-audio/2012JulSep/0843.html
- TPAC update / next face-to-face meeting
- Quick update on recent changes to the specs / early implementations
- Graph introspection / determine connection state of an AudioNode
- DAP / HTML Media Capture
- Face-to-face meeting is cancelled, the group is exploring possibility of a f2f in January in North America
- We decided to not look into an interface to determine the connection state of an AudioNode yet. Postponed for a later phase of work.
- We agreed that The HTML Media Capture specification should define its relationship with GetUserMedia(), and that it should follow the same naming/approach to access to video/microphone as getUserMedia()
- 12 September 2012: http://lists.w3.org/Archives/Public/public-audio/2012JulSep/0768.html
- Interface naming (update)
- Revisiting the circular graph issue
- Use Cases and Requirements review
- Loop start/stop points
- Logistics / TPAC
- noteGrainOn replaced by an overloaded start() method
- Two suggestions for feedback loops: one to specify the minimum as a block of 128 samples (which would make things sound differently on platforms with different sample sizes, but that was deemed acceptable in the same way as graphics look different on platforms with different frame rates and power). The other was to not specify it and let implementations choose their minimum delay.
- Publish the Use Cases document once we incorporate initial feedback
- We decided on a good way to handle loop start/stop points see bugzilla: https://www.w3.org/Bugs/Public/show_bug.cgi?id=17390
- 22 August 2012: http://lists.w3.org/Archives/Public/public-audio/2012JulSep/0632.html
- Renaming interfaces
- Remaming noteOn/noteOff to start/stop or play/stop
- Renaming setTargetValueAtTime (and other AudioParam methods)
- Teleconference schedule
- noteOn/noteOff renamed to start/stop, the old name will be mentioned in informational section in the spec
- Setting audioparam value while there is an automation curve will cancel that automation curve and set value immediately
- setTargetValueAtTime becomes setTargetAtTime
- We need a method to get a readonly reading of the combined value when using audioparam automation curve
- 1-15 August 2012: http://lists.w3.org/Archives/Public/public-audio/2012JulSep/0604.html
- Issues discussed
- sync/delay issue with custom nodes
- revisiting the native vs custom nodes discussion
- Issues discussed
- 15-31 July 2012: http://lists.w3.org/Archives/Public/public-audio/2012JulSep/0409.html
- 1-14 July 2012: http://lists.w3.org/Archives/Public/public-audio/2012JulSep/0179.html
- Issues discussed
- Issues closed and Resolutions
- 12-30 June 2012: http://lists.w3.org/Archives/Public/public-audio/2012JulSep/0175.html
- Doug started an interesting and important thread on testing.
- Issues discussed
- Issues closed and Resolutions
- 13 June 2012: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0749.html
- Testing approach, existing tests and test roles in the group
- Short rechartering update
- 30 May 2012: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0455.html
- Overview of Opera issues - http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0360.html
- ISSUE-24 CircularRouting
- It is OK to have a circular graph so long as there is a delay. The minimum delay should be 128 samples
- 23 May 2012: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0412.html
- Clarifying the issues process
- Charter, MIDI draft
- Usage/Reference to OpenAL
- Frequency of teleconferences
- 9 May 2012: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0144.html
- Spec Roadmap
- The group will publish the mediastream processing API as a note
- Our new charter will document the focus on the web audio API as our audio processing spec
- The group will publish the use cases & requirements as a WD, with a view to publish as a note
- Features left out of scope for the v1 of web audio API will be documented in the UC&R Note
- 2 May 2012: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0100.html
- new members
- ISSUE-12: Loop start/stop points
- ISSUE-6: Audio Param Constructor
- ISSUE-9: Channel handling
- ISSUE-5: Pausing a sub-graph
- Spec Roadmap
- Resolution: Close ISSUE-6, start keeping a "backlog" of features we are keeping out of the v1 spec
- 25 Apr 2012: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0073.html
- Review of web audio API ED changes
- Channel handling (ISSUE-9)
- Gain negative or above 1 (ISSUE-10)
- Offline audio context (ISSUE-11)
- midi and charter
- Resolution: Close ISSUE-10, as recent changes to the ED of web audio API satisfy the group's requirements
- 16 Apr 2012: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0060.html
- Decide on the time/day for our teleconferences through Autumn 2012
- Decide on whether we will meet at TPAC and/or for another f2f
- Quick review of issues "Pending Review" (ISSUE-3, ISSUE-5, ISSUE-7)
- review of recent editor's draft changes
- Resolution: we will say yes to meeting at TPAC, assess later whether we need/want to hold another f2f, possibly in East Coast USA
- Resolution: close ISSUE-3 as satisfying as is, make sure we document limits in the number of contexts - not necessarily in the spec but in some developer doc
- 2 Apr 2012: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0010.html
- ISSUE-8: numberOfOutputs of RealtimeAnalyserNode
- ISSUE-6: AudioParam constructor
- Resolution: make the output for the realtimeanalysernode optional
- Resolution: add a constructor parameter for audio context to specify sample rate - make sure to specify that default is best unless needed
- Tentative Resolution: keep AudioParam constructor for a future version of the spec
- 26 Mar 2012: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0506.html
- ISSUE-5: Pausing a sub-graph
- ISSUE-7: Power of Two FFTs for RealtimeAnalyserNode
- Resolution: an arbitrary size FFT is not needed for version 1
- 19 Mar 2012: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0424.html
- Proposed use case: metronome
- Followup on UC-15, Video with multiple audio tracks
- New WD of Web Audio API published
- Discuss/document Issue: Pausing a subgraph
- face-to-face meetings
- 12 Mar 2012: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0358.html
- Preparing new WD publication for Web Audio API
- Resolution: we will republish the Web Audio API spec a few days after the last batch of edits are done, and will republish the other docs at a later point, when the group feels they are ready
- 05 Mar 2012: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0341.html
- Welcome Matt Paradis,
- MIDI work starting,
- publishing new WD of web audio API,
- syncing video and audio,
- destroying AudioContext instances
- Resolution: That the group will publish a new working draft of the Web Audio APi
- 27 Feb 2012: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0301.html
- rechartering to look at MIDI,
- how we split our work;
- Spec differences document and how we gather feedback.
- Resolution: the group will draft a new charter including MIDI work, we already have a couple of prospective editors
- 20 Feb 2012: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0282.html
- Use Case priorities,
- reviews of recent changes in Web Audio spec,
- spec differences document
- 13 Feb 2012: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0244.html
- New teleconference schedule (now to be two hours earlier than before)
- Prioritizing the use cases : Use Cases 1,2 and 7 were deemed the highest priority, with UC6 also a center of interest.
- Resolution: meetings will be 7pm GMT mondays from now on
- Resolution: to see how large the overlap of requirements between UC 1,2 and 7 is - and split based them in simple/advanced if needed
- 06 Feb 2012: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0164.html
- Intro to Use Case Priorities,
- rechartering for MIDI APIs,
- differences between APIs document
- 23 and 24 Jan 2012: http://www.w3.org/2011/audio/wiki/F2F_Jan_2012
- Major overhaul of the Use Cases and Requirements document
- 16 Jan 2012: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0034.html
- use cases
- 09 Jan 2012: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0009.html
- use cases
- 19 Dec 2011: http://www.w3.org/2011/12/19-audio-minutes
- We've published our FPWDs! Now what?
- Use cases and Requirements
- Next call
- 12 Dec 2011: http://www.w3.org/2011/12/12-audio-minutes
- publication of FPWD and names
- f2f logistics
- explaining the work on use cases and requirements
- Resolution: The three documents will be Audio Processing API for the umbrella, and Web Audio API / Media Streaming API for the two proposals respectively.
- 05 Dec 2011: http://www.w3.org/2011/12/05-audio-minutes
- Olivier's intro
- F2F proposal
- decision on publishing "model"
- use cases and requirements document
- coordination with WebRTC
- 01 Nov 2011: http://www.w3.org/2011/11/01-webrtc-minutes.html#item05 minutes of joint meeting with WebRTC
- Status of Audio WG
- 31 Oct 2011: http://www.w3.org/2011/10/31-audio-minutes (TPAC)
- Where we are and how we got there.
- media capture API
- live-editing of use cases document
- Resolution: no objection to moving to FPWD. There will be an e-mail call for objections to this publication
- 18 Oct 2011: http://www.w3.org/2011/10/18-audio-minutes
- API Proposals, use cases
- 20 Jun 2011: http://lists.w3.org/Archives/Public/public-audio/2011AprJun/0154.html
- F2F Meeting during TPAC2011
- RTC methods for scheduling high numbers of consecutive/overlapping sounds
- Roadmap - Should the Audio WG group take on the larger domain of general temporal media graphs?
- DAW use-cases and the Web Audio spec
- 06 Jun 2011: http://www.w3.org/2011/06/06-audio-minutes
- Status of Linux Web Audio API bug
- Adding links for "Specs in discussion" to W3C Group Page
- Reconsiliation of Web Audio & Media Streaming architecture
- "Connect" Naming
- 16 May 2011: http://www.w3.org/2011/05/16-audio-minutes
- Possible bug in Web Audio with noteOn()
- Page reload issues in Chrome build.
- 02 May 2011: http://www.w3.org/2011/05/02-audio-minutes
- Resolution: remove buffer size from js audio node constructor
We track action items and issues on our Issue Tracker
We also track bugs in Bugzilla.