mpv WASAPI Exclusive No Sound: How to Fix It

When mpv produces no sound after WASAPI exclusive mode is enabled, the failure usually falls into one of a few categories: mpv is using the wrong option or audio device, another application already controls the endpoint, Windows does not permit exclusive access, the device rejects the requested sample rate or format, or an aggressive buffer setting prevents initialization. A profile, script, track selection, stream limitation, or unrelated playback option can also make the problem look like a WASAPI failure. The safest approach is to reproduce the symptom with a minimal command, read the relevant terminal messages, and change one setting at a time. This guide focuses specifically on WASAPI exclusive mode while also showing how to distinguish it from a broader mpv player issue.

1. Confirm the Symptom With a Minimal Clean mpv Command

Start by determining whether exclusive mode itself causes the silence. Do not begin by rewriting your main configuration. Open PowerShell, Command Prompt, or another terminal in a directory containing a known-good local media file with an ordinary audio track. Use a file that already plays correctly in another player and does not depend on a network connection, yt-dlp, DRM, an external subtitle file, or unusual codecs.

Run this shared-mode baseline first:

mpv --no-config --ao=wasapi "test-file.mkv"

If you hear audio, the file, selected track, Windows endpoint, and basic WASAPI output are functioning. Stop investigating subtitles, HDR, shaders, network access, and hardware decoding for the moment. The relevant difference is likely exclusive access.

Now test exclusive mode:

mpv --no-config --ao=wasapi --audio-exclusive=yes "test-file.mkv"

A successful test produces audible sound and terminal output showing that mpv opened a WASAPI audio device. Other applications may temporarily lose access to that device while playback continues. If shared mode works but this command is silent or reports that it cannot initialize the audio device, you have confirmed an mpv WASAPI Exclusive no sound problem.

If both commands fail, exclusive mode is probably not the primary cause. Check whether the file has an audio track, whether mpv selected it, whether Windows is using the expected output, and whether the volume is muted. If the terminal says that wasapi is unavailable, inspect your mpv build and operating system. WASAPI is a Windows audio API, so Linux and macOS do not provide it as a native output backend.

1.1 Understand the Platform Boundary

On Windows, mpv can use WASAPI and request exclusive control of a compatible endpoint. On Linux, use an available backend such as PipeWire, PulseAudio, or ALSA. On macOS, mpv normally uses CoreAudio. A configuration copied from Windows can therefore make mpv not work correctly on another operating system if it forces ao=wasapi or enables a Windows-only profile.

For a cross-platform configuration, place Windows-specific settings inside a conditional profile or keep them in a separate configuration. Success means mpv selects the native backend on Linux or macOS without attempting to initialize WASAPI. Once that happens, stop changing Windows exclusive-mode settings because they cannot affect playback on those systems.

2. Check the mpv Options and Configuration Directly Related to Audio

If the clean exclusive command works, your normal mpv configuration is causing the failure. The most relevant setting is audio-exclusive, but forced devices, audio filters, profiles, scripts, and track-selection rules can alter the result.

2.1 Verify audio-exclusive and the Output Driver

Search mpv.conf and any included configuration files for these options:

• audio-exclusive=yes
• ao=wasapi
• audio-device=...
• audio-samplerate=...
• audio-format=...
• audio-channels=...
• audio-buffer=...
• af=... or af-add=...

Confirm that the option is spelled audio-exclusive=yes. An obsolete example copied from a forum, a misplaced command-line prefix, or an option entered under the wrong profile may be ignored or may prevent the profile from behaving as expected.

Do not force ao=wasapi while testing on Linux or macOS. On Windows, allowing ao=auto can be useful as a comparison because it lets mpv choose a working output. Success means the terminal identifies a usable audio output and sound begins without repeated initialization errors.

2.2 List and Select the Correct Audio Device

Run:

mpv --audio-device=help

This displays the audio devices recognized by the available output drivers. Device identifiers should be copied exactly. Bluetooth headsets, HDMI receivers, monitors, USB DACs, and docking stations can expose multiple endpoints, some of which disappear when disconnected or when the display path changes.

Test the desired endpoint with a clean command:

mpv --no-config --ao=wasapi --audio-exclusive=yes --audio-device="DEVICE_ID" "test-file.mkv"

Replace DEVICE_ID with an identifier printed by mpv. Shell quoting matters when the identifier or file path contains spaces or special characters. In PowerShell and Command Prompt, enclosing the complete value in double quotes is usually appropriate.

Success means mpv opens the intended speakers, headphones, DAC, or HDMI device and audio is heard there. Stop changing device settings when the correct endpoint works consistently.

2.3 Inspect Profiles, Input Bindings, and Scripts

An mpv profile may enable exclusive mode only for particular files, protocols, displays, or codecs. An input binding can also toggle audio settings during playback. Search mpv.conf, included files, and input.conf for audio-exclusive, audio-device, ao, af, and commands that cycle audio tracks.

Use this command to inspect a named profile:

mpv --show-profile=profile-name

Replace profile-name with the profile you suspect. Review every inherited option rather than assuming the profile changes only video or HDR behavior.

Temporarily disable scripts without removing them permanently by testing with --no-config. If a more targeted test is needed, use a temporary configuration directory containing only the audio options under investigation. Success means the minimal configuration works and reintroducing one specific profile, binding, or script reproduces the silence. At that point, fix or remove only the responsible line.

2.4 Confirm the Audio Track Is Present and Selected

Press the key bound to mpv's stats or track-selection interface, or inspect the terminal output, to verify that the file contains an audio stream. You can cycle audio tracks during playback with the default track controls or explicitly select one using --aid.

A file can contain commentary, unsupported passthrough audio, or no audio at all. Network streams can also change track availability after playback starts. Subtitle settings, screenshot templates, shaders, and HDR tone mapping generally do not control WASAPI, but a complex profile may combine them with audio options. Treat them as suspects only if disabling that profile changes the result.

Success means mpv reports a selected audio track and shared mode plays it. If no audio track exists, exclusive mode is not the cause and you should stop adjusting WASAPI.

3. Check Windows Exclusive Access, Device Use, and Format Support

WASAPI exclusive mode asks Windows for direct, exclusive control of an audio endpoint. Unlike shared mode, it cannot rely on the Windows audio engine to mix multiple applications or convert every requested stream into the device's shared format. This makes device availability and format compatibility especially important.

3.1 Close Applications Already Using the Device

Another application may already hold exclusive control. Close music software, games, browsers, voice-chat clients, digital audio workstations, measurement tools, virtual mixers, and other media players. Also check background utilities supplied with a DAC, headset, sound card, or HDMI receiver.

Pause is not always enough because an application may keep its audio stream open. Exit it fully, then restart the mpv test. If necessary, disconnect and reconnect a USB audio device or sign out and back in to clear a stuck session before making configuration changes.

Success means mpv opens the endpoint as soon as the competing application closes. If so, the fix is to avoid simultaneous exclusive clients or use shared mode when multiple applications need sound.

3.2 Enable Exclusive-Mode Permissions in Windows

Open the classic sound device properties for the output endpoint. Depending on the Windows version, you can reach these controls through Sound settings, More sound settings, Playback, the selected device, and Properties. On the Advanced tab, look for options that allow applications to take exclusive control and give exclusive-mode applications priority.

Enable the permission to let applications take exclusive control. Apply the change, close mpv, and launch the clean exclusive test again. Device enhancements or vendor control panels may expose additional controls, but change those only if the basic Windows permission is already correct.

Success means the same --audio-exclusive=yes command that previously failed now opens the device and plays audio. Once confirmed, stop modifying unrelated GPU, subtitle, or network options.

3.3 Test for an Unsupported Sample Rate or Format

An endpoint may accept 48 kHz stereo PCM but reject a different sample rate, channel layout, bit depth, or encoded passthrough format in exclusive mode. HDMI devices can also advertise capabilities differently when a television, receiver, cable, dock, or display mode changes.

First test several known-good files with ordinary stereo PCM or common decoded audio. Avoid forcing audio-format, audio-samplerate, or audio-channels. Let mpv negotiate a format. If your configuration forces any of those values, comment them out temporarily rather than deleting the complete configuration.

If only one media file fails, inspect its audio codec, channel count, and sampling rate through mpv's track information. Try decoding to PCM instead of using passthrough. Options associated with encoded audio passthrough can require exact hardware support and are more restrictive than normal decoded playback.

Success means mpv plays after the forced format or passthrough setting is removed. Stop when normal negotiation works. There is no benefit in forcing a format solely because it appears more advanced.

3.4 Adjust Buffer Duration Conservatively

A very small audio buffer can cause initialization failures, dropouts, or silence on some drivers and devices. Search your configuration for audio-buffer. If it is set to an unusually low value, remove the override temporarily and let mpv use its default behavior.

If you need to test explicitly, begin with a moderate buffer rather than pursuing the lowest possible latency. Change only one buffer-related option at a time and replay the same local file after each change. Bluetooth devices, networked audio paths, USB DACs, and vendor drivers may behave differently.

Success means audio begins promptly and continues without underruns, repeated resets, or gaps. Once playback is stable, stop lowering the buffer. For video playback, a tiny latency reduction rarely outweighs unreliable audio.

3.5 Fall Back to Shared Mode When Appropriate

Exclusive mode is optional. If the device or driver refuses the media format, another application must remain audible, or exclusive access is unreliable after sleep and device switching, use shared mode:

mpv --ao=wasapi --audio-exclusive=no "test-file.mkv"

You can remove audio-exclusive=yes from the regular configuration or put it in a profile used only with a compatible DAC or receiver. Shared mode allows the Windows audio engine to mix applications and perform format conversion.

Success means dependable playback through the correct device with no initialization error. If shared mode satisfies your listening needs, this is a valid permanent fix rather than an incomplete workaround.

4. Separate Audio Failure From Video, Stream, and External Tool Problems

Users with elaborate mpv setups often enable hardware decoding, HDR processing, shaders, scripts, yt-dlp, IPC, custom subtitles, and network options together. These features do not normally determine whether WASAPI can open an endpoint, but they can stop playback before audio initialization or obscure the actual error.

4.1 Test Without Hardware Decoding and GPU Customization

If the player window closes, freezes, or never advances, test with --hwdec=no and without custom shaders. A GPU driver or display-server failure can halt playback even when audio settings are valid. On Linux, Wayland or X11 output issues are separate from WASAPI because WASAPI is unavailable there.

Success means playback advances and audio initialization messages become visible. If video customization was responsible, repair that configuration separately. Do not describe the result as a WASAPI exclusive fix unless shared and exclusive audio now behave differently.

4.2 Replace Online Media With a Local Test File

For online URLs and playlists, first prove that exclusive mode works with a local file. A failing URL may involve network access, authentication, an expired stream address, yt-dlp availability, site changes, or missing media tracks. These failures can produce silence without an audio-device problem.

If local exclusive playback works, run the URL with terminal output visible. Confirm that mpv finds yt-dlp when the site requires it and that the selected stream contains audio. Obtain yt-dlp and mpv only from their official projects or trusted package managers. Do not install random codec packs or unknown binaries.

Success means the URL resolves, an audio track is listed, and the existing exclusive-mode setup plays it. If the URL fails before a track is opened, stop changing WASAPI options and troubleshoot the source or external tool.

5. Use Logs and Runtime Information to Identify the Exact Failure

mpv's terminal output is usually more useful than guessing. Launch mpv from a terminal instead of opening the file by double-clicking. Read messages around audio device selection, format negotiation, track selection, and audio-output initialization.

5.1 Increase Audio Logging and Save a Log File

Run a focused diagnostic command:

mpv --no-config --ao=wasapi --audio-exclusive=yes --msg-level=ao=trace --log-file=mpv-wasapi.log "test-file.mkv"

The log can reveal whether the endpoint was found, whether access was denied, whether the device was busy, or whether format negotiation failed. Avoid posting an unreviewed log publicly because command lines, file paths, URLs, usernames, and tokens may contain private information.

Look for the first meaningful audio error rather than every warning. A subtitle warning or screenshot-directory error is not evidence that WASAPI failed. Likewise, an HDR metadata message does not explain why an endpoint rejected exclusive access.

Success means the log reaches a clear audio-output initialization state and playback begins. If it identifies a specific device, permission, or format error, address that cause and rerun the exact same command.

5.2 Use Profiles, Stats, and Track Information Carefully

--show-profile helps expose hidden options inherited through profiles. The stats overlay can confirm whether playback time advances, which codecs are active, and whether audio is synchronized. Track information confirms whether mpv selected an audio stream.

These tools answer different questions. Use the terminal log to diagnose endpoint opening, the track list to confirm media content, and the stats overlay to verify active playback. Success means all three observations agree: a track exists, the output opens, and playback time advances with audible sound.

6. Run a Clean Temporary Test Before Changing Many Options

A disciplined temporary test prevents one fix from being confused with another. Keep your main configuration intact and use this sequence:

1. Choose one known-good local file with an ordinary audio track.
2. Close other applications that may use the output device.
3. Run mpv with --no-config in shared WASAPI mode.
4. Repeat with --audio-exclusive=yes.
5. If exclusive mode fails, verify Windows permission and test the correct device identifier.
6. Remove forced sample rate, format, channel, passthrough, and low-buffer settings.
7. Save a focused log if the failure continues.
8. Reintroduce your normal options one group at a time.

Group settings by function. Add basic audio options first, then profiles, scripts, hardware decoding, shaders, subtitles, network tools, and IPC settings. Replay the same file after each group. When the silence returns, divide that group into individual options.

Success is not merely the absence of an error message. You should hear continuous audio from the intended endpoint, see playback time advance, and be able to reproduce the result after restarting mpv. Once those conditions are met, stop changing settings.

7. Quick Fix Checklist

• Confirm that shared WASAPI mode plays the same local file.
• Test exclusive mode with --no-config.
• Use --audio-device=help and select the intended endpoint.
• Close applications that may already hold exclusive access.
• Enable exclusive-control permissions in Windows device properties.
• Remove forced sample rate, format, channel layout, and passthrough options.
• Restore a reasonable audio buffer if you forced an extremely low value.
• Verify that mpv selected a real audio track.
• Inspect profiles, scripts, and input bindings for hidden audio changes.
• Use --msg-level=ao=trace and --log-file for a specific error.
• Test local media before troubleshooting yt-dlp or a network stream.
• Use shared mode if exclusive operation remains incompatible or unnecessary.

8. Frequently Asked Questions

8.1 Why Does Shared WASAPI Work While Exclusive Mode Is Silent?

Shared mode uses the Windows audio engine for mixing and format conversion. Exclusive mode asks the endpoint to accept a direct stream and prevents normal sharing. Silence or initialization failure therefore commonly points to a busy device, disabled exclusive permissions, an unsupported format, or a driver limitation.

8.2 Can Another Application Block mpv Exclusive Mode?

Yes. Another exclusive client can prevent mpv from opening the endpoint, and some audio applications keep streams active in the background. Exit those applications fully and repeat the clean test. If mpv works immediately afterward, no further configuration changes are needed.

8.3 Should I Force the Highest Sample Rate?

No. Forcing a high sample rate does not automatically improve playback and may request a format the endpoint cannot accept in exclusive mode. Let mpv negotiate first. Force a format only when you understand the device's documented capabilities and have a specific reason.

8.4 Does Hardware Decoding Cause WASAPI Exclusive Silence?

Not directly. Hardware decoding handles video, while WASAPI handles Windows audio output. However, a GPU or video-output failure can stop the playback pipeline and resemble a general mpv failure. Test with --hwdec=no only when video freezes, the window closes, or playback time does not advance.

8.5 Why Does Exclusive Mode Fail After Switching HDMI Displays or USB Devices?

The old endpoint may have disappeared, changed identifiers, or advertised different audio capabilities. Run --audio-device=help again, choose the current endpoint, and avoid retaining a stale forced device. Reopening mpv after the hardware switch can also release the previous audio session.

8.6 Is Falling Back to Shared Mode a Proper Fix?

Yes. Shared mode is often the better choice when you need audio from multiple applications, automatic format conversion, or reliable device switching. Exclusive mode is useful only when its behavior and hardware compatibility serve a specific need. Stable shared-mode playback is a successful outcome, not a failure.