Closed richardpowellus closed 9 years ago
The ID mismatch is probably coming from Chromaprint, not the tags themselves. Have you tried disabling that? If that changes anything, it's probably just a false negative from the fingerprint database.
Yep, you're right, that did appear to fix the issue. Is there a way to set up some sort of tolerance for this? i.e. if the choma signature is only slightly different consider it a match?
It's not really possible; the comparison is done server-side in the acoustid database. Unfortunately, false negatives are just a fact of life using a heuristic like fingerprinting.
Hi,
Every time I run: beet import /mnt/nas/music I see a bunch of entries like:
Beets shows a difference between the IDs and after I select 'k' (Keep Both) my assumption is that Beets would update the id tag of the 99.2% match to be a 100% match (i.e. fix the mismatch in the id) during the import process. However, this does not happen since if I run the beets import command again I will get the exact same prompt.
My current Beets config is as follows:
Note that I have the "scrub" plug-in enabled and I ran a manual "beet scrub album:'ultimate aerosmith' format:'aac'" before the import to no avail.