having tried out several media players I have finally settled for mopidy. Not only does it appear to be well designed, implemented and documented, it is also the only one I have found that goes beyond the simplistic artist, album performer paradigm as it acknowledges composers and performers, both being artists as shown in the mopidy.models — Data models — Mopidy 3.1.1-1-gf17acacf documentation . There are a few aspects I would like to clarify.
Given that mopidy handles different streams, including file systems, where does the assignment to the data model happen? And what is the mapping, e.g. from an artist found in an ID3 tag to a performer or composer? Or is only the artist populated if no performer can be found? If both performer and composer can be found, will the artist be left empty?
Then to the album, a concept that does not really apply to classical music where one would talk about the oeuvre of a composer which has several parts. There were concept albums in the 1970ies which would be something like an oeuvre. In most cases, however, the album was more related to a release of a collection of works and their pieces on a medium. As it happens the smallest item becomes a track. How could all that be modelled?
The reason I am bringing that up is my hope to use or contribute to a project that is more appropriate to handling classical music, e.g. browsing by period, composer, oeuvre, performer, etc., perhaps even function as a playback for the Idagio streaming service. As it happens I have written up my thoughts on https://peter-wurmsdobler.medium.com/modelling-and-presenting-music-for-streaming-services-2627f52c1fb4 for those interested.