If your lecture stream restarts when a video ends, first find out which playlist has reached its end. A local file or encoder playlist may have stopped sending content, or the viewer’s YouTube app may simply have reached the end of its own playback queue.
For a single lecture in OBS, enable Loop in the Media Source properties. For several lectures, use a VLC Video source with an ordered playlist and enable Loop Playlist, then test what happens when the final file finishes. These settings repeat the source media; they do not, by themselves, guarantee that the live broadcast stays connected through a computer, encoder, power or network failure.
First identify which playlist has ended
The word “playlist” can describe two different things in this situation. The first is the source playlist inside your encoder, such as OBS. It is the collection of files being played locally and sent to YouTube. The second is a viewer’s playback playlist or queue in YouTube, a television app, a phone or a browser.
Those two failures look similar from a distance. Someone may report that “the live stream restarted”, while the encoder is still connected and sending the same broadcast. Alternatively, the viewer may see the content begin again because the source file ended and OBS started it from the beginning, even though the YouTube live connection never stopped.
Start by checking the encoder computer while the viewer reports the problem. Is OBS still showing the scene and an active stream? Is the media source playing, paused or displaying its final frame? Does the timer for the current file return to the beginning? If the encoder continues sending frames, the source or viewer playback needs attention rather than the YouTube broadcast itself.
Then check the live page from a separate device. A phone on mobile data is useful because it does not share the encoder computer’s local playback state. If only one viewer, app or television behaves differently, do not change the encoder immediately. Compare the same live URL in a browser and in the device’s YouTube application.
This distinction matters for a devotional lecture channel, a study stream or a local-language teaching loop. You could spend time changing OBS settings when the issue is a viewer’s queue, or investigate YouTube playback when the encoder has actually run out of media. Treat the encoder loop as a possibility, not as a diagnosis of every autoplay or restart report.
If the encoder source has stopped sending
A source-ending problem normally leaves a visible clue in OBS. A Media Source may stop on its last frame, disappear, or remain in the scene without changing. A playlist source may stop after the final item. The YouTube live page can still exist while the incoming picture has become static or blank.
For one local lecture, select the Media Source in OBS and open its properties. Enable Loop. OBS documents this option as repeating the media after playback completes. If you want the lecture to begin at the start whenever the source becomes active, check Restart playback when source becomes active as well.
These are separate behaviours. Looping handles the normal end of the file. Restart playback controls what happens when the source is activated again, for example after a scene change or when OBS loads the scene. Do not assume that one setting replaces the other.
Also inspect what the source displays at the end. OBS provides Show nothing when playback ends, which hides the source after completion rather than leaving its final frame visible. With Loop enabled, an ordinary uninterrupted playback should return to the beginning instead of reaching that final state, but the end-of-playback behaviour is still worth checking during a test.
If the source is inside a scene that changes, inspect whether it is visible when the lecture reaches its end. An invisible source can follow different rules from a visible one, particularly with VLC Video. A source that pauses or stops while hidden may appear to have failed when it is brought back later.
Before changing anything else, save the source properties and watch the encoder locally. Look for the file timer returning to the beginning. If it does not, the loop setting is not applied to the source that is actually on air, or the source is not the type you think it is. OBS can contain several scenes and sources, so check the active scene rather than an unused test source.
Loop one file or an ordered lecture playlist
Choose the simplest source that matches the channel. If one complete lecture is meant to repeat, a Media Source is easier to inspect because there is only one file and one loop control. If the channel should play several lectures in a fixed order, use a VLC Video source and add the files to its playlist.
For a VLC Video source, enable Loop Playlist. OBS describes this as the setting that makes the source restart after it has run out of media files. Keep Shuffle Playlist off when the order matters, such as an introductory lesson followed by the main lecture and then a question-and-answer recording.
The source choice affects more than the number of files. A single repeating file gives you a predictable transition, but viewers will hear and see the same opening at each cycle. A playlist can provide variety and a more natural schedule, but it creates more points to check: file order, missing media, different audio levels and the transition from the final item to the first.
| Requirement | Suitable OBS approach | Main check before going live |
|---|---|---|
| Repeat one lecture | Media Source with Loop enabled | Confirm the timer returns to the beginning |
| Play several lectures in order | VLC Video with an ordered playlist and Loop Playlist enabled | Confirm the final file returns to the first |
| Keep a fixed teaching sequence | VLC Video with Shuffle Playlist disabled | Verify the visible order matches the intended schedule |
| Hide the last frame after a file ends | Media Source end-of-playback display setting | Test whether the source disappears or loops as intended |
The VLC Video source requires VLC to be installed. OBS documents an architecture requirement: 64-bit OBS requires 64-bit VLC. If VLC Video is missing from the source list, check the installation and architecture before trying to repair the playlist itself.
A useful way to organise the files is to use clear names that sort in the intended order, such as 01-introduction, 02-lesson, and 03-revision. That does not replace checking the playlist inside OBS, but it makes mistakes easier to spot. Keep a copy of the final playlist order in your channel notes so you can rebuild it if the computer needs to be replaced.
For channels built from lessons, recordings and music between sessions, the continuous podcast stream guide covers the same broader scheduling question from a different format. The important principle here remains the same: media must continue at the source if the live encoder is expected to keep sending a changing picture.
Check visibility and playlist behaviour in OBS
A VLC playlist can be correctly configured and still behave unexpectedly when its source is not visible. OBS provides a Visibility Behaviour setting for VLC Video. It controls whether playback continues, pauses or stops when the source is hidden by a scene change.
The documented default is Stop when not visible, restart when visible. That may be appropriate if each scene should begin its media from the start, but it is not appropriate if the lecture must continue playing while another scene is shown. Decide which behaviour matches the broadcast design, then test a real scene change rather than relying on the label alone.
For example, suppose your live layout shows a title card for a short announcement, then returns to the lecture scene. If the VLC source stops while hidden, the lecture may restart when the scene becomes visible. That restart is caused by source visibility, not by YouTube’s viewer playback. If the lesson should continue underneath the announcement, choose a visibility behaviour that allows it to keep playing.
Do not add extra scene changes merely to cover a loop problem. Every additional transition creates another state to test. A straightforward lecture scene with the media source visible is easier to diagnose than a collection of nested scenes, browser sources and temporary layouts.
If you use multiple scenes, write down which one is live and which sources belong to it. During a test, switch scenes deliberately and watch the VLC playlist position. If it jumps to the first item, you have found a source-visibility rule or an activation setting that needs changing.
Do not confuse encoder looping with YouTube viewer playback
YouTube’s own loop control is a viewer-side playback function. It can repeat a video or playlist for the person watching, but it is not the OBS setting that feeds a local lecture file into a live encoder. Turning on a viewer’s loop control will not make an OBS source continue sending media to an existing live broadcast.
This is why reports from viewers need careful wording. “The lesson started again” can mean that the source looped normally, that the live broadcast disconnected and a new session began, or that the viewer’s application replayed content. Ask what appeared on screen, whether the live badge disappeared, and whether the same live URL remained open.
YouTube’s guidance on looping videos or playlists is useful for understanding the viewer control. It does not replace the encoder configuration. Keep the two questions separate: what is OBS sending, and what is the device doing with what it receives.
The same separation applies to a television or set-top device. Some apps resume, replay or move between items differently from a desktop browser. A viewer may also have enabled an app-level repeat option without realising it. If the problem appears only on one device, record the app name, device model and exact point at which playback returns to the beginning.
Do not promise viewers that changing their playback loop will repair a source that has stopped. Conversely, do not rebuild the OBS playlist because one viewer’s application has reached the end of its own queue. A repeatable diagnosis starts with evidence from both ends.
Check the hosting service and the live session
Once the source loop is configured, check the hosting service’s behaviour separately. YouTube receives an encoded live feed; it does not know that your lecture files are intended to form a repeating course unless the incoming stream continues. A source loop can keep producing media, but it cannot repair a stopped encoder, a lost network connection or a computer that has gone to sleep.
YouTube’s HLS streaming documentation discusses ingestion details such as segmented delivery and latency. Those details are not a remedy for a file reaching its end in OBS. Do not change ingestion settings simply because a local lecture has finished.
Check whether the live event remains the same when the problem occurs. If the stream page and event continue while the image freezes, investigate media playback, encoding load or the network feed. If the broadcast ends and a new event starts, investigate the encoder’s connection, scheduling and any automation around it.
The available documentation does not establish that a particular computer and streaming setup will stay connected indefinitely or reconnect after every failure. A looping file is therefore one part of a 24/7 design, not an uptime guarantee. If the channel matters overnight, plan for the possibility that the source, encoder or connection can fail.
For a wider comparison of always-on formats, the guide to turning photos into a 24/7 live stream explains why the media pipeline must be treated separately from the public live page. A lecture channel has the same operational concern even when its content is a single video file.
If you do not want a local computer to remain responsible for replaying the file, StreamNeo removes the particular burden of leaving the lecture file and channel connection running on your own machine: upload the video, provide the YouTube stream key, and let the cloud broadcast handle automatic monitoring and restart behaviour when the stream drops.
Test after the final file reaches its end
Do not stop testing when the Loop checkbox is enabled. The meaningful test is the transition at the end of the file or the final item in the playlist. A short lecture or trimmed test copy is useful because it lets you observe the boundary without waiting through the full programme.
Run the test as a private or unlisted broadcast where appropriate. The guide to testing a live stream without going public covers that workflow. Use a separate device as the viewer and keep OBS visible on the encoder computer.
Record what happens at the transition. Does the Media Source timer return to the beginning? Does the VLC playlist move from the last item to the first? Does the source disappear? Does the scene change? Does the live event remain connected? Each answer points to a different setting or failure mode.
Test the exact file type and audio arrangement you intend to use. A short test clip can prove that the loop control works, but it cannot prove that a long recording has no playback issue, that all playlist paths remain available or that audio stays in sync over the full programme.
Repeat the test with the scene hidden if your normal broadcast uses scene changes. For VLC Video, this is where Visibility Behaviour matters. Also test after restarting OBS, because a configuration that works during one session may not be the configuration that loads when the computer starts again.
Keep a small record of the test date, source type, playlist order, loop settings and what the viewer device showed. You do not need a complex monitoring system to make this useful. A written note can prevent you from repeating the same overnight experiment after changing several settings at once.
Monitor the encoder and live output
A 24/7 lecture stream needs two kinds of monitoring. Encoder monitoring tells you whether the source is still playing and whether OBS is still sending. Viewer monitoring tells you whether the public output is visible, moving and available from a separate device.
On the encoder computer, watch the active scene, source status and stream indicators. Keep the computer from sleeping, and check power and network connections before leaving the channel unattended. A source loop cannot continue if the operating system pauses the application or the computer loses power.
On the viewer side, open the live page independently and check the picture at intervals that fit the importance of the channel. Look for a moving image, audible speech and the expected live status. If you use a television, phone or secondary browser for monitoring, note which device produced the report because playback behaviour is not identical everywhere.
If a failure occurs, change one thing at a time. First capture whether OBS is still connected and whether the source is moving. Then check the live output. Restarting everything immediately may restore the picture, but it removes the evidence needed to find the original cause.
A local OBS arrangement gives you control over the files, scenes and encoder settings, and it can suit a channel that already has a reliable computer and network. The trade-off is that you remain responsible for sleep settings, power, updates, the streaming application and recovery after a failure. A hosted workflow reduces the need to leave that equipment running, but you still need to verify the current service terms, YouTube requirements and the behaviour of your own channel before relying on it overnight.
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
Should I enable Loop or Loop Playlist in OBS?
Use Loop for one Media Source file. Use Loop Playlist for a VLC Video source containing several files. The second option is for the playlist inside the encoder, not for a viewer’s YouTube playback queue.
Why does my lecture restart only when I change scenes?
The source may be stopping or restarting when it becomes hidden. Check the VLC Video Visibility Behaviour setting and the source activation settings, then test the exact scene change used by your broadcast. A viewer-side replay is also possible, so confirm what OBS was doing at the same moment.
Will looping the file guarantee a 24/7 live broadcast?
No. It only addresses the media reaching the end during ordinary playback. Power loss, sleep, application failure, network loss or a disconnected live session can still interrupt the broadcast.
How can I tell whether YouTube or OBS is responsible?
Watch OBS and the public live page at the same time from separate devices. If OBS is still connected and the source timer loops, investigate the viewer app or device. If the source stops or the live connection ends, investigate the encoder source, scene behaviour, computer and network.