A 24/7 YouTube radio stream can be silent because the music source is not reaching the encoder, the encoder is sending no audio, YouTube is reporting an ingest problem, or only one viewer has a playback fault. The quickest way to find the cause is to test the stream from the source outward.
Start by listening to the encoder's own output, then read the health messages in YouTube Live Control Room. A live picture does not prove that audio is being sent, so do not use the moving video alone as evidence that the broadcast is healthy.
Check whether the silence affects everyone
Before changing audio settings, find out whether the problem is stream-wide or local to one listener. Open the public stream on a separate device, preferably using a different internet connection. For example, compare the operator's computer on home broadband with a phone using mobile data. Ask one other viewer to listen and report whether the music is present.
This first comparison prevents a common mistake: rebuilding a working stream because one browser tab was muted. If other listeners can hear the station, check the affected viewer's volume, browser tab, device output, Bluetooth connection and YouTube player controls. Also try a private browser window or another device, since a saved browser setting can affect only one person.
YouTube's live-stream troubleshooting guidance makes the same distinction. An error reported by one viewer is more likely to relate to that viewer's computer or connection, while reports from viewers on different connections can point towards the encoder or the stream itself.
If nobody can hear audio, keep the investigation focused on the broadcast path. Do not start by replacing a microphone, mixer or cable. A radio stream may use a file player or playlist rather than a microphone, and the symptom alone does not identify a hardware fault.
Write down what each test shows. A simple note such as “encoder output silent, YouTube silent, phone silent” is more useful than changing several settings at once. If the encoder sounds normal but YouTube does not, you have already narrowed the fault to ingest, encoding or the connection between them.
Inspect the music source and audio routing
The source is the file, playlist, application or audio device that should feed the broadcast. Confirm that it is actually playing. Check the file locally from beginning to end if possible, rather than assuming that a playlist entry contains audio because it has a title and a waveform preview.
Then check where the sound is going. A music player can be audible through the operator's headphones while sending nothing to the encoder. Conversely, the encoder may be listening to a different desktop output, an unused capture device or a muted application. The important question is not “can I hear music on this computer?” but “is the same audio reaching the output selected for the live stream?”
If you use OBS, inspect the Audio Mixer while the source is playing. A moving meter indicates that OBS is receiving a signal, although it does not by itself prove that YouTube viewers will hear it. If the meter is flat, check the source's selected device, application permissions, mute state and volume. If the meter moves but the local monitoring is silent, check the monitoring device and routing separately.
For a video file, confirm that the file contains an audio track and that the player is not configured to disable it. Test another known-good file only as a diagnostic comparison. If the second file works, the original file, codec or track layout deserves attention. If neither file works, the problem is more likely to be routing or the encoder configuration.
A playlist can also stop producing audio while the video continues. The current item may have ended, the next item may be unavailable, or the player may be waiting for an input that is no longer present. Watch the source for long enough to cover a transition. Overnight channels often fail at the hand-off between items rather than during the first few minutes of a test.
If your channel is built around a repeating visual and music file, the guide on how to stream a video file to YouTube Live without OBS is relevant to the source side of the setup. It does not replace checking the actual output, but it helps separate a file-based workflow from a computer-based mixer or scene collection.
Verify audio in the encoder output
The encoder is the boundary between your source and YouTube. Listen to the encoder's own stream preview or monitoring output, and inspect its audio meters while the stream is active. YouTube specifically advises checking the look and sound of the stream directly in the encoder. This is the most useful dividing line in the diagnosis.
If the encoder output is silent, YouTube cannot restore the missing programme audio. Return to the source and routing checks. Look for a muted scene, a disabled audio track, the wrong input device, an application that has stopped playing, or a source whose volume has been reduced to zero. In a multi-scene setup, confirm that the live scene contains the audio source rather than only the video source.
If the encoder output sounds distorted, intermittent or very quiet, correct that before looking at YouTube. A local recording can help: record a short section from the encoder and play it back outside the streaming application. This can reveal whether the issue is in the source, the monitoring path or the encoded output.
If the encoder output sounds healthy but the public stream is silent, leave the source alone for the moment. Check the encoder's stream settings, its error messages and its resource load. Changing the music file at this stage can hide the original fault and make the next test harder to interpret.
You should also check whether audio is being assigned to the track that is actually sent to YouTube. Some encoder setups show activity on one track while the stream uses another. A separate audio-enable option may also be turned off. YouTube's error guidance explicitly includes cases where the encoder sends no audio and notes that some encoders have a tick box to enable it.
For long-running channels, keep the test simple. Use one known-good video or audio source, one active scene and one intended audio track. Once that combination reaches YouTube correctly, add playlist rules, extra sources or scene changes one at a time.
Read Live Control Room health messages
Open YouTube Live Control Room and look beside the stream health indicator while the broadcast is running. Health messages are more useful than a general impression that the broadcast is live because they describe what YouTube is receiving. Note the message and its timestamp before making a change.
A “no audio” message means that YouTube is receiving an ingest stream without an audio stream. Treat that as a signal to inspect the encoder's audio enablement and selected output, not as proof that the music file itself is defective. YouTube's live-stream error messages also cover multiple audio streams, unsupported codecs and incorrect audio settings.
If the dashboard reports multiple audio streams, remove unintended duplicates or make the intended track clear. An encoder can expose desktop audio, an application capture and a microphone at the same time when the channel only needs one programme feed. Extra tracks make diagnosis less certain and may create an ingest error.
If the message identifies an unsupported codec or audio configuration, follow that specific message and the encoder's documentation. For the documented H.264 ingest context, YouTube's guidance refers to AAC audio and gives 128 Kbps as a recommended audio bitrate. It also includes a 44.1 kHz sample-rate correction message. These are configuration recommendations in YouTube's error guidance, not a measurement of stream quality or a promise that changing one value will fix every silent broadcast.
A radio stream normally does not need surround sound. YouTube documents mono, stereo and 5.1 ingestion, while other channel layouts may not convert reliably to stereo. If your encoder is set to a multichannel mode, check that the source and output channel layout are intentional. For ordinary music, a deliberate stereo or mono configuration is easier to test than an accidental multichannel one. See YouTube's 5.1 surround-sound documentation if you are deliberately sending surround audio.
Correct one reported issue at a time, then allow the dashboard to update and test again. Do not change bitrate, sample rate, codec, channel layout and source routing together. If the health message changes, you will know which part of the correction mattered.
Check encoder settings and outbound connection
Once you have confirmed that the encoder can hear the source, inspect the settings used to send the broadcast. YouTube's encoder setup guide covers entering the YouTube Live server URL and stream key, then configuring the audio and video hardware or sources in the encoder.
Verify that the encoder is connected to the intended YouTube stream and that its saved stream settings have not been replaced. If you have more than one channel, scheduled broadcast or encoder profile, a correct audio configuration attached to the wrong stream will not solve the problem. Check the selected stream in Live Control Room and compare it with the destination configured in the encoder.
If the encoder has restarted, confirm that the audio source came back with it. Some applications reopen with a different output device, a muted source or an incomplete scene. A stream can therefore show video while the audio part of the workflow remains inactive. Review the encoder after any restart instead of assuming that its last state was restored.
Check encoder errors and CPU load after confirming the audio output. A heavily loaded computer may fail to process or send the stream consistently, especially when a large visual, several filters and multiple applications are running. YouTube recommends checking encoder errors and CPU usage as part of its troubleshooting process. A local archive of the broadcast can also show whether the encoded file contains audio during the affected period.
Then test the outbound connection. A connection can be sufficient for ordinary browsing but still struggle with a continuous upload. Look for dropped frames, reconnects or repeated encoder warnings. These signs do not prove that audio alone is failing, but they can explain why the public stream differs from the encoder preview.
For a separate discussion of video transport settings, see the bitrate guide for a 24/7 YouTube stream. Keep bitrate troubleshooting separate from an audio-routing diagnosis: a higher video bitrate will not create an audio track that the encoder is not sending.
If your process depends on a computer running all night, a disconnect can also leave the public channel in a confusing state. The article on restarting a YouTube live stream automatically after a disconnect covers that separate failure mode. Automatic recovery is useful only after the stream has a correct audio path; it cannot repair a silent source.
Retest playback from another viewer's connection
After making a correction, test the public watch page rather than relying only on the encoder preview. Use a second device and, where practical, a different connection. A phone on mobile data is a useful comparison with the computer that operates the channel, but it is still only a comparison, not a guarantee that every viewer has the same result.
Ask the second listener to report three things: whether the video is moving, whether the player shows an audio level or responds to volume changes, and whether any sound is present. The distinction matters. A viewer may have a working stream but no audible output because the phone is connected to a Bluetooth device, the browser tab is muted or the operating system has selected the wrong speaker.
If several viewers on different connections hear silence while the encoder output is healthy, return to the Live Control Room health message and the encoder's outgoing status. Inspect a local archive if one exists. This combination points towards the ingest or outbound path rather than the original music file, but it still does not establish that YouTube is necessarily responsible.
If only one viewer is affected, ask them to try another browser, device or connection before changing the broadcast. If all comparisons are healthy, the stream operator should not keep altering the encoder in response to one local playback report.
Keep a short test record for the next overnight run: source heard, encoder meter moving, encoder preview heard, health message, public page heard, and connection warnings. The record gives you a before-and-after comparison when the same symptom returns.
Make the next overnight test observable
A 24/7 channel needs checks that still make sense when nobody is watching the screen. Before leaving the stream unattended, start one controlled test with a known-good source. Confirm the source audio, encoder output, Live Control Room health and public playback in that order. Save the relevant settings so that a later change can be compared with a known working configuration.
Use a simple monitoring routine rather than trying to judge the whole channel by its thumbnail. A moving image can continue while the audio source is muted, unrouted or absent from the outgoing stream. The useful checks are the encoder's audio activity, YouTube's health message and a playback test from another device.
If you want to remove the need for a computer to stay on solely to keep sending an uploaded file, StreamNeo removes that specific operational burden: you upload the video, add your YouTube stream key, and the channel runs from the cloud with monitoring and automatic restart if it drops. You should still verify the audio in the uploaded file and confirm the public playback, because no hosting arrangement makes a silent source audible.
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 does YouTube show video but no sound?
The video and audio are separate parts of the ingest stream. The encoder may be sending the picture while audio is disabled, routed to the wrong track or missing from the source, so inspect the encoder output and Live Control Room health messages.
Is the problem always YouTube's fault?
No. Silence can begin in the music file, player, audio routing or encoder before YouTube receives anything. If the encoder preview is healthy, then investigate the ingest message, encoder errors and outbound connection rather than assuming the platform is responsible.
What should I check first in OBS?
Confirm that the intended source is playing, that the Audio Mixer meter moves, and that the active scene sends the expected audio track. Then listen to the encoder output and compare it with the public stream from another device or connection.
Why can one viewer hear nothing when others can?
A single report may be caused by that viewer's muted browser tab, device volume, selected output or network. Ask the viewer to try another device or connection before changing a stream that other listeners can hear.