How does scrobble matching decide between multiple releases?

[SiKreuz]

How are scrobbles matched to existing tracks?

I’m running into a case where I would expect a song to be associated with a different release (the single instead of the album). I checked what was actually scrobbled, and I’m fairly certain the correct release was submitted. I didn’t find a relevant log entry in koito, but both multi-scrobbler and my maloja instance logged the correct album.

For some reason, the track ends up being scrobbled under the album release (Europa – Premium Edition) instead of the single (Nackert). The two even have different track durations.

This made me wonder: what criteria are used to map a scrobble to an existing track, and is there any way to influence or modify this behavior?

Log from multi-scrobbler with correct musicbrainz ids:

- Original
+ musicbrainz-MyMB

  Title        : Nackert
  Artists      : LaBrassBanda
  Album Artists: (None)
  Album        : Nackert
  Meta         :
- * brainz-album: 58f77034-38ab-422f-aca3-5375e284886a
- * brainz-track: 03fc5a71-d803-4e3d-857b-c4d8609f87ed
+ * brainz-album: bfec04c0-94ed-4964-b69a-fd214d9d2ad4
+ * brainz-artist: cd261e77-63b3-4cc1-b901-ebb97a56e89f
+ * brainz-track: 2f480a14-3253-4a5e-bbda-1addc8d11d1a
+ * brainz-releaseGroup: 2c99543c-f167-4226-83f4-bcec48362b6b

Log from maloja:

[database] Incoming scrobble [Client: scrobbler | API: native/v1]: {'track_artists': ['LaBrassBanda'], 'track_title': 'Nackert', 'album_title': 'Nackert', 'track_length': 210, 'scrobble_time': 1767186162}

[gabehf]

The logic for matching scrobbles to tracks is within internal/catalog/associate_track.go. The way Koito handles it is it first looks for a MusicBrainz ID match, and if none is found it will try to match by the title and artist(s) of the track.

As of now, Koito does not consider tracks distinct when they have the same title and artist but are from different releases. I'm looking into changing that now.