Tagging riddle

[DavidHB]

(06-05-2015 08:21)Baba Yaga Wrote:  So I think you are right on the money, the tagging errors are out there somewhere

I agree. And it's almost impossible to spot them all using just the Mk. I eyeball, which is why I recommend selecting and filtering all the tracks in the library; as you found, errors can lurk in compilation albums and other places in which you might not think to look.

(06-05-2015 08:21)Baba Yaga Wrote:  BTW: The logging file in Minimserver is most useful!

Fully agree. Its an essential part of my tagging workflow.

(06-05-2015 08:21)Baba Yaga Wrote:  Concerning the 'Composersort' tag, I don't use it at all. Frankly I saw it being mentioned but haven't figured out yet which values are allowed and why I would use it in the first place - how is it different from the sorting the Composer?

It's a different method of achieving the same result. I use it, because I set up my system before the reverseName function was added to MinimServer, and the labour of changing my tagging system would be considerably greater than sticking with my current procedure. If you are using reverseName, you don't need to use the ComposerSort tag, but you should be aware that some online tagging libraries (such as MusicBrainz) do include a ComposerSort tag as a matter of course. It may well be that ComposerSort, being a separate tag which presumably does not appear in your indexTags and itemTags properties, does not interfere at all with Composer.reverseName, but it is probably good practice to remove or blank any ComposerSort tags if you are not using them.

For information, the concept of ComposerSort is that the name is saved in its natural format in Composer, and then copied in 'Last Name, First name(s)' format to ComposerSort. I do this using one of two MP3Tag Actions, depending on whether a single first name or single last name is required. (If I were using reverseName, I would use similar Actions to reverse Composer data in natural format.) My indexTags entry includes the entry 'ComposerSort:Composer', and for this to work I need Composer in itemTags. You can see that this arrangement does with two tags what reverseName does with one. If you are already using either method successfully, I don't think that there is any good reason to change to the other one.

David