obsproject / obsproject/obs-studio
Desktop audio input fails if screen resolution changes
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
Ubuntu 22.04
Other OS
No response
OBS Studio Version
29.0.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/EGdIuc92BvRaUDAF
OBS Studio Crash Log URL
No response
Expected Behavior
OBS should be able to record desktop audio at all times.
Current Behavior
Desktop audio works fine when it is first started, but any change of the monitor's resolution causes audio to immediately fail, and cannot be recovered until OBS is restarted.
Steps to Reproduce
- Load OBS
- Play audio (VLC, for example)
xrandr -s 1920x1080
Audio is lost. Reveting the resolution makes no difference.
The audio on the computer itself is fine and continues to play as expected.
Anything else we should know?
The monitor briefly flickers when resolution changes. This may cause the PC to see a disconnect of the monitor, but there's nothing in the system log to suggest this. Nonetheless, no other app has an issue with this and all audio continues to be played.
Also tested with audio-recorder and this has no issues with the input and continues to record.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure in OBS 29.0.2 on Ubuntu 22.04 using the listed steps, especially xrandr -s 1920x1080, then inspect the linked OBS log. Done means desktop audio continues recording after the monitor resolution changes and recovers without restarting OBS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux, ubuntu
- Domain
- audio-video-rtc, desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100