When OBS advances to the next cartoon episode, first find out whether the stream or recording is silent too, or whether only your local monitoring has stopped. A moving mixer meter and silence in your headphones are clues, not proof either way; a short recording that spans the transition will help distinguish the two cases.
Work through the source and routing checks only after you know where the sound disappears. OBS can play a file or a VLC playlist, and each setup has different controls; changing monitoring settings will not restore audio that is absent from the recorded output.
Determine whether stream audio is missing too
There are two separate things you may be listening to: the audio OBS sends to a recording or stream, and the audio OBS routes back to your computer for monitoring. Monitoring is useful when you want to hear a source locally, but it is not the audience’s copy of the sound. If your headphones go quiet at the episode change, the broadcast may still contain audio. Conversely, a meter that moves does not prove the stream has received an audible track.
Start with a controlled test rather than changing settings at random. Note the time the current episode ends and the next one begins. During that interval, watch the relevant source in the OBS Audio Mixer and make a short recording that includes both sides of the transition. Play the recording in a standard media player. If you can hear the next episode there, the problem is more likely to be monitoring or the selected playback device. If the recording is silent too, check the media item, its selected audio stream, mute or volume state, and recording track assignment.
A live platform’s playback can introduce another variable, so a local recording is a useful first separation test, not a guarantee that every audience device hears the same thing. If the file has sound locally but the live output does not, compare the OBS output and track configuration before changing the source. For a broader view of how a pre-recorded playlist reaches YouTube, see this guide to setting up a YouTube playlist loop.
Treat each result as a direction for the next check, not as a diagnosis on its own. A silent recording does not establish that VLC is at fault; a successful recording does not prove OBS has a universal monitoring bug. The same symptom can arise from different source, track, or device choices.
Check meters and a short recording
While the affected episode is playing, locate its source in the Audio Mixer. A meter that responds to sound means OBS is receiving activity at that point in the chain. It does not confirm that the source is routed to the track you are recording, or that the monitoring device is working. A meter that stays still is a different clue: confirm the source is not muted, the mixer fader is not down, and the media item actually has an audio stream.
Record a sample long enough to include the end of one episode and the beginning of the next. Use the same OBS output settings you normally use, then listen to the saved file outside OBS. If you hear both episodes in it, preserve that file and focus your next tests on monitoring. If the second episode is silent in the file, replay that episode by itself in OBS. A file that is silent both alone and in the playlist points towards its audio stream or source settings; sound when played alone but not after the transition narrows attention to the playlist change or source lifecycle.
If the local test is audible but viewers report silence, check a separate sample of the stream output where practical and verify the selected recording and streaming tracks. Do not infer audience silence from your monitoring headphones. Likewise, do not infer audience sound merely because the mixer meter moves.
Keep a brief note of what each test shows. For example: “episode two plays alone, recording is silent only when it follows episode one, meter moves, headphones silent.” That is more useful than “OBS has no audio” because it identifies the output, source and point at which the symptom appears.
Inspect the episode or VLC playlist source
First identify which OBS source you are using. A built-in Media Source is intended for an individual media file; VLC Video supports playlists and depends on VLC being installed. OBS’s Media Sources documentation describes these source types, their relevant settings and the VLC dependency. It also says that 64-bit OBS requires 64-bit VLC. If you use VLC Video, check that the installed VLC version matches OBS’s architecture rather than assuming the playlist itself is the only variable.
For a Media Source, confirm the selected file is the episode you expect. Test it on its own and check its playback behaviour when it reaches the end or the scene becomes active. “Restart playback when source becomes active” is enabled by default, and “Close file when inactive” unloads the file; OBS notes there can be a short period without the source showing while it reloads. Those options describe playback and visibility behaviour. They are worth checking when scenes hide and reveal a source, but they do not by themselves establish why audio disappeared.
For a VLC Video playlist, inspect the item order and verify that the next item is the intended episode. Test the problem item alone, then put it back in the same position and reproduce the transition. This helps distinguish a file with no usable audio stream from a problem that appears only as the playlist advances. Check the source’s Audio Track selection as well: OBS documents track 1 as the default. A file can contain multiple audio streams, so verify that the selected one is the episode’s intended audio rather than assuming the default suits every file.
If one episode fails while the rest play, compare its audio stream and track choices with a working episode. If every item plays alone but one transition fails, note whether the preceding item, following item, or scene change is consistently involved. Do not convert media or change codecs as a first response unless a specific test points to a file-format problem. The troubleshooting route for a sermon folder played through FFmpeg uses a different playback path, so its source-specific controls should not be substituted for OBS’s.
Verify audio tracks and source routing
OBS’s mixer can show incoming audio even when the recording is configured to save a different track. Open Advanced Audio Properties from the mixer gear menu or the Edit menu. For the affected source, check which tracks are selected. Then open Settings → Output and confirm that the track you expect to record is enabled. The two sides must agree: assigning a source to a track that the recording does not include can produce a video that appears to have no audio.
OBS’s Multiple Audio Track Recording Guide explains how track assignments and enabled recording tracks work. A standard video player generally plays one audio track at a time. If you are not editing the recording later and want ordinary playback to include all sources, OBS advises placing those sources on track 1. If you intentionally keep dialogue, music or other sources on separate tracks for editing, preserve that arrangement and check the player’s selected track when reviewing the file.
Do not assume a track change is needed simply because the monitoring output is silent. First use the short recording to establish whether the recorded sound is missing. If the recording is complete, changing track assignment may disrupt a working output without addressing the monitoring device. If it is silent, check the source’s assignment and the enabled output track before altering monitoring mode.
Also check the source mute button and fader in the mixer. Make one change at a time, record the same transition again, and compare the result with the original test. That makes it possible to tell whether a routing change helped, rather than relying on memory or a momentary sound from the monitoring path.
Check monitoring device and settings
If the recording contains the episode audio but you cannot hear it through OBS, focus on local monitoring. In OBS audio settings, check which monitoring device is selected. Make sure it is the device you are actually listening to, and that the operating system has not switched output to another set of speakers or headphones. If you use more than one audio device, test the selected device directly with other audio before concluding that OBS is at fault.
In Advanced Audio Properties, inspect the affected source’s Audio Monitoring mode. Compare it with the behaviour you want: monitoring may be off, or it may be set to monitor only or monitor and output. The appropriate choice depends on whether you need local listening as well as stream audio. Do not select “Monitor and Output” as a remedy for a source that is absent from the recording; it changes the monitoring route and does not repair missing media audio or incorrect recording-track routing.
If the setting already matches your intent, briefly switch monitoring off and back to the intended mode, then repeat the recording and listening tests. If sound returns, record that as a temporary observation and see whether it remains after another transition. A change that restores local sound once is useful evidence, but it is not proof of a permanent fix.
Historical reports in the OBS issue tracker include individual cases where meters moved while monitoring failed, including reports involving playlist or scene transitions. They span specific older OBS versions and circumstances, and a later report also describes a monitoring symptom in a different looping-audio setup. These reports are examples of possible failure modes, not evidence of how often the problem occurs, a confirmed cause in your setup, or a universal current bug. Keep the exact OBS version and reproduce the issue in your own test before drawing conclusions.
Test the next-episode transition
Once a single episode plays correctly, test the changeover separately. Use a short sample or a copy of the playlist and include enough of the end of one item and start of the next to hear what happens. Keep the scene, source and output settings unchanged during the test. Note whether the meter stops, whether the local monitoring stops, and whether the saved recording loses audio. That gives you a comparison between the media item and the transition itself.
If the affected episode has sound when played alone but loses it only after another item, compare the playlist order and observe whether the same preceding item is always involved. If the problem follows the next item wherever it is placed, inspect that file’s audio stream and selected track. If it occurs only after a scene change or when a source is hidden and shown, review the Media Source visibility options and reproduce with those options unchanged before testing a deliberate adjustment.
Make one adjustment at a time. For instance, correct an Audio Track selection, record the transition, and listen back before touching monitoring settings. If that does not change the result, restore the setting or note it, then move on. A simple sequence avoids ending up with several simultaneous changes and no way to know which one mattered.
Before treating an OBS version-specific explanation as likely, confirm the version shown in OBS and check whether a newer version or current documentation changes the relevant behaviour. Issue reports from past releases can help you describe a symptom, but they do not establish that your current installation shares the same cause. For other continuity checks around a long-running broadcast, see the guide to checking why a 24/7 YouTube stream stops on BSNL broadband; network interruptions are a separate issue from an audio transition, so keep the diagnoses distinct.
Recheck stream audio after changes
After each change, make a fresh short recording that crosses the same episode boundary. Listen to it in a standard player and confirm which track it plays. If the stream is active, verify the stream output independently where possible rather than using your local monitoring as a proxy. Check the next transition too: a one-time return of sound does not show that the playlist will remain audible on later items.
If only monitoring remains silent while the saved output is audible, keep the working stream configuration intact while troubleshooting the device and monitoring mode. If both recording and stream output are silent, return to the media source, track selection, mute state and output-track checks. Avoid making repeated changes to unrelated controls, which can introduce a new problem and obscure the original one.
If the fault persists, gather the operating system, exact OBS version, source type (Media Source or VLC Video), media format, playlist order, whether the meter moves, and whether the issue affects monitoring, recording, stream output, or some combination. Note whether every episode is affected or only a specific file or transition. These details help someone reproduce and diagnose the case; they do not guarantee a resolution.
For a channel built from a fixed file rather than an OBS playlist, you may also want to understand how a YouTube playlist loop is set up with a streaming service. The playback method changes which controls you need to troubleshoot, so describe the actual path you use when asking for help.
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
The OBS meter moves, but I cannot hear the next episode. Is the stream silent?
Not necessarily. The meter shows audio activity entering OBS, while local monitoring and the recorded or streamed output can fail separately. Make a recording across the transition and play it outside OBS before deciding which path is silent.
Does “Monitor and Output” fix missing audio for viewers?
No. It controls whether a source is sent to local monitoring as well as output; it cannot restore an absent media stream or correct an unassigned recording track. First establish whether the saved output has sound, then choose monitoring settings for the local listening you need.
Why does VLC Video play one episode but not the next?
The next file may have a different audio stream or require a different Audio Track selection, or the symptom may occur only during the transition. Test the episode alone and in the playlist, check its selected track, and compare a recording that includes the changeover.
What should I include when asking for help?
Include your operating system, exact OBS version, source type, media format, playlist order and whether the meter moves. Say separately whether monitoring, the recording or stream output is silent, and whether the problem follows a particular file or only an episode transition.