Live Stream Silent While the Recording Has Sound? Stream Track, Monitoring and Platform Diagnosis Guide

Key takeaway
In one OBS session the live stream reaches viewers in silence while the recording of the same session plays back with sound. That split proves capture is working and the fault sits on the stream output path. The decisive checks are the stream track assignment, each source's monitoring setting, and a comparison on a separate device with another viewer.
The shape of this fault — and why the direction matters
This article is about one narrowly defined symptom, and the direction of the split is the whole point. In the same OBS live-streaming session, the stream goes out silent: viewers hear nothing, and opening the stream on a separate device or in another browser also produces no sound. But the file recorded at the same time plays back with sound. Checking the file properly means looking at it with MediaInfo to see whether it contains an audio track, and playing it in VLC while noting which track is being played and at which point in the recording — VLC plays only the first track by default, so "VLC played it" is only partial evidence unless the track and the time point are stated.
Both halves must come from the same session. A silent stream from one evening and a recording with sound from another evening are not this fault; they are two unrelated observations. When the two halves do come from the same session, the split itself is the diagnosis in outline: two outputs, one source, opposite results. Capture is working, so the fault sits on the stream output path. The rest of this guide is about finding exactly where on that path the sound stops.
The direction must not be confused with its mirror image. The mirror case — the stream has sound and the recording file is silent — is a different article, and its checks run in the opposite direction. Reading only the headline is how the two get mixed up; the premise paragraph is what separates them. Everything in this article is written for the direction stated in its title: stream silent, recording has sound.
How OBS moves sound, and where the stream path splits from the recording path
OBS has two output systems, and each one has its own track assignment. Recording can capture several audio tracks at once — OBS supports up to six — while streaming uses a single track. In the advanced audio properties, each source is assigned to tracks one by one; the recording tab and the streaming tab then each choose which track they use. The recording tab's track boxes and the source assignments have to match each other for the recording to carry sound, and the same logic applies on the streaming side: the streaming tab's chosen track has to be a track that actually carries a source. Recording being correct therefore says nothing about streaming being correct, because the two tabs are independent. A recording with sound is not proof that the settings are right overall; it is proof that the recording side's assignment is right.
The audio meter moving is the next thing that gets misread. A moving meter proves only that sound has reached the mixer. After the mixer, the sound still has to pass through the stream track assignment, the encoder output and the platform before it reaches a viewer. One external source on stream audio makes the same point: the meter moving is a checkpoint, not proof that the viewer receives sound; the encoder output settings and the track assignment have to be checked as well. A meter that moves while the stream is silent is therefore not a contradiction. It is the expected picture when the fault sits after the mixer.
Monitoring is local; output is the stream. OBS audio monitoring sends a source's sound to your own monitoring device. The setting "Monitor Only (mute output)" means you hear it and the viewers do not; only "Monitor and Output" sends it to both. Hearing sound yourself proves nothing about what the viewers hear, and it is one of the easiest mistakes in this whole area to make: the stream can be silent for everyone else while the person streaming hears everything perfectly.
A further split can appear at the source device. When OBS desktop audio is set to "Default", it follows the Windows default output, so plugging in headphones, connecting a display or pairing a Bluetooth speaker changes where the source points. When it is set to a specific device, changing headphones or speakers afterwards means the source no longer points at the right device. Because the recording has sound, this layer is less suspect in this fault — but the stream side still has to be checked independently, at the time the stream was running, rather than assumed correct because the recording worked. The two outputs can be captured at different moments, and a device change between them is exactly the kind of thing that produces a split.
Two further pieces of mechanism are worth one sentence each, and no more, because they belong to the mirror article's territory. The graphics driver package contains audio components with different jobs — HDMI and DisplayPort audio on one side, and a virtual audio device such as NVVAD on the capture and streaming side — and a component being disabled or missing can silence one path while the other stays normal. And a sample-rate mismatch can leave the mixer showing a signal while the output is completely silent or badly distorted.
The decisive forks
Fork one: the recording-file comparison
Take the recording file from the same session and check it with MediaInfo for an audio track, then play it in VLC, noting which track is playing and at which point in the recording. A file with sound means capture is working and the fault is in the stream output layer. A file without sound means this is not the article's fault at all, and the recording-silent direction should be followed instead. This is the fork that confirms the premise; without it, every later step rests on an assumption.
Fork two: the meter comparison
While streaming, look at the OBS audio meters source by source. A meter that moves means sound has reached the mixer, so the fault sits in the stream assignment, encoding or platform layer. A meter that does not move points at the source layer — but because the recording has sound, the source itself has sound, so a meter that does not move has to be investigated source by source: which meter is still, and which is moving. A single still meter must not be read as "all sources have a problem".
Fork three: the stream-track assignment comparison
In OBS, open Settings, then Output, then the Streaming tab, and note which track is selected. Then open the advanced audio properties and note which tracks each source is ticked for. If the streaming tab has selected a track that no source is assigned to, the fault is in the stream-track assignment layer. If the selected track does carry a source, the assignment layer is not the fault, and the search moves on. The two sides have to be compared against each other; checking only one side proves nothing.
Fork four: the monitoring comparison
Check the monitoring setting on each source: is it "Monitor and Output", or "Monitor Only (mute output)"? The second setting means you hear the sound and the viewers do not, which is exactly the symptom this article covers. The monitoring device itself should also be noted, because a monitoring setting only makes sense in relation to which device is doing the monitoring.
Fork five: the platform and viewer comparison
Open the stream on a separate device or browser — not through OBS monitoring — and check the platform's stream health status, and ask another viewer. If every viewer hears nothing, the fault is in the stream or platform layer. If only one viewer or one device hears nothing, the fault is on the viewer side, and no amount of changing OBS settings will fix it. This fork is what stops the fault from being blamed on OBS before the platform and the audience have been checked.
The six suspect layers
| Layer | What points at it | What argues against it |
|---|---|---|
| 1. Stream-track assignment | The streaming tab selected a track that no source is assigned to | The selected track carries a source |
| 2. Monitoring setting | A source is set to "Monitor Only (mute output)" — you hear it, viewers do not | Every source is set to "Monitor and Output" |
| 3. Mixer / mute | One source is muted in the mixer or its fader is pulled down | Every source meter moves and no source is muted |
| 4. Source device | The default device changed during the stream, or a specified device no longer matches after a headphone or speaker change | No device was plugged in or removed, and the device matches |
| 5. Driver audio component | A virtual audio device is disabled or missing, silencing one path while the other stays normal | All audio components are present and enabled |
| 6. Platform / viewer side | The platform's stream health shows a problem, or every viewer hears nothing | Another device plays the stream with sound, or only one viewer is affected |
Layer three deserves emphasis because it is the easiest to misread. The mixer has to be checked source by source. A single overall meter moving does not prove that every source is unmuted; a muted desktop audio source and a live microphone can sit side by side in the same mixer, and only the source-by-source view shows which one is silent.
Seven-step diagnosis
- Define the shape. Confirm that the fault is "stream silent plus recording file with sound" in one and the same session, not a comparison across two different times.
- Run the recording-file comparison. Use MediaInfo to check for an audio track, and play the file in VLC, noting which track is playing and at which point in the recording, to confirm that capture is working.
- Run the meter comparison. While streaming, look at each source's meter in turn, note which ones move and which do not, and write the result down.
- Run the stream-track assignment comparison. Note which track the Streaming tab has selected, and which tracks each source is ticked for in the advanced audio properties, and check whether the two sides match.
- Run the monitoring comparison. Check whether each source is set to "Monitor and Output" or "Monitor Only (mute output)", and note which device is the monitoring device.
- Run the source-device comparison. Check whether desktop audio and the microphone are set to "Default" or to a specific device, and whether any headphones, speakers or displays were plugged in or removed during the stream.
- Run the platform and viewer comparison, then stop if the layers still cannot be separated. Watch the stream on another device, check the platform's stream health, and ask another viewer. If the fault still cannot be placed, stop and bring the full set of screenshots — the streaming track tab, the advanced audio properties, and the mixer state — to the shop at Room 1209, Dali Plaza, Shek Mun, telephone 2186 8010, WhatsApp 6558 6806.
Boundary cases — when this is not the fault
- The recording file is silent too: that is the recording-silent direction, not this article.
- The recording file has sound, but the audio track disappears inside editing software while VLC plays it with sound: that is a track-mapping and codec direction, not this article.
- The recording starts with sound and goes silent halfway through: that is a mid-recording silence fault, not this article.
- The sound is there but distorted, crackling or intermittent: that is a game-audio crackling and dropout fault, not this article.
- There is no sound at all when streaming or watching videos, outside of OBS streaming: that is the HDMI and DisplayPort playback chain, not this article.
- The recording or stream stutters, the encoder is overloaded, or frames are dropped: that is a rendering, encoding or network frame-drop fault, and the problem there is stuttering, not silence.
- The encoder cannot be found at all: that is an encoder-missing fault, not this article.
- Only the microphone is silent while desktop audio is normal, or the other way round: that is a single-source layer, not a stream-output layer, and the sources have to be separated one by one rather than treated as a whole-stream silence.
- Viewers say there is no sound, but opening the stream on another device yourself produces sound: that is the viewer side, not the stream side.
- The stream is silent on a phone but has sound on a computer: that is a codec compatibility layer, not this article.
Six common mistakes
- Hearing sound yourself means the viewers hear it. Wrong. Monitoring is local and output is the stream; "Monitor Only" means you hear it and the viewers do not.
- A moving meter means the stream has sound. Wrong. A meter moving proves only that sound reached the mixer, not that it passed the stream track assignment, the encoder and the platform to reach the viewer.
- A recording with sound means the settings are all correct. Wrong. Recording and streaming are two separate outputs with their own assignments; the recording being right says nothing about the stream.
- A silent stream must mean OBS is broken. Wrong. Platform health and the viewer's own device can also be responsible; no such conclusion can be drawn before the platform and viewer comparison.
- Changing the format or reinstalling OBS will definitely fix it. Wrong. Before the layers have been separated, that is blind trial. Format affects only the recording file side; it does not affect stream track assignment.
- The microphone having sound means all sources have sound. Wrong. Desktop audio, the microphone and game capture audio each have their own track assignment and monitoring setting, and they have to be checked one by one.
Two further cautions follow from the same logic. Monitoring is a comparison, not a fix: changing a monitoring setting does not repair the stream, it only reveals where the sound is going. And switching to a different recording format is not a repair for a silent stream either — format affects the recording file, and this fault sits on the stream output path.
What is not known
Which cause is most common has no settled answer: the external sources disagree, and this shop cannot present any one cause — including stream-track assignment — as its own conclusion. The specific reasons for a platform-side silence, such as copyright handling, processing or regional restrictions, should be described as platform behaviour and not stated directly as the cause, and no percentage for platform silence can be written. One external source's guidance on a fix for the opposite direction — stream with sound, recording silent — must not be carried into this article in the other direction; only the track-assignment mechanism behind it is used.
Sources
- umatechnology.org, "Fix Stream Audio: File, OBS Mixer, and YouTube Checks" — trace the fault section by section from file to mixer to encoder to platform; a moving meter is a checkpoint, not proof that the viewer receives sound; monitoring and what the viewer receives have to be kept apart; the encoder output settings and the track assignment have to be checked together; and the platform's stream health status. http://umatechnology.org/how-to-fix-sound-files-not-working-in-your-stream/
- store.hollyland.com, "OBS Audio Not Working: 8 Fixes" — a mixer showing a signal while the output is silent points at the track settings; the monitoring setting ("Monitor and Output"); a sample-rate mismatch can leave the meter moving while the output is silent; and choosing the wrong desktop audio device. Note on direction: that site's Fix 7 covers the opposite direction — stream with sound, recording silent — and only the track-assignment mechanism is used here; its direction is the opposite of this article's direction. https://store.hollyland.com/blogs/creator-hub/obs-audio-not-working
- geekchamp.com, "How to Fix Audio & Sound Not Working in OBS" — a meter moving while the stream or recording is silent points at the track, monitoring, platform settings or a muted output; a device set to "Default" follows the Windows default output and can go wrong when headphones, a display or a capture card is connected. https://geekchamp.com/how-to-fix-audio-sound-not-working-in-obs-game-desktop-microphone-full-guide/
- techbloat.com, "How To Fix Audio & Sound Not Working In OBS" — the monitoring menu in the advanced audio properties, multi-track recording settings, and the reminder that a multi-track MKV file plays only one track in a player by default. https://www.techbloat.com/how-to-fix-audio-sound-not-working-in-obs-game-desktop-microphone-full-guide.html
Frequently asked questions
My stream is silent but the recording has sound. Is OBS broken?
Not necessarily. The split proves capture is working, so the fault is on the stream output path — run the stream-track assignment, monitoring and platform comparisons before blaming OBS.
The audio meter is moving. Why can't the viewers hear anything?
A moving meter proves only that sound reached the mixer. It still has to pass the stream track assignment, the encoder and the platform. Check which track the Streaming tab selected and which tracks each source is assigned to.
I can hear the game myself. Does that mean the stream has sound?
No. If a source is set to "Monitor Only (mute output)", you hear it and the viewers do not. Hearing it yourself is local evidence only.
The recording has sound, so my settings must be right — is that true?
No. Recording and streaming are two separate outputs with independent assignments. The recording being right says nothing about the stream tab's chosen track.
Will switching the recording format to MKV fix the silent stream?
No. Format affects only the recording file. A silent stream is a stream output problem — track assignment, monitoring, source device or platform — and changing the recording format does not touch any of those.
Only some viewers hear nothing. Is the stream broken?
If other viewers and another device of your own hear sound, the fault is on the affected viewer's side, not the stream. Ask a second viewer and test on a second device before changing OBS settings.
When should I stop testing and bring the machine in?
When the five comparisons still do not place the fault, or when the stream stays silent after the assignment and monitoring checks. Bring screenshots of the streaming track tab, the advanced audio properties and the mixer state to Room 1209, Dali Plaza, Shek Mun. The shop's published three-tier service charges are HK$400–2,800; telephone 2186 8010, WhatsApp 6558 6806.
Glossary
- Stream track assignment: which single audio track the Streaming tab uses, and which tracks each source is ticked for in the advanced audio properties.
- Monitor Only (mute output): a monitoring setting where you hear a source locally but it is not sent to the stream.
- Monitor and Output: a monitoring setting where a source is heard both locally and on the stream.
- MediaInfo: a tool that shows whether a media file contains an audio track and what its properties are.
- Stream health: the platform's own status display for an incoming live stream.