Re: Data Import Policy

Tom Crocker <[email protected]> Tue, 12 May 2015 21:53:40 +0100
Newsgroups gmane.comp.audio.musicbrainz.devel
Message-ID <CAHmUbmfxx6G9b3gZHztR=tfq3DDtKNgZorp5ofLKwc4yEOKN0Q@mail.gmail.com>
--===============1359910060==
Content-Type: multipart/alternative; boundary=f46d04448167728ce20515e8b099

--f46d04448167728ce20515e8b099
Content-Type: text/plain; charset=UTF-8

On 12 May 2015 21:22, "Andre Wiethoff" <[email protected]> wrote:
>
...
>
> 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.

--f46d04448167728ce20515e8b099
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On 12 May 2015 21:22, &quot;Andre Wiethoff&quot; &lt;<a href=3D"mailto:brai=
[email protected]">[email protected]</a>&gt; wrote:<br>
&gt;<br>
...<br>
&gt;<br>
&gt; Something completely different: It seems that some audio fingerprints<=
br>
&gt; are misdetected (meaning that one fingerprint has a bunch of results<b=
r>
&gt; with high score, but not all of the correct recording). I tested a liv=
e<br>
&gt; version, but it found also the regular version and one even a cover fr=
om<br>
&gt; a different group - I assume that either an algorithm has wrongly<br>
&gt; assigned the songs metadata to the recording or a user has entered wro=
ng<br>
&gt; artist information)...<br>
&gt;</p>
<p dir=3D"ltr">Yes, this is very common and my understanding is this is usu=
ally incorrectly submitted=C2=A0 data. Various software submits acoustids s=
o depending on how it&#39;s set up and what the user selects or what their =
existing data is, incorrect acoustids can end up attached. Although I&#39;d=
 say if there&#39;s been a lot of submissions the right recording tends to =
have many more. <br>
Having said which...<br>
Sometimes two (or more) recordings will have one acoustid. These are usuall=
y really similar mixes. Vice versa one recording can have multiple acoustid=
s because for example the speed has changed between released versions or on=
e is truncated in a way we consider to be insufficient to treat as two diff=
erent recordings.</p>

--f46d04448167728ce20515e8b099--


--===============1359910060==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MusicBrainz-devel mailing list
[email protected]
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel
--===============1359910060==--