Package: python-eyed3 Version: 0.6.5-1 Severity: normal eyeD3 forgets that the id3v2 header size includes the extended header, so FrameSet.parse (frames.py, around line 1460) expects there to be ~10 more bytes of frame data than there really are. If there's no padding, the frame data runs right up to the end of the header, so it ends up trying to interpret some data after the header as a tag frame; this doesn't work, so eyeD3 bombs out. If there's padding in the header, though, it sees an all-zero frame ID and stops parsing frames.
Unfortunately, as it stands, it looks like that method doesn't have the information it needs to account for the extended header.. so I just hacked it so it worked for the one file I was testing. Otherwise there'd be a patch here. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages python-eyed3 depends on: ii python 2.3.5-2 An interactive high-level object-o -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
