Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Failed to start virtual camera #11891

Open
Funtimes909 opened this issue Feb 23, 2025 · 6 comments · May be fixed by #11906
Open

Failed to start virtual camera #11891

Funtimes909 opened this issue Feb 23, 2025 · 6 comments · May be fixed by #11906

Comments

@Funtimes909
Copy link

Funtimes909 commented Feb 23, 2025 •
edited by gxalpha
Loading

Operating System Info

Other

Other OS

Arch Linux

OBS Studio Version

31.0.1

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/Q8JBY1aQ0Z9qQviP

OBS Studio Crash Log URL

No response

Expected Behavior

Virtual camera would start and applications would detect it

Current Behavior

Virtual camera does not start with the following in OBS logs

info: GPU conversion not available for format: 7
info: NV12 texture support not available
warning: Failed to start virtual camera
info: Starting Virtual Camera output to Source : Screen
info: [pipewire] Stream 0x56d23a748780 state: "paused" (error: none)

Steps to Reproduce

  1. Install from system package manager
  2. Launch OBS
  3. Attempt to start virtual camera, any mode

Anything else we should know?

Occurs on the official OBS Flatpak and on system packages, same error across both
@stephematician
Copy link

If I'm correct (see this comment); this is because OBS has a non-compliant use of the V4L2 API when opening a virtual camera. v4l2loopback has been updated to stronger V4L2 compliance; and hence it now (correctly) fails when OBS tries to open the camera.

I was going to submit a PR to OBS to fix this, but I'm busy and it's still a week or two off. OBS needs a way to identify when the older versions of v4l2loopback is in use vs the compliant newer versions.

Best way to fix it (for now) is to revert to the last release of v4l2loopback, i.e. the commit with tag v0.13.2.

@stephematician
Copy link

This has also been logged with v4l2loopack: v4l2loopback/v4l2loopback#618 - but it is OBS that needs revision.

This was referenced Feb 28, 2025
Open
Closed
@Funtimes909
Copy link
Author

This sounds great, I'll try reverting v4l2loopback once I have the time, thank you

@Funtimes909
Copy link
Author

Just reverted back to "v4l2loopback-dkms-0.13.1-1" from the Arch Linux archives, works as expected

@stephematician
Copy link

Great.

NOTE: v4l2loopback 0.14.0 is now available, so once #11906 or similar gets merged, then OBS and v4l2loopback will play nicely again (at least according to testing on my machine!)

@Funtimes909
Copy link
Author

Awesome! Just gotta wait for the package to update in the arch repos to see if it works and then I can close this issue, thank you for your help :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

linux-v4l2: Fix virtual camera start failure stephematician/obs-studio
2 participants
@stephematician @Funtimes909