OBS transitions and Studio Mode broadcast checks: a practical guide Separate selection of the next scene from confirmed live output, then test shared sources and audio in private rehearsal and on the viewer return. Author: EVENTODIT Editorial Team Published: 2026-10-26T17:23:42+09:00 Updated: 2026-10-31T11:07:15+09:00 Original URL: https://eventodit.com/en/stories/obs-studio-preview-program-shared-sources.html Practical summary Key decision: Do not treat scene selection as completed output; test shared sources and audio in a non-public rehearsal. Responsible roles / intended readers: Corporate-event and conference streaming operators and show callers Record / next task: Checked scene list, transition method, show-call cues and review results Basis of information: Official OBS overview, audio help and source-duplication developer documentation. Role allocation and viewer-return checks are editorial recommendations. Editorial review: 2026-10-26 Part 1. Planning and show caller "Selecting a scene does not mean it is live. Agree the cue and the criteria for confirming the transition." - Separate scene selection from on-air confirmation: In OBS Studio Mode, selecting the next scene and actually changing the broadcast output are different events. Report readiness and confirmed live output separately. - Agree the screen names in rehearsal: In a non-public rehearsal, make sure the production team understands Preview as the area for preparing and editing the next scene and Program as the current live output. Agree consistent names for both. - Call transitions from the running order: The show caller should name the official scene in the running order. The operator checks Preview is ready and switches on the agreed cue. Choose the transition effect and duration in rehearsal for the actual event; do not turn an example duration in OBS documentation into an assumed event standard. - Control property changes during the broadcast: Exclude changes to sources whose independence has not been verified from live preparation. If a setting must change, specify the permitted time and responsible person in the running order. - Define the completion check and account for viewing delay: Do not mistake streaming-platform delivery latency for a Preview system fault. Agree which monitoring picture and received audio will be used to confirm completion. Part 2. Video and broadcast director "A Preview edit is not necessarily isolated from the broadcast. Test shared-source references and return behaviour in a private rehearsal." - Verify Studio Mode displays and return behaviour: Rather than memorising the default left and right positions, identify the actual video output represented by each window. Check the transition setting and test on the actual system whether the previous live scene returns to the editing area. - Test the limits of shared-source duplication: The OBS developer reference for obs_source_duplicate explains that some sources cannot be independently duplicated and may return a reference to the existing source. When a video capture device, browser source or audio capture input appears in several scenes, different names or separate appearances do not establish independent behaviour. - Test interference privately: Before the public broadcast, change the source settings in the prepared Preview scene in a private rehearsal and check whether Program changes unexpectedly. Never experiment on a live input during a public broadcast. - Verify the actual switching environment: Test the chosen transition effect, Quick Transition buttons, hotkey mappings and screen layout on the equipment that will be used for the event. - Follow the three-stage timeline: Before the cue, select the next scene in Preview and check shared sources and audio. At the cue, confirm the scene against the running order and use the agreed transition. Afterwards, compare Program with the actual viewer output. Practical workflow · Timeline Practical workflow: prepare, transition, verify Before the cue — Prepare the scene Select Preview and check shared sources and audio. At the cue — Transition on the cue Confirm the intended scene and use the agreed transition. After the cue — Verify live output Compare Program with viewer picture and sound; report problems. Note: Verify layout and hotkeys on the system. Changing shared-source properties in preparation may still affect the live broadcast. Part 3. Audio and broadcast checks "A moving meter does not guarantee the viewer can hear. Remove duplicate global audio and listen on the receiving device." - Avoid duplicate global and scene audio: OBS audio guidance warns that assigning the same device in global audio settings and as a scene audio source can produce an echo. Compare the scene audio sources with the global devices in Settings and remove duplicate assignments. - Check for unintended Preview audio: A scene appearing only in Preview does not prove that all associated audio is muted in the broadcast. - Listen to actual sources before and after the transition: While checking the next scene name, captions and framing, do not treat a moving level meter as proof of correct audio. Use the actual event sources, listen on monitoring headphones before and after switching, and record where each device is captured. - Check Program and the viewer return: Immediately after the transition, check the scene, caption layout and framing in Program, then compare the picture and sound on a device receiving the real online stream. Allow for viewing-path latency and use headphones or another arrangement to prevent the return audio being picked up by open microphones. - Record the checked output and sound: A completed transition is more than a scene click. Record the final picture and received sound, any faults found and the corrections still required. Use the original records and supporting templates Keep the approved running order and OBS scene/source list as the references. For each cue, record Preview readiness, shared sources and audio paths, the transition signal/effect, and the Program and final receiver picture/sound. The [technical rehearsal failover checklist](/en/templates/rehearsal-failover.html) supports controlled tests, failures and retests; the [cue-change approval log](/en/templates/cue-change-control.html) supports change impacts and distribution of the revised version. Neither form replaces the OBS configuration list or testing on the actual viewing device. **Final check before use:** Before switching scenes in the live broadcast, cross-check the distinct roles of Preview and Program, prior testing of sources whose independence is unconfirmed, removal of duplicate global audio, and comparison of the final viewer picture and sound. Application conditions Covers basic OBS Studio Studio Mode behaviour. Verify layout, version and source-specific settings on the actual system. Unconfirmed information No event system latency, audio quality, source isolation or broadcast outcome has been tested. Sources OBS · Studio overview and Studio Mode · Checked 26 October 2026 https://obsproject.com/kb/OBS-Studio-Overview#studio-mode OBS · Audio Sources · Duplicate device warning https://obsproject.com/kb/audio-sources OBS developer reference · Sources and obs_source_duplicate · Documentation 33.0.0 https://docs.obsproject.com/reference-sources#c.obs_source_duplicate OBS Studio source code · Studio Mode scene swap setting https://github.com/obsproject/obs-studio/blob/master/frontend/OBSApp.cpp