“Rotating videos” can mean repeating one file, advancing through a playlist, or switching between separate OBS scenes. Those are different operations: playback controls decide which media runs, while scene transitions decide how a change between scenes appears.
For a nonstop broadcast, choose the playback method first, then configure any scene transition you actually need. Test the entire sequence, including audio and restart behaviour, before leaving it to run unattended.
First decide what “rotating videos” means
Start by describing the behaviour you want in plain terms. If one long devotional recording should repeat, you need a media source with looping enabled. If several recordings should play one after another, you need a playlist source. If each video belongs to a separate scene that you intend to change between, you need a scene-switching workflow as well.
These distinctions matter because a transition is not a playlist scheduler. A Fade or Cut selected in OBS does not make a clip advance, repeat it, or automatically switch to another scene when it ends. Likewise, enabling a media loop does not apply a visual transition between scenes. OBS documents these controls separately in its guides to media sources and scene transitions.
A useful example is a small channel with a morning prayer recording and a static title card. If the recording should repeat beneath the same scene, loop the media source. If you want to alternate between the prayer and a separate announcement scene, configure a deliberate scene change; do not assume the end of the prayer clip will trigger one automatically.
Write down the sequence you expect before changing settings: “play A, then B, then repeat” is a playlist requirement; “show scene A, then switch to scene B when I click” is an operator-controlled scene transition. That simple description prevents you from looking for a transition duration to solve a playback problem.
Repeat one file with Media Source
For one video that should start again when it ends, add a Media Source to the relevant scene and enable Loop in its properties. OBS’s Media Sources guide says Loop repeats the file after playback completes and is off by default. If it is left off, the source reaches the end and stops rather than starting over.
The setting Restart playback when source becomes active is separate. It is on by default, and it restarts the file when the source becomes active in the current scene and is visible. That can be useful when a clip should begin from its opening frame each time you return to the scene. It can be inconvenient if you expected the clip to resume where it was, so test the actual scene and visibility behaviour you plan to use.
Neither setting is a scene transition. A loop restart concerns the file’s playback; a transition duration concerns how OBS presents a change between scenes. If you use a single scene continuously, you may not need a scene transition at all. If you switch away from and back to a scene containing the source, the active-source setting can affect where playback begins, independently of the Fade or Cut you selected.
Check the file itself as well as the checkbox. Watch the end and beginning together: a source can be configured to loop correctly yet still show a noticeable visual jump or an audio gap because of the content’s edit. For a bhajan recording, for example, listen to the last phrase and the first phrase back-to-back. A setting cannot make two mismatched edits sound seamless.
If the file should play only once, leave Loop off intentionally and decide what should happen after it ends. Do not treat a stopped source as a cue for OBS to pick another video unless you have separately built a playback or operator workflow that does that. When the goal is straightforward repetition of one asset, a Media Source is easier to reason about than a playlist with a single item.
Rotate several files with a playlist
For a sequence of separate files, OBS documents VLC Video as the playlist route. Add the source, build the playlist, and confirm its order. The documented defaults are Loop Playlist on and Shuffle Playlist off, which means repeat-in-order unless you change those options. For a fixed schedule of recordings, leave shuffle off; for an intentionally varied order, enable it and verify the result is acceptable.
VLC must be installed for VLC Video to be available. OBS also specifies that 64-bit OBS requires 64-bit VLC. Those are practical setup dependencies, not optional transition settings. If the source is absent from the add-source menu, check the VLC installation and matching bitness before rebuilding scenes or changing unrelated settings.
Pay attention to visibility behaviour. OBS documents the VLC source’s default as “Stop when not visible, restart when visible.” If the playlist source is in a scene you hide by switching to another scene, that behaviour can alter playback when it becomes visible again. It is therefore important to test the playlist in the same scene arrangement you will use on air, rather than testing the source in isolation and assuming it will behave identically in a multi-scene layout.
| Setup | Best fit | Relevant playback or transition behaviour | What to check |
|---|---|---|---|
| Media Source with Loop | One file repeating | Loop is off by default; source activation behaviour is separate | End-to-start picture and sound, plus restart behaviour when shown |
| VLC Video playlist | Several files in sequence | Playlist loop is on and shuffle is off by default | VLC installation, file order, visibility behaviour and restart at the end |
| Fade or Cut | Straightforward scene change | Select the active transition and set its duration | Preview the actual scenes at the chosen duration |
| Studio Mode or Quick Transition | Operator prepares the next scene | The operator previews and then triggers a transition; quick transitions have their own duration | Who will trigger it and which duration is configured |
| Stinger or Track Matte | Designed overlay between scenes | An animated video covers or reveals a scene change | Cut point and, for Track Matte, a suitable combined file |
A playlist still does not mean OBS will transition among separate scenes when each playlist item ends. It is a media sequence inside a source. If you want a scene change, handle that as a separate part of the setup and verify how the playlist behaves when its scene is hidden or shown.
For a more involved event-replay workflow, see how to schedule recorded event replays in an OBS YouTube Live playlist. If you are comparing ways to manage a music rotation, the playlist automation tools guide is a useful adjacent read, but check each tool’s current capabilities and requirements against your own intended workflow.
Switch scenes when sources are separate
Use separate OBS scenes when the visual layouts are meaningfully different: for example, a full-screen music video, a local news graphic, and a holding slate. Put the appropriate sources in each scene. When you want to move between those layouts, select a transition in the Scene Transitions panel and trigger the scene change through OBS’s normal controls.
This is distinct from putting several files into a VLC Video playlist. A playlist advances media within its source; changing scenes changes the composition OBS sends to the stream. You may use both in one broadcast, but one does not configure the other. Do not infer that a scene will switch because a file finishes: the documented settings here do not promise a built-in automatic scene switch at clip end.
With Studio Mode, you can prepare or edit the next scene in Preview before clicking Transition to send it live. This is useful when a person is operating the broadcast and wants to inspect the next layout first. It also means the change depends on a deliberate operator action as described in OBS’s overview guide. It is not a substitute for configuring unattended playlist playback.
OBS also lets you add a transition to Quick Transitions, with a duration configured for that quick action. Keep track of which duration you have set: the active transition selected in the panel and a quick transition can have separately configured durations. If your workflow relies on a person clicking a control, rehearse the exact control and scene order rather than assuming every scene change uses the same setting.
There is a trade-off. Separate scenes give you control over graphics and layout, but they introduce more state to check: visibility, audio sources, and the chosen transition. If a single video loop in one scene meets the need, adding separate scenes simply to imitate a playlist may make overnight troubleshooting harder. A simple arrangement is often easier to inspect after a restart or edit.
Choose a transition style and duration
OBS lists Fade and Cut as transitions available from first launch. Its overview also describes options including Swipe, Slide, Fade to Color, and Luma Wipe. Choose the visual change that fits the content: Cut is immediate, while Fade can make a change less abrupt. A wipe can suit a designed programme look, but it can also distract from a simple music or ambience loop.
Select the transition in the Scene Transitions panel and set its duration there. There is no universally correct duration: a slow dissolve may suit a quiet landscape, while a news graphic may need a clean, direct change. Preview it with the actual footage, titles and audio. A duration that looks acceptable between two test colour screens may feel very different when one scene contains moving text or a face.
OBS’s overview gives 500 ms and 1000 ms as examples when describing durations; those are examples, not universal recommendations. Choose a duration based on the content and the pacing you want. If you use Quick Transitions, check their separately configured duration too, so your rehearsal reflects the control you will actually use.
A Stinger is for an animated video overlay that covers the cut between scenes. OBS’s Stinger settings use a cut point measured in milliseconds or frames. This is useful when you have a designed bumper or branded animation, but it adds a media asset and timing decision that a basic Fade or Cut does not require. Test whether the reveal happens at the intended point in the animation.
For a Track Matte stinger, OBS describes an animated mask that determines the reveal: black corresponds to the current scene, white to the next, and intermediate grey permits blends. The guide describes combined-file layouts with the video and mask arranged side by side or vertically stacked. It recommends one combined file because separate files cannot be guaranteed to decode in perfect sync; its Track Matte workflow disables separate files for that reason. Use a combined asset if you choose this effect, and validate the reveal on the system and scene arrangement you intend to broadcast.
Test playback, transitions and audio together
Do not test only whether a source appears on screen. Run through the sequence from the first frame to the end of a file, through the playlist restart if there is one, and across any scene changes. OBS recommends testing settings, stream smoothness and scene configuration before a first live stream. For this use case, also check the transitions and source visibility behaviour that your chosen setup relies on.
A practical test has several parts. First, confirm that the correct file or playlist starts. Then let it reach its end and check whether the next item begins, whether the playlist restarts in the intended order, or whether a single source loops. If you expect a manual scene change, have the operator trigger it using the real control. Observe whether the selected transition and its duration look right with the actual content.
Listen at the same time. Music can make a small discontinuity obvious even when a visual loop looks clean. Check both the end and start of each file, audio level consistency between playlist items, and whether scene changes unexpectedly remove or duplicate an audio source. A scene transition changes the visual scene, but you still need to inspect how the sources in those scenes are arranged and heard.
Test source visibility by switching away from and back to a scene that contains the media. This matters particularly for a VLC Video source whose documented default visibility behaviour is to stop when not visible and restart when visible. Confirm whether returning to the scene restarts the playlist or otherwise matches your intended operation. If it does not, revisit the source arrangement and settings before relying on it.
Finally, leave the configured sequence running for an extended test that reflects the way you will use it. Watch for a stalled file, unexpected restart, wrong playlist order, audio gap or scene that does not appear as expected. A short preview can establish that controls are set, but it cannot show what happens at a later file boundary if you never let the sequence reach one. Keep notes of the exact settings that passed, especially if someone else may have to check the broadcast.
If audio is central to the channel, use a focused check such as the bhajan stream audio settings guide. It addresses a different part of the setup, but it reinforces a useful habit here: judge the sound in the live scene, not just the labels in a properties window.
Plan for continuous operation
OBS can be configured to loop a source or repeat a playlist, but those settings do not by themselves ensure a continuous broadcast. Your plan should account for the computer and OBS remaining available, the media files being accessible, and someone knowing how to diagnose the setup if the sequence stops or changes unexpectedly. Test on the machine and network arrangement you will actually use rather than treating a successful preview as proof of unattended operation.
Keep the scene collection simple enough to understand at a glance. Give scenes and sources clear names, keep the intended playlist together, and document whether order or shuffle is expected. If you change a file, scene, or source visibility setting, repeat the relevant boundary and transition test. A change to one source can alter behaviour even when the transition panel is untouched.
If keeping a personal computer on is the part that makes continuous operation difficult, StreamNeo removes that specific burden by letting you upload the video, provide your YouTube stream key and run the broadcast from the cloud while your own computer is off. It does not change the distinction described above: decide whether your media should repeat or advance, and verify your channel’s requirements separately. StreamNeo is for YouTube, so it is not a general-purpose destination for other live platforms.
If you prefer to operate OBS yourself on a rented machine, compare the operational work before deciding. A guide to running a continuous YouTube stream on a Hetzner VPS discusses a different operating arrangement; it is relevant if you are weighing hands-on control against the responsibility of maintaining a remote setup. Neither approach removes the need to check your media sequence and monitor the result.
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 Fade make OBS move to the next video?
No. Fade is a scene transition: it controls the visual change when you switch scenes. A Media Source loop or VLC Video playlist controls media playback; neither should be confused with a scene transition.
How do I repeat just one video?
Add it as a Media Source and enable Loop. Loop is off by default according to OBS’s Media Sources guide, so check the setting and watch the end-to-start boundary before using it continuously.
Can a playlist switch scenes when a clip ends?
The playlist route described here advances files within a VLC Video source; it does not promise an automatic switch to another scene at the end of a clip. If you need scene changes, configure and trigger those separately, and test the sequence you actually intend to run.
Should I use a Stinger for every scene change?
No. Fade and Cut are suitable for straightforward changes, while a Stinger is for a designed video overlay. Use a Track Matte only when its animated reveal serves the content, and follow OBS’s combined-file guidance for that workflow.