Music Player Daemon (Italiano)

From ArchWiki
Revision as of 20:48, 30 December 2010 by Morbin (talk | contribs) (Creata pagina italiana)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Tango-preferences-desktop-locale.pngThis article or section needs to be translated.Tango-preferences-desktop-locale.png

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in Talk:Music Player Daemon (Italiano)#)
Nota: Questo articolo è in fase di traduzione. Seguite per ora le istruzioni della versione inglese.

MPD (music player daemon) is an audio player that has a server-client architecture. MPD runs in the background as a daemon, manages playlists and a music database, and uses very few resources. In order to interface with it, you need a separate client. More information can be found on their website.

Please have a look at the official page for setup and troubleshooting instructions, the main developer called our wiki page in its current state "full of symptom killers", hence the official pages should contain better instructions.

Daemon install procedure

Install with pacman:

# pacman -S mpd

Setup instructions

For more information about MPD configuration visit

Timeline of MPD's behavior on a typical working setup

  1. MPD is started on boot by Template:Filename, by including it in the Template:Codeline array. (Or, this can be done manually each session by running Template:Codeline with root privileges).
  2. Since MPD is now started as root, it first reads the Template:Filename file.
  3. MPD reads the user variable in the Template:Filename file, and changes from root to this user.
  4. MPD then reads the contents of the Template:Filename file and configures itself accordingly.

Notice that MPD changes the running user from root to the one named in the Template:Filename file. This way, uses of Template:Codeline 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 Template:Codeline to Template:Codeline to avoid any confusion over this aspect of MPD's behavior.

A clean configuration file

  • As root, check if Template:Filename exists and delete the file if it does. This is safe.

Mpd comes with an example configuration file, available at Template:Filename. This file holds an abundance of information on MPD configuration, and holds default mixer values you can simply uncomment.

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

(/usr/share/doc/mpd/mpd.conf.example is good for userspace setup)

Never put this file in the user's directory like some tutorials suggest. This would complicate things and most of the time doing this is useless (notice you're reading a quick installation howto). If you previously created a Template:Filename file in your home, remove it now. This is important to prevent conflicts. When placing it in Template:Filename, like we do here, MPD will be able to run as a daemon at boot. Otherwise, a script would be needed to run MPD after the user has logged (like kdm or Template:Filename) or it would require a manual move each time. For a single music collection, the method used here is simply better, even while the collection is shared to multiple users. Also, don't be afraid about root privileges: even while MPD runs as a daemon, it never completely runs as root since it automatically drops its root privileges after execution.

Sound setup correctly

To make audio output actually work ensure that you have setup audio card and mixer correctly. See ALSA. Do not forget to unmute the required channels in alsamixer, raise the volume and save changes with alsactl store. See Template:Filename if it still doesn't work.

Make sure your card can do hardware mixing (most of them can, including onboard audio). Or else this could cause problems with multiple sound playback. For example, this can prevent Mplayer from playing back sound while the mpd daemon is running, returning an audio error message stating the device is busy.

Software mixing

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


Editing Template:Filename

Keeps the setup in /var and uses "mpd" as default user instead of cluttering up ~/. This is the way the arch package is installed.

Edit Template:Filename to reflect as such.


Read steps below carefully, permissions need to be set correctly.

  • Now as root create the files you specified in Template:Filename, if directories do not exist, create those as well. This is not required if you use the defaults in the arch package.
  • If your music collection is contained under multiple dir. you can make symbolic link under /var/lib/mpd then set 'music_dir' in mpd.conf to the directory holding the symbolic links. Remember to set permissions accordingly on the directories being linked.
  • Creating the database is now accomplished via the update feature of the client, for example if you were running ncmpcpp you would just enter 'u'.
    • The previous method, creating the MPD database as root (# mpd --create-db), is deprecated.

Alternative setup

MPD need not be started with root permissions. The only reason why MPD needs to be started as root (by being called from Template:Filename) is because the default files and folders in the default configuration file points to directories owned by root (the /var directory). A less common, but perhaps more sensible, approach is to make MPD work with files and directories owned by a normal user. Running MPD as a normal user has several advantages:

  1. You can easily have a single directory ~/.mpd (or any other directory under /home/username) for all MPD configuration files
  2. No read/write permission errors
  3. More flexible calls to MPD by using Template:Filename instead of including 'mpd' in the Template:Filename DAEMONS array.

The following steps shows how to run MPD as a normal user. Note: this approach will not work if you want multiple users to have access to MPD.

# this starts mpd as normal user
mpd /home/username/.mpd/mpd.conf
Note: that you don't have to put a "&" at the end of the line here, since MPD will automatically daemonize itself.

Lastly, delete the entry 'mpd' from your DAEMONS array in Template:Filename, as you are not running it as root anymore.

Quick setup

The fastest way to do set up the structure is to do this:

$ mkdir -p ~/.mpd/playlists && touch ~/.mpd/database && cp /usr/share/doc/mpd/mpdconf.example ~/.mpd/mpd.conf

Then edit mpd.conf to your liking. Beware that you must uncomment the db_file entry if you do edit mpd.conf.

Then, to run it:

$ mpd ~/.mpd/mpd.conf

Multi-mpd setup

Useful if you you want to run for example an icecast server. If you want a second MPD daemon (e.g., with icecast output to share music over the network) to use the same music and playlist as the one above, simply copy the above configuration file and make a new file (e.g., Template:Filename), and only change the log_file, error_file, pid_file, and state_file parameters (e.g., Template:Filename, Template:Filename, and so on); using the same directory paths for the music and playlist directories would ensure that this second mpd daemon would use the same music collection as your first one (e.g., creating and editing a playlist under the first daemon would affect the second daemon as well, so that you don't have to create the same playlists all over again for the second daemon). Then, call this second daemon the same way from your Template:Filename above. (Just be sure to have a different port number, so as to not conflict with your first mpd daemon).

Client install procedure

Install a client program for MPD. Popular options are:

  • mpc – Command Line Client (you'll probably want this one no matter what)
# pacman -S mpc
# pacman -S ncmpc
# pacman -S ncmpcpp
  • dmpc – Dmenu-based MPC client with a playlist manager and state-saving on playlist changes AUR package of dmpc
Install dmpc from the AUR.
Install pmus from the AUR.
# pacman -S ario
# pacman -S sonata
# pacman -S gmpc
# pacman -S qmpdclient

Extra stuff scrobbling

To scrobble your songs to using MPD there are several alternatives.


mpdscribble is another daemon, but is only available in the AUR. This is arguably the best alternative, because it's the semi-official MPD scrobbler and uses the new "idle" feature in MPD for more accurate scrobbling. Also, you don't need root access to configure it, because it doesn't need any changes to /etc at all. Visit the official website for more information.

To install mpdscribble, just install it from the AUR and do the following (not as root):

 host = <your mpd host> # optional, defaults to $MPD_HOST or localhost
 port = <your mpd port> # optional, defaults to $MPD_PORT or 6600
 log = ~/.mpdscribble/mpdscribble.log
 journal = ~/.mpdscribble/mpdscribble.cache
 verbose = 2
 sleep = 1
 musicdir = <your music directory>
 proxy = <your proxy> # optional, e. g. http://your.proxy:8080, defaults to none

 # section, comment if you don't use
 url = # optional
 username = <your username>
 password = <your password> # md5sum also possible: echo -n PASSWORD | md5sum | cut -f 1 -d " "

 # section, comment if you don't use
 url =
 username = <your username>
 password = <your password>
pidof mpdscribble >& /dev/null
if [ $? -ne 0 ]; then
  mpdscribble &

Sonata & Ario

The easiest way, if you don't care about having to have a program window open all the time, is using Sonata or Ario which are graphical frontends to MPD. They have built-in support for scrobbling in their preferences. A downside of this is that Sonata doesn't cache your songs if for some reason you don't happen to have an Internet connection at the time of playing.


lastfmsubmitd is a daemon which is available in the "community" repository. To install it, first edit Template:Filename and add both Template:Codeline and Template:Codeline to the Template:Codeline array in Template:Filename. playback with lastfmproxy

lastfmproxy is a python script that streams a music stream to another media player. To setup, install lastfmproxy from the AUR and then edit Template:Filename. If you plan to only stream to MPD on the same host, just edit the login info.

Note: Since it installs to a read only directory but it requires read/write access for features like saving previously listened to stations, it would be wise to copy Template:Filename to your home directory.

Start lastfmproxy with Template:Codeline and visit http://localhost:1881/ in your web browser. To add a station navigate to http://localhost:1881/ followed by the lastfm:// url. Example: http://localhost:1881/lastfm://globaltags/punk . Navigate back to http://localhost:1881/ and download the m3u file by selecting the Start Listening link. Simply add it to your music library path.

Never play on start

Method 1

If you don't want MPD to always play on your system start, but yet you want to preserve the other state information, add the following lines to your Template:Filename file:

   stat_busy "Starting Music Player Daemon"
   # always start in paused state
   awk '/^state_file[ \t]+"[^"]+"$/ {
       match($0, "\".+\"")
       sfile = substr($0, RSTART + 1, RLENGTH - 2)
   } /^user[ \t]+"[^"]+"$/ {
       match($0, "\".+\"")
       user = substr($0, RSTART + 1, RLENGTH - 2)
   } END {
       if (sfile == "")
       if (user != "")
               sub(/^~/, "/home/" user, sfile)
       system("sed -i \x27s|^\\(state:[ \\t]\\{1,\\}\\)play$|\\1pause|\x27 \x27" sfile "\x27")
   }' /etc/mpd.conf
   /usr/bin/mpd /etc/mpd.conf &> /dev/null

This will change the player status to "paused", if it was stopped while playing. Next, you want this file to be preserved, so MPD updates won't erase this edit. Add (or edit) this line to your Template:Filename:

NoUpgrade = etc/rc.d/mpd

Method 2

Another simpler method, would be to add mpd to your Template:Filename deamons array and add Template:Codeline or Template:Codeline to Template:Filename and to Template:Filename. (Remember you must have mpc installed to use this method).

Adding only the order in Template:Filename cannot assure that mpd will play absolutely nothing, since there may be a delay before the stop command is executed. On the other hand, if you only add the order to Template:Filename, that will assure that mpd won't play at all, as long as you properly shutdown your system. Even though they are redundant, adding it to Template:Filename would serve as a safety for those, presumably, rare occasions when you do not shutdown the system properly.

Method 3

The general idea between this method is to ask mdp to pause music when user logs out so that during next restart, mdp will stick to that "pause" state. Sending such command can be achieve using mpc, the command line interface to MPD:

pacman -S mpc

GDM users can then add the next line to /etc/gdm/PostSession/Default (be sure to add it before "exit 0"):

/usr/bin/mpc pause

Non-GDM users can use their own login manager's method to launch the line at logout.


Sometimes, when you use other audio output, e.g: some web pages containing Flash applets, MPD cannot reproduce anything anymore (until you restart). The error looks something like: (if you search the file Template:Filename)

Error opening alsa device "hw:0,0": Device or resource busy

And here is the solution (dmix saving our life again). Apply these lines in your Template:Filename:

audio_output {
        type                    "alsa"
        name                    "Sound Card"
        options                 "dev=dmixer"
        device                  "plug:dmix"

And then restart with Template:Codeline.

Searching on Internet I found the reason for why that happens in Gentoo's wiki:

  • The sound card does not support hardware mixing (uses dmix plugin)
  • An application does not work with ALSA with it's default settings

For a detailed description, it is recommended to take a look at this link. There you can find an example asound.conf which worked for me right out of the box.

High CPU usage with ALSA

When using MPD with ALSA, users may experience MPD taking up lots of CPU (around 20-30%). This is caused by most sound cards supporting 48kHz and most music being 44kHz, thus forcing MPD to resample it. This operation takes lots of CPU cycles and results into high usage.

For most users the problem should be solved by telling MPD not to use resampling by adding Template:Codeline into audio_output-part of Template:Filename. This will degrade quality slightly, however.

Example from Template:Filename:

audio_output {
   type			"alsa"
   name			"My ALSA Device"
   auto_resample		"no"

Although it may not give as drastic a speedup, enabling mmap may speed things up:

audio_output {
   type			"alsa"
   name			"My ALSA Device"
   use_mmap		"yes"

Some users might also want to tell dmix to use 44kHz as well. More info about tuning performance of your MPD can be found from: MPD wiki

Control MPD with lirc

There are already some clients designed for communications between lircd and MPD, however, as far as the practical use, they aren't very useful since their functions are limited.

It's recommended to use mpc with irexec. mpc is a command line player which only sends the command to MPD and exits immediately, which is perfect for irexec, the command runner included in lirc. What irexec does is that it runs a specified command once received a remote control button.

First of all, please setup your remotes as referred to the Lirc article.

Edit your favored lirc startup configuration file, default location is Template:Filename.

Fill the file with the following pattern:

     prog = irexec
     button = <button_name>
     config = <command_to_run>
     repeat = <0 or 1>

An useful example:

## irexec
     prog = irexec
     button = play_pause
     config = mpc toggle
     repeat = 0

     prog = irexec
     button = stop
     config = mpc stop
     repeat = 0
     prog = irexec
     button = previous
     config = mpc prev
     repeat = 0
     prog = irexec
     button = next
     config = mpc next
     repeat = 0
     prog = irexec
     button = volup
     config = mpc volume +2
     repeat = 1
     prog = irexec
     button = voldown
     config = mpc volume -2
     repeat = 1
     prog = irexec
     button = pbc
     config = mpc random
     repeat = 0
     prog = irexec
     button = pdvd
     config = mpc update
     repeat = 0
     prog = irexec
     button = right
     config = mpc seek +00:00:05
     repeat = 0
     prog = irexec
     button = left
     config = mpc seek -00:00:05
     repeat = 0
     prog = irexec
     button = up
     config = mpc seek +1%
     repeat = 0
     prog = irexec
     button = down
     config = mpc seek -1%
     repeat = 0

There are more functions for mpc, run Template:Codeline for more info.

Control MPD with bluetooth phone

You can also control MPD (to a certain extent) using a bluetooth enabled phone. You need to do the following:

  • install remuco -- a wireless remote control for several Linux media players (aur)
  • transfer remuco client -- jar/jad files from Template:Filename to your phone and install it
  • run Template:Codeline (as current user)
  • run remuco on your phone, define a new bluetooth remuco connection (pair first if you haven't done this previously) and explore its capabilities

More information about remuco including troubleshooting to be found at its homepage

MPD & PulseAudio

Edit Template:Filename, and uncomment the audio_output section for the type "pulse". The server and sink lines of it should be commented unless you know what you're doing.

Then, add the mpd user (and yours if you haven't done so already) to the necessary pulse groups. The pulse-access group should be sufficient but you may want to add pulse-rt as well. The group "pulse" doesn't appear to be necessary.

# gpasswd -a mpd pulse-access
# gpasswd -a mpd pulse-rt

Lastly, you may or may not need to copy Template:Filename from your current (pulse working) user's dir to your mpd user's home directory. It is likely to be Template:Filename if you followed the first part of this wiki. This would probably only allow your current user to listen in on MPD's pulse. You may consider running pulse system-wide if that's insufficient.


Autodetection failed

During the start of MPD, it tries to autodetect your set-up and configure output and volume control accordingly. Though this mostly goes well, it will fail for some systems. It may help to tell MPD specifically what to use as output and mixer control. If you copied Template:Filename over from Template:Filename as mentioned above, you can simply uncomment:

Example for alsa output type:

audio_output {
	type			"alsa"
	name			"My ALSA Device"
	device			"hw:0,0"	# optional
	format			"44100:16:2"	# optional

Example for alsa mixer:

mixer_type			"alsa"
mixer_device			"default"
mixer_control			"PCM"

Note: in case of permission problems when using ESD with MPD run this as root:

# chsh -s /bin/true mpd

Executable permissions

Warning: This is not good security practice and may be unnecessary.

MPD needs to have +x permissions on ALL parent directories to your music collection (ie. if it's located outside of "mpd" home directory /var/lib/mpd). By default useradd sets permissions on home dir to 1700 drwx------. So if you're like me you will need to change permissions of /home/user. Example... my music collection is located /home/user/music.

# chmod a+x /home/$USER
# chmod -R a+X /home/$USER/music

Alternative solution

An alternative solution would be to use your group to share a selection of files, among them your music library. First remove all permissions for the group then add group permissions to read and execute home and music.

# chmod -R g-rwx /home/$USER
# chmod g+rx /home/$USER
# chmod -R g+rX /home/$USER/music

Another alternative solution

Another alternative is to remount the music directory under a directory that mpd has access to. This does not entail the same security risks as modifying the permissions on one's home directory.

# mkdir /var/lib/mpd/music
# echo "/home/$USER/music /var/lib/mpd/music none bind" >> /etc/fstab
# mount -a
# /etc/rc.d/mpd restart

And that should fix the problem. See also the forum thread.

Avoiding timeouts

To get rid of timeouts (i.e. when you paused music for long time) in gpmc and other clients uncomment and increase Template:Codeline option in Template:Filename.

If files and/or titles are shown in wrong encoding, uncomment and change Template:Codeline and Template:Codeline options. Note that you cannot set encoding for ID3 v2 tags. To workaround this you may use external tag readers.

If you want to use another computer to control MPD over a network, the Template:Codeline option in Template:Filename will need to be set to either your IP address, or Template:Codeline if your IP address changes frequently. Remember to add mpd to the Template:Filename file to enable external access.

With the latest version of MPD (0.15), built-in httpd streaming is now available.

To activate this feature, you'll just need to add a new output of type httpd in Template:Filename:

audio_output {
          type   "httpd"
          name   "What you want"
          encoder "lame"     # vorbis or lame supported
          port    "8000"
          bitrate  "128"
          format   "44100:16:2"  # change 2 to 1 for mono

Restart the mpd deamon and, from another computer, simply load the stream as any other url.

$ mplayer http://<server's IP>:8000
Note: You must open the port on your router / firewall for the stream to be connectible to from another computer.

Most players (i.e. vlc or xmms2) should also be able to load the stream via their "add url..." menu option.

This is a nice clean way to replace your current icecast setup with something natively supported within MPD.

mpd --create-db hangs

This is a common error that's caused by corrupt mp3 tags. Here is an experimental way to solve this issue. Requirements:

  • kid3
  • easytag

This method is very tedious, especially with a huge database. Just as a baseline it took 2.5h to fix a 16Gb DB.

Easy Tag

The purpose of easytag here is that easytag detects the error in the tags, but like MPD it hangs and dies. The trick here is that easy tags actually tells you what file is causing the problem on the status bar. Before starting easytag make sure to have a terminal close to be ready to kill easy tag to avoid a hang. Once you are ready, on the tree view select the directory where all your music is located. By default easytag starts to search all subdirectories for mp3 files. Once you notice that easytag stopped scanning for songs, make note of the culprit and kill easytag.


Here's where kid3 comes in handy. With kid3 go to the offending song and rewrite one of the tags. then save the file. This should force kid3 to rewrite the whole tag again fixing the problem with MPD and easy tag hanging.

Repeat this procedure until your music library is done.

Cannot connect to mpd: host "localhost" not found: Temporary failure in name resolution

Cannot connect to MPD (with ncmpcpp), if you are disconnected from network. Solution is disable IPv6 or add line to /etc/hosts

::1 localhost.localdomain localhost

Port 6600 already in use

MPD needs to bind to port 6600 and cannot start if it's already in use. The most common reason for this is that the user has started MPD once and then subsequently tried mpd --create-db. New MPD behavior is the --create-db option also attempts to start the daemon; if it's already been started, this will fail. If this is the case, try the following:

$ mpd --kill
$ mpd --create-db

A more brute-force approach:

$ killall mpd
$ mpd --create-db
Note: If you typically run MPD as root, you will need to run the above commands as root.

In the git version of MPD, --create-db is completely deprecated. The database will be created automagically on first run and can subsequently be updated via your client (i.e. mpc update). Eventually, inotify support will offer fully automatic database updates as you add content to your music folders

If port 6600 is tied up for some other reason, one can use the following command to find the offending process:

# netstat -tulpan | grep 6600

This will list IP:Port and the process name holding the connection (root privileges are required to see all processes).

Crackling sound with some audio files

This is usually a playback speed problem and can be fixed by uncommenting the audio_output_format line in:


This is usually a sane value for most mp3 files.

daemon: cannot setgid for user "mpd": Operation not permitted

The error is stating that the user starting the process (you) does not have permissions to become another user (mpd) which the configuration has told that process to run as.

To solve the issue, simply start mpd as root.

su -c "/etc/rc.d/mpd start"


sudo /etc/rc.d/mpd start

External links