I have this example multi-value field SetSubtitle:
MB Picard only shows the Original Value with the first content of SetSubtitle and correctly suggests the new value:
But no matter what I try with $setmulti, I can not keep my multi-value field as two separate fields with the same name.
How can I solve this?
The best way would be that MB Picard recognise my two fields as “Original Value” and doesn’t change it at all. How can I do that?
If only a script can solve this, I would use it too 
I use this script for my multivalues:
$setmulti(albumartist,%_albumartists%)
$setmulti(albumartistsort,%_albumartists_sort%)
$setmulti(artist,%artists%)
$setmulti(artistsort,%_artists_sort%)
There must be something trivial that I don’t see.
If I load a track with two SetSubtitle entries as shown above, MB Picard (this time without any scripts loaded) shows this field in black colour as identical and no change pending:
As soon as I save this track, my two SetSubtitle values are merged into one.
From:
To:
The two values are then one string, separated by a real slash.
What can I do to prevent that and keep my two SetSubtitle entries?
Yes, it is ID3v2.4 is the one that supports multi-values.
Manual page:
That says that v2.4 is the default, and if you instead select v2.3 you’ll loose “native support for multi-valued tags in v2.4” It is v2.3 that merges values into the one tag.
Thank you for the link, including
As mentioned above, ID3v2.3 does not support multi-value tags, and so Picard flattens these to strings before saving them to ID3v2.3 tags. This setting [“Join ID3v23 tags with”] defines the string used to separate the values when flattened. Use ‘; ‘ for the greatest compatibility…
Unfortunately, I can’t switch to ID3v2.4 due to not yet compatible devices (surprisingly capable of handling multi-value fields “correctly” in ID3v2.3. - written by other software…)
The old classic headache of “standards” that are implemented in different ways by each product…
