Nelson

Well-well, it seem like I found something interesting: As you said that my mp3 file doesn't have any pipes (because I might sent you the wrong file) I proceed to download the file from this page to check it out with Kid3, and for my surprise I found that it is the right file, but then I proceed to check it out with MP3 Diags and I found out that all the pipes were already replaced with commas with a blank space, in the untouched file. In fact, I reloaded the file in Kid3, close the software, re-open...

Well, this is the first time I read about any issues with the ID3v2.4.0 version, and I'd like to know about it. About the conversion automatic 2.3.0-2.4.0 conversion, I confess it passed me by. I thought the metadata fetching executed by Kid3 was the cause. Now I see MP3Diags does it too (which I'd prefer it doesn't do it, but I guess it have to, to be able to apply the corrections). Another unnoticed consequence of transformations: music genre numeric codes in parenthesis instead of strings. It...

I forgot to mention that the mentioned replacement happens applying the custom transformation list #4 : Restore flipped bit in audio Remove inner non-audio Remove truncated audio streams Repair VBR data Remove mismatched Xing headers Discard invalid ID3V2 data Remove unsupported ID3V2 streams Remove multiple ID3 streams Remove unknown streams Remove broken streams Remove unsupported streams Remove truncated audio streams Remove null streams Remove extra space from ID3V2 Make the largest image "Front...

Pipe characters replaced by commas on ID3v2.4 tags

Playlist group format not working

After read your explanation now I remember that I changed the version of the id3v2 tags of my whole music collection from 2.4 to 2.3 in order to be displayed on Windows Explorer (I comment about it in another post). I was merging (manually) both Arranger frame metadata, but I got tired (I should write a bash script to do that) but before I wanted to understand what was the issue about. That's a very handy table, I've should have read it before. (in fact, I should read more official documentation)....

Since the last Kid3 release (I think) I've been noticing that the Performer frame offered by MusicBrainz is been saved into the Arranger frame, which is highlighted in red when there's another Arranger frame present for the track. So, there's id3 tags with two Arranger frames, with the second one colored in red, containing Performer metadata. I'm using Kid3 3.5.1 compiled on Debian Stretch.

The problem was solved setting the "OggFlacMetadata" extension priority below "TaglibMetadata", as you suggested. Thanks so much!