EasyTAG-2.1.4-destroyed cover

[Jeff Mitchell]

If it's a bug in taglib, this conversation belongs on taglib-devel at kde.org, 
not here.  I'd talk to them soon, because 1.5 is gearing up for release, and 
it doesn't get released often.

Note that you should test this out with the latest SVN version of taglib.  If 
you are using taglib 1.4 release, it could very well be fixed already.

--Jeff

On Monday 21 January 2008, Jakob Sack wrote:
> Hello Jérôme,
>
> I applied your patch and it does work better indeed :-) Unfortunately,
> amarok still has issues with the cover.
> The cover is saved perfectly but has one additional byte (00) in the very
> beginning. *GRML* I really don't know which program has a bug at this point
> because I don't know whether this byte belongs there (in the mp3 file) or
> not.
> If I can help you I'll be glad to do my best but keep in mind I'm C
> programmer :-)
>
> Regards,
> Jakob
>
> Am Sonntag, 20. Januar 2008 23:17:30 schrieben Sie:
> > Hi,
> >
> >     The problem seems to be due to a bug in taglib that don't support
> > frames with unsynchronisation.
> >
> > Could you test the attached patch to don't write unsynchronised frames
> > with EasyTAG?
> >
> > Regards,
> > Jerome
> >
> > Jakob Sack wrote, the 02.01.2008 17:05 :
> > > Hi,
> > >
> > > I've got a problem with EasyTAG. I added a cover to a mp3 file and
> > > played it with amarok. Unfortunately, the cover is displayed completely
> > > destroyed. After some investigation I found out that rhythmbox shows
> > > the cover without any problem. The cover extracted by amarok has some
> > > additional bits compared to the source file. However, these bits
> > > already exist in the mp3 file. Is EasyTAG "destroying" the image? I
> > > mean rhythmbox and EasyTAG are both GTK based apps, Amarok and
> > > Konqueror (also showing the destroyed image) are KDE apps.
> > > I hope this error will be fixed soon (btw I'm not the only Amarok user
> > > having this problem)
> > > Thanks in advance,
> > >
> > > Jakob