Anyone still scrobbling in 2022?

[doomsquirrel]

I tested the TSR and FG mode of the test_usb plugin in the rockbox_TestUSB_FioM3k_bm.zip.

For TSR I did the following procedure from the plugin instructions:

1. entered plugin -> selected Start
2. plugged in and unplugged USB
3. reentered plugin -> selected Status
   it displayed "State: disconnected" then "Prev: connected"

For FG I did:

A:
1. started plugin
  it displayed "Thread started"
2. connected USB cable
  it displayed "Thread exiting"

B:
1. connected USB cable (without entering data transfer mode)
2 started plugin
  it displayed "Thread started"
3. disconnected USB cable
  it displayed "Thread exiting"



I also tried a procedure similar to what amachronic did:

1. set scrobbler to start from Startup/Shutdown > Start Screen
2. restart player
3. play a few tracks
4. plug in USB, I can see the tracks in the scrobbler log
5. unplug USB and play a few more tracks
6. plug in USB again, new tracks show up in scrobbler log

(I didn't restart at all after point 2.)

So, it does seem to be writing track data to scrobbler.log ok now. I can't get it to not write to scrobbler.log anymore. Weird. I can't really say what could have caused it earlier. Maybe it was a side effect of some other crash or hangup. I do sometimes get unexpected behavior like = after unplugging the USB cable the player forgets where it was in the playlist/queue and starts from the beginning of an album I was playing earlier, or sometimes even from the beginning of an album that I was playing a couple of restarts ago.

[sg2002]

Hi, just reporting that I'm another person who still uses scrobbling in 2022. Had to change my setup now, but thanks for at least maintaining this in some form.

[cholero]

Hello I'm also still scrobbling in 2022 and now reverted back to a downloaded build from march 22 on my sansa clip zips and xduoo x3 because background scrobbling without any additional steps is more important to me than the commits from march to now. :-) I am still using rockbox for about 10 hours a week.

[keyb_gr]

Also chiming in to note that yes, I am very much still actively using the scrobbler. Recently I was wondering why my "home" player, a Clip+ that I had updated to a build from September (but not used a whole lot since then), wasn't scrobbling. It would be nice if one could easily get a summary changelog of sorts since date X in order to avoid surprises like this.

We have the ablility to run plugins at start-up so you could simply run scrobbler at start up
(Settings > General Settings > Startup/Shutdown > Start Screen > Open Plugin:
[apps/lastfm_scrobbler]

That seems to work splendidly.

With this workaround, I should be able to upgrade my main FiiO M3K as well, which still runs a 1-year-old build.

[automusician]

Actually, I just created an account in order to add in that I consider Scrobbling a critical feature to my listening habits and within Rockbox. I'm on the 5th gen iPod.
I just updated to the latest development build as I was having some issues and I saw scrobbling was gone and came to the forums to see what's up.

The steps to run a plug-in at start-up may not work if you haven't run the plugin before (I do see it generated a .cfg). I did a quick test and the first song I played did not generate a scrobble. The second did, but I booted up the plugin manually to sniff check. Might be a goof on my end, who knows. Could also be worth testing further.

Anyway, I'm extremely relieved to see this plugin here. Hopefully it works the exact same as before. Is there a way of easily checking if it's running when I boot the device and/or after scrobbling a song? I'm new to Rockbox, so maybe just opening the scrobble log is correct here, but thought to ask for opinions.

Cheers.

[Bilgus]

you should be able to run the plugin a second time and it'll give you a menu:
Settings (see below)
Flush Cache (saves the log immediately to disk)
Exit Plugin (stops the scrobbler)
Back (hides the plugin and runs in background)

Settings:
Resume playback makes it so the scrobbler plugin will resume the last song(if any exists)
save threshold sets how much of the song must be listened to before it gets saved (default is 50%)
Verbose = false suppresses the start-up message

I plan to make these type of plugins auto resume but till I get around to that running another plugin will flush the log to disk and kill the scrobbler plugin which you will need to re-run so slight downsides but better than gone

[automusician]

Cool, thanks for the tips. 

With respect, and asking from a place of curiosity, what's the reason(s) for moving it to a plugin? The first post mentioned that it was being moved but I don't know the rationale.
It seems at first glance to be better as part of the core like it was in the latest stable, but I know nothing about it and would like to know more.

[Bilgus]

It seems at first glance to be better as part of the core like it was in the latest stable

you only say that because you use it, for everyone else its eating up valuable ram
and we need a slimmer core (the space it freed has already been used)

[automusician]

Of course, good to have the rationale!

[automusician]

Would it be possible to eliminate or reduce the loud beep when the plugin starts?
I'd rather it started silently.

[Bilgus]

There youare it'll be in tomorrows builds

https://gerrit.rockbox.org/r/c/rockbox/+/5167
add volume level 0-10
10 is what it is now
0 disables the beep

[Bilgus]

I plan to make these type of plugins auto resume but till I get around to that running another plugin will flush the log to disk and kill the scrobbler plugin which you will need to re-run so slight downsides but better than gone

TSR plugins now restart automatically after you close the plugin that interrupted

if you want to exit the scrobbler for good run the plugin again and choose 'Exit Plugin'

[automusician]

Awesome! Thanks for both

[automusician]

I notice there's some cruft here in the pre-amble on the .scrobbler.log

Code: [Select]

#AUDIOSCROBBLER/1.1
#TZ/UNKNOWN
#CLIENT/Rockbox ipodvideo $Revision$
#ARTIST #ALBUM #TITLE #TRACKNUM #LENGTH #RATING #TIMESTAMP #MUSICBRAINZ_TRACKID
-8d45-f8a3ddc4430c

This is breaking my scrobbling tool https://github.com/ultraelephant/pyapplier and requires manual effort each time.
Is this line supposed to mean something or could it be removed? Maybe it was supposed to be in the client line instead of $Revision$?

[Bilgus]

looks to be the end of a track id?
example of a full one -- 88b49ed9-bd79-48db-909a-4b3007135707

not sure if its a failed write or maybe a buffer that is too small