OBS can loop a VLC Video playlist when it reaches the end, but that is not the same as changing content every six hours. For a scheduled change, put each content block in its own scene and use timer-based scene automation; treat this as a configuration approach to verify, not a tested recipe that works identically in every OBS version.
First decide what you mean by “rotate”: repeat one list, switch between different lists on a clock, or stop and restart the YouTube broadcast. The first two can be handled inside OBS in different ways. A six-hour playlist rotation does not, by itself, mean that you need to end the live broadcast.
What “rotate every six hours” can mean
The phrase can describe several different outcomes. You might want one list of videos to start again when its final file finishes. You might want a morning block to give way to an evening block at a chosen time, whether or not the current file has finished. Or you might mean that the live broadcast itself should end and a new broadcast should begin. These are separate behaviours, and choosing the wrong one can leave your stream showing the wrong content or interrupting the broadcast unnecessarily.
If the same collection can play in the same order repeatedly, an end-of-list loop may be enough. Its timing depends on how long the media items run; the loop does not count six hours from a chosen start time. If you need a block change on a clock, such as devotional material changing to a different set every six hours, you need a timed action that switches the displayed scene or otherwise changes the active source.
A third possibility is to replace or update media while the stream stays live. That is not automatically the same as scheduled scene rotation. If you are changing a demo playlist rather than switching fixed blocks, the process in updating an FFmpeg playlist without stopping YouTube Live covers a different workflow and toolchain. Keep the broadcast-level decision separate from the content-level decision.
Write down the intended behaviour in plain terms before opening OBS: “repeat this list when it ends”, “show scene B six hours after scene A starts”, or “end the broadcast and start another one”. For this article, the main case is switching between content blocks while the YouTube live stream remains active. That distinction makes it easier to configure and test the right mechanism.
What the OBS VLC Video source loops
OBS provides a VLC Video source for playing media files as a playlist. The OBS Media Sources guide says VLC must be installed for the source to be available, and that 64-bit OBS needs 64-bit VLC. Add the source in a scene, then add the local files you want it to play. For a fixed sequence, leave shuffle off; enable it only if you actually want the order to vary.
The source’s Loop Playlist option means that the source restarts after it has run out of media files. In practical terms, the final item finishes, then the list begins again. This is useful for a collection that should repeat without someone manually returning to the first item. It does not set a delay, start time, or recurring six-hour alarm.
You should also decide what happens to a VLC source when its scene is not visible. OBS exposes a Visibility Behaviour setting that determines whether playback continues, pauses, or stops while hidden. The appropriate choice depends on your plan. If you expect the next scene’s playlist to be ready at the moment of the change, check whether it has been playing in the background or needs time to start. If you want hidden media to remain stopped, account for its start-up behaviour in the transition test.
Keep the job of this source simple: play the files in its playlist and, if wanted, repeat them at the end. The OBS Sources guide explains the broader distinction between sources and scenes. A scene is the composition you show; a media source is one item in that composition. Thinking in those terms will help you avoid expecting a playlist control to perform scene scheduling.
Why playlist looping is not a six-hour timer
A loop is event-driven: the list reaches its end, and the source starts over. A timer is clock- or elapsed-time-driven: a scheduled action occurs after a chosen interval, regardless of whether a file is near its end. Those triggers can coincide by chance, but they are not interchangeable. If a list runs longer than six hours, a loop will not force it to change at the six-hour mark. If it runs for less time, it may loop more than once before six hours have passed.
The difference matters when your content has a purpose or a schedule. A local news loop might need a refreshed block at a known point in the day. A study channel might use one block for quiet music and another for a planned break. A bhajan channel may simply want its set repeated continuously, in which case end-of-list looping could be the more direct choice. Start with the viewer-facing requirement rather than with a control that happens to contain the word “Loop”.
There is also a difference between changing scenes and restarting a YouTube broadcast. A scene change alters what OBS sends as the programme while the broadcast is already active. Ending and starting the broadcast is a separate action with its own consequences for the viewing session. Do not assume a scheduled content change requires restarting YouTube Live, and do not assume a scene switch guarantees every aspect of the broadcast behaves as intended. Verify what viewers see and hear in your own setup.
For a single collection that should repeat forever, the VLC loop setting avoids adding a timer system that you do not need. For a sequence of distinct blocks, the timer is a separate layer. The guide to looping educational videos with FFmpeg is relevant if you are comparing a file-processing approach, but its FFmpeg workflow should not be confused with OBS’s VLC source controls.
Create separate scenes for content blocks
For timed rotation, make a scene for each block you want to show. For example, a channel might have one scene for its first recorded set and another for the next set. Put the appropriate VLC Video source and playlist in each scene, and give the scenes names that are easy to distinguish in OBS and in any automation rule. Avoid names such as “Scene 2” if you will later need to identify the intended target quickly during a test.
Before adding automation, select each scene manually and confirm that the picture is framed correctly, the audio is at the intended level, and the playlist contains the right files in the right order. A scene can include more than the playlist: it might contain a logo, background, or text overlay. Check these elements in every block rather than assuming that a correctly configured first scene means the rest are ready.
Consider how playback should behave in scenes that are not on air. If a playlist continues while its scene is hidden, returning to that scene may show a later point in the media. If it pauses or stops while hidden, returning may resume or restart depending on the source behaviour and settings. Neither choice is universally right. The relevant choice is the one that matches the schedule you intend, and you should observe it directly during a short test.
Keep transitions modest until you have confirmed the switch. A cut is easier to diagnose than a complicated transition if the outgoing and incoming audio overlap unexpectedly or the picture appears late. Once the basic scene change behaves as intended, you can decide whether a different transition suits the channel. If your concern is the computer handling a long-running OBS broadcast as well as the scene changes, the advice on monitoring CPU and network usage for an OBS stream can help you think through what to watch, though the hardware and environment will differ.
Use a timer macro to switch scenes
OBS itself does not make the VLC playlist loop control into a six-hour scheduler. One possible route is the Advanced Scene Switcher plugin, using a macro to trigger a scene change on a timer. The plugin’s macro properties documentation describes the kinds of conditions and actions available, and its OBS forum thread is a place to check current plugin discussion. These sources support the general automation concept; they do not establish a complete six-hour recipe tested across all plugin and OBS versions.
At a high level, the configuration has three parts: a condition that represents the intended interval, an action that selects the next scene, and a decision about when the timer begins or resets. You might want the schedule to start when you manually begin the stream, or you might want it to align with a particular wall-clock time. Those are different requirements. Confirm which timing model the installed plugin version supports before relying on it.
If you create a macro, make its intent explicit. Identify the scene it should switch to, decide whether the action should repeat or alternate between destinations, and check what happens after OBS is restarted. Do not assume a timer will resume at the correct point after an application restart, a plugin reload, or a temporary connection issue. The source material does not establish those behaviours for every setup, so test them locally rather than inferring them from a macro label.
A scene-switching rule also needs a sensible fallback. If the incoming source is missing a file or fails to play, you need to know what will be sent to the audience and how you will notice. During initial testing, keep OBS visible and observe the programme preview and audio meters at the change. If you cannot monitor the switch live, arrange a recording or another way to review what happened before treating the configuration as unattended.
Test timing and recovery behaviour
Do not wait six hours for your first useful test. First confirm that each playlist plays, that the selected scenes show the correct material, and that a manual scene change works. Then test the timer using a short interval supported by your installed version, if available. This checks whether the rule fires and targets the intended scene without making you assume that a successful short test proves every long-run behaviour.
When you do a longer rehearsal, check the points that affect the audience: whether the change happens when expected, whether there is a blank or frozen picture, whether audio is interrupted or doubled, and whether the incoming playlist starts at the point you expect. Also check whether the macro fires once or repeats unexpectedly. If the source is set to continue while hidden, it may have advanced before its scene appears; if it pauses or stops, the first moments after the switch may be different. Record the result in your own notes, including OBS and plugin versions, so a later update does not leave you relying on memory.
Test recovery, not only the happy path. Close and reopen OBS in a controlled rehearsal, then verify whether scenes, source settings, and automation remain configured as you intended. If you can safely test a brief interruption, observe whether the stream resumes with the expected scene and whether the schedule remains aligned. Do not create an interruption during an important live programme just to satisfy a checklist. There is no universal claim here that every setup recovers in the same way.
OBS’s Quick Start Guide recommends testing before relying on a stream. That is especially relevant when automation is involved: a scene switch that looks plausible in a settings panel still needs to be seen in the actual programme output. If your channel is intended to run continuously, consider a separate, low-stakes rehearsal stream or recording where you can inspect the complete sequence without risking an important broadcast.
Version and setup caveats
The exact labels, available conditions, and timer options can vary with OBS and plugin versions. Install software only from its official or recognised project source, check compatibility information for your operating system and OBS build, and review the documentation for the version you have installed. The presence of a macro feature in documentation is not proof that a particular six-hour configuration will work unchanged on your computer.
VLC is a prerequisite for OBS’s VLC Video source. Pay attention to the 32-bit or 64-bit match noted in OBS documentation; a mismatched installation may mean the source is unavailable. Keep your media files in stable locations and avoid renaming or moving them after building the playlist unless you then reopen OBS and verify that every item resolves correctly. A playlist that looks configured but points to unavailable files is not ready for an unattended schedule.
There is also an optional community resource called Media Playlist Source, but it is not needed for the basic VLC workflow. Its OBS resource listing describes that separate option; check the current listing for compatibility and behaviour before deciding whether it fits your requirements. Do not add another plugin merely because “playlist” appears in its name. First identify what the built-in source does not provide for your specific use.
If the real difficulty is that an always-on broadcast depends on leaving your personal computer running, a different operating arrangement may remove that particular burden: StreamNeo takes an uploaded video and runs it as a YouTube live stream without your computer remaining on, which can be useful when the pain is keeping a local OBS machine available overnight. It is YouTube-only, so it is not a substitute for OBS scene automation when you need interactive scene control or a schedule built around multiple live sources.
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 OBS loop a playlist every six hours?
No. The VLC Video source’s Loop Playlist option restarts the list when it runs out of media files. A six-hour switch requires a separate timer-driven action, such as a scene automation macro, which you should verify with your OBS and plugin versions.
Can OBS automatically switch scenes after a set time?
Scene automation with Advanced Scene Switcher is a plausible way to arrange a timed change. The sources reviewed do not establish one tested configuration for every version, so check the documentation for your installed version and rehearse the behaviour before relying on it live.
Do I need to stop and restart YouTube Live when the scene changes?
A scene change is a change to the programme OBS is sending; it is distinct from ending the broadcast and starting another one. The article’s workflow is about switching content scenes while the broadcast is active, but you should test the actual stream output rather than assume every aspect of your setup will behave identically.
Why does my VLC playlist not appear in OBS?
OBS says VLC must be installed for the VLC Video source to be available, and 64-bit OBS requires 64-bit VLC. Check that the installations match, then verify the source and its media paths in OBS before relying on the playlist.