Support and General Use > Plugins/Viewers

Last Fm logging Scrobbler

<< < (2/3) > >>

Bilgus:
Sorry?
The previous version was a TSR plugin that you had to remember to run
I think remembering to export before track removal is probably less problematic

The main issue I have with scrobbler in core is the amount of data
you have to write to the buffer (and to disk) during playback

With this method devices without a spinning harddisk can just write directly to the disk
they don't need a big buffer to do it quickly enough and it doesn't consume so much core RAM even for the spinning disk devices
because we have a set limit on the amount of data and can have a sensible buffer that is able to hold at least 10 tracks it should also result in less battery used

Not that you aren't still doing the processing anyway but it can be deferred till charging is close at hand..

pfych:
I just swapped to the daily build and am looking for some clarification regarding the new scrobbling plugin. Once I've started it for the first time and set up playback logging - do I need to launch it every time I start my device (iPod 6th gen)?

Also, will automatic export ever be an option for devices with a bit more grunt and flash storage? It was convenient just plugging in my device and having a script grab/delete my scrobble log file. Needing to remember to go into the plugin, select "export" & then go back into the plugin and select "Delete playback log" is a bit tedious. Especially if you're doing it every night after a day of listening.

Thanks!

Bilgus:
once you start it it enables playback logging, you don't need to run it again till you want to reap your log and export it then run the plugin and copy the .scrobbler.log file

pfych:

--- Quote from: Bilgus on March 19, 2025, 03:09:53 AM ---once you start it it enables playback logging, you don't need to run it again till you want to reap your log and export it then run the plugin and copy the .scrobbler.log file

--- End quote ---

Awesome, Thanks for the clarification.

orgone:
The new mechanism skips some listens without any visible reason. Don't know how to debug it to provide more detailed info.
Some listens are just not listed in the result .scrobbler.log file


--- Quote from: Bilgus on January 19, 2025, 10:21:46 AM ---Sorry?
The previous version was a TSR plugin that you had to remember to run
I think remembering to export before track removal is probably less problematic

The main issue I have with scrobbler in core is the amount of data
you have to write to the buffer (and to disk) during playback

With this method devices without a spinning harddisk can just write directly to the disk
they don't need a big buffer to do it quickly enough and it doesn't consume so much core RAM even for the spinning disk devices
because we have a set limit on the amount of data and can have a sensible buffer that is able to hold at least 10 tracks it should also result in less battery used

Not that you aren't still doing the processing anyway but it can be deferred till charging is close at hand..

--- End quote ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page