Multi-scrobbler only submits the last 20 cached scrobbles to Maloja using Last.fm as a source

[maluvola]

• multi-scrobbler: [0.6.5, no docker or flatpak]
• maloja [3.2.2]

[FoxxMD]

Hello

This is by design. multi-scrobbler is not an application for importing your historical scrobbles from LastFM. If you'd like to import all of your scrobbles from LastFM please follow the directions in the Maloja documentation under How To Use -> Data.

multi-scrobbler is designed to be run continuously so it can monitor scrobbles in real time. The 20 scrobble value is in place to help "fill in the gaps" in the event it crashes or is stopped for some reason -- the cache is used to get any missed scrobbles during that down time. If this use case, getting that last 20 scrobbles, is not adequate for you please describe where it is failing and I may be able to address it.

Additionally, since you are running MS natively, you can adjust this value yourself to get more "cached" scrobbles, if you would like:

• stop multi-scrobbler, if it is running
• replace limit in LastfmSource.ts and replace this.MAX_STORED_SCROBBLES on this line in MalojaScrobbler.ts with the number of cached scrobbles you want
• restart multi-scrobbler by running npm run start

[maluvola]

Thank you. The reason I want to increase the number of cached scrobbles is that I don't keep the server on at all times, and I like to have it mirrored with Last.fm. This way, scrobbles can be submitted to Maloja after I listen to music on my phone.

[FoxxMD]

Then increasing the limits I mentioned should accomplish your goal. Be aware that Last.FM will return a maximum of 200 scrobbles so that's as high as the limit in LastfmSource.ts can go. You should make sure to start multi-scrobbler before you have scrobbled that many tracks since last using it.

[FoxxMD]

@maluvola please try pulling the develop branch. It has these changes in it:

• sources pull the maximum # of listens supported by the api on startup (200 for last.fm)
• clients pull the maximum # of scrobbles supported by the api for comparison on startup (100 for maloja)
• source and client configs can specify these numbers for startup if the default maximum is not desirable:

ex lastfm.json

[
  {
    "name": "mylfm",
    "enable": true,
    "configureAs": "source",
    "data": {
    },
    "options": {
      "scrobbleBacklogCount": 100
    }
  }
]

ex maloja.json

[
  {
    "name": "default",
    "enable": true,
    "data": {
    },
    "options": {
      "refreshInitialCount": 20,
    }
  }
]

I believe this should address your issue?

[maluvola]

Yes, it should. Does your previous answer work as well? I made the changes but haven't listened to more than a dozen tracks yet.

[FoxxMD]

Yes my previous answer will still work. The new solution in develop is a configuration-based version of my previous answer. I'd suggest switching to that, eventually, so that you can continue to pull updates to MS without having to resolve file changes. I will drop a comment here when the solution is included in a full release (probably next week).