From: Jean Boullier <jean.boullier_at_wanadoo.fr>
Date: Sat, 27 Mar 2004 02:51:29 +0100

Linus,
I appreciate your intention to make the TCON processing "more
forgiving". You have not given details but I assumed that it would be
simply showing the string which is there, without trying to interpret
anything, which is actually where the jungle begins. I had simply read
the general frame specifications and I had forgotten to look for a
particular article for the TCON string. Having corrected this lack I
must admit that the confusion appears now. Even though my understanding
of the (xx) coding is that it is an option for those who want to simply
convert the amazingly poor id3v1 genre coding, not a mandatory item.
Otherwise where is the improvement brought by id3v2 versus id3v1 (on
this topic)?

Anyway, the sad point is that I have tried the 20040326 build and that I
do not see a difference for my "simple" TCON tags.Genre is still saying
"no info". I have been able to find a few pieces that I have not
created myself and that have a (xx) TCON coding and those pieces do show
a genre in the ID3 info screen, but I assume that it was already doing
that before, no?

Thanks for trying, still. Jean.

Linus Nielsen Feltzing a écrit:

> Jean Boullier wrote:
>
>> All these tags are from MusicMatch at different times but anyway, as
>> far as the TCON frame is concerned, they all look the same as far as
>> I can see.
>
>
> MusicMatch may still violate the (very unclear) ID3V2 specification
> anyway.
>
>> Thanks once more for all your dedication and attention to this project.
>
>
> Since you put it that way, I have now made the TCON parser a little
> more forgiving. :-)
>
> All your test files show the genre now. The 20040326 build will
> include this fix.
>
> Linus
> _______________________________________________
> http://cool.haxx.se/mailman/listinfo/rockbox
>

-- 
Jean Boullier - Rouen - Normandie - France
_______________________________________________
http://cool.haxx.se/mailman/listinfo/rockbox

Received on 2004-03-27