I’m scrobbling listens from my navidrome server to ListenBrainz and they keep getting mismatched. One example is this:
{
"playing_now": true,
"track_metadata": {
"additional_info": {
"artist_mbids": [],
"artist_names": [
"西木康智"
],
"duration_ms": 206150,
"submission_client": "navidrome",
"submission_client_version": "0.58.5 (131c0c56)",
"tracknumber": 51
},
"artist_name": "西木康智",
"release_name": "OCTOPATH TRAVELER Original Soundtrack",
"track_name": "ボスバトル2",
"mbid_mapping": {
"recording_mbid": "f0438d99-9ecd-4ef3-ae1b-253fc5d81869",
"release_mbid": "ea640f54-a168-414e-8875-7bfcbf2518cb",
"artist_mbids": [
"181c4177-f33a-441d-b15d-910acaf18b07"
],
"caa_id": 23758992519,
"caa_release_mbid": "ea640f54-a168-414e-8875-7bfcbf2518cb",
"artists": [
{
"artist_credit_name": "西木康智",
"join_phrase": "",
"artist_mbid": "181c4177-f33a-441d-b15d-910acaf18b07"
}
]
}
}
}
The payload submitted by navidrome contains the release_name and tracknumber. And I expected it to be perfectly matched to 9edf73af-727b-4041-81cc-595ba17a40c8 but ListenBrainz instead matches it to ea640f54-a168-414e-8875-7bfcbf2518cb. This release doesn’t even have 51 tracks.
This only happens for some of the tracks. When I listen to the entire Album of 85 tracks most are matched correctly while a few are matched to one of two different releases. Most likely because only a subset of the tracks appears on other releases.
I know I could add the MusicBrainz release id to the metadata but I don’t believe that should be necessary when artist, title, release and track number uniquely identify the correct track and release. I would understand if it ended up on one of the other releases in the group but not a totally different release.
What’s the issue here and how, other than adding a tag with the release id, do I fix it?