Dual-PC audio routing

Decide which PC each sound starts on

Every dual-PC source needs an owner and a crossing. Game audio may cross embedded in HDMI, through analog audio or through a supported software/device route. Creator voice and team chat need deliberate sends and returns; the capture card solves only the HDMI capture path.

Two computers have separate clocks, default devices and software states. The route must still work after reconnecting and during a full-length local recording.

What to plan

Check these in order. The first two, device ownership and game audio crossing, decide whether it works at all; the rest make it easier to use.

• Device ownership: Decide which PC the microphone, headphones, interface and capture card each plug into.
• Game audio crossing: Choose HDMI, analog or a documented digital route and keep it singular.
• Creator microphone: Define how voice reaches stream and gaming-PC chat.
• Chat return: Bring teammates to the creator monitor and stream as permitted.
• Mix-minus: Exclude chat return from the send back to chat.
• Monitoring: Create one low-latency creator mix containing both computers.
• Recording tracks: Assign game, voice and chat to intended stream/record tracks.
• Recovery: Document device names and startup order for both machines.

What can catch you out

Any of these can change your choice, or tell you what to check next when something fails.

• HDMI audio default: Changing display/capture topology can change the gaming PC output device.
• Double crossing: HDMI audio plus a second software/analog route produces doubling.
• Clock drift: Independent devices can drift over longer sessions.
• USB ownership: A device’s routing software runs on the PC its USB cable plugs into.
• Chat application: Current app/device support must be checked for your exact two-PC setup.

Set it up step by step

Follow the steps in order. Check that your computer sees each device before you choose it in OBS or your audio app, and change one cable or setting at a time.

• Step 1: Draw both computers and all crossings.
• Step 2: Connect/prove HDMI video and embedded audio first.
• Step 3: Connect your microphone and headphones to the PC you chose for them.
• Step 4: Create chat send/return with the return excluded from the send.
• Step 5: Record a long test and inspect level, drift, mute and reconnect behavior.

Two common setups

A basic route embeds gaming-PC sound in HDMI to the capture device, while the microphone and headphones live on the stream PC. Voice-to-team-chat then needs one supported return crossing.

An interface or mixer that connects to two computers can handle the sends in one place, but dual USB ports may have different roles. Verify each source/destination rather than treating two connectors as identical.

See also the dual-PC streaming setup and the mix-minus guide.

What usually goes wrong

Find your symptom below. Change one thing at a time, and make a short test recording after each change before you go live again.

• No game audio after reboot: Re-select HDMI/capture as the gaming-PC output and OBS input.
• Robotic or drifting audio: Simplify clock domains/routes and test before applying compensation.
• Teammates hear stream echo: The program/chat return is inside their send; remove it.
• Creator hears voice twice: Direct monitoring and a returned stream/chat path both contain the microphone.

Test it after a restart

Record game audio and a speaking sample while monitoring on the streaming computer. Confirm each source arrives once and reaches the intended stream and recording destinations.

Restart both computers and reconnect in the normal order, then run a full-length local recording. Growing drift or changed default devices means the route is not yet stable.

Equipment for these connections

Start with the kind of gear you’re missing, and read its full profile before adding it to your setup.

As an Amazon Associate I earn from qualifying purchases. How this site earns · Amazon offers a free 30-day Prime trial, with free delivery on eligible items.