You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As stated in #122, ListenBrainz will not likely be supported due to limits with the ListenBrainz API that aren't going to change any time soon. I'm proposing that instead, supporters can import their ListenBrainz JSON user export much like they can with Spotify. Some users may have more, earlier data on ListenBrainz than on Spotify or Last.fm, thanks to its Last.fm/Libre.fm importing feature (I am personally in that camp), so having this would be nice for those users.
The track_name and artist_name is probably what you're looking for with these dumps. I'm not sure on how .fmbot handles featured artists in the title on Last.fm imports, but it's also something to keep a look out for with ListenBrainz.
I saw that MusicBrainz is used as the source for artist countries. I doubt .fmbot is/will be using MBIDs, but if MBID mapping is used, mbid_mapping is used by MusicBrainz's automatic resolver, which has some reliability issues but does have extended information that you would have to query MusicBrainz for. Any MBID data submitted manually by the user (i.e. from a scrobbler that submits the IDs) is under additional_info if you want to manually grab data from MusicBrainz.
recording_msid is used by MessyBrainz, which is used by ListenBrainz to automatically link messy metadata to MusicBrainz entities. It's not out for the public yet though AFAIK.
The text was updated successfully, but these errors were encountered:
As stated in #122, ListenBrainz will not likely be supported due to limits with the ListenBrainz API that aren't going to change any time soon. I'm proposing that instead, supporters can import their ListenBrainz JSON user export much like they can with Spotify. Some users may have more, earlier data on ListenBrainz than on Spotify or Last.fm, thanks to its Last.fm/Libre.fm importing feature (I am personally in that camp), so having this would be nice for those users.
I have attached a quick export dump from my ListenBrainz development account. listen_dev_thing_lb-2023-10-31.json
An example track listen can be seen here:
Some attributes to keep a look out for:
track_name
andartist_name
is probably what you're looking for with these dumps. I'm not sure on how .fmbot handles featured artists in the title on Last.fm imports, but it's also something to keep a look out for with ListenBrainz.mbid_mapping
is used by MusicBrainz's automatic resolver, which has some reliability issues but does have extended information that you would have to query MusicBrainz for. Any MBID data submitted manually by the user (i.e. from a scrobbler that submits the IDs) is underadditional_info
if you want to manually grab data from MusicBrainz.recording_msid
is used by MessyBrainz, which is used by ListenBrainz to automatically link messy metadata to MusicBrainz entities. It's not out for the public yet though AFAIK.The text was updated successfully, but these errors were encountered: