I have this automatic script:
When those tags are not present, everything works fine. When they are , i.e. I reopen album in Picard later to fix some tags and I get above tags doubled as lower case along with original case:
Picard alone added the lower case lettered tags which are not present in the metadata. Here is the screenshot of the Foobar2k song properties:
If I don’t remove older tags they are merged by Picard:
This looks like a Picard bug to me, not sure what else it could be?
Have you tried using lower case for your script?
(I suspect that Picard is simply defaulting to lower case for the old tags and you then create new upper-case versions.)
Yeah, that fixes it, tags are again in the result uppercase and there are no lowercase variants.
This weird behavior should be fixed anyway, unless I am mistaken about something crucial. I see now that Foobar converts lowercase tag names to uppercase on save, so maybe its that custom tags MUST be uppercase. But even so, behavior is IMO not correct - I shouldn’t get lowercased tags then anyway.
Picard scripting is case-sensitive, and in general, you have to handle MP3 differently from M4A differently from FLAC/Vorbis, which requires lots of branches in your tagger scripts.
By default, Picard writes MP3 tags that don’t have great compatibility with a mixed format library (e.g., mix of MP3 files and FLAC files), or play nicely with foobar2000. This script moves Picard fields so that they look the same as FLAC files in foobar2000.
$noop(Move UFID:http://musicbrainz.org to TXXX)
$noop(foobar2000 can't read INVOLVED PEOPLE / TIPL v2.4 / IPLS v2.3)
@yindesu So you say its not a bug ? If its case sensitve, why is it listing lowercased tags which I didn’t specify anywhere?
BTW, I have only mp3 and flac and behavior is the same on both.