Originally created by: alexande...@gmail.com
Originally owned by: soylent...@gmail.com
What steps will reproduce the problem?
1. run webcamstudio
2. run chrome (or chromium)
3. Go to: http://www.testwebcam.com
What is the expected output?
Flash player permission dialog will appear asking to proceed with loading the camera (which in this use case should be the "virtual" webcamstudio camera.
What do you see instead?
webcamstudio camera is not among the cameras listed in chrome's available cameras dropdown
The Operating system you are using (Linux, Windows etc)?
Ubuntu 14.04 LTS
What version ofWebcamStudioare you using?
0.71
What version of Java are you using?
Java(TM) SE Runtime Environment (build 1.7.0_72-b14)
What is your Webcamera vendor, model and version?
Logitech 9000
For *nix users please enter the output from "sudo lsusb"?
Bus 002 Device 004: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
Bus 002 Device 006: ID 046d:0809 Logitech, Inc. Webcam Pro 9000
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 009: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
Bus 001 Device 008: ID 0763:2012 Midiman M-Audio Fast Track Pro
Bus 001 Device 007: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 006: ID 04f2:b15e Chicony Electronics Co., Ltd
Bus 001 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 004: ID 138a:0007 Validity Sensors, Inc. VFS451 Fingerprint Reader
Bus 001 Device 003: ID 03f0:231d Hewlett-Packard 4 GB Flash Drive
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: soylent...@gmail.com
Hi Alexander,
I'm sorry but at the moment I am the only person who can try to debug this issues, and also the only maintainer of WS.
Anyway I hope that someone can give WS project an hand :)
Back to us this issue was solved by Kevin Branham in the community.
About the permission issue, I can't reproduce the issue on my Ubuntu 14.04 64bit machine, but I got it on my UbuntuStudio 14.10 x86.
Seems more a Chrome issue than WS ... anyway I will try to debug this.
Will let you know.
Thanks.
karl
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: soylent...@gmail.com
I'll handle this one.
Owner: soylent...@gmail.com
Status: Accepted
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: soylent...@gmail.com
Hi Alexander,
this is what i try, and finally, got it working.
This first steps may not be necessary:
- Adding my user to "video" group --> Result: no permissions
- Installing diff packages to my working Ubuntu 64bit:
phyton3-requests
python3-urllib3 --> Result: no permissions
- Installing diff packages to my working Ubuntu 64bit:
nginx-core --> Result: no permissions
- Setting Java Permissions in control panel --> Result: no permissions
I saw that http://www.testmycam.net/ works.
Because https://jitsi.org is on a secure connection i tough that the problem was on port 443 ... but in google hangout (https connection) the virtual device works ok.
After this I uninstall Chrome Version 38.0.2125.111 and I install the deb they propose on the chrome site (version 33.0.1750.146).
Running Chrome give me a warning message, but now https://jitsi.org works.
Really don't know why this occurs.
Will try now to re-update chrome to the latest, and see what happen ...
karl.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: soylent...@gmail.com
Reinstalling Chrome latest version, the problem is back on my UbuntuStudio machine.
Maybe https://jitsi.org/ support can understand the problem.
I also tried with the virtual webcam feeded by gstreamer in a command line, without WebcamStudio, and the problem persists ... Contact v4l2loopback team is another possible help.
karl
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: soylent...@gmail.com
More tests ...
On my UbuntuStudio 14.04 x64 machine after giving the permissions, https://jitsi.org works correctly with the webcamstudio (v4l2loopback) SkyCam module, so I can reproduce the problem only on my UbuntuStudio x86 machine.
The only workaround i found is to uninstall completely chrome current version 38.0.2125.122 in this way (This will delete all bookmarks and settings on chrome):
Delete /home/user/.config/google-chrome and .config/chromium if you have it.
Purge the packages with:
$ sudo apt-get purge google-chrome-stable
$ sudo apt-get purge chromium-browser
And then installing the Chrome version 33.0.1750.146 that if you cannot find i will upload here:
https://drive.google.com/file/d/0BxkZ_wh6t7jbelBST3ZSU0FzQW8/view?usp=sharing
Don't know why I get this version when I first download it from the Chrome official page (yesterday ...) ...the successive downloads from the same official chrome page give me the latest 38 version ...
No i can't find it anywhere at the first searches ...
karl
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: jan...@lizardsun.com
Karl,
Thank you for all of these excellent responses!
I will try everything you have advised here right now and let you know what I find.
Best,
Alex
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: alexande...@gmail.com
By installing the version of Chrome you staged on your Google Drive, (and also by removing chromium), I am happy to report that WCS is now working 100% perfectly with Jitsi Meet. Thank you so much Karl!
-Alex
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: soylent...@gmail.com
You welcome Alex,
it would be good to understand why this version works ... Seems that
Chrome latest works well only on my 64bit machines. I also try Chrome beta
and unstable latest version on my x86 machine without results ...
Have a good day.
karl
2014-11-12 21:35 GMT+01:00 <webcamstudio@googlecode.com>:
From what I've seen of this issue it seems like it was probably just on Google's end. Using v4l2loopback I've been able to see my loopback stream in VLC, Firefox, and WCS itself - but not Google Chrome. But when I upgraded Google Chrome to a more current version (43.0.2357.81 (64-bit)) I can now see the WCS loopback feed in Chrome - but there's some kind of color channel issue. (Apparently, red and blue color channels appear swapped in Chrome - perhaps that should be a new ticket?)
I haven't tested the webcamstudio version of the v4l2loopback driver because, honestly, I've not had any success with it in any of my tests. Since it's very nearly the same code as v4l2loopback I'm not sure what's happening there.
Last edit: Tetsujin 2015-05-31
Just tested in Google Chrome 43.0.2357.81 (64-bit).
I can confirm that now the WSVideoDevice (same code of v4l2loopback - only name changes) is listed in Chrome but with red/blue swapped.
If you use SkyCam (it makes a new dev/video21 via a Gst-launch pipe) and choose that, also the colors works, but for some reason works only once and if re-selected, doesn't works.
We can open a ticket on v4l2loopback github:
https://github.com/umlaeute/v4l2loopback
I can really do nothing about that.
Hi George,
I will test the new version of Chrome as soon as possible. Thanks for the feedback.
Have you try to apply the Swap red/blue filter on the webcam Stream?
If the colors get ok then it is a red/blue swap for sure.
I will let you know.
karl
Diff:
Code changes in Chrome and/or the upstream v4l2 loopback driver seem to have fixed this. Other issues are being tracked as we aim to further improve WCS functionality with Chrome.