I’m wondering if Mopidy is a good start for the kind of music player I’ve been looking for for a while. The short version is that I’d want to expose more (in the case id3v2) tags than seem to be present in the Mopidy “track” structure.
I see that the Local Library API supports an “add_supports_tags_and_duration” flag and allows “all” these tags to be passed to the library, however I don’t see any way to get those tags back out of the library, (and I don’t see any library backend that supports this flag) is that correct? I was hoping that maybe an extra “tags” dictionary might make it out to the http interface as an optional property.
I’m comfortable writing code to support these things at the library end and the client end, just need to understand if there are infrastructure blockers.