Bug 121400

Summary: Embedded cover images are not displayed correctly
Product: [Frameworks and Libraries] taglib Reporter: Hans Meier <ma2412ma>
Component: generalAssignee: Scott Wheeler <wheeler>
Status: RESOLVED NOT A BUG    
Severity: normal CC: kretschmann
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Hans Meier 2006-02-05 07:56:07 UTC 
Version:           1.3.8 (using KDE KDE 3.5.0)
Installed from:    SuSE RPMs
OS:                Linux

The cover images from my MP3 files, which contain images embedded in the ID3 tag (created with iTunes), are not displayed correctly. More specifically, the upper two thirds are correct, but the lower third is just a gray area. Everything works fine in iTunes.
Comment 1 Mark Kretschmann 2006-02-05 08:58:08 UTC 
We use TagLib for reading the images. So I'm reassigning the report.
Please specify the version of TagLib you are using.

(/me waves to Scott and Michael)
Comment 2 Scott Wheeler 2006-02-06 01:18:12 UTC 
Can you email one of these problematic files to wheeler@kde.org with the filename 121400.mp3?
Comment 3 Hans Meier 2006-02-06 07:56:46 UTC 
I'm using taglib 1.4-8 that comes with Suse 10.0. Scott, I will send you a file as soon as possible.
Comment 4 Scott Wheeler 2006-02-06 23:43:24 UTC 
This is actually a bug in the Apple ID3v2.4 implementation.  (I was glad to see that a few months ago they finally switched over to 2.4, from 2.2, but there are still some bugs in their implementation.)

Specifically, on the odd chance that anyone has contact with the Apple developers, the bug is that they're not properly using synch-safe integers in the ID3v2 frame lengths.  They're "plain" 32-bit integers, which when processed as synch safe integers come out too small.

(I've added Mark back to the CC as we're likely to see more of these.)
Comment 5 Scott Wheeler 2006-02-07 00:01:01 UTC 
I actually did just put this in Apple's bug tracking system; we'll see if that makes any difference.
Comment 6 Scott Wheeler 2006-02-08 01:32:38 UTC 
Just got confirmation from Apple that this is a known issue for them.