1232 Unsynchronized tracks lists EVERY track #5454

[IDisposable]

I always keep my track tags in sync, so imagine my surprise when Build 1232 declare all 8000+ of them out of sync. They all were highlighting the Release Date column so I assume something's borked in that logic. Note that this happens with tracks tagged with only a year AND with tracks tagged with a complete date.

[Timo_Beil]

My complete library is unsynchronized (year).
The TYER tag had been changed in .1231. Perhaps this results in that effect?
-- Timo

[Bex]

Thanks, it was easy to reproduce. I've reopened the Mantis issue Timo linked to:
http://www.ventismedia.com/mantis/view.php?id=5454

[Bex]

This is fixed in build 1233.

[Friedrich]

This is fixed in build 1233.

Seems to be back again in 1247 (Windows 2000 Professional)

Another thread, referring to the same problem:
http://www.mediamonkey.com/forum/viewto ... =6&t=39634

[gpzbc]

yes, I noticed that about 2000 of my 14,000 tags are supposedly unsynchronized with the installation of build 1247. And they weren't unsynchronized in build 1244.
I noticed that 98% of the songs that supposedly have unsynchronized tags have a blank date field. That missing date is being highlighted when I check for unsynchronized tags.

[fourteen]

I noticed that 98% of the songs that supposedly have unsynchronized tags have a blank date field. That missing date is being highlighted when I check for unsynchronized tags.

We don't know what Date field/tag value is actually stored in the track, do we? Is the value displayed (i.e. empty/blank) the value stored in the track or the value stored in the database?

We do know, by MediaMonkey highlighting the Date field, that there is a discrepancy between the values in the track and in the database, but I am not sure we know what value is currently stored in the track and what value is currently stored in the database. And we don't know what "the other value" is - the value that is unsynchronized - that will presumably be wiped out and overwritten by a Synchronize Tags action.

[gpzbc]

no, I don't know. That has always been confusing to me. I wish the MM would show me the two values that are out of sync. For example, The date field is XX here and it is YY there. Then I could chose one or the other.
So anyways, I simply chose not to synchronize the tags for now. I figured I would just wait and let the problem get ironed out.

[fourteen]

So anyways, I simply chose not to synchronize the tags for now.

I think that is very smart. Especially given the fact that nothing changed in your database and nothing changed in your track/file. And pre-1247 MediaMonkey deemed the values synchronized, and 1247 deems the values different. So, if we do a synchronize we don't know what will get wiped out and thus what metadata will get lost.

Luckily for me, I only have a few of these files.

[rusty]

Thanks. Tracked at: http://www.ventismedia.com/mantis/view.php?id=5651

-Rusty