P
psychoadept
Guest
I had a hiatus from Picard and MusicBrainz until a few of months ago, and I figured there would be changes to adjust to. The main thing I’ve noticed, to my surprise, is that Picard’s ability to look up single tracks seems to have gone haywire. Clusters are good, and scans are as good as they’ve ever been, but for single files I get some of the weirdest results.
I mean, it was always a little finicky based on settings for release type and so on, but I don’t remember it having any trouble with a well-tagged file. I tried resetting the release type filters to see if that helped, but I can’t tell that it has.
In the example below, the track was already tagged with almost all the details (99% match) and the correct release was loaded in Picard, and yet it matched to this other release with a 66% match.
How is Picard prioritizing results? I can make a ticket if I need to, I just feel like I’m losing my mind. I haven’t seen any sign of other people having the problem. (I know I can tweak the match thresholds but in something like 15 years of using Picard I’ve never had to.)
1 post - 1 participant
Read full topic
Continue reading...
I mean, it was always a little finicky based on settings for release type and so on, but I don’t remember it having any trouble with a well-tagged file. I tried resetting the release type filters to see if that helped, but I can’t tell that it has.
In the example below, the track was already tagged with almost all the details (99% match) and the correct release was loaded in Picard, and yet it matched to this other release with a 66% match.
How is Picard prioritizing results? I can make a ticket if I need to, I just feel like I’m losing my mind. I haven’t seen any sign of other people having the problem. (I know I can tweak the match thresholds but in something like 15 years of using Picard I’ve never had to.)
1 post - 1 participant
Read full topic
Continue reading...