obsproject / obsproject/obs-studio
Replay Buffer doesnt work consistently
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
Windows 11
Other OS
No response
OBS Studio Version
31.0.3
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/RokOBsbYCTxCgXnK
OBS Studio Crash Log URL
No response
Expected Behavior
I want replay buffer to save the last 30s, so I click my designated button (F17),
Current Behavior
taken from another bug report #8753 as i am having the same issues.
Whenever I click on the Save Replay button, 4/5 times it just does absolutely nothing, then whenever I click on Stop Replay Buffer in the application to try to fix it, it says "Stopping Replay Buffer..."
This happens indefintely, and i have to close OBS from task manager, and boot it back up manually. This sometimes fixes the problem, but not every time. This seems to happen after every sleep, hibernate, shutdown and restart, so power cycle, and im unsure of the cause. I went through another thread not so long ago that made a windows script to close obs, and then start obs on system wakeup, but that seems to do nothing.
Steps to Reproduce
- Start replay Buffer
- Hide OBS to system tray
- Click save replay button
Anything else we should know?
No response
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 with the listed steps: start Replay Buffer, hide OBS to the system tray, and click Save Replay. Review the supplied OBS log while testing the behavior after sleep or restart; done means saving the last 30 seconds works reliably and Stop Replay Buffer does not remain stuck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100