If audio from an OBS VLC playlist disappears between videos, first find out whether it is missing only from your headphones or also from the stream or recording. Those are different faults: OBS reports include cases where monitoring was silent or clipped while the recorded or streamed audio remained intact.
A moving meter is useful evidence, but it does not prove that sound is reaching your chosen monitoring device. Check the output independently, then work through the source, monitor destination and playlist transition before changing several settings at once.
First locate where the audio is missing
Treat “no sound” as a symptom to classify, not a diagnosis. OBS can send source audio into the programme mix while your local monitoring path is silent. Conversely, you may hear audio locally while the stream or recording does not receive it. The fix depends on which path is failing.
Make a short test with one playlist item that normally causes trouble. Keep the scene and source unchanged, and note whether you can hear it locally, whether the mixer meter responds, and whether a recording contains the sound. If you are testing a live broadcast, use a private or otherwise controlled test where appropriate; do not assume a monitoring test is equivalent to checking the audience output.
| What you observe | What it suggests | Next check |
|---|---|---|
| Monitoring is silent; recording has audio | The local monitor destination or monitoring path may be the issue | OBS monitoring device and operating-system output |
| Monitoring is silent; recording is also silent | Source track selection, mixer routing or output-track assignment may be involved | VLC source and Advanced Audio Properties |
| You hear audio locally; recording or stream is silent | The source may be monitored but not routed to the relevant output track | Active tracks and output routing |
| Meter moves, but you hear nothing | Audio is reaching some part of the OBS mix, but audibility is unconfirmed | Check monitoring device and device mute/output |
These are diagnostic clues, not proof of a particular cause. In one report, an OBS user said the recording seemed fine despite silent monitoring; another described a cutoff during monitoring rather than streaming or recording. Those cases show why you should test the paths separately, not that every similar fault behaves the same way. The OBS report about mixed playlist items concerned a particular older setup and is not a universal explanation.
If your issue is a broader failure to carry audio from an OBS setup to YouTube, keep the distinction in mind while reading about YouTube stream quality settings for a low-motion playlist. Picture quality and audio routing are separate checks, even when they appear during the same broadcast.
Check the stream or recording separately
A local recording is often the least ambiguous first test. Record a short passage that includes the transition, then listen to the file in a player outside OBS. Check the moment before the change, the transition itself and the start of the next item. Do not judge the result only by what you hear through the same headphones that are currently failing as a monitor.
If the recording is clean but headphones are silent, avoid immediately changing bitrate, encoding or YouTube settings. Those do not explain a monitoring-only failure. Focus instead on OBS’s monitoring destination and the operating system’s selected playback device. If the recording is silent too, inspect the source’s audio-track choice and whether the track is enabled for the recording or stream output.
For a stream test, listen to the broadcast output independently from the OBS monitoring path. A second device can help, but make sure it is actually playing the live output rather than a local preview or a delayed copy of the same monitoring feed. YouTube’s live streaming help is a useful official reference for the platform side; it does not diagnose a local OBS monitor problem.
Keep a simple record of what each test shows. “Audio is missing” is less useful than “OBS meter moves, headphones silent, local recording contains audio, failure begins on the next playlist item.” This description helps you distinguish a local listening issue from missing programme audio and avoids repeating fixes that target the wrong path.
Read the VLC source meter with care
Start playback of the affected item and look at the VLC source’s audio meter in the OBS mixer. If it responds, OBS is registering activity from that source at some point in the mix. It does not establish that sound is reaching your speakers, that the correct output track is active, or that the stream contains it.
If the meter does not move, check the VLC source’s audio-track selection and confirm that the file itself has an audible audio track. Then inspect the mixer controls for mute state and the source’s advanced properties. In Advanced Audio Properties, check which tracks are selected for the relevant outputs. Labels and layout can vary by OBS version, so focus on the function rather than relying on a screenshot from a different release.
If the meter moves but the recording is silent, the next question is not “why is the meter wrong?” but “which track is being recorded, and where is this source assigned?” Compare the source’s track assignment with the recording configuration. If the recording is audible and only monitoring is silent, return to the monitor destination rather than changing output-track settings without a reason.
A community checklist in the OBS forum discussion suggests reviewing the VLC track, mixer, active tracks, monitoring device and operating-system output. Treat that as troubleshooting advice from users, not an official guaranteed fix. Work through one item at a time and repeat the same test clip after each change.
Check the monitoring device and mode
OBS sends monitored audio to a chosen monitoring device. If that destination is a disconnected headset, an unused monitor output or a device that the operating system has muted, a moving mixer meter can coexist with silence in your headphones. In OBS audio settings, confirm the selected monitoring device is the one you are actually using. Then check the operating system’s current output device and mute/volume state.
Test the same headphones or speakers with another application. This does not prove that OBS is configured correctly, but it can rule out a simple device, cable or system-volume problem. If the operating system has switched outputs since you last used OBS—for example, from headphones to a monitor—select the intended device and test the playlist again.
For the VLC source, note its monitoring mode in Advanced Audio Properties. “Monitor Off” means OBS does not play that source through the monitoring output; it may still be routed to programme output. A mode that includes monitoring asks OBS to send audio locally, but it still depends on the destination device and does not by itself confirm that the stream or recording is configured correctly.
One forum participant reported that switching the source from “Monitor and Output” to “Monitor Off” and back restored local sound. Another reply described an unresolved recurrence, and the original poster did not know which setting had fixed the problem. You can try the toggle as a quick, reversible test, but it is anecdotal rather than a dependable cure. Change it once, repeat the same transition and check both the local monitor and a recording.
The separation matters for long-running channels. If your computer is also handling a playlist for a 24/7 podcast stream, your headphones are only one point of observation; the actual programme output still needs its own check. Monitoring is useful for listening locally, but do not use it as a substitute for verifying what the output contains.
Test the transition, not just the first video
A playlist can play its first item correctly and fail at the boundary between items. Test the exact sequence that reproduces the problem. Note whether the playlist mixes audio-only and video files, whether the failure happens at natural completion or only after pressing “Next”, and whether the next file begins silently or the outgoing file is cut short.
Repeat the test with a simple playlist containing the affected item and one known-good item. If the fault appears only when advancing manually, record that. If it happens at natural completion too, record that instead. Avoid changing the audio mode, the operating-system output and the file order together; otherwise you will not know which change altered the result.
An OBS project issue filed against OBS 26.0.2 on Windows 10 described monitored audio cutting off shortly before the end of an item. It was marked confirmed by a project member, then closed as not planned. That history supports treating transition-related monitoring problems as a plausible diagnostic category, not assuming that the same behaviour occurs on current versions or that the status means a fix shipped. See the issue report on audio cuts between clips for its specific context.
If the next item is audio-only and the previous video frame remains visible, include those details in your notes. A separate older report described that combination on OBS 25.0.8 and 26.0.0-rc1. It does not show that every mixed playlist causes audio loss, nor does it identify a universal setting to change. The practical value is in making your reproduction specific enough to compare with the report.
For a long playlist of repeated material, transitions can be hard to monitor continuously. A recorded exam-preparation channel workflow raises a similar operational point: the playlist and its output need checking as a sequence, not merely by confirming that one file starts. Keep a test sequence short while troubleshooting, then verify the full playlist before relying on it.
Compare headphone monitoring with a recording
A recording lets you compare the local listening path with captured output. Make a brief test that includes the last part of one item and the start of the next. Listen to the file in a separate player, preferably after the test rather than while relying on the same OBS monitor. If the recording contains both sections but headphones did not, your evidence points towards the local monitor path.
If the recording drops the same audio, check the relevant output track assignment and source track selection. If only the transition is absent in the recording, compare whether the source itself stopped, whether the next item loaded, and whether the issue repeats when you play the files in a different order. Do not infer that the playlist software is at fault merely because the gap aligns with a boundary; confirm that the source audio is present and assigned to the output.
A local recording is not identical to a live stream in every respect. It is a useful comparison, not a guarantee about what YouTube received. When the recording is fine but the live output is not, test the stream independently and investigate the relevant output path. An open 2025 OBS report describes a different case in which local sound was audible but did not reach the live stream; the reporter said rolling back to an earlier version resolved their case. That is one user’s report, not a general recommendation to roll back.
Keep the test small and repeatable: same scene, same files, same order, same transition method. Write down the result after each change. This method is less tempting than reinstalling applications or rebuilding a scene, but it preserves the clues that tell you whether the fault is local monitoring, a playlist boundary or output routing.
When to investigate routing or report a bug
If both the recording and stream lack sound, check source track selection, mute state and the active tracks for the output you are testing. If local monitoring works but the stream does not, investigate output routing rather than the monitor device. A 2025 report for OBS 32.0.2 on Windows 11 describes that distinct pattern; its author’s rollback result should not be treated as a fix for a monitoring-only issue.
If the fault persists, gather enough detail for someone else to reproduce it: OBS version and operating system; the source’s monitoring mode; whether the meter moved; whether the playlist contains audio-only files; natural end versus manual advance; and whether a recording or stream also lost audio. Note whether the problem happens with one pair of files or throughout the playlist. Include the result of testing the operating-system output device and a short recording.
Check whether VLC is installed and whether its architecture matches OBS if the VLC Video Source is absent or cannot initialise. The OBS reference manual hosted by the University of Regina describes this as a prerequisite for the source. It also describes playlist items playing in the order added. That information can help with setup and sequencing, but it is not evidence that matching architecture cures a transition-only monitoring fault.
Do not buy new headphones or an interface just because a VLC source meter moves while monitoring is silent. The evidence here points first to configuration and routing checks; hardware becomes relevant only if you independently establish a device fault. For an always-on channel, if the repeated local checks do not explain missing programme audio, consider a workflow that does not depend on keeping your own computer running and listening to the monitor all night. StreamNeo can remove the need to keep a computer on for a file-based YouTube broadcast, but it does not replace checking the channel’s audio and content.
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
Does a moving VLC source meter mean I should hear audio?
No. Meter activity shows that OBS is registering audio activity, but it does not prove that the selected monitoring device is receiving sound. Check the device, operating-system output and recording separately.
If I cannot hear the playlist locally, is the YouTube stream silent too?
Not necessarily. OBS reports describe monitoring failures where recording or streaming output remained fine, but those reports do not guarantee that your own stream has audio. Verify with a recording or an independent stream check.
Should I switch the VLC source to “Monitor and Output”?
Check the current monitoring mode first. A forum user reported that toggling modes restored monitoring, but other reports did not establish a reliable fix. Try it only as a reversible test and compare the same playlist transition afterwards.
Is an old OBS issue proof that my current version has the same bug?
No. The reports describe particular versions, operating systems and symptoms, including cases closed as not planned. Use them to guide a careful reproduction and report the details of your own setup rather than assuming the cause or a fix.