I just tried and edited a track that is in the Music Collection in the My Computer node. I changed the Artist, went back to the Music Collection and the track shows the new value. No rescanning required.

Found it- still believe my last comment correctly describes the expected behavior. Didn't use the location node..

If you don't, you need to enabled it in the Media Tree settings.

Library > Location should be Music > Location (replace Music with the Collection you're tracks are in).

Not sure I follow: I did use the "My Computer" node. I do not ave a "Location" node.

In any case (whatever node) I believe MM should not mark changes as half-noticed. If it updates the timestamp/size in it's DB it should make sure that it understands the attributes at that time.

Try the Library > Location node instead of My Computer.

I was tagging in disk mode since:
- tagging a single album would have meant doing it for every song individually (as they had different album artists)
- and all compilations are in a single folder on disk

Yet- the changes were ignored upon rescanning, as if the file date change had already been registed in MM?

I'm not sure if I follow. If you change tags in MediaMonkey you don't need to scan the tracks to see these new tags or are you not tagging in the Library node?

Btw, the progress bar for the update operation is broken, see screenshot.

I've also seen the lower scroll bar extend to the right off the screen across the image.

Mhm. But that's only half-clean, is it? If it does update the file as changed it should read the new tags as well- in fact it did just write them to disk!

andig wrote:I've retagged all compilations and re-inserted the folders from disk. Result: 8000 items ignored (did not meet import criteria). I've found that the criterium in question is the "Only for files with changed timestamp or size" option that was enabled. I'm wondering why though- as both timestamp (should have) and filesize (must have) changed when updating to "Various" artist this should not have been a problem?

If you tagged in MediaMonkey, the new timestamp is also in the database so rescanning would ignore them.

Understood- strange only I've never noticed this with 3.x...

I've retagged all compilations and re-inserted the folders from disk. Result: 8000 items ignored (did not meet import criteria). I've found that the criterium in question is the "Only for files with changed timestamp or size" option that was enabled. I'm wondering why though- as both timestamp (should have) and filesize (must have) changed when updating to "Various" artist this should not have been a problem?

Best regards,
Andreas

Yes, otherwise all you're greatest hits albums would be one big Album. So MediaMonkey uses Album and Album Artist to determine what tracks belong to the same Album: http://www.mediamonkey.com/sw/webhelp/f ... erties.htm

Mhm. Will check that. But. Same Album is still same album and shouldn't take Album Artist into account, is it? Or is the logic here that an identically- named album with a different artist is a different album?

Sounds like you didn't tag your Album correctly, which is why the Album is shown multiple times. Makes sure all tracks on the Album have the same Album Artist. Otherwise a screenshot might be helpful.

Steps to reproduce (example):

1) Search "Dog eat dog" (band) in "Entire Library" -> "Contains dog eat dog" gives 3 results, one from Album "Fetenhits Party Classics"
2) Find more from same album "Fetenhits Party Classics" -> gives 1 result (subset from above search)

Explorer shows "Fetenhits Party Classics" several times, the entry "Fetenhits Party Classics (Dog eat Dog)" is selected -> this seems to explain why there is only one result showing up.

The previous search criterium seems to be persisted.

3) Alternatively, search for "Fetenhits Party Classics" in "Entire Library" -> result list is 20+ items long, which shows that the result from 2) is wrong.

Best regards,
Andreas