A playlist that appears frozen during a 24/7 bhajan stream can mean several different things: the media source has stopped, a scene change has hidden or paused it, OBS cannot keep up with rendering or encoding, or viewers are buffering while your local playback continues. Start by checking which of those is happening; the title alone does not identify the cause.
The right fix depends on the source you added and the symptom you can observe. First identify whether you are using OBS Media Source for a file or VLC Video for a playlist, then check playback, visibility, OBS indicators and viewer reports in that order.
Identify what appears frozen
Before changing a setting, note what you can actually see. Is the preview frozen on one image? Has the audio stopped as well? Did the source reach the end of a file or playlist? Does it stop only after changing scenes? Or does the OBS preview continue while people watching YouTube report buffering? These observations point to different branches of the diagnosis.
If you are beside the computer, listen to the audio and watch the source in OBS. A still image with continuing bhajan audio is not the same symptom as a source that has stopped advancing entirely. If the playlist appears stuck at the same item but the video is moving, it may be playing normally rather than being frozen. Check the current item and its position before resetting anything.
Ask a viewer to describe what they see, but do not treat their report as proof that the local source stopped. A viewer may have a buffering or playback problem even when OBS is still sending a moving picture. Conversely, a smooth OBS preview does not prove that the stream is reaching viewers correctly. The local and delivered pictures are separate checks.
If you did not witness the moment it stopped, write down when it was noticed and what happened immediately beforehand: a scene switch, a file ending, a computer restart, or a change to the stream connection. Keep the notes modest and factual. A useful first record is the source type, whether local audio and video continue, whether the OBS preview moves, and whether OBS shows an output warning.
Check whether the OBS source itself stopped
OBS has two relevant source types, and their controls are not interchangeable. Media Source is intended for a media file; VLC Video can play a playlist and depends on VLC being installed. The OBS Media Sources documentation describes the controls for both, so begin by opening the source properties and identifying which source you are troubleshooting.
For a single bhajan video in Media Source, inspect Loop. That control is relevant when one file should start again after it finishes. If the source reaches the end and remains stopped, check that the loop setting matches the intended behaviour. If the source stops in the middle of a file, looping is unlikely to explain that symptom; record the file position and look at other possibilities rather than toggling unrelated controls.
For a playlist in VLC Video, inspect Loop Playlist. OBS describes this as controlling whether the source restarts when it has run out of media files. A playlist that plays through its items and then ends is a case where this setting and the playlist contents deserve attention. Do not assume it is correct merely because OBS lists it as enabled by default; check the actual property and save your intended setting.
Also look at the playlist itself. Confirm that the files you expect are present and that the final item is not simply the end of a short playlist. If the source advances through some items but stalls on one particular file, note its name and format. That is a more useful clue than repeatedly restarting the entire broadcast.
If VLC Video is unavailable or behaves unexpectedly, check the prerequisite: VLC must be installed, and OBS notes that 64-bit OBS requires 64-bit VLC. Match the VLC installation to the version of OBS you are running. This is a source-availability and compatibility check, not a general remedy for every playback interruption.
Keep a simple distinction in mind: a source reaching the end, a source stuck on one item, and a source that stops only after a scene transition are not the same failure. The guide to looping a folder of MP4 files on YouTube Live covers a different playback arrangement, but the same discipline applies: verify what is in the queue and what should happen at its end.
Check scene visibility and source behaviour
A source can stop because it is hidden, even if its loop controls are set correctly. In OBS, visibility is controlled through scenes and their source lists. If playback consistently halts after you switch scenes, inspect whether the playlist source remains visible in the active scene and whether your scene arrangement is designed to keep it playing.
VLC Video has a Visibility Behaviour property. Its options determine whether the source continues, pauses or stops when it is not visible. Choose the behaviour that matches the way your scenes are meant to work. If the bhajan audio should continue under a different visual scene, a setting that pauses or stops when hidden would not match that plan. If the source is meant to stop when hidden, then stopping after a deliberate scene change may be expected rather than a playlist fault.
Reproduce the scene change while watching the source. Note whether audio and video continue, pause or stop when the source becomes hidden, then return to the original scene and see whether playback resumes. Change one visibility property only if the observed behaviour conflicts with your design. Avoid changing the loop control at the same time, because you will not know which change affected the result.
The OBS Sources Guide explains how sources are arranged and used in scenes. It is useful when you are unsure whether the media source exists in the active scene or is merely hidden behind another source. Check the source list and visibility indicators before rebuilding scenes or removing a source that may still be part of the intended layout.
For a simple always-on channel, keep the scene design easy to reason about. If you have one visual scene and one playlist source, a scene change should not be part of ordinary playback. If you use multiple scenes for a title card, devotional image or announcement, decide explicitly whether audio should continue when the playlist is not visible. That choice is more reliable than relying on an accidental default.
Inspect OBS load and output indicators
Now check whether the media is actually advancing locally and whether OBS can produce its output. If the preview moves but looks jerky, or OBS indicates encoding overload, investigate performance rather than treating the playlist as though it reached its end. A load problem can make the output look choppy even while the source continues playing.
OBS's Encoding Performance Troubleshooting guide recommends reducing expensive sources, using media at a resolution suited to the output, limiting unnecessary filters and simplifying complex scenes. Apply these ideas when you see a performance symptom, such as a choppy preview or an encoding warning. They are not universal fixes for a playlist that pauses on a scene change or stops at the end of its files.
For a bhajan stream, review what is in the scene: animated backgrounds, browser sources, multiple videos, filters and other active elements can add work. Test with a simpler scene if the output is struggling. If that improves the picture, reintroduce elements one at a time so you can see which addition makes the load worse. Do not lower every quality setting at once; that can obscure the cause and make the channel look worse without addressing the issue.
A useful distinction is whether the media timeline advances. If it advances normally in the source while the output stutters, the playlist is not necessarily frozen. If the timeline itself is stationary and audio has stopped, return to the source and visibility checks. OBS load indicators and source playback answer different questions, so record both rather than using one as a substitute for the other.
Do not infer performance trouble from a viewer complaint alone. Check the local preview and OBS indicators at the same time as the report if possible. For an overnight stream, a brief written log of what you observed is more valuable than changing encoder, resolution and source settings between each check.
Separate local playback from viewer buffering
A stream can be playing smoothly inside OBS while delivery to YouTube or playback for a viewer is interrupted. Ask a viewer to refresh or check from a separate connection, and compare their report with what OBS is showing. This is a diagnostic comparison, not a guarantee that the issue lies with the viewer.
OBS distinguishes dropped frames from a media source stopping. Its Stream Connection Troubleshooting guide treats dropped frames as a connection stability or bitrate-capacity issue and provides network checks. If OBS continues to play the file but reports dropped frames, follow that connection branch rather than changing Loop Playlist. A loop setting cannot fix an unstable delivery path.
Likewise, if the OBS preview and output remain smooth while one viewer sees buffering, do not call the playlist frozen on that evidence. Check whether other viewers report the same thing and whether the stream continues to appear live. Reports from different viewers can help separate a local playback problem from a broader delivery issue, though they do not establish the cause by themselves.
If OBS itself shows choppy output or encoding overload, that is another distinct branch. A connection warning, an encoding warning and a stopped source each call for different checks. Keep the wording precise when asking for help: “the source timeline stopped at this file,” “the preview is moving but output is choppy,” or “OBS is playing normally but viewers buffer” gives a more actionable description than “the playlist froze.”
For a deeper comparison of local media playback and viewer-side symptoms, see why a church stream can buffer even when its source video is local. The same distinction matters for a bhajan channel: a file on your computer can be healthy while the route from OBS to a viewer has trouble.
Apply one source-specific fix at a time
Once the symptom and source type are clear, change only the control that fits. For Media Source playing one file, test Loop if it stops at the end. For VLC Video playing a playlist, test Loop Playlist if the sequence ends without restarting. For a source that stops when hidden, choose the appropriate Visibility Behaviour. For a missing or unusual VLC source, verify the VLC installation and 64-bit match.
Do not change Network caching (ms) simply because the word “freezing” appears in a report. VLC Video exposes a network caching property, but it is not a general cure for a local playlist freeze. Consider it only when you have a specific network-media symptom that justifies targeted troubleshooting, and record the original value before testing a change.
For each test, note the source type, the one property changed, what the source did before and after, and whether the symptom returned. If nothing changes, put the property back before trying another branch. This is especially useful when a channel has been running unattended: the next person checking it can distinguish an attempted fix from the original configuration.
If the issue is clearly an OBS performance symptom, simplify the scene or reduce expensive sources as a separate test. If the problem is dropped frames while local playback continues, investigate the connection and bitrate path. Do not combine those changes with source loop settings; otherwise a better or worse result will not identify the relevant cause.
If your channel depends on a single local computer running through the night, recovery also means considering what happens when that computer or OBS needs attention. StreamNeo addresses the specific burden of leaving your own computer running for a file-based YouTube broadcast: after you provide the file and channel key, playback can continue with your computer switched off, with monitoring and restart if it drops. That is a different operating arrangement, not a diagnosis or a guarantee that every source issue disappears. It is YouTube-only, so it does not fit a channel that needs the same broadcast sent to another platform.
Retest and monitor the stream
After a targeted change, test the exact condition that caused the problem. If the playlist stopped at its end, let it reach the end again and confirm whether it restarts. If it stopped after a scene change, switch scenes and watch the source behaviour. If it was choppy, observe both the preview and output indicators with the simplified scene. A short successful check confirms that the change affected that symptom; it does not prove that a 24/7 channel will never encounter another interruption.
Use a second device or ask someone to check the live YouTube player while you watch OBS. Confirm separately that the source advances locally and that the delivered stream appears to move. If local playback is sound but the viewer-side stream buffers, return to connection troubleshooting. If the local source stops, go back to source and visibility checks.
Keep a small run note with the date, OBS version, operating system, source type, file or playlist involved, scene changes and the time of any failure. If the cause remains unclear, this context and an OBS log covering the failure can help someone investigate. The research available for this issue does not establish a single fix or a particular endurance guarantee, so avoid assuming that one clean retest settles every possible failure mode.
For channels that rely on a continuous loop rather than a live operator changing scenes, it may help to compare the trade-offs of looping a white-noise video overnight with your own file-based arrangement. The content differs, but the operational question is similar: what should happen at the end of the media, and how will you notice if playback or delivery has stopped?
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 use Media Source or VLC Video for a bhajan stream?
Use Media Source when you are playing one media file, and VLC Video when you need a playlist. The controls differ, so identify the source in OBS before changing loop settings. VLC Video also requires VLC to be installed, with a matching 64-bit installation for 64-bit OBS.
Why does my playlist stop when I change scenes?
VLC Video's Visibility Behaviour can pause or stop a source when it is not visible. Check whether the source becomes hidden during the scene change and choose the behaviour that fits your scene design. If playback stops even while the source stays visible, investigate the source itself instead.
Is buffering on YouTube proof that the OBS playlist froze?
No. OBS may still be playing the media while dropped frames or a connection issue affects delivery, or an individual viewer may have playback trouble. Compare the local OBS preview and indicators with reports from viewers before changing playlist controls.
What should I do if none of these checks identifies the problem?
Record your operating system, OBS version, source type, file formats, scene changes and the time the symptom occurred. Preserve the relevant OBS log and describe whether local audio, video and the preview continued. Those details are needed for a more precise diagnosis; there is no single source-independent fix established for every playlist.