mpd

Start MPD

$ mpd

$ mpd --no-config

$ mpd --no-daemon

$ mpd --kill

mpd [options] [config_file]

--help
    Displays help information and exits.

--version
    Displays version information and exits.

--no-daemon
    Prevents mpd from detaching from the console; runs in the foreground.

--kill
    Sends a SIGTERM signal to a running MPD instance, typically used to stop it gracefully.

--verbose
    Increases the verbosity of log messages output to stdout/stderr.

--stdout
    Directs log messages to standard output instead of a configured log file.

--stderr
    Directs log messages to standard error instead of a configured log file.

config_file
    Specifies an alternative path to the configuration file. Defaults to ~/.config/mpd/mpd.conf or /etc/mpd.conf.

mpd (Music Player Daemon) is a flexible, server-side application for playing audio files.

It runs as a daemon in the background, managing a library of music files and playing them according to commands received from client applications. This daemon/client architecture allows users to control music playback remotely from various devices and interfaces (e.g., desktop clients, mobile apps, command-line tools).

Key features include gapless playback, support for various audio formats (FLAC, MP3, Ogg Vorbis, etc.), streaming capabilities, and a robust playlist management system. mpd aims to be resource-efficient and provide a stable, continuous music playback service, independent of the graphical environment.

mpd is a daemon; it typically runs in the background without a direct user interface. Interaction requires a separate client application. Proper configuration via mpd.conf is crucial for its operation, including music directory, audio output, and network settings. By default, it might listen on localhost, requiring specific configuration for remote access if you intend to control it from another machine.

MPD operates on a strict client-server model. The mpd daemon handles all music playback, library management, and streaming. Clients (like mpc, ncmpcpp, graphical clients, or mobile apps) connect to the daemon, send commands (e.g., play, pause, add to playlist), and receive status updates. This separation allows for headless server setups, remote control, and multiple clients accessing the same music server simultaneously.

The behavior of mpd is primarily controlled by its configuration file, typically mpd.conf. This file specifies critical parameters such as the directories containing music files (music_directory), playlists (playlist_directory), database (db_file), log file (log_file), and crucial audio output settings (audio_output section, defining ALSA, PulseAudio, or other outputs). Correctly configuring this file is essential for MPD to function as intended.

MPD was initially developed by Warren Woodford, with its first public release appearing around 2003. It was created to provide a lightweight, stable, and network-transparent music playback solution, addressing limitations of existing players that were often tied to graphical environments or lacked robust remote control capabilities. Over the years, it has gained significant popularity within the Linux community for its flexibility, extensibility, and stable daemon architecture, becoming a de-facto standard for server-side music management.

mpc(1), ncmpcpp(1), mpd.conf(5), systemctl(1)