START HERE
A capture card can carry the gaming PC’s HDMI sound into the streaming PC, but it does not automatically share every microphone and headphone between both computers. Choose where the microphone and headphones live, prove a one-way game-audio route, then add only the chat or monitoring paths you actually need.
Choose which computer owns each job
For a first working configuration, put OBS, the microphone, headphones, and Discord on the streaming PC. Send game video and sound from the gaming PC through HDMI capture. You can monitor the captured game in OBS, but this adds a listening path that may feel delayed. This is a useful baseline, not a promise of low-latency competitive-game monitoring.
If you need immediate game audio from headphones attached to the gaming PC, you will need a separate way to hear streaming-PC chat and alerts. If a microphone must feed in-game voice on the gaming PC and your broadcast on the streaming PC, that also needs an intentional split or return route. A USB microphone connected to one machine is not automatically an input on the other.
Prove game audio across HDMI
- Connect the gaming PC’s HDMI output to the capture card input. Connect the card to the streaming PC as its manufacturer specifies.
- On the gaming PC, choose the HDMI audio device associated with that connection. The device can be named after the display, card, or GPU audio driver.
- Play a repeatable game sound. In OBS on the streaming PC, add the capture device once and check its meter.
- Record a short clip before enabling chat, microphone filters, or a software mixer.
If picture works but the meter is still, use the capture-card audio checklist. Your original gaming-PC headphones may become silent when you choose HDMI as its output; that is expected until you deliberately duplicate or reroute the signal.
Add microphone and chat without capturing the monitor twice
Add the streaming PC’s microphone once in OBS, selecting its named device. Configure Discord on that same PC to use the microphone and physical headphones. Capture Discord separately if you want it in the broadcast; do not assume that hearing friends means OBS is recording them.
For this baseline, keep broad Desktop Audio capture disabled on the streaming PC and use intentional sources for the game, mic, and call. Otherwise OBS monitoring of the captured game can return through Desktop Audio, doubling a signal that OBS already has. This is especially easy to miss when the original and delayed copies are close together.
In OBS 32.1+ (and 32.2+), monitor and output-mute controls are independent (on OBS 31 or earlier, leave the mixer speaker unmuted and pick Monitor and Output or Monitor Only in Advanced Audio Properties). Set the physical headphones as OBS’s monitoring device and enable monitoring only for the capture-card game source. Leave the microphone’s monitoring off unless you have a specific reason to hear delayed speech.
Check what each audience should hear
| Signal | You hear | Stream receives |
|---|---|---|
| Gaming-PC sound | Capture-card monitoring in streaming-PC headphones | Capture-card source |
| Your microphone | Normally no software monitoring | One microphone source |
| Discord friends | Discord’s headphone output | Dedicated call capture, if wanted |
| Stream playback preview | Muted during the broadcast | Nothing |
Test the table one row at a time. Ask a friend to speak while you stay silent, then reverse roles. Mute each source in OBS and confirm that only the intended sound disappears from a saved clip. A meter moving on the wrong source reveals a duplicate or mixed route.
Improve monitoring only after the baseline works
If OBS-monitored game sound is too delayed for play, consider a hardware mixer/interface with appropriate direct monitoring or an explicit gaming-PC split to headphones and HDMI. A mixer such as Voicemeeter can send a signal to two chosen outputs, but do not add it just because a tutorial uses it; if you use Windows virtual cables on either PC, map the endpoints with the Windows & OBS routing helper first. Save the working configuration first, then change one destination and repeat your recordings.
For in-game voice on the gaming PC, design a microphone-only return. Do not send a complete stream mix back as the game’s microphone: teammates would hear their own voices, music, and alerts. The same rule applies to a call return: exclude that call’s received audio from the mix sent back to it.
MicDrop is a phone audio endpoint, not a replacement for the PC-to-PC capture transport in this setup. If you add a phone microphone on the streaming PC, treat its virtual-cable output as the one microphone source and retest it independently.
Run a rehearsal under the real workload
Record several minutes while the game is active, switch scenes, play a test alert, and mute both game and microphone in turn. Listen for doubling, missing call audio, and changes in sync. Reboot both PCs and confirm the explicitly selected devices still resolve. Keep a short written route list beside the setup; it is much faster to recover from a changed default device when every connection has a name. Once every source arrives cleanly on the streaming PC, follow how to mix your mic, game, Discord, and alerts in OBS and inspect your rehearsal recording in the live stream LUFS loudness checker.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.