Problem
Switching scenes causes a one-frame flash of a private source because transition ordering is misconfigured.
Solution
Root Cause / Diagnostic:
When switching between scenes in OBS or software vision mixers, rendering pipeline execution order can evaluate source visibility before the transition wipe or stinger matte completely occludes the canvas. If private production feeds (such as backstage green rooms or private notes) exist on an unmuted layer without transition point masking, a 1-frame artifact leaks to the Program feed.
Actionable Fix:
1. Calibrate Stinger Transition Point to 100% Matte Coverage: Open Transition Properties and set the Transition Point Type to "Time" or "Frame" exactly matching the frame index (e.g., frame 32 at 60fps / 533ms) where alpha opacity is complete.
2. Isolate Internal Feeds to Dedicated Preview Busses: Never place private operator notes, Run-of-Show dashboards, or unvetted backstage video inside broadcast Program scenes; route them exclusively to secondary physical monitors via OBS Fullscreen Projector.
3. Enable Studio Mode and Verify Transition Masking: Always switch utilizing Studio Mode with "Duplicate Scene" enabled, auditing transitions at full framerate on an offline multiview monitor before taking on-air.
Pro Tip:
When using stinger transitions with animated alpha channels, encode them strictly as Apple ProRes 4444 or QuickTime Animation codec with 32-bit depth; avoid CPU-heavy WebM stingers that drop frames and desynchronize the transition cut point under high render loads.
When switching between scenes in OBS or software vision mixers, rendering pipeline execution order can evaluate source visibility before the transition wipe or stinger matte completely occludes the canvas. If private production feeds (such as backstage green rooms or private notes) exist on an unmuted layer without transition point masking, a 1-frame artifact leaks to the Program feed.
Actionable Fix:
1. Calibrate Stinger Transition Point to 100% Matte Coverage: Open Transition Properties and set the Transition Point Type to "Time" or "Frame" exactly matching the frame index (e.g., frame 32 at 60fps / 533ms) where alpha opacity is complete.
2. Isolate Internal Feeds to Dedicated Preview Busses: Never place private operator notes, Run-of-Show dashboards, or unvetted backstage video inside broadcast Program scenes; route them exclusively to secondary physical monitors via OBS Fullscreen Projector.
3. Enable Studio Mode and Verify Transition Masking: Always switch utilizing Studio Mode with "Duplicate Scene" enabled, auditing transitions at full framerate on an offline multiview monitor before taking on-air.
Pro Tip:
When using stinger transitions with animated alpha channels, encode them strictly as Apple ProRes 4444 or QuickTime Animation codec with 32-bit depth; avoid CPU-heavy WebM stingers that drop frames and desynchronize the transition cut point under high render loads.