First, identify the Windows application playing your bhajans and choose one route for its sound into OBS. On supported Windows versions, Application Audio Capture is usually the most selective path; then check the mixer and listen to a short recording rather than assuming that moving meters mean the stream sounds right.
The exact steps depend on your Windows version and player. A successful test confirms the audio path at that moment, not that a computer or continuous broadcast will keep running without interruption.
Identify the player and your Windows version
Before changing OBS, note which application is playing the bhajan file or playlist and which playback device it uses. It might be a desktop media player, a browser tab, or another application. The right capture route depends on both the application and the Windows version, so do not assume a route will work simply because it works on another PC.
Check your Windows version in Settings under System and About. OBS documents Application Audio Capture for Windows 10 version 2004 or later and Windows 11. If you have an older version, or the player does not behave properly with that source, use one of the device-based alternatives below instead.
It also helps to decide what OBS should hear. If the stream should contain only the bhajan player, capturing a single application can keep unrelated notifications and other desktop audio out of the mix. If you intentionally want everything playing through one output device, global Desktop Audio may be suitable, but that choice can include sounds you did not mean to broadcast.
For a wider view of the computer and workflow choices involved in a devotional channel, see streaming devotional songs from a spare PC. The audio steps here work independently of whether you ultimately use a local PC for the whole broadcast.
Choose one OBS audio capture method
Pick one intended route for the bhajan player. Capturing the same playback device globally and again as a source can make the signal echo or sound doubled. OBS warns about using an Audio Input or Output Capture source while the same device remains selected globally in Settings → Audio.
| Capture route | When it fits | What to check |
|---|---|---|
| Application Audio Capture | Supported Windows version and a compatible player; you want to isolate that application | Select the player and disable global Desktop Audio to prevent a duplicate path |
| Global Desktop Audio | You are content to capture the selected Windows playback device, including other sounds from it | Select the intended device in OBS Settings → Audio and check the mixer response |
| Scene-level Audio Output Capture | You want a specific playback device attached to a scene | Disable that same device as a global source to avoid duplicate capture |
| Virtual-cable workaround | OBS application capture does not handle the player audio | Route the player to the cable's playback endpoint and capture its recording endpoint in OBS |
For Application Audio Capture, OBS supports per-application capture on Windows 10 version 2004 or later and Windows 11. A device-based route may be more appropriate when you want the whole playback device, or when the application-capture source is not available or compatible. OBS documents a virtual-cable workaround for incompatible applications; treat it as troubleshooting, not as a required part of every setup.
If your channel is built around pre-recorded material, a separate issue can be keeping sound and picture together. The guide to fixing an out-of-sync pre-recorded YouTube stream addresses that problem; it does not replace checking the audio route in OBS.
Set Application Audio Capture
In your OBS scene, add an Application Audio Capture source. Give it a name that makes the purpose clear, such as “Bhajan player audio”, then open its properties and choose the application playing the bhajans. The exact labels and available choices can vary with the OBS version and Windows setup. Start or resume playback while you configure it so you can see whether the source responds.
If the player is not listed, first check that it is running and producing sound through the expected Windows output. Then reopen the source properties and check the available application choices. Do not select a different application just because it appears in the list: that could capture a browser notification or another sound instead of the intended bhajan.
For this route, set global Desktop Audio to Disabled in OBS Settings → Audio. This keeps the same player audio from coming in again through the desktop device. If you also need a microphone or another source, configure it separately and check its level and routing; disabling Desktop Audio does not mean you need to disable every other audio source.
Windows system and per-application volume sliders can affect what OBS receives. If the source is silent, too quiet or unexpectedly loud, check the player's own volume and its Windows volume setting before changing unrelated OBS controls. Make one adjustment at a time and watch the result in the mixer.
Application capture is selective, but it is not a universal compatibility guarantee. If the player cannot be captured reliably, move to a device-based option rather than adding a second capture source on top of the first one.
Disable duplicate Desktop Audio when applicable
This step matters whenever you use a source that captures the same sound as a global device. With Application Audio Capture, disable global Desktop Audio in Settings → Audio. With a scene-level Audio Output Capture source, disable the corresponding device globally instead. The names of devices shown in OBS depend on the playback devices available on your computer.
After changing the setting, play the bhajan and watch the Audio Mixer. You should see the intended source respond without a second source visibly responding to the same playback. If you hear a doubled or echoing signal in a test, inspect the mixer and source list for a second route before attempting to fix it with volume adjustments.
When the selected method is global Desktop Audio, do not add another source for the same playback device unless you have a distinct reason and understand the routing. Confirm that Settings → Audio names the playback device the player actually uses. If the player is routed to a different device, the global source can appear configured but receive no sound.
A clean route also makes later changes easier to reason about. If you add a new player, output device or microphone, check whether it has created another path into OBS. Keep only the sources your scene needs and verify each one separately.
Check the Audio Mixer meter
Play a section of the bhajan and look for movement on the meter for the source you selected. If the meter moves on the intended source, OBS is receiving some audio from it. That is useful evidence, but it is not proof that viewers will hear the right mix: a meter cannot tell you whether the audio is doubled, whether an unwanted sound is included, or whether the result is comfortable to listen to.
If the meter does not move, check the basics in order: confirm playback in the player, confirm its Windows output device and volume, and confirm that the OBS source is pointed at that application or device. OBS's Quick Start Guide notes that desktop audio and microphone are captured by default, and advises selecting devices manually in Settings → Audio if the mixer does not respond or captures the wrong device. See the OBS Quick Start Guide for its setup steps.
If the meter moves but seems too quiet or too loud, check the application and Windows volume controls first, then make a considered adjustment in OBS. Keep the bhajan intelligible and avoid raising levels simply to make the meter look fuller. The useful check is how the recording sounds, not a particular meter appearance.
The OBS Audio Mixer Guide explains the mixer and monitoring controls. Use it alongside the OBS audio sources guide when deciding whether a source should capture an application or a playback device. These are OBS Project documentation, not promises about how a particular application will behave on every Windows configuration.
Configure monitoring only if needed
Monitoring lets you hear an OBS source locally through the monitoring device configured in OBS. It is useful when you want to listen to the mix OBS is handling, but it is not the mechanism that sends audio to viewers. A source can reach the stream without local monitoring being enabled.
If you want to monitor, open Settings → Audio and choose the monitoring device you actually use, then open the source's audio properties and choose the appropriate monitoring mode. The available choices and labels can depend on OBS version and device configuration. Leave monitoring off if you do not need to hear the OBS mix locally.
Be deliberate about where monitored sound plays. Sending it through speakers close to a microphone can create feedback or an unwanted extra pickup, and routing the monitored output back into a captured device can create a duplicate path. Headphones make it easier to listen without adding room sound, but they are a convenience rather than a requirement.
Listen for the bhajan as it will be mixed in OBS, not only through the player's own playback. If monitoring is silent, check the configured monitoring device and the source's monitoring setting. Do not treat local monitoring as a substitute for a recording or test stream: the audience hears the encoded output, not your monitoring device.
Make and listen to a short test
Use the intended scene and player to make a short recording or test stream. Listen back from the resulting recording or stream and check that the bhajan is audible, not doubled, and not accompanied by Windows sounds you did not intend to include. Listen at an ordinary volume, and check the beginning as well as a section after playback has continued.
The OBS Project Quick Start Guide says it strongly encourages running a test for a few minutes before a first stream or recording, rather than jumping straight in. The important part is listening to the result: a moving meter alone cannot confirm that the whole path sounds as intended. If the recording is wrong, change one routing or level setting at a time and make another short check.
A test only describes the setup at the time you made it. It does not establish that the PC, power, network, player or broadcast will remain available through a night or for a continuous 24/7 stream. For an always-on channel, think separately about what happens if the player stops, Windows restarts, the network drops or OBS closes. The audio test is one part of preparation, not a continuity guarantee.
If keeping a local computer on and attending to it is the part you are trying to avoid, StreamNeo turns an uploaded video into a YouTube live stream that runs with your computer switched off, and monitors and restarts the broadcast if it drops. It is YouTube-only; this does not remove the need to prepare suitable source material or check the channel and current platform requirements. If you are comparing local and hosted approaches, low-cost VPS choices for a church YouTube stream in India explain a different route, while 24/7 YouTube streaming services with a free plan is useful when comparing operating models.
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 Application Audio Capture work on every Windows version?
No. OBS documents it for Windows 10 version 2004 or later and Windows 11, and an individual player may still be incompatible. If it is unavailable or does not capture the player properly, use a device-based route or OBS's documented virtual-cable workaround.
Should Desktop Audio stay enabled with Application Audio Capture?
Disable global Desktop Audio when you are capturing the player through Application Audio Capture. Otherwise the same sound may reach OBS twice. If you use a different route, check that the same device is not selected both globally and as a scene-level capture source.
Why does the OBS meter move when the stream sounds wrong?
A moving meter means OBS is receiving signal, not that the intended audio is clean or correctly routed. Listen to a short recording or test stream to check for silence, doubling, excessive or low volume, and unwanted desktop sounds.
Does a successful test mean the bhajan stream will run all night?
No. It confirms the audio chain at the time of the test. Continuous operation also depends on the computer, power, network, player and broadcast staying available, so do not treat an audio check as a guarantee of uninterrupted streaming.