On my system, after loading v4l2loopback, the virtual camera device was created at /dev/video0. However, this device number can vary depending on your system's hardware configuration and which video devices are already present.
Your gst-launch command failed with: ERROR: from element /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0: Device '/dev/video0' is not a output device. This error is crucial. It means that on your system, /dev/video0 is not the virtual camera created by v4l2loopback. Instead, it's likely your actual physical camera (or another input device), which cannot be used as an output sink. To fix this, you need to identify the correct device path for your v4l2loopback virtual camera. Please run : v4l2-ctl --list-devices Look carefully through the output for an entry similar to: Virtual Camera (platform:v4l2loopback-000) , dummy Video Device (0x0000):, or any other device explicitly labeled as a "loopback" or "virtual" device. Once you have identified the correct path for your virtual camera, replace /dev/video0 in the gst-launch-1.0 command with that path. Additionally, If you simply run 'gst-launch-1.0 libcamerasrc ! autovideosink' you should see yourself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2107304 Title: Intel MIPI Camera not working out of the box on 25.04 where it did on 24.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/2107304/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
