Compilations at end?

[paultaylor]

Not really important, but just continuing discussion.

(20-03-2019 20:50)simoncn Wrote:  

(20-03-2019 19:47)paultaylor Wrote:  I must disagree, the trouble with this approach is its difficult to determine if an artist doesn't have a sort album artist because the sort album artist is the same or just because the user hasn't got round to entering a sort album artist.

As I said in my previous post, it is very simple to discover this with MinimServer by making ALBUMARTISTSORT an index tag.

Not really, that simply tells if an ALBUMARTISTSORT has been set it doesn't tell you why it hasnt been set. More to the point, as you explained if you consider a single ALBUMARTIST MinimServer logic dictates that if two songs by the same ALBUMARTIST have different values then the ALBUMARTISTSORT value would be ignored, therefore there should only be one ALBUMARTISTSORT valuer for a particular ALBUMARTIST, which makes sense. So from a MinimServer pov it would be best for only one of the songs by a particular ALBUMARTIST to have ALBUMARTISTSORT set and leave the rest blank. This would use the least processing, and possibly the least memory because only one ALBUMARTISTSORT field would be read for all songs with that ALBUMARTIST. But would it really make any difference, since MinimServer would only need to store the ALBUMARTISTSORT value once in memory anyway for a particular ALBUMARTIST. And although it would work for MinimServer it would clearly be wrong if using your files outside of UPNP.

Similarly even if ALBUMARTISTSORT is set for every song even when they have same value as ALBUMARTIST, you would only have to store once for a particular ALBUMARTIST. And you could in fact just store as boolean to note sortartist is the same. I don't think MinimServer should modify usual tagging behaviour.