Think you might be interested ot know

[-=raTTan=-]

When ever dbpoweramp adds a ID3v.2 it corrups the vbr header, and both winamp and dbpoweramp can't tell you the proper average bit-rate nor properly determine the length of the tracks which constantly will flicker and also cannot even determine the correct encoder that was used, this which may also even be possible with CBR. this is only for MP3 that i have seen. i had a lame file that i had just made which said encoded by x-ing (new). and of course all the other info was corrupted too. however this never happens with id3v1. I came to this conclusion after extensive testing. you can disable id3v2 in configuration. as long as your entries are within 30 or so characters, and you use one of the pre-defined GenreS it should use v.1.:o

[Spoon]

I am in two mind if it corrupts it, or if it is a problem with Winamp and dAP in decoding the VBR header after ID3v2.

This is one of the reasons why Id3v2 is disliked so much.