Bug when track# is 256 - appears on unsynchronized node

[datprogrammer]

This is a simple one...

MM Version 2.3.1.845 on Windows XP

ANY Track that has a track number of 256 appears in the "Unsynchronized tags" node.

This one drove me nuts for days but I finally figured it out.

I had one track in unsynchromized tags list that just would not go away no matter what I did (clean tags, synch tags, even in desperation, manualy retype each tag).

I noticed that the track number was 256. Neing a programmer myself, that rang alarm bells, so I changed te track number - and yup, it went off the list. I changed another song to have track # 256 and tada! It shows up in the unsynchronized list.

Please fix!

[jiri]

This is because ID3v1 tag cannot have track# values >256. So any track with such number in MM library really isn't and cannot be properly synchronized with ID3v1.

Jiri

[datprogrammer]

But tracks over 256 work, it's just the number 256 itself (the collection is avtuially church hymns, over 300 of them, so I would like them all in the same album

[jiri]

Ok, I see, tracks>256 are propertly ignored but 256 accidentally isn't. This will be fixed in MM 2.5.

Thanks,
Jiri