To request this task, one of the MPD clients must be used. In order to build the database file, MPD must scan into the music_directory defined above. MPD can now be started (an optional custom location for the configuration file can be specified): If playlists are enabled in the configuration, the specified playlist directory must be created: #sticker_file "~/.config/mpd/sticker.sql" #playlist_directory "~/.config/mpd/playlists" # Uncomment to enable the functionalities # Uncomment to refresh the database whenever files in the music_directory are changed # The music directory is by default the XDG directory, uncomment to amend and choose a different directory # If running mpd using systemd, delete this line to log directly to systemd. ~/.config/mpd/mpd.conf # Recommended location for database Then edit the configuration file in order to specify the required and optional files and directories: The user must have read write access to this directory. $ cp /usr/share/doc/mpd/mpdconf.example ~/.config/mpd/mpd.confĪ 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. To build the user configuration, the MPD configuration example included in the package is a good starting point, copy it using the following lines: We will assume here $XDG_CONFIG_HOME equals the default of ~/.config. ![]() In user mode, the configuration is read from $XDG_CONFIG_HOME/mpd/mpd.conf. Avoiding unforeseen directory and file permission errors.Ĭonfigure the location of files and directories.Regrouping into one single directory ~/.config/mpd/ (or any other directory under $HOME) all the MPD configuration files.Running it as a normal user has the benefits of: music_directory - The directory that MPD scans for music.playlist_directory - The directory where playlists are saved into.state_file - MPD's current state is noted here.pid_file - The file where MPD stores its process ID.These are some of the most commonly used configuration options: /etc/mpd.conf in system-wide configuration.~/.config/mpd/mpd.conf in per-user configuration mode, this is the first location searched,. ![]() In short, the two common locations used are: 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). The #Audio configuration section thereafter describes the parameters needed for ALSA, PulseAudio or PipeWire. In order for MPD to be able to playback audio, ALSA, optionally with PulseAudio or PipeWire, must be set up and working. The system-wide setup might be better suited for a always-on audio server with multiple users but a shared MPD instance. The way of setting up MPD depends on the way it is intended to be used: a local per-user configuration is easier to set up and may prove more adapted on a desktop system. Also it is possible to run multiple instances of MPD in a #Multi-MPD setup. MPD is able to run in #Per-user configuration or #System-wide configuration mode (settings apply to all users). Install the mpd package, or mpd-git AUR for the development version. In order to interface with it, a separate client is needed. It plays audio files, organizes playlists and maintains a music database, all while using very few resources. MPD (music player daemon) is an audio player that has a server-client architecture.
0 Comments
Leave a Reply. |