ListenBrainz

Feedback
1

The ListenBrainz support new in v2.67 seems to be working perfectly, including for live radio. And Roon ARC.

Thanks very much indeed for adding this.

It would be nice if it were possible to upload my 5 years of Roon history into it (I wasn’t previously using last.fm), but it’s still great.

2

Definitely agreed; ListenBrainz support was probably my #1 most wanted feature in Roon, so I’m very glad to see it.

I was a little disappointed to find that it doesn’t seem to be submitting any MusicBrainz IDs read from the file metadata along with the scrobbles; hopefully this is something that can be added in a future update. Adding MBIDs makes it much easier for ListenBrainz to properly match listens to the correct recordings and releases in the MusicBrainz database.

2 Likes
3

I’m seeing some mbid in the data… not sure if this is what you mean?

{
“inserted_at”: 1779839970,
“listened_at”: 1779839691,
“recording_msid”: “08543273-d3c8-45b0-8432-5de0fc929535”,
“track_metadata”: {
“additional_info”: {
“duration_ms”: 278000,
“recording_msid”: “08543273-d3c8-45b0-8432-5de0fc929535”,
“submission_client”: “Roon”,
“submission_client_version”: “Roon”
},
“artist_name”: “Van Morrison”,
“mbid_mapping”: {
“artist_mbids”: [
“a41ac10f-0a56-4672-9161-b83f9b223559”
],
“artists”: [
{
“artist_credit_name”: “Van Morrison”,
“artist_mbid”: “a41ac10f-0a56-4672-9161-b83f9b223559”,
“join_phrase”: “”
}
],
“caa_id”: 7471421537,
“caa_release_mbid”: “f93751c8-4c35-4bb4-b935-83dc32212939”,
“recording_mbid”: “6bf69cec-254f-4b2a-b99a-5c844572d45e”,
“recording_name”: “Gypsy”,
“release_mbid”: “d7fbc257-c44c-4c7c-97a8-c32a6c62c964”
},
“release_name”: “Saint Dominic’s Preview”,
“track_name”: “Gypsy”
},
“user_name”: “cdmackay”
}

That release MBID is valid: Verifying your browser

4

That looks like the ListenBrainz mapper was able to match that one to MBIDs based on the metadata submitted, but Roon itself is not submitting them. See this example:

{
  "inserted_at": 1779843615,
  "listened_at": 1779843568,
  "recording_msid": "93d25722-079d-462b-8126-a5cbb297604f",
  "track_metadata": {
    "additional_info": {
      "duration_ms": 47000,
      "recording_msid": "93d25722-079d-462b-8126-a5cbb297604f",
      "submission_client": "Roon",
      "submission_client_version": "Roon"
    },
    "artist_name": "on4word",
    "release_name": "Parallel Universe 46",
    "track_name": "Parallel Universes"
  },
  "user_name": "NotTheJohn"
}

which should be this recording: Verifying your browser

If it’s not able to automatically match it is possible to do manual matches through the website, but obviously it would be better for Roon to submit the IDs in the first place given that it has access to the files being played which are ideally already tagged with them.

5

Got it; interesting, thanks.

6

You ought to add a feature request in Feedback > Feature Suggestions.

1 Like
7

8 posts were split to a new topic: Roon natively supports ListenBrainz scrobbling

8

Done:

1 Like
9

This topic is specifically about Roon not passing MBID (specific version information) to ListenBrainz.

I’ve moved discussion items to a new thread so as not to dilute the feedback provided here.

10

It wasn’t in fact, but that’s fine :slight_smile:

11

You are correct, it was positive feedback followed by a comment about importing history. I see you replied to a comment about the release ID, which is now a feature suggestion.

However, the posts I moved were general discussion about ListenBrainz, and diluted the general feedback nature of this thread.

1 Like