Issue metadata
Sign in to add a comment
|
Device cannot access microsoft 3000 camera |
||||||||||||||||||||||||
Issue descriptionChrome Version: 64.0.3282.24 Chrome OS Version: 10176.13.1 Chrome OS Platform: Haswell Network info: wifi (guest) What steps will reproduce the problem? Precondition: Insert Microsoft external camera into the device to be tested 1.1.2: TestRTC 1. Browse to https://test.webrtc.org/ 2. Click Allow in the getUserMedia prompt 3. Click on 'three horizontal bars" icon in blue bar "WebRTC Troubleshooter" 4. Select "Microsoft" camera from "Video source" drop-down list 5. Click Start' What is the expected result? mike should be accessible and should not throw error. What happens instead? Mute button is active, but the status of the call is un-muted which is wrong.
,
Dec 15 2017
,
Dec 15 2017
Vasant, Can you please confirm : a) if this issue is specific to Microsoft 3000 camera ? Is it working with any other Microsoft camera like Microsoft LifeCam VX-2000, Microsoft LifeCam Cinema b) if it is a regression from M63 Can you please upload testrtc logs from Tricky ? (Run tests in WebRTC troubleshooter page, click on bug icon, download the report and upload the logs in this bug)
,
Dec 18 2017
@srcv: a. I do not have other Microsoft camera with me. Let me borrow from Ravi or Chris and get back to you regarding this step. b. Testrtc log is already attached in the ticket. Plz let me know if having any issues.
,
Dec 18 2017
https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/795304 I have tested it with Microsoft life cam with the same test case. It seem to have even more issues. kindly have a look on the two logs.
,
Dec 18 2017
Thus the issue is available in old version 63.0.323986 (microsoftand 64.0.3282.24. Kindly see the video recording the test case. It seem that the issue is not device specific and happens to logitech webcam C930e also. Its a state of this particular page. This cannot be applied when opening single video test page(https://webrtc.github.io/test-pages/src/single-video/).
,
Jan 18 2018
Ping for triaging.
,
Jan 25 2018
This is reproduced for Reks in 65.0.3325.9 / 10323.1.0 https://test.webrtc.org/report/AMIfv944J7GYb3ii6nuz4r2oZYCwQ1eNp2MJN_EumkeTX7lF37049Ykn3P5dSO0t6cm_HbPfmxBQDZ_qpNLgVWj9UM0cJizpcOsbhHBruba991CBEhqId7ohF2sxwIJgU7DLDxK0je8JmXDpLIMefWC8I8O0G49blQ
,
Jan 25 2018
This issue is reproduced in Lars device with 65.0.3325.9 / 10323.1.0. https://test.webrtc.org/report/AMIfv94zKyFjs9LFK3_BWqILT6iZjL9VbOFjNXtlsjDvi4cvyDnGPTrkYt6DdLOzTTJZFl471WvjBy2BSoyvXFjss1qwNzGIMmlMC9PPiRSfquez0--0vCrhJxexDpqFq7qvdUxbwHfIAu2VT2RG0Lj1126dqvQ1Cw
,
Jan 25 2018
Doesn't look like this is related to popup blocking.
,
Mar 21 2018
Seems like the same scenario as 571074. Can we merge into a single ticket?
,
Mar 22 2018
,
Mar 22 2018
Re comment 6, if this is a test.webrtc.org issue, please close this and file a bug in the testrtc github repo. If its a device specific issue, please try to narrow this down using a simpler test page.
,
Mar 22 2018
,
Mar 22 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by vasanthakumar@chromium.org
, Dec 15 2017