Last Fm logging Scrobbler

[Bilgus]

Last Fm Scrobbler

The Scrobbler plugin keeps a log of songs played and songs skipped

There are some new options

Settings

• Remove duplicates
  Only keeps the same track with the most time elapsed
  
• Delete playback log
  Remove the current playback log once it has been read
  
• View log
  View the current playback log
  
• Save threshold
  0-100% when this percentage of time has elapsed the track will be marked (L)istened
  
• Minimum Elapsed
  0-10000(ms) Tracks played less than Minimum Elapsed will not be logged
  
• Revert to Defaults
  removes changes to settings
  
• Cancel
  quit the plugin
  
• Export
  Only visible if playback.log exists exports log saves changes and exits plugin
  

[Bilgus]

There is a new version of this in the latest dev versions

we now have playback logging in core and you can parse that to export your scrobbler file

see the manual for your device for more info

[orgone]

There is a new version of this in the latest dev versions

we now have playback logging in core and you can parse that to export your scrobbler file

see the manual for your device for more info

I don't see Last Fm entry in the Playback settings. How can I use scrobbler.log now?

[Bilgus]

Plugins>apps>lastfm_scrobbler

when you run it the first time it'll ask you to 'enable playback logging' select YES
and optionally set your options, cick cancel and if asked select yes to save changes
go play some tracks at some time later in the future run the scrobbler plugin again and select Export
you now have your log its located at /.scrobbler.log

Note: you don't have to run the scrobbler plugin except when you want to update the log
but do be aware that you should do it occasionally once playback logging is active
since it will dump rockbox's internal log and mitigate performance issues trying to load such a large log
 I've had no ill effect with a playback log as big as 10mb but its something to be aware of if you let it go for months..

[orgone]

Thank you.
Usability got worse, in my opinion.
1) One more action to export;
2) Listened files must be accessible during export; no metadata in .scrobbler.log otherwise

[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]

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

Awesome, Thanks for the clarification.