How to Configure MPD Audio Output Through PipeWire

Before you start

This procedure configures a local MPD instance to send audio to PipeWire. It assumes MPD and PipeWire are already installed on the same machine, and that your PipeWire session is running for the user who starts MPD. You need permission to edit the MPD configuration file and restart the MPD service or process afterward.

If you are not sure which configuration file MPD reads, start by checking the main configuration path used by your installation. System service configurations and per-user configurations may use different filenames or locations, so confirm the active file before editing.

Step-by-step instructions

1) Open the MPD configuration file in a plain text editor. Keep a backup copy of the original file before making changes so the procedure can be reversed.

2) Find the audio output configuration section. If an output is already enabled, note its name, device binding, and any format settings before adding a PipeWire output.

3) Add a PipeWire output block. A minimal declaration uses the pipewire output type and a unique name:

audio_output {
    type            "pipewire"
    name            "PipeWire output"
}

4) Decide whether to keep or disable the old output. Having more than one block with the same name can cause a configuration error, so give each enabled output a distinct name.

5) Add optional format controls only when needed. The relevant settings depend on the PipeWire graph and the output device, so start without forcing a sample rate or format. If your setup requires a specific value, check the value accepted by your PipeWire and MPD versions before setting it.

6) Save the file and restart MPD. For a system service, use the service manager; for a user-run process, stop and start it again. Restarting is required because MPD reads its audio output configuration at startup rather than while playing.

Check the output

Open the MPD client you normally use and load a track. If the output appears in the list of available outputs, enable it with the client's output command. Start playback and confirm that audio reaches the expected output device.

The output may be listed even when no stream is active. Playback confirmation is more reliable than an enabled state alone: if the client shows the track progressing but no sound is audible, the stream may be routed to an unexpected device or muted at another level.

Check the active stream in a PipeWire graph tool if one is installed. This helps confirm which application or output device is receiving the MPD stream. Volume, mute, and routing in that tool are separate from MPD playback controls.

Common problems and next steps

If playback fails with a permission or connection message, confirm that MPD is running in the same user session as PipeWire. A system-wide MPD process may not see the PipeWire socket used by your desktop session, even when both services are active.

If the output is visible but silent, inspect routing before changing the MPD configuration. The stream may be connected to the wrong output device or affected by a low input level at another stage. Background noise should not be treated as a configuration failure by itself, because it can come from the recording path or the selected source rather than from the MPD output block.

If MPD reports an unknown type or unsupported option, compare the configuration against the MPD version in use. Older versions may not include the PipeWire output type, while newer versions may reject option names that are no longer valid. Keep the backup file so you can restore the previous output configuration without retyping it.

For a quick isolation test, play a short test signal through the same PipeWire output. This separates an MPD configuration issue from a downstream routing or output device issue.