First identify whether the scene uses OBS’s VLC Video source, a single-file Media Source, or the separate Media Playlist Source plugin. They behave differently, so the right check depends on which one is actually playing the gaming VODs.
There is no confirmed universal fix for a playlist that skips its first item. Check the source type first, then test its order, playback settings and version in a controlled scene before changing a live broadcast.
Identify the source before changing settings
In OBS, select the item in the Sources list and inspect its name and properties. A source name can be anything, so open its properties rather than assuming that “VOD playlist” tells you what type it is. The relevant types are the built-in Media Source, built-in VLC Video, and Media Playlist Source, which is a separate plugin.
Media Source is intended for an individual media file. VLC Video can play a playlist and depends on VLC being installed. Media Playlist Source adds playlist functionality through a plugin. OBS’s Media Sources documentation describes the distinction between Media Source and VLC Video; the plugin’s resource page describes the separate plugin.
Write down the exact source type before proceeding. Also note the OBS version, operating system, source settings, file order and what happens immediately before the skip. If a scene change or source-visibility change comes before the symptom, that detail may help narrow the investigation.
A useful first test is to make a temporary scene with only the relevant source and a few harmless local files. Do not use a live broadcast as your first diagnostic run. Note whether the first entry starts at all, whether it advances to the next entry, and whether the behaviour changes after hiding and showing the source. These are suggested checks, not a documented reproduction of this exact symptom.
If you are setting up a gaming rerun channel, the distinction between a local OBS list and the channel’s presentation matters in other ways too. For example, planning for different resolutions in a gaming rerun channel is a separate concern from which local file OBS plays first.
If it is VLC Video, check VLC architecture
VLC Video requires VLC. Check that VLC is installed and that its architecture matches OBS: the OBS documentation specifies that 64-bit OBS requires 64-bit VLC. If OBS cannot use the expected VLC installation, troubleshoot that dependency before changing the order of files or the YouTube stream settings.
Confirm the architecture of the OBS installation you actually run, then confirm the VLC installation. Do not infer either from the Windows version alone: a 64-bit operating system can run software built for different architectures. If you are uncertain, check the application’s About or installation information rather than installing additional versions at random.
After confirming the match, reopen the source properties and check that the expected playlist entries are present. If the source is newly configured, test it in the temporary scene. Keep a note of the exact change you make and its result; changing one variable at a time makes it easier to tell whether the dependency was relevant.
VLC Video exposes options for playlist order, shuffle, loop, network caching and audio tracks, among others. Those options can affect what you observe, but a playlist starting on the wrong entry is not automatically evidence of a VLC architecture issue. Architecture is a prerequisite check, not a diagnosis of the first-item skip.
If your channel uses long-form ambience or music alongside gaming VODs, keep playback testing separate from your content workflow. The practical setup considerations in streaming relaxing music with nature footage may help with that broader workflow, but they do not establish the cause of a local OBS playlist problem.
Verify order, shuffle, loop and visibility
Inspect the list in the source properties and confirm that the intended VOD appears first. If the list is shuffled, turn shuffle off for a test where the first item must be predictable. OBS documents VLC Video’s default shuffle setting as off, but an existing source may have been changed, so check its actual setting rather than relying on the default.
Check loop as well. OBS documents VLC Video’s loop default as on. Looping controls what happens at the end of the list; it does not prove that the first item should be skipped. Test a short sequence that ends cleanly, and observe whether the source advances through the entries and returns to the beginning as expected.
Visibility behaviour deserves particular attention in scene-based layouts. OBS documents the VLC Video behaviour as stopping playback when the source is not visible and restarting when it becomes visible. If a scene transition briefly hides the source, the next playback may look like a restart rather than a continuation. Test the same sequence with the source kept visible, then repeat with the scene transition that normally precedes the issue. Record what changes.
| Check | What to inspect | What the result can tell you |
|---|---|---|
| Order | The actual sequence in the source properties | Whether the intended VOD is truly first in OBS’s list |
| Shuffle | Whether shuffle is enabled | Whether playback order can vary rather than follow the displayed sequence |
| Loop | Whether the list repeats at its end | Whether end-of-list behaviour is being mistaken for a startup issue |
| Visibility | Stop/restart behaviour when the source is hidden | Whether a scene change alters playback or makes it appear to restart |
| Test files | A short local sequence in a temporary scene | Whether the symptom can be isolated from the live broadcast |
Do not change several of these settings at once. If you turn off shuffle, change loop behaviour, and restructure scenes in one pass, a successful test will not tell you which change mattered. Start with the actual list order, test shuffle separately, and then test visibility with the relevant scene transition.
For a single-file Media Source, do not apply VLC Video’s playlist settings. There is an OBS forum discussion about resuming a single pre-recorded file after switching away from its source; its advice about “Restart playback when source becomes active” concerns activation behaviour for that single-file source. It is not a proven fix for a playlist skipping its first entry. Keep that distinction in mind if you consult the OBS forum discussion.
If it is Media Playlist Source, check compatibility
Media Playlist Source is a plugin, not the built-in Media Source or VLC Video. Record both the OBS version and the plugin version, then compare them with the plugin resource’s stated requirements. If the plugin does not appear in the Add Source menu after installation, check the resource’s installation guidance and compatibility information rather than assuming the playlist itself is malformed.
Confirm you are editing the playlist in the plugin source you intend to use. Check that the expected VOD is first, and note whether any path is repeated. File paths can matter when a list contains the same file more than once, and the plugin’s update history includes a change related to repeated paths. That makes repetition worth testing, not proof that it is responsible in your case.
The plugin resource describes being able to edit the playlist without restarting playback and to save the current file across OBS restarts. These behaviours may suit a channel that changes its queue while running, but they differ from the needs of a fixed, predictable sequence. Compare the workflow you need with the resource’s requirements and current release notes before switching sources.
If you are comparing approaches for a continuous channel, consider whether the list must be edited during playback, whether the scene hides the source, and whether installing a separate plugin is acceptable for the machine that runs OBS. A setup built around a playlist is not the same as a single looping file; the useful choice depends on how often your queue changes and how you recover when a test fails. A 24/7 lo-fi stream built with OBS offers a related example of thinking through an always-on OBS workflow, not a diagnosis of this symptom.
Treat plugin release notes as leads, not proof
The Media Playlist Source update history for version 0.1.3, dated 13 April 2025, records fixes for continuing to the next item after a scene transition and for continuing when a file path repeats. These are relevant leads if your setup uses that plugin and the circumstances match. They do not confirm that the plugin caused the reported first-item skip, nor that installing that version will fix it.
Compare the release notes with what you actually observe. Does the issue occur only after a scene transition? Does it involve a repeated path? Can you reproduce it in a temporary scene without either condition? Answers help decide whether a release note is pertinent, but do not convert a resemblance into proof. The plugin’s update history is the primary place to check its changes and their dates.
Before updating or changing a production setup, save the current scene collection and note the plugin version. If possible, test the new version in a copy of the scene collection first. Follow the resource’s own installation and compatibility guidance. Avoid removing or replacing a plugin in the only working production setup without a recovery plan.
If the problem persists, collect the OBS log, operating system, exact source type, OBS and plugin versions, playlist order, and steps that reproduce the issue. Include whether a scene transition or repeated path is involved. A reproducible example is more useful to support than a report that says only that the first gaming VOD was skipped.
Keep the OBS list separate from YouTube history
An OBS media playlist is a local playback list. It is not the same thing as a playlist on your YouTube channel, a list of past live streams, or YouTube’s ingestion process. Changing a YouTube playlist or looking at channel history will not by itself change the order configured in an OBS source.
YouTube’s HLS ingestion guide discusses an encoder submitting media segments and sequence numbers. That concerns how a live encoder supplies its stream. It does not establish a cause for OBS skipping an item in a local video playlist. YouTube’s live-streaming Help page is useful for the platform-side live workflow, but it does not replace checking the OBS source.
Keep the layers separate while troubleshooting: OBS selects and plays local media; the encoder sends the live output; YouTube receives and presents the broadcast. If OBS’s preview already shows the wrong file or a restart, start with the source and scene behaviour. If OBS preview is correct but viewers see a different result, then investigate the output and platform side as a separate issue. Do not infer that the local playlist and YouTube’s HLS segment list are interchangeable because both are called playlists.
A channel that needs to keep broadcasting while the computer is off has a different operating requirement from this OBS-specific diagnosis. StreamNeo can remove the need to leave an OBS computer running by turning an uploaded video into a YouTube live stream, but that does not alter an OBS playlist or explain why its first item was skipped. Keep this troubleshooting path focused on the source actually used.
A safe test and recovery sequence
Use a copy of the scene collection or a temporary scene, and choose short local files that are safe to play. Add only the source under investigation. Verify the first entry in its properties, then start playback and watch whether it starts on that entry, advances, and responds to a hide/show or scene transition. Repeat only the condition relevant to your normal setup.
For VLC Video, first confirm VLC is installed with the matching architecture, then inspect order, shuffle, loop and visibility behaviour. For Media Playlist Source, note plugin and OBS versions, check the resource requirements and release notes, and test transition or repeated-path conditions if they apply. For Media Source, remember that it handles one file; its activation controls are not playlist controls.
Keep the original source and settings intact until the test gives you a clear result. If a change helps, make it in the production scene deliberately and verify the output before relying on it overnight. If it does not help, revert it and preserve the log and reproduction steps. This avoids accumulating changes that obscure the original problem.
There may be a source configuration or version-specific cause that these checks do not reveal. The available documentation narrows the relevant paths, but it does not identify one universal cause for the wording in this title. When seeking help, give the exact source type, versions, file order, scene sequence and log so others can distinguish a local playback issue from a live-output issue.
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
Does the Media Playlist Source plugin cause the first VOD to be skipped?
There is no confirmation that the plugin is the cause of this exact symptom. Its release notes document fixes involving continuation after a scene transition and repeated file paths, which are useful leads only if those conditions match your setup. Check your source type and reproduce the behaviour before drawing a conclusion.
Is VLC Video the same as Media Source?
No. OBS’s standard Media Source handles an individual media file, while VLC Video can play a playlist and requires VLC to be installed. Use settings for the source type you actually have, rather than transferring playlist advice to a single-file source.
Does YouTube’s playlist or live history control OBS’s file order?
No. The local order is configured in the OBS source. YouTube’s live ingestion documentation describes encoder-submitted segments, not the ordering of files in an OBS media playlist.
What should I send when asking for help?
Include the exact OBS source type, OBS and plugin versions if applicable, operating system, playlist order, and a short sequence of steps that reproduces the issue. Include the OBS log and note whether a scene transition, visibility change or repeated path is involved. These details narrow the investigation without assuming a cause.