Report showing acoustids likely to be bad link to musicbrainz recordings

[ijabz]

@IvanDobsky

On rare occasions I have found that the wrong lengths are actual data errors on the Release. Manually typed values that are wrong. Majority of cases I agree these are nearly always wrong versions \ different mixes wrongly linked.

Certainly the case sometimes, but this can only be fixed really by preventing acoustids being linked to a musicbrainzid if outside a reasonable track length (20% should more than suffice). If the MusicBrainz track really is the right one but with the one wrong track length recorded then the submitter needs to fix the issue on MusicBrainz and then submit the pairing.

In the early days of Acoustid the priority would be increasing the size of the database as quickly as possible, but now it is a more mature product should be more careful about letting data in. Since Luks doesnt seem to be round much these days the easiest way to get this done would be implement changes in Picard, what do you think about this @outsidecontext and this

@IvanDobsky

This is all happening from “Lookup by Name” and no checking going on as to the results. Only have to watch the forums to see people who do “close enough” type lookups an 20000 tracks and then hit the pretty looking < Submit AcoustID > button because they don’t realize the damage it is about to do… that button needs hiding. (Especially if more than 100 tracks are being matched in one session)