[Bug 22101] New: facingMode is too restrictive to select specific camera (or microphone)

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22101

            Bug ID: 22101
           Summary: facingMode is too restrictive to select specific
                    camera (or microphone)
    Classification: Unclassified
           Product: WebRTC Working Group
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Capture and Streams
          Assignee: public-media-capture@w3.org
          Reporter: silviapfeiffer1@gmail.com
                CC: public-media-capture@w3.org

I have an application where I need three cameras as input. It is not a phone,
but a desktop with multiple cameras. I have three video elements into which I
add the video streams with gUM.

I would like it to be deterministic which camera is projected into which video
element. Right now in Chrome I have to manually select the camera from the list
of exposed cameras in settings (or the camera icon once the first camera is
connected) to choose which camera the next video element will contain.

The current spec proposes to introduce a "facingMode" enum to pick between
cameras. Unfortunately, that is of limited use to only mobile cameras. It won't
help in my case. I would prefer if the means to pick cameras was based on a
more generic means of identifying cameras.

Here's my proposal:
In the Chrome settings list, the cameras are identified by their name. I can
imagine having a "cameraName" enum in the constraints. If there are multiple
cameras with the same name, a number (such as "HD Pro Webcam C920 #1") should
be added (that's how VLC does it). Similarly, one could think of a
"microphoneName" constraint.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Received on Tuesday, 21 May 2013 01:16:31 UTC