Re: new device APIs?

Hi Dom, all,

I am not sure if API you mentioned would fit well for use case I mentioned.

It seems to be rather hard to determine headphones from the list of media devices. You should check all “audiooutput” devices, determine which one of them represent headphones somehow.. it is not very clear. Also I bet on many systems there would be one device, something like “Generic Sound Output” with different connectors (like on my Linux machine), which won’t be notified or changed at all when user plugs or unplugs headphones.

But using MediaDevices API for this purpose sounds reasonable. It would be much easier for developer if there would be high-level objects like headphones (representing any connected headphones - wired, bluetooth headset, etc.), microphone (any sound recording device), speakers and ways to observe their statuses - plugged, unplugged, unknown, etc.

Regards,
Ilya

On 07 июля 2014 г., at 19:28, Dominique Hazael-Massieux <dom@w3.org> wrote:

> Le lundi 07 juillet 2014 à 11:25 -0400, Marcos a écrit :
>> On July 7, 2014 at 9:13:40 AM, Dominique Hazael-Massieux (dom@w3.org) wrote:
>>>> This is supposed to be already covered by the navigator.mediaDevices  
>>> interface, described in
>>> http://dev.w3.org/2011/webrtc/editor/getusermedia.html#enumerating-devices  
>>> (as audioouput devices), with the devicechange event triggered  
>>> on
>>> availability of new devices.
>> 
>> Do you know if anyone supports this? I can't seem to find the attribute on either Chrome or Gecko. 
> 
> This is a fairly recent addition to the spec, and I don't think anyone
> has implemented it yet.
> 
> Dom
>

Received on Tuesday, 8 July 2014 15:25:18 UTC