obsproject / obsproject/obs-studio

Window capture bug #4877 still happens in 27.0.1

Open
#4,878 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

issue/confirmed platform/windows
Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

Windows 10

Other OS

No response

OBS Studio Version

Other

OBS Studio Version (Other)

27.0.1

OBS Studio Log URL

https://obsproject.com/logs/F9J0ct49Egk4jyTA

OBS Studio Crash Log URL

No response

Expected Behavior

A window capture shows at the moment that I switch to a scene contains it.

Current Behavior

See #4877 .
A window capture shows 1 second later after I switch to a scene contains it.

It was said that this has been fixed in 27.0.1, but after updating it's still happening. :(

a

Steps to Reproduce
  1. Create a window capture. Any capture method has this issue.
  2. Create another scene. It can contain the window capture that you just created or other sources. The issue will happen whether the scenes you switch from or to.
  3. Open studio mode or this issue won't happen.
  4. Switch the two scenes. You'll see that the window capture shows about a second after you switch the scenes.
Anything else we should know?

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the delayed window capture after scene switches on Windows 10 using the steps in the report, then review issue #4877 and the provided OBS log. The report names no source files or tests, so locating the window-capture and scene-transition paths will require project familiarity. Done means the capture appears immediately after switching scenes without Studio Mode.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.