Intent to Implement: Audio Output Devices API

178 views
Skip to first unread message

Guido Urdaneta

unread,
Apr 7, 2015, 7:15:08 AM4/7/15
to blink-dev, Tomas Gunnarsson
gui...@chromium.org,to...@chromium.org http://w3c.github.io/mediacapture-output  
This feature will incorporate a set of JavaScript APIs that let a Web application direct the audio output of a media element to authorized devices other than the system or user agent default.

A significant number of Web developers have expressed interest in being able to  programmatically direct audio to nondefault audio output devices when multiple such devices exist. Currently, this functionality is not available, which makes it impossible to develop certain types of applications. Some examples are multilingual applications that output different languages to different devices, or music applications that output one song to a loudspeaker and a different one to a headset (see [1,2,3,4,5] for more examples).

Firefox: No public signals Internet Explorer: No public signals Safari: No public signals Web developers: Positive

We do not anticipate any compatibility risks. This feature is to be implemented behind a runtime flag.
None. Yes.
None yet.
https://crbug.com/438023 was originally set up to track the implementation of this feature. https://www.chromestatus.com/features/4621603249848320
No.

Chris Wilson

unread,
Apr 7, 2015, 1:38:12 PM4/7/15
to Guido Urdaneta, Hongchan Choi, Raymond Toy, Jan Linden, blink-dev, Tomas Gunnarsson
I'd really like to see more participation and review from the Web Audio team on this.  I think implementation experience is good, but there are a lot of unanswered questions on the interaction with web audio (and in extensible-web style, we should be thinking about how the high-level "play this media to this output device" is mapped to low-level features).  Not only is the web audio link not discussed with the WG, there are significant issues around symmetry with getUserMedia (knowing it's the same audio clock for both devices is important), multichannel support isn't clear, ...

I don't think this needs to block any progress here, but I think it will need to be a clear partnership and picture between Web Audio and this feature prior to shipping.

(+Hongchan, Raymond and Jan for Web Audio)

Philip Jägenstedt

unread,
Apr 17, 2015, 8:31:04 AM4/17/15
to Chris Wilson, Guido Urdaneta, Hongchan Choi, Raymond Toy, Jan Linden, blink-dev, Tomas Gunnarsson
Has there been any progress on this issue? Is implementation proceeding?

The spec is pretty small, and only the bit about HTMLMediaElements looks ready to implement:

Is the plan to implement only that, or what about Web Audio?

One mildly odd thing is the mix of the terms input/output and source/sink in the specs. The MediaDeviceKind enum uses the terminology input/output, but the HTMLMediaElement extensions calls it a sink. I doubt this will really confuse anyone, but is there a reason to not use the input/output terminology everywhere?

Philip

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

gui...@google.com

unread,
May 25, 2015, 8:07:35 AM5/25/15
to blin...@chromium.org, hong...@google.com, to...@chromium.org, jtli...@google.com, rt...@google.com, gui...@chromium.org, cwi...@google.com


On Friday, April 17, 2015 at 2:31:04 PM UTC+2, Philip Jägenstedt wrote:
Has there been any progress on this issue? Is implementation proceeding?


Implementation is proceeding.
 
The spec is pretty small, and only the bit about HTMLMediaElements looks ready to implement:

Is the plan to implement only that, or what about Web Audio?


The current plan is to implement the HTMLMediaElements part.

Yehonathan Sharvit

unread,
Oct 25, 2015, 1:44:19 AM10/25/15
to blink-dev, hong...@google.com, to...@chromium.org, jtli...@google.com, rt...@google.com, gui...@chromium.org, cwi...@google.com, gui...@google.com
When will the WebAudio part be implemented?
Reply all
Reply to author
Forward
0 new messages