To replay a festival recording continuously as a YouTube Live broadcast, add the local video to OBS as a Media Source, enable its Loop option, then send OBS’s output to a stream you create in YouTube Studio. The file repeats in OBS; YouTube’s separate job is to receive and publish the encoder feed.
Before you schedule anything, confirm that your channel can go live and that you have the necessary rights for the recording and its music. Set up early, preview the feed in Live Control Room, and plan to monitor the broadcast rather than assuming that a long stream will run or archive without attention.
Check whether your channel is ready to go live
YouTube’s general live-streaming eligibility guidance says that a channel must be verified and must not have had live-streaming restrictions in the preceding 90 days. Its getting-started guidance also says that a person streaming must be at least 16. These are general YouTube conditions; the official material reviewed here does not settle every possible India-specific account condition, so check the current YouTube Help pages for your account before building the event around a particular start time.
If live streaming has not been enabled on the channel before, do not wait until the day of the festival replay. YouTube says first-time enablement can take up to 24 hours. Verify the channel, request access and confirm that the Live Control Room is available well in advance. A channel that is otherwise ready may still need that initial activation period.
Also check the channel you intend to use, not merely an account that has access to it. If several people manage the channel, agree who will create the event, who will hold the stream key and who can stop the broadcast if something goes wrong. Keep the stream key private: anyone who has it may be able to send a feed to that broadcast. YouTube’s live-stream eligibility guidance is the right place to recheck current requirements.
A useful early check is whether a short, private or unlisted test can be created and viewed by the people responsible for the event. This tests access to the control room and the channel’s actual workflow without announcing a public event prematurely. Do not confuse a successful test with approval of the festival material; rights are a separate question.
Confirm rights for the recording and its music
Having a copy of a festival recording does not by itself establish that you may rebroadcast it. The video can contain performances, background music, recorded announcements, audience footage, stage visuals or other material controlled by different people. A festival having taken place in public, or a recording having been posted previously, does not automatically answer who may broadcast that material again, to which territory or for how long.
YouTube says live-stream providers represent that they have the rights needed for worldwide exploitation, including music rights, and that they must meet applicable laws and regulatory requirements in the stream territory. The official sources reviewed for this article do not determine which Indian permissions apply to a particular event, venue, organiser, performer or recording. Treat that as a question to resolve with the relevant rights holders and, where needed, qualified local advice; neither assume a special permission always applies nor assume none does.
There is a separate platform risk even when you believe you have permission. YouTube scans live streams for third-party content. It may replace the stream with a placeholder and warn you to stop using identified material; if the material remains, the live stream can be interrupted or terminated. YouTube also notes that licensed third-party content can still cause an interruption unless the relevant rights owner has added the channel to its Content ID allowlist. Read YouTube’s copyright guidance for live streams and ask rights holders about the specific recording, music and any necessary allowlisting before broadcast.
Keep a record of what you checked: who supplied the file, which rights holders you contacted, what uses were authorised and any limits on territory, dates, monetisation or edits. This is practical recordkeeping, not a guarantee that a claim will not occur or that YouTube will treat a particular file in a particular way. If the recording includes a song or performance whose status is unclear, resolve that before building a public event around it.
Add the festival recording as an OBS Media Source
For one local recording, OBS Studio’s built-in Media Source is a straightforward starting point. Create or select the scene you want to broadcast, add a Media Source, and point it to the video file on the computer running OBS. Menu wording can vary by version, so check the current OBS interface and its Media Sources documentation rather than relying on an old screenshot.
OBS documents common media formats including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM. A file extension alone is not a promise that every file will play correctly: codecs, damaged files and unusual encoding choices can affect playback. Open the recording locally first and review enough of it to confirm the picture, audio and intended beginning and ending. If the source fails in OBS, test a compatible export rather than discovering the problem after the scheduled start.
The source should fill the canvas as intended. Check the preview for black bars, cropped titles, unexpectedly small footage or a portrait video placed in a landscape scene. Confirm that the audio meter responds when the recording plays, then listen through speakers or headphones. A meter moving does not prove that speech is intelligible or that music is free of distortion.
There are two distinct choices for repeated playback in OBS. A single file can use the built-in Media Source with its own Loop control. For a sequence of clips, OBS also documents a VLC Video Source that can take a playlist and has a Loop Playlist option; that route requires VLC to be installed. For a single festival recording, Media Source avoids adding a playlist tool and makes the repeat setting specific to the file you are using.
If you are actually planning a rotating programme rather than repeating one recording, a playlist may suit the editorial plan better, but test transitions, duration and audio between clips. A playlist is not the same as an event stream created in YouTube Studio, and it does not remove the need to configure an encoder connection. For a broader scheduling problem, the blog’s guide to using a CSV to schedule videos in a YouTube 24/7 stream covers a different kind of playback plan.
Enable and test local-file looping
Select the Media Source and turn on its Loop option in the source properties. OBS describes this setting as making the file play again once playback has completed. That is the repeat behaviour: OBS reaches the end of the local file and starts it again. YouTube does not loop the file on your behalf; it receives whatever picture and sound OBS is sending at that moment.
Test the source before connecting it to a public event. Let the clip reach its end and confirm that it starts again, rather than relying on the checked setting alone. Watch for a brief black frame, a silence gap, a jump in volume or an unwanted opening slate on the restart. If the ending is abrupt, a repeat will make that abrupt cut recur throughout the broadcast. Edit or export a smoother transition if it matters to the viewing experience.
Check whether the file has a deliberate start and finish. A festival recording might open with a countdown or a title card and end with credits; looping means viewers may see those parts each time the file cycles. That may be appropriate, but it should be a choice. If you need an uninterrupted atmosphere, review how the last frame and final audio lead back to the opening rather than assuming a loop will look seamless.
For reliability, keep the file in a stable local location and avoid moving or renaming it after configuring the source. Make sure the machine has enough free space and is not set to sleep during the event. These checks apply when OBS is running locally; they do not change the separate YouTube encoder setup. If you are using a computer to run an overnight broadcast, review how to configure OBS to reconnect automatically to YouTube Live, while remembering that reconnect behaviour does not fix a missing file or a rights interruption.
Create the event in YouTube Studio
In YouTube Studio, open the Live Control Room and create or schedule the stream. Choose a clear title, description, visibility and start time, then review the watch page details before sharing it. A scheduled event gives viewers a destination to return to; it does not mean the encoder is already sending video. If your event is public, make sure the page does not announce a start time that your team cannot support.
For an encoder stream, YouTube provides a server URL and stream key in the relevant stream settings. The interface may offer a key you already use or let you create a separate one. Keep that key confidential and match it carefully when configuring OBS. YouTube’s encoder setup instructions explain how the connection works; OBS and YouTube are separate products, not a single preconfigured festival-loop workflow.
YouTube recommends allowing substantial preparation time: its guidance says to set up encoders at least two hours ahead and to start the encoder at least 15 minutes before the scheduled event. Treat these as preparation recommendations, not a guarantee of readiness. That time gives you room to check the stream health, correct an incorrect key or scene, and verify the watch page before viewers arrive.
For a live event, decide who is responsible for each action: starting OBS, checking Live Control Room, watching chat if enabled, and ending the broadcast. If one person is doing all of this, write the order down. The playback loop can continue unattended in OBS while the stream connection still needs attention from someone who can respond to warnings or a dropped feed.
Connect OBS and preview the feed
In OBS, choose the streaming service and enter the server URL and stream key supplied in YouTube Studio. Check that you are connecting to the intended channel and event, especially if the operator has access to more than one channel. Start streaming from OBS when you are ready for the encoder to send its output. YouTube’s instructions describe the encoder connection; the Loop setting remains a local OBS playback setting.
Before making the event public or announcing that it has started, inspect the incoming preview in Live Control Room. Confirm that the expected festival footage appears, that the framing is correct and that the audio is audible. Check that the stream is associated with the intended event rather than a different scheduled stream. Then view the watch page as a viewer would, using a separate device or browser where possible, to catch issues that the control-room preview alone may not reveal.
Upload capacity matters more than download speed for sending an encoder feed. YouTube recommends leaving 20% upload-bandwidth headroom beyond the total stream bitrate and checking outbound bandwidth. That is platform guidance, not a universal bitrate prescription: actual needs depend on the settings and connection you use. Test the upload path at the location and time you expect to stream, and avoid saturating it with large uploads or other heavy traffic during the broadcast.
OBS output settings also affect the connection and picture. If you need to choose resolution, frame rate or bitrate, compare the available settings against YouTube’s current encoder recommendations and your measured upload capacity. The blog’s OBS quality settings guide for YouTube Live can help frame that decision, but no setting substitutes for checking the actual preview and stream health. Prefer a stable feed that your connection can sustain over a higher setting that fails intermittently.
Monitor the event and plan its archive
Once the broadcast is under way, monitor both sides of the workflow. In OBS, make sure the Media Source is still playing and the audio meter is active. In Live Control Room, look for connection or stream-health warnings. A local file repeating successfully does not prove that YouTube is receiving a healthy feed, and a healthy encoder connection does not prove that the recording itself is repeating as intended.
Agree how the team will respond to a freeze, silent feed or disconnection. Check whether the file continues to play, whether OBS is still streaming and what YouTube reports. If the encoder drops, a reconnect attempt may help restore the connection, but assess the preview before telling viewers the problem is resolved. The guide to monitoring an FFmpeg YouTube stream on a VPS addresses another encoder setup; the useful principle here is to have a person or a tested monitoring process observe the output, not just the playback source.
End the event deliberately. Stop the encoder feed in OBS, then review the Live Control Room and end the stream there as appropriate. Make sure the team knows which person has authority to end it, particularly if the stream key is used by more than one operator. A clear end prevents an accidental continuation into a blank scene or an unintended repeat after the public event is supposed to finish.
YouTube’s encoder setup guidance says streams under 12 hours are automatically archived. Do not turn that into a promise that every long broadcast will be archived: YouTube does not state that streams of 12 hours or more will always be saved. If you need a replay, plan a separate recording or archive workflow and verify the resulting video after the event. Check the current YouTube guidance, since archive handling and interface details can change.
For viewers in India, consider how the event timing, description and support contact will work for the audience, but do not treat location as evidence of a different technical loop mechanism. The core arrangement remains OBS playback feeding a YouTube encoder stream. If leaving a computer running through the event is the specific burden you need to remove, StreamNeo can run an uploaded video as a YouTube live stream without your computer staying on; it does not determine whether you have rights to the recording or settle YouTube’s review of it.
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 OBS loop the recording, or does YouTube?
The repeat setting belongs to OBS’s Media Source: it starts the local file again when playback completes. YouTube receives the encoder output through the server URL and stream key, so the broadcast connection and the file loop are separate parts of the workflow.
Can I replay a festival recording just because I have the file?
No. Possessing a copy does not establish permission to rebroadcast the video, performances or music. YouTube also scans live streams for third-party content, so resolve the rights position and any relevant Content ID allowlisting before you go live.
Will YouTube always archive a long stream?
No. YouTube says streams under 12 hours are automatically archived, but that does not establish that a stream at or above that duration will be saved. If a replay matters, plan an additional recording or archive approach and verify the result after the event.
Do I need a playlist source for one recording?
Usually not: OBS Media Source has a Loop option for a single local file. OBS’s VLC Video Source is worth considering for a playlist, but it requires VLC and introduces playlist behaviour you should test separately.