After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 331393 - id3 genre number is not translated to name
id3 genre number is not translated to name
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.2
Other Linux
: Normal normal
: 0.10.2
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 338261 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-02-16 09:37 UTC by Loïc Minier
Modified: 2006-04-18 08:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Loïc Minier 2006-02-16 09:37:10 UTC 
Hi,

Some people have complained that their id3 tags are not handled correctly anymore in 0.10 when a genre id is used.  Joe Wreschnig explained:

<<
This looks like GStreamer is not properly interpreting ID3 tags. ID3v2          
genre (TCON) tags can be a freeform text string, but they can also be           
prefixed with an ID3v1 genre number in parentheses, or in ID3v2.4, just         
be a number of a genre. "(8)" and "(8)Jazz" should be just "Jazz";              
"(13)" should be "Pop", etc.                                                    
>>

This is Debian bug http://bugs.debian.org/352213.

Cheers,
Comment 1 Jan Schmidt 2006-02-16 10:09:52 UTC 
This was fixed in the 0.10.2 release:
          Rewrite parsing of text tags to handle multiple NULL terminated
          strings. Parse numeric genre strings and ID3v2 type
          "(3)(6)Alternative" style genre strings.
          Parse dates that are only YYYY or YYYY-mm format.
          (Fixes #328241 and #322154)

Are you sure the people are running 0.10.2?
Comment 2 Jan Schmidt 2006-02-16 10:10:27 UTC 
That's 0.10.2 of gst-plugins-good, in case it wasn't clear
Comment 3 Loïc Minier 2006-02-16 13:40:58 UTC 
In fact they were running 0.10.1, and 0.10.2 fixed it, thanks.
Comment 4 Alex Lancaster 2006-04-18 08:14:51 UTC 
*** Bug 338261 has been marked as a duplicate of this bug. ***