Upmpdcli: MPD UPnP Renderer Front-End

upmpdcli is not audited for security issues, and, as far as I know, it may be full of exploitable bugs. Do not run it on an Internet-facing host.

See the man page for command line details. In most situations, upmpdcli will be run as follows:

The -D option tells upmpdcli to fork and run in background. The -c option specifies a configuration file.

The configuration file has a simple name = value format.

The configuration parameters can be set from the command line, a configuration file, or the environment in this order of priority. It would be rather confusing to use a mix of methods, so you should probably chose one. Some less common parameters can only be set in the configuration file.

All parameters have defaults, and a typical installation needs no modification of the configuration file. If several instances of upmpdcli run on the same network, you will want to give them distinct names (friendlyname parameter). The other parameters are only useful in special situations.

The following parameters can be set:

iconpath note: the UPnP protocol has provisions for a renderer to send the URL to a descriptive icon as part of the device description. The icon to use can be set using the iconpath configuration file parameter. Due to current (and probably permanent) upmpdcli limitations, the image file must be a 64x64 32 bits-per-pixel png file.

The support for ohMedia services (play queue managed by the player instead of on the control point) is activated by default as of release 0.8.0, only an explicit option will turn it off.

The previous version default was set to off in the software, and on in the configuration file. As the configuration file is not usually overwritten during an upgrade, if you are upgrading to 0.7.x from an earlier version and you want to enable the services, you need to set the option in the configuration file.

upmpdcli will try to change its uid to user upmpdcli if it is started by root. It will refuse to run if the user does not exist.

If started by root, upmpdcli will also write its process id to /var/run/upmpdcli.pid.

There are boot-time startup scripts in the debian/ directory inside the source tree (for Debian/Ubuntu/Mint/Raspbian etc.). There is also a systemd service file under systemd/ (for Fedora et al.).

The boot scripts are installed by the pre-built packages, so will just have to edit the configuration file after installing them, all the rest should just work.

For building from source, you will need a recent C++ compiler (C++11), and the development packages for libupnp version 1.6, libcurl, libmpdclient, and libexpat.

If you are using the source from Github, you will also need the autoconf/automake/libtool trio. Use the autogen.sh script to set things up.

The libupnpp library, which used to be part of upmpdcli, has been separated, and you need to build this first.

So you need to either clone two github repositories: https://github.com/medoc92/libupnpp and https://github.com/medoc92/upmpdcli, or download the corresponding release tar files from the the download area

Once the source is extracted, the procedure is standard and there are currently no specific configure options:

Which you should apply first to the libupnpp source, then to upmpdcli.