You schedule the public live event in YouTube Studio, then use Advanced Scene Switcher to schedule actions inside OBS that control playlist playback. They are separate jobs: the plugin does not create or start the YouTube event, and you should test the exact stream and start configuration you plan to use.
The practical sequence is to create the event, prepare the OBS playback, connect OBS with that event’s stream URL and key, and rehearse the preview and Go live steps. YouTube offers auto-start and auto-stop settings, but treat those as configuration choices to verify rather than a reason to skip a test.
Schedule the event in YouTube Live Control Room
Open YouTube Studio and go to Live Control Room. Under Manage, schedule a stream, either by reusing settings or creating a new event. Add the title, description, visibility, thumbnail and planned time that suit your channel. YouTube’s guide to creating a live stream with an encoder describes this event-creation flow.
Scheduling the event gives viewers an upcoming watch page before the broadcast begins. They can visit it and opt into a reminder. This is useful for a bhajan programme, local news bulletin or scheduled study session: the audience can find the event before OBS sends anything. The event schedule does not itself make your playlist play, and an OBS macro schedule does not publish the event.
Keep the event and playback times aligned. Write down the event time and the intended time to begin OBS actions, allowing for your preview check and any operator steps. If you advertise a start time, decide whether it means the scheduled event time or the time viewers should expect content to appear. That distinction matters if the stream feed arrives early but you wait to click Go live.
Use the event’s own stream settings for the encoder connection later. Do not assume that an old key or a key from another scheduled broadcast points to the event you just created. A mismatch can leave the event waiting for a feed even though OBS appears to be streaming.
Prepare playlist playback in OBS
Before configuring schedules, assemble and test the scenes and media sources you expect to use. OBS can play media sources and switch between scenes; the exact arrangement depends on whether your playlist is a single looping file, several media items, or scenes with different overlays. There is no single playlist design that suits every channel.
For a single long file or a rendered loop, confirm that it starts at the right point, uses the intended audio, and behaves as expected at the end. For a sequence of separate items, check transitions and what happens between files. If you are still making a continuous file from source clips, this guide to creating a looping playlist with FFmpeg covers a different approach to preparing media; it is relevant when you want one finished asset rather than OBS-side item changes.
Give each scene and media source a clear name. Names such as Main playlist and Starting slate are easier to recognise in a macro than several entries called Media Source. Check that files are available at the paths OBS will use when the computer restarts, and avoid changing those paths after building actions around them.
Run playback manually before adding automation. Watch the opening, a transition, and the point at which the playlist should repeat or end. Listen for silence, clipping, or a source that appears in the preview but has no audible output. A macro can trigger an action at a time; it cannot make an untested file behave like the programme you intended.
Install and configure Advanced Scene Switcher
Advanced Scene Switcher is an OBS plugin for building macros from conditions and actions. Its documented feature set includes date and time conditions and media-related conditions and actions. The OBS Project Forums resource for Advanced Scene Switcher lists supported platforms and compatibility information; check the current listing against your installed OBS version before installing or updating.
The resource listing cited in the research for this article reports version 1.36.1 and an OBS minimum of 31.1.1, with Windows, macOS and Linux support. Releases and compatibility requirements can change, so verify the listing at installation rather than relying on those details indefinitely. If this is an existing production setup, note your current versions and back up the plugin settings before changing them.
Install the version appropriate to your operating system, then restart OBS if the installation instructions require it. Look for Advanced Scene Switcher in OBS’s plugin or dock interface. Confirm that it opens and that its macro controls are available before building anything. A plugin that did not load is not a scheduling problem; resolve compatibility or installation first.
The plugin’s 1.34.0 update history introduced a Macro Schedule tab for scheduling macro actions at a date and time. Confirm that your installed version exposes the relevant tab and controls. Treat the plugin as automation inside OBS, not as a substitute for the YouTube event, stream destination, or broadcast confirmation.
Create and schedule the OBS macro actions
Build a small, understandable macro around the playback behaviour you actually want. Advanced Scene Switcher’s available media conditions and actions can be used to respond to or control media-related state, while date and time conditions provide scheduling. The exact controls depend on the source type and plugin version, so use the plugin’s interface and documentation rather than assuming a generic recipe applies to every playlist.
A useful first macro might activate the scene containing your opening slate at a chosen time, followed by a separate playback action or scene change that begins the programme. Another setup may simply start or reveal a playlist source. Decide whether the schedule should start playback, switch a scene, or do both, and make each action explicit. If your desired sequence depends on one item ending before the next begins, test the media condition that detects that state rather than relying only on clock time.
Set the macro date and time to match the computer’s local clock and the planned event. Check the date as well as the hour, and account for whether the schedule is a one-off action or something intended to recur. The macro’s clock controls when OBS acts; YouTube’s event schedule controls when the public event is due. Changing one does not automatically update the other.
Avoid adding several unverified actions at once. Start with one action, test it in a non-public rehearsal, then add the next. If a macro unexpectedly changes scenes or triggers playback while you are preparing the broadcast, disable it until you understand the condition. Keep a note of which macros are enabled and when they are due, particularly if you reuse the OBS profile for different events.
For an established setup, export or otherwise back up the plugin settings before editing. Keep a manual fallback: know how to select the correct scene and start the media source yourself. Scheduling reduces routine input, but a human-readable sequence helps you recover when a file path, scene name or timing assumption changes.
Connect OBS to the scheduled event
In YouTube Live Control Room, open the settings for the event and copy its stream URL and stream key. In OBS, open the stream configuration and choose the appropriate YouTube connection method; if entering the details manually, paste the URL and key into the corresponding fields. YouTube explains that the key identifies where the encoder sends its feed and treats it as a credential in its live stream settings guidance.
Keep the key private. Do not include it in a screenshot, tutorial recording, public document or message to someone who does not need it. If it is exposed, use the reset process in Live Control Room and update the OBS configuration before the next test. Be especially careful when sharing a screen during a remote setup session.
Double-check that the copied details belong to the event you intend to broadcast. Then save the OBS configuration and confirm that the selected service and output settings are appropriate for your channel. OBS showing a connected configuration is not the same as YouTube receiving the correct event feed. The preview test confirms whether the event is actually receiving usable video and audio.
If you normally use OBS to reconnect after a dropped connection, make that behaviour a separate part of your operating plan. The guide to reconnecting OBS to YouTube Live after an internet outage addresses recovery; it does not replace checking that the event key and destination are correct before going live.
Test preview, start behaviour and Go live
Rehearse the complete path before relying on the schedule. YouTube recommends setting up an encoder well ahead of a live stream, starting it before the event and checking the preview. Its tips for live streaming give timing guidance; use it as a recommendation, not as a guarantee that a particular lead time will solve every setup issue.
For the test, use the event or a suitable private/unlisted rehearsal configuration, and avoid surprising viewers with a public test. Trigger the intended macro at the planned time, or use a controlled test schedule, then start streaming from OBS. In Live Control Room, wait for the incoming feed and inspect the preview. Confirm the expected scene, movement, audio, framing and overlays, and verify that the feed belongs to the right event.
The standard encoder sequence includes a preview check and a YouTube Go live action. Once the preview is correct, complete the Go live step in Live Control Room when the event is meant to become live. OBS macro scheduling alone does not publish the YouTube event. If your workflow intentionally uses auto-start, test that exact setting and still inspect the arriving feed during rehearsal.
Test the edges, not just the first frame. Leave the stream running long enough to observe a scene change or playlist transition, and check the behaviour when a file ends or loops. If you use a scheduled macro, confirm what happens when OBS is already open, when the action time passes while OBS is closed, and when you restart OBS. Do not infer those behaviours without checking the installed version and your setup.
A successful test is a record of what you checked, not a promise about the next broadcast. Note the event, stream destination, macro time, media behaviour and whether an operator had to click Go live. If any part differs from your intended sequence, adjust and rehearse again before announcing the arrangement as unattended.
Check auto-start and auto-stop settings
YouTube’s live stream settings include auto-start and auto-stop options. They affect how the YouTube event responds to an encoder feed; they do not turn the Advanced Scene Switcher macro into an event scheduler. Review the settings for the particular event and decide whether you intend to use the standard preview-and-Go-live workflow or a deliberately configured auto-start workflow.
| Choice | What it controls | What you still need to verify |
|---|---|---|
| YouTube event schedule | When the public event is listed as upcoming and due | Correct time, title, visibility and event details |
| Advanced Scene Switcher schedule | When OBS runs its configured macro actions | Correct date, local time, scene and media behaviour |
| Manual preview and Go live | Operator checks the incoming feed before publishing | Feed reaches the right event; picture and sound are correct |
| Auto-start or auto-stop | YouTube’s response to encoder activity, depending on event settings | Exact configuration tested end to end, including stream start and stop |
For many channels, manual preview is a useful safeguard: you can catch a wrong scene or silent source before making the event live. An auto-start workflow may suit a well-rehearsed, controlled schedule where an operator cannot be present at the start, but it leaves less opportunity to inspect before publishing. Neither choice removes the need to test.
Test the combination you will actually use. A rehearsal with auto-start disabled does not establish how the event behaves with it enabled, and a test of one event’s settings does not automatically prove another event is configured the same way. Include the stop path: verify what you expect when OBS stops sending, whether the event remains open or ends, and what your next scheduled broadcast requires.
For a continuous channel, separate a single scheduled event from the wider 24/7 operating plan. YouTube’s encoder guidance says streams under 12 hours are automatically archived; do not treat that as a guarantee for longer unattended broadcasts. For a channel that needs playback to continue when a desktop is off, consider whether a cloud playout approach fits; this explanation of what cloud playout is and how it works helps distinguish that operating model from OBS running on your own computer.
If you need remote or unattended operation, write down who checks the preview, who can intervene, and how you will know that playback stopped. For a small devotional channel, that may be a simple opening check and a contact who can restart the encoder. For a local news loop, the priority may be confirming the correct event and current bulletin. Pick a process your team can actually perform.
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 Advanced Scene Switcher schedule the YouTube live event?
No. Create and schedule the event in YouTube Studio. Advanced Scene Switcher schedules actions inside OBS, such as macro actions related to scenes or media playback.
Can the macro click Go live for me?
Do not treat the plugin’s macro schedule as a way to publish the YouTube event. The standard workflow is to start the encoder, confirm the feed in Live Control Room preview, and complete YouTube’s Go live step. If you intend to use YouTube auto-start, test that exact event configuration instead of assuming it will behave as expected.
What should I check if the YouTube preview is blank?
Confirm that OBS is streaming and that its stream URL and key came from the scheduled event you opened. Check the OBS output and source visibility, then inspect the Live Control Room preview again. Keep the key private; if you suspect it was exposed, reset it in YouTube and update OBS.
Is a scheduled OBS macro enough for an unattended 24/7 channel?
Not by itself. It schedules OBS-side actions, but you still need a playback setup, an event and stream configuration, and a tested start and stop process. Rehearse the complete combination you intend to use and plan how someone will detect and respond to a failure.