Build a deliberate scene collection, verify source transforms and audio routing, and rehearse failures and transitions at the actual output size.
Write the order of the broadcast and what each state must show and play. Include arrival, main content, interruptions and ending where needed. List reusable camera, microphone and media sources, and name them clearly. Choose a canvas and output aspect ratio for the actual destination.
Create each scene and add only the sources it needs. Check stacking, crop, fit and position in OBS’s transform controls. Reuse an existing source when shared settings are intentional; use a separate source when behavior must differ. Lock finished transforms and confirm the capture target after reconnecting devices.
Enter the browser source’s actual viewport width and height, then test its content in the scene. Configure refresh and shutdown behavior according to whether the widget must retain state while hidden. Trigger long names, multiple alerts and an offline state. Physical monitor PPI does not define the browser viewport.
Name each audio path and identify what reaches the stream, local recording and headphones. Avoid capturing the same microphone or application twice. Rehearse scene transitions while speaking and playing media; verify mute and monitoring behavior, then listen to a recording for echo, missing audio and abrupt level changes.
View the output at the expected player size on a phone and desktop. Check text over the actual moving background, source crops, alert collisions and caption space. Use the contrast tool for a chosen text color and an opaque backing color; a single color pair cannot validate every changing video frame.
Test a missing camera, unavailable browser widget and an unexpected break. Confirm a usable fallback scene and an understandable return to the main content. Export the OBS scene collection and relevant profile through OBS, retain required assets and protect account credentials. Download a note describing the tested versions and any remaining manual checks.
Check the chosen canvas and output aspect ratios.
Draft and download the scene map, recovery actions and asset list.
Estimate storage for a rehearsal recording from its actual format.
Check a selected text color against an opaque backing color.
Loading your checklist…
OBS explains source stacking, visibility, positioning and transform controls. Use these controls to verify the actual scene output.
OBS browser sources have their own viewport dimensions and refresh/shutdown options. Test the chosen settings with the widget’s state and content.
WCAG’s contrast guidance concerns the colors behind the rendered text. An opaque backing makes a selected text/background pair stable for comparison.
Keep these task-specific records with the tested version and review date.
| Record | Include | Verify |
|---|---|---|
| Scene | Visible sources and audio routes | Transition into and out of the scene |
| Widget | Viewport and refresh/shutdown behavior | Long content, reconnect and unavailable source |
| Backup | Collection, profile, assets and versions | Reopen and confirm source paths |
Source names such as Guest camera and Presentation audio make routing reviews easier.
A collection export is useful only when its assets and device mappings can be restored.