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.
Play at 4K60 on your TV while streaming in 1080p60
Elgato Game Capture Neo
Use its HDMI output to play on your TV in 4K60 HDR and its USB output to capture up to 1080p60. Choose another card if you need to stream or record in 4K.
Connections & full profile →An external capture card for console streaming
Elgato Game Capture 4K S
Select a listed capture mode and a separate listed display mode. If HDR or high refresh is essential, match both exact modes before choosing this card.
Connections & full profile →High-refresh HDMI capture on a fast direct USB port
Elgato Game Capture 4K X
Use a 10 Gbps USB port to get every mode. On a 5 Gbps port, pick one of the lower capture modes, or use a faster port, before buying it for high resolution.
Connections & full profile →Two XLR voices and two headphone mixes in a compact interface
Elgato Wave XLR Pro
Plug your streaming computer into the main USB socket. Keep the second USB socket for the other device, and set up what each one hears separately.
Connections & full profile →HDMI capture and a microphone input in one box
RØDE Streamer X
Set capture output separately from the display passthrough mode. Configure the audio returns before going live so HDMI audio and computer loopback do not reach OBS twice.
Connections & full profile →Two people in the room, plus a remote guest and computer sound
RØDE RØDECaster Duo
Assign the stream, headphones and guest return explicitly. Exclude the guest’s own voice from their return, then record a call to check the mix before going live.
Connections & full profile →