obsproject / obsproject/obs-studio
Audio delay removed from media source after transition
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 24.04
Other OS
No response
OBS Studio Version
31.0.0
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/kdxzlDgFeNFqLsy2
OBS Studio Crash Log URL
No response
Expected Behavior
Audio delay as set in advanced audio properties should always be applied to the source.
Current Behavior
Having a scene with a media source on it, with an audio delay, after transitioning to another scene with a media source, and back to the original, the audio delay isn't applied anymore.
Steps to Reproduce
- Create a scene with a media source (ideally one with easy desync detection like this)
- Add a noticeable audio delay to it
- Create a second scene with another media source
- Close obs on the scene with the delayed source, reopen, start recording
- Transition to scene 2, then back
- Notice the delay is present in the recording before the transition, but not after.
...
Anything else we should know?
The video taken in that log, which showcases the issue can be found here.
Was also reproduced on Windows 11 and 30.2.3.
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 transition sequence with two media-source scenes and compare the recording before and after returning to the delayed source. Start with the provided OBS Studio log and reproduction video; the fix is complete when the configured audio delay remains applied after scene transitions on the affected setups.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100