How to Fix Your OBS Studio Audio Setup After the Update

You launch OBS Studio, prepare your overlays, turn on your camera, and run a quick mic check, only to realize the audio mixer is completely dead. Or worse, your stream can hear your game, but you can’t hear it in your headphones.

This scenario has become incredibly common following recent updates to OBS Studio. The development team completely overhauled the audio mixer engine to improve long-term performance and add modern monitoring features. However, this rewrite broke legacy workflows, removed long-standing settings, and caused Windows and macOS to lose track of OBS audio permissions.

If your audio setup was ruined by the latest changes, you do not need to reinstall your operating system or roll back to a buggy, older version of OBS. Here is a comprehensive guide to understanding what broke, why it happened, and how to get your audio routing working flawlessly again.

Why the Audio Update Broke Your Settings

Before diving into the fixes, it helps to understand what actually changed under the hood. OBS Studio replaced its legacy audio subsystem with a modernized mixer engine. This change was designed to support features like pinned sources, per-channel monitoring controls, and lower latency processing.

Unfortunately, this rewrite meant that any custom configurations relying on the older framework were invalidated. The most significant changes include:

• The Removal of “Output Only” Monitoring: In the Advanced Audio Properties panel, you used to have three choices for monitoring: Monitor Off, Monitor Only (mute output), and Monitor and Output. The Monitor Only (mute output) setting was frequently used to route audio to specific tracks without sending it directly to the stream’s primary mix. That specific toggle is gone, leaving many users with duplicated audio or complete silence.
• The Reset to “Default” Devices: During the update process, OBS often fails to migrate hardware IDs for microphones, audio interfaces, and headphones. It falls back to the system “Default,” which breaks your mix the moment your computer updates a driver or changes your primary playback device.
• Audio Integrity Blocks: Modern operating systems, particularly Windows 11, treat major software updates as “new” installations. This can trigger security flags, blocking OBS from accessing your microphone or system sound because the OS no longer recognizes the app as trusted.

---

Step 1: Force Specific Audio Devices (Stop Using “Default”)

The single most common reason audio stops working after an update is that OBS resets its global audio devices to “Default.”

When OBS is set to “Default,” it relies entirely on your operating system to tell it which microphone or headphones are active. If you plug in a controller, turn on a wireless headset, or update your GPU drivers, your OS might temporarily switch its default output. OBS follows suit, completely scrambling your audio path.

How to Bind Your Actual Hardware

1. Open OBS Studio and click on Settings in the bottom-right corner.
2. Navigate to the Audio tab on the left menu.
3. Locate the Global Audio Devices section.
4. Go through each dropdown menu (Desktop Audio, Mic/Auxiliary Audio) and change them from Default to the exact name of your hardware. For example, choose Shure MV7 or Focusrite Scarlett Solo instead of Default Mic. Select your specific headphones or audio interface for the output.
5. Click Apply and then OK.

By manually selecting your hardware, you tell OBS to lock onto those specific hardware IDs. Even if Windows updates its default device list, OBS will continue looking for the correct physical inputs and outputs.

---

Step 2: Re-Route Your Audio Without the “Output Only” Option

The removal of the “Monitor Only (mute output)” option in Advanced Audio Properties left many broadcasters scrambling. If you previously used this feature to route game audio, Discord, or alerts to your headphones without sending them to the main stream mix, your audio is likely now looping, echoing, or silent.

To fix this, you must adjust how you handle monitoring and track assignments in the new setup.

The Modern Workaround: Multi-Track Matrixing

Instead of relying on the old “Monitor Only” toggle, you need to use the audio track matrix to control what goes to the stream and what goes to your ears.

1. Right-click anywhere in the Audio Mixer dock and select Advanced Audio Properties.
2. Look at the right side of the window under the Tracks columns (numbered 1 through 6).
3. By default, Track 1 is typically your stream track (the mix that goes live to Twitch, YouTube, or Kick).
4. If you want to hear a source (like Discord) in your headphones but do not want it to play on the stream:
   • Set that source’s Audio Monitoring to Monitor Only (mute output) if your version still displays a legacy variation, OR set it to Monitor and Output.
   • If using Monitor and Output, simply uncheck Track 1 for that source.
   • By unchecking Track 1, you prevent that audio from being mixed into the primary stream broadcast, but because “Monitor” is still active, you will hear it perfectly through your designated monitoring device.

Setting the Correct Monitoring Device

If you are using the monitoring method described above, you must ensure OBS is sending that monitored audio to the correct place.

1. Go to Settings > Audio.
2. Scroll down to the Advanced section.
3. Under Monitoring Device, select your exact headphones or physical audio interface.
4. Crucial Step: Check the box that says Disable macOS/Windows audio ducking if it is available. This prevents your operating system from lowering the volume of your stream game sounds when someone speaks on Discord.

---

Step 3: Unhide and Clean Up “Ghost” Audio Sources

The rewritten audio mixer introduces a cleaner UI, but it also hides inactive or disconnected sources by default. This can lead to situations where a “ghost” source (such as an old capture card or a disconnected USB mic) is still assigned to an audio channel behind the scenes, creating resource conflicts.

If your active microphone is flat-lining and refusing to show movement on the volume meter, check for these hidden conflicts:

1. Look at your Audio Mixer panel.
2. Click the three vertical dots next to any active audio source.
3. Select Show Inactive/Hidden Sources from the context menu.
4. Look through the newly revealed list. If you see old, grayed-out sources that you no longer use (like a webcam mic you replaced long ago), right-click them and select Remove or Hide.
5. Restart OBS Studio to clear the audio cache.

This cleanup process ensures that OBS isn’t trying to share a driver path between an active device and a disconnected zombie device.

---

Step 4: Resolve Operating System Permissions and Integrity Blocks

If you have assigned the correct devices and configured your tracks properly, but the mixer bars are still completely still, your operating system is likely blocking OBS from accessing your audio hardware.

Major OBS updates can change the digital signature of the application executable. Security protocols in Windows 11 (like Core Isolation and Audio Integrity checkmarks) or macOS Sequoia security settings may see this changed signature and block microphone access without telling you.

Fixing Access Block on Windows 11/10

1. Open your Windows Start Menu and click the Settings gear icon.
2. Go to Privacy & Security (or just Privacy on Windows 10).
3. Scroll down on the right side and click on Microphone under App Permissions.
4. Make sure the toggle for Let desktop apps access your microphone is turned On.
5. Scroll down the list of apps and verify that OBS Studio (or Open Broadcaster Software) is listed and active. If it is turned off, toggle it back on.
6. If it is already on, toggle it off, wait five seconds, and toggle it back on. This forces Windows to refresh the app’s security token.

Fixing Access Block on macOS

1. Click the Apple menu in the top-left corner and open System Settings.
2. Navigate to Privacy & Security and select Microphone.
3. Locate OBS in the list of applications.
4. Toggle the switch next to OBS to the blue (active) position.
5. If prompted, enter your administrator password to confirm the change, then restart OBS.

---

Step 5: Implement Virtual Routing for Complex Mixes

If the removal of legacy monitoring options has completely broken your setup and you cannot achieve the separation you need using OBS’s built-in track matrix, it is time to transition to a virtual audio router.

Relying entirely on OBS to mix and monitor your audio can be risky during updates. By offloading your audio routing to a dedicated software mixer, you insulate your stream setup from future OBS updates.

Virtual Audio Cable (VB-Audio) Method

Using a virtual cable allows you to split audio streams before they ever reach OBS.

1. Download and install a virtual audio cable driver (such as VB-Cable or Virtual Audio Cable).
2. Restart your computer to allow the virtual driver to register with your system.
3. Set your game or communication app (like Discord) to output to Cable Input (VB-Audio Virtual Cable).
4. In OBS, add a new Audio Input Capture source to your scene and set it to Cable Output (VB-Audio Virtual Cable).
5. Because the audio is now coming in as an independent capture source, you can control its volume, mute status, and track assignments separately without relying on complex internal OBS monitoring loops.

Dedicated Mixer Software

If you have a modern USB microphone or audio interface, you might already have access to proprietary routing software:

• Elgato Wave Link: Ideal for Wave microphone users. It provides virtual channels for game music, voice chat, and system sounds, outputting a single, clean “Stream Mix” directly to OBS.
• SteelSeries Sonar: A free software suite that works with any headset. It allows you to drag and drop applications into virtual channels (Game, Chat, Media, Aux) and send them as clean virtual inputs into OBS.
• Rode Central / Unify: Excellent for users of Rode hardware, offering physical-to-virtual routing that bypasses OBS’s internal monitoring altogether.

By configuring your audio routing in one of these external applications, your OBS audio setup becomes incredibly simple: you only need to add two sources to OBS—your microphone and your virtual “Stream Mix” output. Even if OBS updates its audio mixer again in the future, your main routing will remain completely untouched.

---

Final Verification Steps

Before you go live, run through this quick checklist to ensure your new configuration is stable:

• Check Sample Rates: Make sure your physical hardware, your operating system settings, and OBS are all running at the same sample rate (either 44.1 kHz or 48 kHz). You can verify this in OBS under Settings > Audio > General, and in Windows under Sound Control Panel > Properties > Advanced. Mismatched sample rates can cause audio drift, crackling, or complete silence over long broadcasts.
• Test with a Test Recording: Never test your audio live. Click Start Recording in OBS, speak into your mic, play your game, and trigger some alerts. Stop the recording and play the video file back in a media player like VLC to verify that all tracks are hitting the correct volume levels.
• Save an Audio Profile Backup: Once everything works, go to Profile in the top menu bar of OBS and click Duplicate. Name it something like “Audio Fixed Backup.” If a future update resets your settings again, you can switch back to this profile to restore your configurations instantly.