You schedule the YouTube event in YouTube Studio, then use OBS to play a jingle in the stream. For one repeating clip, use an OBS Media Source with Loop; for a sequence of clips, use VLC Video with Loop Playlist.
These controls do different jobs. YouTube scheduling makes the event available for viewers ahead of time; the OBS controls repeat a file or playlist during the broadcast. They do not establish a way to insert a short jingle at an exact interval over a separate, continuous music bed.
Separate the event from the playback
Think of the setup as two layers. The YouTube event is the viewer-facing page and its planned start time. The encoder is the software that sends your audio and video to YouTube. OBS handles the media sources in that outgoing programme, including a jingle file or playlist.
Scheduling an event does not schedule a sound. Creating an event for 8 pm, for example, does not cause YouTube to play a jingle at 8 pm, or every 15 minutes after the stream begins. You still need to connect your encoder and start the broadcast, and any audio cue has to be produced by the encoder setup.
The distinction matters if you run a devotional channel, a local news loop or a small station with announcements. A scheduled event can tell viewers when to return, but the sound they hear depends on what OBS is outputting. The documented OBS Loop controls repeat media; they are not evidence of clock-based cueing, timed insertion, or mixing over a separate music source.
If your goal is simply to have one station ident repeat, OBS can handle that straightforwardly. If you need a five-second ident precisely every quarter-hour while another source continues uninterrupted, pause before building around Loop: the cited controls do not provide that behaviour. Identify and test a separate cueing or automation method before promising that schedule to listeners.
Schedule the YouTube event
In YouTube Studio, open Go live, choose Manage, and select Schedule stream. Create a new event or reuse settings where appropriate. Check the title, description, visibility, thumbnail and planned start time before saving; those details describe the event to viewers, not the jingle playback.
A scheduled event gives people an upcoming page where they can see the planned broadcast and opt into reminders. The event can be ready for viewers even though your encoder is not yet sending a programme. At broadcast time, YouTube’s workflow expects you to connect the encoder, inspect the incoming preview and then start the event from Live Control Room.
Use an event title that describes the actual programme and a time you can meet. If you are testing audio beforehand, do not assume that an upcoming event means viewers are already hearing your OBS scene. Confirm the privacy and audience settings for the intended broadcast, and check the current YouTube encoder setup instructions, since Studio’s interface can change.
This is also a useful point to decide what listeners should encounter at the opening. If the jingle is meant to precede music, build and test that sequence in OBS rather than relying on the event’s scheduled start to trigger it. For an always-on programme, the planned event start is only one part of the hand-off between the YouTube page and the signal your encoder sends.
Connect OBS to the event
Once the event is prepared, open its stream settings in Live Control Room and copy the stream URL and stream key into OBS’s stream settings. The URL identifies the destination; the key identifies the stream connection. YouTube describes stream keys as credentials, so keep yours private and do not paste it into a public chat, document or screenshot.
Treat the stream key much like a password. If you believe someone else has seen it, use YouTube’s documented reset option in Live Control Room and update the encoder before the next broadcast. The live stream settings guidance explains the key and its reset process. Avoid sending a screenshot that includes the key when asking for technical help.
In OBS, select the YouTube service if available, then enter the event’s stream key and the appropriate server or stream URL as required by the chosen connection method. Take care not to mix credentials from an older event with the one you intend to start. The simplest check is to verify the selected event in Studio and the key in the encoder before you begin testing.
When the connection is made, YouTube should receive the OBS output for preview. That is not yet proof that the right audio is playing: the preview can be silent, use the wrong scene, or contain a jingle that is too loud. Keep the event in its intended state until you have checked the signal and are ready to go live.
Add a local jingle in OBS
In the scene that should contain the jingle, add a Media Source and select the local audio file. OBS documents common audio formats such as MP3, AAC, OGG and WAV for Media Source. Keep the file in a stable location on the machine running OBS; moving or renaming it later can leave the source pointing to a missing file.
Give the source a clear name, such as “Station ident”, rather than leaving a generic label. That makes it easier to distinguish it from a music bed or another announcement when you return to the scene after a break. If you use several scenes, make sure the source is placed in the scene whose output will actually reach YouTube.
Set the source’s audio level while listening to the programme in context. A jingle mastered much louder than the music can startle listeners, while one set too quietly may be difficult to hear on a phone. Use OBS’s mixer meters as a warning against clipping, and make a local recording or private test to listen on ordinary speakers or headphones before relying on the level.
A local file is only a playback choice, not a rights clearance. Use audio you have permission to stream, and check that any permission covers livestreaming and an archived replay if you keep one. A short sound effect or a file described as royalty-free is not automatically cleared for every use. For a closer look at the issue, see what a short sound-effect loop can mean for a YouTube copyright claim.
Loop one jingle file
If one clip should repeat as soon as it ends, open the Media Source properties and enable Loop. OBS describes this setting as repeating the file when playback has completed. It is a repeat-on-completion control: if the file is short, it will begin again after it finishes, rather than waiting for a clock time or playing over a different source at an interval you specify.
Listen through several repetitions before using it on air. Check whether the file has silence at the start or end, whether the join is distracting, and whether the final sound leads cleanly into the next repetition. An ident made to play once may sound unnatural when repeated without a gap, so the repeat behaviour itself should be part of your decision about the asset.
Also decide what should happen when the source or scene is hidden. OBS documents visibility behaviour for media sources, and the result can depend on source settings and scene changes. If a jingle must continue across a switch to another scene, test that exact change in a recording; do not infer that it keeps playing simply because the source exists in the project.
A single looping source is useful for a fixed repeated announcement or sound, but it offers no playlist-level rotation. If the requirement is “play this once when the stream starts, then leave the music alone”, a looping source is the wrong behaviour unless you stop it manually or use a different arrangement. Match the setting to the intended playback rather than treating Loop as a general scheduler.
Play and loop a playlist
For several files in a sequence, use an OBS VLC Video source and add the media files to its playlist. OBS documents playlist playback and a Loop Playlist setting that restarts the source after it has run out of items. VLC must be installed for this source to be available in OBS.
Choose the order deliberately. If the station needs a fixed sequence, leave shuffle disabled and inspect the list before the broadcast. If order is not important, shuffle may be useful, but it changes what comes next and makes it harder to predict the next jingle. Neither setting means “play at a specific time”; it controls the sequence of items in the playlist.
Loop Playlist repeats the list after its last item, not each short clip at a chosen interval over another continuously playing source. A playlist of three jingles will play those items according to the source’s sequence and then restart the list if looping is enabled. That is different from mixing those jingles into a separate music bed every 15 minutes, and the documented control should not be presented as doing that.
Check visibility and scene behaviour as well as the order. If you change scenes, determine whether the VLC source is intended to continue, pause or restart according to its settings and your layout. Make a test recording that includes the scene transition. For a wider look at a related radio workflow, streaming a radio playlist to YouTube with VLC may help you think through the playlist side, but it does not turn playlist looping into timed cueing.
| Need | OBS control | What it does not establish |
|---|---|---|
| Repeat one jingle | Media Source with Loop | No exact-interval insertion over a separate music bed |
| Rotate through several files | VLC Video with a playlist and Loop Playlist | No clock-based cue schedule |
| Place jingles over continuous music at chosen intervals | Not demonstrated by these loop controls | Verify a separate scheduler or automation workflow |
If the station needs exact timed insertion, test a suitable automation method independently and verify how it mixes, handles scene changes and recovers from an interrupted file. Do not advertise a precise interval to listeners until you have confirmed that the source actually produces it in a sustained test.
Preview the encoder output
Before the event, test with audio and video similar to what you intend to broadcast. YouTube’s live streaming tips recommend advance testing, checking the Live Control Room preview and monitoring stream health and audio/video quality. Follow the current YouTube recommendations for live streams rather than relying only on what OBS appears to show locally.
Connect OBS to the scheduled event and wait for the incoming preview. Confirm the picture, listen for the jingle and music levels, and make sure the expected source is audible in the intended scene. If the preview is silent, check OBS’s mixer, source audio settings and selected scene before pressing Go live. A green-looking meter in the encoder is not by itself proof that YouTube is receiving the right programme.
Test the specific behaviour you plan to use. For a single jingle, record enough to hear it finish and restart. For a playlist, confirm the order and the transition from the final item back to the first. If the programme uses multiple scenes, switch between them during the test and observe whether the audio carries on, pauses or starts again. A short test before the event can catch a missing file or an unexpected loop that a last-minute glance will not.
During the broadcast, keep an eye on YouTube’s stream health and listen for changes in output. If a local computer or encoder loses power or connectivity, these instructions do not establish that the stream will restart itself or remain available. If continuity matters, consider the operating arrangement separately and test recovery rather than assuming that a successful preview guarantees an uninterrupted night. A practical discussion of what happens after an app crash and whether a stream restarts can help frame that separate reliability question.
For a channel that should continue while your own computer is off, StreamNeo removes the specific burden of keeping that computer running for an uploaded-video broadcast; it does not change the distinction between event scheduling and timed jingle cueing described here. Confirm that the service fits the actual programme before relying on it, particularly if your requirement is precise sound insertion rather than continuous playback of a prepared file.
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 scheduling a YouTube livestream schedule its jingles too?
No. YouTube Studio schedules the event so viewers can see it ahead of time, while OBS controls the media sent by the encoder. The event’s start time does not trigger a jingle or set a repeating cue interval.
How do I repeat just one jingle?
Add the local file as an OBS Media Source and enable Loop in its properties. It plays again when playback completes; it does not wait for a chosen clock time or insert itself over a separate music bed at intervals.
Can a VLC playlist put a jingle on every quarter-hour?
The documented VLC Video source can play a playlist and repeat the playlist with Loop Playlist. Those controls do not document exact-interval insertion over continuous audio, so verify a separate automation method if that is the requirement.
What should I check before going live?
Connect the encoder to the scheduled event, inspect YouTube’s incoming preview, and listen for the correct scene, levels and jingle behaviour. Test the loop or playlist through its restart and any scene changes, then monitor stream health and audio/video quality during the broadcast.