How to enable exclusive mode on macOS

Last updated September 2026

Exclusive mode — hog mode, in CoreAudio’s own terms — lets one application take sole control of an audio device. Sample-rate selection, volume and processing still need to be checked separately. It is the first of the conditions for bit-perfect playback, and on its own it is not sufficient. This is how to turn it on, what else has to be true, and how to check rather than assume.

The one-line version: turn on Exclusive Mode in your player, let it set the device to each file’s own rate, leave the software volume at unity, and then read the signal path instead of trusting the toggle.

What exclusive mode actually does

CoreAudio exposes a property on every device — hog mode — that a single process can claim. While it is held, that process owns the device and the system mixer is out of the picture.

That matters because of what the mixer does the rest of the time. macOS runs every application’s audio into one shared graph, resamples all of it to whichever rate the device happens to be set to, and applies the system volume. It is an excellent design for a computer — your music, a video call and a notification chime can all play at once — and it is the wrong design for one specific job. Play a 96 kHz file while the device sits at 48 kHz and your DAC receives 48 kHz. Nothing tells you. The file was fine; the path was not.

Exclusive mode removes that stage. It does not make the audio better; it stops something from being done to it.

Steps

1. Connect your DAC and select it as the output device. Exclusive mode is for a real hardware device — USB, Thunderbolt, or S/PDIF — not for AirPlay, Bluetooth or a system aggregate.
2. Enable Exclusive Mode (hog mode) in your player’s audio settings. In BitMuse it is a single toggle. While it is on, macOS routes other system sounds to another output.
3. Turn on integer mode and let the player match the device sample rate to each file, so nothing is resampled or converted to floating point on the way out. See integer mode on macOS for what that second switch adds.
4. Leave the volume at unity — 0 dB — or use the DAC’s own hardware volume. A software volume slider below 100% multiplies every sample, which is arithmetic on your audio and ends bit-perfect output immediately.
5. Verify the signal path. A player worth using shows the device rate, the format at each hop and the state of every one of these conditions, live, while the music plays.

Exclusive mode alone is not bit-perfect

This is the part most guides skip, and it is why people turn the toggle on and still do not get what they came for. Four things have to hold at once:

• The device is held exclusively — the mixer is out of the path.
• The device rate equals the file rate. A player set to a fixed output rate, or to “power of two” upsampling, is resampling on purpose. That may be what you want; it is not bit-perfect.
• No format conversion at the last step. Without integer mode the samples are handed over as floats and converted by the driver.
• Volume passes at unity. Hardware volume on the DAC is free; software volume is not.

Any DSP you have switched on breaks it too, by definition — an equaliser that changes nothing is an equaliser doing nothing. That is why a well-built chain ships with every effect off and says so.

When a device refuses

Some outputs cannot be taken exclusively, and a player that pretends otherwise is worse than one that says no:

• Bluetooth and AirPlay. Both re-encode the audio before it leaves the Mac. There is no untouched path to protect, so exclusive mode is meaningless rather than merely unavailable.
• Aggregate and multi-output devices. An aggregate is a software device in front of the real ones, so BitMuse does not take exclusive control of it — multi-output switches exclusive and integer mode off.
• A device another application already holds. Only one process can hold hog mode. If something else has it, the request is refused.
• The occasional class-compliant device whose driver declines the property outright.

In each case the honest behaviour is to report the refusal and keep playing without the claim. BitMuse puts the reason on the signal path and takes the bit-perfect badge down.

How to confirm it actually worked

Enabling a toggle is not proof. Nor is listening: the failure mode here is a resample that sounds fine, which is precisely why it goes unnoticed for years.

The reliable check is a live signal path — exclusive mode active, device rate equal to file rate, integer output, volume at unity, no processing — read while the track is playing rather than from a settings screen. BitMuse reports bit-perfect only when every condition is met, and names the one that is missing when it is not, so what you are doing is verifying rather than assuming.

What exclusive mode does not do

It does not restore information missing from a lossy file, change your DAC’s analogue stage or make a 44.1 kHz recording into a hi-res one. The Mac’s built-in speakers also apply processing that the player cannot bypass.

Exclusive mode controls access to the device. An unchanged signal also depends on the output rate, format, volume and processing. Inspect the active path while music is playing; the toggle alone is not a guarantee.

FAQ

Do I need a DAC for exclusive mode?

BitMuse can use your Mac’s output or an external DAC. Available modes depend on the device and its driver. The built-in speakers and headphone jack are different outputs; the speakers apply processing that BitMuse cannot bypass. Use Signal Path to check the actual mode. Experimental DoP requires a compatible DSD DAC.

Will other apps still make sound in exclusive mode?

No, not through that device. While a process holds a device in hog mode, macOS routes other system audio elsewhere — usually to the built-in output. Notifications, browser video and system alerts keep working, they just do not come out of your DAC. Turning exclusive mode off hands the device back.

Is exclusive mode the same as bit-perfect?

No. Exclusive mode is one of four conditions. The device also has to be running at the file’s own sample rate, the samples have to reach it without a float conversion or resampling step, and the volume has to be passing at unity — a software volume slider below 100% scales every sample and breaks it. Exclusive mode removes the mixer; the other three are separate settings.

Why does exclusive mode fail on some devices?

Bluetooth and AirPlay outputs cannot be taken exclusively in any useful sense — both re-encode the audio before it leaves the Mac, so there is no untouched path to protect. Aggregate and multi-output devices are owned by the system rather than by your player. And another application can already be holding the device, in which case the request is refused. A player worth using reports the refusal rather than continuing quietly.

Get exclusive-mode playback — free for 30 days

30 days, every feature, no account and no card.
$99.95 once if you keep it · macOS 15+ · Apple Silicon