A black screen between product demo videos in OBS usually means a media source has ended or is not visible, or that the next source has not appeared yet. Check the clips’ end and inactive behaviour first, then source visibility, restart settings and transitions; rehearse the complete sequence before taking it to YouTube Live.
The key is to note exactly when the picture goes black and where: in OBS’s own programme output, or only in YouTube playback. A brief gap as a file reloads calls for a different check from a scene with no visible source.
Identify when the black screen appears
Watch the sequence in OBS and mark the moment the picture disappears: at the end of a clip, while changing scenes, when a hidden clip returns, or only in the YouTube player. Then note whether the sound also stops. These observations narrow the possibilities without assuming that YouTube or OBS is at fault.
A black interval that starts precisely as a clip finishes points towards that source’s end behaviour. One that occurs when returning to a scene may involve a file being unloaded and reloaded. If the preview looks right but programme output is black, check what is actually on the live output; if OBS output looks right but YouTube playback does not, keep the observation separate and investigate that path rather than changing source settings at random. This guide’s evidence does not establish a YouTube-specific cause for this symptom.
Reproduce the issue with the same clips, order and scene changes. Keep a simple note of the scene, the source that was active, and whether the output recovered on its own. If the sequence has a presenter camera, product close-ups or overlay graphics, include those too: a transition that works with one clip may behave differently with the actual layout.
For a straightforward file loop, the setup questions overlap with those in this guide to looping a long video for YouTube Live. Here, however, the aim is to locate the gap in an OBS sequence, not to change streaming software before identifying the cause.
Check what happens when each clip ends
Open the Media Source properties for each local demo clip and review “Show nothing when playback ends.” OBS documents this option as on by default: when the file completes, the source is hidden. If there is no other visible source underneath it, the scene can become empty and appear black.
Decide what the viewer should see after each product demo. It might be a holding slide with the product name, a presenter camera, the next clip, or an intentional transition to a different scene. The right arrangement depends on the show; simply turning an option off without deciding what should occupy the screen can leave a frozen last frame or an unintended layout.
Check every clip rather than only the first one. Sources can have different properties, and a sequence may mix short close-up videos with longer demonstrations. If only one source is configured to hide on completion, the gap may appear at just one boundary, which can make the symptom seem inconsistent.
OBS’s Media Sources documentation describes the relevant options and notes that labels or defaults can differ in the OBS version you use. Use the properties shown in your installed version, and test any change with the actual files. Don’t rely on a remembered default from another computer or an older tutorial.
A clean end frame does not necessarily mean the next source will be ready. The next source also needs to be visible, placed correctly, and either already playing or configured to start as intended. Treat the end of one clip and the appearance of the next as two separate checks.
Review what happens when a source is inactive
In the same Media Source properties, look for “Close file when inactive.” OBS says this unloads a media file when the source is hidden or not on the current scene to free memory. Its documentation also warns that, when the source returns, there may be a small period when it is not showing while the file reloads.
That behaviour is a plausible explanation if a clip appears normally on its first visit but produces a short blank when its scene returns. To test it, rehearse the same scene change with the option off and compare the output. Change one property at a time so you can tell whether the gap moved or disappeared; do not assume that a result on one clip proves every source is configured the same way.
There is a trade-off. Keeping a file loaded may avoid the documented reload interval, while unloading is intended to free memory. The practical choice depends on the computer, the clips and the scene collection. Test both settings under the conditions you plan to use rather than treating either as a universal fix.
A file that is off-scene is different from one that has reached its end while visible. For that reason, test both cases: let a clip finish in its scene, and separately switch away from and back to a scene that contains it. A short pause on return suggests a different lead from a black screen that begins exactly at the clip boundary.
Confirm the next source is visible
In the Sources list, inspect the eye icons for the outgoing and incoming clips, as well as any holding image or camera that should remain on screen. OBS’s overview explains that the eye controls whether a source is shown. A source can be present in the list and still be hidden, so presence alone is not proof that viewers can see it.
Then check source order. Sources higher in the list can cover items below them, depending on what they show. A full-frame image or video above the intended next clip may conceal it; a visible clip below an opaque layer can look like a failed source even when playback is running. Temporarily hide layers one at a time in a rehearsal to find what is covering the picture.
Confirm the incoming source is in the scene that actually goes live. With multiple scenes, the clip you can see in one scene may not be present in the one selected for programme output. If you use OBS Studio Mode, distinguish the scene in preview from the one currently live before concluding that the source has failed.
The OBS Studio overview covers scenes, sources and transitions. Its basic visibility and ordering mechanics matter particularly in demo layouts, where a product clip, logo, title card and camera may occupy the same canvas. Check the layout at the intended resolution and aspect ratio; an image outside the canvas or behind another source can be effectively absent even though its eye icon is on.
Set restart behaviour deliberately
The Media Source option “Restart playback when source becomes active” determines whether OBS restarts the file when the source is in the current scene and visible. OBS documents it as on by default. The visibility condition matters: changing the option alone will not explain why a source that remains hidden does not appear.
Choose the behaviour according to the role of the clip. If every entry should show a complete demo from the beginning, restarting on activation may suit that source. If you expect it to continue from its existing playback position after returning to a scene, a restart may instead make the show repeat part of the demonstration. Neither choice is automatically correct for every channel.
Test the setting by switching away and back, and by allowing a clip to reach its end before the next activation. Those are different events. A source that restarts as expected on scene entry might still be hidden at the end of playback, while one that does not restart could be continuing from its previous position rather than failing to load.
A narrow report, OBS issue #11040, described unreliable restarting after an immediate hide/show at playback end on OBS 30.2.0 under Windows 11. The issue report is not a universal timing rule, nor proof that it explains a current installation. If your sequence toggles a source immediately at the boundary, test that exact sequence in your own OBS version and avoid adding automated hide/show actions until you have seen them work reliably in rehearsal.
If you are comparing a playlist-driven arrangement with separate clips, remember that playback control is only part of the choice. A looping playlist for a scheduled live event has different operating questions from a set of manually controlled OBS scenes. Choose the arrangement that matches the show’s need for per-clip layout and operator control.
Inspect transitions and source order
A scene transition can make a boundary look intentional, but it cannot make an absent source appear. First verify that the incoming scene has a visible picture; then choose a transition that fits the change between demos. OBS includes Cut and Fade transitions, and its overview describes Studio Mode for preparing one scene before transitioning it to the live scene.
Use a cut when you want the next product shot to appear directly. A fade can create a deliberate pause between products, but if the incoming scene is empty the fade can simply reveal black. Test the actual duration and the complete layout rather than judging the transition from a preview of one still frame.
Check that the transition is applied to the scene change you actually make. An operator can prepare one scene in preview and leave another live, or use a transition that differs from the one expected at a particular boundary. During rehearsal, watch programme output, not just the editing canvas, and say aloud which scene should be live next. That simple check catches scene-selection mistakes before they reach viewers.
For separate Media Sources, give each demo a clear place in the sequence and confirm whether it should be shown alone or over another layer. If videos are a simple ordered sequence, OBS’s VLC Video source can use a playlist; OBS notes that VLC must be installed for this source type to appear, and that 64-bit OBS requires 64-bit VLC. A playlist centralises order, but does not provide the same per-clip scene and layout control as separate sources.
| Arrangement | Better fit | Checks to make | Trade-off |
|---|---|---|---|
| Separate Media Sources in scenes | Demos need different overlays, layouts or operator-controlled transitions | End behaviour, inactive behaviour, visibility, restart choice and source order | More control per clip, with more sources and scene setup to maintain |
| VLC Video playlist | Clips form a straightforward ordered sequence | Playlist order, loop and shuffle settings, visibility, and matching VLC installation | One central sequence, with less per-clip scene and layout control |
For more on the distinction between a playlist and repeatable playback, see this explanation of resuming a study stream’s playlist after a reboot. It addresses a different operating problem, but the choice between an ordered playlist and individually controlled segments is relevant when planning a sequence.
Rehearse the complete sequence before going live
Run the whole show from the opening scene through every product clip and back to the start if the programme repeats. Include the real transitions, overlays, scene changes and timing actions. A single clip test can confirm that a file opens, but it cannot show whether the next source is visible after the previous clip ends or whether a reload gap appears after switching scenes.
Observe the stream output in OBS as well as the programme’s YouTube playback in a controlled rehearsal. Note which view shows the black interval and at what point. If the black appears in OBS itself, continue with the source, visibility and transition checks. If it appears only in YouTube playback, you have established that the local output looks different; the material here does not identify the YouTube-side cause, so do not claim that a source property fixes it.
Keep a short run sheet with the expected picture at each boundary. For example: product A ends; a branded card appears; product B starts from its opening shot. Compare what you expected with what actually appeared. This makes it easier to distinguish a brief reload gap from a scene that has no visible source, a hidden clip, or a transition to the wrong scene.
For channels that need to continue playing while the operator’s computer is off, StreamNeo addresses the separate burden of keeping an uploaded video running as a YouTube live stream without leaving the computer on. It does not correct OBS source settings or diagnose a black interval in an OBS sequence, so resolve and rehearse this symptom in OBS before changing how the programme is delivered.
OBS recommends testing scenes, settings and stream smoothness before a first live stream in its Studio overview guide. For an OBS-based programme, that means testing the complete sequence on the computer and scene collection you intend to use. Repeat the rehearsal after changing a source property, a transition or the clip order; the change can affect what appears at the next boundary.
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 does OBS go black at the end of one product video?
Check “Show nothing when playback ends” on that Media Source. OBS documents that the option hides a source when its file completes; if nothing else is visible underneath or in the scene, the result can be an empty picture. Verify what should appear next before changing the setting.
Why does a clip briefly disappear when I return to its scene?
Check “Close file when inactive.” OBS says it unloads a hidden or off-scene file and warns there may be a short period without a picture while it reloads on return. Rehearse the same scene change with the option off to compare, using your own clips and OBS version.
Should I enable restart playback when a source becomes active?
Use it when you want the clip to start again on activation, and leave it off if the intended behaviour is to continue from its existing position. OBS documents restart as occurring when the source is in the current scene and visible, so check visibility as well as the setting. Test both scene entry and clip-end behaviour.
Is the black interval caused by YouTube?
Not necessarily. First determine whether the black picture is present in OBS’s programme output or only in YouTube playback. The evidence for this troubleshooting guide does not establish a YouTube-specific cause, so keep the two observations separate and investigate the output where the interval occurs.