A looping playlist and scene switching do different jobs in OBS. The VLC Video source plays media in sequence, while a scene determines the layout sent to your YouTube broadcast; switching scenes does not schedule or restart that broadcast.
For an operator-led channel, assign hotkeys to named scenes. For condition-based or unattended changes, use OBS WebSocket with a separate client, then test the whole arrangement before relying on it. Plan archives separately: YouTube automatically archives streams under 12 hours, which is not a promise that one longer continuous broadcast will be saved as a complete replay.
Separate playlist playback from scene changes
Think of the playlist as content and scenes as layouts. A VLC Video source can play a list of files in order and repeat it. A scene can show that source alongside a logo, a text label, a still image or other sources. Changing scenes changes the composition OBS sends to its encoder; it does not change YouTube’s broadcast lifecycle.
That distinction matters in a 24/7 setup. You might keep the same devotional playlist running while switching from a full-screen artwork layout to a scene with the channel name and a schedule. Or you might move from a playlist scene to a holding screen while an operator checks a file. In either case, the scene action is not a command to end or restart the live broadcast.
Decide what should change and what should keep playing before building anything. If your goal is only to repeat songs in order, configure the playlist loop; switching scenes adds nothing. If you need different on-screen layouts, create separate scenes. If you need the broadcast to start or stop at particular times, treat that as a separate broadcast-lifecycle task rather than assuming scene automation will do it.
For a single ordered video sequence, the guide to making a YouTube loop stream play videos in order is a useful companion. This article focuses on OBS layouts and the controls that move between them.
Install and configure the VLC Video source
OBS’s VLC Video source is intended for a playlist of local media files. Install VLC before adding the source. OBS specifies matching bitness: if you use 64-bit OBS, use 64-bit VLC. The OBS media sources guide describes the source and its playlist controls.
In OBS, add a VLC Video source to the scene that should show the playlist. Give it a name that describes its role, such as Main playlist, rather than a generic name like Video. Add the files in the order you want them to play. Keep Shuffle Playlist off when order matters, for example when a station has a morning sequence followed by a set of longer tracks.
The files must remain accessible to the computer running OBS. If you move the media to another drive, rename a folder, or prepare the collection on a different machine, confirm that the source still points to the right files. A playlist entry is not a copy of the media, so moving or removing a file can break playback.
OBS also has an ordinary Media Source. Use it when you need one file, rather than treating it as interchangeable with VLC Video for a multi-file playlist. Keep one playlist source in a scene collection and reuse it where appropriate, or create separate sources only when their playback behaviour needs to differ. Clear names make it easier to check which source a scene actually uses.
Pay particular attention to Visibility Behaviour in the source properties. OBS documents choices that can stop or restart media when its source becomes hidden, and media sources can have a short delay when shown again. If you hide the playlist by switching to another scene, the selected behaviour can determine whether playback continues, stops or starts again when you return. Test the behaviour you intend to use rather than inferring it from the scene preview.
Enable playlist looping
When the ordered list is ready, enable Loop Playlist in the VLC Video source properties if it should begin again after its final item. Looping applies to that playlist source; it does not cycle through scenes. Leave Shuffle Playlist off for a fixed sequence, and make a separate decision about whether hidden-source behaviour should allow playback to continue through a layout change.
Test with a short, representative playlist before putting a long collection on air. Confirm that the first file starts, that the next file follows in the intended order, and that the list returns to its beginning after the last item. Then switch away from the scene and back. This tests both the loop and the Visibility Behaviour setting, which are separate controls.
A useful small test is to use three files with recognisable openings. Watch or listen through each transition and check whether the last item returns to the first. Then hide the source, wait, and show it again. If playback resumes at an unexpected point or starts from the beginning, adjust the source visibility behaviour to match the programme you want viewers to see.
A playlist loop does not check whether every file is suitable for a live channel or whether a file will remain available indefinitely. Keep a clean copy of the media and periodically verify that the list still opens correctly in OBS. For an unattended channel, a missing file discovered after a scene change can be harder to diagnose than a simple playback test done in advance.
Create scenes for each broadcast layout
Create scenes around distinct viewer-facing states, not around every individual file. A compact collection might include Playlist — full screen, Holding — channel information and Playlist — schedule overlay. The first can show the VLC source alone; the holding scene might show a still image and text; the overlay version can add a schedule while using the same playlist source if that source’s visibility and playback settings suit the use.
OBS scenes can include video, images, text and capture sources. Name scenes and sources deliberately: OBS’s overview notes that scene and source names share a global namespace. Avoid giving a scene and a source the same name, and use labels that will still make sense in a hotkey menu or automation client months later.
Before switching live, check each scene at the canvas size you plan to broadcast. Confirm that text is readable, the artwork is not cropped unexpectedly, and the playlist source is visible in the scenes where you expect it. In Studio Mode, you can prepare a scene in Preview and then take it live with the configured transition. That gives an operator a chance to check the composition before it reaches viewers, but it does not replace monitoring the actual output.
Save a backup of both your Scene Collection and Profile. OBS Profiles hold stream, video and output settings; Scene Collections hold scenes and their sources. They are different pieces of a setup, so copying one does not preserve the other. This is useful if you are moving from a test layout to the machine that will run the channel.
If you are planning a small music channel on modest equipment, running a 24/7 Bhojpuri music channel from a spare laptop offers a related operational context. Do not treat any example hardware arrangement as a universal specification: the actual collection, encoder settings and connection need to be tested together.
Switch scenes with hotkeys
Hotkeys are the simplest control when someone is present to operate OBS. In Settings, open Hotkeys and assign a distinct key combination to each scene’s switch action. Choose combinations that are unlikely to be pressed accidentally while you are using another application, and record which combination selects each scene.
Test every key while watching the program output. Check that the intended scene becomes live, that its sources appear as expected and that the selected transition behaves as planned. If you use Studio Mode, practise preparing the next scene in Preview and taking it live. A hotkey that changes the live scene directly and a workflow that stages a Preview are not the same operation, so make sure the operator knows which is configured.
Hotkeys require a person or another control mechanism to trigger them. They are suitable for a host who changes from a playlist to a notice screen when needed, but they do not provide time-based unattended scheduling by themselves. If your requirement is “show the notice scene at a chosen time every day”, a key binding alone does not meet it.
Keep a fallback route available. If a key does not work because another application has focus or the wrong scene collection is open, an operator should know how to select the scene in OBS directly. Do not use scene switching as a substitute for checking stream health: a layout change can alter what viewers see, but it does not establish whether YouTube is receiving a healthy signal.
For a related troubleshooting case, see encoder checks after an OBS scene transition. A scene transition is one possible moment to inspect output, not proof that the transition itself caused a warning.
Automate switching with WebSocket
For external control, OBS WebSocket exposes commands for scenes and sources. It has been included with OBS Studio 28 and later; OBS documents the feature in its Remote Control Guide. A compatible external client or a custom integration can issue scene changes based on a time, condition or operator action. The exact setup depends on the client and its current compatibility with your OBS version.
Enable WebSocket authentication and keep the password private. Do not expose credentials in a shared script or leave an unauthenticated control endpoint available to other people on a network. Limit access to the people and tools that need to operate the broadcast. If you are not comfortable maintaining a separate control client, manual hotkeys may be the more dependable choice for your use case.
Write down the intended sequence before automating it. For example, a local news loop might show the main playlist scene, then a news card, then return to the playlist. Decide what event triggers each change, what happens if the client is not running, and how an operator can take control. WebSocket gives a client scene/source control; it does not make an untested schedule reliable, nor does a scene command start or restart the YouTube broadcast.
Test each command with the stream offline or in a private test arrangement before relying on it on the public channel. Confirm the target scene name, transition, source visibility and return path. Then leave the automation running through the times and conditions it is meant to handle while you observe it. There is no single official OBS macro or schedule that fits every playlist and client, so avoid copying a configuration without checking what its commands actually do.
| Approach | Use it when | Main trade-off |
|---|---|---|
| Scene hotkeys | An operator is present and needs direct control | Native and straightforward, but a person must trigger each change. |
| WebSocket with an external client | Changes should follow a time or condition, or be controlled remotely | Flexible, but requires a client, testing and secure authentication. |
| Segment automation | You need to manage broadcast segments as well as layouts | A separate tool may add API, compatibility and failure-handling work; it is not the same as scene switching. |
The options solve different problems. If the pain is an operator having to keep the broadcast machine switched on for a file-based channel, StreamNeo removes that specific computer-running burden by turning an uploaded video into a YouTube live stream, without asking you to maintain an OBS scene automation setup. It is YouTube-only; it is not a way to control scenes inside OBS.
Plan around YouTube archive limits
A 24/7 playlist can be one continuous broadcast, but do not plan on a single complete YouTube replay of a stream longer than 12 hours. YouTube Help states, “All streams under 12 hours will be automatically archived.” The YouTube encoder live-streaming help page establishes the automatic archive condition for streams under that duration; it does not promise a complete archive for a longer continuous stream.
If viewers need a replay, treat archive planning separately from playlist and scene setup. Consider whether shorter broadcast segments suit the channel, and check YouTube’s current guidance before changing how you operate. Segmenting a broadcast is a lifecycle decision, not a scene change: selecting a different OBS scene does not create a new broadcast segment or guarantee an archive.
Third-party segment automation exists, but its presence is not a guarantee that it will work for your channel. Before relying on a tool that uses YouTube APIs, check its supported OBS versions, permissions, maintenance status and failure handling. Be clear about what happens if the tool loses authorization or misses a transition. YouTube’s official archive statement is the relevant baseline, not a plugin’s stated purpose.
YouTube’s Live Control Room is where you obtain the stream URL and key for an encoder setup. Enter the key in OBS’s stream settings, keep it private, start sending, and check the incoming preview and broadcast status in YouTube. YouTube notes that first-time live streaming enablement can take up to 24 hours, so complete that step before a planned launch rather than leaving it to the final check.
The broadcast also depends on the files, OBS configuration, computer and upload connection behaving together. OBS’s Auto-Configuration Wizard can provide a starting point based on intended use, hardware resources and network conditions, but it does not guarantee a stable 24/7 operation. Run the actual playlist and scenes under realistic conditions and check the output, rather than assuming a configuration will hold because a short test looked correct.
A useful preparation checklist is to verify the VLC files and loop, test every scene and hotkey, confirm any WebSocket client can authenticate and issue the intended command, and check the incoming YouTube preview. If you need archives, add a separate plan for broadcast length and recovery. Those checks cover different failure modes and should not be collapsed into “the playlist is running”.
When the file and channel are ready, compare the operating options before committing.
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 switching scenes restart the YouTube broadcast?
No. A scene change alters the composition OBS sends to the encoder; it does not schedule, stop or restart the YouTube broadcast. Manage broadcast start and end separately in your chosen workflow.
Will the VLC playlist keep playing when I switch scenes?
It depends on the VLC source’s Visibility Behaviour. OBS provides settings that can stop or restart media when it is hidden, so switch away and back during a test to confirm the selected behaviour matches your intent.
Can hotkeys switch scenes on a schedule?
Hotkeys let an operator trigger a scene change; they do not create a time-based schedule on their own. For automated changes, use WebSocket through a compatible external client and test its commands and authentication.
Will YouTube save one complete replay of a 24/7 stream?
Do not assume that it will. YouTube says streams under 12 hours are automatically archived, but that does not establish that a single longer continuous stream will appear as one complete replay; check current YouTube guidance and plan archives separately.