!! BUG FIXED ALREADY !!

Excellent news for … well, me.
Every problems I exposed here were no more in version 0.9.5.2. Thank you very much !! (^o^)y
(I was not able to mark this thread fixed in the subject line. If someone can do this …)

Hey I don't want to sound uncool but the bug is still in the latest version v0.9.5.

Becomes wrong after any tag edit in foobar2000 v0.9.5 :

I do this edit because it's like this topic is not taken into account. Maybe because the first post is too vague …

Original post :

Hello,
I use mp3tag to tag my files in ID3v2.3 format.
I use (among others) the tags TRACK, TOTALTRACKS, DISCNUMBER, TOTALDISCS and UNSYNCEDLYRICS in this way for 1 example mp3 file :



If I scan replaygain and write replay gain tags, then foobar2000 changes TRACK, DISCNUMBER and UNSYNCEDLYRICS tags and it deletes TOTALTRACKS and TOTALDISCS tags like this :



So that's bad and each time I scan for replaygain, I have to go back to mp3tag and redo all my files' tags.

For the ID3v2.4 tags I know it's because foobar2000 can't write ID3v2.3 (no option) and it's OK because it's fast to just resave the tags with mp3tag. But the other tag changes are quite long to be revert to what they were before.

foobar supports ID3V2.4 and has an option to use a so called 'compatibility mode' as some players and software (itunes e.g.) are not able to use ID3v2.4 or are still using bad implementations (not standard-compliant).
In 'compatibility mode' written ID3v2.4-tags by foobar should be readable by players using ID3v2.3 AFAIK so maybe this might be your solution (File > Preferences > advanced > Tagging ...). Don't know about custom tags.

foobar2000 FAQ tagging

ID3v2 Writer Compatibility Mode, ID3v2.4 vs. my mp3 players

Thanks for the links

As I said, the ID3v2.4 is not my problem because I have mp3tag to convert to standard compliant UTF-16 ID3v2.3.

No, my problem is the altering of the tags I mentionned in my first post.
Either I check the compatibility mode or not, the tags are altered in an unwanted, unsollicited way.

Reminder

Tags that are altered without sollicitation when I modify other tags within the foobar2000 tag editor * :


And maybe some other tags I did not stumble upon.



* I just noticed that it was a general behaviour. Not only when tagging replaygain.

EDIT: I forgot to say I love foobar2000 anyway!

^ This is the standard behavior. When foobar2000 is updating the tags, it removes the deprecated tag standards.

You could replaygain your files and then use mp3tag.

Yes, Now I will use replaygain at first then mp3tag.

But which tags are deprecated exactly ? I'm not really convinced with deprecated tags.

Oh, maybe I did not use TOTALTRACKS and TOTALDISCS as I should have… Because here I see that the same frame is used for TRACK/TOTALTRACKS and for DISCNUMBER/TOTALDISCS. I'll have a look at that…

BUT

But for UNSYNCEDLYRICS : Are all languages deprecated and only eng remains ??

Reminder:

And after a foobar2000 save :

I think this is really a bug here.

Hello,
I'm now using the latest version available at the moment (which is version 0.9.4.4).
The bug is still there.
At tag save time, foobar2000 0.9.4.4 replaces any language of UNSYNCEDLYRICS by eng.

So this (whatever valid 3 letters language code is in ***) :

Invariably becomes :


Please watch out for this bug.

Hey I don't want to sound uncool but the bug is still in the latest version v0.9.5.

Becomes wrong after any tag edit in foobar2000 v0.9.5 :

- Hello?

Maybe someone could tell me where the report bug link is ?
Because maybe I'm wrong reporting bugs here ?

Have you tried the new 0.9.5.1 version yet?

http://www.foobar2000.org/

Frankly, I won't test every new version, it's not fixed if you read the changelog.
I will wait for a more interesting version than just x.x.x.1.

Yeah this BS is biting me too, so you're not alone!

I use Tag&Rename to tag my mp3s from their filenames to id3v2|id3v1 and then I use foobar2000 to ReplayGain the mp3s.. but after I ReplayGain them, if I load the files back into Tag&Rename all my id3v2 tags are corrupt or empty (verified in WinAmp 5.531).

The File > Preferences > Advanced > Tagging > MP3 > ID3v2 Writer Compatibility Mode seems to have stopped my id3v2 tags from getting corrupted, but I'm not very pleased at having to go through a significant proportion of my mp3 collection to correct this mess.

Excellent news for … well, me.
Every problems I exposed here were no more in version 0.9.5.2. Thank you very much !! (^o^)y
Thank you Keikonium, maybe it was already fixed in ...1