Other ways to determine Db/Tag Mismatches?

[Chondog]

So, in MM5 (RC2), I tried to use the "Files to Edit" node to identify db/Tag mismatches, but it was taking a huge amount of time to process over 7000 folders. It seemed to eventually stop reading (i.e. froze) after about 2000 folders.

Is there another way to determine (more efficiently) the db/Tag mismatches?

[Lowlander]

Use Collections to filter the amount of files. With a smaller Collection the process should be faster.

[Chondog]

So I ran files to edit/db and tag mismatches. It came up with a few hundred "mismatches" and the problem fields are highlighted. I read through the wiki where it walks through updating and cleaning tags.

How do I know when the db and tags match after cleaning? I highlight the tracks in question, clean tags and then update tags. I figured that would take care of it, but the tracks don't disappear from the db/tag mismatches after processing. Should they disappear from that window?

Also, when a field is highlighted representing a mismatch, can I do something with just that field to fix it? When i go to properties it doesn't look like anything is incorrect.

[Lowlander]

They should disappear after running it again. So leave the node and select it again.