'''MPD''' ('''m'''usic '''p'''layer '''d'''aemon) is an audio player that has a server-client architecture. It plays audio files, organizes playlists and maintains a music database all while using very few resources. In order to interface with it, a separate [[#Clients|client]] is needed.

+

'''[http://mpd.wikia.com MPD]''' ('''m'''usic '''p'''layer '''d'''aemon) is an audio player that has a server-client architecture. It plays audio files, organizes playlists and maintains a music database all while using very few resources. In order to interface with it, a separate [[#Clients|client]] is needed.

== Installation ==

== Installation ==

=== Stable version ===

=== Stable version ===

The latest stable version of {{Pkg|mpd}} is available in the [[official repositories]].

The latest stable version of {{Pkg|mpd}} is available in the [[official repositories]].

+

=== Git version ===

=== Git version ===

Should users wish to run an experimental version, the [[AUR]] offers several from which to choose. For example, {{AUR|mpd-git}}.

Should users wish to run an experimental version, the [[AUR]] offers several from which to choose. For example, {{AUR|mpd-git}}.

== Setup ==

== Setup ==

−

MPD is able to run globally (settings apply to all users), locally (per user settings), and in multiple instances.

−

The way of setting up mpd depends on the way it is intended to be used.

−

A local configuration may prove more useful on a desktop system than on a system that is used by several people simultaneously.

−

For a comfortable use, it is sensible to provide MPD access to the following files and directories:

+

MPD is able to run locally (per user settings), globally (settings apply to all users), and in multiple instances. The way of setting up mpd depends on the way it is intended to be used: a local configuration may prove more useful on a desktop system, for example.

−

mpd.db # The music database

+

−

mpd.pid # The file where mpd stores its process ID

+

For a proper MPD operation these are the necessary files and directories:

−

mpd.log # mpd logs here

+

−

mpdstate # mpd's current state is noted here

+

* mpd.db - The music database

−

playlists # the folder where playlists are saved into

+

* mpd.pid - The file where mpd stores its process ID

+

* mpd.log - mpd logs here

+

* mpdstate - mpd's current state is noted here

+

* playlists - the folder where playlists are saved into

In order for MPD to be able to play back audio, [[ALSA]], [[PulseAudio]] or [[OSS]] needs to be setup and working.

In order for MPD to be able to play back audio, [[ALSA]], [[PulseAudio]] or [[OSS]] needs to be setup and working.

+

+

=== Local Configuration (per user) ===

+

+

MPD can be configured per user (rather than the typical method of configuring MPD globally). Running MPD as a normal user has the benefits of:

+

+

* A single directory {{ic|~/.mpd}} (or any other directory under {{ic|/home/$USER/}}) that will contain all the MPD configuration files.

+

* Easier to avoid unforeseen read/write permission errors.

+

+

To setup: create a directory for the required files and the playlists; copy the example configuration locally; create all of the requisite files:

+

+

mkdir -p ~/.mpd/playlists

+

cp /usr/share/doc/mpd/mpdconf.example ~/.mpd/mpd.conf

+

touch ~/.mpd/{database,log,state,pid}

+

+

Edit {{ic|~/.mpd/mpd.conf}} and specify the requisite files:

+

+

{{hc|~/.mpd/mpd.conf|

+

music_directory "~/music" # Can keep commented if XDG music dir.

+

playlist_directory "~/.mpd/playlists"

+

db_file "~/.mpd/database"

+

log_file "~/.mpd/log"

+

pid_file "~/.mpd/pid"

+

state_file "~/.mpd/state"

+

}}

+

+

MPD can now be started by typing {{ic|mpd}} on the command line (mpd first searches for {{ic|~/.mpd.conf}}, then {{ic|~/.mpd/mpd.conf}}, and then for {{ic|/etc/mpd.conf}} [there is no support for XDG-config directory {{ic|~/.config/mpd/mpd.conf}}]). To specify the location of the configuration file :

+

+

mpd ~/.config/mpd/mpd.conf

+

+

To start MPD on login add to {{ic|~/.profile}} (or another [[Autostarting#Shells|Autostart file]]):

+

+

# MPD daemon start (if no other user instance exists)

+

[ ! -s ~/.mpd/mpd.pid ] && mpd

+

+

To start with the X.org server add to either [[xprofile]] or [[xinitrc]]. Some DEs ignore these files (GNOME does) and a desktop file must be placed in {{ic|~/.config/autostart/mpd.desktop}}:

+

+

<pre>[Desktop Entry]

+

Encoding=UTF-8

+

Type=Application

+

Name=Music Player Daemon

+

Comment=Server for playing audio files

+

Exec=mpd

+

StartupNotify=false

+

Terminal=false

+

Hidden=false

+

X-GNOME-Autostart-enabled=false</pre>

+

+

==== Autostart with systemd ====

+

+

{{Note|1=As of 2013-03-20 this functionality is still in development ([https://bbs.archlinux.org/viewtopic.php?pid=1208585 forum thread]). However, there is a workaround though it is peculiar as it requires a running X.org server to work.}}

As recommended above, it is best to use MPD as a service per user. In this case, we will use {{ic|~/.mpd/mpd.conf}} and not start mpd.service as a daemon for the whole system and all users.

+

We will NOT use the {{ic|/usr/lib/systemd/system/mpd.service}} which is intended to start the mpd.service as root and for all users.

+

+

{{Note|It is recommended to follow the instructions in the [[Systemd/User]] page fully, and to have your whole session managed by {{ic|systemd --user}}.}}

+

+

If you already enabled it, just disable it first:

+

{{bc| # systemctl disable mpd.service}}

+

+

If you used to start mpd inside your {{ic|~/.xinitrc}}, comment or delete the line

+

{{bc|mpd ~/.mpdconf}}

+

+

Then, edit a new file ~/.config/systemd/user/mpd.service

+

{{hc|~/.config/systemd/user/mpd.service|

+

[Unit]

+

Description &#61; Music Player Daemon

+

+

[Service]

+

ExecStart &#61; /usr/bin/mpd --no-daemon

+

Restart &#61; always

+

+

[Install]

+

WantedBy &#61; default.target

+

}}

+

+

Then, add this line to [[xinitrc|.xinitrc]] before any exec <session-command>

+

{{hc|~/.xinitrc|

+

#run systemd as user instance

+

systemd --user &

+

}}

+

+

Log out, log in your xsession.

+

Let's first check mpd is not running. If yes, just kill it. If not, continue to the next step.

+

{{bc|$ ps -ef &#124; grep mpd}}

+

+

Now, enable and start mpd.service as per user

+

$ systemctl --user enable mpd

+

$ systemctl --user start mpd

+

+

Check the mpd status and see if mpd.service is correctly enabled and started

+

{{bc|$ systemctl --user status mpd}}

+

+

==== Scripted Configuration ====

+

Rasi has written a script that will create the proper directory structure, configuration files and prompt for the location of the user's Music directory; it can be downloaded [http://53280.de/dl/mpdsetup.sh here].

=== Global Configuration ===

=== Global Configuration ===

−

{{Note|For user-specific permissions, change the "user" line above to reflect one of the system users.}}

{{Warning|Users of PulseAudio with a local mpd have to implement a [[Music Player Daemon/Tips and Tricks#Local (with separate mpd user)|workaround]] in order to run mpd as its own user!}}

{{Warning|Users of PulseAudio with a local mpd have to implement a [[Music Player Daemon/Tips and Tricks#Local (with separate mpd user)|workaround]] in order to run mpd as its own user!}}

−

MPD comes with an example configuration file, available at {{ic|/usr/share/doc/mpd/mpdconf.example}}. This file holds an abundance of information on MPD configuration, and holds default mixer values.

+

The default Arch install keeps the setup in {{ic|/var/lib/mpd}} and uses ''mpd'' as default user.

−

−

Normally,{{ic|/etc/mpd.conf}} is created when installing mpd. If not, copy the included example file to {{ic|/etc/mpd.conf}}.

−

# cp /usr/share/doc/mpd/mpdconf.example /etc/mpd.conf

−

−

==== Editing mpd.conf ====

−

The default Arch install keeps the setup in {{ic|/var/lib/mpd}} and uses "mpd" as default user.

Edit {{ic|/etc/mpd.conf}} to reflect as such:

Edit {{ic|/etc/mpd.conf}} to reflect as such:

{{hc|/etc/mpd.conf|

{{hc|/etc/mpd.conf|

−

music_directory "/home/user/music"

+

music_directory "/path/to/music/dir"

playlist_directory "/var/lib/mpd/playlists"

playlist_directory "/var/lib/mpd/playlists"

db_file "/var/lib/mpd/mpd.db"

db_file "/var/lib/mpd/mpd.db"

−

log_file "/var/log/mpd/mpd.log"

+

log_file "syslog"

pid_file "/run/mpd/mpd.pid"

pid_file "/run/mpd/mpd.pid"

state_file "/var/lib/mpd/mpdstate"

state_file "/var/lib/mpd/mpdstate"

user "mpd"

user "mpd"

−

# bind_to_address "127.0.0.1"

−

# port "6600"

}}

}}

−

Now change permissions for mpd to write to {{ic|/var/log/mpd/mpd.log}}, otherwise mpd will returns an error when started. Best is to make the {{ic|/var/log/mpd/mpd.log}} belongs to mpd [[Users and Groups#Group management|user]].

−

# chown -R mpd /var/log/mpd

−

also, run this to create the /run/mpd dir:

−

# systemd-tmpfiles --create

−

To change the volume of audio from mpd independent of other programs, uncomment or add the switch in mpd.conf:

+

We just configured MPD to run as the ''mpd'' user, but {{ic|/var/lib/mpd}} is owned by ''root'' by default, we need to change this so ''mpd'' can write here:

+

# chown -R mpd /var/lib/mpd

+

+

==== Music directory ====

+

MPD needs to have {{ic|+x}} permissions on ''all'' parent directories to the music collection (ie. if it's located outside of {{ic|/var/lib/mpd}}). Thus users will most likely need to remount the music directory under a directory that mpd has access to -- this only applies if running as the 'mpd' user.

Also see [https://bbs.archlinux.org/viewtopic.php?id=86449 this forum thread].

+

+

An additional solution would be to just create a symbolic link into {{ic|/var/lib/mpd/music}}.

+

# mkdir /var/lib/mpd/music

+

# ln -s /path/to/music/dir /var/lib/mpd/music/

+

+

If the music collection is contained under multiple directories, create symbolic links under the main music directory in {{ic|/var/lib/mpd}}. Remember to set permissions accordingly on the directories being linked.

+

+

==== Start MPD ====

+

MPD can be controlled with the ''mpd'' [[daemon]]. The first startup can take some time as MPD will scan your music directory.

+

+

Test everything by starting a client application ({{Pkg|ncmpc}} is a light and easy to use client), and play some music!

+

+

==== Configure audio ====

+

{{Note|Everything should work by default, only change this if it doesn't work for you!}}

+

To change the volume for mpd independent from other programs, uncomment or add this switch in mpd.conf:

{{hc|/etc/mpd.conf|

{{hc|/etc/mpd.conf|

mixer_type "software"

mixer_type "software"

}}

}}

−

Users of [[PulseAudio]] will need to make the following modification:

+

Users of [[ALSA]] will want to have the following device definition, which allows software volume control in the MPD client to control the volume separately from other applications.

{{hc|/etc/mpd.conf|2=

{{hc|/etc/mpd.conf|2=

audio_output {

audio_output {

−

type "pulse"

+

type "alsa"

−

name "pulse audio"

+

name "My Sound Card"

+

mixer_type "software" # optional

}

}

}}

}}

−

Users of [[ALSA]] will want to have the following device definition, which allows software volume control in the MPD client to control the volume separately from other applications.

+

Users of [[PulseAudio]] will need to make the following modification:

{{hc|/etc/mpd.conf|2=

{{hc|/etc/mpd.conf|2=

audio_output {

audio_output {

−

type "alsa"

+

type "pulse"

−

name "My Sound Card"

+

name "pulse audio"

−

mixer_type "software" # optional

}

}

}}

}}

+

==== Changing user ====

+

{{Note|This is only required if you change the user!}}

Changing the group that MPD runs as may result in errors like "output: Failed to open "My ALSA Device"" "[alsa]: Failed to open ALSA device "default": No such file or directory" "player_thread: problems opening audio device while playing "Song Name.mp3""

Changing the group that MPD runs as may result in errors like "output: Failed to open "My ALSA Device"" "[alsa]: Failed to open ALSA device "default": No such file or directory" "player_thread: problems opening audio device while playing "Song Name.mp3""

−

This is because by default MPD runs as member of '''audio''' group and the sound devices under {{Ic|/dev/snd/}} are owned by this group.

+

This is because by default MPD runs as member of '''audio''' group and the sound devices under {{Ic|/dev/snd/}} are owned by this group, so add user {{Ic|mpd}} to group {{Ic|audio}}.

−

+

# gpasswd -a mpd audio

−

===== Music directory =====

−

MPD needs to have {{ic|+x}} permissions on ''all'' parent directories to the music collection (ie. if it's located outside of "mpd" home directory {{ic|/var/lib/mpd}}). By default useradd sets permissions on home directories to {{ic|1700 drwx------}}. Thus users will most likely need to remount the music directory under a directory that mpd has access to -- this only applies if running as the 'mpd' user.

−

−

# mkdir /var/lib/mpd/music

−

# echo "/home/$USER/music /var/lib/mpd/music none bind" >> /etc/fstab

−

# mount -a

−

# rc.d restart mpd

−

See also [https://bbs.archlinux.org/viewtopic.php?id=86449 the forum thread.]

−

−

An additional solution would be to just create a symbolic link into {{ic|/var/lib/mpd/music}}.

−

# mkdir /var/lib/mpd/music

−

# ln -s MUSIC_FOLDER /var/lib/mpd/music/

−

# rc.d restart mpd

−

−

If the music collection is contained under multiple directories, create symbolic links under the main music directory in {{ic|/var/lib/mpd}}. Remember to set permissions accordingly on the directories being linked.

−

−

==== Creating the required files ====

−

Now, having finished configuring MPD, the files and directories for MPD to write in need to be created:

−

−

Create the directories and files specified in {{ic|/etc/mpd.conf}}:

−

# mkdir -p /var/lib/mpd/playlists

−

# touch /var/lib/mpd/{mpd.db,mpdstate}

−

−

Usually the init-script should properly create {{ic|/run/mpd/}} when starting. The deamon will use this directory to create {{ic|mpd.pid}} in it. However, when running mpd as a different user, requires an update to the tmpfiles.d: In {{ic|/usr/lib/tmpfiles.d/mpd.conf}}:

−

Change:

−

d /run/mpd 0755 mpd mpd

−

to:

−

d /run/mpd 0755 ''username'' ''groupname''

−

−

Change the file's permissions so that the daemon can modify them.

−

# chown -R mpd /var/lib/mpd

−

−

==== Create database ====

−

Creating the database is now accomplished via the update feature of the client, for example {{ic|mpc update}}.

To depict when MPD drops its superuser privileges and assumes those of the user set in the configuration, the timeline of a normal MPD startup is listed here:

To depict when MPD drops its superuser privileges and assumes those of the user set in the configuration, the timeline of a normal MPD startup is listed here:

−

# MPD is started on boot by {{ic|/etc/rc.conf}}, by including it in the {{ic|DAEMONS}} array. (Or, this can be done manually each session by running {{ic|rc.d start mpd}} with root privileges).

+

# Since MPD is started as root by systemd, it first reads the {{ic|/etc/mpd.conf}} file.

−

# Since MPD is now started as root, it first reads the {{ic|/etc/mpd.conf}} file.

# MPD reads the user variable in the {{ic|/etc/mpd.conf}} file, and changes from root to this user.

# MPD reads the user variable in the {{ic|/etc/mpd.conf}} file, and changes from root to this user.

# MPD then reads the contents of the {{ic|/etc/mpd.conf}} file and configures itself accordingly.

# MPD then reads the contents of the {{ic|/etc/mpd.conf}} file and configures itself accordingly.

Line 146:

Line 235:

This way, uses of {{ic|~}} in the configuration file point correctly to the home user's directory, and not root's directory.

This way, uses of {{ic|~}} in the configuration file point correctly to the home user's directory, and not root's directory.

It may be worthwhile to change all uses of {{ic|~}} to {{ic|/home/username}} to avoid any confusion over this aspect of MPD's behavior.

It may be worthwhile to change all uses of {{ic|~}} to {{ic|/home/username}} to avoid any confusion over this aspect of MPD's behavior.

−

−

=== Local Configuration (per user) ===

−

MPD does not need to be run globally as a daemon and can rather work per user. The usual method to configure MPD globally is because the listed files and folders in the default configuration file point to directories owned by root (the {{ic|/var}} directory).

−

−

A less used (but perhaps more sensible) method is to make MPD work with files and directories owned by a normal user. Running MPD as a normal user has the benefits of:

−

−

* A single directory {{ic|~/.mpd}} (or any other directory under {{ic|/home/username}}) that will contain all the MPD configuration files.

−

* Easier to avoid unforeseen read/write permission errors.

−

−

{{Note|This approach will not work with multiple users to having access to MPD at the same time.}}

−

−

Begin the setup by creating a directory for the required files and the playlists:

−

−

{{bc|mkdir -p ~/.mpd/playlists}}

−

−

Copy the contents of the default MPD configuration file in {{ic|/usr/share/mpd/mpd.conf.example}} to the target user's home directory:

Rasi has written a script that will create the proper directory structure, configuration files and prompt for the location of the user's Music directory; it can be downloaded [http://karif.server-speed.net/~carnager/mpdsetup.tar here].

MPD (music player daemon) is an audio player that has a server-client architecture. It plays audio files, organizes playlists and maintains a music database all while using very few resources. In order to interface with it, a separate client is needed.

Installation

Stable version

Git version

Should users wish to run an experimental version, the AUR offers several from which to choose. For example, mpd-gitAUR.

Setup

MPD is able to run locally (per user settings), globally (settings apply to all users), and in multiple instances. The way of setting up mpd depends on the way it is intended to be used: a local configuration may prove more useful on a desktop system, for example.

For a proper MPD operation these are the necessary files and directories:

mpd.db - The music database

mpd.pid - The file where mpd stores its process ID

mpd.log - mpd logs here

mpdstate - mpd's current state is noted here

playlists - the folder where playlists are saved into

In order for MPD to be able to play back audio, ALSA, PulseAudio or OSS needs to be setup and working.

Local Configuration (per user)

MPD can be configured per user (rather than the typical method of configuring MPD globally). Running MPD as a normal user has the benefits of:

A single directory ~/.mpd (or any other directory under /home/$USER/) that will contain all the MPD configuration files.

Easier to avoid unforeseen read/write permission errors.

To setup: create a directory for the required files and the playlists; copy the example configuration locally; create all of the requisite files:

MPD can now be started by typing mpd on the command line (mpd first searches for ~/.mpd.conf, then ~/.mpd/mpd.conf, and then for /etc/mpd.conf [there is no support for XDG-config directory ~/.config/mpd/mpd.conf]). To specify the location of the configuration file :

As recommended above, it is best to use MPD as a service per user. In this case, we will use ~/.mpd/mpd.conf and not start mpd.service as a daemon for the whole system and all users.
We will NOT use the /usr/lib/systemd/system/mpd.service which is intended to start the mpd.service as root and for all users.

Note: It is recommended to follow the instructions in the Systemd/User page fully, and to have your whole session managed by systemd --user.

If you already enabled it, just disable it first:

# systemctl disable mpd.service

If you used to start mpd inside your ~/.xinitrc, comment or delete the line

We just configured MPD to run as the mpd user, but /var/lib/mpd is owned by root by default, we need to change this so mpd can write here:

# chown -R mpd /var/lib/mpd

Music directory

MPD needs to have +x permissions on all parent directories to the music collection (ie. if it's located outside of /var/lib/mpd). Thus users will most likely need to remount the music directory under a directory that mpd has access to -- this only applies if running as the 'mpd' user.

If the music collection is contained under multiple directories, create symbolic links under the main music directory in /var/lib/mpd. Remember to set permissions accordingly on the directories being linked.

Start MPD

MPD can be controlled with the mpddaemon. The first startup can take some time as MPD will scan your music directory.

Test everything by starting a client application (ncmpc is a light and easy to use client), and play some music!

Configure audio

Note: Everything should work by default, only change this if it doesn't work for you!

To change the volume for mpd independent from other programs, uncomment or add this switch in mpd.conf:

/etc/mpd.conf

mixer_type "software"

Users of ALSA will want to have the following device definition, which allows software volume control in the MPD client to control the volume separately from other applications.

Changing user

Note: This is only required if you change the user!

Changing the group that MPD runs as may result in errors like "output: Failed to open "My ALSA Device"" "[alsa]: Failed to open ALSA device "default": No such file or directory" "player_thread: problems opening audio device while playing "Song Name.mp3""

This is because by default MPD runs as member of audio group and the sound devices under /dev/snd/ are owned by this group, so add user mpd to group audio.

# gpasswd -a mpd audio

Timeline of MPD startup

To depict when MPD drops its superuser privileges and assumes those of the user set in the configuration, the timeline of a normal MPD startup is listed here:

Since MPD is started as root by systemd, it first reads the /etc/mpd.conf file.

MPD reads the user variable in the /etc/mpd.conf file, and changes from root to this user.

MPD then reads the contents of the /etc/mpd.conf file and configures itself accordingly.

Notice that MPD changes the running user from root to the one named in the /etc/mpd.conf file.
This way, uses of ~ in the configuration file point correctly to the home user's directory, and not root's directory.
It may be worthwhile to change all uses of ~ to /home/username to avoid any confusion over this aspect of MPD's behavior.

Multi-mpd setup

Useful if running an icecast server.

For a second MPD (e.g., with icecast output to share music over the network) using the same music and playlist as the one above, simply copy the above configuration file and make a new file (e.g., /home/username/.mpd/config-icecast), and only change the log_file, error_file, pid_file, and state_file parameters (e.g., mpd-icecast.log, mpd-icecast.error, and so on); using the same directory paths for the music and playlist directories would ensure that this second mpd would use the same music collection as the first one e.g., creating and editing a playlist under the first daemon would affect the second daemon as well. Users do not have to create the same playlists all over again for the second daemon. Call this second daemon the same way from ~/.xinitrc above. (Just be sure to have a different port number, so as to not conflict with the first mpd daemon).