For a mostly static Punjabi Gurbani playlist, start OBS at 720p and 30 frames per second, using H.264, CBR, a two-second keyframe interval and RTMPS. YouTube’s H.264 recommendation for 720p30 is 8 Mbps, but that figure is a platform setting to test against your connection, not evidence that your local upload or computer can sustain it.
Move to 1080p30 only if the artwork or text benefits from the extra detail and a realistic test shows that your connection and encoder can carry the higher bitrate steadily. Neither resolution makes a recording permissible to rebroadcast: check rights for the specific Gurbani composition and recording before you go live.
Assess the playlist visual and computer
Begin with what viewers will actually see. If the stream uses a still image, album artwork or a slowly changing visual, 30 fps is a sensible starting choice. It avoids spending bandwidth and processing effort on frames that add little to a mostly static picture. If the visual includes movement that genuinely benefits from smoother motion, assess that separately; do not choose 60 fps merely because OBS offers it.
Look closely at the parts of the image that matter. A 720p canvas may be sufficient for a devotional image and a short title, but small Gurmukhi text, fine ornament or detailed artwork can be harder to read when reduced. Preview the image at the size viewers are likely to use, including on a phone. If you need to show lyrics or a schedule, make the lettering large enough to remain legible rather than relying on 1080p to rescue tiny text.
The playlist itself matters as much as the canvas. Check that its videos play continuously, that the audio level does not jump between tracks, and that the visual does not unexpectedly switch to a blank or error screen. For preparation advice on a video-based playlist, see how to prepare long MP4 files for reliable playback in OBS. A reliable source file does not guarantee reliable streaming, but it removes one avoidable cause of trouble.
OBS has to encode the picture while the computer plays the playlist and handles audio. A high-resolution output can add work even when the image barely changes. Watch OBS’s status indicators during a test and check whether the computer stays responsive. If frames are missed or rendering and encoding lag appears, lower the output resolution or reduce the workload before adding other moving elements.
For an audio-led channel, the purpose is to make the devotional programme easy to hear and identify. Avoid animated overlays, frequent scene changes and needless visual effects unless they serve viewers. A simple layout is easier to inspect, lighter to encode and less likely to conceal a problem with the playlist.
Start with 720p at 30 fps
In OBS, set the output to 1280 by 720 at 30 fps as your first profile. Use the same output resolution consistently for a test and the live schedule. YouTube recommends 8 Mbps for H.264 at 720p30. Treat that as the initial encoder target for testing, not as a guarantee of quality or proof of capacity.
This is a conservative choice for a largely still image, not a universal best preset. It can be the right trade-off when the image is simple, the upload connection is uncertain or the streaming computer is modest. If the stream looks clean and the text is legible at that size, a higher resolution may bring little practical benefit to viewers.
In OBS, the base (canvas) resolution and output (scaled) resolution are separate controls. The canvas describes the layout you arrange; the output is the encoded picture sent to YouTube. If your sources are laid out at a larger canvas size, OBS can scale the output to 1280 by 720. Check the preview for soft lettering, cropped artwork or black edges after scaling.
Set the frame rate to 30 in the video settings. For a static image or slow visual, higher frame rates do not make devotional audio clearer. YouTube supports higher frame rates, but each choice should have a reason in the picture and should be tested against both encoding load and upload capacity.
If your channel already uses OBS for continuous playlists, the related OBS settings guide for 24/7 YouTube playlist streaming in India can help you compare the general setup with this Gurbani-specific starting profile. Keep the distinction in mind: the target settings may be similar, while rights checks for your playlist remain specific to its recordings.
Set H.264, CBR, keyframe interval and RTMPS
Choose H.264 video encoding in OBS where it is available and supported by your computer. Set rate control to CBR, or constant bitrate, so the encoder aims to send a steady video bitrate rather than varying it with picture complexity. YouTube’s current encoder guidance also lists other codecs, but figures for H.264 should not be copied automatically to H.265 or AV1. Use the table for the codec you have actually selected.
Set the keyframe interval to two seconds. YouTube recommends two seconds and says not to exceed four seconds. A keyframe is a full reference picture from which later compressed frames can be reconstructed; a consistent interval is part of making the encoder output suitable for the platform. In OBS, the control may be expressed in seconds or frames depending on the encoder and interface. Confirm that your chosen entry represents two seconds at the selected frame rate.
For the service, select YouTube or YouTube RTMPS if OBS provides that option. RTMPS encrypts the connection between the encoder and YouTube’s ingestion service. If you must enter a server URL manually, use the URL shown for your stream in YouTube Studio rather than a copied address from an old setup. YouTube’s encoder settings and bitrates guidance describes its supported protocols and encoder recommendations.
The stream key is a credential that directs OBS to your channel’s live stream. Copy it from the stream setup in YouTube Studio, paste it into OBS and keep it private. Do not put it in a public screenshot, tutorial or shared document. If you think it has been exposed, reset it in Studio and update OBS with the replacement. YouTube’s live streaming setup instructions explain how to create an encoder stream and connect it.
Compare 720p30 and 1080p30 bitrate recommendations
YouTube’s recommendations help you configure an encoder, but they do not tell you what your internet connection can sustain. For H.264, the two relevant 30 fps starting points are:
| Output | YouTube H.264 video bitrate recommendation | When it may suit the playlist |
|---|---|---|
| 720p30 | 8 Mbps | Static or slow visual, or a setup where upload and encoding capacity call for a cautious start |
| 1080p30 | 14 Mbps | Artwork or text needs more detail and the connection and encoder have passed a realistic test |
The video bitrate is not the entire stream. Audio also uses bandwidth, and network conditions fluctuate. YouTube advises allowing 20% room above the full stream bitrate. Use that headroom when judging whether your measured upload has enough room; do not mistake the video figure alone for the total needed capacity.
At 720p30, the artwork may already be clear enough, while 1080p30 can make fine detail easier to read if the source image has that detail. The cost is a higher recommended video bitrate and potentially more encoding work. More pixels do not improve a low-resolution source image, and they do not make a poor recording sound better. Compare the actual preview on a phone or television before changing profiles.
If your stream carries text that must be read, inspect the output at both sizes and consider the practical context: a small phone screen, a viewer with a slower connection, and the artwork’s original resolution. If there is no visible improvement that matters to viewers, keep the lower setting. If 1080p is useful, only adopt it after sustained testing at its intended bitrate.
A playlist built from multiple files may need different preparation from a single looping video. For that workflow, making a 24/7 Indian music YouTube stream from MP4 files covers file-based planning. The resolution and bitrate decision still belongs to the output you test, not to the source folder or the genre.
Allow upload headroom and test under real conditions
A speed test taken beside the router at a quiet time may not represent the conditions during a night-long broadcast. Test from the same computer, using the connection and location you intend to use. Include ordinary household or venue activity: other people may be watching video, uploading files or using the same Wi-Fi. The bandwidth available to OBS can be lower than the headline speed on an internet plan.
YouTube recommends 20% room above the full stream bitrate and a reliable connection. Apply that guidance to the whole stream, not just the video encoding field. If the result is marginal, varies considerably between tests or falls short when other users are active, do not push the 1080p setting. Try the lower resolution and bitrate, or resolve the connection issue before relying on the stream.
A wired Ethernet connection can reduce dependence on a busy or weak Wi-Fi link, but it cannot increase the upstream capacity supplied by your internet service. If using Wi-Fi is unavoidable, test in the place where the computer will remain and at the time of day when the stream will run. Avoid making a change based on one unusually favourable speed test.
Run a private or unlisted test with the actual playlist and intended output. Leave it running long enough to include the conditions you expect overnight: the same files, overlays, audio routing, computer load and network use. Watch OBS for dropped frames, encoding lag and disconnects. A test with a static desktop and no audio is not a meaningful substitute for the real programme.
When the upload is unstable, change one thing at a time. Lower the output resolution or bitrate, test again, and note whether the stream health improves. If the computer is struggling, reduce encoder load or visual complexity as well. Keeping a short record of the profile and test result makes it easier to return to a known configuration rather than changing several settings in a hurry before going live.
For a continuous channel, consider who will notice a failure and how it will be recovered. OBS runs on your computer, so a power cut, operating-system restart or local internet outage can stop the broadcast. If keeping a computer on and checking for dropped streams is the specific burden, StreamNeo removes that particular always-on-computer task by running an uploaded video as a YouTube live stream after you provide the stream key; it does not change the need to test the content, connection assumptions or rights.
Connect OBS and check YouTube stream health
In YouTube Studio, open Go Live and create or schedule an encoder stream. In OBS, select the YouTube service or enter the server details shown in Studio, then add the stream key privately. Set the video output and audio settings before connecting. Confirm that the selected scene contains the intended playlist visual and that the source playing the Gurbani audio is actually captured.
Start OBS streaming and inspect the Live Control Room preview before sharing the link or depending on the broadcast. YouTube’s stream setup guidance covers encoder setup, while its stream health troubleshooting information is a useful reference when the incoming signal is not behaving as expected. Read the current instructions in Studio, since its available stream controls and indicators are the ones for your account and event.
Check that the preview shows the right picture and that audio is present, clear and in sync. Look at stream health for warnings and observe whether the bitrate remains steady or fluctuates. If YouTube reports an unstable signal, do not assume the public player will be fine simply because the local OBS preview looks correct. Diagnose the encoder, network path and output settings before treating the test as passed.
A successful connection at the start is not a full-night test. Continue to monitor the broadcast, especially during the first run with a new profile. If you cannot watch continuously, arrange a practical way for someone to check the event or use a workflow with monitoring and recovery. A playlist loop can keep the media moving, but it cannot by itself restart an encoder that has stopped sending.
Review audio and broadcast rights
For stereo audio, YouTube’s guidance lists 44.1 kHz and 128 kbps. Set OBS and the playback chain consistently, and confirm that the correct desktop or application audio source is captured. Watch the audio meters while the playlist plays; listen to a test stream rather than relying only on the meters. Check for clipping, silence, unexpected desktop sounds and abrupt changes in loudness between tracks.
Do not assume that Gurbani text, devotional purpose or a purchased file grants the right to rebroadcast a particular commercial recording. Rights can differ for the composition and for the sound recording, and the permission you need may depend on the territory, live use and whether YouTube archives the stream. Verify the terms for each recording with the relevant rights holder or authorised distributor before scheduling it.
YouTube’s live-stream copyright guidance says live streams are scanned for third-party content. A detected match can lead to a placeholder, warning, interruption or termination if the content remains. A recording owner may also need to add your channel to a Content ID allowlist for an authorised stream not to be interrupted by a match. An archived live stream can receive a Content ID claim after the broadcast.
Keep written permission and the licence terms for the actual recording. Ask whether the authorisation covers live streaming and archived replay, and whether allowlisting is needed. Attribution, a “free” label or a purchase receipt does not by itself establish those permissions. YouTube’s terms for live streaming put responsibility on the provider to have the necessary rights, including relevant music rights. Check the current official pages and the actual licence; there is no basis to infer the status of an unspecified playlist.
Before relying on the stream for a programme or daily schedule, test the audio and visual in the Live Control Room and make sure your rights records match the exact files in the playlist. If you replace a track, revisit the rights check rather than assuming the new recording is covered because it contains the same devotional text.
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
Is 8 Mbps enough for a 720p30 Gurbani stream?
It is YouTube’s recommended H.264 video bitrate for 720p30, not a measurement of your connection or a promise that the stream will remain stable. Include audio and YouTube’s recommended 20% upload headroom when assessing capacity, then test under the conditions in which you will actually broadcast.
Should I use 1080p for devotional artwork?
Use it when the source artwork or text becomes meaningfully clearer at 1080p and your computer and connection pass a realistic test at the higher setting. If the visual is mostly static and 720p remains legible, the lower output may be the more practical choice.
Does OBS need to stay open for a playlist stream?
For an OBS stream, the computer needs to keep playing and sending the broadcast; shutting it down stops that local workflow. Plan for power, connection and recovery, or choose a workflow that does not depend on your own computer remaining on.
Can I stream any Gurbani recording if I credit the singer?
No. Credit does not establish permission for the composition, recording, live use or archived replay. Check the rights for the specific recording and ask whether the channel must be allowlisted to avoid a Content ID interruption.