Enabling WASAPI Exclusive Mode

Setting an output device to Exclusive in MZAP is only half the job — Windows must also permit applications to take exclusive control of that endpoint. If the Windows checkbox is off, MZAP cannot acquire the device exclusively, falls back to Shared mode, and shows a fallback warning on the device card.

Use this page when a device you set to Exclusive keeps coming back as Shared, or when zones mapped to rear/center/LFE channels are silent.

Why exclusive mode matters

In Shared mode every application's audio passes through the Windows audio engine, which mixes and — on Windows 11 — often downmixes multichannel content to the front stereo pair. Zones mapped to channels 3–6 (rear, center, LFE) then play nothing.

Exclusive mode hands the device to MZAP directly, bypassing the Windows mixer, so each channel is addressed individually and latency is lowest.

The trade-off: while MZAP holds the device exclusively, other applications — including Windows system sounds and browser audio — cannot play through it.

Enable it in Windows

1. Open the classic Sound control panel. Press Win + R, type mmsys.cpl, and press Enter.

   In the MZAP desktop app you can jump straight there: select Exclusive on a device card and click Open Sound settings. (Host machine only — the shortcut is hidden for LAN and browser clients.)

2. Go to the Playback tab and select the output device you want MZAP to own.

3. Click Properties, then open the Advanced tab.

4. Tick Allow applications to take exclusive control of this device.

5. Also tick Give exclusive mode applications priority — this lets MZAP keep the device when another app requests it.

6. Click OK to close both dialogs.

Set the default format

The Advanced tab also has a Default Format dropdown. This sets the sample rate and bit depth Windows uses for the device in Shared mode.

MZAP does not resample in Exclusive mode: it probes the device for a supported exclusive format, preferring the engine rate and then 48000, 44100, 96000, 88200, and 192000 Hz. Choosing a Default Format your source material matches (commonly 24-bit, 48000 Hz) avoids an unnecessary conversion when the device runs in Shared mode.

Restart MZAP

Windows applies the change to new audio sessions, so restart MZAP afterwards. On the next launch the device card should show the effective mode as Exclusive rather than a Shared fallback warning.

Set the speaker layout for multichannel cards

For a card that should output 5.1 or 7.1, tell Windows its physical layout as well, or MZAP only ever sees a stereo endpoint:

1. In the same Sound control panel, Playback tab, select the device.
2. Click Configure.
3. Choose 5.1 Surround or 7.1 Surround and complete the wizard.
4. Back in MZAP, re-initialize devices so it picks up the full channel count.

If it still falls back to Shared

• Another application already holds the device exclusively. Close other audio apps and restart MZAP. Ticking Give exclusive mode applications priority (step 5) usually prevents this.
• The device exposes no exclusive format at its channel count. MZAP logs a warning and stays in Shared mode so the device still plays — the front pair only, on a multichannel card. Try a different Default Format, or use the DirectSound output path.
• The card collapses multichannel regardless of mode. Some hardware — the Creative Sound Blaster Live! 24-bit External is a known example — downmixes to the front pair over WASAPI in both Shared and Exclusive modes. These cards need the DirectSound output path for discrete 5.1/7.1.
• A second endpoint on the same card is open. Opening an unused sibling endpoint can force the whole card to stereo. Switch the unused endpoint off — see Turning output devices on and off.

Check the logs for the warning MZAP writes when an exclusive initialization fails; it names the device and the reason.