First find out where the missing video disappears. If it is absent from OBS’s preview or a local recording, check playback, playlist settings and scene visibility; if those are continuous but viewers see a gap, investigate stream delivery or a YouTube interruption instead.
A report that a Media Source or playlist “resets” is a useful clue, not a rule that applies to every OBS version or source. Work through the checks below before changing several settings at once. That gives you a better chance of identifying the cause without replacing a sound setup with a new one.
Find out where the video disappears
Write down what “skip” means in your case. Is a particular file missing from the sequence? Does the picture freeze, jump forward or go black? Does the stream end or show a YouTube notice? These symptoms point to different parts of the path from file to viewer.
Compare three views, as close together in time as you can: the OBS preview, an OBS local recording, and the YouTube live player or Live Control Room. If you cannot record while live, make a short test recording with the same scene and playback settings. Note the file that was meant to play, the time of the event, and whether the source was visible in the active scene.
| What you observe | First area to investigate |
|---|---|
| The file is absent or advances unexpectedly in OBS preview and the local recording | Source type, playlist entry, file readability, playback controls or visibility behaviour |
| Preview and recording look continuous, while YouTube viewers see frozen or missing frames | OBS dropped-frame statistics, rendering or encoding load, and outbound connection |
| YouTube replaces the picture, shows a warning or ends the broadcast | Live Control Room notices, including possible copyright or Community Guidelines action |
| Only one file causes trouble, even when tested alone | That file’s path, readability, format or encoding; the extension alone does not prove compatibility |
A delayed YouTube player can make comparisons confusing. Check the event against the same approximate point in the recording, rather than assuming the preview and live player are showing the same moment. Ask a viewer what they saw and when, but use the OBS recording and dashboard as your own evidence.
If you need background on a different playback setup, the guide to streaming a playlist of lectures with OBS covers the broader arrangement. Here, the immediate task is to locate the first point at which the intended video is missing.
Check the OBS preview and local recording
Start with the preview. Watch the transition into and out of the affected file, not just the moment after it has disappeared. A source may fail to load, finish and stop, or become inactive during a scene change. Check whether the next item appears as expected and whether audio follows the same pattern.
Make a local recording using the scene and sources you actually use for the stream. A short recording is useful for reproducing a problem, but if the skip is rare, keep a longer test only if your computer has enough storage. Compare the recording against the playlist order and mark the time of each transition. You do not need to infer a cause from a single frozen frame; look for a repeatable relationship, such as a particular file, scene switch or period of high system load.
If OBS preview and recording both omit the same file, begin with local playback. Verify that the file still exists at the path used by OBS and opens outside OBS. Then add just that file to a test source. A known-good file in the same source makes a useful comparison. If the known-good file plays and the affected one does not, the issue may be tied to the file or its encoding rather than the playlist as a whole.
OBS lists supported file types for Media Source, including common video containers such as MP4, MOV, MKV and WebM. A supported extension does not establish that every codec or file encoded in every way will play correctly. If the file fails alone, check how it was created and whether a fresh export in a compatible format behaves differently. Keep an untouched copy before converting anything.
When the preview is continuous but the local recording has a problem, the recording path may add useful evidence about rendering or encoding. Check OBS’s Stats window during a repeatable test, including rendering and encoding indicators, rather than changing playlist controls immediately. OBS notes that rendering scenes and sources use GPU resources; a complex scene or high-resolution media can increase the work. Simplifying the scene or testing a lower-resolution copy can help establish whether load is involved, but treat that as a test, not a diagnosis.
Inspect Media Source or VLC playlist behaviour
The built-in Media Source and VLC Video Source have different jobs. OBS documents Media Source as a source for an individual local file, with a Loop control to replay that file. VLC Video Source is the documented choice for a playlist of local media files. If you are trying to queue several study videos, first make sure the source you chose is intended for a playlist rather than expecting one Media Source to behave as a queue.
The VLC source relies on VLC being installed, and OBS specifies that 64-bit OBS needs 64-bit VLC. If a VLC playlist is missing or fails to behave as expected, confirm the installation and architecture as well as the playlist contents. The OBS Media Sources guide describes the available controls and their intended behaviour; the settings in your installed version are the ones to inspect.
For VLC Video Source, check the playlist itself and the playback options. Loop Playlist determines whether the list starts again when it reaches the end. Shuffle Playlist determines whether items play in a randomized order rather than the order you arranged. If your study stream depends on a set order, make sure shuffle is not changing it. If you expect the sequence to repeat, confirm that looping is enabled.
Visibility Behaviour matters when a source is not shown in the current scene. OBS documents choices that determine whether playback continues, pauses or stops while hidden; its documented default is to stop when not visible and restart when visible. A scene transition that hides the source can therefore affect playback depending on the selected behaviour. This is a setting to verify against your scenes, not proof that every playlist resets when hidden.
Media Source also has a “Restart playback when source becomes active” control. That may be appropriate when a source should begin at the start each time it appears, but it can produce an unexpected restart if you expect playback to continue through a scene change. Check the control and test the actual scene sequence. Do not turn it off or on as a blanket fix: the right behaviour depends on whether the source should resume, restart or stay hidden.
If one file works alone but the playlist fails at its transition, inspect the playlist entries and try a small test list with the same files. Add files back in a controlled way if the smaller list works. For a library containing varied formats, the guide to preparing a playlist with mixed audio codecs may help you think about file consistency. It does not mean an audio codec is necessarily the cause of a missing video.
Check whether a hidden or edited source resets
A source can be affected by what happens to the scene around it. You might switch scenes to show a timetable, hide a media source temporarily, or edit its properties while the stream is running. Depending on the source and its settings, becoming inactive may pause or stop playback, and becoming active may restart it. Reproduce the same action during a local test and note whether the source resumes at its old position or begins again.
This is especially worth checking if the sequence restarts after an operator action rather than at a consistent file boundary. List the actions that happen around the event: scene changes, source visibility toggles, property edits, or changes to the playlist. Test each action separately. If a restart follows one action reliably, that is stronger evidence than a report that a source type always resets.
Some OBS users have reported resets after adding a Media Source or a video to a VLC playlist. Such a report can suggest what to test, but it does not establish universal behaviour or a current-version defect. OBS versions, source settings and scene arrangements differ. Record your version and actual settings, and avoid changing several controls together in response to someone else’s setup.
If the source is meant to run continuously, consider whether it needs to be present in every active scene or whether the chosen visibility behaviour suits the way you switch scenes. Make a copy of the scene collection before changing a live setup. Then test the change in a local recording or an unlisted stream, if appropriate, before relying on it overnight.
Separate playback skips from dropped frames
Dropped frames are not the same as a playlist advancing past a file. If the local preview and recording show continuous playback but the viewer sees freezes, missing frames or a blocky image, inspect OBS’s stream statistics while the issue occurs. OBS describes dropped frames as a sign that the connection is unstable or cannot sustain the configured bitrate. It recommends investigating the connection; lowering bitrate can reduce drops in some cases, but also reduces picture quality and does not address the underlying connection problem.
Check the Stats window for dropped frames, rendering lag and encoding lag. The labels help separate network delivery from the work OBS is doing locally. If dropped frames rise while the local picture remains intact, test the outbound connection and whether other devices or uploads are competing for it. If rendering or encoding indicators rise instead, reduce scene complexity or test a lower output resolution to see whether the event changes. Do one test at a time and keep a note of the result.
A continuous local recording is useful evidence, not a guarantee that every viewer receives every frame. OBS and YouTube are separated by your outbound connection and YouTube’s ingest and playback path. You can compare the encoder output with the live dashboard and a local archive, then follow YouTube’s live-stream troubleshooting guidance if the encoder output looks healthy but the viewer experience does not.
For a 24/7 channel, a connection that works during a short daytime test may still be affected by congestion or interruptions at another time. Note when the problem occurs and whether the dropped-frame count changes. If your setup uses a metered connection, the guide to reducing data use on a 24/7 stream discusses the trade-off between stream settings and data use; do not lower bitrate without checking what it does to the picture and whether it resolves the observed drops.
Check for a YouTube-side interruption
Consider YouTube as the cause when the whole broadcast is interrupted, replaced or ended, rather than when a local playlist silently moves past one file. Check the Live Control Room and YouTube Studio for warnings or notices around the time of the event. YouTube scans live streams for third-party content matches and may replace the picture, warn the creator, or interrupt or terminate a stream in relevant cases. A dashboard notice is more useful evidence than guessing from a viewer’s description.
Copyright claims and strikes are not interchangeable, and a playback symptom alone does not tell you which, if either, applies. Check YouTube’s current official guidance and the specific notice in your account. The article on copyright claims versus strikes on live streams can help you understand the distinction, but the current YouTube notice should guide what you do next.
A policy-related interruption is also separate from whether a repeated study stream is eligible for monetization. YouTube’s policy update describes “inauthentic content” in relation to repetitive or mass-produced material and says monetization requires material variation and creative, educational or other value. That does not mean every looped stream is automatically disallowed, nor does it explain a file missing from OBS preview. Check YouTube’s current policy pages for your own channel and content.
Test one change at a time
Once you know where the symptom occurs, make a small test plan. Start with the simplest reproducible case: one affected file alone, then one known-good file, then the intended playlist. Keep the scene and stream settings unchanged while comparing them. If the problem only happens after a scene change, reproduce that scene change with the same media. If it appears only on YouTube, keep watching the OBS statistics and dashboard rather than repeatedly rebuilding the playlist.
Change one relevant setting per test and record what you changed, what you expected, and what actually happened. For example, if a playlist restarts when its scene becomes active, first test Visibility Behaviour while leaving shuffle and loop unchanged. If one file fails in isolation, do not simultaneously change the playlist order, encoder and bitrate; you will not know which change mattered.
Before a long unattended run, make a local recording long enough to include the transitions that normally fail. Check the start, a file boundary, a scene change if you use one, and the point where the list loops. A short test can rule out a basic setup error, but it cannot show that a rare overnight issue has been fixed. Keep the previous working scene collection and write down how to restore it.
If the evidence still does not identify the cause, collect details before asking for help: OBS version, operating system, source type, playlist settings, file formats, whether each file plays alone, the time of the event, and whether it appears in preview, local recording or only on YouTube. An OBS log from the affected session can also help. Remove stream keys and other private information before sharing it publicly. This is more actionable than saying only that OBS “skips videos”.
If the recurring problem is that a computer must stay on and playback must be watched through the night, that is a separate operational burden from diagnosing a bad file or dropped frames. StreamNeo turns an uploaded video into a YouTube live stream, so you do not have to keep your own computer running for that part of the job. It does not establish why an OBS playlist skipped a file, and YouTube remains the destination.
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 my OBS playlist start from the first video again?
Check whether the source became hidden or active, whether its visibility behaviour stops playback, and whether “Restart playback when source becomes active” is enabled for a Media Source. A restart can depend on the settings and scene changes in your setup; it is not a universal behaviour of every source. Reproduce the same scene action in a local recording before changing other controls.
Should I use Media Source or VLC Video Source for several study videos?
OBS documents Media Source for an individual file and VLC Video Source for a playlist. VLC Video Source requires VLC to be installed, with matching architecture for 64-bit OBS. Choose based on whether you need a queue, the intended file order and what should happen when the source is hidden.
How can I tell whether YouTube or OBS caused the missing video?
Compare OBS preview, an OBS local recording and the YouTube player or Live Control Room. If the local views are continuous but viewers see freezes, check stream statistics and outbound delivery; if YouTube shows a warning or replaces the picture, inspect the dashboard notice. A file missing locally points first to playback or source configuration, not automatically to YouTube.
What should I include when asking for help?
Share your OBS version, source type, relevant playback and visibility settings, file formats, and whether the problem appears in preview, recording or only on YouTube. Include a log from the affected session if possible, with stream keys and private details removed. Say whether the affected file plays by itself and whether a scene change preceded the event.