QUOTE(shrinkmail @ Apr 10 2007, 13:06)

And this is a major bug !!
No, it is definitely not a bug. As it says in the fb2k preferences, the function you're using to tag your files is only a Writer
Compatibility Mode for software that doesn't implement ID3v2 correctly. If the developers really wanted to provide complete downward compatibility, I'm sure they would have called the option "Enable ID3v2.3 support."
QUOTE(shrinkmail @ Apr 10 2007, 13:06)

It's amazing that no one has replied to yur post after 2 weeks !
A simple forum search would have pointed out that this topic has been discussed in the past over and over again in many other threads, for example
here and
here, just to mention a few. It is no wonder that noone replies to a post if there are several existing threads in this forum that can already provide a complete answer.
QUOTE(shrinkmail @ Apr 10 2007, 13:06)

You can't tag a classical collection properly without non-standard tags and I really don't like the way foobar treats your meticulously entered (non-standard) ID3V2.3 tags in such a cavalier fashion.
Again, I don't quite understand why you blame foobar for this. We wouldn't need functions like Writer Compatibility Mode if the ID3v2 specifications were correctly supported by other software and hardware players. Sadly this is not the case, and if you want to try changing it, write a mail to the developers and complain about the bugs in their software/firmware rather than complaining about a feature in fb2k that you can be glad of and the implementation of which is under no obligation of the foobar developers. As it is annotated in the preferences, it "activates workarounds for common bugs in other software".
I would recommend closing this thread as to how similar discussions have developed in the past...
QUOTE(shrinkmail @ Apr 10 2007, 13:06)

If there is no solution to this issue, I guess I'll have to go back to good old 0.8.3

Feel free...