For one Hindi bhajan video repeating continuously, add it as an OBS Media Source and enable Loop. For a sequence of recordings that should play in order and start again at the end, use VLC Video and enable Loop Playlist; the two source types do different jobs.
Before leaving a stream running, check that the image fits your canvas, the bhajan is audible in the stream mix, and playback returns to the beginning as expected. Then test the complete stream in YouTube’s preview and monitor its health rather than assuming an OBS setting alone makes an all-night broadcast reliable.
Choose one bhajan file or an ordered playlist
Start by deciding what viewers should hear after the current recording finishes. If you have one long bhajan video and want that same file to repeat, a Media Source is the direct route. If you want several recordings to play in a deliberate order before the sequence starts again, use a playlist source instead.
The distinction matters because a file’s Loop setting is not a playlist control. A single file can contain a full programme, or several separate files can form one programme; the right OBS source depends on how you have prepared the material. Making that choice first avoids building a scene around a control that cannot produce the intended sequence.
| Your playback plan | OBS source | Repeat control | Practical trade-off |
|---|---|---|---|
| One video file repeating | Media Source | Loop | Simple setup; the same file returns to its beginning |
| Several videos, in a chosen order | VLC Video | Loop Playlist | Plays a sequence; VLC must be installed |
For a single-file stream, check the file from beginning to end before importing it. Look for a silent opening, an abrupt ending, unwanted blank frames, or a change in sound level near the point where it will repeat. For a playlist, write down the intended order and check that every file is present; the viewer will encounter the sequence you supply, not an order you have only planned in your head.
A playlist is useful when you need distinct recordings to rotate in a set order, but it has more items to manage. A single Media Source is easier to inspect, though it repeats the same content. If you are weighing other ways to arrange multiple files, this guide to setting up a YouTube stream with multiple video files can help you think through the workflow. For a channel built around one continuous music presentation, the Hindi bhajan playlist setup for Mac is another useful comparison of the broader task.
Add one file as a Media Source
In OBS, choose the scene that will carry the broadcast, then add a Media Source. Give it a clear name such as “Main bhajan video” so it is easy to identify later if the scene gains a logo, background, or additional source. Select the local video file and confirm it appears in the preview. OBS documents Media Source as a way to play media files in a scene; see the OBS Media Sources guide for the source’s available controls and supported media types.
A local file keeps the playback input straightforward: OBS reads the video you selected rather than asking a viewer to follow a link. That does not tell you whether the file is suitable for a long broadcast, so check it in a normal player first. Confirm the picture and sound are present throughout, and note the file’s ending. If its final frame cuts off a sung line, for example, the loop will repeat that cut every time the file ends.
Keep the source name and the filename recognisable. If you later replace a bhajan recording, a descriptive name helps you spot whether the active source is still pointing at the intended file. This is especially useful when the scene is not being watched continuously and the source list is your main way to check what OBS has loaded.
After adding the source, place it in the scene’s layer order where it belongs. If it is meant to be the full-screen picture, ensure that other sources do not cover it. If you plan to add a small title or channel mark, put those elements above the video and inspect them against both light and dark parts of the footage.
Turn on Media Source Loop
Open the Media Source properties and enable Loop. OBS’s definition is simple: playback starts again when the file reaches its end. It is the setting that makes one selected bhajan video repeat, not a general instruction to keep every source active forever.
Test the actual end-to-start transition. If you can, seek close to the end in a private or otherwise controlled test, then watch for the source to return to its opening. Listen as well as look: a click, sudden level change, or conspicuous gap may come from the edit in the file rather than from OBS. A seamless loop depends partly on how the audio and video were prepared.
For music over a mostly still image, this check is easy to overlook because the picture may appear unchanged for long periods. It is still worth checking the boundary. If the video contains a devotional image that remains on screen while the audio continues, viewers may not notice a visual transition, but they can hear a poorly joined ending immediately.
Do not use Restart playback when source becomes active as a substitute for Loop. That control concerns what happens when the source becomes visible or active in the scene; it does not itself repeat a file that has finished. A source hidden and later shown may begin again depending on that setting, which is a different behaviour from looping at the end of playback.
Understand the separate restart control
The restart option can be useful when a scene change should cause a media source to start from its beginning. It is a scene-activation behaviour, not an end-of-file repeat setting. If you have one bhajan file, leave the responsibilities clear: Loop handles the repeat; Restart playback when source becomes active handles a restart when the source becomes active.
Consider a scene that has a starting slate before the bhajan. When you switch into the scene, a restart setting may be appropriate if you want the video to begin at its opening each time that scene becomes active. But if the scene remains active and playback reaches the end, only the loop behaviour is relevant to making the file play again.
For a simple always-on layout that never switches away from the bhajan scene, the restart control may not change the result you see during ordinary playback. Avoid toggling several controls at once just because they sound similar. Change one setting, observe what it does in a test, and leave a note if another person may later operate the scene.
This separation is useful when diagnosing a stream that appears to start over unexpectedly. First ask whether the source became active again, or whether the file reached its natural end. Those are different events, and changing the wrong control can conceal rather than fix the behaviour you want to understand.
Use VLC Video for a playlist
When your programme contains several video files in a particular order, add a VLC Video source instead of adding one Media Source and expecting its Loop option to manage a queue. Configure the playlist in the source and enable Loop Playlist so the sequence returns to the start after its final item. OBS requires VLC to be installed for the VLC Video source to work; install and test that dependency before relying on it for a long run.
Check the list itself as carefully as you check the repeat setting. Verify the first item, last item, and any transitions where the audio changes between recordings. A playlist can faithfully repeat an awkward order, a missing section, or a file with a different sound level. It is worth listening to the hand-off between each pair of items, particularly if the videos were produced separately.
A playlist offers more variety than one repeated file, but each added recording is another file path and another opportunity for a mismatch. Keep the files in a stable location, use names that make their intended order obvious, and avoid moving or renaming them after you have configured the source without checking it again. A successful first play does not prove every later item will load as expected.
If you need finer control over scenes, sources, or routing beyond a straightforward playlist, OBS’s overview of scenes and sources explains how those pieces fit together. For a music channel, this guide to managing a YouTube stream key safely in OBS is relevant to the separate connection setup; a stream key does not control which media source repeats.
Check the scene canvas and audio mix
Once playback is configured, check how it sits on the canvas. A video with a different shape from the OBS canvas may leave empty space, be cropped, or need resizing. Decide which outcome is intended. If the recording includes text or artwork near an edge, avoid cropping it off merely to fill the frame. OBS scenes combine sources into the layout sent to the stream, so inspect the full composition rather than only the media source in isolation.
A practical canvas check is to compare the preview with the video as it appears in its original player. Look at the outer edges, any embedded Hindi text, and the placement of important devotional artwork. If you add a title or logo, ensure it is legible without covering a face, instrument, or caption that matters to viewers. The scene should look deliberate at the resolution you plan to send, not merely fit inside the OBS window.
Then check audio in the OBS mixer and in the stream itself. The Media Source may contribute its own audio, while desktop audio capture can also pick up the same playback on some setups. If both paths are active, the result can sound doubled or phasey. Do not assume that audio routing behaves the same on every computer or device: inspect the sources and listen to the output on the system you will use.
Set a repeatable listening check. Listen for a clear vocal and instruments, watch the mixer for activity while the video plays, and confirm that the stream preview also carries sound. If you change the audio source or mute desktop capture to avoid duplication, test again; muting the wrong path can leave the stream silent even though the local player still sounds normal.
A useful diagnostic is to compare what you hear locally with what reaches YouTube’s preview. If local playback is audible but the preview is not, the issue may be in the OBS mix or output path. If both are quiet, review the file and its source volume. The exact routing depends on the machine, operating system, and selected devices, so treat this as a system-specific check rather than a universal device recipe.
Choose encoder settings and test the signal
Playback settings determine what OBS plays; output settings determine what it sends. A reasonable starting point for a mostly static devotional video is 1920×1080 at 30 frames per second, provided your computer and upload connection can sustain it. Static artwork often has little motion, so 30 fps is a sensible first test rather than a requirement. If your design contains scrolling text or moving footage, judge the result in the preview.
For H.264 at 1080p30, YouTube lists a recommended video bitrate of 10 Mbps and a minimum of 5 Mbps in its live encoder settings guidance. The same guidance lists 6 Mbps recommended and 2 Mbps minimum for H.264 720p30, 8 Mbps and 3 Mbps for 720p60, and 17 Mbps and 6 Mbps for 1080p60. These are YouTube’s figures, not a promise that a particular connection can hold the stream. Do not apply H.264 figures to a different codec without checking the table for that codec.
Use CBR and a two-second keyframe interval as the platform-aligned starting point, and select the bitrate for the actual resolution, frame rate, and codec. YouTube recommends RTMPS where available. Its guidance also specifies audio encoding choices and a stereo audio bitrate; check the current table rather than treating a remembered value as universal. A setup that looks correct on paper still depends on upstream capacity and the load on the computer.
The trade-off between 720p and 1080p is not only sharpness. Higher output detail needs more bitrate headroom and may increase encoding work. Likewise, moving to 60 fps raises the demands of the encode; OBS cautions that higher frame rates can tax system resources. For a mostly still bhajan image, first see whether 1080p30 gives the artwork the clarity you need. If the machine or connection struggles, reduce the output mode and test again instead of assuming a higher setting is always better.
Test a representative stretch that includes normal audio, any motion or captions, and the transition back to the beginning. Watch YouTube’s Live Control Room preview and stream-health messages for warnings. YouTube recommends testing before going live and monitoring stream health; a local OBS preview alone cannot show whether the upload path is stable. For troubleshooting network symptoms, this guide to OBS dropped frames on a shared connection covers a different but relevant part of the signal path.
OBS can attempt to reconnect after a connection interruption, but reconnect behaviour is not a guarantee of uninterrupted viewing. Keep an eye on dropped-frame indicators and YouTube status messages, especially during a test that resembles the planned broadcast. If the stream is meant to run while you sleep or leave the premises, consider who can check the channel and what the fallback plan is if the local computer, power, or connection stops behaving normally.
Decide whether OBS is the right operating path
OBS gives you direct control over the scene, source, and encoder, and it is useful when you want to adjust the composition or combine live elements with a bhajan video. The trade-off for an always-on stream is that the computer, power, network, and OBS session remain part of the operating chain. A strong configuration does not remove the need to test that chain or to consider what happens if the machine needs attention overnight.
If the specific problem is keeping a local computer on just to repeat one uploaded file, StreamNeo removes that particular burden: you upload the video and provide your YouTube stream key, then the broadcast can run with your computer switched off. It is YouTube-only, so it is not the route for a simultaneous stream to another platform, and it does not change how you should prepare or check the bhajan file itself.
Whether you use OBS or a different operating path, keep the source plan, audio check, and stream preview test. If this is a new channel or a new type of broadcast, read the current YouTube Live Control Room instructions before relying on a long session; this guide does not establish channel eligibility or archive behaviour.
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 one repeating bhajan?
Use Media Source for a single file and enable Loop. VLC Video is the playlist route when you want multiple files in order, and it depends on VLC being installed.
Does “Restart playback when source becomes active” repeat the file?
No. It controls what happens when the source becomes active in the scene; it does not make a completed file repeat. Enable Loop on the Media Source to repeat one file.
Why is the stream preview silent when OBS plays the bhajan?
The local preview or media playback may be audible through a different audio path from the stream mix. Check the mixer, listen to YouTube’s preview, and look for duplicate or muted sources on the system you are using.
What bitrate should I try for 1080p30?
For H.264, YouTube lists 10 Mbps recommended and 5 Mbps minimum for 1080p30 in its encoder guidance. Treat that as platform guidance, then test whether your computer and upload connection can sustain the chosen mode.