If your OBS playlist video appears on YouTube Live but viewers hear no sound, trace the audio path in order: from the file and playlist source, through OBS's mixer and stream track, to YouTube's incoming feed. The first visible clue is whether the playlist source's audio meter moves in OBS.
That order helps you avoid changing unrelated settings. A silent YouTube preview does not by itself tell you whether audio is missing from the file, not reaching OBS, excluded from the outgoing stream, or failing during ingestion.
Start with the source and the playing file
First identify how the playlist was added to OBS. OBS's VLC Video source is designed to handle playlists; the standard Media Source is intended for individual media files. The distinction matters because their playback controls and audio-track settings differ. OBS describes both in its media sources documentation.
If you use VLC Video, select the source in the Sources panel and confirm that the intended item is active and playing. Check whether the playlist is paused, whether playback has started, and whether the current item has reached a quiet section or a silent lead-in. A still or moving picture only confirms that video is reaching the scene; it does not confirm that the file has an audible track.
If the playlist is built from separate Media Sources or another arrangement, check the active source rather than assuming the playlist controller is the source that carries audio. Select a representative item and play it in OBS. Confirm that the file itself has an audio track and that the part currently playing contains sound. A video exported for a silent visual loop, or with its audio removed during encoding, cannot provide audio to OBS.
It can help to open the same file in a media player outside OBS. If it is silent there too, inspect the file or return to the export. If it plays there, that narrows the problem but does not prove OBS is capturing the same track. For a multi-video loop, check more than the first item: one file may have audio while another does not, or the playlist may be transitioning to a different item than expected.
Keep the test simple. Use a short, known-audible clip with speech or music at a clearly audible level. That makes it easier to distinguish a quiet passage from a missing signal. If you are preparing a larger sequence, this guide to encoding a video playlist for YouTube Live covers the file-preparation side; here, the immediate question is whether the current source produces audio in OBS.
Check VLC and the selected audio track
If you are using VLC Video and the source is unavailable or does not behave as expected, check VLC installation. OBS documents that VLC Video uses VLC libraries and requires VLC to be installed. OBS also specifies matching the VLC architecture to OBS, such as 64-bit VLC with 64-bit OBS. Follow the current OBS media sources guidance for the supported setup rather than guessing at an installation from memory.
In the VLC Video source properties, find the Audio Track setting. If the media has multiple tracks, selecting an unintended track can leave video playing while the desired audio is absent. Choose the track that contains the programme sound, then apply the change and watch the mixer while the file plays. Do not change tracks at random: note the current selection first so you can undo a test that makes no difference.
Also check the source's playlist behaviour. Loop Playlist, Shuffle Playlist, and visibility behaviour affect which item is active and when. They do not repair a file with no audio, but they can explain why a test seems inconsistent: a playlist may have advanced to another item, or a source may have restarted. Let a representative clip play long enough to see whether the sound meter responds across a transition.
For Media Source, inspect its own properties instead of looking for VLC-only controls. OBS lists loop and restart behaviour among its Media Source options. If a source is configured to restart or loop, observe the point at which it does so. The goal is to confirm that playback is happening from the source actually used in the live scene, not just from a separate preview window.
If the source depends on an audio device in its playback path, check that the device is still available, but treat this as one possible check rather than assuming a hardware fault. OBS's guidance notes that an absent input indicator can mean audio is not reaching OBS; a media file may not have begun playback, for example. The meter is the next useful checkpoint.
Read the OBS mixer meter
With the clip playing, look in OBS's Audio Mixer for the channel associated with the playlist source. A moving meter indicates that audio is reaching the OBS mixer from that source. If the meter is empty while video plays, stay at the source layer: check the file's audio content, playback state, VLC Audio Track selection if applicable, and whether the source is actually routed into the scene.
The key question is not whether some other mixer channel moves. Desktop audio, a microphone, or another scene source may have its own meter. Watch the channel for the playlist itself. If you cannot identify it, use the source name shown in the mixer and, where available, rename sources clearly so that the playlist does not get confused with a microphone or desktop channel.
An absent meter does not prove a particular device has failed. OBS's technical guidance says that no input indicator means audio may not be streaming towards OBS; one possible reason is that a media file has not started playing. Use this observation to narrow the next check, not to leap to a diagnosis. If restarting playback makes the meter move, the issue was upstream of the mixer at that point in the test.
A meter that barely moves calls for a different check from one that remains flat. Confirm that the source's audio is not simply very quiet in the file, and look at the mixer scale while a known audible passage plays. Avoid pushing the fader up before confirming the signal is present; a fader cannot restore a missing audio track. If you need to prepare recurring transitions between looped material, the article on OBS scene transitions for looped videos may help with scene behaviour, but transition settings are separate from audio capture.
Once the playlist channel meter responds, move downstream. That observation establishes that the source is reaching the mixer; it does not prove the stream includes it. Keep the source meter in view as you check mute, track selection, and the outgoing output.
Check mute, fader and stream track routing
If the playlist meter moves, inspect the channel's mute control and fader. Make sure the source is not muted and the fader has not been pulled all the way down. Then open Advanced Audio Properties and check which audio tracks include the playlist source. OBS allows sources to be assigned to tracks, and the track selected for streaming must be one that actually receives this source.
This is an easy point to miss when an OBS scene has been copied or changed. A source can show activity in the mixer while the stream uses a different track. Compare the playlist's track assignment with the track selected in OBS's output or streaming settings. If the labels or controls differ in your OBS version, consult the current OBS documentation and verify the selected track rather than relying on a remembered menu location.
Audio Monitoring is useful, but interpret it narrowly. Configure the monitoring device in OBS and listen to the playlist source through that device. If it is audible, OBS can deliver a monitor signal to that device. This is a local listening check; it does not prove that the same source is routed into the track being encoded for YouTube.
If monitoring is silent while the meter moves, inspect the monitoring assignment and chosen monitor device. If monitoring works but the live output is silent, return to track inclusion, mute, and the selected stream track. Listening on wired headphones can be a practical way to hear the configured monitor output, but headphones do not fix routing and are not a substitute for checking the outgoing stream.
Make one change at a time and observe again. For example, correct the track assignment, then check encoder output before changing the file or installing anything. That preserves the useful evidence already gathered and avoids masking one issue with a second change.
Inspect OBS's outgoing audio and YouTube's incoming stream
After confirming the source meter and track assignment, check the sound leaving OBS. Listen directly to the encoder or stream output if your workflow provides that option. OBS's guidance distinguishes the quality of audio and video sources routed to the encoder from problems further along the connection. YouTube likewise advises checking the stream directly in the encoder when troubleshooting a stream that looks or sounds wrong. See YouTube's live stream troubleshooting guidance.
Then open the YouTube Live Control Room and inspect the stream health and any audio warning. YouTube documents an error such as “Your encoder is sending no audio” and notes that some encoders have a setting to turn audio on. It also warns that multiple audio streams can cause ingestion problems. If YouTube reports no audio, verify that OBS is sending the intended track and one appropriate audio stream rather than assuming the source file is at fault.
If the outgoing encoder audio sounds healthy but YouTube reports a problem or viewers still cannot hear it, use the health information to investigate delivery and ingestion. YouTube's troubleshooting advice says that if encoder output is healthy, you should investigate the outbound internet connection. A picture arriving at YouTube is not conclusive evidence that audio is arriving in the expected form.
Codec settings are worth checking when YouTube identifies an audio-format issue, but they are not the first explanation when the source meter is empty. YouTube's encoder settings guidance lists AAC or MP3 as audio codecs. For stereo, it recommends 128 Kbps and lists 44.1 kHz. Treat these as documented encoder recommendations to compare against your settings, not as a guarantee that changing them will fix every silent stream; check YouTube's current page in case its requirements change.
The sequence matters: a flat playlist meter points upstream; a moving meter with a silent stream points towards mute, track assignment or encoding; a healthy encoder output with a platform warning points towards delivery or ingestion. This is a diagnosis by observation, not a claim about any particular setup.
Use a short private or unlisted test
Before an important broadcast, make a short test using representative material: include the kind of audio and movement you expect in the real programme. YouTube recommends testing with audio and movement similar to the planned stream and monitoring stream health. Choose a private or unlisted test if you do not want a troubleshooting broadcast to be public, and confirm the visibility setting in YouTube before starting.
During the test, follow the path in order. Confirm the intended playlist item is playing. Watch its OBS meter. Check the mute state and stream-track assignment. Listen to the encoder output, then compare that with YouTube Live's health indicator and the arriving stream. Note the first point where the sound disappears; that is the layer to investigate next.
A simple record of observations is more useful than a list of changes. For instance: “file audible in player; source meter moving; monitor audible; encoder output silent; YouTube reports no audio.” That points to routing or output configuration rather than the source file. Conversely, if the meter never moves, you have not yet established that audio is reaching OBS, so changing YouTube settings is unlikely to be the most useful next move.
Use a test long enough to include a playlist transition if transitions are part of the channel. Check whether audio continues after the next item starts. If the first clip works and the next does not, compare those files and source settings individually. For a channel assembled from study material or other repeated videos, this guide to making a YouTube Live loop from Hindi study videos is relevant to the playlist workflow, while the checks here isolate its audio.
A short test can reveal where to look, but it cannot guarantee that a later broadcast will be problem-free. Keep the official stream-health page available when you go live, and recheck the current YouTube guidance if an encoder warning names a setting that has changed.
Find the next check from what you observe
| What you observe | Layer to inspect next | Useful check |
|---|---|---|
| Video plays; playlist meter stays empty | File or source playback | Confirm the file has audio, playback started, and the correct VLC track is selected if using VLC Video. |
| Playlist meter moves; monitor is silent | OBS monitoring | Check Audio Monitoring assignment and the selected monitoring device. |
| Meter and monitor work; stream is silent | Stream routing or encoder output | Check mute, source-to-track assignment and which track OBS sends to the stream. |
| YouTube reports no audio or multiple streams | Encoder audio configuration | Confirm audio is enabled, the intended track is sent, and avoid unintended multiple audio streams. |
| Encoder output sounds healthy; delivery still appears silent | YouTube health or outbound connection | Check stream health and follow YouTube's connection troubleshooting. |
Treat the table as a route to the next observation, not a list of certain causes. More than one issue can coexist: for example, a quiet file may also be assigned to the wrong track. Change one thing at a time and repeat the test so you know which observation changed.
If you need to keep a channel broadcasting while your own computer is switched off, StreamNeo removes the need to leave a local OBS session running for that continuous file-based stream; it does not diagnose or repair an OBS-to-YouTube audio path. Resolve the audio issue in the tools and workflow you intend to use, then verify the resulting broadcast on YouTube before relying on it overnight.
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 the video play in OBS when the playlist has no sound?
Video and audio are separate parts of the source signal. The file may lack usable audio, the VLC Video source may have the wrong Audio Track selected, or the audio may not be reaching the OBS mixer. Start by checking playback and the playlist source's meter.
The OBS meter moves. Why is YouTube still silent?
A moving source meter shows audio reaching the mixer, not necessarily the track sent to YouTube. Check mute and Advanced Audio Properties, then confirm that OBS streams the track receiving the playlist source. Listen to encoder output and check YouTube Live's health warning as separate downstream checks.
Does Audio Monitoring prove viewers can hear the stream?
No. Monitoring lets you listen to audio through OBS's configured monitor device, but it does not establish that the source is routed to the outgoing stream track. Verify the track assignment and listen to the encoder output or test stream as well.
What if YouTube says the encoder is sending no audio?
Check that audio is enabled in the encoder, that the intended OBS track is sent, and that you are not sending multiple audio streams unintentionally. If the encoder output itself is audible, inspect YouTube's stream-health information and outbound connection rather than assuming the source file is silent.