MinimServer doesnt like multivalues for AlbumArtist

[simoncn]

(06-08-2017 17:53)paultaylor Wrote:  Simon I dont see any logical reason why MinimServer should not work as expected if all albumartists on the one album have the same multi-value album artist. Is it possible to consider this as feature request, or is there a logical/techincal reason why this cannot be done ?

The current rules for how MinimServer handles AlbumArtist tags, Artist tags, the AlbumArtist index, the Artist index and the All Artists index have been designed to do what most users want for most music libraries. Explaining how all this works is already fairly complex and the restriction to a single AlbumArtist value per album limits this complexity by reducing the number of cases that need to be described in the documentation and supported by the implementation. Allowing multiple AlbumArtist values would add complexity to both the description and the implementation and would create a new class of errors where some tracks in an album are tagged with two AlbumArtist values and some tracks are tagged with only one of these values.

Quote:So, the workaround that I suggest in http://blog.jthink.net/2017/05/minimserv...album.html is to leave albumartist alone so Artist index works as expected

But add another index called Album Artist that is populated by the Album_artists field

So now you have an All Artists, Artists and Album_artist index and the best of both worlds.

This would also be my suggestion, except that I would suggest not having an Artist index because this would contain things that the OP doesn't want to see (Baba Saad feat. Bushido). Instead, indexTags could contain Albumartists:Artist so that the Artist index contains just the "album artist" values and the All Artists index contains just the "track artist" values.