If your OBS YouTube loop has no audio, first find the last point where you can hear it: test the exact generated file outside OBS, then trace playback through OBS and into a controlled YouTube test. Do not change FFmpeg encoding settings until those checks show the silence begins in the file.
A silent live stream can originate in the file, the OBS source or selected audio track, OBS mixer and output routing, or YouTube ingest. Each stage gives you a separate check; a meter moving in OBS, for example, is not by itself proof that viewers receive sound.
Locate where the audio disappears
Think of the path as a series of boundaries: the file must contain sound, OBS must play and receive it, OBS must send it on the intended output track, and YouTube must ingest that output. Test those boundaries in order. If you start by changing codecs or adding FFmpeg options, you may alter a working file while leaving a muted source or an unrouted OBS track untouched.
Write down what you actually observe at each step. Can you hear the file in a normal media player? Does the relevant source meter move in OBS while it plays? Can you hear audio through OBS monitoring or in a local recording? Does a controlled YouTube test have sound? These answers narrow the search without assuming an unverified cause.
| What you observe | Where to look next |
|---|---|
| The file has no audible sound outside OBS | Check the file's audio stream and the actual FFmpeg inputs, mapping and output settings |
| The file plays with sound, but the OBS source meter does not move | Check the selected file, playback state, mute state and source audio-track selection |
| The source meter moves, but a local recording or test stream is silent | Check OBS track assignment, recording or streaming output settings, and monitoring separately |
| A local recording has sound, but the YouTube test does not | Check the outgoing stream's audio format and YouTube stream health |
The table is a diagnostic map, not a claim about what is wrong with your setup. A positive check tells you that signal reached that boundary; continue to the next one if the final stream is still silent. For an overview of recurring FFmpeg loop concerns, see how reconnect behaviour fits into a YouTube music stream, but reconnect settings do not establish whether a file contains audio.
Confirm the generated file has an audio stream
Use a media inspection tool available on your system, or inspect the file in a player that exposes its tracks, to check whether the exact output you intend to loop has an audio stream. The relevant file is the output after generation, not merely the source video or audio file you fed to FFmpeg. If you regenerated it, verify the newest output rather than a similarly named earlier copy.
An audio stream in the file's metadata is useful evidence, but it does not prove that the stream contains audible content. A track can exist yet be silent, or it may carry a different language, commentary, or other material than the one you expect. Follow metadata inspection by playing the file and listening to a section where sound should be present.
If the output has no audio stream, the problem is upstream of OBS. Review the actual command, inputs and file metadata before changing anything: the evidence available here does not establish a universal FFmpeg mapping or codec correction. A video-only source, an unintended output selection, or a silent source are possibilities to investigate against your own command and media. Do not paste in a generic -map example and assume it fits a file whose stream layout is unknown.
For a file that has an audio track but sounds silent in a player, inspect whether the track is selected and whether the relevant part of the source itself contains sound. If you are building a longer lecture loop, the distinction between a video file that contains sound and a silent visual file is also important in a 24/7 lecture stream workflow with FFmpeg on Debian. That guide is a separate workflow, not evidence about the file currently failing.
Play the file outside OBS
Open the exact generated file in a desktop player and listen through a known working output device. Jump to a part of the clip where you expect sound; a quiet title card or a silent gap can otherwise look like a failure. If the file is long, test more than one representative point, including a point near the beginning and one later in the programme.
If you can hear the expected audio outside OBS, the file is not simply silent end to end. You have not yet proved that OBS will select the same track or that YouTube will receive it, but you can now focus on the source and routing path. If you cannot hear audio, try another player or a known working output device before concluding the file is silent. This separates a playback-device issue from a file issue.
Do not treat a waveform, file size, or the presence of an audio track as a listening test. Those clues may help you inspect a file, but listening to the exact output answers the more practical question: does the programme contain sound at the point you need it? If another player confirms silence, preserve the original and investigate the actual FFmpeg inputs, stream mapping, selected codec and muxing for that job. A precise correction depends on those details.
Check the OBS Media Source audio settings
In OBS, confirm that the source points to the file you just tested. Check that playback is active, the source is not muted, and the source is enabled and visible as needed in the scene. If the file plays in an external player but its OBS meter stays still, these basic source checks are more informative than changing YouTube's encoder settings.
The built-in Media Source supports a range of video and audio formats, and its Loop property controls replay after playback completes. OBS documents supported formats and the source's controls in its Media Sources guide. A loop setting determines whether playback repeats; it does not by itself prove that audio is present or routed to the stream.
If you use OBS's VLC Video source rather than Media Source, check its Audio Track selector. OBS documents track 1 as the default, so a multi-track file may need a different track selected if the one carrying the intended audio is elsewhere. Also check that the playlist is configured as intended and that Loop Playlist is on if you expect it to repeat. The VLC source requires VLC to be installed, and OBS notes that 64-bit OBS needs 64-bit VLC.
Test one setting at a time. If selecting another track makes the source meter move, you have evidence that the prior selection was not delivering the expected audio to that source. If nothing changes, restore the setting if appropriate and continue to the mixer and routing checks rather than cycling through unrelated encoding options.
Check OBS output routing and meters
Play the source while watching the OBS Audio Mixer. OBS's Audio Mixer guide recommends keeping an eye on the meters. A moving meter shows that audio reaches that mixer input; a stationary one directs attention upstream, such as source playback, track choice, or mute state. Check that you are watching the meter for the source you expect, not a different microphone or desktop-audio input.
If the meter moves, listen through OBS audio monitoring if it is configured, and make a short local recording using the same scene. OBS recommends recording a session and listening to the result before going live. A recording with sound confirms that audio reached that recording path, but it does not alone confirm that the streaming output uses the same tracks. Listen to the file rather than relying only on the meter.
Review the source's track assignment and the streaming output's selected audio track in OBS. Settings differ by configuration and version, so verify the controls in your own OBS instance instead of assuming that a particular track number is active. If you record and stream using different track selections, a local recording can have audio while the live output does not.
Use Monitoring to listen through the device OBS is configured to use. Monitoring silence is not conclusive if that device is unavailable or misconfigured; compare it with the local recording and meter. Conversely, hearing the monitored source does not prove that the stream output includes that track. The point is to compare independent observations and identify which boundary stops passing sound.
If your scene also uses Audio Input Capture or Audio Output Capture devices, check whether the same device is enabled globally under Settings > Audio. OBS warns that capturing the same device both globally and at scene level can cause echo. That caveat concerns duplicate device capture; it is not evidence that a Media Source file is silent. For a 24/7 setup, keep the scene and track configuration understandable enough that you can repeat these checks after an edit or restart.
Determine whether audio reaches YouTube ingest
Once the file plays, an OBS source meter moves, and your routing checks look correct, make a controlled test stream using the workflow available to your channel. YouTube advises testing with audio and video similar to the planned broadcast and reviewing stream health during the event. Keep the test brief and private or unlisted if that suits your workflow, and use the live control room or another available monitor to check whether YouTube reports a healthy incoming stream and whether sound is present in the test playback.
A local recording with sound and a silent YouTube test points toward the outgoing stream configuration or ingest, but it does not identify which one without further checks. Compare the OBS streaming track and output settings with YouTube's published guidance for the protocol you are using. YouTube's live encoder settings and bitrate guidance lists AAC or MP3 audio for RTMP/RTMPS. It recommends stereo audio at 44.1 kHz and 128 kbps. These are published encoder recommendations, not proof that your missing audio is caused by an incompatible setting.
Check stream health during the test and listen to the playback rather than relying on a single status indicator. If OBS's local recording includes sound but the YouTube playback does not, note the exact output format and track configuration before changing them. If the source meter never moved, YouTube's ingest settings cannot restore sound that did not reach OBS's mixer in the first place.
If your broadcast is a radio or music loop with still or minimal visuals, the audio path still needs to reach the live output; the visual format does not remove that requirement. The practical distinction between audio-only programming and a YouTube live video is discussed in whether a YouTube radio livestream can run without a video. Check the current official YouTube guidance for your actual encoder protocol and setup rather than treating a blog example as a guarantee of approval or delivery.
Change one layer and retest
When a check locates the failure, change one relevant setting and repeat the same test. If the exact file is silent outside OBS, investigate the inputs and output mapping in the command that generated it. If it plays elsewhere but the source meter stays still, correct the source file selection, playback or track settings. If the meter moves but a recording or stream lacks sound, inspect track routing. If the recording works but YouTube playback does not, test the outgoing encoder settings and ingest path.
Keep a short record of the original observation, the single change you made, and what changed in the retest. This prevents a chain of simultaneous edits from obscuring which one mattered. If a setting has no effect, return it to its previous state before testing a different layer where practical. Save or note a known-good configuration so an unrelated scene edit does not make the next overnight run harder to diagnose.
For a channel that depends on a file repeating overnight, there is also an operational choice separate from this audio diagnosis. Running the loop through OBS means the local machine, scene and output settings remain part of the broadcast path; a cloud-based workflow can remove the need to keep that computer running, but it does not change the need to verify that the uploaded programme has sound. StreamNeo removes the specific burden of leaving your computer on to keep a prepared video live, while you still need to check the file and YouTube channel before relying on the stream.
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 my OBS source meter move but the YouTube loop still have no sound?
The meter shows that audio reaches that OBS mixer input, not necessarily that it is assigned to the track sent to YouTube. Check the streaming track selection and make a local recording, then compare both with a controlled YouTube test.
Should I change FFmpeg's audio codec first?
No. First confirm that the generated file has an audio stream and plays audibly outside OBS. Only investigate the command, mapping or codec when your tests place the failure in the file or outgoing encoding path; the right change depends on the actual inputs and stream layout.
What does the VLC Video Audio Track setting do?
It selects which audio track the VLC source uses from a multi-track file. OBS documents track 1 as the default, so check that the selected track is the one carrying the sound you expect.
Do YouTube's recommended audio settings prove why a stream is silent?
No. YouTube's listed RTMP/RTMPS audio formats and recommended stereo settings are useful comparison points for an outgoing encoder, not a diagnosis. Trace the sound through the file, OBS source and routing first, then test what YouTube receives.