I just decided to finally switch to foobar today and have the feeling my problem is actually something quite basic. However I just can't figure out where to look.
I was adding files to my playlist when I noticed that some of the file names just don't look the way I remember them from Winamp. After confirming that the file was still correctly tagged (explorer -> preferences) I was confused.
After some thinking I switched to Winamp and looked at the file's information and noticed that foobar displays the idv1 tags (which are, in some cases, screwed up, because when fixing the tags for Winamp I would normally only change the IDv2 tags).
So, anyway my question is how do I tell foobar to ignore the idv1 and only read what's written in the IDv2? The most obvious solution seemed to be Tagging -> MP3 Tag Types and to deselect everything besides IDv2, however this didn't change anything.
I'm running v0.9.4.4
Full Version: How to ignore ID3v1 when reading tags?
QUOTE
So, anyway my question is how do I tell foobar to ignore the idv1 and only read what's written in the IDv2?
That's not possible.
You can use an application like Mp3tag to remove the ID3v1 tags from your files.
Remove: [x] ID3v1, [_] ID3v2
File, Remove tag
Can't you use Tagging > MP3 Tag Types > deselect ID3v1 too?
No. Note that he had already tried this.
If certain fields of the ID3v1 tag were prioritized over their ID3v2 counterparts when the file was read, this would only cause the ID3v1 values to be written to the ID3v2 tag. This is just how foobar2000 works internally - it abstracts the access to tags by merging them to a unified list of fields and values, so that components and users won't have to care about which formats they are actually dealing with.
This of course fails if the contents of ID3v1 and ID3v2 tags don't follow certain rules. ID3v1 fields for example are expected to never contain strings longer than the respective ID3v2 field.
If certain fields of the ID3v1 tag were prioritized over their ID3v2 counterparts when the file was read, this would only cause the ID3v1 values to be written to the ID3v2 tag. This is just how foobar2000 works internally - it abstracts the access to tags by merging them to a unified list of fields and values, so that components and users won't have to care about which formats they are actually dealing with.
This of course fails if the contents of ID3v1 and ID3v2 tags don't follow certain rules. ID3v1 fields for example are expected to never contain strings longer than the respective ID3v2 field.
QUOTE(Frank Bicking @ Oct 10 2007, 23:58) 
You can use an application like Mp3tag to remove the ID3v1 tags from your files.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.