To run lessons during Indian school hours, schedule a YouTube Live event in Studio and separately configure playback software such as OBS Studio to send the lesson videos. The scheduled event creates the viewer-facing live page; it does not start lesson files or guarantee that the broadcast begins on time.
For a local playlist of files, OBS Studio’s VLC Video source can play items in order and loop them. Treat the timetable, the YouTube event and the playback sequence as three things to verify, especially the exact date and local time displayed in Studio.
Plan the school-hour timetable
Start with the school timetable, not the software. Write down the intended date, the local start and finish time, the lessons in order, and any break or transition that viewers should see. If the school timetable is 09:00–12:00 India time, for example, decide whether the live event should begin at 09:00 sharp or whether an opening slide and welcome period should precede the first lesson. That decision affects the files and the event time you prepare.
Make a simple running order with one row per item: lesson name, file name, expected duration, and what should follow it. Include an opening slate, a break screen or closing card if useful. Durations are planning aids, not a promise that a video will finish at an exact clock time: a file may be replaced, trimmed or encoded differently, and a manual transition may take longer than expected.
Decide whether the stream is meant to be watched live with interaction, or whether the school mainly needs lesson material available to view at a chosen time. A live event can present a live feed and may include chat; scheduling an uploaded video is a publication workflow instead. YouTube’s encoder setup guidance describes scheduled live events, while YouTube’s separate video upload and publication guidance covers uploaded videos. Choose based on how teachers and pupils will use the session, not on the word “schedule” alone.
Also decide who is responsible for the machine running OBS, watching the preview, and responding if a lesson fails to advance. A timetable can be fixed while the playback still needs a person to start the encoder and check the output. If lessons span subjects or regions, it can help to keep media and event details clearly separated; the approach in managing separate playlists for multiple regional channels is relevant when naming and organising distinct runs.
Schedule the YouTube Live event
In YouTube Studio, go to Create, choose Go Live, open Manage, and select Schedule Stream. Create a new event or reuse prior settings, then enter its title, description, audience and privacy choices, along with the intended start time. Save the event and open its watch page to check what viewers will see and to share the link with the school community.
A scheduled broadcast is one event and one video page, not a queue of lesson items. The YouTube Live Streaming API describes a broadcast as representing a YouTube video; it does not turn a channel playlist into consecutive live lesson broadcasts. Keep the concepts distinct: Studio schedules the event and viewer page, while an encoder such as OBS sends the live picture and sound. The LiveBroadcasts API reference is useful if you need to understand that event model.
Select public, unlisted or private according to the intended audience and the school’s access requirements, then test that the right people can open the event page. An unlisted link is convenient to distribute but should not be treated as a substitute for checking who receives it. If the event is public, make sure the title and description do not expose pupil details or other information that should stay within the school.
YouTube says a channel must be verified and have no live-streaming restriction in the preceding 90 days to go live. First-time live activation may take up to 24 hours, so complete this step well before the first lesson rather than during the school morning. Check the current YouTube live-streaming eligibility guidance because channel status and platform requirements can change.
If you are setting up a recurring school timetable, do not assume that saving one event schedules every later lesson or date. Inspect the controls available in the current Studio interface and verify each resulting event page. The reviewed guidance establishes scheduled event times, but does not establish that Studio can run a school bell timetable or manage a repeating playlist for you.
Prepare lesson files and playback order
Gather the lesson videos as local files that you have permission to use. Put them in a dedicated folder and give each a clear name such as 01-maths-introduction.mp4 or 02-reading-session.mp4. A numbered prefix makes the intended order visible when you review the folder, though the playback order must still be checked in OBS. Keep a copy of the original files and note which version is approved for the session.
Play each file before the event. Check that the intended picture, voice, captions or slides are present, and that the beginning and end do not contain an accidental blank section. Confirm that the audio is audible at an ordinary listening level. If a lesson includes material for one class only, check the title card and narration before sending it to a public or shared event.
OBS Studio’s VLC Video source is designed to play multiple local files. Its documented controls allow you to preserve the listed order rather than shuffle the items and to enable looping. VLC must also be installed for this source to work. Read the OBS Media Sources guide and test with the same files and settings you intend to use; a YouTube channel playlist is not the input to this local-media workflow.
Choose looping deliberately. If the lesson run should stop after the final item, leave looping off and arrange a closing slate or a person to stop the feed. If pupils may join late or the school wants the content to repeat, enable looping only after deciding where the sequence should restart. A repeated opening lesson may be confusing during a timetable that expects a different class or topic after each period.
If the playlist is long, calculate the approximate total runtime from the file durations and compare it with the planned event window. Use that estimate to spot a likely early finish or a sequence that would run past the school day, not as a guarantee of exact transitions. For a discussion, teacher introduction or changing class group between files, keep a planned pause or holding screen rather than relying on the previous lesson to end at precisely the bell.
Set up OBS VLC playback and looping
Install OBS Studio and VLC on the computer you will use for the broadcast, then open OBS and create a scene for the lesson output. Add a VLC Video source and select the intended media files. Review the list in the source properties, move items into the required order, and make sure shuffle is not selected. If the source displays a black screen or refuses to load a file, test VLC installation and file access before changing the YouTube event.
Set the source’s loop option to match the timetable. A finite lesson block usually needs a deliberate ending; a repeating revision session may need the sequence to loop. Keep the source visible in the scene, and add any title, school logo or break slate as a separate visual element only if you have checked how it layers with the video. Do not obscure lesson captions or slides with overlays.
OBS is the encoder in this setup: it combines the scene and media playback, then sends that output to the YouTube event using the stream URL and stream key shown for the event. Keep the key private; anyone with access to it may be able to send a feed to the event. YouTube’s event documentation explains connecting an encoder, and the encoder and stream-key steps should be followed in the current Studio interface.
Do not treat a successful file preview inside OBS as proof that viewers can see the stream. The OBS preview checks the local composition; the Live Control Room preview checks what YouTube is receiving. Check both. If you are changing scenes or media sources, verify the audio source remains active after each transition. The troubleshooting notes on OBS audio stopping after the first video cover a failure mode worth checking before a long lesson block.
For a sequence requiring different events at different lesson periods, plan how the feed will change and who will perform that action. VLC’s playlist controls handle a sequence of local files, not school-bell scheduling or separate YouTube events. Do not assume that arranging lesson files in OBS will automatically start or stop broadcasts at each period boundary.
Check the local date and time in Studio
Before saving the event, compare the date and time shown on the Studio screen with the school’s intended local timetable in India. Read the date as well as the clock time: a correct hour paired with the wrong day is still a missed lesson. Do not rely on memory, a copied calendar invitation or another person’s screenshot without checking the event currently open in your own Studio account.
After saving, open the event’s watch page and check its displayed upcoming time. If you share the link, ask a colleague to confirm the time they see and that the page is accessible. Where the interface displays a timezone or converts times for the viewer, interpret it carefully; the important check is that the event page and the school’s intended local date and time agree. The exact timezone controls may vary, so verify what the current Studio screen actually shows rather than assuming a setting.
Write the confirmed event time in the school’s timetable and in the OBS run sheet, with the timezone stated plainly, for example “India local time”. If a teacher or operator is in another location, make sure both people are comparing the same local reference. A calendar reminder is useful, but it does not replace checking the Studio event after changes.
If the timetable changes, update the event and then recheck the watch page and shared link. A changed school period, a holiday or a substitute lesson can make an otherwise correct scheduled event misleading. Keep the file order and the event details together in a run sheet so the operator does not start the right playlist against the wrong event.
Test the event and lesson transitions
Run a rehearsal before the first class, using the intended event settings and the actual media files. YouTube advises encoder users to set up at least two hours before a stream and start the encoder at least 15 minutes before the scheduled time. Treat these as platform recommendations for preparation, not as a promise that the broadcast will start automatically. The early start gives you time to inspect the incoming feed and fix a wrong scene, missing file or silent microphone.
In Live Control Room, check the preview, stream health, picture motion and sound. Confirm the event is reachable from the channel or its watch page using the same privacy setting planned for class. Ask someone not operating OBS to open the viewer link, since the operator’s signed-in account may have access that pupils or teachers do not. YouTube’s live-stream setup checklist includes previewing and monitoring the stream.
Test transitions by letting one lesson finish and the next begin. Listen for a silent gap, duplicated audio or a source that remains on the previous file. Check that any break slate appears as intended and that the first frame of the following lesson is not hidden. If the sequence loops, test the final-to-first transition too. For more general continuity planning, the guide to keeping a YouTube live stream running while your laptop is off explains why the operator’s computer and an always-on broadcast are different concerns.
Network capacity matters because OBS has to upload the live feed continuously. YouTube recommends planning 20% upload bandwidth headroom beyond the total stream bitrate. Check the actual connection from the location where the stream will run, and avoid judging it only by a speed test taken elsewhere or at a quieter hour. If the connection cannot sustain the planned output, reduce the stream settings and rehearse again.
Make a simple failure plan: who can contact the operator, how a lesson can be skipped if its file fails, and what to tell viewers if the event needs to be rescheduled. Keep a local copy of the source files and, if a replay matters, plan a local recording or archive backup. YouTube says streams under 12 hours can be automatically archived, but streams longer than 12 hours may not be captured; its archive guidance is worth checking for current details. Do not rely on the archive as the only copy of a lesson recording.
Before committing to a production workflow, decide who will be present to check the event and transitions. If the specific problem is keeping a broadcast running while the classroom computer is switched off, StreamNeo removes that particular need to leave your own computer on by running an uploaded video as a YouTube live stream; it does not replace checking the timetable, event page or suitability of the lesson files.
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 Live event play my lesson playlist?
No. The scheduled event creates the YouTube live page and time, while OBS or another encoder must provide the actual feed. Configure and test lesson playback separately.
Can OBS play a YouTube playlist in VLC Video?
The OBS VLC Video source described here is for local media files, not for importing a YouTube channel playlist as a queue. Put the authorised lesson files in the intended order, then verify the source list and transitions in OBS.
Will the stream start exactly when the school timetable says?
A scheduled time does not guarantee that the encoder is running or that the feed is ready. Start early, inspect the Live Control Room preview and have an operator responsible for the broadcast.
What should I check if the event time looks wrong?
Compare the full date and time shown in Studio with the school’s intended local date and time in India, then inspect the saved event page. If the timetable changes, update the event and confirm the shared page again.