obsproject / obsproject/obs-studio
Stopping and Starting the replay buffer can sometimes misleadingly say "Start Replay Buffer" highlighted in Blue - when the buffer is not actually running
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 6.6.9
OBS Studio Version
30.1.0-beta1
OBS Studio Version (Other)
30.0.2
OBS Studio Log URL
https://obsproject.com/logs/7dMcegktuCWy5ECG
OBS Studio Crash Log URL
No response
Expected Behavior
The replay buffer to start
Current Behavior
The replay buffer sometimes doesn't start, but the button becomes filled with blue as if it has started (Despite the text remaining the same) which is misleading and has lead to me missing many potential clips the past year.
Steps to Reproduce
- Do something potentially requiring a save of the Replay Bufrfer
- "Flush" the Replay Buffer by toggling it off and on again to trim the beginning of a potential clip.
- Sometimes clicking the Replay Buffer will cause it to change it background color to blue, indicating the buffer has started. Sometimes, it actually still says "Start Replay Buffer" and has not actually toggled the feature on.
This leads to many lost potential clips.
...
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 with the linked OBS log and reproduce the replay-buffer toggle sequence described in the issue, comparing the button's highlighted state with whether the buffer actually starts. Trace the replay-buffer toggle flow and its UI state updates; done means repeated toggling keeps the label, highlight, and running state consistent.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100