Here is an example where just removing the lowest count is not an answer:
https://acoustid.org/track/f8bf526d-aa92-4cf9-9d16-940163002340
I noticed a pattern with a number of Pixes tracks all on the same Release. Here we see “Gigantic” having a length same as “Debaser”. So I chased down the rabbit hole and located the albums in the MB IDs. With a bit of detective work it showed the AcoustID was correct, it was the track title that was wrong. An “off by one” error on a couple of track lists.
It is an example of why we can’t just assume that the lone one is wrong and needs deleting. In this example it was right, just had the wrong name on the recording.
It is also something where AcoustID is really valuable in helping identify the error. Have had issues like this before.
(Note: For the completist, The AcoustID from this list that started that rabbit hole was this one: Track "324f18cb-30c4-4a97-802f-b71566e9d76d" | AcoustID)
@ulugabi - interesting what Picard does. As that MBID is enough then I’ll look slightly different at these now, but still will doubt a single track on its own. Funny how many I just wiped out tonight where a random Audiobook track had been linked to a music album. A good example of those editors who let Picard mass tag thousands of tracks and then upload AcoustID data without checking.
Has made me laugh working on this old 2019 list tonight. Especially when in the middle of Pink Floyd, I was recognising so many of these I had already sorted out in the last 18 months.