“Playlist transition time” can mean how long an OBS scene change takes, or when one playlist video gives way to the next. Those are separate controls: a scene fade duration does not schedule playlist items, and playlist looping does not set a clock time for a change.
For one file that repeats, use an OBS Media Source and enable Loop. For a collection of files, use VLC Video and decide whether you want the list to repeat or shuffle. If you need an item to start at a particular clock time, you need a separate scheduling approach; the standard VLC Video playlist controls do not provide that schedule.
What “transition time” means
Before changing settings, decide which moment you are trying to control. OBS scene transitions govern the visual change between scenes, such as moving from a title card to a camera or from one graphic layout to another. Their duration is the time taken by that scene change. It is not a countdown that says when the next video file should start.
Playlist advancement is different. A playlist source plays media items in sequence, and an item normally finishes according to its own duration before playback moves on. Loop and shuffle affect what happens to the list as a whole; they do not say “play this item at 9 pm” or “hold this item for fifteen minutes”. If you want a different scene to appear at a particular point, that is also a scene-change scheduling question, not simply a playlist setting.
The wording causes confusion because a viewer may see an image dissolve while the underlying media advances, and call both events a transition. Write down the desired result in plain language first: “fade to the next scene over a short interval”, “play these four files in order and start again”, or “show the evening notice at a chosen time”. Each describes a different job.
This distinction matters especially on an always-on channel. If a devotional stream should play a set of bhajans continuously, a playlist can handle ordered playback and repetition. If you want a morning greeting scene to appear at dawn, a looped playlist alone is not a clock-based scheduler. Avoid promising yourself a timed change simply because a list advances automatically.
Set an OBS scene transition duration
In OBS, select the transition type in the Scene Transitions controls, then set its duration there. OBS documents Fade and Cut as transition types available from the first launch, and its overview explains that the active transition duration can be changed. A cut changes immediately; a fade takes the duration you choose. Consult the OBS Studio overview for the current interface and terminology.
A sensible starting point is to choose the effect for the content rather than to search for a universally correct number. A cut suits a hard switch between a camera and a holding slide. A fade can make a change feel less abrupt when moving between artwork or scene layouts. The duration is a production choice: a very long fade can make important text hard to read during the change, while a cut may feel sudden for quiet music or ambience.
The transition is applied when you change scenes, manually or through another control that causes the scene change. Setting a duration does not make OBS switch scenes later by itself. If the scene never changes, its transition duration has nothing to animate. Similarly, if the playlist is inside one scene and its media moves from file to file, changing the scene transition does not configure a crossfade between those files.
Test the transition with the actual graphics and text used on air. A logo can appear to linger or disappear differently against a dark background than against a bright one. Watch the programme output, not just the settings panel, and confirm the outgoing and incoming scenes remain understandable throughout the change.
For more OBS setup context, the guide to configuring an OBS VLC Video source for a church stream is useful when your scene contains a sequence of media rather than a single camera shot. Keep the two jobs distinct as you configure it: the source handles media playback, while scene transitions control scene changes.
Understand Quick Transitions
Quick Transitions are controls for applying a scene transition promptly from OBS. Their configured durations are still durations for the scene change, not instructions to advance a playlist item at a clock time. Depending on your workflow, they can be convenient when you are operating scenes with a mouse or using an established switching routine.
Do not assume every way of changing a scene uses an identical transition configuration. Check the transition controls associated with the action you actually use, including any Quick Transition settings, and test what the programme output does. If the ordinary scene transition has the expected fade but a quick action cuts instead, the issue may be the action’s own configuration rather than the playlist.
This distinction is useful for small teams. Suppose one person watches chat and periodically changes between a song-art scene and a notice scene. A quick transition can make that operator’s scene switch consistent. It still requires the person or another scheduling mechanism to initiate the switch. It does not mean the next playlist file receives a timed fade.
The OBS scene API further illustrates that scene-item show and hide transition durations are separate properties expressed in milliseconds. That is technical reference material rather than a user-interface walkthrough, but it reinforces the important point: visibility animation and playlist progression are different concerns. See the OBS scene reference if you are building or maintaining an integration; for ordinary setup, rely on the current OBS controls and verify the result on screen.
Configure a VLC Video playlist source
For several local media files, add a VLC Video source in OBS and add the files to its playlist. This source depends on VLC being installed; OBS notes that 64-bit OBS requires 64-bit VLC. If VLC Video is not available as a source type, check that dependency and that the installed versions match before assuming the playlist settings are missing. The OBS media sources guide documents the source and its playlist options.
Choose the files and ordering deliberately. With shuffle disabled, the source follows the listed order; with shuffle enabled, it randomises the order. Loop Playlist determines whether the playlist starts again after it reaches the end. These controls help answer “what should happen after the current media finishes?” They do not provide a separate start time for each item or establish a crossfade duration between playlist items.
OBS also exposes behaviour for when the source is not visible. The selected visibility behaviour determines whether playback stops or restarts, pauses and resumes, or continues while hidden. Consider the scene layout before selecting it. If the source is hidden while you show a notice scene, continuing playback means the media can carry on out of view; stopping or pausing it may instead affect where it resumes. Confirm the chosen behaviour in a short test rather than inferring it from the word “hidden”.
For a single repeating video, a Media Source with Loop is usually the simpler arrangement; OBS describes Loop as repeating a file when playback completes. A VLC Video source is intended for a playlist of multiple files. The OBS sources guide can help orient you to the distinction between source types. A playlist with one item can work, but an unnecessary playlist makes it harder to diagnose whether a problem comes from a file, list order, or source behaviour.
Prepare files before the stream begins. Give them clear names, check the intended order, and play each one on the same machine or in the same OBS profile you intend to use. A file that works in a desktop media player is not proof that the OBS source will behave exactly as expected. Verify that the image and sound are present and that the end of one item leads to the next as intended.
A guide to running a 24/7 Indian music stream after a server reboot addresses a related operational concern: playback configuration and recovery after a restart are separate pieces of an always-on setup. It is worth planning both, but neither should be mistaken for a playlist’s clock schedule.
Looping and shuffle are not timed changes
Looping answers what the source does when it reaches the end of the media or playlist. Shuffle answers whether the list should play in its listed order or a randomised order. Neither setting is a timer. In particular, “loop playlist” means return to the start after the end; it does not mean “change scenes every hour” or “switch to a different item at midnight”.
| What you want | OBS control to consider | What it does not do |
|---|---|---|
| Repeat one file | Media Source with Loop | It does not create a multi-item schedule |
| Repeat a list in order | VLC Video with Loop Playlist and shuffle off | It does not assign each item a clock time |
| Vary the order | VLC Video with Shuffle Playlist | It does not guarantee a planned sequence |
| Fade or cut between scenes | Scene transition type and duration | It does not crossfade playlist items or start scenes later |
| Change content at a chosen time | A separate scheduling or automation workflow | It is not established by loop or shuffle |
For a bhajan channel with a fixed morning sequence, a non-shuffled list is more predictable than random playback. For an ambience station where repeating a fixed order is acceptable, Loop Playlist can keep the list going after it runs out. If you need a news loop to present a bulletin at a particular time, playlist order alone may not meet that requirement: the item starts when playback reaches it, which depends on what came before and how long those items run.
This is also why you should avoid describing a playlist as “timed” merely because its files have durations. A media duration tells the player how long that item runs; it is not an independent wall-clock appointment. Changing an earlier file, inserting an item, or restarting playback can shift when later items are reached. When the clock matters, use a system designed to schedule changes and test it under the same conditions as the live channel.
The official OBS media-source documentation describes playlist loop, shuffle, and visibility behaviour, not per-item clock schedules or playlist-item crossfade controls. Do not infer a gap-free or frame-accurate crossfade from these settings. If an uninterrupted hand-off is essential, test the actual source, files, and OBS version you plan to use, and consider a different production workflow if the result does not meet your needs.
Test scene changes and media playback
Test the two kinds of transition separately. First, place two simple scenes in OBS, choose the scene transition and duration, and switch between them while watching the programme output. Confirm the transition looks right and that text, logos, and other important elements remain legible. A settings value is not proof that the scene change you will use on air has the expected effect.
Then test the media source. For one file, check that Loop starts it again after playback completes. For a VLC playlist, verify the order, whether the list repeats, and whether shuffle is actually on or off as intended. Test the visibility behaviour by hiding the source and bringing it back, then note whether playback continued, paused, or restarted. Use representative content with sound, not only short silent test cards.
Do a longer rehearsal if the stream is meant to run unattended. Observe a complete item hand-off, the end of the list, and the restart at the top. Keep a note of the expected sequence and compare it with what appears on the programme output. This catches mismatched files, unexpected ordering, and a source left hidden in the wrong scene before viewers encounter them.
For channels with audio-led content, watch and listen across item boundaries. If you hear silence, a sudden level change, or a picture that briefly goes black, first identify whether it occurs at a file boundary, a scene change, or because the source has become hidden. Those are different symptoms and need different fixes. A relevant companion guide is fixing audio that is out of sync in a Hindi songs stream; it covers a separate playback problem, but the same disciplined diagnosis helps you avoid changing an unrelated transition setting.
Finally, test after saving and reopening the OBS profile, and after any restart that is part of your normal operation. Settings that appear correct in a temporary session are only useful if the saved setup restores the intended scene and source behaviour. Keep a written note of which scene transition is used, whether the playlist loops, and what should happen when the source is hidden. That makes later troubleshooting more concrete than “the transition stopped working”.
Choose automation when clock time matters
If you need a scene or item to change at a particular clock time, treat that as a scheduling requirement. The built-in scene duration control describes how long a scene change takes, and VLC playlist controls describe list order, looping, shuffle, and visibility behaviour. The cited controls do not establish a per-item wall-clock schedule. YouTube’s live interface should not be assumed to add an independent playlist-transition-duration setting for an OBS source.
A clock-based workflow may involve a separate automation tool or an operator following a schedule. The right choice depends on how precise the time must be, whether an operator can intervene, and what should happen if a file is still playing when the scheduled change arrives. Advanced plugins or automation may offer more control, but verify a particular product and its compatibility from its own documentation; do not assume a feature exists because a playlist setting sounds similar.
Write down the event rules before choosing a tool. For example: at the start of a scheduled notice, should the current song be cut, allowed to finish, or faded out? Should a missed change happen immediately after a restart, or wait for the next scheduled slot? What should viewers see if the intended file is unavailable? These decisions determine the workflow more than the word “transition” does.
A local OBS setup also has an operational trade-off: your computer and streaming session must remain available, and you are responsible for testing playback and recovery. Where the specific pain is keeping the same uploaded video running without leaving your own computer on, StreamNeo can remove that need by running the broadcast after you upload the file and provide your YouTube stream key. It is for YouTube streams from an uploaded video, not a replacement for an OBS production that needs live scene switching or a clock-based multi-item schedule.
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
Is an OBS scene transition duration the same as playlist transition time?
No. Scene transition duration controls how long a scene change takes, such as a fade from one layout to another. Playlist progression is about which media item plays next; loop and shuffle do not schedule a scene change.
How do I loop a playlist in OBS?
Add the files to a VLC Video source and enable Loop Playlist if you want the list to start again after it reaches the end. Turn Shuffle Playlist on only if you want randomized order, and check the source’s visibility behaviour as part of your test.
Can VLC Video start each file at a set clock time or crossfade between items?
The documented VLC Video playlist controls cover playlist behaviour such as looping, shuffle, and visibility, not per-item clock schedules or crossfade duration between items. Use a separately verified automation workflow if a wall-clock change is required, and test the actual result before relying on it live.
Does setting a longer scene fade make the stream change files more slowly?
No. A longer fade changes how long the scene switch takes; it does not alter the duration or advancement of a media file. Check the source playback and scene-switch controls independently.