i don't get something.. normally, when you add more than one entry to a tagfield, you'd be able to do so with the \ as a separator, ie. Mirella Freni\Christa Ludwig\Nicolai Ghiaurov\Carlo Cossutta.
This would then result in comma separated entries in the playlist.. however, with some tracks (which are generally mp3s) it refuses the recognize the \ as a separator, and i get to see the \ in the playlist in stead of the ", "
it then requires me to make multiple performer fields, and add the performers one at a time.. and with some tagtypes, when you add more than one 'field' of the same type, it asks whether or not you want to overwrite, while sometimes it doesn't.. (this happens with mp3, as well as mpc type files, both written with apev2, and for mp3 also id3v1 tags)
It really seems quite random, and quite illogical..
The only thing that stays the same throughout is the fact that i never succeed in 'merging' the performer fields afterwards (nor does foobar do so in the 'properties' popup).. so i assume there's a real difference between having 4 'performer' tags and 1 'performer' tag with 4 entries separated by a \

does anyone have a clue as to what to do here? it seems to be foobar-related rather than file-related, as rewriting the filetags doesn't do anything to fix this either..

1) With WMA files the "\" separator will not work, with MP3s it should.

2) In FB, both 0.8 and 0.9, there is a main inconsistency between the behaviour of the properties dialog (both the built in and the special one) whether you invoke it after selecting many tracks or a single track. (Unfortunately, no dev seem interested in correcting this bug, at the moment)

With many tracks selected the "\" works as expected.

With only one track selected it doesn't. At least not directly.

A solution is to run the masstagger script "split field by separator" once you have finished editing the files. In this way you can do your tag editing, track by track if needed, whithout bothering if the "\" is working or not and then run that script over all the edited tracks.

Do some tests and let me know.

Whether the backslash as separator works, depends on whether you are using the multi-file version of the "Properties" dialog (where the tag editing dialog contains a note about it) or the single-file version (where there is no such note). If the audio format in question supports multi-value tags is another question.


<nitpicking>
Technically, this is not the bug. The code does perfectly what the specification says, even if said specification only exists in the mind of the programmer. That you don't like the particular behaviour, does not make it a bug.
</nitpicking>

That being said, I'd prefer a consistent behaviour as well. It does not currently have a high priority, because it is "merely" a frontend issue. API redesigns that affect how foobar2000 works internally and how components interact with it have a higher priority at the moment.

I'm sure you understood that that "bug" was meant to be just a little (very little) and harmful provocation...

And... it worked.
Now, at least I know that, even with a low priority, it is in a to do list.
The other time I mentioned it I never got an answer...



(Hope the properties dialogues will be redesigned so that each tag will have its box and maybe, each box will have its custom list (I'm thinking of instruments or genres or similar things) to avoid mispelling.)