New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 818195 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

getUserMedia fails when using 4k camera [Device Specific]

Project Member Reported by vasanthakumar@chromium.org, Mar 2 2018

Issue description

Chrome Version: 64.0.3282.186 [Stable Live]
OS: Windows 7 [Model: Lenovo Thinkpad X1 Carbon]

Device configuration: Windows 7, Intel Core i7-5600U CPU @ 2.60 2.60 GHz 8 Gb
Camera: Logitech Brio 4K Stream Edition (046d:086b)

What steps will reproduce the problem?
(1) Plug the 4K camera I used [Logitech Brio 4K Stream Edition (046d:086b)]
(2) Choose the camera under chrome://settings/content/camera
(3) Open any webrtc samples which uses camera For example: https://webrtc.github.io/samples/src/content/getusermedia/resolution/ 

What is the expected result?
Chrome should display all the supported resolution. As per the media internals, device is capable of handling other resolutions like HD, FULL HD till 4K. 

What happens instead?
As of now only QVGA works fine. Other feeds are 2*2 resolution which is wrong. Due to this many other sample pages are not working. 

Other useful information:
This happens only when using 4K camera. Other cameras looks fine. 
 
4k camera.PNG
83.2 KB View Download
settings-content.PNG
70.5 KB View Download
Media Internals win 7.html
17.9 KB View Download
webrtc.github.io-1520005266733.log
1.7 KB View Download

Comment 1 by sprang@chromium.org, Mar 15 2018

Components: -Blink>WebRTC>Video Blink>GetUserMedia

Comment 2 by guidou@chromium.org, Mar 15 2018

Cc: guidou@chromium.org
Components: -Blink>GetUserMedia Blink>GetUserMedia>Webcam

Comment 3 Deleted

Cc: phoglund@chromium.org
Labels: -Pri-3 M-66 FoundIn-64 Pri-2
Summary: getUserMedia fails when using 4k camera [Device Specific] (was: Chrome fails to display all the resolutions from 4k camera [Windows 7])
Ping! This issue is still reproducible in M66 Beta on the same device.

66.0.3359.66
Cc: chfremer@chromium.org
Cc: -chfremer@chromium.org
Owner: chfremer@chromium.org
Status: Assigned (was: Untriaged)
Looking at this now. Do we already know whether or not this is specific to Windows 7 or would this reproduce on Windows 10 as well?

I don't have a Windows 7 machine, so I'll try on Windows 10 first.
I tested and was unable to reproduce on the following configuration:

Chrome Version: 66.0.3353.0 (Developer Build)(64-bit)
OS: Windows 10
Device: Dell Precision M3800 Laptop
Camera: Logitech BRIO (046d:085e)

Interestingly chrome://media-internals only lists formats up to 1920x1080. I don't see any 4k resolutions listed. The ID of the camera model seems to be different. Not sure if I have a different hardware model, or just a different driver.
The reason the 4k resolutions didn't show up in the list was that I had plugged it into a USB2 port. When plugging into a USB3 port, 4k works fine on that machine.
Cc: chfremer@chromium.org
Labels: Needs-Feedback
Owner: vasanthakumar@chromium.org
I checked on a 64-bit Windows 7 machine running Chrome 63.0.3239.132 (Stable). There, the issue reproduces. QVGA works, and for all other resolutions I get "getUserMedia:: NotReadableError".

I then installed Skype and tried to use the camera there. But Skype also wasn't able to use it at the resolution it requested. It only showed a black image.

I found that support for this camera on Windows 7 seems limited, see http://support.logitech.com/en_us/article/BRIO-webcam-not-recognized-in-Windows-7?product=a0q3100000BNfaFAAT

But in theory it should be possible to get it to work up to 1080p30. Could you check if you can get any resolution higher than QVGA from apps other than Chrome on your test machine? If not, then the issue is not a Chromium one.

Status: WontFix (was: Assigned)
Thanks Chfremer! 4K camera does not work well in Skype. I have tried in firefox as well. It seem to be the issue with Windows 7 and the the hardware specific. 

Thus closing the ticket. Thanks a lot!

Sign in to add a comment