The Web Audio Developers Community Group brings together hackers and developers interested in using the emerging Web Audio API. By providing community support on using the API and surfacing issues with the draft standard, it complements the work of the W3C Audio Working Group where the specification is being developed.
This group will not create specifications.
Group's public email, repo and wiki activity over time
Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
Working on a Audiology related application, I need to have the ability from our web application to select when to output sounds to a device connected to speakers or to a device connected to headset.
This feature seems to be useful for music apps where a DJ may want to control both headset and speakers, or where someone has multiple speakers set in multiple rooms, connected to different audio devices (sound cards).
This feature can also help in educational apps where a teacher can control what to output to a single student headset and to the whole classroom speakers.
I did not found any trace of discussion around use cases requiring output device selection. Did I missed them?
Welcome to the Web Audio Developers Community Group. This community is an extension of the W3C Audio Working Group aiming to provide developers with a space where we can exchange, learn and help each others.
This group will not be working on standard specifications – instead, whenever possible we will try and gather our input and give it to the Working Group, where specifications such as the Web Audio API and Web MIDI API will continue to be developed.
We expect that a lot of the activity of the community group will happen on the mailing-list (public-audio-dev@w3.org), to which you will automatically be subscribed upon joining the group.
Usual (n)etiquette rules apply in this group. In particular, you want to make sure to search the Mailing-list archives for answer before asking a question – thus saving everyone time and energy.
