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 335028 - [typefinding] ID3 v1 tag is not recognized with mp3-in-wav file
[typefinding] ID3 v1 tag is not recognized with mp3-in-wav file
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.x
Other All
: Normal normal
: 0.10.6
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 336964 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-03-18 17:31 UTC by Jean-François Fortin Tam
Modified: 2006-04-03 19:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Jean-François Fortin Tam 2006-03-18 17:31:56 UTC 
Please describe the problem:
The ID3 tags in this file (and lots of similar files) are not read.
http://jeff.nanokron.info/bug-gstreamer_id3v1.mp3 (6.1mbytes)

Steps to reproduce:
open the file in totem/rhythmbox or view its properties in nautilus

Actual results:
title = the file name
artist = unknown
album = unknown
etc.

Expected results:
See the id3 tags

Does this happen every time?
Yes

Other information:
I can see the tags in tagtool or easytag
Comment 1 Tim-Philipp Müller 2006-03-19 11:37:49 UTC 
2006-03-19  Tim-Philipp Müller  <tim at centricular dot net>

        * gst/typefind/gsttypefindfunctions.c: (id3v2_type_find),
        (id3v1_type_find), (apetag_type_find), (plugin_init):
          Can't do tag preferences via probability, as tags would then
          lose against types that are recognised with MAXIMUM probability
          (like .wav); so let all tag typefinders return MAXIMUM themselves
          and order them via the rank. Split ID3v1 and ID3v2 typefinders so
          that we can prefer APE to ID3v1 (fixes #335028).
Comment 2 Tim-Philipp Müller 2006-04-03 19:25:38 UTC 
*** Bug 336964 has been marked as a duplicate of this bug. ***