STREAMING GUIDE / OBS STUDIO

OBS desktop audio not working? Follow the signal

Find the first point where game or computer sound disappears, before changing drivers or rebuilding your scenes.

START HERE

First check whether the intended OBS meter moves. A flat meter points toward capture or device selection. A moving meter with a silent recording points toward output mute, track routing, or the player. Test one sound and one capture route at a time.

Start with a sound you can identify

Stop streaming and save a short local test instead. Play a familiar, non-private clip in one application, using your normal headphones, or generate a steady test signal in the browser tone generator. Close your stream dashboard player so its delayed sound cannot confuse the test. Write down the output device that actually plays the clip; a USB headset, HDMI monitor, and Bluetooth headset are different capture targets even when all are connected.

If the clip is silent outside OBS too, use the single-app audio checklist first. OBS cannot capture a useful signal from an app that is muted or routed somewhere unexpected. Avoid changing the Windows default device repeatedly while investigating: that changes the experiment.

A flat meter: check the capture target

  1. Find the intended source in the Audio Mixer and confirm it is active in the scene you are testing.
  2. For a Windows device capture, inspect its Properties or the global device under Settings > Audio. Select the named playback device that passed your listening test rather than relying on Default.
  3. Replay the same clip and watch that source. If another meter moves instead, identify what it captures before adding anything new.
  4. If the application restarted or changed its window, reselect it in the application-capture source and repeat.

The OBS audio-source documentation distinguishes scene sources from global devices. A source intended for one scene is not automatically the audio source for every other scene.

Choose one capture method for the test

On supported Windows versions, Application Audio Capture can isolate an application. OBS 30.1 and later also offer audio capture with compatible Game or Window Capture sources. Start with one of these routes, or one whole-device capture, rather than stacking all three. Whole-device capture may include notifications and other apps.

If a particular game works through device capture but not application capture, the application method is the variable to investigate; reinstalling the headset driver is not the first conclusion. macOS uses a different path: OBS 30+ on macOS 13+ provides a macOS Audio Capture source. Follow the OBS Mac desktop audio guide and the official Mac documentation instead of looking for the Windows source name. Linux capture choices depend on its audio backend.

A moving meter: check where the sound goes

Make a 15-second recording with only this source intended for the mix. Check the source output-mute control, then open Edit > Advanced Audio Properties and inspect its track assignments. Compare those assignments with the recording tracks enabled under Settings > Output. The source must be sent to a track the recorder actually writes.

Open the resulting file and inspect the player’s audio-track menu. If sound appears on another track, capture worked: the problem is the expected mix or playback selection. Monitoring in headphones is a separate test and cannot prove that the file contains the audio. Use the recording-track guide when you intentionally keep isolated tracks.

Use the observation to choose the next change

ObservationNext check
Only one scene is silentCompare its active sources with the working scene; do not duplicate the device globally as a shortcut.
Only one game is silentCompare its output device and capture method with a known-working app.
All saved tracks are silent despite meter movementCheck output mute and track assignments with a fresh single-source recording.
Local recording works but the live feed is silentInspect the streaming audio-track selection and service preview separately.

Verify the fix survives your real workflow

Repeat the same clip after switching scenes, restarting the source app, and reconnecting the headset. Then restore the other sources one at a time and record a complete minute with game sound and speech. Listen to the saved file, not an open live player on the streaming computer. Keep a note of the device and capture method that worked so a later default-device change is recognizable.

Should I turn on monitoring to fix silence? Only if the missing sound is specifically your local monitoring feed. Enabling monitoring does not repair a missing capture source or a recording-track mismatch, and it can create a second captured path. If you use Streamlabs Desktop instead of OBS Studio, check the Streamlabs Desktop audio checklist.

Sources & version notes

Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.