[mediacapture-output] Predefined IDs conflict with future direction of device selection

joeberkovitz has just created a new issue for 
https://github.com/w3c/mediacapture-output:

== Predefined IDs conflict with future direction of device selection 
==
I am concerned that the use of predefined IDs with somewhat vague 
meanings (see 
https://cdn.rawgit.com/w3c/mediacapture-output/master/index.html#mediadeviceid-enum)
 sets up a recipe for confusion that will not be easy to get rid of in
 the future. While these appear to map to some existing MS Windows 
concepts, that does not provide applications with the ability to offer
 a meaningful choice of output device to end users (imagine offering 
users the choice of "playback" or "communications" in a music 
synthesizer app, for example). I suggest that these IDs be omitted 
from the spec altogether at this stage.

My belief is that most developers need to be able to discover devices 
that satisfy various context-dependent constraints, e.g. "is a 
headphone", "is a speaker", "can support 44K sample rate", "can 
support a 5.1 channel layout". I am aware that this work is being 
deferred to a later phase of enhancing `enumerateDevices()`, and so 
on. But I think that's the best place to focus effort on selecting 
devices, rather than on a stopgap distinction between playback and 
communications.


Please view or discuss this issue at 
https://github.com/w3c/mediacapture-output/issues/51 using your GitHub
 account

Received on Wednesday, 26 October 2016 17:02:37 UTC