Fetching wrong ISRC

info's Avatar


25 Mar, 2021 08:34 AM

I did a comparison on key detection here:

To obtain missing ISRC for some tracks, I used beaTunes to get them using the following settings:

Turns out beaTunes (sometimes?) fetching wrong ISRC.

An example track attached.
It fetches the ISRC: USUM70502664 which is a different track by the same artist.
In my opinion, it should fetch USUM70500143 instead.

Who to blame?

Built Feb 22,2021
Windows 10 10.0
No iTunes

Just MP3tag to inspect ISRC tag and copy/paste that into https://isrcsearch.ifpi.org/#!/search (look up by code)

  1. 1 Posted by info on 25 Mar, 2021 09:18 AM

    info's Avatar

    A more extreme example, where they don't resemble anything, at all musical or artist nor title wise:

    local track:

    but fetched isrc of:

  2. 2 Posted by info on 25 Mar, 2021 09:32 AM

    info's Avatar

    This next example is so different musical, that I have no clue how it can fetch this, when I assume its using acousticID or some sorts, to detect it:

    local track:

    fetches ISRC of:

  3. 3 Posted by info on 25 Mar, 2021 09:42 AM

    info's Avatar

    I'll probably find more faulty fetched ISRCs, but I'm getting annoyed.
    One last example, since then u should have an idea.

    local track:

    fetched ISRC of:

  4. 4 Posted by info on 25 Mar, 2021 09:45 PM

    info's Avatar
  5. Support Staff 5 Posted by hendrik on 26 Mar, 2021 05:55 PM

    hendrik's Avatar


    the ISRCs in beaTunes are fetched from the central database, which is fed by MusicBrainz and user data. Neither is necessarily 100% correct, though MusicBrainz data certainly has the higher quality.

    That said—and I am aware that this does not cover all the cases you mention—I believe different ISRCs may be assigned to multiple acoustically identical tracks, if they have been released in multiple years or on multiple albums. So forcing lookup via fingerprint is probably a bad idea.

    Hope this sheds some light on things,


  6. 6 Posted by info on 27 Mar, 2021 11:36 AM

    info's Avatar

    Forcing lookup via fingerprint.... is that like AcousticID, like Shazam sort of?

    If I look the tracks up at MusicBrainz:

    Now where do those differences come from?
    If beaTunes would fetch them from MusicBrainz, I think they should have the following ISRC instead:

  7. Support Staff 7 Posted by hendrik on 27 Mar, 2021 12:27 PM

    hendrik's Avatar

    Forcing lookup via fingerprint.... is that like AcousticID, like Shazam sort of?

    Yes. And it only makes sense, when you have really bad or missing textual metadata.

  8. 8 Posted by info on 28 Mar, 2021 10:26 AM

    info's Avatar

    Ahh, thanks for clarifying that part!
    Good to know, there's no need to use fingerprint option, when there are tags that are supposedly correct inside the metadata, makes sense.
    Consider the issue fixed.

  9. Support Staff 9 Posted by hendrik on 28 Mar, 2021 11:04 AM

    hendrik's Avatar

    Actually, after some digging, I have found some issues, I’d like to address. I‘ll write more later.

  10. 10 Posted by info on 28 Mar, 2021 12:19 PM

    info's Avatar

    Ok, curious, let me know what you found out when possible.

  11. Support Staff 11 Posted by hendrik on 10 Apr, 2021 03:44 PM

    hendrik's Avatar


    sorry for not answering for so long.

    So first of all, beaTunes did not use Musicbrainz as reference for ISRCs. Also, ISRCs are unique per recording, i.e. they do not depend on the release (i.e. the album, CD, compilation etc.). Apologies for misstating this earlier.

    In the meantime, I have built a mechanism that does update the entries in the central beaTunes database with data from Musicbrainz. This means that starting now, beaTunes may actually use ISRCs from Musicbrainz. I am using "may actually" for a reason. The central beaTunes database consolidates a lot of user data with reference data from Musicbrainz and Discogs. It does this asynchronously, as data is requested from users. This means that some tracks may already be updated, but others are still in the update queue. To make sure that all relevant tracks are eventually updated, I have added them manually to the processing queue. But please understand that this may take a while (and frankly I cannot say how long—more popular tracks will be updated faster than rare tracks).

    Regarding lookup via acoustic fingerprint: What I said earlier is not wrong. Whenever you have halfway decent metadata (artist, title, album), do not force the lookup via fingerprint. This increases your chance of getting correct information about your particular version of a track.

    Hope this sheds some light on things.

    Have a great weekend,


Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Already uploaded files

  • 500_-_Kanye_West_-_Gold_Digger.mp3 3.25 MB

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac