mpv Surround Sound Downmix Wrong: How to Fix It

When an mpv surround sound downmix sounds wrong, dialogue may be too quiet, effects may dominate, rear-channel sounds may disappear, or audio may seem to come from the wrong side. The usual causes are an incorrect target speaker layout, an unexpected channel map in the operating system, a custom audio filter, or an HDMI receiver configuration that does not match the selected output mode. The safest approach is to reproduce the problem with a clean command, identify whether mpv is actually downmixing, and change one audio setting at a time.

1. Confirm the Symptom With a Minimal Clean mpv Command

Begin with a local media file whose audio track you understand. A movie can reveal weak dialogue, but a channel identification sample is better because it announces or plays a signal through each labeled channel. Use a legally obtained test file from a trusted source.

Open a terminal or command prompt and run mpv without loading your normal configuration:

mpv --no-config --audio-channels=stereo "path/to/test-file.mkv"

On Windows, use the complete path to mpv if its directory is not in PATH:

"C:\path\to\mpv.exe" --no-config --audio-channels=stereo "C:\media\test-file.mkv"

On Linux or macOS, quote paths containing spaces:

mpv --no-config --audio-channels=stereo "/home/user/Videos/channel test.mkv"

The --no-config option temporarily bypasses configuration files, profiles, user scripts, and normal customizations. It does not delete anything. The --audio-channels=stereo option asks mpv to produce a two-channel output layout, causing multichannel audio to be downmixed when necessary.

Success means the left and right channel announcements are correctly positioned, the center channel is audible through both speakers, dialogue is balanced, and surround content contributes without overwhelming the front channels. If this clean test sounds correct, stop changing operating system and driver settings. The fault is probably in your mpv configuration, profile, script, binding, or filter chain.

If the clean test remains wrong, repeat it with a second known-good local file. A single file can have mislabeled channels, an unusual mix, or incorrect metadata. If only one file fails, the file is the likely limitation rather than a general mpv player issue.

1.1 Verify the Selected Audio Track

A media file may contain stereo, 5.1, 7.1, commentary, descriptive audio, or alternate-language tracks. Selecting a commentary track or a poorly mixed stereo track can resemble a failed downmix.

During playback, use mpv's track controls or on-screen interface to inspect the selected audio track. You can also run:

mpv --no-config --audio-channels=stereo --aid=auto "path/to/test-file.mkv"

If necessary, select a specific audio track by its displayed ID:

mpv --no-config --audio-channels=stereo --aid=2 "path/to/test-file.mkv"

Success means mpv reports the intended multichannel source track and produces balanced stereo. Once the correct track fixes the symptom, do not alter downmix coefficients or install additional codecs.

2. Check the mpv Settings Directly Related to Downmixing

The central setting is audio-channels. It describes the output channel layout mpv should request or create. For headphones, laptop speakers, stereo monitors, and most two-speaker desktop systems, explicitly testing stereo removes uncertainty.

2.1 Set the Intended Speaker Layout

Add the following line to mpv.conf only after the clean command proves it works:

audio-channels=stereo

Typical user configuration locations include %APPDATA%\mpv\mpv.conf on Windows, ~/.config/mpv/mpv.conf on Linux, and ~/.config/mpv/mpv.conf on many macOS installations. The actual location can vary with the build, launch method, or portable configuration.

Do not assume that selecting a larger layout improves sound. If a stereo device is told to accept 5.1 channels, center and surround channels can be lost downstream instead of being mixed into left and right. Conversely, forcing stereo is inappropriate when the goal is to send discrete multichannel PCM to an AV receiver.

Success means mpv's output is two channels when using stereo speakers, with center dialogue clearly represented in both channels. At that point, stop. Extra filters intended to boost the center channel can distort a correctly produced mix.

2.2 Search for Conflicting Configuration Entries

Open mpv.conf and search for settings involving audio-channels, af, audio-spdif, ao, or profiles. Duplicate settings can be confusing because a later applicable value may supersede an earlier one.

Temporarily comment out custom audio filters and test again. Pay particular attention to filters that remap channels, apply pan matrices, normalize volume, compress dynamic range, or add crossfeed. A custom pan matrix written for one channel order can produce an unbalanced result with another layout.

Also inspect profiles activated by file type, protocol, resolution, display, or other conditions. A profile intended for television playback may force an HDMI layout when used with headphones. A profile for network streams may contain different audio options from your local-file profile.

Success means normal playback with configuration enabled now matches the clean --no-config test. Stop once you identify the single conflicting line. There is no need to remove unrelated subtitle, shader, HDR, or video settings.

2.3 Inspect Input Bindings and Scripts

Review input.conf for bindings that modify audio channels, audio filters, track selection, or profiles. A key used for another purpose may toggle a filter without an obvious permanent indication.

User scripts can also change properties after playback starts. Temporarily move only suspected audio-related scripts out of the scripts directory, or disable them using the method documented by that script. Do not delete the entire configuration directory.

Subtitle settings do not ordinarily alter a surround downmix. Video shaders, screenshot settings, HDR tone mapping, and hardware decoding also do not normally change audio channel mixing. Investigate them only if a script or profile ties audio behavior to those features. This distinction prevents an audio problem from turning into an unnecessary full-player rebuild.

3. Check the Output Path and Operating System Channel Map

If --no-config --audio-channels=stereo is still wrong across multiple known-good files, inspect the path after mpv. The operating system's audio server, device driver, USB interface, television, or receiver can remap or discard channels.

3.1 AV Receiver and HDMI Output

Decide whether you want mpv to downmix or your AV receiver to process discrete surround audio. These are different workflows.

• For stereo speakers connected to the computer, request stereo from mpv.
• For discrete multichannel PCM over HDMI, configure the operating system and receiver for the actual speaker layout.
• For encoded passthrough, the receiver performs decoding, and mpv's normal PCM downmix is not the active path.

When troubleshooting, avoid passthrough first and test decoded stereo PCM. Passthrough can make volume controls, filters, and downmix expectations irrelevant because the encoded stream is sent to the receiver. If stereo PCM is correct but passthrough is not, focus on the receiver's supported formats, HDMI connection, selected input mode, and speaker configuration.

Success with an AV receiver means every announced channel reaches the correct physical speaker in multichannel mode, or every channel folds into the expected left and right speakers in stereo mode. Once that happens, do not force a second downmix in both mpv and the receiver.

3.2 PulseAudio and PipeWire Channel Maps

On Linux, PulseAudio or PipeWire may expose a sink with a channel map that does not match the hardware. Desktop sound settings may also have the device set to stereo, 5.1, or 7.1 independently of mpv.

Use the desktop audio control panel or trusted distribution tools to confirm the active output device and profile. Test each speaker through the system's own speaker test. If the operating system's front-left test plays through another speaker, correct that map before changing mpv.

PipeWire systems may provide PulseAudio-compatible control tools, so seeing a PulseAudio-style interface does not necessarily mean PipeWire is inactive. Avoid editing low-level audio-server configuration until the graphical device profile and physical cabling have been verified.

Success means the operating system's channel test and mpv's channel identification sample agree. If the system test itself is wrong, mpv cannot reliably compensate for every application with a one-off filter.

3.3 WASAPI and Windows Speaker Configuration

On Windows, check the selected playback device and its speaker configuration. If Windows is configured for 5.1 while only two speakers are connected, applications may send center-channel dialogue to an output that has no physical speaker.

For a stereo setup, select a stereo speaker configuration in Windows and retest with --audio-channels=stereo. For an HDMI receiver, select the layout that reflects the connected speakers and confirm the receiver is on the correct HDMI input and processing mode.

Exclusive audio output can behave differently from shared output because format negotiation changes. If you explicitly configured mpv to use a particular WASAPI mode or device, remove that override for one test. Success means shared and clean default output produce a stable, correctly mapped signal. You can then reintroduce the preferred output mode and confirm it does not recreate the problem.

3.4 macOS Output Layout

On macOS, verify the current output device and its channel configuration using the system's audio tools. HDMI devices and multichannel interfaces can expose layouts that differ from built-in speakers or headphones. Test built-in stereo output separately from HDMI. If built-in output is correct and HDMI is wrong, the issue is likely device negotiation, channel mapping, cabling, or receiver setup rather than mpv's basic downmix.

4. Use mpv Diagnostics Instead of Guessing

Terminal output can show the source audio format, selected track, decoder, requested channel layout, and audio output backend. Run the failing file from a terminal rather than launching it only through a file manager.

4.1 Create a Focused Log

Use a temporary log file and increase messages for audio decoding and output:

mpv --no-config --audio-channels=stereo --msg-level=ad=debug,ao=trace --log-file=mpv-audio.log "path/to/test-file.mkv"

Look for the selected audio stream, its reported channel layout, the decoded format, and the output layout accepted by the audio backend. Do not assume every warning is related. Network, subtitle, video, or cache messages may appear in the same log without affecting the downmix.

Success means the log shows a multichannel source being delivered as two-channel output when stereo was requested, and the audible channel test agrees. If the log reports stereo but physical speakers remain misassigned, investigate the operating system or downstream hardware.

4.2 Check Profiles and Runtime Information

If a named profile is suspicious, inspect it with:

mpv --show-profile=profile-name

Replace profile-name with the actual profile. This helps identify inherited audio options without rewriting the configuration.

With default input bindings available, mpv's statistics overlay can display playback information. The exact pages and bindings can depend on configuration and build, so use it as supporting evidence rather than the only channel-layout test. Terminal output and a channel identification file are more direct.

Inspect the track list to ensure the intended audio stream is selected. If an online source offers several formats, the chosen stream may contain stereo even when another format contains surround, or vice versa.

4.3 Separate Online Playback From Local Playback

For a URL opened through yt-dlp integration, first test a local multichannel file. If local downmixing works, mpv's core audio path is probably sound. The online service may provide a different audio format, yt-dlp may select another stream, or the server may advertise misleading metadata.

Update yt-dlp only through its official distribution method or your trusted package manager. Confirm that mpv can locate the intended executable. Do not download replacement binaries from random codec or utility sites.

For direct network streams, save or test a short authorized sample locally when practical. Network interruptions typically cause buffering or discontinuities, not a stable left-right imbalance, but a stream can change tracks or layouts between programs.

5. Run a Clean Temporary Test Before Making Permanent Changes

Use a controlled sequence so each result answers one question. Keep the volume moderate during channel tests.

1. Play a trusted channel identification file with --no-config --audio-channels=stereo.
2. Repeat with a second known-good local multichannel file.
3. Run the same command through a different physical output, such as wired headphones.
4. Remove --no-config while keeping --audio-channels=stereo.
5. Re-enable suspected profiles, filters, scripts, and output overrides one at a time.
6. Test HDMI or network playback only after local stereo output is correct.

If headphones sound correct but HDMI does not, stop editing mpv's downmix settings and inspect the HDMI device, receiver, and operating system layout. If both outputs fail only when your normal configuration loads, return to the conflicting configuration entry. If one media file alone fails, inspect that file's tracks and metadata.

Hardware decoding concerns video decoding and generally does not determine audio downmix coefficients. GPU drivers and display servers are similarly unlikely causes of a persistent channel imbalance. They become relevant only when the entire playback device or HDMI connection disappears, changes during display hot-plugging, or selects a different combined audio device.

6. Quick Fix Checklist

• Test a trusted channel identification sample at a safe volume.
• Run mpv --no-config --audio-channels=stereo "file".
• Confirm the correct audio track rather than commentary or descriptive audio.
• Set audio-channels=stereo for a genuine two-speaker output.
• Remove custom channel-remapping and pan filters temporarily.
• Check profiles, input bindings, and scripts that modify audio properties.
• Match PulseAudio, PipeWire, WASAPI, or macOS channel settings to the hardware.
• Test decoded PCM before diagnosing HDMI passthrough.
• Verify every receiver speaker with a channel identification sample.
• Use a log to compare source and output channel layouts.
• Test local media before blaming yt-dlp or a network stream.
• Stop changing settings as soon as channel positions and dialogue are correct.

7. Frequently Asked Questions

7.1 What does audio-channels=stereo do in mpv?

It requests a two-channel output layout. When the selected source track has more channels, mpv's audio processing path can downmix them into left and right. It does not turn a poorly authored track into a perfect mix, and it cannot repair speakers that are physically connected to the wrong outputs.

7.2 Why is dialogue quiet but music and effects are loud?

Film dialogue is commonly concentrated in the center channel. If the output path expects a physical center speaker that is not connected, dialogue can become very quiet or disappear. Force stereo for a two-speaker system and verify that the operating system is also configured for stereo. Dynamic range can also make effects louder than dialogue, but first rule out a missing center channel.

7.3 Should I use stereo output with an AV receiver?

Use stereo when you want mpv to perform the downmix or when only two receiver speakers are active. Use a matching multichannel layout when you want discrete decoded channels delivered to a properly configured receiver. If using encoded passthrough, the receiver handles decoding, so troubleshoot its format support and speaker setup separately.

7.4 Can hardware decoding, HDR, or shaders cause a wrong downmix?

Not ordinarily. Hardware decoding, HDR processing, and shaders operate on video. They may coincide with an HDMI device change or a profile that also modifies audio, but they do not normally calculate the audio downmix. Test with --no-config before changing video options.

7.5 Why does a local file work while an online URL sounds wrong?

The online source may supply a different track or channel layout, and yt-dlp may select a format that differs from your local test. Inspect the selected audio track and terminal output. If a direct local sample plays correctly, avoid changing global channel settings solely to compensate for one unusual stream.

7.6 When should I stop troubleshooting mpv?

Stop when a clean mpv test reports the intended output layout and a channel identification sample sounds correct. If the same signal is wrong only through HDMI, a receiver, or a particular system device, continue at that downstream layer. If only one file fails, treat it as a media-file or track-specific issue rather than a global mpv not working problem.