A black interval between files in a YouTube Live loop can begin in the local OBS scene, at a source’s playback boundary, or later in the delivered stream. Compare OBS preview with what viewers receive before changing settings; that comparison narrows where to investigate but does not identify every cause.
For one file, check an OBS Media Source and its Loop and end-of-playback settings. For several files, check the VLC Video playlist, its visibility behaviour and whether VLC matches OBS’s architecture. Neither route promises a gapless handoff between separate clips.
Locate where the black interval begins
First note precisely when the black picture appears. Does it happen only as one playlist item changes to the next, after the final item, when a scene or source is hidden, or throughout the live output? Also note whether audio continues. These details help separate a file-boundary symptom from a broader output failure.
Watch the OBS preview through the affected point, then check the delivered stream at the same point. A local recording can also help: make one for diagnosis and review it alongside the preview and the viewer-facing stream. Avoid changing several settings between tests, or you may lose track of which change affected the result.
| What you observe | Where to investigate first |
|---|---|
| Preview and delivered stream both go black at the boundary | Source playback, visibility, scene stacking and the file boundary |
| Preview is correct, but the delivered stream is black | OBS output path and logs; keep the source settings under review, but do not assume they are the cause |
| The whole picture is black, not just a transition | Confirm the active scene and sources, then compare preview, recording and delivered output |
| Audio continues while video goes black | Check the video source’s playback and visibility separately from audio continuity |
| The symptom occurs after the playlist ends | Check whether the source is set to repeat or what it does at end of playback |
This is a sorting step, not a diagnosis. A black preview makes a source or scene path worth checking first; a correct preview with a black delivered stream points you towards output investigation. If the symptom is intermittent, note the time and item boundary so you can compare evidence from the same event rather than relying on memory.
If you are building a loop from recorded material, keep the media preparation and the live output as separate questions. The guide to testing a prerecorded kirtan stream before making it public is useful for checking a complete programme before a public run; here, the aim is to isolate the transition itself.
Check the OBS preview at a file boundary
Keep OBS visible and watch the preview as the current file reaches its end. If you can, make a local test recording at the same time. The preview shows what the scene is currently drawing; the recording gives you another local reference, while a private or otherwise controlled live test shows what is delivered to YouTube. Compare the same boundary in each rather than comparing unrelated moments.
If both preview and recording show black, do not start by changing YouTube ingest or encoder settings. Inspect the source that should be visible, whether playback has ended, the source’s visibility, and the order of sources in the scene. A source lower in the Sources list may be covered by another visible source. If the scene contains a background, confirm it is still present and visible as the clip changes.
If preview is clean but the recording is black, repeat the test and confirm that you are recording the same scene and output you are watching. If preview and recording are clean but YouTube is black, investigate the delivered path. The distinction matters: changing playlist settings cannot explain a picture that remains correct in OBS, and changing output settings at random can create new problems without addressing a local black preview.
For channels that also use still images or cover art between spoken or musical segments, make sure those elements are intentionally part of the scene rather than relying on an ended video source to leave a useful frame behind. The practical checks in adding podcast cover art to an always-on YouTube stream can help when the intended picture is a persistent visual, not a transition effect.
Loop one file with Media Source
For one local video, OBS documents Media Source as the source type for media files. Add or select the Media Source in the intended scene, confirm it points at the correct file, and enable Loop if that file should repeat. OBS describes Loop as repeating the file after playback completes. It is a playback control, not a guarantee about every decoded frame or about transitions between different files. See the OBS Media Sources documentation for the available properties.
Check the file path as well as the setting. A source aimed at a moved, renamed or different file may not be playing the content you think it is. Test the intended file from its actual location, and check that it opens and plays through its end. If you replace or prepare a file, update the source deliberately and test again before the live run.
Do not confuse repeating one file with looping a playlist. A single Media Source with Loop enabled repeats that source’s file; it does not sequence a folder of different clips. If your programme consists of separate items, use a playlist source and examine its own settings rather than adding multiple Media Sources and expecting one source’s Loop control to coordinate them.
A single continuous programme file can be a useful test when the black interval occurs specifically between separate items. It removes separate playlist item boundaries from that test, but is not an official, independently verified fix and may not address a problem elsewhere in the scene or output path. Keep the original clips, prepare the continuous file carefully, then check its internal joins and playback in OBS before relying on it.
If a long-running channel is built from a fixed recording, some operators prefer not to leave a desktop machine responsible for playback overnight. StreamNeo can remove the need to keep your own computer on for the broadcast, but it does not diagnose an OBS playlist boundary; establish whether the file itself and the intended sequence are right before changing how you host the stream.
Check end-of-playback visibility behaviour
A black interval after a file ends can be an end-of-playback behaviour rather than a failed live connection. OBS documents the Media Source option “Show nothing when playback ends”: when enabled, the source is hidden after playback finishes. If the source is not looping, reaching the end can therefore leave the scene without that video picture. Check this setting when the black appears after completion, and verify what other visible sources remain underneath it.
Also inspect “Close file when inactive” if the source is hidden and later shown, or if scene changes coincide with the symptom. Visibility and playback are related but distinct: a source can be hidden because it is not on the active scene, and a source’s playback handling while inactive can affect what happens when it becomes visible again. Test the actual scene changes you use rather than toggling settings without a repeatable case.
For VLC Video, OBS provides Visibility Behaviour options that determine whether playback continues, pauses or stops while the source is not visible. If your playlist is in a scene that is temporarily inactive, or a source is covered or hidden, inspect the selected behaviour. Test hiding and showing the source deliberately, then watch preview through the next boundary. This can reveal whether the issue tracks visibility rather than a normal transition from one playlist item to another.
Finally check the Sources order and scene contents. A source may still be playing but obscured by a colour source, image, browser source or another video above it. Conversely, the video may disappear and reveal an empty scene. A visible fallback background can make the intended state clear, but it does not make a transition gapless and should not be mistaken for proof that the file handoff is fixed.
Loop several files with a VLC playlist
For multiple local files, OBS documents VLC Video as the playlist source. Add the intended files to that source’s playlist and enable Loop Playlist if the list should start again after it runs out of media files. OBS describes this as restarting the source after the playlist is exhausted; it does not say that the handoff between each distinct file is gapless.
Check the list itself. Confirm that the right files are present and that their order is the order you expect. If order changes unexpectedly, inspect Shuffle Playlist. Confirm that the files can be opened and played, and check the boundary that produces the symptom. A broken or unsuitable file, an unexpected list order, and a playlist that has simply ended are different problems and call for different checks.
A helpful test is to use a short, known-good playlist in a controlled scene, then watch both preview and a local recording at the boundary. Keep other sources out of that test scene if possible. If the test behaves differently from the original, add the other scene elements back one at a time; that can expose an overlap or visibility change without assuming that the playlist itself is responsible.
If the playlist repeats only after its last item, do not expect Loop Playlist to erase the boundaries between its items. For recurring programming, compare retaining separate playlist entries with preparing a single continuous file and testing that file as a Media Source. The latter avoids separate playlist items in principle, but the available documentation does not establish it as a remedy for every black interval. Keep a recording of the test and verify the exact joins.
Channels that combine music, ambience or devotional recordings may also need to check that video and sound remain aligned across the boundary. If the picture is restored but the sound pauses or restarts differently, the separate audio symptom deserves its own test; see how to fix an ambience stream that loses audio after looping.
Verify VLC and OBS architecture compatibility
VLC Video requires VLC to be installed. OBS’s documentation specifies that a 64-bit OBS installation requires 64-bit VLC. Confirm the architecture of the OBS installation you actually run, and install the matching VLC version from the vendor’s official source if it is missing or mismatched. Do not infer compatibility only from the computer’s operating system: the relevant check is the application architecture.
After confirming installation, reopen OBS if needed and test the VLC Video source again. Verify the playlist is populated and that the source can play each entry. If the source does not appear or behaves inconsistently, note the exact symptom and consult OBS’s documentation and log before reinstalling unrelated components. Keep a record of changes so you can return to the prior state.
This compatibility check is not evidence that architecture mismatch caused every black transition. It is one prerequisite for the documented VLC playlist route. If VLC loads and plays the files, but the preview still goes black at a particular boundary, return to the source, visibility, file and scene checks rather than treating installation as a complete fix.
Inspect output and logs if preview is correct
When OBS preview remains correct through the same moment viewers see black, move attention to the output path. Confirm that the intended scene and stream output are active, then inspect the OBS log for errors or warnings around the time of the event. Logs can provide clues, but a message by itself is not proof of a cause. Preserve the log from the affected session and note when the black interval occurred so the evidence can be correlated.
Repeat a controlled test before changing encoder, output or network settings. Check whether a local recording is correct while the delivered stream is not; that pattern supports investigating beyond the source preview. Change one relevant setting at a time, then reproduce the same boundary and compare again. If the preview is black too, return to local playback and visibility checks instead of making speculative output changes.
Do not treat YouTube’s HLS guidance as a fix for an OBS playlist handoff. The YouTube Help page on setting up an HLS stream describes HLS ingestion requirements; it does not establish that those requirements explain a local black interval between OBS files. Apply documentation to the part of the system it actually covers.
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 my YouTube Live stream black between playlist videos?
There is no single confirmed cause for every setup. Compare OBS preview with the delivered stream at the same boundary, then check source playback, visibility and scene stacking if preview is also black; if preview is correct, inspect output and logs separately.
Does OBS Loop Playlist make transitions between files seamless?
No such guarantee is documented. OBS describes Loop Playlist as restarting the source after it runs out of media files, so test the actual boundaries you plan to broadcast.
What should I use to loop one video file?
Use an OBS Media Source, confirm the intended file is selected and enable Loop if it should repeat. Also check “Show nothing when playback ends” if the symptom appears after the file finishes.
Can one continuous file avoid a gap between separate clips?
It is a reasonable workaround to test because it removes separate playlist item boundaries, but it is not a verified fix for every cause. Check the joins in the prepared file and test it in OBS and a recording before using it live.