MediaMonkey forum

Hi all,

using MM 2.586 and found that "Unsynchronized Tags" (Tree View, "Files To Edit") all of a sudden shows a lot of files that weren't there before, were correctly tagged before and have no highlighted items at all.

If I use "Tools | Advanced Tag Management | Synchronize Tags" on them (or other files), the status bar shows that something is happening but hitting refresh will - after rebuilding the list - still show the same titles.

Is there another new configuration option I've missed or is this a problem?

Cheers, Susanne

Read around the forum and you'll find similar posts.

There were some minor problems, try the next release (it should be out within a day) and let us know if it's ok there, please.

Thanks,
Jiri

The weekend is saved!

Tralla,

The change that we made actually occurred in build 584 (internal build) -- prior to build 586. At the moment, both you and Jake Ames (see http://www.songs-db.com/forum/viewtopic.php?t=759) are reporting problems with this function, but I'm having trouble replicating them.

From your description, the cause of the files appearing can be desynchronization that isn't apparent (e.g. a space or tab, etc.), or a bug.

To rule out the first possibility can you try the following on a couple of the files that show up for no apparent reason:
a) Select them, and Clean their tags (v1 and v2) (from Advanced Tagging menu)
b) Select them, and Synchronize their tags (from the same menu)
c) Reload the unsynchronized tags node. Do the tracks still appear?

If the tracks still appear in the 'unsynchronized tracks', please e-mail Jiri and I a couple of the smaller ones so we can get to the bottom of this. If the tracks don't appear in the 'unsynchronized tracks', then the issue was most likely caused by something in the tags preventing a complete update.

thx.

-Rusty

Rusty,

Tried your three steps on three files. It worked on one, didn't work on two. As you suggested, I sent you email with a link to those two files.

Cheers, Susanne

Thx for the files. As mentioned offline, they helped Jiri find that newline characters in the comments field can cause the problem. This will be resolved in the next build.

-Rusty