Mismatched picture representing recording and actual releases

ListenBrainz
, , ,
1

(This is my first time here so I apologize if I make any mistakes)

On certain recordings in Listenbrainz, the pictures representing the recording will be from a different release. None of the other releases contain the recording, but a different, similarly named one. Inspecting the listens find that they are both linked to the wrong release.

Inspecting this listen:

{
  "listened_at": 0,
  "track_metadata": {
    "artist_name": "Каскад",
    "track_name": "Шли сегодня танки",
    "release_name": "Концерт в Баграме",
    "additional_info": {
      "duration_ms": 168000,
      "recording_mbid": "6cc02b99-0aea-4377-809f-0fd89616eda8",
      "artist_mbids": [
        "b823f87a-b89f-4d7e-844e-db7a11062aa1"
      ]
    },
    "mbid_mapping": {
      "artist_mbids": [
        "b823f87a-b89f-4d7e-844e-db7a11062aa1"
      ],
      "artists": [
        {
          "artist_credit_name": "Каскад",
          "artist_mbid": "b823f87a-b89f-4d7e-844e-db7a11062aa1",
          "join_phrase": ""
        }
      ],
      "recording_mbid": "6cc02b99-0aea-4377-809f-0fd89616eda8",
      "release_mbid": "58c92be4-ccbf-4d49-ae02-c7b5f6d96380",
      "caa_id": 42225244420,
      "caa_release_mbid": "58c92be4-ccbf-4d49-ae02-c7b5f6d96380"
    }
  },
  "user_name": null,
  "listened_at_iso": "2025-09-28T07:46:44.600642+00:00"
}

Finds that it has the “release_mbid” as 58c92be4-ccbf-4d49-ae02-c7b5f6d96380 when it should be either b5b11692-e5a2-4431-8273-b7d5bc75943e or f1df092b-3810-4c7b-983e-cae1fd4ffe44, the releases that actually has the recording. The “release_name” field is also incorrect.

The same issue happens with this other recording, with the “release_mbid” being 7c48bdae-f1c8-475f-9b1f-7433ecc834c3 instead of either 3ad3ba44-0e2a-4e54-8729-30f40aef258b or 60269463-3998-410e-abfb-9471b817a54f. The “release_name” field is wrong here as well:

{
  "listened_at": 0,
  "track_metadata": {
    "artist_name": "Lovejoy",
    "track_name": "One Day",
    "release_name": "One Day / Sex Sells",
    "additional_info": {
      "duration_ms": 144616,
      "recording_mbid": "4efd6eb0-386e-4a2a-bade-424356e0d09e",
      "artist_mbids": [
        "deefd67b-c917-4b0d-ab48-c5af7f92cd82"
      ]
    },
    "mbid_mapping": {
      "artist_mbids": [
        "deefd67b-c917-4b0d-ab48-c5af7f92cd82"
      ],
      "artists": [
        {
          "artist_credit_name": "Lovejoy",
          "artist_mbid": "deefd67b-c917-4b0d-ab48-c5af7f92cd82",
          "join_phrase": ""
        }
      ],
      "recording_mbid": "4efd6eb0-386e-4a2a-bade-424356e0d09e",
      "release_mbid": "7c48bdae-f1c8-475f-9b1f-7433ecc834c3",
      "caa_id": 38609966261,
      "caa_release_mbid": "7c48bdae-f1c8-475f-9b1f-7433ecc834c3"
    }
  },
  "user_name": null,
  "listened_at_iso": "2025-09-28T08:08:00.802867+00:00"
}

I don’t know what the algorithm is for picking the recordings but I think this is not the intended behavior

2 Likes
2

Hi!

Yes, the current mapping system does not use the release name in the mapping process. The good new is that I am in the middle of writing a better, more scalable mapper. Hopefully that will be released in a few weeks.

12 Likes