A scheduled YouTube event gives viewers a place and time to find your Sikh shabad kirtan stream; it does not start the broadcast by itself. For an encoder-based 24/7 stream, schedule the event, send its feed from an encoder, check the Live Control Room preview and click Go live when the event is ready.
Before you begin, check rights for each composition, arrangement, performance and recording, and decide how you will retain an archive. YouTube says a stream longer than 12 hours may not be captured at all, so a single continuous event should not be your only archive plan.
Plan the kirtan stream and archive
First decide what viewers will receive. A channel might carry a prepared sequence of recorded shabad kirtan, a live performance from a gurdwara, or a mixture of recordings and spoken announcements. The distinction matters: a prepared file can be tested in advance, while a live performance also depends on the musicians, the venue's audio path and someone able to operate the event.
Choose whether you will use one long event or recurring shorter events. A single event gives viewers one destination, but a stream running beyond YouTube's archive threshold may not leave a replay. Shorter events can make archives more manageable, though someone or some supported automation must start and monitor each event. The overview of building a 24/7 YouTube live channel can help you think through how the event fits into a broader channel plan.
Decide whether the event will be public, unlisted or private. A public event can be found by viewers; an unlisted link is useful when you want to share a destination directly; a private event is limited to invited viewers. Set a clear title and description that identify the programme and explain whether it is a recording, a live performance or a repeating sequence. Avoid promising an uninterrupted broadcast or a complete replay.
Make an archive decision separately from the scheduling decision. If a YouTube replay is important, consider scheduling several shorter events and check YouTube's current archive guidance. Record a local copy as well, if your equipment and rights permit it, and verify that the file is actually being written and has sound. For music, a recording made for internal backup is still a copy: confirm that your permissions cover it, as well as any public replay or later upload.
Verify rights for every musical element
A devotional subject does not by itself establish permission to broadcast a particular recording. The composition, a specific arrangement, the musicians' performance, the sound recording and any accompanying backing track can involve different rights holders. Permission for one item does not automatically clear the others, and rights may differ by territory and by use.
Build a track-by-track inventory before scheduling. For each item, identify what you will play, who controls the composition and recording, who performed it, and which party can grant the permissions you need. Ask for permission covering the actual use: live transmission, the territories where viewers may watch, the planned period of use, and whether an archive or replay will remain available. Keep the written permission and any conditions with the programme notes so another operator can check them.
YouTube's livestream terms and conditions place responsibility on the person providing the live content to secure necessary rights, including music licensing rights. YouTube also scans live streams for third-party content. Its copyright guidance for live streams explains that a match can lead to a replaced stream image, interruption or termination. A licence alone may not prevent that outcome if a relevant rights owner has not allowlisted the channel through Content ID.
If a distributor or rights owner says allowlisting is needed, ask them to confirm that the correct channel is covered before you go live. Do not assume that a recording cleared for one channel, event or platform is cleared for another, or that an allowlist replaces the need for permission. This is particularly worth checking when your programme combines recordings from several sources.
Keep the rights inventory current when you change the playlist. Replacing one rendition with another may introduce a different performance or recording, even if the shabad is the same. If you cannot establish the required permissions for an item, leave it out until the relevant rights holders clarify the position. For uncertainty about a specific composition, performance, recording or territory, ask the rights holders or qualified counsel; this guide cannot determine the status of a particular work.
Schedule the event in YouTube Studio
Check channel eligibility before building the event. YouTube's current live-stream guidance says the channel must be verified and must not have a live-stream restriction in the preceding 90 days. If you are not sure, use the channel's live-stream eligibility information in Studio rather than assuming that a past broadcast means the channel is ready now. Our guide to checking live-stream eligibility in YouTube Studio explains where to look.
In YouTube Studio, open the Live Control Room and create a scheduled encoder event. Enter the event details: title, description, visibility, thumbnail and start time. Check the time zone and share the event link with viewers through the channels you already use. If this is a recurring programme, make each event's timing and destination clear; do not assume a viewer's link to one event will take them to the next one.
Scheduling creates the event page and lets you announce it in advance. It does not begin sending video or audio to YouTube. The encoder must connect, and depending on the event settings, an operator may still need to click Go live in the Live Control Room. Review the auto-start and auto-stop settings for the specific event so that the actual steps on broadcast day are not a surprise.
For a repeating schedule, write down who owns each task: creating or checking the event, starting the encoder, watching the preview, clicking Go live, monitoring the stream and handling an interruption. Even a small devotional channel benefits from a simple handover note. Include the event link, the location of the rights inventory, what to do if the stream drops, and who has authority to stop or restart it.
Add the server URL and key to the encoder
Open the scheduled event's stream settings in Studio and copy the YouTube server URL and stream key into the encoder you plan to use. YouTube's encoder setup guide describes this connection. The names of the fields vary by encoder, so verify that the URL goes in the server field and the key goes in the stream-key field. A wrong key or an old event's settings can prevent the feed from reaching the intended event.
Treat the stream key like a password. Do not put it in a public document, a shared description or a message group where it does not need to be. If you believe it has been exposed, reset it in Studio and replace the saved value in the encoder before the next broadcast. Keep access limited to the people who actually need to operate the channel.
Choose the encoder to suit the way you will run the programme. For a pre-recorded sequence, software on an existing computer may be adequate if it can play the material and maintain the stream. A hardware encoder can suit a more involved installation or a team that prefers a dedicated device, but it brings its own setup and maintenance needs. YouTube does not require expensive equipment. The comparison of YouTube Studio and OBS for a pre-recorded live stream is useful if you are deciding how to build the playback and encoding workflow.
For audio from a venue mixer or instruments, check how the signal reaches the encoder. An interface or preamp may be useful where the computer does not have the inputs you need, but neither is a universal requirement. Test the actual source, including the quietest parts of the programme and any changes between tracks. A devotional stream can be difficult to follow if the voice is too low, the accompaniment distorts or silence is mistaken for a connection problem.
Use YouTube's current encoder settings page and your encoder's capabilities rather than copying a preset from an older tutorial. Its guidance covers supported video and audio codecs, recommends constant bitrate encoding and a two-second keyframe interval, and advises that the interval should not exceed four seconds. Prefer RTMPS when the encoder offers it. These are settings to verify against the current documentation, not a reason to change a working setup blindly on broadcast day.
Start the encoder before airtime
Do a full test before the first public broadcast, using the same file or source, encoder, internet connection and audio routing you expect to use. YouTube recommends setting up well ahead of the event and previewing before going live. This gives you time to correct a silent audio input, a frozen image, an incorrect aspect ratio or a stream key problem without asking viewers to wait.
Start the encoder early enough for it to connect and produce a feed before the listed event time. You should see the incoming stream in the Live Control Room before the scheduled start. If it does not appear, check that the encoder is running, the key belongs to the correct event, the connection is available and the software is not waiting for a local playback cue. Do not treat a scheduled clock time as evidence that the feed has started.
Check the outgoing connection as well as the encoder's status. YouTube recommends leaving upload capacity beyond the stream's total outgoing bitrate; its guidance gives 20% as a recommended margin. Test the connection at the place and time you will operate, where possible, and prefer a wired connection if practical. A speed result from a different network or a quiet time of day may not reflect the upload available during the actual broadcast.
Keep the video and audio settings simple enough for the connection to sustain. If you are comparing a sharper picture with a more conservative stream, the bitrate and viewer-quality guide explains why increasing bitrate does not automatically improve what every viewer sees. For kirtan, clear and stable audio is central; a modest visual treatment can be preferable to a demanding picture setting that leaves too little upload headroom.
If you intend to keep a local archive, test that recording in the same rehearsal. Confirm the destination has enough free space, that the recording includes the intended audio and video, and that you can reopen the resulting file. A local recording is useful only if the rights cover the copy and if it is actually being saved. Do not assume that a green indicator in one application proves the other application is recording correctly.
Check the preview and go live
When the encoder feed reaches the Live Control Room, use the preview as a final operational check. Confirm that the image is the intended programme, the sound is audible and balanced, and there is no unwanted desktop, private material or test card visible. Listen on a second device if you can; the operator's local monitoring may not reveal what YouTube is receiving.
Check the event details one more time: title, visibility, thumbnail and scheduled time. If the programme includes an announcement or opening silence, make sure it is intentional and that the audio path is not simply disconnected. Look at YouTube's stream health indicators and address any warning you understand before proceeding. If the preview is missing or the sound is wrong, pause and troubleshoot rather than clicking through in the hope that it will correct itself.
For the normal scheduled workflow, once the preview is correct, click Go live in the Live Control Room at the time you intend to begin. The event page having existed for days does not mean viewers are receiving the broadcast. Conversely, seeing the encoder send data does not necessarily mean the scheduled event has been made live to viewers. Check the event's actual status after the action and, if practical, confirm from a separate viewer device that the public destination is playing the right content.
Auto-start and auto-stop settings can change the operator steps, so confirm them in advance rather than relying on memory or a guide for another event. If an operator will be away when the programme is due to start, the workflow needs a tested, supported way to handle that. StreamNeo can remove the need to keep a local computer running for a prepared file-based broadcast, which is useful when the recurring pain is leaving an office machine on overnight; you still need to prepare the event and confirm rights, preview and the start procedure.
Plan for interruptions and streams over 12 hours
A long-running broadcast should have a response plan, not just a start plan. Decide who will notice a lost feed, what they should check first, and how viewers will be told about a changed event link or restart. Note the encoder's normal state, where to see the stream health information, how to reconnect, and who can access the stream key. A small written checklist is more useful at an inconvenient hour than relying on one person's memory.
YouTube's archive guidance says streams under 12 hours can be automatically archived, while a stream longer than 12 hours may not be captured at all. It recommends a local archive backup. For a 24/7 programme, therefore, do not promise a complete YouTube replay of a single event. If viewers need a durable archive, record locally where permitted and consider splitting the output into shorter scheduled events, with a clear way to direct viewers from one event to the next.
Shorter events create operational work: someone or a tested supported workflow must handle the transition, and viewers need to find the next event. One long event reduces those handovers but leaves the archive uncertain and makes a single interruption potentially more disruptive. Compare the options before launch:
| Approach | What it simplifies | What you must plan |
|---|---|---|
| One continuous event | One destination for viewers to return to | No assurance of a full YouTube archive beyond 12 hours; local recording and interruption response |
| Recurring shorter events | Separate event pages and a more manageable archive plan | Event transitions, viewer notices, operator coverage and rights for each replay |
| Prepared file with a local encoder | Direct control over playback and the local recording workflow | A computer, connection and encoder that remain available, plus monitoring and recovery |
| Prepared file using a managed workflow | Less need to leave a personal computer running | Event setup, rights checks, preview, and a clear plan for any interruption |
No approach makes continuity automatic in every circumstance. A UPS can help with a short power loss at the operating location, but it cannot protect against an internet or platform outage. Likewise, monitoring and restart features can address some failures but do not remove the need to check whether the event is actually live. Before launch, run the complete workflow and rehearse the decision to reconnect, start a replacement event or pause the programme.
Keep archive rights alongside the file plan. If a rightsholder has permitted live use only, do not assume that a local recording, YouTube archive, or later upload is covered. Confirm permissions for each form of use, and check any Content ID allowlisting requirements with the relevant rights owner. Review YouTube's current event, copyright and archive guidance again before changing the programme or its duration.
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 the YouTube event start my kirtan stream?
No. Scheduling creates the event and lets you share it in advance, but the encoder still has to send the feed. For the scheduled encoder workflow, check the preview in Live Control Room and click Go live when the programme is ready, unless the event's configured start settings change those steps.
Will YouTube save a complete replay of a 24/7 stream?
Do not rely on that. YouTube says a stream longer than 12 hours may not be captured at all, so use a permitted local recording and consider shorter events if an archive matters. Verify the local file rather than assuming it was saved.
If I have permission for a kirtan recording, is the whole stream cleared?
Not necessarily. A composition, arrangement, performance, recording and backing track can have different rights holders, and permission for one recording does not clear every musical element. Confirm live and archive uses with the relevant rights holders, and ask whether Content ID allowlisting is needed.
What should I check just before going live?
Confirm that the encoder is feeding the correct event, the preview picture and sound are right, and the event's details and visibility are as intended. Review stream health, then click Go live and verify the event status from a separate viewer device if possible. Keep the interruption and archive plan close at hand.