A YouTube Live loop stream with no sound can be silent at the viewer, in the media file, in the encoder, or between YouTube and the viewer. To find where, compare the sound at each stage before changing settings; a fix for one silent leg will not repair another.
If you are asking, “YouTube Live loop stream has no sound: how to fix it”, start by checking whether the problem affects one viewer or several, then test the source, encoder output and YouTube preview in order. The result tells you what to investigate next without assuming a particular file, OBS setup or audio-track arrangement.
First check what the viewer is hearing
Ask a viewer to check that the YouTube player is not muted and that the device volume is up. Then open the stream on a second device or browser, ideally on a different internet connection. If only one person cannot hear it, begin with that person’s player, device and connection rather than changing your broadcast settings.
YouTube’s live-stream troubleshooting guide makes this distinction: a report from one viewer points towards that viewer’s computer or connection, while reports from people on different connections make an encoder problem more likely. This is a useful first split, not proof of the cause. Several people may share a playback issue, and an encoder can fail even if only one person has reported it so far.
Record what each person tested: device, browser or app, and whether another video plays with sound. You do not need to collect private account details. You need enough information to distinguish “this stream is silent everywhere” from “this stream is silent here”. If the symptom is confined to one viewer, have them check the player’s mute control, reconnect, and try a different playback route before you alter the live setup.
Check the loop file or playlist
Play the exact file locally, using headphones or speakers you know are working. Listen to a section that should contain sound; some videos include a quiet introduction, a long pause or a soundtrack that begins later. If the local file is silent at that point, the encoder cannot supply audio that is not present in the media.
If the file plays with sound, confirm OBS or your other encoder is using that exact file. A similarly named export or an older version can look right in a playlist while containing a different audio mix. For a playlist, check each item, not only the first one. Note whether sound is absent throughout or only for particular entries or sections.
In OBS, a Media Source plays a selected file and can be set to loop. A VLC Video source can play a playlist, loop it and select an audio track. OBS documents these options in its Media Source and VLC Video guide. Looping controls whether playback repeats; it does not create an audio track, prove the selected track contains sound, or guarantee that the source is routed to the stream.
If you have a known-good copy of the file, compare that locally with the version loaded into the scene. Keep the original unchanged while testing so you can return to the current setup. When a continuous channel is built around recorded services or music, its media workflow matters as much as the broadcast settings; the guide to running a continuous stream of recorded services offers context on that kind of source-based channel.
Read the encoder’s audio meters and source state
With the loop playing, look at OBS’s Audio Mixer. Find the meter for the expected source and watch it during a part of the file where you heard sound locally. A meter that does not move suggests the source is absent, silent, assigned to a different scene, or not being captured by the selected device. It narrows the search; it does not by itself identify which of those explanations applies.
If the meter moves, audio is reaching that mixer input. Check that its speaker or mute control is not muted and that the source is on the active scene. Do not treat monitoring as proof that viewers receive sound: monitoring lets you listen through the configured monitoring device, while the outgoing stream has its own routing and track selection. OBS explains the mixer controls in its audio mixer guide.
The next check depends on the source type. For Media Source, confirm the file path and that playback is advancing. For VLC Video, confirm the playlist entry, playback and chosen audio track. OBS’s VLC source documentation identifies track 1 as the default, but a different file may place audio elsewhere. Change a track only when the source evidence suggests the current selection is wrong, then listen again locally and watch the meter.
If the stream takes audio from desktop capture or a microphone rather than the media source, check the input device. In OBS, Settings → Audio lets you select devices; a default device may not be the one currently carrying sound. OBS’s Quick Start guide recommends checking mixer activity and selecting devices manually if needed. For a device-based input, avoid capturing the same microphone or headset both globally and again as a scene source unless you have a specific reason: that duplication can create echo, although it is not the usual explanation for total silence.
Check mute, monitoring and track routing
A moving meter confirms activity somewhere in OBS, but the source still needs to be included in the audio output sent to YouTube. Open the source’s Advanced Audio Properties and confirm which track it is assigned to. Then check the encoder’s streaming or output settings to see which track is selected for the live stream. When you use separate tracks for recording and streaming, the loop’s audio must be present on the one being sent.
This is a common point of confusion when you can hear a source in OBS but not on YouTube. Listening through monitoring and hearing audio in a local player are separate from sending that audio on the correct output track. Compare the selected streaming track with the source assignment rather than ticking every track at random. OBS’s guide to multiple audio tracks explains track assignments; ordinary playback software may also play only one track, so a recording can appear silent if you inspect a different track from the one containing the sound.
Use a short test recording to verify the result after any routing change. If possible, record the same scene and audio configuration used for the live stream, then listen to the recording in a normal media player. A test recording is useful evidence, but it is not a substitute for checking the stream’s own track selection: the recording and stream may use different tracks.
Change one setting at a time and note what changed. If you toggle mute, move a source between tracks and switch devices all at once, a successful result will not tell you which change mattered. If the setup has been working and silence started after a scene or device change, compare the current source and track assignments with the last known working state.
Inspect YouTube’s ingest and preview
Once the source meters and output routing look right, inspect the stream in YouTube Live Control Room. Check the encoder preview, stream-health status and any error message while the test is active. YouTube’s health-status documentation lists noAudioStream for an ingestion feed with no audio stream, although YouTube requires exactly one audio stream. That message is more useful than guessing that YouTube has muted a correctly configured source.
Read the exact status and act on the problem it identifies. YouTube also reports audio codec or settings issues; those call for checking the encoder’s audio output format, not for repeatedly changing an unrelated file or viewer volume. Its live encoder settings guidance documents AAC or MP3 audio for RTMP/RTMPS, with 44.1 kHz for stereo and 128 kbps stereo among its recommended settings. Treat these as format checks when the encoder or health message points to configuration, not as a general cure for a muted or missing source.
Compare the preview with a local recording of the same output. If both are silent, return to the source, track and encoder path. If the recording contains sound but the preview does not, inspect the streaming output track and encoder status. If preview and recording both sound right but a viewer still cannot hear audio, test on another viewer device and connection before making further encoder changes.
YouTube’s troubleshooting guide also recommends checking encoder audio, the local archive and dashboard errors. The order matters: a preview or health message can show that the incoming signal is wrong, while a local recording can help isolate the encoder’s own output. Neither observation alone establishes that every viewer’s playback path is healthy.
Test playback and the viewer connection
If the encoder output and YouTube preview have sound, test the public stream from another device. Check the player’s mute state, device volume and audio output destination. Bluetooth headphones, a connected display or a device’s selected speaker can take sound somewhere other than the speaker the viewer expects. Try headphones or the built-in speaker you already know works before concluding that the broadcast is silent.
If the second device works but the original does not, focus on the original device’s browser or app, audio output and connection. Reloading the player or trying another browser can separate a stuck playback session from a channel-wide issue. If the stream is silent on multiple independent viewers while the preview and recording are audible, compare the public playback again and check YouTube’s current status and stream-health messages; do not assume the cause without evidence.
A slow or unstable connection can disrupt playback, but a connection problem is not the same as an audio source with no track. YouTube’s guidance distinguishes poor encoder output from a healthy encoder with outbound network trouble. If audio is present in your output evidence but delivery varies by viewer, test the connection on the sending side and ask affected viewers to test their own connections. Avoid changing audio codec or bitrate simply because one person has a playback problem.
For a channel that must continue through a local internet outage, stream continuity is a separate question from audio routing. The guide on making a YouTube replay stream survive an internet outage covers that resilience problem; it should not be treated as a fix for a silent source or track.
Narrow down the silent leg before changing settings
Use the first stage where the sound disappears to choose the next check. The table is a diagnostic map, not a guarantee: several faults can coexist, and a result should be repeated with the same media section and scene wherever possible.
| Checkpoint | What you observe | Next place to investigate |
|---|---|---|
| Local media player | The file is silent where sound is expected | File, mix, selected playlist item or source audio track |
| OBS mixer | No activity while known-audible media plays | Active scene, source selection, file playback or device capture |
| OBS mixer | Activity moves, but test recording is silent | Mute, source routing, recording track or output configuration |
| Test recording | Audio is present, but YouTube preview is silent | Streaming track, encoder output and Live Control Room health |
| YouTube preview | Audio is present, but multiple viewers report silence | Public playback and delivery path; gather another device and connection test |
| One viewer device | Other viewers hear the stream | That viewer’s player, audio output, browser or connection |
Before changing anything, write down the result at each checkpoint and the precise section of the loop you tested. “Meter moves” is more useful than “OBS looks fine”; “preview plays sound on another device” is more useful than “YouTube seems okay”. A short note of the source, active scene and selected track makes it easier to undo a test and prevents a long-running channel from accumulating unexplained changes.
If you need to test a change while the channel is live, choose a low-risk moment and tell anyone monitoring the channel what you are testing. Do not replace files, reset all audio settings or change several tracks at once before you have a baseline. If the stream is scheduled or has a regular audience, a brief controlled test may be less confusing than repeated unexplained interruptions. For another operational reference, the guide to scheduling a YouTube Live stream that plays videos automatically discusses preparation for a file-led broadcast.
When the persistent problem is keeping a local computer and its playback running through the night, rather than tracing a specific silent track, StreamNeo removes that particular operating burden: you upload the video and provide the YouTube stream key, then the channel can continue with your computer switched off. It does not replace checking that the media itself contains the intended audio or that the viewer can play it.
If your tests point instead to continuous playback being difficult to maintain on a local machine, compare the operating options before rebuilding the setup.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Why can I hear it in OBS but not on YouTube?
You may be hearing the source through OBS monitoring while its audio is not assigned to the track selected for streaming. Check source mute and track assignment, then compare a short recording with the YouTube preview and its health message. If those outputs contain audio, test the public player from another device before changing the source.
Does enabling Loop add sound to a video?
No. Loop repeats playback; it does not add an audio track or select a track that the file does not contain. Play the exact file locally and check the source’s audio-track selection before looking for an encoder fix.
What does noAudioStream mean in YouTube Live Control Room?
YouTube’s health-status documentation uses noAudioStream when the ingestion feed contains no audio stream, even though it must contain exactly one. Check the encoder’s outgoing audio track and its configuration, then follow the specific health message shown for your stream.
What if only one viewer reports silence?
First check the viewer’s mute control, device output, browser or app, and connection. Ask them to test another device or browser and compare with someone on a separate connection; do not change a healthy encoder based on a single playback report.