Re: Question about audio device selection

Yep.  I don't think that's incompatible, it's just a different use (hooking
up a media element to a given device, using the same enumeration of IDs.)
 That's part of the same infrastructure of "how are media elements really
working" layer on top of the device layer.

On Tue, Oct 7, 2014 at 2:45 PM, Rob Manson <robman@mob-labs.com> wrote:

> There's also this work that Ami seemed to get some traction on at the
> beginning of the year.
>
> http://lists.w3.org/Archives/Public/public-whatwg-archive/
> 2013Dec/0124.html
> https://code.google.com/p/webrtc/issues/detail?id=2243
> https://code.google.com/p/chromium/issues/detail?id=374698
>
>
> roBman
>
>
> On 8/10/14 3:15 AM, Chris Wilson wrote:
>
>> We have not yet taken on audio output device selection for Web Audio.  We
>> do have an open issue on it (https://github.com/WebAudio/
>> web-audio-api/issues/359). I expect this will take on the form of
>> something like an AudioContext constructor that takes a deviceId (from
>> MediaDeviceInfo).  (You could also use streams, doing a
>> createMediaDestination on a getUserMedia of the output stream, but that
>> would run the audiocontext at the default device's sample rate, which would
>> obviously be a Bad Thing(tm).)
>>
>> On Tue, Oct 7, 2014 at 6:42 AM, Joseph Berkovitz <joe@noteflight.com
>> <mailto:joe@noteflight.com>> wrote:
>>
>>     Hi Philippe,
>>
>>     I can’t answer for the overall W3C position (which I am still
>>     coming up to speed on myself), but right now this is not a feature
>>     that is available in the Web Audio spec. It’s on the WG's radar as
>>     something that’s important and I expect it will be explored in the
>>     upcoming face to face WG meeting later this month.
>>
>>     One idea that has been raised is to achieve this goal by some
>>     common device or stream abstraction that can shared with WebRTC (a
>>     la getUserMedia(), but for output devices). That makes sense to me.
>>
>>     Sorry I don’t have more right now; perhaps others can chime in
>>     with thoughts.
>>
>>     Best,
>>
>>     .    .       .  .  . ...Joe
>>
>>     *Joe Berkovitz*
>>     President
>>
>>     *Noteflight LLC*
>>     Boston, Mass.
>>     phone: +1 978 314 6271 <tel:%2B1%20978%20314%206271>
>>     www.noteflight.com <http://www.noteflight.com>
>>     "Your music, everywhere"
>>
>>
>>     On Oct 6, 2014, at 10:04 AM, Philippe Cohen <philc@audyx.com
>>     <mailto:philc@audyx.com>> wrote:
>>
>>      H*ello *Web Audio Developer community -
>>>
>>>     I am having hard time to understand the w3c position regarding
>>>     output audio devices selection. I was glad to see that the
>>>     Enumeration has been defined and is being implemented (at least
>>>     in Chrome) but I do not see yet any sign of defining the
>>>     selection of an audio device.
>>>
>>>     I’ve paid attention that in
>>>     https://code.google.com/p/webrtc/issues/detail?id=3606 webrtc was
>>>     opening a discussion about this very important feature few months
>>>     ago, and I feel that it can be very useful to decide when to
>>>     direct audio to headset vs. to speakers in many circumstances but
>>>     I do not see any reaction.
>>>
>>>     Could you please clarify where the specifications efforts stand
>>>     in term of device enumeration and selection ?
>>>
>>>     Thanks very much in advance -
>>>
>>>     Philippe Cohen
>>>
>>>
>>>     *Philippe Cohen** | **CTO **
>>>     *CELL +972.52.3454100 <tel:%2B972.52.3454100> | SKYPE:
>>>     philjosephcohen
>>>     Changing Audiology
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
> --
> Rob
>
> Checkout my new book "Getting started with WebRTC" - it's a 5 star hit
> on Amazon http://www.amazon.com/dp/1782166300/?tag=packtpubli-20
>
> CEO & co-founder
> http://MOB-labs.com
>
> Chair of the W3C Augmented Web Community Group
> http://www.w3.org/community/ar
>
> Invited Expert with the ISO, Khronos Group & W3C
>
>
>