obsproject / obsproject/obs-studio
Replay buffer does not respect maximum time setting, saves files much longer/larger than intended
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
Arch Linux
OBS Studio Version
30.0.0
OBS Studio Version (Other)
30.0.0
OBS Studio Log URL
https://obsproject.com/logs/b3YBDkUJ7gyoovOa
OBS Studio Crash Log URL
No response
Expected Behavior
When my replay buffer is set to a maximum of 120 seconds and 8192MB memory usage, I expect it to output files with a length of ≤120 seconds (± a few seconds due to keyframes and other variables).
For context, given my other recording settings, this typically works out to around ~2.5GB file sizes for saved replay buffer segments.
Current Behavior
Saving the replay buffer creates a file that instead goes back to the moment OBS was launched, rather than respecting the maximum length setting.
As an example: I currently have a recording from replay buffer that is over 26 minutes long, and approximately 9GB. As you might expect, the quality is severely degraded (to say the least), and it takes much longer than normal to actually save + write to disk.
Steps to Reproduce
- Launch OBS
- Wait for an amount of time greater than specified in the "Maximum Replay Time" setting
- Save the replay buffer and observe the file produced
Anything else we should know?
- Rolling back to the previous version in the Arch repositories (28.x.x) resolves the issue
- Manually stopping/starting the replay buffer seems to reset it, however the next saved segment will begin at the moment the buffer was restarted (ie, still not respecting the maximum time value).
- Changing the "Maximum Replay Time" value does not work
- Whether or not you are actively recording has no effect
- Disabling plugins or changing other video settings does not appear to have an effect
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
Start by reproducing the issue in OBS Studio 30.0.0 with Maximum Replay Time set to 120 seconds, following the listed steps, and compare the result with the 28.x version. Trace the replay buffer handling responsible for the saved segment length. Done means saved files remain within the configured maximum time instead of extending back to launch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100