Bug in MM or file? some files' tags not updated

Post by **jiri** » Thu Feb 26, 2004 5:41 pm

Pablo,

there's indeed a problem in showing unsynchronized tags because of accented characters written to ID3v1 tags. It will be ok in the next release.

Jiri

Pablo · Post by **Pablo** » Thu Feb 26, 2004 10:26 pm

Thanks!

duckjibe · Post by **duckjibe** » Sun Mar 14, 2004 8:11 am

I was using K-MP3 5.0.0.16 to tag & rename my mp3 files.
When using MM it cannot read the tags.
I've upgrade to K-MP3 5.5.0.53 but it does not
change anything.

Winamp has no problems with the tags.

Why MM cannot read tags ?
is their a bug in MM or in KMP3 ?

Thanks

Post by **Lowlander** » Sun Mar 14, 2004 3:17 pm

Which version of MM are you using?

Do you have any special characters (other than alphabets 26) in the tags?

What do you actually see?

DuckJibe · Post by **DuckJibe** » Sun Mar 14, 2004 6:05 pm

I'm using MM 2.1 Build 1596

There are special caracters in some tags but not all tags.

I can see no Tags in MM from any mp3 ( even mp3 without
special caracters) but the mp3 contains idv1 & idv2 tags !
I can read them with winamp.

I've just seen that when I browse with MM in the directory
containing the mp3, the mp3 tags appears uncorrectly
we can see only ' square" caracters

I have no problem in MM with special caracteres like "é è ç à" 'm
using all the time ... since I'm french !

Maybe you try the software K-mp3.
If you tag some files ( you need a complete album) & import them
in MM you'll see the problem for sure !

Pablo · Post by **Pablo** » Sun Mar 14, 2004 9:08 pm

My guess from similar (but different) problems I came accross is that MediaMonkey adheres to the standards very strictly. Maybe K-mp3 is slightly off the standards and this causes the problem.

You may want to try the latest alpha version of MM 2.2. It solved some problems I had with tags. And now you can choose among several languages, including French! This is an alpha version so it's for regular testers only, but it seems quite stable. As long as you backup your database regularly, you should be ok.

Pablo

duckjibe · Post by **duckjibe** » Tue Mar 16, 2004 6:14 am

I asked the question on K-MP3 forum,

K-MP3 tags in ID3v2.4 + Unicode.

Does MM supports this ?

Post by **jiri** » Tue Mar 16, 2004 6:39 am

Have you tried the latest MediaMonkey 2.2 beta 1? There were some changes in tag operations since MM 2.1, maybe your problem was fixed. MM also should be able to read ID3v2.4 tags, in case you are unsuccessful with MM 2.2, e-mail me some shorter track that has the described problem and I'll try to look into it.

Jiri

Duckjibe · Post by **Duckjibe** » Tue Mar 16, 2004 2:11 pm

I've just downloaded MM 2.2.1 721

But the problem remains the same, MM cannot read the tags.

I'lll send you a MP3 so that you can try to see what is wrong

Post by **jiri** » Tue Mar 16, 2004 3:44 pm

Thanks, I received the file and tested it. The result is:

- The problem is at K-MP3 side. It writes Unicode strings (of type '1' in ID3v2 terminology) and all such strings _must_ start with Unicode BOM (0xFEFF integer) according to ID3v2.x specification.

- Even though it isn't MM problem, I made a little change so that MM expects strings in little-endian format which is common on PCs. However, this change is only in order to prevent problems with _improperly_ formatted ID3v2 tags.

Jiri

DuckJibe · Post by **DuckJibe** » Tue Mar 16, 2004 6:15 pm

The K-MP3 Programmer will have a look at the point & release a new version
if there is a bug.

Anyway, I think it is a good point if you accept "_improperly_ formatted ID3v2 tag"

So Ill keep incorrect mp3 to test it

Thanks for your analyse

Duck

Kyle_Katarn · Post by **Kyle_Katarn** » Thu Mar 18, 2004 5:22 pm

Hello,

I'm the developper of K-MP3.

Thank you for reporting the BOM bug.
I've fixed it in my latest "internal" release but it seems that there are still a problem with MM, just like if it tried to display the trailing $00 00 of my unicode strings.

You can grab the latest beta here : ftp://ftp2.kcsoftwares.com/kcsoftwa/beta

Please confirm.
I'm glad to see that mutual help is possible with you, unlike with PP (Foobar's dev).

THANK YOU.

Post by **jiri** » Fri Mar 19, 2004 6:09 am

Although it isn't really common to include the trailing $00 00 sequence in ID3v2 strings, you are right that the zeroes as well as any subsequent text must be ignored. It will be fixed in the next release.

Thanks,
Jiri

Kyle_Katarn · Post by **Kyle_Katarn** » Fri Mar 19, 2004 6:18 am

Perfect.
Thank you for advice.

$00 00 is explicitely required by ID3v2 specs.

Post by **jiri** » Fri Mar 19, 2004 7:29 am

You are right that ID3v2.4 explicitely _requires_ termination of all strings. ID3v2.3 is a bit vague in the definition, but my understanding is that the terminating zeroes are only optional (except for some cases where the frame continues after the first string, e.g. WXXX frame). Windows XP Explorer doesn't terminate strings, I think that most of the applications do the same thing.

Jiri