-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fake.py freaks out when trying to access with chrome #25
Comments
This is the limitation of v4l2loopback, please refer to umlaeute/v4l2loopback#78. |
Sadly, this does not really help. In my case, the "cam" IS detected but fake.js stops working as soon as I connect with chrome. |
Well, my point is that this problem has got nothing to do with these scripts. It has got to do with Chrome or v4l2loopback. |
@mtedaldi, you could potentially output stream of this webcam to webcamoid + akvcam, if you are desperate for chrome. |
@mtedaldi , I added support for akvcam, it should work with Chrome. |
Thank you very much! I'll try as soon as possible! |
Hi. Since I have no Webcam on my system I had to do a few more tricks. I'm using my DSLR as webcam via gphoto2 and v4l2loopback. So my modprobe looks like this
sudo modprobe v4l2loopback video_nr=0,2 exclusive_caps=1,1 card_label="EOS 7D mkII","Fake Webcam"
(Creating 2 devices, video0 and video2, each with exclusive_caps=1).
This way I can run the software without any changes. I can access both streams with VLC and everything runs fine.
BUT when I want to access the Webcams from google chrome (using jitsi for video chat), fake.py "freaks out". Seems, it can't get the mask anymore.
It's the same behaviour with or without the option "- f 12". That's just that my camera doesn't deliver more FPS over USB, so why should I waste a lot of processing power.
Tested jitsi with Firefox and there is no issue (but Jitsi is unbearably sluggish in firefox).
There are quite some people having issues accessing v4l2loopback "cameras" with chrome. But they normally just get "no picture" or "device not detected". But that chrome seems to be able to crash the video source seems really strange!
The text was updated successfully, but these errors were encountered: