obsproject / obsproject/obs-studio
[macOS]: Twitch frame judder when OBS is hidden
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
macOS 14
Other OS
No response
OBS Studio Version
30.2.3
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/msO6lZ5uXO5hjBN9
OBS Studio Crash Log URL
No response
Expected Behavior
When hidden, OBS should perform normally. If it is unable to, some indication should be visible, like dropped frames or another indicator of GPU instability.
Current Behavior
When hidden OBS experiences rendering lag, as seen in the above log, which causes odd frame judder on Twitch without any corresponding dropped frames in either OBS or Twitch's video player. For instance this time mark in a recent stream of mine. You can see later in that same video that the judder is gone once I realized it was due to being hidden. Perhaps this is due to macOS' App Nap or related tech? (Disable App Nap.
Steps to Reproduce
- Start stream, ideally a game for GPU resource usage.
- With OBS foreground, observe the smoothness of the stream.
- Hide OBS (Command - H).
- Observe stream's frame judder. Observe no dropped frames from OBS or Twitch.
Anything else we should know?
Hardware is a Mac Studio M1 Ultra, macOS 14.6.1, 128GB RAM.
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
No source file or test is named. Start by reproducing on macOS 14.6.1 with OBS 30.2.3 while streaming a GPU-intensive game, compare OBS foreground and hidden, and inspect the linked log for rendering-lag details. Done means hidden OBS no longer causes Twitch frame judder without reported dropped frames.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, macos
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100