START HERE
First see whether the capture-card meter moves in OBS. A still meter points toward the HDMI source, card input, or selected device; a moving meter with a silent recording points toward OBS output mute or track selection. Hearing nothing in your headphones alone does not prove capture has failed.
Start with one known sound and one capture app
Stop the live stream and save your current scene collection before changing routes. Play a menu sound or a short clip you can repeat. Close the card manufacturer’s preview app while using OBS, and close OBS when testing the manufacturer’s app. This makes the comparison meaningful and avoids two programs competing for the same device.
Write down three results: sound from the source itself, movement in the OBS capture-card meter, and sound in a saved recording. Check the recording after stopping playback on the source so you cannot mistake live sound for recorded sound. Leave the microphone muted during this first test.
Prove that sound reaches the HDMI input
- Connect the console or gaming PC directly to a TV with working speakers. If it is silent there, fix its output selection or cable before adjusting OBS.
- Reconnect the card and compare the TV connected to its HDMI passthrough, if available. This narrows the break to the source-to-card or card-to-computer part of the route.
- For an Elgato baseline, use stereo PCM rather than a Dolby/DTS bitstream. Check your own card’s specifications before generalizing that setting to other hardware.
- Temporarily disconnect a console headset. Headsets can redirect sound away from HDMI, including on PlayStation and Switch configurations. If sound returns, choose a supported headset/capture route rather than repeatedly reinstalling OBS.
Elgato’s HDMI troubleshooting checklist documents these source-side checks. A headset microphone is a separate signal: hearing game sound does not mean party chat or your voice is also included.
Select the card’s actual audio path
Check whether the card expects HDMI audio or an analog/line input. A previous Chat Link setup can leave a supported card on analog even after the cable has been removed. Use the manufacturer’s settings for that exact model; some OBS capture properties are separate from the manufacturer app’s settings.
On Windows, open your Video Capture Device source’s properties. If its integrated audio is missing and the card exposes a separate audio endpoint, use Use custom audio device and choose that endpoint. Alternatively, capture its endpoint once with an Audio Input Capture source. Do not leave both routes active merely because both are available. macOS and Linux expose different source options, so follow the model’s platform instructions rather than looking for Windows-only fields.
Use the meter to choose the next check
| Observation | Next check |
|---|---|
| No sound in either capture app | Recheck HDMI versus analog, source format, USB connection, and the card’s driver/support utility. |
| Manufacturer app works; OBS meter is still | Close that app, reselect the card in OBS, and compare its audio endpoint and permissions. |
| OBS meter moves; saved clip is silent | Check output mute and whether the source is assigned to the recording track selected in OBS. |
| Recording is good; headphones are silent | Capture works. Configure monitoring separately if you need to listen locally. |
A Windows Video Capture Device source set to Capture audio only is not automatically played through your speakers. Changing Audio Output Mode to Output desktop audio redirects the card’s audio out of the Video Capture Device source to Windows’ default playback device instead—which silences the capture in OBS if Desktop Audio is disabled, or doubles it if both Desktop Audio and a separate Audio Input Capture source are active. Use the monitoring checklist once the recording is correct.
Verify the route before restoring the full scene
Record a short game segment with the microphone silent, then another with speech. Listen for correct left/right channels (confirming your headphones outside OBS with the stereo channel test if sound seems panned) and one copy of each sound. Switch away from the scene and back, because a source configured to deactivate when hidden may behave differently after a scene change. Reconnect your normal headset and repeat the same test.
If a fixed sound-to-picture offset remains, use a visible in-game action and the OBS sync guide. Changing sync offsets cannot repair silence or intermittent USB dropouts. If the card still fails in its own app, send its support team the exact model, OS, source device, connection path, and the first failed checkpoint above.
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.