• Home
• Downloads
• Documentation
• Support
• News
• Comments
• lesbonscomptes

An UPnP Audio Media Renderer based on MPD

upmpdcli is a UPnP Media Renderer front-end for MPD, the Music Player Daemon. It supports UPnP gapless track transitions and the OpenHome ohMedia services (including a Radio service to listen to Internet streams). OpenHome is supported by major control points. Its big advantage is a locally managed playlist, meaning that the control point (e.g. your phone) does not need to stay active.

• The program also implements a Media Server providing a gateway for accessing music streaming services, and a local server for audio files. The gateway allows browsing and playing tracks from external or internal streaming services (at the moment: Tidal, Qobuz, HighResAudio, Subsonic). Audio tracks from the streaming services can be played by an upmpdcli instance or by any other local UPnP renderer. All modules are optional and can be activated separately.
• With a supplemental application, upmpdcli implements a Linn Songcast Receiver and Sender. The Songcast Receiver function allows you to implement a well-synchronized multi-room system to which any audio (Spotify, etc.) playing on a Windows or Mac system can be forwarded. The upmpdcli Sender/Receiver function also allows multiroom playing from Linux, including of an external input source.

👁 upmpdcli

upmpdcli is written in C++, open-source, free and licensed under the GPL. It now relies on its own UPnP libraries ( libnpupnp and libupnpp), and a number of other common and reliable libraries (libcurl and libmicrohttpd).

The current version is 1.9.17. See the release notes.

The typical setup is a home network with:

• A UPnP Media Server: e.g. Gerbera (ex. Mediatomb), ReadyMedia (ex. MiniDLNA), MinimServer, or some other commercial product,
• A UPnP Control Point (e.g. Bubble UPnP running on a tablet or phone, Linn Kazoo on a PC/MAC, or upplay for Linux or Windows).
• upmpdcli and MPD running on some Linux device (e.g. a Raspberry Pi hooked up to your bedroom stereo).

As managed by upmpdcli, MPD does not need to index the audio files metadata and its configured music directory may be empty. If you want to use a native MPD client, upmpdcli is not the right solution: have a look at the alternative approaches for MPD/UPnP integration.

What's the point ? If you are running a UPnP network with multiple devices, you may prefer using a single control application (UPnP-based) for everything. MPD is a very capable and robust music-playing application, which runs well on small computers (e.g. Raspberry PI or other "plug" type computers). However it needs a specific control application. upmpdcli lets you control your MPD-based players with your UPnP control point, and also brings new functions such as synchronized multiroom (Songcast), and access to streaming services.

Comments

Please use the Isso comments for praise, insults, or for tips which may help others.

Use the issue tracker for problem reports and enhancement suggestions.

Use E-mail if you run into trouble, I'll be glad to help: jf at dockes dot org.