A black screen between sermon videos usually means the clip ended, the OBS source was hidden or reloaded, or the scene or outgoing stream has a separate problem. Start by checking whether the scene is still visible in OBS at the moment the gap occurs; then choose the playback checks that match a single file or a playlist.
For one repeating file, OBS Media Source has a Loop option. For a sequence of local videos, VLC Video Source has Loop Playlist. These documented controls address common playback-end problems, but they do not guarantee perfectly gapless transitions across files or systems. Test the actual clips in the intended scene before a service.
Identify exactly when the screen goes black
First establish what “between videos” means in your setup. Does the picture disappear only when one sermon or announcement ends and the next should begin? Does it happen when you switch scenes, when a source is hidden and shown again, or at unpredictable times during a clip? Those distinctions matter: a playback setting is a sensible first check at a repeatable clip boundary, but it is not a complete diagnosis of a stream that drops at random.
If possible, reproduce the transition before service with the same scene and the same files. Keep OBS’s preview or output visible and, at the same time, look at the stream preview and status in YouTube Live Control Room. Note whether the gap starts exactly as a clip ends, whether it lasts until the next file appears, and whether audio continues. A brief written note such as “OBS preview stayed on the scene; picture went black after announcement file ended” is more useful than simply recording “YouTube went black”.
The symptom alone does not identify its cause. If the scene remains on screen in OBS but its video content disappears, investigate the media source and its playback behaviour first. If the entire OBS scene disappears or freezes too, broaden the checks to the scene, OBS output and encoder connection. If OBS looks normal while YouTube’s preview or stream status is degraded, treat that as a different layer of the setup rather than changing playlist options blindly.
This distinction also helps a volunteer hand over a useful report. Record which source type is in use, whether the file is meant to repeat, and what OBS and YouTube showed at the same time. For problems that look like an encoder interruption rather than a clip boundary, see the separate guidance on recovering a continuous stream after an encoder crash. That is a different fault pattern from one source reaching the end of its file.
Check OBS preview and scene visibility
At the boundary, check whether the scene itself is still present in OBS. If the preview continues to show the correct scene layout but the video area is black, look at the media source in that scene: is it still visible, does it appear to have ended, and is the next file or playlist item actually playing? If the whole preview changes or goes blank, inspect the scene selection and visibility before adjusting media playback.
OBS sources have visibility controls. A source that has been hidden, removed from the active scene or made inactive may behave differently from one that remains visible. This matters when a volunteer switches from a sermon scene to a holding slide and back. For a Media Source, OBS documents that Close file when inactive unloads the file when the source is hidden or not on the current scene; when shown again, there may be a short period while it reloads. If the gap occurs after a scene change, check this option in the source properties and consider whether unloading is needed for your setup.
For a VLC Video Source, review its Visibility Behaviour setting as well. OBS documents choices that determine whether playback continues, pauses or stops while the source is hidden; its documented default is to stop when not visible and restart when visible. If you expect a playlist to continue while another scene is displayed, that expectation may not match the selected behaviour. Decide deliberately: continuing can preserve the playlist’s position, while pausing or stopping may suit a source that should only play in its own scene.
Do not infer from a healthy-looking OBS preview that YouTube is necessarily receiving the same picture. The local preview helps locate a playback or scene issue; YouTube’s Live Control Room preview helps check what is reaching the platform. YouTube’s encoder setup and live-streaming guidance describes connecting an encoder and checking the stream preview. Use that preview alongside OBS, not instead of it.
Use Media Source for one repeating file
If the church is replaying a single local video—perhaps a recorded sermon that should run again after it ends—use OBS Media Source. This source is for an individual local audio or video file. Open its properties, confirm that the intended file is selected, and enable Loop if the file should repeat. A looping setting for one file is not the same control as looping a playlist.
Then examine what should happen at playback end. OBS Media Source includes Show nothing when playback ends. If enabled, the source can show nothing when its file finishes; that behaviour can explain a blank area or screen at the end of a non-looping file. If your source should always be showing a video, check that setting along with Loop. If the file is meant to play once and then reveal a holding slide, showing nothing may be intentional—but make sure the rest of the scene provides the picture you expect.
Keep the test narrow. Use the same Media Source and the same scene, play the file to its end, and watch the OBS preview. Confirm that the source remains visible and that the end behaviour matches the plan. If you change a property, repeat the transition rather than assuming the setting has fixed it. A file can loop and still have a visible transition; OBS’s documented option does not promise seamless playback at the boundary.
For continuous channels that use several recordings, the choice of playback method is a separate design decision. A church planning a programme from recorded services may find the discussion of streaming recorded services continuously from a Mac useful for thinking about the wider operating setup. It does not replace the source-specific check here: a single file in OBS and a list of files in VLC use different controls.
Use VLC Video Source for a playlist
If the sequence contains several local sermon, music or announcement files, use OBS VLC Video Source rather than treating each clip as one Media Source. Add the source, inspect its playlist, and verify both the files and their order. A missing item or an unintended order can look like a transition failure when the playlist has simply reached its end or moved to an unexpected item.
VLC Video Source requires VLC to be installed. OBS specifies that 64-bit OBS needs 64-bit VLC, so check that the installed VLC matches the OBS version’s bitness. If the source is unavailable or does not behave as expected, confirm this dependency before changing unrelated stream settings. The OBS Media Sources documentation covers both source types and their relevant properties.
When the playlist should start again after its final item, enable Loop Playlist. This setting applies to the playlist as a whole: OBS describes it as determining whether the source restarts after it has run out of media files. It does not mean that every individual transition is guaranteed to be invisible, nor does it fix a missing or unsupported file. Check the playlist end separately from the boundaries between clips.
Compare the two source choices before rebuilding the scene:
| Your material and intention | OBS source and setting to check | What to verify |
|---|---|---|
| One local video should repeat | Media Source; Loop | The correct file is selected and end behaviour matches the scene |
| One local video should play once | Media Source; playback-end options | Whether Show nothing when playback ends is appropriate |
| Several local videos should play in order and restart | VLC Video Source; Loop Playlist | Playlist contents, order, VLC installation and visibility behaviour |
| Playback should change when a source is hidden | Either source; visibility or inactive behaviour | Whether the source continues, pauses, stops or reloads as intended |
For a playlist that includes a holding slide, prayer, sermon and announcements, think through the final item as well as the ordinary clip changes. Loop Playlist concerns what happens when the list runs out; it is not a scheduling tool for deciding which scene should appear at a particular time. If you want to build a continuous playlist around OBS, the nonstop bhajan playlist settings guide is another relevant reference, while keeping in mind that your church’s files and scene layout still need their own test.
Check loop and playback-end behaviour
A loop option answers a specific question: should playback begin again after the relevant file or list reaches its end? For Media Source, Loop applies to the single file. For VLC Video Source, Loop Playlist restarts the list when it has run out of media files. Set the control that corresponds to what the source contains; enabling one does not substitute for the other.
Next check whether the source is expected to remain active. In Media Source properties, Close file when inactive can release the file when its source is hidden or absent from the current scene. OBS notes that showing it again can involve a small reload delay. That may be a reasonable resource choice for a source used only occasionally, but it is worth reconsidering if a scene change is followed by a conspicuous black interval.
For VLC Video Source, review visibility behaviour with the actual scene-switching plan. If the source stops when hidden and starts again when shown, a volunteer may see a restart or delay on returning to that scene. If it continues while hidden, the playlist can advance off screen, which may not be what you want if the next sermon is meant to begin only after a service leader selects the scene. There is no universally correct choice: decide whether hidden playback should continue, pause or stop, then test the choice.
A practical settings check is to write down the intended behaviour in ordinary language: “This sermon video repeats in the same scene,” or “These four clips play in order, then start the playlist again; if the scene is hidden, stop playback.” Match the source and options to that sentence. This avoids changing several controls at once and makes it easier for another volunteer to understand the setup later.
Test transitions with the actual files
Before a service, test the exact video files in the scene and playback source that will be used. Start early enough to observe the complete boundary between at least the clips that have caused trouble, including the last playlist item if the list should repeat. Watch OBS’s preview or output through the transition, then check the stream preview in YouTube Live Control Room. The purpose is to see which layer shows the gap, not to claim that one successful test rules out every future interruption.
Use files from the real programme rather than short substitute clips. The material may differ in format, duration, audio track or other properties, and the transition you need to diagnose is the one the congregation will actually see. Keep the scene, source visibility and playback settings consistent with the intended service. If you change a setting, note it and repeat the boundary test so you know what changed.
If OBS preview shows the clip ending and nothing replacing it, return to source type, loop and playback-end behaviour. If the scene remains healthy in OBS but YouTube’s preview or status shows a problem, inspect the encoder connection and YouTube’s live controls. YouTube also provides guidance for checking stream health and stream status; follow the current instructions for your account and encoder rather than assuming a source setting is responsible.
Write down the working configuration in a small volunteer handover note: which scene to use, whether the source is Media Source or VLC Video Source, whether it loops, what happens when hidden, and which files are in the playlist. This is particularly useful when the person diagnosing a problem is not the person who built the scene. It also prevents a late change to a file or source from going unnoticed before the next service.
Review other causes if the gap remains
If the OBS scene remains present and the source settings look right, inspect the media files and the way they are being played rather than immediately blaming YouTube. Confirm that each playlist entry points to the intended file and that the file can be opened and played in the intended source. Remove stale entries or correct their order, then test again. If a source is being hidden by scene changes, check the visibility behaviour and inactive-file settings against the actual scene plan.
If the entire local OBS output turns black, freezes or disappears, the problem is broader than a clip boundary. Check whether the correct scene is active, whether the expected sources are visible, and whether another scene element is covering the video. Compare what OBS shows with what YouTube receives. Avoid changing bitrate or network settings solely because one file transition is black; those settings are more relevant when the local output is healthy but the outgoing stream has a connection or encoder problem.
If OBS remains healthy but YouTube’s preview is missing or degraded, use Live Control Room’s status and encoder guidance to investigate the outgoing path. YouTube’s checks are separate from OBS’s file-playback controls. For an issue that behaves like recurring audio or video interruptions on a hosted stream, the FFmpeg interruption troubleshooting guide may help frame the distinction, though its setup is not the same as an OBS church scene.
Some churches choose a managed workflow when a particular recurring burden is keeping a computer available overnight to run a pre-recorded channel. In that situation, StreamNeo removes the need to leave your own computer running for the broadcast, but it does not change the OBS source diagnosis or guarantee gapless transitions between separate files. For a volunteer-led OBS setup, the direct remedy remains to match the source to the content, check playback and visibility behaviour, and test the actual files.
If a local scene and the YouTube preview disagree, retain the time of the incident, a note of which view was affected, and the relevant source settings. That gives the next volunteer or technical helper something specific to investigate. Do not treat a black interval as proof of one particular fault until you have compared the local scene and the platform view.
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
How do I stop a black screen between videos on our church YouTube livestream?
First check OBS at the moment the picture disappears. For one file that should repeat, use Media Source and check Loop; for several files, use VLC Video Source and check the playlist and Loop Playlist. Then confirm that playback-end and source-visibility settings match what you want to happen.
Should I use Media Source or VLC Video Source?
Use Media Source for one local audio or video file. Use VLC Video Source for a playlist of local files, and make sure VLC is installed with the matching bitness for OBS. The controls for repeating a single file and restarting a playlist are different.
Does Loop Playlist guarantee a seamless transition?
No. It tells OBS to restart the playlist after it runs out of media files, but it does not promise a perfectly gapless hand-off between separate files across all systems. Test the actual files in the intended scene and check both OBS and YouTube’s preview.
What should I check if OBS looks normal but YouTube is black?
Compare OBS’s local preview with the stream preview and status in YouTube Live Control Room. If the local scene is healthy but the platform view is not, investigate the encoder connection and YouTube’s current stream-health guidance rather than changing playlist settings without evidence.