And I speculate that how this may have happened, is that in older versions of Picard, if you just dumped a few thousand MP3s or whatever into it, and then had some identified, and some not (yet)… you could hit a button to have Picard try and match things up, and many times it would get things spectacularity wrong. I have seen some very very wrong links between AcoustIDs and recording MBIDs before. I have personally, accidentally, submitted acoustIDs for the wrong tracks, and then had to immediate go to the MusicBrainz web site to unlink them so that in the future no one else would be confused by my mistake.
And, I think that Picard’s UI does not make it easy to see what exactly it is you are doing when you submit AcoustIDs… Even if you enable the obscure, hard-to-see, column that shows a red or grey colored squiggle next to a track when it thinks there’s a new AcoustID to submit… the data is still very opaque. So, about that erroneous attachment… How does this happen? Well, anybody can get an API key to submit new AcoustIDs from Picard… And then submitting new AcoudID association with Picard is really simple, really really simple… so easy that you can do it by accident. If you register as an editor on MusicBrainz, you can unlink any AcoustID from any recording it may have been erroneously attached to…
0 kommentar(er)
