obsproject / obsproject/obs-studio

V4L2 Camera Controls are saved but not applied

Open
#11,633 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

Other

Other OS

Gentoo Linux

OBS Studio Version

30.2.3

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/VkYUN8m2U7UviFwB

OBS Studio Crash Log URL

No response

Expected Behavior

Either the properties should simply show the current values, or the saved values should be applied when starting OBS.

Current Behavior

OBS allows setting properties for V4L2 devices, and these appear to be saved, but not applied unless I go back and set a new value.

Steps to Reproduce
  1. Add a Video Capture Device (V4L2) device to the scene
  2. Change a value (e.g. "Zoom, Absolute")
    - The setting is applied.
  3. Close OBS
  4. Unplug and reinsert the device
  5. Reopen OBS
    - The settings have been reset.
Anything else we should know?

A number of similar issues have been marked as duplicates of #3092, but that issue has now been closed without a resolution.

Some properties may be applied correctly, but I'm not sure, and Zoom definitely is not.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with the V4L2 Video Capture Device and the "Zoom, Absolute" control, then inspect how V4L2 properties are restored when OBS starts. Done means saved controls are applied after reopening OBS and reconnecting the device, or the properties accurately show the current values.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.