Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: ID3 tag version preference / reading order (Read 1682 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

ID3 tag version preference / reading order

Hello,

foobar seems to prioritize ID3v1 over ID3v2 tags when reading tags which is kinda not so cool.

For example, when importing music from iTunes many files will be messed up in foobar while they look fine in iTunes (which prefers ID3v2) and also in Windows Explorer.
Only way to fix the problem right now is to use a third-party tool to remove id3v1 tags from the problematic files.


I'm asking for an advanced option to configure the reading order or changing foobar's default behavior.


Here is a quote from a related thread:
Quote from: Peter on
[...] I'm considering changing it to always prioritize APEv2 over ID3v2 and ID3v2 over ID3v1 somehow; [...]


That was 4 years ago. Wonder why it still hasn't changed.

ID3 tag version preference / reading order

Reply #1 –
Foobar now chooses the longest version of each field. In most cases this will prioritise ID3v2 over ID3v1's cut values, the only times this is not the case is when ID3v1 and ID3v2 do not contain the same information.
 

ID3 tag version preference / reading order

Reply #2 –
Hmm, I've had files that foobar detected with a long URL as title and all other tag fields were0 empty (messed up v1 tag I guess). The v2 tag was fine however, I checked it with mp3tag.

Is this a bug or a feature? 

ID3 tag version preference / reading order

Reply #3 –
(sry for double post)

Anyway, it would be nice to be able to configure/force foobar to read the v2 tag first similar to the "Force preferred tag writing scheme" option.
Would make sense to have a reading option if there's already a writing option.