When OBS audio is missing, doubled, distorted or reaching viewers on only one side, trace it from the player or input device through operating-system routing and OBS, then check YouTube Live. A moving OBS meter confirms that some audio has reached OBS; it does not prove that the stream output is correct.
The available capture sources depend on your operating system and OBS version, so first note both. Then follow the signal in order rather than changing several settings at once: a controlled check at each point tells you where to look next.
Identify the symptom and setup
Write down what you hear and where. “No sound” could mean the music player is silent, the desktop is audible but OBS is not, OBS’s mixer moves but a test recording is silent, or the recording sounds right while YouTube playback does not. Those are different breaks in the chain. Also note whether the problem affects all audio or one application, whether it is continuous, and whether it began after a device or scene change.
Record your operating system and OBS version, plus the route you intend to use. Are you capturing the whole computer output, one application, a microphone or mixer input, or some combination? A radio station playing a local playlist may need a different route from a station taking audio from a hardware mixer. Do not assume that instructions for one operating system’s capture source apply to another.
If only one application is absent, check that application’s output and capture compatibility before changing the rest of OBS. If all sources are absent, begin with the selected device and operating-system route. If the signal is present but wrong, such as doubled or one-sided, focus first on duplicate paths or channel assignment rather than replacing the source.
A simple signal map helps keep the diagnosis clear:
| Point in the chain | What to check | What the result tells you |
|---|---|---|
| Player or physical input | Playback, output selection, input gain | Whether a usable signal begins at the source |
| Operating system or application | Output device and routing | Where the source is being sent |
| OBS source and mixer | Active source, selected device, meter | Whether OBS receives the intended signal |
| OBS output and recording | Mute, fader, channels, track, playback | Whether the signal survives the OBS mix and encode path |
| YouTube Live | Stream preview, playback and health messages | Whether the destination receives and presents the intended audio |
Change one thing at a time and note what changed. If you alter a player output, OBS source, global device and fader together, even a successful result will not show you which change mattered. For a continuous channel, make the checks with the actual playlist or a representative segment, not only with a brief sound from a different application.
Confirm audio at its source
Start the music or other representative content. Listen at the device where it is meant to play, and check the player’s own volume and output selection. A player can be sending to headphones while OBS is configured to capture speakers, or it may be muted independently of the system. Confirm the selected output by name if the application offers a choice.
Next check the operating system’s output device and, where available, its per-application volume or mixer. Confirm that the player is routed to the endpoint you think it is. The desktop sounding correct is useful evidence that playback exists, but it does not establish that OBS is capturing that endpoint. Keep the distinction between “I can hear it” and “OBS receives it” in mind throughout the process.
If the source is a physical mixer, interface or other input device, follow its signal path too. Check the relevant input gain, channel mute, routing and master or output control. A device may show activity on an input channel while its main output is muted or routed somewhere other than the computer input OBS is using. Avoid raising gain aggressively to compensate for silence: first establish that the signal is reaching the intended output.
Use a short, familiar piece of audio at a moderate level. It makes interruptions, distortion or left-right differences easier to recognise than a quiet passage or a track with long gaps. If the station runs music from files, the guide to making a 24/7 Indian music stream from MP4 files covers the broader playback setup; here the important question is whether that playback produces the signal you intend OBS to capture.
If there is no audible output at the source, pause the OBS diagnosis. Fix the player, device or physical input first, then repeat the check. An OBS filter cannot restore audio that never reaches the selected output.
Check operating-system and application routing
Once the source plays, establish where it is routed. A system-wide desktop capture generally follows an output endpoint, whereas a source aimed at one application can be more selective. The choice depends on whether you want every computer sound or only the radio player. Selective capture can keep notifications out of a station, but a separate application route will not help if that application is sending its sound to another device.
Capture-source availability varies by platform and OBS release. OBS documents Audio Input/Output Capture on Windows and macOS, and ALSA/PulseAudio capture sources for Linux. Check the current OBS audio sources documentation for the source types that apply to your system rather than looking for a menu described for another platform. A source name in an older guide may also differ from what your installed version offers.
On Windows, OBS documents Application Audio Capture for Windows 10 version 2004 or later and Windows 11. It can be useful when you need one application without all desktop sounds, but do not assume every application is compatible. OBS describes a virtual-cable route for some incompatible applications: send that application to the cable, then capture the cable output in OBS as an input. Treat this as a targeted workaround, not a required step for every Windows station. The current OBS application audio capture guide gives the relevant conditions and routing details.
On Linux, use the ALSA or PulseAudio capture options documented for OBS and account for the audio system in use. Device selection and routing can differ between distributions and audio servers; if a source remains silent, gather the distribution, audio-server and OBS-version details before following platform-specific advice. On macOS, OBS lists Audio Input/Output Capture, but Windows instructions for capturing an individual application should not be assumed to apply there.
For a station already using OBS to play a scheduled list, the Windows startup and playlist guide may help with the broader arrangement. It is still important to test the specific audio route after startup: a player opening automatically does not prove it is using the output OBS expects.
Inspect OBS sources and mixer
In the scene that is actually on air, confirm that the intended audio source exists and is enabled. Open its properties and inspect the selected device. “Default” can point to a different endpoint after a headset, interface or other device is connected, so select the intended device explicitly when that choice is available. Check the source in the active scene, not only in a scene you use for setup.
Play the representative content and watch the OBS mixer. If the relevant meter does not move, OBS is not showing a signal on that source. Return upstream: source activation, properties, device selection, and operating-system or application routing are the useful checks. Repeatedly changing the OBS fader will not help a meter that stays still.
If the meter moves, OBS is receiving something. Do not keep changing the capture device without evidence. Check whether the source is muted, whether its fader is pulled down, and whether the meter responds to the intended player rather than another computer sound. Then continue to monitoring, channel and output checks. A moving meter narrows the problem; it does not certify the signal that YouTube viewers receive.
You can compare OBS’s received audio with the original by using Audio Monitoring and the configured monitoring device. OBS documents monitoring controls in Advanced Audio Properties and the audio mixer guide. Listen for whether the sound is absent, delayed, distorted or doubled. Choose a monitoring route you can identify, and do not mistake the monitor feed for the stream itself: monitoring is another point in the chain, not a substitute for a recording or destination test.
Check levels, duplication and channel balance
Echo or doubled music often points to two capture paths carrying the same audio. For example, the endpoint may be enabled in global OBS audio settings and also added as a scene-level capture source. OBS warns that capturing the same device in both places can cause echo. Choose one route for that endpoint and disable the duplicate; then listen again. For application capture on Windows, OBS also recommends disabling global Desktop Audio when capturing applications separately, so the same playback is not included twice.
Check channel balance while the source plays. OBS shows left and right meter bars separately. If only one side moves, a stereo stream may deliver sound on one side only. Inspect the source’s channel layout and the routing upstream; listen to both sides of headphones or another known stereo playback device. Mono audio is normally heard in both channels, and OBS offers Downmix to Mono in Advanced Audio where appropriate. Use it when the source is meant to be mono, not as a blind fix for an incorrectly routed stereo signal.
For quiet or distorted sound, establish levels in order: physical input or device controls, operating-system and application levels, then the OBS fader. Clipping can sound harsh or broken; turning down only the final fader may reduce loudness without correcting distortion introduced earlier. OBS’s guidance places background music in the green meter area, but meter colour is not a calibrated loudness target. Listen to the audio as well as watching the meter.
Filters are for a defined problem after the signal route is correct. OBS describes Gain for boosting a quiet source, a Compressor for controlling level above a threshold or lowering one source when another is active, an Expander for reducing background sound, and Invert Polarity for phase-related cancellation. Each changes the signal in a different way. A filter cannot make a disabled source active, choose the right device or repair a missing route, so diagnose those points first.
For a steady radio programme, avoid stacking processing just because a source sounds low. Raise the appropriate upstream level if it is safely available; then make a small, deliberate OBS adjustment and listen back. If the sound pumps, becomes harsh or loses detail, undo the last processing change and compare with the unprocessed signal. The aim is intelligible, consistent playback, not a meter that looks busy.
Verify the signal in YouTube Live
Make a short recording from OBS using the same scene, player and audio route planned for the station. Listen to the recording from start to finish, including a passage with music and any transitions that matter. This separates what you hear through OBS monitoring from what OBS actually records and sends through its output path. If the desktop sounds right but the recording is silent, return to OBS output, track and source checks rather than assuming YouTube is the cause.
Then make a private or otherwise suitable test in YouTube Live and listen to the destination playback. Include both audio and the motion or programme content intended for the live stream. YouTube’s official live encoder settings guidance recommends testing before starting a live stream and checking stream health and messages during the event. A preview or successful connection alone does not establish that the audio sounds right to a viewer.
If OBS’s mixer moves and the recording plays correctly, but YouTube is silent, inspect the OBS output and track selection and then the destination’s audio settings. For a normal stereo radio stream, verify that the output is stereo rather than an unintended surround layout. YouTube’s current RTMP/RTMPS guidance lists AAC or MP3 for audio and recommends 44.1 kHz and 128 kbps for stereo; its figures for 5.1 are different. These are YouTube’s published recommendations, not a guarantee that every source or route is correct. Check the live YouTube encoder guidance again when configuring, as platform recommendations may change.
Keep the test representative. If your station will run overnight, use the intended playlist, scene and output device, then confirm that audio continues through a transition or other point where playback might change. A short recording is useful for tracing a fault, but it does not show what happens after a player switches files or a device changes. For the separate question of keeping an OBS-based stream observable, see the guide to monitoring an FFmpeg YouTube stream on a VPS; regardless of workflow, check the actual destination and its messages.
When the recurring fault is that the computer must stay on and keep the player routed correctly, StreamNeo removes that particular operating burden: you upload the video once and the YouTube broadcast can continue with your computer switched off. It does not change the need to prepare the file, use audio you have the right to broadcast, and verify the resulting channel and playback.
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
Why is OBS audio not working when I can hear the music on my computer?
Desktop playback confirms that the player produces sound, but OBS may be listening to a different device or source. Check the player’s output, system routing and the selected OBS device, then watch the relevant mixer meter while it plays.
Why does my YouTube radio stream have an echo?
Look for the same endpoint captured in more than one place, such as both global Desktop Audio and a scene-level source. Disable one duplicate route and test again; if the echo remains, compare OBS monitoring with a recording to locate where it enters.
Why does the OBS meter move but the stream is silent?
A moving meter means OBS receives a signal, not that the correct source reaches the encoded output. Check mute and fader state, channel and track selection, then listen to a recording and a representative YouTube Live test.
Can I use the same OBS audio instructions on Windows, macOS and Linux?
No. OBS’s available capture sources and application-routing options depend on the operating system and OBS version. Check the OBS documentation for your platform and version before following steps that name a particular source.