New issue
Advanced search Search tips

Issue 651227 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

When two separate Blackmagic capture devices are connected, only one is selectable by getUserMedia

Reported by je...@culturehub.org, Sep 28 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Steps to reproduce the problem:
1. Aquire two Blackmagic capture devices, such as two Mini Recorders, and two cameras and connect devices to separate Thunderbolt ports
2. Open Chrome and go to https://webrtc.github.io/samples/src/content/getusermedia/gum/
3. Select either device from the Camera menu found in the URL line; they are distinguished by a parenthesized number, (1) and (2)
4. Reload the page

What is the expected behavior?
The selected device should have it's video feed displayed in the video element

What went wrong?
Only the feed for device (1) is displayed, even when device (2) is selected

Did this work before? No 

Chrome version: 53.0.2785.116  Channel: stable
OS Version: OS X 10.10.3
Flash Version: Shockwave Flash 23.0 r0

The devices can be displayed simultaneously in other applications. I've used two Blackmagic capture devices simultaneously with MAX/MSP/Jitter and similar tools. This suggests the feeds are distinguishable, and indeed they are distinguished by a parenthesized number in the Camera menu. Specs for relevant devices can be found here: https://www.blackmagicdesign.com/products/ultrastudiothunderbolt
 
Components: Blink>WebRTC
Cc: jansson@chromium.org
jansson can you have a look since you've done some work with Blackmagic devices?

Comment 3 by mcasas@chromium.org, Oct 11 2016

Components: -Blink>WebRTC Blink>GetUserMedia>Webcam
Better component: Blink>GetUserMedia, since
Blink>WebRTC pertain to remote-peer connections.

Comment 4 by mcasas@chromium.org, Oct 17 2016

Labels: Needs-Feedback
Owner: jansson@chromium.org
Status: Assigned (was: Unconfirmed)
jansson@, I parsed the code and we should support >1 
Blackmagic device. Can we repro in any way?
Owner: jkallar@chromium.org
jkallar@ could you take a look?
I’m awaiting a second camera to re-produce this bug.

However, I found the issue when same model Blackmagic devices are both used then you can only choose the device parenthesized number (1). See below for steps:


1. Use two identical model Blackmagic capture devices, eg ‘Ultra Studio Express’ in this case and connect devices to separate Thunderbolt ports
2. Open Chrome and go to https://webrtc.github.io/samples/src/content/devices/input-output/
3. For ‘Video source’ select the device distinguished by a parenthesized number (2). For example “Ultra Studio Express (2) - 720p59.24”

What is the expected behavior?
Video source shows “Ultra Studio Express (2) - 720p59.24”

What went wrong?
Video source shows “Ultra Studio Express (1) - 720p59.24”

Chrome version: Version 54.0.2840.71 (64-bit)  Channel: stable
OS Version: OS X 10.11.6 (15G1108)
Adobe Flash Player - Version: 23.0.0.205
Shockwave Flash 23.0 r0

Owner: mcasas@chromium.org
mcasas@ could you take a look? When two blackmagic devices are connected, only the first one is usable (i.e. if you select device 2 it selects device 1 regardless). Seems to be some exclusive access to the SDK or something.
Cc: mcasas@chromium.org
Labels: -Pri-2 Pri-3
Owner: jansson@chromium.org
Status: Untriaged (was: Assigned)
I have no way to replicate this bug, so back to you
for retriage.

Lowering prio in the light of the #users affected by
this issue.
Cc: -jansson@chromium.org
Labels: -Needs-Feedback
Owner: ----
Status: Available (was: Untriaged)
Changing available and removing myself as owner, this is owned by the component owners team.
Project Member

Comment 10 by sheriffbot@chromium.org, Nov 8 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)

Sign in to add a comment