AliasTags and Artists

[hvaleton]

(27-05-2013 12:02)simoncn Wrote:  

(27-05-2013 11:19)hvaleton Wrote:  Could it be that, because of the aliasing, the splitting of the Artist string using semicolons does not work anymore? (or am I doing something wrong here?) And was that a deliberate choice on your part? Could anything be done about it?

MinimServer doesn't support splitting tag values by semicolons. It doesn't make any difference whether or not the tag is aliased. For example, if you have an Artist tag set to 'Artist 1; Artist 2; Artist 3', MinimServer interprets this as a single artist named 'Artist 1; Artist 2; Artist 3' (with or without tag aliasing). This is required to conform to the tagging standard specifications.

To get what you want, you'll need to leave your Artist tags with commas (for the Sonos) and use a new tag for each individual artist. For example, you could use the Performer tag for each individual artist and add the tag aliases

Performer:Artist
Artist:nil

In the previous example, the file would have tags

Artist=Artist 1, Artist 2, Artist 3
Performer=Artist 1
Performer=Artist 2
Performer=Artist 3

and MinimServer will see these as

Artist=Artist 1
Artist=Artist 2
Artist=Artist 3

The All Artists index will show

Artist 1
Artist 2
Artist 3

and the album and track information will show

Artist 1, Artist 2, Artist 3

Hi Simon,
thanks for your prompt reply.
I was completely flabbergasted, though, by your answer, until I put on my thinking cap and went a little deeper into this strange case.
Why strange?
Well, when I first tested multiple artitsts by replacing all the comma's in the original Artist tag, this did give the desired result. And using an aliased tag it did not!
Just now I looked 'inside' the flac file (using PSPad editor) and noticed that apparently MediaMonkey stores the various artist names that I put in the original Artist tag, into as many separate Artist tags.
Your reply made me suspect that this would be the case, but I had never before read that MM worked this way.
As you have guessed by now, MM does not "cut up" the Custom4 tag into the necessary number of identically named tags, but just stores it as is: one long string.
I will now try and find a solution for this... (suggestions, anyone?)

Have a nice evening!

Hans