Game audio is audible in the stream but missing from the recording: where to look for the cause

The symptom and where it comes from

Streaming and recording follow different paths across the streamer — platform — archive chain. The platform receives the mix you send from the encoder and builds the archive itself. The local recording is made by the same encoder, but according to its own rules. If game audio is present in the stream and disappears from the recording, that means the mixer is working, but two other links diverge: the set of tracks when the file is saved, and which output device physically delivers the sound.

Hence two main scenarios: either the wrong set of audio tracks is selected for the recording, or game capture goes through a device that doesn't make it into the recording. Below is how to tell one from the other.

First check: which tracks are being written

Open the recording properties in the encoder. In OBS this is "Settings → Output → Recording" and the audio track selection field. Each checkbox is a separate track in the file. Players and editing programs play the first one by default, while the others sit alongside in silence. If your game goes to track 2 but only track 1 is checked, everything sounds in the stream (the overall mix goes there), but the game is missing from the file.

Check which tracks the file actually contains: OBS has recording stats, and any player with audio stream selection will show the list. If there are several tracks but only one plays — the cause is found.

How to spread sources across tracks

In "Advanced Audio Properties," each source has a track number. Game — one, microphone — another, alerts — a third. This scheme is convenient for editing, but it requires all the needed tracks to be checked for recording. A common mistake: you set up separation for editing but forgot the checkboxes in the output.

• Check all the tracks you want to see in the file in the output.
• Put the game and microphone on separate tracks so you can adjust the balance later.
• Verify with a 20–30 second test recording using actual game audio, not music from a browser.

The downside of this approach: files get bigger, and some players and platform uploaders only take the first track. If you upload the recording somewhere directly, without editing, it's wiser to record the mix on a single track.

Output device and audio capture

If the tracks are in order, look at where the encoder gets game audio from. Desktop capture with audio, application capture, and a separate output device are different mechanisms with different behavior.

Application capture

Works when the game sends audio to a separate stream. With some games and launchers, audio goes through the system mix, and application capture doesn't see it. Then the source is there in the mixer, the indicator moves, but the file is silent.

System audio

More reliable, but it pulls in everything: notifications, browser, voice chat. You'll have to clean up the excess with filters or mute other apps during the stream.

Virtual device

A flexible option: the game outputs to a virtual cable, and the encoder listens to it as a separate source. Setup takes longer, but the game doesn't get mixed with everything else. The downside is that when you change the output device in the system or after a driver update, the route breaks and the sound disappears again.

Monitoring: you hear it, but the recording doesn't

A separate trap is monitoring. You enabled source listening, the sound goes to your headphones, and it seems everything is fine. But monitoring is a branch to your headset, not a guarantee that the sound made it into the recording mix. Go by the mixer indicators on the sources, not by what you hear yourself.

The reverse situation happens too: the source indicator moves, but it's not in the recording mix because the source isn't assigned to a track or is set to zero in the mixer.

Platform archive and local recording are not the same thing

The platform archive is built from the stream you sent and usually mirrors the live broadcast. The local file is written by the encoder independently. So "it was in the stream, it was in the platform archive, but it's missing from my recording" is almost always local output settings, not the platform. And vice versa: if it's specifically the platform archive that's missing audio, check the audio bitrate, codec, and channel stability.

What to check step by step

1. Make a short test recording with game audio and open the file in a player that lists tracks.
2. Compare the tracks in the file with the checkboxes in the output settings.
3. See which source is responsible for the game in the mixer and whether its indicator moves during recording.
4. Check which device the game itself outputs audio to.
5. Mix everything down to a single track and record again — this separates the track problem from the capture problem.

Prevention

Keep a separate encoder profile for recording and for streaming if the tasks differ. Before an important stream, do a half-minute test recording and listen to it in the same player you'll use later. After driver and encoder updates, recheck the audio route: settings may persist while devices change.

And don't rely on what you hear in your headphones: the only reliable test is to listen to the finished file the way a viewer will hear it.