A countdown and an intermission screen for a 24/7 YouTube channel are best built as separate scenes in OBS Studio. You can switch between them while OBS continues sending the encoder feed; the scene changes the picture, not the broadcast connection.
YouTube scheduling and auto-start or auto-stop settings can help organise a broadcast, but they do not schedule OBS scene changes. Prepare the visuals in advance, connect OBS to the stream in YouTube Studio, and test every handoff before leaving the channel unattended.
What the screens need to do
A countdown screen gives viewers a clear indication that a programme is about to begin. An intermission screen fills the gap between programmes, when a static slate, a short loop, or a schedule may be more useful than leaving the previous programme frozen on screen. In both cases, the aim is to change what viewers see without stopping OBS output to YouTube.
In OBS, a scene is a collection of sources arranged into a picture. One scene might contain a local countdown video, a logo and a line of text. Another might contain an intermission loop and a programme schedule. When you select the next scene, OBS sends that composition through the same output connection. You do not need to stop and restart the stream just to change the visual.
Plan what each screen should show and how it should behave when it becomes active. A countdown clip may need to begin at its first frame every time. An intermission loop may need to repeat until you return to the programme. Decide whether your audio should continue, fade, or be silent on each scene as well; an image change does not automatically make the audio transition suitable.
For a channel made from a sequence of prerecorded programmes, scene changes are one part of a wider playback setup. The guide to scheduling a prerecorded playlist on YouTube Live covers the separate question of arranging the programme material itself.
Create the YouTube Live stream
In YouTube Studio, open Live Control Room and create or schedule an encoder-based live stream. Enter the title, visibility and other details you need, then find the stream URL and stream key for the encoder connection. YouTube’s guide to creating a live stream with an encoder describes the setup and the usual preview-and-go-live process.
Scheduling creates a watch page viewers can find in advance. It does not tell OBS when to switch from a countdown scene to a programme scene, or from a programme scene to an intermission. Treat the schedule as YouTube-side broadcast organisation and the scene sequence as an OBS-side task.
YouTube also provides auto-start and auto-stop controls in stream settings. Their effect depends on the stream configuration, so check the current controls in Studio and test your actual workflow rather than assuming that a scheduled stream will start or end in a particular way. Neither setting creates a scene schedule.
Treat the stream key as a credential. It allows the encoder to send a feed to the relevant YouTube stream, so do not publish it or include it in a screen capture. If you think it has been exposed, reset it in YouTube Studio and update OBS with the replacement. For a channel using a particular format or audience, the Kannada devotional playlist settings guide is a useful companion for thinking through the stream configuration, not a substitute for checking the current Studio controls.
YouTube’s encoder instructions describe starting the encoder feed, waiting for a preview in Live Control Room, and selecting “Go live” when required. Auto-start settings may change that manual step. Confirm the preview and live status on your own stream rather than relying on a setting name to tell you what viewers can see.
Connect OBS to the stream
In OBS Studio, open the stream settings. If YouTube is available as a service, select it and follow the connection options shown in OBS. If you are using a custom connection, copy the server URL and stream key from the relevant YouTube Studio stream into the corresponding OBS fields. Check that each value belongs to the same stream.
Save the settings, then start streaming from OBS when you are ready to test. The YouTube preview should show the output OBS is sending. If it does not, pause before selecting “Go live”: check the selected service, URL, key, and the connection status in both applications. A preview that shows the wrong scene is also a cue to fix the OBS composition before viewers arrive.
Keep the encoder running during your scene test. Start with the countdown scene selected, verify its picture and audio in the YouTube preview, then switch to the programme scene and the intermission scene. The YouTube feed should remain connected throughout the changes. If a scene switch appears to interrupt the feed, check whether you pressed “Stop Streaming” or changed a stream connection setting rather than selecting another scene.
The output also depends on the computer, network and media playback remaining available. If the channel is running from a local computer, plan for the machine and connection to stay on, and watch a supervised test long enough to see how the media behaves. For network-related preparation in India, the JioFiber and OBS continuity guide addresses connection considerations beyond the scene layout.
Build a countdown scene from prepared media
Create a scene in OBS and give it a clear name such as “Countdown”. Add a Media Source and point it to a countdown video stored locally on the computer running OBS. A local file avoids relying on a web page or external site at the moment the scene is shown. Before adding it, check that the file has the picture, countdown numbers and any audio you intend viewers to hear.
In the Media Source properties, decide whether the clip should loop. For a countdown with a known start time, looping may be confusing: viewers could see the numbers restart while they are waiting. If the clip should start from its beginning each time you activate the scene, enable “Restart playback when source becomes active”. Confirm the exact behaviour in OBS with a scene switch; do not infer it from how the source looks while you are editing it.
A countdown can be a full-screen video, or a background video with separate text and logo sources above it. OBS layers sources, so items higher in the list appear over items below. Put text and branding above the background if you want them visible throughout. Make the wording readable at the size of a phone screen, and ensure the countdown communicates what is actually about to happen rather than implying a precise start time you cannot meet.
Audio deserves its own check. If the countdown has music or a spoken message, listen to it in the programme output and confirm that it is not unintentionally competing with the programme audio. If you want silence, remove or mute the relevant audio source for that scene. A scene transition can change video and audio conditions together, so listen during the handoff, not only while the countdown plays by itself.
If the countdown is one clip, a Media Source is the straightforward starting point. If you need several clips in sequence, OBS’s VLC Video Source can handle a playlist, but it requires VLC to be installed. The OBS VLC Video Source documentation notes that OBS and VLC need matching architecture, such as both being 64-bit. Check that requirement before building a workflow around a playlist.
Build an intermission scene
Create a separate scene named “Intermission” and add the media or sources that should appear between programmes. For a simple break, use a locally stored video or still image with a schedule, channel name or short message. If you choose a video, enable Loop when it should continue until you switch away. If viewers should always see its opening frame after you return to the scene, test “Restart playback when source becomes active” as well.
An intermission does not have to be visually busy. A clear slate that tells viewers what is next may serve a devotional channel better than an unrelated moving background. For a lofi or ambience station, a slow, prepared loop may fit the channel while avoiding an abrupt frozen frame. Keep the information current: a time or programme label that becomes inaccurate can be worse than no label.
Arrange sources deliberately. A background can sit below a logo or text overlay, and a schedule can sit above both. Verify that no important line is cropped and that the text remains legible against the moving picture. If you use a Browser Source for a custom layout, check that the page loads and continues to display correctly during a longer test. A local media file has fewer dependencies during playback.
Make the intermission scene’s audio choice explicit. It might continue low-level ambience, play a prepared loop, or be silent. Watch for an audio source that remains active when you move to a scene where it should not be heard. OBS’s scene and source configuration can be arranged in different ways, so listen to the actual programme output after setting it up.
Switch scenes without stopping OBS output
Choose a scene transition in OBS, such as Cut or Fade. A cut changes the picture directly; a fade blends between the two compositions. OBS includes both transition types. Set a duration appropriate to the material, then check how it looks in the output rather than assuming the preview alone represents the viewer’s experience. A devotional countdown that fades gently may feel different from a local news slate that needs a clean, immediate change.
During the broadcast, use the scene list or the configured transition controls to move from Countdown to Program, then from Program to Intermission. Keep OBS streaming. Selecting a different scene changes the encoder’s video composition; it does not itself end the YouTube broadcast. The distinction matters on an always-on channel: stopping the encoder and starting again is a different action from changing the scene while the output is active.
For a recurring manual workflow, write the sequence down where the person operating the channel can see it: select Countdown, confirm playback, switch to Program, then select Intermission between shows. If another person takes over, use names that are unambiguous and avoid creating several nearly identical scenes. A scene called “Break – next show” is easier to identify than “Scene 4 copy”.
YouTube stream settings can make repeated broadcasts easier to configure, but that does not create an OBS scene timer. If you need scene changes at exact times without an operator, investigate a separate automation workflow and test it carefully; this walkthrough does not assume any automatic scene scheduling. Keep the distinction clear when deciding whether you need one continuous watch page or separate broadcast events.
A continuing feed also has archive implications. YouTube’s encoder help says streams under 12 hours are automatically archived; that statement does not establish that an uninterrupted 24/7 broadcast will produce one complete replay. If each programme needs a replay, check YouTube’s current guidance and consider whether separate broadcasts or a local recording workflow better fits your needs.
Test every handoff before going live
Run the complete sequence while watching the YouTube preview or a supervised live test. Start on the countdown, wait long enough to confirm its playback behaviour, switch to the programme, and then move to the intermission. Check that OBS remains connected and that the YouTube image changes as expected. Testing only the editor preview can miss a problem in the actual encoder output.
Check both picture and sound at each transition. Look for a blank frame, an unintended freeze, a countdown that restarts unexpectedly, text hidden behind another source, or a clip that does not loop. Listen for music that overlaps the programme or silence where you expected audio. Correct one issue at a time and repeat the sequence so you know the fix worked.
Also test the return from intermission to the programme. A one-way test may not reveal that the countdown or break source behaves differently when reactivated. Confirm whether the media restarts or continues from its previous position, based on the properties you chose. Write down the expected behaviour so the operator knows whether a restarted clip is a fault or the intended result.
Keep an eye on the computer and connection during the test. A local file can still fail to play if it was moved, renamed, or stored on a drive that is unavailable. A network interruption can affect the encoder feed independently of the scene sequence. Do not leave a new setup unattended until you have observed it running and know how you will check it later.
If a problem occurs, distinguish between an OBS scene issue and a YouTube broadcast issue. If the scene changes in OBS but the YouTube preview does not, inspect the output and connection before going live. If the stream is active but a video source is blank, check the file path and Media Source properties. For a deeper overview of scene and media preparation, the guide to running a YouTube channel from a Windows PC covers the broader operating context.
When the workflow is stable, keep a short operating note with the scene order, expected audio, stream-start steps and the person to contact if the feed drops. Recheck it after changing a file, updating OBS, replacing a stream key or changing the broadcast configuration. A tested handoff is a more reliable basis for overnight use than assuming a setting will behave as it did in another stream.
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 YouTube scheduling change OBS scenes for me?
No. Scheduling can create a watch page and organise a broadcast, but it does not tell OBS to switch between Countdown, Program and Intermission. Make those changes in OBS or use a separately configured and tested scene-automation workflow.
Can I change scenes without ending a 24/7 stream?
Yes. When OBS remains connected and streaming, selecting another scene changes the composition it sends to YouTube. Confirm that the output is still active and that the new scene appears in the YouTube preview.
Should my countdown and intermission videos loop?
Loop an intermission clip if it needs to continue until the next programme. A countdown often should not loop, since viewers may see it restart; test whether playback should restart when its scene becomes active.
Will a 24/7 stream create one complete YouTube replay?
Do not assume it will. YouTube’s encoder help says streams under 12 hours are automatically archived, which does not guarantee a complete archive for an uninterrupted stream beyond that duration. Check the current official guidance and plan separate broadcasts or local recording if retaining each programme matters.