Fwd: Re: EasyTAG-2.1.4-destroyed cover

[Jeff Mitchell]

Valid bug?


----------  Forwarded Message  ----------

Subject: Re: EasyTAG-2.1.4-destroyed cover
Date: Monday 21 January 2008
From: Jakob Sack <jakob.sack at googlemail.com>
To: Jeff Mitchell <kde-dev at emailgoeshere.com>

Hi Jérôme,

I found the error :-)
Easytag has written the tags (by default?) as UTF16. In this way the name 
amazon.jpg was saved as "61 00 6d 00 61 00 7a 00 6f 00 6e 00 2e 00 6a 00 70 
00 67 00 ( 00 ff d8 ff e0 ...)". ID3v2.4 says that after the name of the file 
comes a "00" and then the binary data. It seems to me like amarok was using 
the "00" after the "67" as the "this is the end of the name-00".
I switched to UTF8 ("61 6d 61 7a 6f 6e 2e 6a 70 67 ( 00 ff d8 ff e0 ...)") and 
everything is fine. So I think it's an amarok bug.

Regards,
Jakob

@amarok: I use amarok 1.4.8 from www.mandrivauser.de :-)

> 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

-------------------------------------------------------