OBS can switch between different playlists on a timetable, but the timetable belongs to OBS, not YouTube Studio. Create scenes for your content blocks, put the right playlist source in each scene, and use Advanced Scene Switcher macros with date and time conditions to move between them.
YouTube Studio has a separate job: create or schedule the broadcast and manage its encoder connection. Keeping those two schedules distinct prevents a common mistake—expecting a scheduled YouTube broadcast to decide which local videos OBS plays.
Separate broadcast scheduling from playlist scheduling
Think of the workflow as two clocks that meet at the stream output. OBS decides what appears in the video at a given time; YouTube Studio decides when the platform-side broadcast is available and how its encoder feed is managed. You configure them separately, even when the viewer experiences one continuous channel.
For example, a devotional channel might show morning bhajans, then a daytime instrumental block, followed by evening aarti recordings. OBS can change scenes at the chosen times. YouTube Studio does not need a new broadcast for each content block: it is not the local playlist controller. The encoder sends the current OBS output while the broadcast is active.
Google’s documentation distinguishes a broadcast resource from a stream resource. A broadcast represents the event shown on YouTube; a stream resource carries the encoder feed, and the resources can be bound. The YouTube Live Streaming API documentation describes that relationship. API-based broadcast management is useful for developers automating platform objects, but it does not configure your OBS media files or scene changes.
If you are new to a recurring pre-recorded format, the article on scheduling recurring YouTube livestreams from pre-recorded videos can help you think through the platform-side event. For the OBS timetable in this guide, keep the key distinction in view: broadcast scheduling is not playlist scheduling.
Organise content into time-based blocks
Before opening OBS, write down what should play and when. Use clock-based blocks if the schedule follows the day, such as morning, afternoon and evening programming. Use sequential playback if a block should continue until its files finish. Those are different requirements: a clock-based transition can interrupt a long item, while end-of-file sequencing does not guarantee a change at a particular hour.
A simple schedule might look like this:
| Block | Example content | Intended change | Playback decision |
|---|---|---|---|
| Morning | Bhajans and devotional visuals | At a chosen morning time | Ordered playlist, then loop if the block continues |
| Daytime | Instrumental music or study ambience | At a chosen daytime time | Ordered or shuffled, depending on the programme |
| Evening | Aarti and devotional recordings | At a chosen evening time | Ordered playlist, with a planned return to the next block |
The table is a planning aid, not a setting imported into OBS. Translate each boundary into a scene-switching condition later. Decide whether the playlist loops, shuffles, or simply reaches its end, and write down the expected behaviour. A shuffle may create variety but makes the exact next item unpredictable; an ordered playlist is easier to audit and repeat.
Keep media in stable locations. Renaming, moving, or disconnecting a folder can leave an OBS source pointing at a path that no longer exists. Use clear names such as Morning_Bhajans or Evening_Aarti for both the scene and playlist source. Where several people may edit the setup, add a simple schedule document alongside the content files so the intended order is not stored only in one operator’s memory.
Also plan what happens outside a block. Does the next block begin immediately at the scheduled time even if a song is mid-way through? Is there a short visual transition, or a static holding scene if content is missing? Be explicit. A scheduled scene change is a clock decision, not an intelligent choice to wait for a song to end.
Create OBS scenes for each block
In OBS, make a scene for each distinct programme block. A scene per block makes the timetable visible and gives each playlist a clear home. A morning scene can contain its own playlist source plus any title, logo, or background elements. The daytime and evening scenes can use the same layout structure with different media and labels.
Avoid putting every playlist into one crowded scene and relying on memory to enable the right source at the right time. Multiple scenes make it easier to inspect which block is active, test a transition manually, and correct a missing file without disturbing unrelated sources. If your stream includes an audio bed or common overlay, decide whether to duplicate it into each scene or use an OBS arrangement that keeps shared elements consistent; then test both video and audio during scene changes.
Name scenes and sources consistently. A scene called Daytime_Study paired with Playlist_Daytime_Study is clearer than a set of generic names such as Scene 2 and Media 4. This matters when you configure macros, because a condition or action that points to the wrong scene can look plausible while producing the wrong programme.
Scenes do not themselves create a time schedule. They are destinations for the automation, and you can still switch between them manually. If you use a single looping video rather than a playlist, OBS’s standard Media Source has a loop option. For a more complete discussion of continuous playback problems, see why OBS can stop looping videos during a church YouTube stream.
Add playlist sources to the scenes
For an ordered or shuffled list of local clips, OBS’s VLC Video source is one route. Add it to the relevant scene and add the files in the desired order; then choose whether the playlist loops or shuffles. OBS documents VLC-based media sources alongside other media source options. The VLC source depends on VLC being installed, and OBS notes that a 64-bit OBS installation needs 64-bit VLC for the source to appear.
Test a source before building the full schedule. Confirm that the first item starts, that the next item behaves as expected, and that looping or shuffling matches your plan. Check audio levels across files, since recordings from different sources can vary. If the last file ends before the next clock-based change, decide whether the source should loop, show a holding scene, or leave a deliberate gap. Do not assume that playlist completion will automatically select the next scheduled block.
A community plugin, Media Playlist Source, offers another playlist-oriented route. Its author’s plugin page describes playlist functions, but a community plugin is not the same as an OBS built-in source. The listed release has its own OBS version requirements, and compatibility can change. Check the current plugin page against your installed OBS version before you install or update it.
| Method | Useful when | Scheduling behaviour | Main consideration |
|---|---|---|---|
| VLC Video source in an OBS scene | You need a straightforward list of clips | Plays the list; loop and shuffle options affect playback | Requires a compatible VLC installation; it does not set clock times |
| Media Playlist Source plugin | You want the plugin’s playlist-oriented controls | Provides playlist functions, not a substitute for time-based scene switching | Check the author’s current OBS version requirements and test updates |
| Multiple scenes with Advanced Scene Switcher | Different blocks should begin at specific times | Macro conditions can trigger scene actions | Requires plugin setup and testing with your OBS build |
Keep playlist choice and schedule choice separate. A source decides which files it plays and in what playback mode. The scene-switching macro decides when OBS changes to a different scene. Neither choice alone provides both behaviours.
Use Advanced Scene Switcher time conditions
Advanced Scene Switcher adds macro automation to OBS. For a clock-based programme, create a macro for each boundary: a date/time condition checks when the change should happen, and an action switches to the scene for the next block. This makes the timetable an OBS-side control rather than a YouTube Studio setting.
The plugin’s author page for Advanced Scene Switcher documents its macro features and supported versions. The research available for this guide lists version 1.36.1 as supporting OBS 31.1.1 or later; that is not a guarantee for every installation or future release. Re-check the current author page for the plugin version you intend to use and match it to your installed OBS release. Do not assume that a plugin built for one version works across all versions.
Start with one boundary. Make a macro whose time condition corresponds to a near-term test and whose action switches to a plainly named scene. Confirm that the action runs, then add the remaining boundaries. Use unambiguous times and review whether the macro should recur daily or apply to a particular date. If your timetable changes on weekdays or festival days, represent those differences deliberately instead of assuming one repeating daily rule covers them.
Avoid competing macros that can activate at the same time and direct OBS to different scenes. Review the conditions together as a timetable, especially where one block ends exactly when another begins. Name each macro after its boundary, such as Switch to Evening, and document its time, target scene and recurrence. This will make later troubleshooting much quicker.
Date and time conditions are not the same as “wait until this playlist ends”. If a change must happen after the current song, a clock condition may cut across it. If the content must change at a fixed time, the clock condition is appropriate even if it interrupts an item. Decide which rule matters more for your channel, then build and test for that rule.
Back up the OBS scene collection and plugin settings before significant changes or upgrades. A working scene collection is an operational asset. After changing OBS or the plugin, verify that macros still load and that scene actions target the intended names before leaving the stream unattended.
Configure YouTube Studio broadcast separately
Once OBS scenes and their playlist sources are ready, configure the platform-side broadcast in YouTube Studio. Create or schedule the live broadcast in the Live Control Room, then configure OBS with the stream URL and key using YouTube’s encoder workflow. YouTube Help explains how to create a live stream with an encoder, including scheduling as a way to promote the stream.
For a scheduled encoder stream, follow the current on-screen instructions: start the encoder feed, wait for YouTube to show a preview, and use the Live Control Room control to go live where required. The steps and labels can change, so check the current Help page rather than relying on an old screenshot. A channel enabling live streaming for the first time may need to wait for YouTube’s activation process; plan this before the intended launch rather than discovering it on the day.
A YouTube broadcast’s schedule does not switch OBS scenes, and an OBS macro does not create a scheduled YouTube broadcast. Think of the YouTube object as the programme’s platform event and the OBS scene collection as the content timetable. If you use the YouTube API, it can manage broadcast and stream resources, but it still does not tell a local OBS playlist which files to play.
There is a separate session-length consideration for 24/7 operation. YouTube Help says streams under 12 hours are automatically archived. Do not assume the same archive behaviour for a single stream that runs longer than that threshold; check the current official guidance and decide whether successive sessions or another supported arrangement fits your channel. A session boundary may interrupt the viewing experience, so plan it alongside your OBS scene timetable rather than treating it as an unrelated administrative detail.
Test scene transitions and schedule behaviour
A macro that looks correct in its settings still needs an operational test. First test each playlist source manually: check that the expected files play, audio is present, and the scene looks right. Then test scene switching using a near-term condition or a manual action. Verify that the old source stops or behaves as intended and that the new scene’s playlist starts in the expected state.
Test the schedule across a representative cycle before leaving it to run overnight. Confirm each boundary, including one where a playlist is still playing when the scheduled switch occurs. Listen for doubled audio or a sudden silence, check that overlays remain readable, and confirm that the next playlist starts at the intended item. If your schedule has different weekday or calendar behaviour, test each distinct rule rather than extrapolating from one day.
Include failure cases in the test. Temporarily remove or rename a test file and observe what the source does; do not risk the production library to simulate this. Restart OBS and make sure the scene collection and macros return in the expected state. Consider what happens after a network interruption, a computer restart, or a scheduled change near the YouTube broadcast’s session boundary. The OBS and YouTube documentation describe features, not a promise of unattended continuity.
Keep an operator recovery path. That can mean someone who can check the stream, a way to receive alerts, and a short checklist for restoring the correct scene or encoder connection. If a stream is important to a congregation, shop, or news audience, test the recovery steps rather than assuming automation will resolve every fault. For related encoder-side thinking, see how to make an FFmpeg YouTube stream recover from network errors.
If the recurring pain is keeping a computer on solely to sustain the broadcast, StreamNeo can take an uploaded video and keep the YouTube stream running while your computer is off; it does not replace careful content planning or the need to confirm how a schedule should behave.
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
Can YouTube Studio schedule different OBS playlists?
No. YouTube Studio schedules or manages the broadcast on YouTube, while OBS controls the local scenes and media sources sent through the encoder feed. Use OBS automation for playlist changes and configure the broadcast separately.
Can an OBS playlist source change at a set time by itself?
A playlist source handles playback of its items; it does not provide the clock-based scene timetable described here. Use a separate automation tool such as Advanced Scene Switcher to switch to the scene containing the next playlist at the planned time.
Does Advanced Scene Switcher work with every OBS version?
Do not assume so. Check the plugin author’s current version requirements against your OBS installation, then test the macros after installation or an update.
Will a 24/7 broadcast always be archived on YouTube?
YouTube Help says streams under 12 hours are automatically archived, but you should not infer the same behaviour for a single longer session. Check the current official guidance and plan session boundaries around your channel’s needs.