A silent interval between videos can begin in the media files, in an OBS playback source, in monitoring, or after the stream leaves your computer. The quickest fix is not to change settings at random, but to compare the OBS meter, a local recording and the public stream at the same transition.
Once you know where the silence starts, make one targeted change and record the transition again. The checks below cover playlist track selection and loop settings for VLC Video sources, Media Source playback, scene and audio routing, and the connection to YouTube.
Locate the point where the audio disappears
Start by reproducing the problem. Note which item is ending, which item is starting, and whether the silence happens at every transition or only between particular files. If the interval is long enough to identify easily, write down its approximate position in the local files and in the YouTube playback.
Watch the audio input-level indicator in the OBS mixer while the transition occurs. OBS describes this indicator as a way to show the level reaching the mixer, so it gives you a useful first division: is OBS receiving audio, or is the audio absent before it reaches the mixer? The OBS Audio Mixer technical details explain what the input indicators represent.
Make three observations:
| Observation | What it suggests | Next check |
|---|---|---|
| The mixer meter falls silent at the boundary | The source may have no usable audio at that point, or the next item may not be using the expected track | Inspect both files, playlist order and audio-track selection |
| The meter moves but headphones are silent | Monitoring may be the problem rather than the stream output | Listen to a local recording and the public stream |
| The local recording has continuous audio but YouTube does not | The problem may be in the stream connection or ingest path | Check OBS connection symptoms and YouTube stream health |
| Only one item causes the silence | That file or its selected track deserves individual testing | Play it alone through the same OBS source |
This is a diagnostic framework, not a claim that one setting fixes every boundary gap. The same audible symptom can come from different points in the path. Keep the test controlled by changing one thing at a time.
If you are still building the setup, the guide to starting a 24/7 YouTube live stream with OBS covers the wider arrangement. For this problem, however, begin with the transition itself rather than rebuilding the whole channel.
Check the media files at their boundaries
Open the ending file and the following file outside OBS. Listen to the final seconds of the first item and the opening seconds of the next. Check that both actually contain audio, rather than assuming that a video file with a picture also has an audible track.
A file can contain several audio tracks, or an audio track that a particular player does not select in the way you expect. A mixed playlist can also contain video-only items, audio-only items, or files made with different audio arrangements. Test the files individually through the same OBS source if the gap affects only some transitions.
Look for a clean explanation at each boundary:
- Does the first file end with silence already present in the file?
- Does the second file begin with silence before speech, music or ambience starts?
- Does the next item contain an audio track at all?
- If it contains more than one track, is the intended track available and selected?
- Does the gap occur after the same item every time, or does it follow playlist order rather than a particular file?
Do not treat a silent opening as an OBS failure until you have listened to the source file itself. For a devotional channel, for example, a video may show a title card before the bhajan begins. For a study channel, a short silent lead-in may have been included deliberately. The remedy is different from a source that stops producing audio unexpectedly.
If you control the media preparation, one practical workaround is to join a sequence into a single continuous file with the desired transitions already present. This moves the boundary from a playlist hand-off into one file, but it also changes how you edit, replace and schedule items. It is a production workaround, not a guarantee of gapless playback. Put the joined file through a local recording before using it for a live broadcast.
Audio encoding differences can also make a playlist harder to diagnose. Avoid changing several properties at once. If you are checking video encoding choices as part of a wider setup, the CBR versus VBR guide for pre-recorded 24/7 streams gives that issue its own treatment. It will not, by itself, identify whether the source meter goes silent at a file boundary.
Verify VLC playlist loop and track settings
For a sequence of files, check whether the OBS source is VLC Video rather than assuming that every media source handles a playlist in the same way. OBS documents VLC Video as a playlist-capable source and lists controls including Loop Playlist, Shuffle Playlist and Audio Track in its Media Sources documentation.
Open the source properties and inspect the playlist itself. Confirm that the intended files are present, that the order is correct, and that the source has not been left with an old item at the top or bottom. Temporarily disable Shuffle Playlist while diagnosing a boundary, because a changing order makes it harder to reproduce the same transition.
If the channel should repeat the playlist, check Loop Playlist. A disabled loop can make the final item behave differently from the ordinary transitions. It may stop, show nothing, or leave you investigating the end of the playlist as if it were an audio defect. Looping is a playlist control, not a promise that the audio between two separate files will be seamless.
Next, inspect Audio Track. The selected track must exist in each item you expect to play. If one file has the chosen track and another does not, the transition may expose a source or selection mismatch. Test the files separately with the same track setting rather than selecting a different track for each item and then losing a reproducible setup.
Network caching appears among the VLC source settings, but do not prescribe a cache value for a local file-boundary gap without evidence. Increasing it may alter playback behaviour, but it does not establish that the silence began with a cache problem. First determine whether the mixer meter, local recording or stream is affected.
Historical OBS issue reports can be useful clues, but they are not current universal diagnoses. One report concerned unexpected behaviour when a VLC playlist alternated video and audio files and was tied to OBS versions from 2020. Another described audio clipping during monitoring in a different old configuration. These reports justify separating mixed media and monitoring tests, not claiming that a current OBS release has the same defect.
Inspect Media Source playback behaviour
If you are playing one file repeatedly rather than moving through a playlist, compare the setup with an OBS Media Source. OBS describes Media Source as a source for supported audio and video files, with its own Loop control and playback-end behaviour.
Check Loop when the same file should replay. A source that is meant to run one video continuously needs a different check from a VLC playlist that should move through several files. If Loop is off, playback may simply reach the end. If Loop is on but the recording still contains silence, observe the exact point at which the source stops producing audio.
Also inspect the option to show nothing when playback ends. That setting affects what is displayed after playback finishes. A blank visual output can make the end of a file look like a broader stream failure, but it is not proof that the setting caused an audio gap. Listen to the local recording and watch the mixer meter before drawing that conclusion.
A single looping file may avoid some playlist hand-offs, but it can introduce a different boundary: the end of the file meeting its beginning. Test that loop in a local recording rather than assuming that the source will join the two points without an audible change.
For several programmes, compare two controlled arrangements: the original VLC playlist and a prepared continuous file. Keep the same scene, audio routing and output settings for both. If one arrangement records continuously and the other does not, you have narrowed the issue to the playback method or its media boundaries rather than to the YouTube delivery path.
Check scene transitions and audio routing
A file can have audio and a source can play it while the selected scene still sends no audible output. Review which scene is live at the moment of the transition and whether a scene change is happening at the same time as the playlist change.
If separate scenes are used for different videos, check whether the audio source exists in both scenes and whether one scene has its volume muted. Look at the OBS mixer while moving between scenes. A meter that disappears exactly when the scene changes points you towards scene or source configuration, while a meter that continues moving points elsewhere.
Also check whether the source is routed through the intended mixer channel. A source may be visible in the preview but not contributing to the output you are recording or streaming. Keep the test simple: one playback source, one visible scene, and the expected mixer channel. Once that arrangement records correctly, add the other scenes back one at a time.
Monitoring needs a separate check. Headphones use OBS monitoring and your chosen monitoring device; they are not the same evidence as the encoded recording sent to viewers. A historical OBS report described clipping heard during monitoring while streaming and recording were reported as unaffected. It relates to an old version and configuration, so use it only to support the distinction between monitoring and output.
If headphones are silent but the local recording contains the programme audio, do not alter the playlist merely to restore monitoring. Check the monitoring device and output settings first. Conversely, if both the mixer and local recording lose audio, monitoring is unlikely to be the only problem.
Record locally to verify one targeted change
Before changing the public stream, make a short local recording that includes the end of one item, the transition and the beginning of the next. Use the same scene and source that you intend to broadcast. The recording should be long enough to include a normal transition and, if relevant, the playlist loop back to its first item.
Change one setting or one media item, then record the same transition again. Examples include enabling Loop Playlist, correcting Audio Track, removing a problematic file from the test playlist, or testing a prepared continuous file. If you change the source, scene, media files and monitoring device together, a successful result will not tell you which change mattered.
Listen to the recording with headphones and watch the waveform or playback time if your player provides those views. The important question is whether the recorded programme contains the audible interval, not whether the OBS preview looked normal. Compare the recording with the mixer meter you observed during the test.
Use a small test playlist with known files if the live playlist is large. Keep a note of the order and the setting changed. If the gap occurs only between particular items, test the same pair repeatedly. If it occurs between every item, compare the playlist with one continuous file and then return to the source settings.
A local recording is also useful for avoiding unnecessary network changes. If it contains continuous audio while headphones do not, investigate monitoring. If it contains a gap while the meter also drops, stay with the source and media checks. The recording gives you evidence from the programme output rather than from one person’s listening position.
Confirm the result in the stream
Only after the local recording is clean should you check the public stream. Allow enough time for the same item boundary to reach the YouTube player, then compare what you hear with the local file. If the local file and public stream differ, the problem is no longer best treated as a simple playlist setting.
Check OBS for dropped-frame or intermittent-connection symptoms. OBS’s stream connection troubleshooting guide explains that dropped frames and disconnections can relate to the connection with the ingest server or the ability to sustain the configured bitrate. That guidance helps investigate delivery problems, but it does not establish that every audio gap is caused by the network.
You can also use YouTube’s stream health information while the test is running. Compare the timing of any reported disruption with the local recording. A clean local recording and a disrupted public stream justify checking the connection and stream health. A gap present in both places sends you back to the source, files or OBS scene.
Do not judge the fix from one preview alone. Repeat the specific transition that previously failed, then check a different transition and the playlist loop if the channel uses one. If you have changed a file, keep the original available until the replacement has passed the same recording and public-stream checks.
For operators whose main difficulty is keeping a computer and connection running overnight, the article on a YouTube stream disconnecting and possible causes may help with the wider connection problem. A cloud workflow can remove the need to leave your computer switched on, but it does not remove the need to test the media file and its boundaries.
If your workflow is to upload one prepared video, paste the YouTube stream key and avoid leaving a local computer running, StreamNeo removes the operational burden of keeping OBS open and can monitor and restart the broadcast when it drops. You should still verify the uploaded file through a local test before committing it to an always-on channel, because a cloud playback workflow cannot correct silence that is already present in the media.
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 there silence between every two videos?
Start with the OBS mixer meter and a local recording. If the meter drops and the recording contains the gap, inspect the ending and beginning files, the VLC playlist, the selected Audio Track and the source playback settings. Do not assume that one setting fixes every boundary type.
Why can I hear a gap in headphones but not in the recording?
That points towards monitoring rather than necessarily towards the programme output. Check the monitoring device and listen to the local recording or public stream before changing the media playlist. Historical OBS reports support treating monitoring and recording as separate paths, but they do not prove a current universal bug.
Should I increase VLC network caching to fix local file gaps?
Not without evidence that caching is involved. The OBS VLC source exposes caching-related settings, but a local file-boundary gap should first be tested through the mixer meter, individual file playback and a local recording.
What if the recording is clean but YouTube has the gap?
Check OBS connection symptoms, dropped frames and YouTube stream health, then compare their timing with the public interruption. If the local recording remains continuous, investigate the path to the ingest service rather than changing the media files again.