Bug 152209 - id3 v2.4 album art not displayed in applications (kid3 & amarok)
Summary: id3 v2.4 album art not displayed in applications (kid3 & amarok)
Status: RESOLVED FIXED
Alias: None
Product: taglib
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Scott Wheeler
URL:
Keywords:
: 152175 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-11-12 18:22 UTC by Syam
Modified: 2007-11-21 16:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Syam 2007-11-12 18:22:33 UTC
Version:           1.5 (Release: 0.5.20070924svn.fc8 - from yum info) (using KDE KDE 3.5.8)
Installed from:    Fedora RPMs
OS:                Linux

I had my MP3 files tagged using kid3/taglib. I was using embedded album art with id3 v2.4 tags, inserted using kid3/taglib. Everything was fine and Amarok was displaying the album art just fine. After upgrading to Fedora 8, I found that Amarok no longer displays id3 v2.4 albm art. Nor does kid3. I tried adding a new album art (APIC) to a fresh MP3 file, using kid3/taglib. I successfully added a jpeg file.
Later, when I open the file using kid3, the APIC field is mentioned. But the image cannot be viewed or exported. The same applies to all my older mp3 files which used to work just fine.
Comment 1 Seb Ruiz 2007-11-12 23:58:52 UTC
*** Bug 152175 has been marked as a duplicate of this bug. ***
Comment 2 Lukáš Lalinský 2007-11-20 09:11:26 UTC
Is this using taglib 1.4 or some SVN shapshot? SVN had an off-by-one error in API frame parsing for a while. The resulting cover art always contained one extra byte of junk info at the start.
Comment 3 Scott Wheeler 2007-11-20 12:12:33 UTC
This is Fedora's SVN snapshot; I suspected that was the problem as well, but hadn't gotten around to testing with the current SVN.
Comment 4 Syam 2007-11-20 16:40:27 UTC
So, what is the recommended course of action?
Since this seems to be a problem with the Fedora8 version of taglib (0.5.20070924svn.fc8), I've submitted a bug report at RedHat bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=392591
Should I replace the package with TagLib 1.4 compiled myself?
Comment 5 Scott Wheeler 2007-11-20 18:27:12 UTC
No, while a few people have done that, TagLib (like most libraries) is backwards compatible, but not forwards compatible -- meaning if you replace a newer version with an older version you have to recompile everything.

At some point tonight I'll try to see if I can reproduce the bug with the SVN from the snapshot date vs. current SVN.  If I can only reproduce this with the older SVN snapshot then this issue goes back to Fedora.
Comment 6 Rex Dieter 2007-11-20 18:29:38 UTC
Thanks Scott.
Comment 7 Rex Dieter 2007-11-20 19:09:50 UTC
Syam, this may already be fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=376241
Comment 8 Lukáš Lalinský 2007-11-21 08:08:59 UTC
Scott, the problem was fixed in r735035, which includes a simple way to reproduce it (it's actually a combo of multiple bugs). 
Comment 9 Rex Dieter 2007-11-21 14:05:46 UTC
fwiw, r735035 was comitted 2007-11-10, so should be included in the latest taglib snapshot f8 update.

Let's consider this fixed (unless someone provides evidence to the contrary).
Comment 10 Syam 2007-11-21 16:02:02 UTC
The bug is indeed fixed by the updated package (1.5 - 0.6.20071111svn.fc8). Thanks guys for your support.