I can have a track that has a 100 match score within the “Search for similar tracks” dialogue (using the default search query), but the “Match” functionality says that there’s no match above the threshold. If I load the matching track from the “Search for similar tracks dialogue”, the only modified tag is Genre, which goes from null to having a value.
The default query was
track:(Lune) artist:(Tim Green) release:(Eastbound Silhouette) tnum:(4) tracks:(0) qdur:(283)
I tried playing around with the “Tags to ignore for comparison” setting, ignoring everything except for track title and artist name, but this made no difference. The only way that I was able to get the track to match with the first 100 match score item listed in the “Search for similar tracks” dialogue was to reduce the threshold setting from 70% to 60%.
Perhaps the “Tags to ignore for comparison” setting is broken?
FWIW I have an example track that had the following fields matching exactly:
- Title (“Name” in the similar tracks dialogue)
- Album (“Release” in the similar tracks dialogue)
Perhaps there is a mapping issue between Title>Name or Album>Release?
The only potential mismatch is the following field:
- Date (2022 in original tags, but 2022-10-28 in the similar tracks dialog)
Perhaps there is a match % issue with the date value?
The other tags that already existed on my track (that do not appear as columns in the “Search for similar tracks” dialogue) were:
- Track Number (set)
- AcousticID Fingerprint (set)
- Disc Number (set)
- Total Discs (set)
- Total Tracks (set)
Perhaps there is an issue whereby additional original fields reduce the match %?
The columns that appear in the similar tracks dialogue that weren’t already tags on my track were:
- Country (set)
- Type (null)
Perhaps there is an issue with null values, or Preferred Release Types/Countries/Formats? Or perhaps there are mismatching fields that are not displayed within the similar tracks dialogue? Does Picard score tag matches prioritising certain tags, eg. title, artist, before other tags? It would be nice to be able to customise this. Do the Preferred Release Type settings lower the match % (esp. if the database returns a null value for that tag)? They shouldn’t.
FWIW the following missing tags that appear in the similar tracks dialogue do not get added as new values:
- Date (2022-10-28, maintains original value of 2022)
- Country (XW)
- Type (null)
This issue has left me perplexed - please help! I cannot afford the time to manually select results from the similar tracks dialogue as I have a lot of single tracks in my collection that are from albums.