Plan the video and audio path between two computers, verify capture compatibility and synchronization, and compare representative runs before committing to the setup.
Capture a baseline of the current game or presentation and OBS behavior: frame pacing, rendering lag, encoding lag, network drops and required sources. Decide which measured constraint the second computer is meant to address. List existing hardware and required input/output modes before choosing a capture or network path.
Document the source output, capture input, passthrough display and stream output. Check the exact device specifications for resolution, frame rate, color format and any HDR or variable-refresh behavior you need. Confirm capture support separately from passthrough support. Use the ratio tool to identify required crop or letterboxing, then test the actual device.
Draw the route for microphone, game audio, voice chat, stream mix and headphones. Identify which computer captures each source and prevent monitoring from feeding back into capture. Use compatible device settings and test channels, mute behavior and reconnects. Investigate hum by isolating signal paths according to equipment instructions; do not alter protective electrical grounding.
Use a visible clap or another repeatable audiovisual event to measure the recorded offset. Adjust the appropriate synchronization setting, then repeat the check through the full capture and encoding path. Listen for echoes or missing channels. For an audio noise comparison, enter only compatible measured signal/noise levels. Budget local PCM tracks from their actual stored format.
Run the same busy scene or game sequence as the baseline, with the full overlay and audio setup. Record local playback and inspect rendering, encoding and network statistics separately. For a network video path, measure the actual protocol, configuration and competing traffic; a fixed switch speed or latency claim does not prove sufficiency.
Test loss of the capture source, restart of either computer and an interrupted audio route. Confirm a holding scene or simpler single-computer fallback. Save device models, ports, supported modes, OBS configuration and synchronization observations. Download the wiring and acceptance record; retain the setup only if the observed benefit justifies its complexity.
Write and download the baseline, wiring diagram as text, and recovery record.
Compare the source and output proportions for crop or letterbox decisions.
Compare compatible measured signal-only and noise-only levels.
Budget uncompressed local audio tracks with the actual stored sample width.
Loading your checklist…
OBS documents video-capture sources and their device-dependent format, resolution and frame-rate properties. Verify supported combinations on the actual capture hardware.
OBS rendering and encoding need system resources even when hardware encoding is used. Compare real runs and inspect the affected stage.
Keep these task-specific records with the tested version and review date.
| Record | Include | Verify |
|---|---|---|
| Video | Source port → capture → display/output modes | Capture and passthrough independently verified |
| Audio | Source → mix → stream/headphones | No duplicate route or feedback |
| Recovery | Failed component and fallback action | Rehearsed restart and return to program |
A baseline and a borrowed or existing capture path can reveal whether the second machine solves the actual problem.
A device’s advertised passthrough mode may differ from the mode it records.