AcoustID

Hello Tom,

> > Something completely different: It seems that some audio fingerprints
> > are misdetected (meaning that one fingerprint has a bunch of results
> > with high score, but not all of the correct recording). I tested a live
> > version, but it found also the regular version and one even a cover from
> > a different group - I assume that either an algorithm has wrongly
> > assigned the songs metadata to the recording or a user has entered wrong
> > artist information)...
> >
>
> Yes, this is very common and my understanding is this is usually
> incorrectly submitted  data. Various software submits acoustids so
> depending on how it's set up and what the user selects or what their
> existing data is, incorrect acoustids can end up attached. Although
> I'd say if there's been a lot of submissions the right recording tends
> to have many more.
> Having said which...
> Sometimes two (or more) recordings will have one acoustid. These are
> usually really similar mixes. Vice versa one recording can have
> multiple acoustids because for example the speed has changed between
> released versions or one is truncated in a way we consider to be
> insufficient to treat as two different recordings.
>
Thank you for the detailed explanation! I thought that it might be that 
way...

If I understood correctly, the AcoustIDs itself are stored on 
Acoustid.org server externally.
Are there any references from Musicbrainz tables (e.g. a GUID) to the 
data on Acoustid.org, or are they link all from AcoustID.org back to 
Musicbrainz (so that the AcoustId.org API need to be called in order to 
display which fingerprints are assigned to a recording for display on 
the Musicbrainz webpage)? I didn't found any reference for it in the 
CreateTables.sql script...

Thanks in forward for your answer!

Best regards,

Andre