Mpd linux ��� ���

Music Player Daemon

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.

Contents

Installation

Install the mpd package, or mpd-git AUR for the development version.

Configuration

MPD is able to run in #Per-user configuration or #System-wide configuration mode (settings apply to all users). Also it is possible to run multiple instances of MPD in a #Multi-MPD setup. The way of setting up MPD depends on the way it is intended to be used: a local per-user configuration is easier to setup and may prove more adapted on a desktop system. The system-wide setup might be better suited for a always-on audio server with multiple users but a shared MPD instance.

In order for MPD to be able to playback audio, ALSA, optionally with PulseAudio, must be setup and working. The #Audio configuration section thereafter describes the parameters needed for ALSA or PulseAudio.

MPD is configured in the file mpd.conf(5) which can be located in various paths depending on the setup chosen (system-wide or per-user). In short, the two common locations used are:

/.config/mpd/mpd.conf in per-user configuration mode, this is the first location searched,

/etc/mpd.conf in system-wide configuration.

These are some of the most commonly used configuration options:

• pid_file — The file where MPD stores its process ID
• db_file — The music database
• state_file — MPD’s current state is noted here
• playlist_directory — The folder where playlists are saved into
• music_directory — The folder that MPD scans for music
• sticker_file — The sticker database

Per-user configuration

MPD can be configured per-user. Running it as a normal user has the benefits of:

Regrouping into one single directory

/.config/mpd/ (or any other directory under $HOME ) all the MPD configuration files.

Avoiding unforeseen directory and file permission errors.

Configure the location of files and directories

In user mode, the configuration is read from $XDG_CONFIG_HOME/mpd/mpd.conf . We will assume here $XDG_CONFIG_HOME equals the default of

To build the user configuration, the MPD configuration example included in the package is a good starting point, copy it using the following lines:

A good practice is to use this newly created

/.config/mpd/ directory to store, together with the configuration file, other MPD related files like the database or the playlists. The user must have read write access to this directory.

Then edit the configuration file in order to specify the required and optional files and directories:

If playlists are enabled in the configuration, the specified playlist directory must be created:

MPD can now be started (an optional custom location for the configuration file can be specified):

In order to build the database file, MPD must scan into the music_directory defined above. To request this task, one of the MPD clients must be used. For example with mpc the command is:

or alternatively one can set the option auto_update to «yes» in the configuration to refresh the database whenever files are changed in music_directory .

Audio configuration

If ALSA is used, autodetection of the default device should work out of the box without any particular setting. If not, the syntax for ALSA audio output definition is provided thereafter; the required name parameter specifies a unique name for the audio output. The exact device as displayed using aplay —list-pcm from the package alsa-utils can optionally be indicated with the device option.

Users of PulseAudio will need to make the following modification:

Starting with version 0.23 of MPD, PipeWire support can be configured:

Autostart with systemd

The mpd package provides a user service file. The service starts the process as user, there is no need to change permission nor use the user and group variables in the MPD configuration file.

Start/enable the user unit mpd.service (i.e. with the —user flag).

/.config/mpd/mpd.conf , see systemd#Editing provided units if you would like to indicate a custom configuration file path.

Autostart on tty login

To start MPD on login add the following to

Scripted configuration

The mpd-configure tool creates a MPD configuration optimized for bit perfect audio playback, without any resampling or conversion, using the ALSA interface hardware address (hw:x,y).

System-wide configuration

The default /etc/mpd.conf keeps the setup in /var/lib/mpd which is assigned to user as well as primary group MPD.

Music directory

The music directory is defined by the option music_directory in the configuration file /etc/mpd.conf .

MPD needs to have execute permission on all parent directories of the music collection and also read access to all directories containing music files. This may conflict with the default configuration of the user directory, like

/Music , where the music is stored.

While there are several solutions to this issue, one of these should be most practical:

• Switch to the #Per-user configuration mode instead
• Add the mpd user to the user’s group and grant group execute permission to the user directory. This way the mpd user has permission to open the user directory:

• Store the music collection in a different path, either:
  • by moving it entirely,
  • with a bind mount,
  • or with Btrfs#Subvolumes (you should make this change persistent with an entry to /etc/fstab ).

The MPD configuration file must define only one music directory. 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.

To exclude a file — or files — from the update, create a file called .mpdignore in its parent directory. Each line of that file may contain a list of shell wildcards. Matching files in the current directory and all subdirectories are then excluded from subsequent updates.

Start with systemd

MPD can be controlled with mpd.service using systemd. 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!

Socket activation

mpd provides a mpd.socket unit. If mpd.socket is enabled (and mpd.service is disabled), systemd will not start MPD immediately, it will just listen to the appropriate sockets. Then, whenever an MPD client attempts to connect to one of these sockets, systemd will start mpd.service and transparently hand over control of these ports to the MPD process.

If you prefer to listen to different UNIX sockets or network ports (even multiple sockets of each type), or if you prefer not to listen to network ports at all, edit the mpd.socket unit appropriately and modify /etc/mpd.conf to match the configuration (see mpd.conf(5) for details).

User id startup workflow

MPD should never run as root, you may use the user option in the configuration to make MPD change its user id after initialization. Do not use this option if you start MPD as an unprivileged user. To describe how MPD drops its superuser privileges and switch to those of the user set in the configuration, the steps of a normal MPD startup are listed thereafter:

1. Since MPD is started as root by systemd, it first reads the /etc/mpd.conf file.
2. MPD reads the user variable in the configuration, and changes from root to this user.
3. MPD then reads the rest of the configuration file and configures itself accordingly. Uses of

in the configuration file points to the home user’s directory, and not root’s directory.

Multi-MPD setup

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 uses 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 — but be sure to have a different port number, avoiding a conflict with the first MPD daemon.

Satellite setup

The method described in #Running an Icecast server works, but at least in theory could lead to issues with the database, when both MPD instances try to write to the same database file concurrently. MPD has a satellite mode where one instance can receive the database from an already running MPD instance.

In your config-icecast add this, where host and port reflect your primary MPD server:

Clients

A separate client is needed to control MPD. See a long list of clients at the mpd website. Popular options are:

Источник

Ubuntu Documentation

Music Player Daemon (MPD) is a flexible, powerful, server-side application for playing music. Through plug-ins and libraries it can play a variety of sound files while being controlled by its network protocol.

Installing with the GUI

Start Synaptic Package Manager ( System > Administration > Synaptic Package Manager ) and in the search box enter mpd. Mark the package mpd for installation and client if required. In this guide Sonata is used as an example.

The following packages should be marked for installation:

• mpd
• sonata

Click Apply.

Installing with the command line (advanced users)

$ sudo apt-get update

$ sudo apt-get install mpd sonata

Configuring MPD to run as a system service

By default MPD is configured to run as a daemon to is available to all users.

• In the configuration, many of the default options will be what is required; however, there is still some customization needed to be done.

Editing the configuration

Almost all of the default settings in /etc/mpd.conf can be left untouched, but there are some things that you may want to change.

$ sudo nano /etc/mpd.conf

You will need to specify the music directory:

music_directory «/home/user/Music» # or whatever your music is located

The audio controller will need to be defined. First, comment the ALSA section:

Then add Pulse Audio below it (comment out, and define name [optional]):

Sometimes there can be a problem with sound getting processed correctly and uncommenting this line might help:

Bugfix: Giving MPD proper permissions

Unfortunately, by default MPD does not have the proper permissions to access PulseAudio, the default audio setup on most new Ubuntu systems. If MPD plays for you without these steps, then that’s great, but if you can play your songs but no sound is emitted, try the following steps.

What we need to do is add the user mpd to the groups pulse and pulse-access so that it can access the audio system.

$ sudo usermod -aG pulse,pulse-access mpd

MPD starts new pulseserver

Unfortunatly MPD tries to start its own pulseaudio server. So if you still unlucky you could try:

Then you need to allow access. You should install paprefs

Then run it (e.g. alt+f2 and enter paperfs). Click the Network Server tab, then check the Enable network access to local sound devices box, and finally check the Don’t require authentication box. At this point make sure to restart the pulseaudio daemon.

Now you should see MPD in Sound settings Application tab and hear music.

Configuring MPD to run as a user service

MPD doesn’t need to run as a daemon and can be run as a regular program by any user. By doing this, MPD will use the users configurations and has no need for a system-wide configuration (useful if you keep your /home on a separate partition.

First stop the daemon and disable from starting on boot:

* Note: This will probably change as of Ubuntu 11.04 (Natty) the MPD daemon is not yet an upstart service yet.

Create a directory for the mpd files and the playlists:

Copy the MPD configuration file to the home folder:

Create all of the requisite files:

Edit the configuration file to direct to the local MPD files:

The music_directory isn’t required to be specified unless the music directory is in another place besides /home/user/Music.

Comment the user line (unnecessary/unwanted if using as a non-daemon):

Comment out alsa audio_output section, select Pulse section:

Create a desktop file for MPD to have MPD load on log in:

Now the MPD daemon will run in the background and a MPD music client can connect to it; until then mpd can be started by running mpd from the command line.

Bugfix: Pausing loses connection with Pulse server

This is a bug the occurs with Pulse when pausing a track and trying to play it again that the MPD client will show that the track is playing but no sound is heard (skipping to will resume contact with the Pulse sound server, or stopping and playing will as well). This bug effects pulseaudio-1:09.22 and possibly later.

To fix this modify the MPD configuration to use ALSA directly.

In the mpd.confdirect MPD to use ALSA and comment the pulse section if previously specified:

Configuring MPD to stream to an IceCast server

FIXME

MPD (последним исправлял пользователь dani.behzi 2017-02-08 06:24:48)

The material on this wiki is available under a free license, see Copyright / License for details
You can contribute to this wiki, see Wiki Guide for details

Источник