A pre-recorded YouTube Live stream with no audio in OBS is usually best diagnosed by tracing the signal from the video file to the OBS mixer, then to the stream output and YouTube preview. Check each point in that order; a moving mixer meter shows that OBS has received a signal, but does not prove that viewers can hear it.
Start with a short test, not a long live broadcast. Play the file locally, watch its source meter in OBS, make a brief recording and listen back, then check a YouTube preview or test stream. The point where the sound disappears tells you which part of the signal path to investigate.
Check the source file first
Before changing OBS settings, open the exact video file you intend to stream in a local media player. Play a part where you expect sound. If you cannot hear it there, OBS cannot restore audio that is absent from the selected file or audio track. Check that the player is not muted and try another point in the video, since an opening slate or quiet passage can be misleading.
If the file is silent throughout, check whether it contains an audio track and whether the intended track is selected in your player or editing workflow. Do not assume the file is corrupt: the audio may be missing, may be on another track, or may simply not be present in the portion you tested. Compare it with a known-good clip if one is available. If the known-good clip has sound, you have narrowed the issue to the original asset rather than the whole OBS setup.
OBS Media Source supports common video formats such as MP4, MOV, MKV, AVI and WebM, as well as audio formats including MP3, AAC, OGG and WAV. Format support does not guarantee that every file has a usable audio track. The OBS Media Sources guide explains the source and its file and playback properties.
If the content is intended to play continuously, first confirm that this specific file has audio before testing the complete playlist or loop. The distinction matters for devotional music, lofi, podcast and local programming channels: a silent introductory clip can make a healthy stream appear broken, while a missing track in the main programme needs to be corrected at the source. For playlist planning, the guide to building a 24/7 devotional music stream can help you think through the content workflow, but it cannot replace checking each file you actually use.
Watch the Media Source mixer meter
Once you have established that the file plays with sound locally, check the corresponding source in OBS. Select the scene that contains the video and identify whether it is a Media Source or a VLC Video source. Confirm that the intended file is selected and that playback is active. If the source is hidden, inactive or not playing, its sound may not be reaching the mixer as expected.
While the clip plays through a part with audible content, watch the Audio Mixer meter for that source. OBS describes its meters as indicators of source audio level. If the Media Source meter stays still, the signal has not appeared at that mixer input. Recheck the file, playback and source properties, including the selected audio track if you are using VLC Video. A still meter is a useful clue, not a diagnosis on its own.
If the meter moves in time with the clip, OBS is receiving audio at the mixer. That shifts attention to mute state, output track selection and the final stream preview. Do not treat meter movement as proof of audible YouTube output: monitoring, recording and streaming can follow different routes. The OBS Audio Mixer guide covers the mixer meter, mute and monitoring controls.
Make sure you are watching the meter for the source that actually plays the clip. A scene can contain several audio sources, and movement from Desktop Audio or a microphone does not demonstrate that the Media Source is producing sound. If you have scenes for a holding screen and the main video, test the scene that will be on air, not only a scene that happens to show activity. This distinction is useful when you are using a holding screen between videos: the screen and the programme may not use the same sources.
Inspect mute and source audio settings
With the clip playing, inspect the Media Source row in the Audio Mixer. Check that it is not muted. If the meter moves but the source is muted, the signal is visible in OBS while the muted mix is not sent as audible programme audio. Check the mixer again after changing the control; avoid making several unrelated changes at once, because that makes it harder to tell which one resolved the issue.
For a VLC Video source, confirm that its selected audio track is the one containing the sound. A video can play normally while the wrong audio track is selected. If the source is a standard Media Source, recheck its chosen file and playback state rather than adding unrelated capture sources in the hope that sound will appear.
The mixer’s Monitor control is separate from the stream output. Monitoring routes audio to the device OBS is configured to use for listening. Hearing sound there tells you that monitoring is working, but it does not establish that the same sound is included in the encoded stream. Conversely, not hearing monitoring does not by itself prove that the stream mix is silent. Use the meter to see whether the source is reaching OBS, then use a recording or YouTube-side test to check what leaves OBS.
If the sound really comes from another application or an external device, rather than from the video file itself, then investigate the appropriate capture source. OBS documents Audio Input and Audio Output Capture for capturing a chosen device into a scene on Windows and macOS; Linux workflows use sources such as ALSA or PulseAudio. The OBS audio sources guide describes those routes. They are not automatically needed for audio embedded in a Media Source file.
Take care not to capture the same device both as a scene source and through the global audio selection in Settings → Audio. OBS notes that duplicating a device this way can cause echo. For a file playing inside a Media Source, adding Desktop Audio as a reflex can introduce another source without fixing the actual missing signal. First establish where the file’s own audio disappears.
Confirm the stream output includes audio
After confirming an unmuted source and a moving meter, inspect the audio output or track configuration used for streaming. Do not infer the stream mix from what you hear on headphones or from the settings used for a local recording. OBS can route audio across tracks; the stream output must include the intended source mix on the track it sends.
The exact controls and available options can depend on the OBS version and setup, so verify the active streaming configuration rather than copying a track number from advice written for another workflow. In particular, do not assume that a separate recording track is also the track being sent to YouTube. The OBS multiple audio track recording guide explains why track choices matter for recordings and ordinary playback.
If you are diagnosing a saved OBS recording or an archived file that sounds silent, consider whether the audio was assigned only to a different track. Standard video players generally play one audio track at a time, and OBS advises putting all sources on track 1 when a recording is intended for normal playback without editing. That is a recording playback check, not a universal instruction to choose an exact streaming track. For the live broadcast, inspect the actual stream output selection.
Keep the test simple: use one known-audible clip and confirm that its source is included in the output mix. If the clip is intended to have music and spoken introductions, test both rather than relying on one passage. For an ongoing Telugu devotional radio channel, for example, a short test can include the kind of bhajan and voice segment that will actually be broadcast. That makes it easier to spot a source-specific routing issue before a long session.
Record and listen before going live
Make a short local OBS recording while the representative clip plays. Stop the recording, open it in an ordinary player and listen to the result. This checks more than the mixer meter: it tests whether the recorded output contains audible sound. If the recording is silent but monitoring sounded normal, revisit track assignment and the recording output configuration. If the recording has sound, that is useful evidence, but it still does not prove that the YouTube stream output has the same routing.
Listen with the same care you would give the final programme. Check a section near the beginning and another where the content changes, such as a transition from instrumental music to a spoken announcement. Listen for the intended programme audio, not just any noise. If the recording plays only one track, make sure the intended mix is available to a normal player; when editing multi-track recordings, check the other tracks in an editor as well.
Next, run an OBS test stream or YouTube preview using audio and movement similar to the planned broadcast. YouTube recommends testing with representative audio and motion before going live, and its encoder settings help lists AAC or MP3 as supported audio codecs for RTMP/RTMPS encoder settings. Check what the YouTube-side preview actually plays and review the stream health information. The final check is whether the output reaching YouTube is audible, not whether a local meter moved.
If YouTube’s preview has sound but a later replay does not, compare the replay with the local test recording and review the output and archive settings used for that broadcast. If both preview and replay are silent while the local recording is audible, return to the stream-specific output routing. Keep the checks tied to what you observe: silence only in one destination is different from silence in the source file and every output.
Isolate source problems from output problems
Use the first place where sound is missing to choose the next check. The table is a compact way to keep the diagnosis specific instead of changing several settings at once.
| What you can hear or see | Likely point to inspect | Next check |
|---|---|---|
| The file is silent in a local player | Source file or selected audio track | Test another passage, verify the track, or compare with a known-good file |
| The file plays with sound locally, but its OBS source meter stays still | OBS source selection or playback | Confirm the scene, file, playback state and VLC audio-track selection if relevant |
| The source meter moves, but the local test recording is silent | Mute or recording track/output | Check mute and the recording’s track assignment; test playback of other tracks if needed |
| The local recording has sound, but YouTube preview is silent | Stream output routing or stream test | Inspect the actual streaming audio output and repeat the YouTube-side check |
| The preview is audible, but the replay is silent | Archive or playback track selection | Compare the replay with the test recording and inspect which audio track the player uses |
These are diagnostic branches, not guarantees. A meter that moves establishes that a signal is reaching that mixer source; it does not establish that the source is included in a particular recording or stream output. Similarly, one audible local recording does not rule out a separate stream-routing problem. Confirm each destination you intend to use.
If audio comes from a separate application, external mixer or device, follow that route only after you have established that the file itself is not the source. Check the selected capture device and the operating system’s input or output level. On Windows and macOS, the relevant OBS scene capture source is generally an Audio Input or Audio Output Capture; on Linux, use the appropriate ALSA or PulseAudio source. Avoid duplicate capture of the same device if it creates echo. This conditional branch is different from embedded media audio, where the Media Source itself should supply the sound.
For a 24/7 channel, keep a small preflight routine alongside the file or playlist: play a representative section locally, confirm the correct OBS source meter moves, record and listen to a short sample, and check a YouTube preview before relying on the setup. If continuous operation is the wider concern, the article on choosing a cloud stream for one playlist discusses that separate operating decision. It does not change the need to verify that your source and YouTube output carry the sound you expect.
Where the preflight keeps breaking because the broadcast depends on a computer being left on or someone restarting a dropped session, StreamNeo can take the uploaded video and YouTube stream key and run the file-based broadcast while your computer is off, so that operational burden is separate from diagnosing OBS audio. It is YouTube-only; check your own content and output before relying on any workflow for a live channel.
If the file and channel are ready, compare the operating choices before committing.
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 is the OBS audio mixer not moving when my video plays?
The video can play while its audio signal is absent, the wrong file or scene is selected, playback is not active, or the source is using the wrong audio track. Play the same file locally first, then check the meter for the specific Media Source or VLC Video source while an audible section plays.
The meter moves, but YouTube has no sound. What should I check?
Check that the source is not muted and that the audio mix is included in the stream output. Then run a representative YouTube preview or test stream and listen there. Meter movement alone does not establish that the stream output includes audible audio.
Should I add Desktop Audio to fix a silent Media Source?
Not if the sound is embedded in the file playing through Media Source. Adding a desktop capture source does not repair a silent file or its source routing, and it can create duplicate capture in some setups. Investigate Desktop Audio or another capture source only when the programme sound genuinely comes from a separate application or device.
Why does my OBS recording have no audio when I could hear it while recording?
Monitoring and recording output are different checks, and a recording can have audio assigned to a track that the player does not select. Inspect the recording’s track assignment and try an editor if you need to examine multiple tracks. For ordinary playback without editing, OBS recommends assigning all sources to track 1; streaming still needs its own output check.