OBS Virtual Cam doesn't activate (Ubuntu 20.04) #404
Comments
|
This is what happens to me when trying to load the v4l2loopback module |
|
please paste error messages instead of screenshots of them. the screenshot adds zero information and cannot be searched. on my mobile github client it doesn't show at all. apart from that: the template that opens for every new issue asks for a number of specific things to help triage any problem, like your system, kernel and module version. it seems I (or you) missed those questions. finally: please paste the output of |
|
ah, I now see there's a bit of info in the subject. |
|
modprobe: ERROR: could not insert 'v4l2loopback': Operation not permitted |
|
thanks for the text-output. however
|
|
btw, with "the output of |
|
Hi, First, thanks a lot for your great job. I am facing a very similar issue. My configuration : Ubuntu 18.04 LTS - Kernel 5.4.0-70-generic I have installed OBS 26.1.1 and I want to use the vitual cam option. Therefore, I have installed v4l2loopback-dkms : At this stage, OBS displays the virtual cam button. When trying to run v4l2loopback in terminal using the following command : Here is the dmesg output : |
|
@ewennedelec please try a newer version of
There are no external dependencies of v4l2loopback, so you should be able to install the packages from the newer releases without any problems (just download the |
|
Hi, Thanks a lot for your very appreciated support. I now get a "Start vitual cam" button on OBS working, which creates an OBS Virtual Camera device (so things are already better). v4l2-ctl --list-devices gives me the following output : " Chicony USB 2.0 Camera: Chicony (usb-0000:00:14.0-10): But I do not get any output from this device. Trying with Guvcview, I get the following message : Another strange symptom is that my build-in webcam is not accessible anymore after having hit the Start Virtual Cam button once (it's OK before). |
|
@umlaeute : Excellent suggestion to use the .deb files and most importantly the mention of "no external dependencies". I was thus able to get v4l2loopback-0.12.5 running on Bionic Beaver (18.04 LTS) using the Groovy (20.10) .deb packages ! If anyone is wondering from where exactly to download the "latest" v4l2loopback 0.12.5 .deb packages, here is a list of all the download mirrors : https://packages.ubuntu.com/groovy/all/v4l2loopback-dkms/download |
|
Ubuntu 20.04 comes with If you "downgrade" to |
|
Then it is a problem with Ubuntu specific modifications (see the version number), and you should report the problem *there*.
|
|
in my case, the virtual camera from OBS only works, if I unload the module ( |
|
Copy my comments from https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1946660/comments/9: The second open has: As indicated in the capabilities field returned from the This is a direct result of 9a77eb6 merged in #415. This behavior is actually a bug in the upstream v4l2loopback source, function v4l2_loopback_write: Which set |
To resolve this, it involves the designed behavior of read/writing a fd and their effects on |
#457 targets similar thing. Multiple simultaneous streaming (2 reads, 2 writes, read & write) is not allowed in a formal Linux V4L2 driver. And to correctly set the right states for this issue, I think this must be enforced to avoid creating further troubles. |
In my case the module was not loaded at all. Loading it ( |
|
Strangely enough, I've only experienced this issue just recently after upgrading my PC and moving to Jammy. This hasn't happened to me while I was using the OBS virtual camera in Focal. I could toggle it on and off repeatedly without any problems. It does ask for sudo on the first activation though. |
|
Is this still an issue? Running Ubuntu 22.04, OBS 30.2.2, v4l2loopback (latest), I can start and stop a Virtual Camera no problem. I can watch the Virtual Camera with |
I installed v4l2loopback-dkms in order to add the Virtual cam option to obs. But when I try to activate the virtual cam it doesn't actually activate.
I already reported this bug in OBS Linux support, but they told me to report the bug here.
The text was updated successfully, but these errors were encountered: