Replies: 1 comment
-
|
Hi and thanks for checking out multi-scrobbler!
This is correct and the current limitation preventing what you want to do. This is currently an active area of development that will be resolved in two parts. Arbitrary Scrobble Time
This design choice is meant to help prevent duplicate scrobbles. MS checks the scrobbler's recent history before making any scrobbles to see if any match the data/timestamp. However, right now it only gets "recent" history and if the data to-be-scrobbled is older than the oldest scrobble found from recent, then it ignores it since it can't determine if it would be a duplicate or not. This is due to the real-time scrobbling design of MS. The backlog option you found is for filling in the gap for short periods of time when MS is not active. Like, the last 20-100 scrobbles. This will be mostly solved by PR #471 , which redesigns MS to re-fetch scrobbles from the scrobbler based on the time range of all the currently queued scrobbles, rather than just recent. Another user has this same issue. I'm hoping to have this released in the next couple of weeks. Be aware this only solves the time issue when the Source is providing MS new scrobbles that have an old timestamp. MS polls Sources based on "most recent" so if the Source sorts its data by when the track was played then "new" scrobbles with old times won't appear for MS to scrobble. This is where the next part comes in... Bulk Scrobble Transfers
The arbitrary scrobble time refactor sets up MS to implement bulk scrobble transfers between different services, currently on-hold in PR #390 . This will be a larger effort since it requires paginating all data from very different sources and keeping track of progress to be able to resume in the event of error or MS stopping. I don't have an ETA for this but it's close on the roadmap. If you don't want to wait for this to be done then
Is the right way to solve this. Then have MS handle "real time" scrobbling. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Intro
Hi I've been working on freeing myself from streaming services and bringing everything in locally and was hoping multi-scrobbler would be my solution to scrobbling
I set-up up Koito and fed in my import data from a streaming provider and set Koito as a source in multi-scrobbler
My intention was to get all my old scrobbles imported from Koito and fed into multiple clients for diversity (ListenBrainz, last.fm, libre.fm, maloja) using multi-scrobbler.
After that I would switch over to a local endpointlz as my source to feed in my scrobbles from Navidrome to multi-scrobbler and out to all the clients listed above + Koito, which I would switch from being a Source into a client after initial import.
Progress/Issues:
So far I've imported some scrobbles to Koito, unfortunately my data was not imported in date order and a couple .json files did not import the first time around into Koito.
The main problem I was facing was a message along the lines of
"Will not scrobble {Track} from Source {Source} because it occurred {TimeInThePast} before the oldest scrobble returned by this client"
I received this message for ListenBrainz, last.fm, majola as I had existing scrobbles from before with those clients.
The only one that worked and is currently working was libre.fm due to it not having any existing scrobbles. Though I'm not sure how it will handle the 2 json files that are going to be imported to Koito after the fact and them being in the past compared to the ones that were imported before.
My fear is, I will have to spin up another instance of Koito and multi-scrobbler to get those 2 json files into libre.fm OR I don't get that information imported into libre.fm at all due to the "Will not scrobble {Track} from Source {Source} because it occurred {TimeInThePast} before the oldest scrobble returned by this client"
Potential Solution/s:
I later saw there was a getBackloggedPlays option available here:
https://foxxmd.github.io/multi-scrobbler/development/dev-source/#backlog
But I could not see any further information about it for usage with Koito or Maloja as sources.
I ended up adding the existing scrobble data in directly to ListenBrainz and Maolja like I was doing for Koito as they had the option to.
Question:
However, I would like to know if there was a way to do this cleanly using multi-scrobbler? I plan on setting this up for other users in my household.
I understand that multi-scrobbler was mainly intended as a way to push current scrobbles form multiple sources to multiple clients but I imagine this would be valuable for many who are trying to ditch streaming services and own/control their data and move things locally.
Additional Note:
There is no easy options for Last.fm to import backlogged scrobbles as far as I'm aware. It has a limitation of only being able to backlog a max of 2 weeks back from the current day and limited to ~2600 scrobbles per day meaning it would probably require a manual solution like this https://github.com/joinemm/spotify-to-lastfm
Versions:
Logs:
Update:
Looks like Libre.fm has the same issue with older scrobbles :(
Beta Was this translation helpful? Give feedback.
All reactions