Download free
Fuidzy / Tunedzy / Blog / Two-PC Streaming Audio Routing: A Clear Way to Set It Up

Two-PC Streaming Audio Routing: A Clear Way to Set It Up

Updated October 2026 · Live streaming audio

Quick answer

A two-PC setup moves the game to one computer and the streaming software to another, which keeps the stream smooth. Audio must be sent from the game machine to the streaming machine and your microphone must go to the stream. Plan each path on paper, test the delay and make sure you can mute each source quickly.

Many serious streamers run two computers: one for the game and one for the streaming software, the overlays and the chat. The split keeps the game running smoothly while the stream is encoded, and it protects the frame rate from heavy processing. It also makes the audio harder to manage, because sound must travel between machines and still reach the viewer in the right balance. A clear plan saves a great deal of frustration.

This post explains how two-PC audio routing works, the main paths to plan, the problems that appear most often and a setup that is easy to understand and test.

Why a second computer changes the audio

On a single computer, the game, the microphone and the stream all share one audio system, which is simple but can be overloaded. On two computers, the game audio must leave the game machine and arrive at the streaming machine, which adds a link to the chain. Each link can add delay, change the level or create an echo loop if it is set up badly.

The aim is to make each link deliberate, so you know exactly what the viewer hears and where each source comes from.

Plan the paths on paper

Draw the path for each source before you set anything up. The game audio goes from the game machine to the streaming machine. Your microphone goes from the streaming machine into the stream, and may also go to the game machine if you talk to teammates. Music, alerts and chat sounds each need their own path. A diagram with boxes and arrows makes the plan easy to check.

Decide which sources you want viewers to hear and which should stay private. Private sounds, such as voice chat from a game or notifications, need a path that does not reach the stream.

Sending game audio between machines

There are several ways to send game audio from one machine to another, including dedicated network audio software, a virtual audio device or a hardware mixer. Each has its own setup steps, which change between versions, so check the current instructions for the tool you choose. Whichever method you use, test it with a short clip and listen for delay and dropouts.

Keep the sample rate consistent between the two machines. A mismatch can cause crackles, pitch shifts or dropouts that are hard to trace.

Routing your microphone

Your microphone should go to the streaming machine, which is where the stream is built. If you also need to talk to teammates on the game machine, you may need a separate path for the voice chat, so that the game and the stream do not create an echo loop. Test the loop carefully: a voice that comes back into the stream a moment later is one of the most irritating problems for viewers.

Common problems

  • An echo loop, where the stream sends your voice back to your headset.
  • Delay between the game and the voice, which makes reactions feel late.
  • Dropouts or crackles from a mismatched sample rate or a weak network link.
  • Private sounds, such as voice chat or notifications, reaching the stream by accident.
  • Music or alerts playing twice, because two paths were set up for the same source.

Test before going live

Run a full test with the game, the microphone, the music and an alert. Watch the stream on a second device to check the delay and the balance as viewers will hear it. Check for the echo loop, and mute each source in turn to confirm that the mute works. A test takes a few minutes and prevents most of the problems.

Keep the second machine simple

The more software you run on the streaming machine, the more chances there are for audio conflicts. Close anything you do not need, especially background music players, sync tools and notification-heavy programs. Keep the audio drivers updated, but change them only one at a time, and test after each change, since a new driver can alter how the routing behaves.

Consider making the streaming machine a dedicated stream computer, with only the programs the stream needs. A simple machine is easier to diagnose when something goes wrong during a live show. Label the cables and the ports on each machine, so anyone can follow the path during a fault.

Limits

Two-PC setups have more parts, and more parts mean more things to go wrong. Software and hardware change quickly, and the steps here are general. Keep notes of the working setup, and rebuild the path carefully after an update.

Keep the voice clean on both machines

A clean voice is easier to route and to balance. The Clean Streaming Mic describes live noise cancellation that feeds OBS, Discord and Zoom. The Tunedzy Go page covers cleaning recordings. For a single-machine version of the same idea, read the virtual cable setup post in this series.

Try it free: Clean Streaming Mic

Learn your room noise, remove it live and feed OBS, Discord or Zoom. Runs in your browser, nothing is uploaded.

Frequently asked questions

Why do I get an echo loop?

The voice path returns to the microphone. Remove the loop by changing which sources go where.

Is a second computer necessary?

Not for everyone. It helps heavy games and high-quality streams, but a single computer can be enough.

How do I stop private sounds reaching viewers?

Give private sources their own path that does not connect to the stream, and test it.

What should I test first?

The echo loop and the delay, using a full run with the game and the microphone.

Keep reading