Unable to reproduce the issue on Mac 10.11.4 using chrome version 50.0.2661.75  and canary 52.0.2712.0 .Adding TE-NeedsTriageFromMTV as we dont have webcam with Linux.

MTV Team@ Could any one please look into this issue .

Thanks,

More info about the Webcam Creative VF0640 Live! Cam Socialize issue.

https://dl.dropboxusercontent.com/u/83676403/Varios/Shot_Top17_Chrome_settings_1.jpg

https://dl.dropboxusercontent.com/u/83676403/Varios/Shot_Top17_Chrome_settings_2.jpg

Note: The info of chrome://media-internals can be found at https://productforums.google.com/d/msg/chrome/rejkT8r86y0/sTwy344gBQAJ

Components: -Internals>Media>Video Blink>WebRTC>Video

Sorry, I don't understand. What should do about?

chrome://media-internals/players

render_id: 10
player_id: 1
event: WEBMEDIAPLAYER_DESTROYED
url: blob:https%3A//www.playwithapro.com/5aa3cf48-7f4b-492e-a4bd-298de410f6eb


Is this info relevant?

luis@ - on the same linux machine, with the VF0640 cam attached, can you go to https://test.webrtc.org/? Before pressing the Start button, please press the menu button at the top and make sure the right webcam is selected (see attached screenshot).

Then save the settings, press the Start button, and let the tests run to completion. After the tests finish, click the bug icon at the top of the page, click "download report," and attach that report to this bug. Thanks!

Deleted: testrtc-screenshot.png 60.8 KB

	testrtc-screenshot.png 60.8 KB View Download

The same problem tnakamura@.

You can see the attached files.

Deleted: Shot_Top17_Chrome_settings_3.jpg 103 KB

	Shot_Top17_Chrome_settings_3.jpg 103 KB View Download

Deleted: testrtc-2016-04-26T17-12-51.150Z.log 16.1 KB

testrtc-2016-04-26T17-12-51.150Z.log 16.1 KB View Download

Thanks for the quick follow up!

tommi@ and niklase@ - do you have a suggestion for a next triage step?

[triage] luis.orden@ could you copy and paste the output of 'v4l2-ctl --list-formats' here?

FTR media-internals lists V4L2 splane as the API.

Here is the output:

$ v4l2-ctl --list-formats
ioctl: VIDIOC_ENUM_FMT
	Index       : 0
	Type        : Video Capture
	Pixel Format: 'YUYV'
	Name        : YUYV 4:2:2

Thank you for providing more feedback. Adding requester "jansson@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

[triage]: Christoffer, please take a look at #13.

magjed@ do we support the YUYV pixel format in Chrome?

Yes, we support YUYV in Chrome on Linux:
https://cs.chromium.org/chromium/src/media/capture/video/linux/v4l2_capture_delegate.cc?rcl=1468379992&l=48

Could you try one last thing:

1. Enable logging in Chrome https://www.chromium.org/for-testers/enable-logging 
2. browse to https://webrtc.github.io/samples/src/content/peerconnection/constraints/ and select 160x120 resolution
3. Check if errors are printed in "dmesg"
4. Attach the logs from Chrome in this bug.

[triage] Will leave this open for another week.

Hi jansson,

sorry, I was on holidays... :)

I attached the output of dmesg and the output at https://webrtc.github.io/samples/src/content/peerconnection/constraints/.

Deleted: dmesg 49.6 KB

dmesg 49.6 KB View Download

Deleted: WebRTC 9.5 KB

WebRTC 9.5 KB View Download

You have not done step 1 and included the log. The output from the constraints page just concludes the camera was never opened due to some lower level issue most likely. Could you please try that?

Also, does the camera work in guvcview? If so, which formats?

Sorry, jansson, I didn't understand what he meant. 

Is this the correct kog file?

Deleted: messages 1.2 MB

messages 1.2 MB View Download

jansson, this is the output in terminal after enable-login:

$ google-chrome --enable-logging --v=1
NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted).
NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted).
[6586:6623:0831/211001:ERROR:audio_input_sync_writer.cc(324)] AISW: No room in socket buffer.
[6586:6623:0831/211001:ERROR:audio_input_sync_writer.cc(324)] AISW: No room in socket buffer.

You should find a chrome log file in the Chrome user directory, check where that is for linux at http://dev.chromium.org/user-experience/user-data-directory. 

Also, could you see if the camera works using the guvcview app?

Jansson, is this the file?

Yes, the camera works fine using guvcview.

Deleted: chrome_debug.log 1.8 MB

chrome_debug.log 1.8 MB View Download

Yes that is the file, however I realize you might need to pass some extra flags to get the logging we want, also it might not even be available in release builds.

mcasas@, magjed@ what flag should be passed to chrome in order to get some hints to why the camera does not work?


luis.orden@ also, could you try the different video formats in the video tab by changing in the Camera Output drop down. Then take a screenshot of the one that does not work and add it here.

mcasas@, magjed@: can you please help out as requested in #27?

luis.orden@: did you have any chance to try different video formats?

Eureka!! 
Today I did a standard update in my system and Chrome updated to the new Version 53.0.2785.101 (64-bit)

Now the Camera is working pretty well!!

I don't know what solved the problem but for the moment the camera is working!!

Good stuff, I would still like to know why it started working. What parts of the system was updated? Maybe some new UVC drivers?

magjed@ we have not merged anything related to video this late in M53 right?

I'm not aware of any camera/video work that has been merged, but I haven't worked in Chromium much at all lately.

Jannson, here are the updates (I can't remember but I think the camera was working before I updated the kernel from 4.6.6 to 4.7.3):

Commit Log for Mon Sep 12 19:11:27 2016


Instaló los paquetes siguientes:
kernel-4.7.3-pclos1 (1-1pclos2016)
kernel-devel-4.7.3-pclos1 (1-1pclos2016)


----------------

Commit Log for Mon Sep 12 19:05:46 2016


Actualizó los paquetes siguientes:
bleachbit (1.10-1pclos2016) to 1.12-1pclos2016
dkms-broadcom-wl (6.30.223.271-1pclos2016) to 6.30.223.271-2pclos2016
dkms-ndiswrapper (1.59-4pclos2015) to 1.60-1pclos2016
google-chrome-stable (52.0.2743.116-1) to 53.0.2785.101-1
lomanager (5.2.0-1pclos2016) to 5.2.1-1pclos2016
mesa (12.0.1-4pclos2016) to 12.0.2-1pclos2016
mesa-devel (12.0.1-4pclos2016) to 12.0.2-1pclos2016
ndiswrapper (1.59-4pclos2015) to 1.60-1pclos2016
python-httplib2 (0.8-1pclos2013) to 0.9.2-1pclos2016

------------------------------


Commit Log for Wed Aug 31 20:45:33 2016


Quitó los paquetes siguientes:
lib64qalculate5

Actualizó los paquetes siguientes:
git (2.8.4-1pclos2016) to 2.9.3-1pclos2016
kde-baseapps (15.04.3-1pclos2015) to 15.04.3-2pclos2016
kde-baseapps-core (15.04.3-1pclos2015) to 15.04.3-2pclos2016
kde-baseapps-dolphin (15.04.3-1pclos2015) to 15.04.3-2pclos2016
kde-baseapps-help (15.04.3-1pclos2015) to 15.04.3-2pclos2016
kde-baseapps-kdepasswd (15.04.3-1pclos2015) to 15.04.3-2pclos2016
kde-baseapps-kdialog (15.04.3-1pclos2015) to 15.04.3-2pclos2016
kde-baseapps-kfind (15.04.3-1pclos2015) to 15.04.3-2pclos2016
kde-baseapps-plasma (15.04.3-1pclos2015) to 15.04.3-2pclos2016
kde-plasma-addons (4.14.3-2pclos2015) to 4.14.3-3pclos2016
kde-workspace (4.11.22-1pclos2016) to 4.11.22-2pclos2016
kde-workspace-core (4.11.22-1pclos2016) to 4.11.22-2pclos2016
kde-workspace-cursor-themes (4.11.22-1pclos2016) to 4.11.22-2pclos2016
kde-workspace-help (4.11.22-1pclos2016) to 4.11.22-2pclos2016
kdm (4.11.22-1pclos2016) to 4.11.22-2pclos2016
lftp (4.7.3-1pclos2016) to 4.7.3-2pclos2016
lib64cln6 (1.3.1-2pclos2011) to 1.3.4-1pclos2016
lib64wxgtku3.0_0 (3.0.2-5pclos2015) to 3.0.2-6pclos2016
slimjet (11.0.3.0-1pclos2016) to 11.0.5.0-1pclos2016
wxgtk (3.0.2-5pclos2015) to 3.0.2-6pclos2016

Instaló los paquetes siguientes:
lib64qalculate6 (0.9.9-1pclos2016)
lib64tidy-html5 (5.2.0-1pclos2016)

I think the updates where done in Chrome because the camera is still not working in Slimjet...

The only problem now is that this version of Chrome crashes some times...