Issue metadata
Sign in to add a comment
|
Chromebox OS cannot handle few resolutions from Logitech Brio 4K Stream Edition (046d:086b) |
||||||||||||||||||||||||
Issue descriptionChrome Version: 10176.47.0 / 64.0.3282.87 Zako, Tricky OS: Chrome OS [not reproducible in chromebook- Glimmer, Macbook pro corporate machine] As of now strictly limited to chrome boxes and specific camera model. What steps will reproduce the problem? Pre-requisite: Logitech Brio 4K Stream Edition (046d:086b) is plugged in the chrome box. Make sure it is selected in chrome://settings/content/camera. 1. Browse to https://webrtc.github.io/samples/src/content/peerconnection/constraints/ 2. Open the javascript console (alt+cmd+j or ctr+shift+j) and watch for any errors 3. Adjust the Camera constraint sliders as shown in the picture. (sample below too) width 1036-1592 height - 1434 - 1796 last two parameters 0 make sure you plan these things as per the OS support by opening chrome://device-internals and then click video capture. This lists down all the resolutions for this camera. 4. Press "Get media" 5. Press "Connect" What is the expected result? Video should appear as per the range provided or the nearby range. What happens instead? Video of 2*2 is shown and in other terms video is blacked out. Note: Similar tests were performed in chromebook (Glimmer) and Mac OS. What happens is either a corresponding resolution or nearby range if not exact resolutions were displayed. For example in the above example we should expect the height range between 1434 - 1796. Chromebook and Macbook provides a range like 1080 for eg. Blacking out is not observed on any devices.
,
Jan 18 2018
Does the device gets all fixed resolutions from this page ? https://webrtc.github.io/samples/src/content/getusermedia/resolution/
,
Jan 18 2018
Yes it gets those resolutions. No issues in it.
,
Apr 17 2018
Ping!
,
Apr 17 2018
Kindly skip the comment 5 & 6.
,
Apr 17 2018
This issue is still reproducible in M67 67.0.3383.0 / 10539.0.0 [Zako]
,
May 17 2018
Ping!
,
May 18 2018
,
May 18 2018
I believe this is an issue with the UVC driver in older kernels. Cyan works because it has 3.18 kernel. We found that this issue seems to reproduce in 3.14 and earlier kernels. Zako and Tricky are on 3.8 kernel.
,
May 18 2018
Let me duplicate this one to the other bug which has more context on the same failure on 3.8 kernel on another device. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by vasanthakumar@chromium.org
, Jan 18 2018