To show the current song name inside a 24/7 Gurbani stream, add a text label to the video scene your encoder sends to YouTube. In OBS, that can be a text source displaying a text file; YouTube’s stream title and description are separate metadata and do not put a label over the picture.
For a morning aarti programme, decide how titles will change, test the hand-off between tracks, and arrange a way to check the broadcast after it starts. Keep the live schedule and the replay plan separate: YouTube may not capture a stream longer than 12 hours, so one continuous feed is not a dependable complete archive.
Decide the live schedule and replay needs
First decide what “24/7” means for your channel. You may want one continuing broadcast, a repeated daily programme, or a morning aarti block followed by other Gurbani recordings. Those are different schedules, and they affect when you need to check titles, how you handle transitions, and what you expect viewers to find afterwards.
Write down the intended start and end of each programme block, the playback order, and who will verify the current song name. If the stream is meant to remain live overnight, specify what should appear during a quiet interval or an unexpected pause. Avoid leaving a title on screen if it no longer describes the audio.
Also decide whether viewers need a song name in the image, on the YouTube watch page, or both. An on-screen title travels with the encoded picture. Editing the stream’s metadata in YouTube Studio changes the broadcast listing, not the words embedded in the video. YouTube explains stream settings and metadata in its live stream settings guidance.
Think about viewers who arrive part-way through a programme. A persistent label can help them identify what they are hearing without scrolling the description, but it should be readable without covering the singer, scripture, or other important visual material. If you are planning broader access as well, this guide to making a 24/7 YouTube radio stream accessible to viewers covers considerations beyond the title overlay.
Clear rights for aarti audio and recordings
Before building a repeating schedule, establish what recordings you are permitted to use on a public live stream and in any replay or archive. A devotional work, a particular performance, and a recording of that performance may involve different rights. The fact that a prayer or composition is traditional does not by itself establish that a specific recording is free to broadcast.
Keep a simple record for every audio file: its source, the name of the performer or rights holder where known, the permission or licence you rely on, and whether that permission covers live streaming, replay, and any intended territory. If a temple, label, artist, or distributor supplied the audio, ask specifically about YouTube livestreams and saved replays rather than assuming a permission for in-person use covers both.
Check the current YouTube rules and any claims or restrictions shown in your account. A rights check is not a guarantee that a stream will be approved or remain available, and platform policies can change. If the recording’s ownership or permitted use is unclear, seek clarification from the rights holder before putting it into a continuous public feed.
This matters especially when a playlist repeats while no operator is present. One unreviewed track can recur through the schedule and complicate a replay as well as the live broadcast. Build the playlist only from recordings you have checked, retain the supporting information somewhere you can find it, and review any changes before replacing a file.
Prepare the visual and playlist feed
Create a simple scene with the visual elements your viewers need and enough clear space for a song label. In OBS, add a text source and position it where it stays legible across the programme’s imagery. OBS describes text sources as customisable text, including text read from a file, in its Sources Guide.
A file-based label is a practical starting point when someone can update it. Put the current song name in a plain text file, point the OBS source to that file, and check the preview after changing the text. Use a consistent convention for spelling and artist or recording details, if those are useful to your audience. Keep the displayed wording concise enough to fit the scene.
The audio playlist and the title label are separate parts of the setup. OBS documents media playback options, including a VLC Video source that can play a playlist, loop it, and shuffle it; VLC must be installed for that source to be available. The Media Sources documentation describes playback, but that alone does not establish that a playlist automatically updates a separate text source with the current track name.
For a planned morning aarti sequence, an operator can update the file as each track begins. If you need unattended changes, identify the exact player or integration that knows which item is actually playing and can update the label. Verify that hand-off in your own setup: do not infer the current title from a playlist order if playback can pause, skip, or restart independently.
Keep a fallback label ready for an unknown item, a pause, or a file that fails to load. A neutral message such as “Gurbani programme” is more accurate than leaving yesterday’s song name onscreen. Preview the first item, a normal change, a long title, and the fallback before relying on the scene.
| Approach | What viewers see | What you must verify | Main trade-off |
|---|---|---|---|
| OBS text source reading a file | A label in the video image | The file path, wording, and update at each change | Simple to understand, but somebody or some process must update it correctly |
| Text source with an automated update | A label that may follow playback | That the chosen player or integration exposes the actual current item and updates reliably | Less manual work, with more setup-specific behaviour to test |
| YouTube Studio metadata edit | A changed title or description on the stream listing | That the correct live broadcast is being edited | Useful for the watch-page listing, but it is not an image overlay |
Live captions have a different purpose. YouTube’s live caption requirements describe captions as a visual display of audio in a programme, with supported ways to send them. They are not the documented method for placing song names on screen.
Connect an encoder through Live Control Room
In YouTube Studio, create or select the live broadcast and open Live Control Room. Review the stream settings and connect your encoder using the stream key for that broadcast. Treat the key as private: anyone with access may be able to send a feed to the channel. YouTube’s live stream settings guidance covers the stream’s configuration and metadata; use the current instructions in Studio because its interface can change.
In OBS, select the intended scene and configure the stream output using the details supplied by YouTube. Before going live, confirm that the preview shows the right image, the song label is visible, and the audio is coming from the intended playlist rather than a desktop sound or unrelated source. Start with a private or unlisted test if you need to inspect the result without presenting it as the public programme.
There are two distinct title fields to check. The OBS text source controls the label viewers see within the video. The title and description in Studio describe the live broadcast on YouTube. Changing one does not automatically change the other, so check both when the schedule or programme changes.
If the feed is already running, avoid making a major scene or playlist change without checking the preview and broadcast status. Keep an operator’s short checklist near the workstation: correct broadcast selected, encoder connected, audio present, current label accurate, and schedule understood. For an India-based team preparing a morning programme, this can be done before the planned start rather than discovering a wrong scene after viewers have arrived.
Test the network and monitoring arrangements
A dependable workflow depends on more than the advertised connection speed. The encoder must maintain an upload path to YouTube while the computer is awake, the router remains powered, and the local connection stays available. Test from the actual location and equipment you plan to use, at a time representative of the expected broadcast, rather than relying on a provider’s general package description.
Observe the encoder’s connection status and the broadcast preview during a test. Listen for gaps and check whether the picture freezes or drops. If the network is shared, other uploads or household activity may affect it; try the stream under the conditions you expect during the morning schedule. Do not assume an India-specific speed threshold: the suitable configuration depends on the video settings and the connection’s actual behaviour.
Decide who will notice a problem if the stream goes silent, the label stops changing, or the broadcast disconnects. That may be an operator who checks at planned intervals, a channel team member who receives an alert from a supported monitoring arrangement, or a combination. Test the notification path itself. A dashboard that nobody watches is not a monitoring plan.
You can also make a short checklist for someone who is not the original operator. Include where the stream status appears, how to confirm audio and title, and whom to contact before restarting or changing the broadcast. The useful question is not only whether the stream looks right at launch, but whether another person can recognise a problem later without guessing.
For the encoder choice, consider the computer and the work you need it to do. OBS provides scene composition and text sources, but it requires a machine and an operator or reliable operating arrangement. This comparison of OBS and FFmpeg for a YouTube live loop on a low-power PC can help frame the software trade-offs. If keeping a computer running, awake, and monitored is the pain you need to remove, StreamNeo can take an uploaded video and run it as a YouTube live stream with your computer switched off; the song-name overlay still needs to be prepared as part of the video workflow.
Plan interruption recovery
An always-on plan should say what to do when the stream stops, not promise that it will never stop. Common interruptions include a network loss, a computer restart, a power cut, a frozen media source, or an operator changing the wrong scene. Identify which of these you can detect and who can take the next action.
Write down whether recovery means reconnecting the same broadcast, creating a new one, or waiting for the encoder to resume, and check YouTube’s current instructions before adopting a procedure. The right action can depend on the broadcast state and what viewers see. If the encoder has stopped but YouTube still shows a live event, do not assume that starting a second event is the correct fix.
After reconnecting, verify the image and sound in the actual broadcast, not just the local OBS preview. Check the current song name against the audio, because a restart may begin a different playlist item or leave a stale label. Record the time and cause of a disruption where possible; recurring failures are easier to address when they are not treated as unrelated surprises.
If the content is scheduled around morning aarti, define the acceptable response when no one is at the controls. You might arrange a person to check shortly before the programme and another to confirm it has begun, but choose intervals that fit your own team. Do not claim uninterrupted service or imply that automatic recovery removes the need for rights, network, or content checks.
Handle archives for long streams
A live feed and a replay are separate deliverables. YouTube may not capture streams longer than 12 hours, so do not rely on one continuous 24-hour broadcast to become a complete recording. Check YouTube’s current live-stream archive guidance before setting expectations for viewers, and decide how you will preserve the programme you need.
If a complete replay matters, plan a separate recording workflow or divide the programme into shorter broadcasts that suit your archive needs. A local recording requires storage, a machine that remains available, and someone to check that the file is usable. A split schedule requires clear starts and ends and may produce more than one watch-page item. Each approach has operational costs; neither should be described as a guaranteed complete archive without testing.
Check the saved result before sharing it as a full programme. Confirm that it begins where expected, includes the relevant audio, and has not ended early. If song names need to be available in the replay, an overlay recorded into the video can remain visible there, while a YouTube metadata title alone will not identify every item within a long programme.
The archive should follow the rights check as well. Permission to stream live does not necessarily answer whether you may retain, publish, or replay the recording. Make that distinction clear with the rights holder and in your own schedule. For a channel that rotates episodes and reruns, this guide to alternating podcast episodes and reruns in a YouTube live stream offers a useful way to think about programme blocks, though the audio and permissions for Gurbani recordings remain your responsibility.
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
How do I show the current Gurbani song name on the video?
Add a text source to the scene your encoder sends, then supply it with the current song name. In OBS, a text source can read from a file; someone or a tested integration must update that file when the actual track changes.
Will changing the YouTube stream title show the song name over the picture?
No. YouTube Studio metadata changes the stream listing, while an OBS text source is part of the encoded video image. Use the one that matches where you want viewers to see the information, or maintain both separately.
Does an OBS playlist automatically update a song-name overlay?
Do not assume so. OBS documents playlist playback and text sources as separate capabilities, not automatic synchronisation between them. Test the specific player or integration that you choose before leaving it unattended.
Will YouTube save the complete replay of a 24-hour stream?
Do not rely on a single 24-hour live feed for a complete archive; YouTube may not capture streams longer than 12 hours. Use a separately tested recording or a schedule designed around shorter broadcasts, and check the saved result and replay rights.