Recording showing on stats is not the same as Listens page

ListenBrainz
1

While reviewing my stats page for this week, I noticed that I supposedly listened to the prologue to Hook twice: (Prologue and John Williams are grey since I clicked the link)

image
image475×251 43.5 KB

However, I never listened to the prologue of Hook this week (I don’t have the CD for it). Instead, I listened to the prologue of Harry Potter:
image
image952×233 47.3 KB

(This is the one time from Monday)
Additionally I listened to the Oliver and Company soundtrack release of Once Upon a Time in NYC, which upon reviewing that recording, the recording that shows on the stat page is not the same one either that I listened to. To me, It appears that the stats page is just matching recording title and artist. As seen with the Prologue, this causes problems when an artist (often in cases like soundtracks) has released multiple recordings with the same title, but aren’t related at all. And in the case of Once Upon a Time in NYC, the wrong recording gets selected (although it appears to be the same, but a version from a Compilation release). Is it possible to fix this? (I would think just using the recording ID and computing the track name, artist and album would be better)
Thanks, 14Super60pa

1 Like
2

Currently it’s not possible to tell listenbrainz from which album you listened to it. It’s planned, but not there yet.
Most times it matches the first inserted release in MB

1 Like
3

I’m using Jellyfin LB plugin and from what I can tell (I haven’t dug into the source of the plug-in yet) it has always successfully matched what I listen to on Jellyfin to the listens page on LB.

4

IIRC the plugging have been made so that the thumbnail match. But the statistic don’t care yet.

1 Like
5

It will be huge when the stats match up!

6

I’m more on the side of a listen of a recording should count for all releases, but yeah

1 Like
7

I can see that logic if it was linked to the “main” release reliably, e.g. the full album that the song first appeared on…

8

I don’t think that’s the problem. I like to tag my recording on picard with the release with the first release/single release for those sweet cover arts.
But if I listen to the single release, then the rest of the album, if the first recording count only for the single release, then I haven’t listened to the album fully according to the stats.

it’s also neat to see how much your are listening to a compilation release that you don’t even own, but your recording were rereleased in it

Edit: I mean release groups. Releases can be ignored

1 Like
9

I think ultimately we don’t want to choose but want to have it both ways right? We want to be able to check how often we’ve listened to the tracks on the compilation itself and/or elsewhere. Just like we might want to be able to see how often we’ve listened to a particular song (all recordings included) and how often we’ve listened to each different recording of that same song. Just like I’d very much appreciate an overview of most listened works. Would be interesting to see which work is most popular across all of LB.

I like to think of LB as being quite rudimentary right now. That’s not meant to downplay the incredible shape it’s in already, but meant to highlight the beautiful possibilities out there. The beauty of LB is that it’s ever evolving and with enough support could in the future be tailored to everyone need. As long as the data that we gather is as complete as possible, then it can be displayed in all sorts of ways in the future.

1 Like
10

Hi there! I apologize in advance for necro-ing this thread (is a year and a half too long?), but this is the one that I’m in the same boat with.

I was just wondering if there was any more information on this front, because it’s managed to confuse me quite a bit. I’m scrobbling to ListenBrainz via Navidrome, which seems to be passing all the relevant information including the release, recording, and release group IDs. Each individual listen is matched to the expected release. I can click “Open in Musicbrainz” for each release, and get the expected result. Clicking on the track takes me to the album, as expected.

Example of inspected listen, showing data passed to LB 
{
  "inserted_at": 1777145684,
  "listened_at": 1777144927,
  "recording_msid": "f8745896-8bf8-43b2-8789-6870e8e0658f",
  "track_metadata": {
    "additional_info": {
      "artist_mbids": [
        "e5c7b94f-e264-473c-bb0f-37c85d4d5c70"
      ],
      "artist_names": [
        "Belle and Sebastian"
      ],
      "duration_ms": 298170,
      "recording_mbid": "bbe7bd1f-61c7-404d-811e-2bf42ca4b9cc",
      "recording_msid": "f8745896-8bf8-43b2-8789-6870e8e0658f",
      "release_group_mbid": "25f3f7bf-f308-390c-b512-e0d4caaa8417",
      "release_mbid": "e9a19db6-155e-449b-9fb3-a2a9d9224712",
      "submission_client": "navidrome",
      "submission_client_version": "0.61.1-SNAPSHOT (664217f3)",
      "tracknumber": 2
    },
    "artist_name": "Belle and Sebastian",
    "mbid_mapping": {
      "artist_mbids": [
        "e5c7b94f-e264-473c-bb0f-37c85d4d5c70"
      ],
      "artists": [
        {
          "artist_credit_name": "Belle & Sebastian",
          "artist_mbid": "e5c7b94f-e264-473c-bb0f-37c85d4d5c70",
          "join_phrase": ""
        }
      ],
      "caa_id": 2985927666,
      "caa_release_mbid": "b407c978-7336-392b-a8bc-bdce9d8622a6",
      "recording_mbid": "bbe7bd1f-61c7-404d-811e-2bf42ca4b9cc",
      "recording_name": "Sleep the Clock Around",
      "release_mbid": "ea7b829c-3de6-33a6-8303-7101b3e669c6"
    },
    "release_name": "The Boy With the Arab Strap",
    "track_name": "Sleep the Clock Around"
  },
  "user_name": "nemiko"
}

Exclusively on the stats page, however, I repeatedly get tracks showing up as under a different release. Usually, it’s a handful of tracks from a release getting matched to something else. Obviously, this diminishes the usefulness of the stats page to begin with.

As an example, I’ve listened to Belle & Sebastian’s The Boy With the Arab Strap quite a few times. Each time, it’s scrobbled as expected, with each track matched to the correct release on MB. When LB coalesces these scrobbles into stats, two of the listens get credited to a bootleg, and another two to yet another bootleg. Judging by the listening numbers on those releases, it appears I’m not alone in this situation with this specific album, but as OP shows, it’s a more general issue.

image
image457×437 68.8 KB

This is something that can be seen throughout my LB stats, with some tracks consistently attributed to different releases than was scrobbled: singles, bootlegs, live albums, etc. My question is twofold - is there a way to fix this on my end? If not, are there any plans to improve this? Thanks :slight_smile:

2 Likes
11

Hello!

Necro-ing is justified, as we still have not resolved this issue…

The answers to your questions are: no, unfortunately nothing you can do on your end and and emphatic YES! we definitely want to fix this annoying issue, very much so.

We are working on big infrastructure changes to improve many things, including this particular issue.

2 Likes