Bug#1065473: ITP: upmpdcli -- UPnP Media Renderer front-end to MPD, the Music Player Daemon
Package: wnpp
Severity: wishlist
Owner: Jean-Francois Dockes <jf@dockes.org>
X-Debbugs-Cc: debian-devel@lists.debian.org, jf@dockes.org
* Package name : upmpdcli
Version : 1.8.9
Upstream Contact: Jean-Francois Dockes <jf@dockes.org>
* URL : https://www.lesbonscomptes.com/upmpdcli
* License : GPL
Programming Lang: C++, Python
Description : UPnP Media Renderer front-end to MPD, the Music Player Daemon
upmpdcli primarily acts as an UPnP Media Renderer to be controlled
with any UPnP controller like, e.g. BubbleUPnP or Kazoo on an
Android tablet, or any other UPnP or OpenHome Control Point.
It uses an MPD instance to actually play the tracks.
A typical configuration might have for example, MPD running on a Raspberry
PI, with upmpdcli on the same host or any other Linux PC on the network.
The program also has a Media Server function, which can be configured by
various plugins to act as a Proxy for external services (streaming or radios)
or to serve local audio files.
Compared to other UPnP renderers upmpdcli brings the combined renderer/server
possibility, and support for OpenHome (local management of the playlist, allowing
the control point to go to sleep).
upmpdcli already has a Debian package, which I am willing to improve
for inclusion in the official repositories, I am in need of a sponsor.
The source and debian directory can be found here:
https://framagit.org/medoc92/upmpdcli
The existing Debian packages are pointed to from there:
https://www.lesbonscomptes.com/upmpdcli/pages/downloads.html#debian
upmpdcli is already part of audio-oriented, Debian-derived
distributions (Moode Audio, Volumio), and is quite widely used to build
audio streamers based on small computers. It is also embedded in some
hardware streamers.
Having it distributed from the default Debian repositories would
make things much more convenient for potential users.
upmpdcli depends on two additional libraries (libupnpp and libnpupnp),
also already packaged, which I will propose for inclusion in separate
messages.
Reply to: