Any number in ID3v2 genre field is matched with ID3v1 genres
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-mutagen |
New
|
Undecided
|
Unassigned |
Bug Description
I tag all my music with the release year in the genre (I also use the year field, but almost no browser or PMP that I know lets you browse by year, so I resort to that little trick), and when trying to import my Music into Exaile, I found that it all got categorized as genre "Unknown".
After doing a little digging, I found that Exaile is trying to match
any number in the genre field to the list of genres in the ID3v1 spec,
even if you are using ID3v2 tags as I do. Given no genre exists for,
e.g., "2007", it's classified as Unknown.
I understand that the ID3v2 spec for the TCON frame is especially
awkward regarding that subject, but could Exaile understand that if
the number is larger than 127, there's no way that it's an ID3v1 genre
(and therefore display the "bare" number as the genre).
I wouldn't be complaining if I had not tried before with other media
managers like Amarok or iTunes, where I found no problem with this.
Thank you.
I am using Exaile 0.2.14 on Ubuntu 8.10beta