(02-28-2024, 09:57 PM)Tim Curtis Wrote: So is just like upmpdcli?

(02-29-2024, 12:11 AM)Tim Curtis Wrote: What I suppose I meant was does it provide the same functionality, but better in some way?

(02-29-2024, 08:16 PM)bsergiu Wrote: Wouldn't the MPD upnp Plug-in activation already expose the UPNP server content as an additional root folder in mpd, and thus available in the library ?

database {
   plugin "upnp"
}

As described here : https://www.lesbonscomptes.com/pages/mpd-upnp.html

The mpd binary on the Moode does not have the upnp plug-in activated, but on another Ubuntu laptop I have in the network I have that, and here is what I get:

mpc ls
192.168.178.55 - Sonos Move192.168.178.55 - Sonos Move Media ServerGarten - Sonos Move Media Renderer
Michi-X3 UPNP-mediaserver

The first one is a Sonos Move, the other one is a upmpdcli running on the Moode Raspi.

Drawback: I need to disable the mpd db, but I guess people would use either or ...

That should make the library browser UI happy, or? Am I wrong ?

Quote:Once mpd is running, your client should see a list of the network Media Servers as the top level directory.

Under the top level, you will see the hierarchy chosen by the type of Media Server, which usually has little to do with the file tree (so this is quite different from the usual MPD).

Note that you should always follow the 'Browse by Folder' options from the MPD client (these can have various names depending on the MPD client). Options to browse by artist or album, as provided by MPD will not work. You will find equivalent lists inside the tree shown by the UPnP server.

UPnP servers do not expose functionality which could be used to implement the direct tag-based browsing offered by an MPD server.
...

Quote:Known issues

Loading playlists should work, but saving them probably won’t.

Recursive directory add does not work fully: the depth is limited to 1, so this is ok to add an album directory, but it won’t go further.

Things based on VisitUniqueTags, like requesting all genres, or all artists, does not work, so the metadata browsers in most clients do not work. UPnP just does not work like this. Browse the database tree instead: it will usually have a directory with all the artists, one with the albums, the genres.

There is a fundamental difference about track identifiers between MPD and UPnP. As far as I understand, for MPD, the pathname is the fundamental identifier. This is not the case at all for UPnP, where a given track will be seen under several pathnames in the virtual tree, and objects are identified by an arbitrary unique Id.

The MPD plugin synthetizes paths based on track or container title attributes, but this means that a directory can contain apparently identical paths (if several entries have the same title).

There could be ways around this (the title could be made unique in some way), but I did not pursue them. Simply adding other fields may not be enough, so this would have to be based on the object id, or some other arbitrary value.

The consequences are mostly for searching. The normal pathnames are mostly useless as search results (typically a search for "Satisfaction" may have the UPnP server respond with entries under "All Music", all with the same title).

In this situation the MPD plugin choses to respond with arbitrary and recognizable paths based on the object ID, but clients which directly display them end up showing garbage. Happily enough most clients retrieve the object attributes for display, which works fine. Notably, phpmp does not.
...