Start by checking whether the source in OBS is VLC Video or Media Source. VLC Video is the OBS source designed to hold a playlist; Media Source is for playing an individual media file, with its own file-loop setting. If the wrong source is being used, changing YouTube settings will not make the next video appear.
India does not require a separate OBS playlist fix. The useful evidence is where playback stops: inside OBS, in YouTube Live Control Room, or only for one viewer. Work through those checkpoints in that order, because each points to a different cause.
Identify the OBS source before changing anything
Open the Sources dock in OBS and look at the source name and type. Right-click the source, choose Properties, and confirm what OBS calls it. A source named “Playlist” may still be a Media Source if it was created with an informal name, so rely on the type shown in its properties rather than the label you gave it.
The two source types have different jobs. OBS documents VLC Video as a source that can contain a playlist of media files. Media Source is a separate source for one media file, with an option to loop that file. It is not the playlist source described in OBS's media-source guide.
That distinction explains a common symptom: one video plays repeatedly, while the owner expects OBS to move through several files. If the source is Media Source and its loop option is enabled, OBS may be doing exactly what that source has been configured to do. It is not evidence that YouTube is refusing to advance the playlist.
If you are unsure which source you created, make a note of the current properties before deleting or rebuilding anything. Record the file path, whether the source is visible, and whether the source is currently playing. Those details make it easier to restore a working scene if the change does not solve the problem.
For a wider explanation of arranging continuous content in OBS, see how to add music between videos in an OBS 24/7 stream. The important point here is simpler: first establish whether OBS has a playlist-capable source at all.
Confirm that VLC Video is the playlist source
If several files should play one after another, create or use a VLC Video source. In its properties, the playlist area should show the files that OBS is expected to play. If the list is empty, contains only one file, or points to a different folder than you intended, the source cannot advance to the expected item.
Do not assume that converting a Media Source into a playlist is a matter of enabling another checkbox. The ordinary Media Source has individual-file playback controls. The documented multi-item playlist controls belong to VLC Video. This is why adding more files to a folder will not, by itself, change the behaviour of an existing Media Source.
A practical test is to use two short, local files with uncomplicated filenames. Add both to the VLC Video playlist, keep the source visible in the scene, and watch the transition in OBS. This removes several variables at once: a long devotional recording, a missing file, a network location, and a scene that hides the source can all make a correct playlist look faulty.
If the short test advances but your normal files do not, the source type is probably not the main problem. Check the original files, their paths, and the playlist order. If even the short test remains on its first item, continue with the VLC installation and source settings below.
A playlist also depends on the files remaining available at the paths saved in the source. Moving a file after adding it, changing a drive letter, disconnecting a removable drive, or using a path that is unavailable when OBS starts can leave the list looking correct while playback fails at the transition.
Check VLC installation and matching architecture
VLC Video depends on VLC being installed on the computer running OBS. If VLC Video does not appear as an available source, or the source cannot open its files, check the VLC installation before rebuilding the scene. OBS's Media Sources documentation explains this dependency and the architecture requirement.
The architecture must match. A 64-bit OBS installation requires 64-bit VLC for VLC Video. Installing VLC is not enough if the installed edition does not match the OBS edition. Check whether your OBS is 64-bit, then install the corresponding VLC build from the official VLC site if necessary. Do not use a third-party download page for this check.
After installing or correcting VLC, close and reopen OBS. Applications do not always detect a newly installed dependency while they are already running. Then open the VLC Video properties again and test the playlist locally before starting another YouTube broadcast.
If VLC can open a file in its own player but OBS cannot move to it, that is useful evidence but not a complete test. OBS still has to access the same path through the VLC Video source, and the source may have visibility or playlist settings that VLC's standalone player does not use.
Avoid changing several parts of the setup at once. Install the matching VLC architecture, restart OBS, and test the existing source. If that fails, use two known-good local files and build a small test source. This gives you a clear comparison between a dependency problem and a problem in the original list.
Inspect playlist order and shuffle
Open the VLC Video source properties and inspect the order of the entries. Put the expected next video immediately after the current one for the first test. If the list contains a mixture of files from different folders, temporarily reduce it to two or three known files so that the transition is easy to identify.
Check Shuffle Playlist. When shuffle is enabled, the next item may not be the file you expected. That can look like a playlist that is stuck, especially when the list contains similar ambience loops or several versions of the same bhajan. Disable shuffle while diagnosing order, then enable it later only if random playback is actually wanted.
Check Loop Playlist separately. Looping the playlist means the list should begin again after its final item. It does not mean that a Media Source will become a multi-file playlist, and it does not correct a missing or unreadable item. First establish that the source reaches the next item; only then decide how the end of the list should behave.
Use descriptive filenames and avoid relying on the order in which files happen to appear in a folder. For example, names such as 01-morning-aarti.mp4, 02-mantra.mp4, and 03-evening-bhajan.mp4 make a simple sequence easier to inspect than filenames copied from a phone. The names do not control OBS by themselves, but they reduce mistakes when editing the playlist.
Also inspect Visibility Behaviour. OBS lists “Stop when not visible, restart when visible” as the default behaviour for this source. If the VLC Video source is hidden during a scene change, it may stop and restart instead of continuing as you expected. During testing, keep the source continuously visible in one scene. If that fixes the transition, decide whether to change the visibility behaviour or keep the source visible in the scenes used by your live channel.
Check looping and media-file availability
A playlist can fail at a transition because the next file is not available, not because the current file has reached its end incorrectly. Check every entry in the VLC Video list. Confirm that the file still exists, that the path is local and accessible, and that the account running OBS can read it.
Pay particular attention to files stored on an external drive, a network share, or a synchronised folder. A path that works during an afternoon test may not be available after a restart, sleep event, drive remount, or change of network connection. For an overnight stream, local files on a stable drive are easier to diagnose than files whose availability depends on another device.
Test the files individually. Open the source properties, temporarily leave only the suspected next file, and see whether OBS can play it. If it cannot, the playlist transition is only where the problem becomes visible. Repair or replace that file before testing the complete list again.
File format compatibility can also matter. Keep the diagnosis controlled by testing files that OBS and VLC already play correctly in the same setup. If one particular file stops playback while the others advance, compare that file's container, codec, and audio track with a working file. Do not treat a YouTube upload or a YouTube playback problem as proof that the local file itself is healthy.
For channels using long rain, temple, or ambience recordings, a useful overnight test is a short playlist containing two files that end quickly and one normal file. Watch at least one complete transition in OBS before starting the real broadcast. This is more informative than letting a single long file run for hours and discovering only in the morning that no transition was ever tested.
If your channel depends on a continuous loop rather than a sequence of separate files, compare the simpler approach in how to run event replays as a continuous YouTube live stream. The right arrangement depends on whether you need individual playlist items, a single long programme, or a repeated loop.
Test the source in OBS preview
Before looking at YouTube, watch the OBS preview or program output when the current file reaches its end. This is the most important separation in the diagnosis. If the next file does not appear in OBS, the fault is local to the source, playlist, VLC dependency, file path, visibility, or OBS performance.
For a clean test, use one scene with the VLC Video source visible. Keep the OBS window open and note the exact point at which the current item ends. Do not judge the result from a separate phone or from the public YouTube watch page yet. Those displays can have their own delay and buffering.
If OBS changes to the next file, note whether the audio changes too. A moving picture with missing or unchanged audio may indicate a media-file or audio-track issue rather than a playlist-order issue. If both picture and audio advance in OBS, the source has passed the local test and you should move to the encoder and YouTube checks.
If OBS freezes while its system is under load, inspect the OBS performance indicators and CPU or GPU usage. OBS's encoding performance troubleshooting guide recommends reducing output resolution or frame rate and simplifying scenes when rendering or encoding cannot keep up. Apply those changes only when the performance evidence points there; they are not the first response to a wrongly configured playlist.
Do not repeatedly restart the live broadcast while a local source test is still failing. A restart can make the public stream look different without fixing the underlying source. First get two files to advance in the OBS preview, then check the live path.
Separate OBS faults from YouTube stream faults
There are three different symptoms to separate:
| Where the problem appears | What it suggests | First check |
|---|---|---|
| OBS preview or program output | Local source, VLC, file, visibility, or computer performance | Source type, playlist entries, and a two-file test |
| OBS advances but Live Control Room does not | Encoder output, upload path, or YouTube ingest delay | Encoder output, stream-health messages, and connection status |
| Live Control Room advances but one viewer sees a freeze | Viewer device, player buffer, or local network | Another device and another connection |
If OBS advances but the Live Control Room preview remains on the old image, check the stream-health messages and the encoder's output. YouTube's live-stream metrics guidance explains where to inspect live information. The Live Control Room preview is a separate checkpoint from the picture shown in OBS.
YouTube recommends checking the encoder version, the audio and video directly in the encoder, encoder errors, and CPU load when troubleshooting a live stream. If the encoder looks healthy, test the outbound connection. This sequence helps distinguish a playlist problem from a stream that is failing to deliver the changing picture reliably.
Dropped frames are also a separate issue from playlist logic. OBS explains in its stream connection troubleshooting guide that dropped frames indicate an unstable connection or a bitrate the connection cannot sustain. A playlist may advance locally while the upload path delivers an old or interrupted picture to YouTube.
YouTube recommends leaving room between the total stream bitrate and available upload bandwidth, with 20% headroom recommended in its streaming tips. OBS gives starting guidance of about 75% of total upload speed for video bitrate. These are starting recommendations, not a guarantee for a particular Indian ISP, route, Wi-Fi network, or time of day.
If the picture advances in Live Control Room but one viewer sees the same frame, test another supported device and connection. Network congestion, buffering, and player delay can affect an individual viewer. A viewer-side freeze does not establish that the OBS playlist failed to advance.
Prepare a test that can survive the night
Once the source advances locally and the live preview follows it, run a controlled pre-broadcast test. Keep the source visible, use the intended playlist order, and watch at least one transition. Then leave the setup unchanged while you check the stream-health status and the public watch page from a second device.
Write down the result at each checkpoint: the time the item changed in OBS, the time it changed in Live Control Room, and what the second device showed. You do not need precise timing to identify the class of fault. You need to know whether the change happened nowhere, locally only, or everywhere except on one viewer's player.
For a long-running channel, remove avoidable dependencies. Keep media in stable locations, avoid changing filenames after adding them to the list, and prevent the computer from sleeping. If you use scene changes, verify that the VLC Video source remains visible or that its visibility behaviour matches your intended playback.
If the computer must remain on all night, include its power, internet, and restart behaviour in your test. A correct playlist does not protect against a sleep event, a disconnected drive, or a connection that drops after several hours. For readers comparing whether to keep a computer running, how to estimate 24/7 YouTube stream electricity cost using your state tariff covers the operating trade-off without changing the OBS diagnosis.
When the repeated local checks are sound but keeping the computer on and recovering a dropped broadcast is the practical problem, StreamNeo removes that particular burden by letting you upload the video, add the YouTube stream key, and have the channel run with automatic monitoring and restart from the cloud.
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 India change how an OBS VLC playlist works?
No evidence in the documented OBS behaviour establishes an India-specific playlist defect. The same source type, VLC dependency, playlist settings, and visibility behaviour apply; India mainly affects the connection path, available upload headroom, and viewer network conditions.
Why does OBS play one video repeatedly instead of moving to the next?
First check whether the source is Media Source with its individual-file loop enabled. If several files are intended, use VLC Video, confirm that the playlist contains the files, and check that the next file exists at its saved path.
OBS advances, but YouTube shows the old video. What should I check?
Compare OBS with the Live Control Room preview and inspect YouTube's stream-health messages. Then check encoder output, dropped frames, upload headroom, and CPU load before changing the playlist again.
Why does the public watch page lag behind OBS?
Live playback can have delay and buffering, so the public page is not the same checkpoint as the OBS preview. Test the Live Control Room and another viewer device or connection before concluding that the playlist is stuck.