Compilations at end?

[simoncn]

I don't think setting ALBUMARTISTSORT for every song even when it has the same value as ALBUMARTIST is "usual tagging behaviour". When I rip a CD using dBpoweramp, I get ALBUMARTIST tags but not ALBUMARTISTSORT tags.

In MinimServer, there is an overhead for every tag value that has a custom sort value. This overhead applies whether or not the custom sort value is the same as the tag value. For a specific tag value, adding the custom sort value to every file increases processing cost when scanning these files but does not increase memory usage because only one copy of the custom sort value is stored. If a custom sort value is required, this processing cost is a necessary price to pay and I have never advocated trying to reduce this processing cost by only storing the custom value in a single file. The point we are discussing here is whether this cost should be incurred when the sort value is not being customized.

Having MinimServer process the custom sort value and store a boolean if it is present and identical to the tag value would be significantly more complex than the way MinimServer current handles this and would not reduce processing time compared with the current design. Adding a boolean to every tag value object would increase memory usage for the normal case of no custom values except where needed and I would not wish to do this.