Webcam testMicrophone testWebcam and mic test
TestsWebcam testMicrophone testWebcam and mic testHeadphone testPre-stream checklist
SetupsSetup builderSetup guidesAudio routingCamera checker
SettingsBitrate calculatorUpload calculatorSettings by platformTwitchYouTube LiveKickFacebook LiveTikTok LIVE
GearAll gearComparisonsStream Deck selector
GuidesChoose your gearConnect and set upFix a problemAll guidesAll tools
AboutCorrections and contact

Search stays on this device. Esc to close.

Work out where game sound and chat go

Console party chat is an audio-routing problem layered on the HDMI video path. Decide where game audio, remote party voices and the creator microphone enter, then build a player monitor mix and a party send that excludes the party return.

A capture card receives only the signals the console sends to it. Party-chat behavior depends on the exact console, controller or headset path and current settings.

What to plan

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

  • Game audio: Determine whether it leaves through HDMI, headset/controller or both.
  • Party return: Identify how remote voices reach the player and streaming computer.
  • Creator microphone: Decide whether one mic reaches both party and stream or separate mics/routes are used.
  • Player headphones: Build a monitor mix containing game, party and stream cues without delayed duplicate voice.
  • Party send: Send creator voice and required game audio while excluding the party return.
  • OBS source: Capture the game/chat route once and label it.
  • Console setting: Verify output-to-headset/HDMI behavior with the headset connected.
  • Platform privacy: Respect current console/game chat and broadcast settings; capture hardware does not grant access.

What can catch you out

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

  • Headset switching: Connecting a headset can change HDMI audio output.
  • Analog standards: Controller chat cables and TRRS pinouts are device-specific.
  • Capture audio: Embedded HDMI audio may include game but not every chat configuration.
  • Mix-minus: Returning the party bus to itself creates echo.
  • Current console path: Recheck the exact console, headset and game after updates; keep the wiring conditional until all three carry chat in the preflight.

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: List game, party and creator voice as separate sources.
  • Step 2: With headset connected, confirm what remains on HDMI.
  • Step 3: Route creator mic to stream and party through supported destinations.
  • Step 4: Exclude party return from the party send.
  • Step 5: Record locally and ask a test participant to report echo and level while each source is active.

Chat in the controller, or through a mixer

A console may send game audio over HDMI to capture while party chat stays in a controller headset. In that case, a separate supported party route is needed; the capture card cannot invent it.

A routing mixer can combine creator voice and required sources for party and stream, but only if its bus assignments explicitly exclude the remote return from the party send.

See also the console streaming setup, and plan who hears what in the audio routing builder.

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.

  • Stream has game but no party: Party return is not present on the captured route; verify the console/headset output setting.
  • Party hears itself: Remove party return from the send and any program loopback.
  • Player loses game audio: Restore the intended headset/monitor destination and check console output changes.
  • Creator voice doubled: Two microphone routes reach OBS; keep one intentional stream source.

Test it with your party

Run the preflight with the exact console, controller or headset, capture device and chat participants. Confirm game audio, local voice and remote voices at both the creator monitor and recorded output.

Repeat after a cold start because console output settings can revert. If party chat is missing, trace its selected output path before changing the capture card.

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.

Sources