![]() It can be funny when working on a live release and realise you are then finding it has been associated to a totally different concert by just one uploader. ![]() There are counts of the number of submissions for an acoustID source, so this helps to spot the rogues and disable them. This is the Picard users who get Picard hunting through hundreds of tracks in one hit. I think one of the biggest ways things get tangled are VA collections as you can see a number of legit recordings all associated on one AcoustID, and then suddenly you have a very unrelated track attached. Like I spend too much time looking at recordings and AcoustIDs attached. The program is called “acoustid-fingerprinter.app” on OS X… and it was last updated in 2011. This is pure speculation by me… but also explains the evidence… If you look in the AcoustID database directly, you’ll notice a lot of AcoustIDs have a list of artist names and song titles, with a bunch of slight variations in spelling and capitalization, (and occasionally something completely obviously wrong), and a count of how many times that particular tag has been seen by users…Īnd, I think, Picard uses some of that data too when it tries to “guess” what a recording is, if there is currently no AcoustID linked to any MBID recording…Īnd then once Picard does that… whatever wrong info someone once had in a file somewhere, is close enough for Picard to put the two together… and then… if the user hits “Submit AcoustID” without noticing the error… it now becomes officially linked together in the database. Oh, also! There is another program besides Picard, which you can use to submit new AcoustIDs… and it does not require any MBIDs, so it doesn’t actually link the AcoustIDs to any particular recordings, but it does submit whatever random strings are currently attached to the audio files at the time… no matter how possibly wrong the info the those tags may be! (Also AcoustID ignores any recording shorter then 30 seconds in total duration.) Something else that’s not well documented about AcoustIDs, is that they only identify the first 120 seconds of any recording… if you have two different recordings, which are identical for the first two minutes, and then diverge, AcoustID will be unable to tell them apart. Oh yeah, there’s these docs too: AcoustID - MusicBrainz Wiki but they don’t go into a lot of detail… It mostly seemed to match things up based on time duration… so, two songs that just happened to be the same length would be associated in Picard… and if the user didn’t notice, and they hit the “Submit AcoustIDs” button… now everyone else in the future will be confused as to why this recording is so badly misidentified.Īlso if you drag and drop a bunch of recordings onto the wrong album in Picard, it’ll try to do this associating too, and then if you don’t notice before hitting “Submit AcoustIDs” (like, you thought you were submitting something else…) then things will also be mixed up. ![]() 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |