If your YouTube live stream has video but no sound over RTMP, first find the point where the audio disappears: the source, the encoder output, YouTube’s ingest, or viewer playback. Checking those points in order is more reliable than changing audio settings at random.
Start by confirming that the intended audio is selected and audible in the encoder. Then compare a local recording or encoder output with YouTube’s Live Control Room preview and the public watch page. The difference between those checks tells you which part of the path needs attention.
Map the audio path before changing settings
A live broadcast normally follows this path:
audio source → encoder input and mix → outgoing RTMP/RTMPS stream → YouTube ingest → YouTube preview and watch page
The source might be a microphone, application audio, mixer, media file, or a combination. The encoder receives that source, places it into an audio track, and sends the track alongside the video. YouTube then reads the incoming stream and makes the result available in the Live Control Room and to viewers.
A silent watch page does not prove that the original file is silent. Equally, an active microphone meter does not prove that YouTube is receiving a valid audio stream. Each stage can show a different result.
Use the following comparisons rather than relying on one indicator.
| Check | What it tells you | Where to investigate if it fails |
|---|---|---|
| Source or mixer is audible | The original input is producing sound | Source device, application audio or mixer |
| Encoder meters move | The encoder is receiving the source | Input selection, mute state or routing |
| Local encoder output has sound | The encoder can produce an audio-containing output | Output track, codec or encoder configuration |
| YouTube preview has sound | YouTube is ingesting and previewing audio | RTMP settings, audio stream and ingest health |
| Watch page has sound | The delivered broadcast is audible to viewers | Playback, YouTube processing or viewer device |
This sequence also helps with a 24/7 channel. A stream that was working yesterday may lose audio after a source device changes, an encoder profile is edited, or a media file with a different audio layout is loaded.
Confirm the audio source and routing
Begin at the source, not at YouTube. Play the intended media, speak into the microphone, or produce the application sound that should be included. Confirm that you can hear it through a direct monitor or the source application itself.
Then open the encoder’s source, mixer, or input area. Menu labels vary between encoder versions, so look for the control that selects the audio device or media input rather than searching for one exact label. The relevant control may be called an audio source, input, mixer, track, channel, or capture device.
Check these points:
- The intended microphone, application, media file, or mixer is selected.
- The source is active rather than disabled or hidden.
- The source is routed to the track being sent to YouTube.
- The source is not muted at the operating-system level, in the application, and in the encoder.
- The selected device is still connected and available.
- A media file actually contains an audio stream.
A common example is a devotional channel using a video file with music. The file can play sound in a normal media player while the encoder is configured to capture a different desktop or system-audio input. In that case, YouTube is not the first place to troubleshoot. The encoder is receiving the wrong source.
The same distinction matters for a local news loop. If the presenter’s voice is audible in the production software but not in the outgoing mix, check whether the microphone is routed to the programme output rather than only to a private monitoring bus.
YouTube’s live-stream troubleshooting guidance also points to the audio and video sources routed to the encoder when the stream has quality problems. Keep a note of what the source is meant to be, especially if the channel runs unattended overnight.
If you are building a pre-recorded channel rather than capturing a live production, the workflow in how to stream pre-recorded video to YouTube Live from a cloud server is useful for separating the media file from the live ingest stage. It does not remove the need to verify the file’s audio track.
Check mute state and encoder audio meters
Once the source is playing, watch the encoder’s audio meters. They should respond when the source produces sound. A moving meter normally shows that the encoder is receiving some signal, but it does not by itself confirm that the correct track is being sent to YouTube.
If the meter is completely still, work backwards:
- Produce a definite sound at the source, such as speech or a short media passage.
- Check the source’s own volume and mute controls.
- Check the operating system’s selected input and input permission, if relevant.
- Check the encoder source mute and track assignment.
- Check whether another source is selected instead.
- Restart or reconnect the source only after recording what was changed.
Avoid raising every volume control at once. A level that is too low can be difficult to hear, while a level that is too high can distort. The immediate question is whether a signal reaches the intended encoder track, not whether the meter is as large as possible.
Look for more than one mute control. Some encoders have a mute for the source and another for the programme mix. A scene, profile, or output may also have a separate audio-track assignment. The names and layout differ by software version, so use the concepts rather than assuming your screen will match a guide made for another release.
If the source meter moves but the programme or output meter does not, the problem is likely between input and output routing. If both move but a recording is silent, inspect the recording track and output configuration next.
For channels that use a mixer, test with the simplest route available. Temporarily send one known source to one output track. Once that works, add other sources one at a time. This avoids trying to diagnose a microphone, media file, desktop capture, and mixer bus simultaneously.
Test the local encoder output
The next question is whether the encoder itself can produce sound before YouTube receives anything. If the software offers a local recording, preview output, or archive, use it for a short test and play the resulting file in a separate media player.
A local file with sound indicates that the encoder has produced an audio-containing output. It does not prove that YouTube will accept its codec, sample rate, channel count, or stream layout, but it moves the investigation further along the path.
A silent local file points upstream of YouTube. Check the source, routing, mute state, output track, and the encoder’s recording profile. If the encoder preview is silent as well, there is little value in changing the YouTube event settings yet.
If the local recording has sound but the encoder’s monitoring headphones do not, distinguish monitoring from programme output. Monitoring may be disabled, routed to another device, or controlled by a separate volume setting. The recording is more useful for checking what the encoder actually wrote than headphones alone.
YouTube recommends checking a local archive when a live stream has audio or video problems. Its streaming tips also advise verifying that the archive file is being created and that its size is growing. For a 24/7 channel, this is worth checking during a controlled test rather than discovering after a night of silent playback.
Keep the test short and representative. If the planned channel uses music, speech, or ambient sound, include those kinds of audio. A test with a microphone cannot confirm that a long video file’s audio track is being handled correctly.
Compare the local output with YouTube’s preview
If the local output contains sound, open the YouTube Live Control Room and compare its preview with the same test. You are now testing the hand-off from the encoder to YouTube rather than the original source.
There are several possible outcomes:
- Local output is silent and YouTube is silent: investigate the source and encoder first.
- Local output has sound but the YouTube preview is silent: investigate the outgoing audio track, format, and ingest messages.
- YouTube preview has sound but the public watch page is silent: compare playback devices and the delivered broadcast, then check the archive.
- The preview and watch page work for some viewers but not one viewer: investigate that viewer’s device, browser, volume, or connection.
The preview is useful, but do not treat it as the only evidence. Check the public watch page where possible, preferably from a separate device or connection. The dashboard and the viewer-facing page are different points in the delivery path.
YouTube’s official troubleshooting material distinguishes an issue affecting one viewer from reports across different networks. One viewer’s silence can be local playback trouble; silence reported by viewers in different places is more consistent with a stream, encoder, or delivery problem.
A local archive can add another comparison. If the archive has sound, the preview is silent, and the watch page is silent, the loss is likely occurring after local encoding and before or during YouTube ingest. If the archive and preview have sound but the watch page does not, examine the viewer-facing playback and the timing of the test.
For a channel that must remain available overnight, write down the result of each check. A small table with the test time, local result, preview result, watch-page result, and dashboard message prevents repeated work when the issue returns.
Check stream health and encoder settings
When local output has sound but YouTube does not, read the Live Control Room health messages before changing individual fields. YouTube’s live-stream error messages include audio-related cases such as no audio stream, multiple audio streams, unsupported codecs, incorrect sample rate or bitrate, and too many channels.
The exact message matters. If YouTube reports that the encoder is sending no audio, check that an audio stream is enabled and assigned to the outgoing broadcast. If it reports multiple audio streams, remove the unwanted track rather than adding another. If it identifies a codec, sample-rate, bitrate, or channel problem, correct that named setting and test again.
For a straightforward stereo RTMP or RTMPS stream, YouTube lists AAC or MP3 as supported audio codecs and recommends one AAC audio stream at 44.1 kHz and 128 Kbps. These are platform recommendations for a simple stereo setup, not a guarantee that every encoder profile will behave identically.
YouTube’s encoder guidance also lists 48 kHz for 5.1 surround and 384 Kbps for 5.1. Five-point-one audio over RTMP or RTMPS is supported only with AAC. If you are not deliberately producing surround audio, a simple mono or stereo configuration is easier to inspect. Follow the specific Live Control Room message when your setup has a different requirement.
Check the outgoing profile, not only the input. An encoder can receive audio while its streaming output has no audio track, has more than one track, or uses a different format from the local recording. Look for controls relating to stream audio, output track, codec, sample rate, bitrate, and channel count.
Do not assume that a larger bitrate or a different sample rate will cure silence. Audio that is absent is not fixed by making an existing stream more generous. First establish that one valid audio stream is present, then use the supported settings for the intended channel layout.
YouTube also recommends checking encoder errors and CPU load. If the encoder is overloaded, it may fail to deliver the stream consistently even though a local test looked normal. Check the outbound connection as well. YouTube’s operational guidance recommends leaving about 20% upload bandwidth headroom beyond the total stream bitrate. If you send primary and backup streams, that headroom needs to be considered for both.
For broader video-side checks, the YouTube Live bitrate calculator by resolution and frame rate can help you examine the total stream budget. It will not diagnose a muted audio track, but an overloaded connection can make a healthy-looking test unreliable.
Isolate source, routing, ingest, or playback problems
At this stage, reduce the setup to one known source and one audio track. Use a short test with a clear voice or a licensed media passage, record it locally, and watch the YouTube preview. Make one change at a time and record the result.
A useful isolation order is:
Test the source
Play or speak directly into the source and confirm that it produces sound. Replace a complex source temporarily with one simple source. If the simple source works, return to the original media, mixer, or application and inspect that route.
Test the encoder mix
Confirm that the encoder meter moves and that the programme output contains the source. If the input meter moves but the output does not, the likely area is track assignment, mix routing, or a mute control.
Test the outgoing format
Use one audio stream, a supported codec, the intended sample rate, the intended channel count, and a bitrate appropriate to that layout. For a simple stereo baseline, YouTube’s recommended AAC settings are 44.1 kHz and 128 Kbps. Recheck the dashboard after applying the change.
Test delivery
Compare the local file, Live Control Room preview, watch page, and reports from more than one viewer or network. If only one viewer has no sound, inspect that device before rebuilding the stream. If the problem is consistent across the preview and viewers, return to ingest health, encoder output, and connection checks.
Test unattended operation
Run a private or unlisted test if appropriate, then leave it running for enough time to represent the real use. Check that the local archive continues to grow, the preview remains audible, and the watch page plays sound. For a continuous channel, a short successful start-up test is useful but cannot show what happens after a source disconnects or a profile changes.
If you operate a church, devotional, or local information stream, also check the related failure modes rather than treating every problem as audio. For example, the guide to fixing a church YouTube live stream that keeps disconnecting in India deals with connection stability, which can sit alongside an audio configuration issue.
If the encoder output and settings are correct but the problem continues, YouTube’s guidance suggests considering a different encoder or contacting YouTube support. That is a later step, after you have preserved the dashboard message and recorded which comparison points passed.
For a file-based YouTube-only channel, moving the job away from a personal computer can remove the particular failure of a sleeping, restarting, or disconnected home machine. StreamNeo removes that operational chore by taking an uploaded video, a YouTube stream key, and the unattended broadcast out of the local computer, while you still need to check the source file and YouTube playback.
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 audio?
The audio may be missing from the encoder output, absent from the outgoing RTMP stream, rejected because of its format, or lost between ingest and playback. Check the source, encoder meters, local recording, YouTube preview, and watch page in that order.
What audio settings should I try for a basic stereo RTMP stream?
YouTube lists AAC or MP3 for RTMP or RTMPS audio. For a simple stereo baseline, its guidance recommends one AAC stream at 44.1 kHz and 128 Kbps. Follow the exact Live Control Room error if it identifies a different problem.
The encoder meters move, so why is YouTube silent?
A moving input meter only confirms that the encoder receives a signal. The output may use another track, contain multiple tracks, or contain no audio stream at all. Test a local recording and inspect the outgoing audio configuration and YouTube health messages.
Could only one viewer have no sound?
Yes. If the preview and other viewers have audio, check that viewer’s device volume, browser, player mute state, and connection. If viewers on different networks all report silence, investigate the encoder output, YouTube ingest, and stream health instead.