I have a question, what is the difference between a backport and a not backport? or more to the point what are the strengths of each? I only ask because there is a backport of exaile available through the mint software portal as well as a normal one.
Mind you both of them spit the dummy and crash half way through importing my music collection
The \x05\x00\x00\ gibberish at the end goes on for a few thousand lines.
- Code: Select all
Possibly corrupt file: /media/sda5/My Music/Pendulum/Hold Your Colour/Through The Loop.mp3
-----------------------
fill_tag_from_path ( /usr/share/exaile/xl/media/mp3.py @ 63):
-----------------------
Traceback (most recent call last):
File "/usr/share/exaile/xl/media/mp3.py", line 69, in fill_tag_from_path
id3 = mutagen.id3.ID3(tr.io_loc)
File "/usr/lib/python2.5/site-packages/mutagen/id3.py", line 74, in __init__
super(ID3, self).__init__(*args, **kwargs)
File "/usr/lib/python2.5/site-packages/mutagen/__init__.py", line 39, in __init__
self.load(*args, **kwargs)
File "/usr/lib/python2.5/site-packages/mutagen/id3.py", line 136, in load
for frame in self.__read_frames(data, frames=frames):
File "/usr/lib/python2.5/site-packages/mutagen/id3.py", line 275, in __read_frames
try: yield self.__load_framedata(tag, flags, framedata)
File "/usr/lib/python2.5/site-packages/mutagen/id3.py", line 298, in __load_framedata
return tag.fromData(self, flags, framedata)
File "/usr/lib/python2.5/site-packages/mutagen/id3.py", line 984, in fromData
raise ID3BadUnsynchData, '%s: %r' % (err, data)
ID3BadUnsynchData: invalid sync-safe string: '\x00image/jpg\x00\x03\x00\xff\xd8\xff\xe0\x00\x10JFIF\x00\
x01\x01\x01\x00`\x00`\x00\x00\xff\xe1\'`Exif\x00\x00MM\x00*
\x00\x00\x00\x08\x00\x07\x01\x12\x00\x03\x00\x00\x00\x01
\x00\x01\x00\x00\x01\x1a\x00\x05\x00\x00\x00\x01\x00\x00\
x00b\x01\x1b\x00\x05\x00\x


