Anyone still scrobbling in 2022?

[automusician]

Good eye! It's the tail-end of the first track-id that should have shown up as a 'S' (skip).

I tried the steps again and it's fully reproducible in the daily build from March 27.

1. Delete .scrobbler.log
2. In Rockbox, go to Files
3. Select an album
4. Skip the first track (after a few seconds played is fine)
5. Wait a few more seconds
6. Pause / Stop
7. Connect and check

boom. The first track ID there should be https://musicbrainz.org/recording/969ee8a7-8b12-4297-bf05-c2a67b09c40c

Seems the scrobbler might have a write bug if there's no file already present.

Code: [Select]

#AUDIOSCROBBLER/1.1
#TZ/UNKNOWN
#CLIENT/Rockbox ipodvideo $Revision$
#ARTIST #ALBUM #TITLE #TRACKNUM #LENGTH #RATING #TIMESTAMP #MUSICBRAINZ_TRACKID
2-4297-bf05-c2a67b09c40c
Billy Talent Billy Talent II Red Flag 2 196 S 1680430715 5ee8e632-4c88-49e4-ab07-0626fbc196eb


[Bilgus]

I have a fix that should do the trick but I won't have time to test it for about a week

https://gerrit.rockbox.org/r/c/rockbox/+/5206

after I do I'll update here

[cirdanlunae]

The Scrobbler plugin seems to be causing Rockbox to crash. I'd submit a bug on rockbox.org/tracker, but the register page is broken (gives a fatal error). So, might as well mention it here.

Edit: Also tested with Daily Build 2747e920ba-230617 on iPod Video 5.5
Info: Daily Build 666a836227-230609 on iPod Video 5.5

What causes crash:
Switching between songs, either manually or as the song progresses, causes Rockbox to randomly crash. The crash states:

Code: [Select]

Data abort at 03f8074c (0)
pc: 03f8074c
sp: 000d6de0
bt end

After turning off the Scrobbler plugin and switching between nearly 100 songs does not result in a crash. Turning the plugin back on causes a crash within 10 or so songs.

The last version of Rockbox I used before this was Daily Build b6d04d1ac0-230310, and the error did not happen then.
Edit: Reverted my Rockbox install to the 230310 build, no issues so far while running the Scrobbler plugin. It looks like there must have been either an update to the plugin or (more likely) Rockbox itself that is causing the crash between March 10 2023 and June 9 2023.

Will gladly provide any additional information that I can.

EDIT: After some experimentation, it seems that setting VERBOSE to NO is what causes the crash. When setting VERBOSE to YES, it seems to act normally. Going to test this by having a 20 song playlist play with VERBOSE set to YES, following by trying again with VERBOSE set to NO. Will report back.
EDIT EDIT: Nope. Crashed even when VERBOSE set to YES. Tried setting to default settings, and when rebooting Rockbox and starting up the plugin, it still will crash after about 5 songs.

[chris_s]

The Scrobbler plugin seems to be causing Rockbox to crash. I'd submit a bug on rockbox.org/tracker, but the register page is broken (gives a fatal error). So, might as well mention it here.

Edit: Also tested with Daily Build 2747e920ba-230617 on iPod Video 5.5
Info: Daily Build 666a836227-230609 on iPod Video 5.5

What causes crash:
Switching between songs, either manually or as the song progresses, causes Rockbox to randomly crash. The crash states:

Code: [Select]

Data abort at 03f8074c (0)
pc: 03f8074c
sp: 000d6de0
bt end

After turning off the Scrobbler plugin and switching between nearly 100 songs does not result in a crash. Turning the plugin back on causes a crash within 10 or so songs.

The last version of Rockbox I used before this was Daily Build b6d04d1ac0-230310, and the error did not happen then.
Edit: Reverted my Rockbox install to the 230310 build, no issues so far while running the Scrobbler plugin. It looks like there must have been either an update to the plugin or (more likely) Rockbox itself that is causing the crash between March 10 2023 and June 9 2023.

Will gladly provide any additional information that I can.

EDIT: After some experimentation, it seems that setting VERBOSE to NO is what causes the crash. When setting VERBOSE to YES, it seems to act normally. Going to test this by having a 20 song playlist play with VERBOSE set to YES, following by trying again with VERBOSE set to NO. Will report back.
EDIT EDIT: Nope. Crashed even when VERBOSE set to YES. Tried setting to default settings, and when rebooting Rockbox and starting up the plugin, it still will crash after about 5 songs.

I was able to reproduce this on an iPod video. Looks like it is fixed by aligning the buffer for the cache entries.

edit: Fix has been merged and is now available in the dev build

[joswef]

Hello! I've been having trouble with not all of my songs being added to scrobbler.log on my iPod and I'm wondering if there are any settings to fix it? I have minimum elapsed and threshold at 0ms / 0%. This often happens with tracks that I pause but sometimes whole albums aren't scrobbled for no reason. I have the plugin set to launch on startup so I'm not just forgetting to start it. Does the 'Unique Track MRU' setting have anything to do with it? Any kind of help with any of this is gratefully received. Thanks all!

[hooded_paladin]

What's tricky about this being a plugin is that in poweroff situations (idle timeout, sleep timer, and closing the simulator) it gets a SYS_POWEROFF event before the audio stack gives you a track_finish_event. Have you encountered that?

I use a script to sync plays between my rockbox device and iTunes so I'm picky about everything getting logged. (I used to use a database hack, but I'm trying to switch over to a scrobbler hack). I was experimenting with some way to maybe get the track_finish_event before getting SYS_POWEROFF. Maybe have it send some pre-poweroff event, wait a little while, and then power off. Or I might just revert all the patches and go back to scrobbling from the core, since I'm hacking things anyway.

[joswef]

I’m unsure. I don’t use the sleep timer at all, a lot of scrobbles are simply absent from my .log file. We seem to be in a drought of dev updates at the moment and so I’m just stuck. Thanks for replying.

[hooded_paladin]

Well I guess that was more of a general comment for Bilgus or chris_s maybe. While reverting, I did notice that original version used to check for a currently playing song in the poweroff path:
        if (audio_status())
            add_to_cache(audio_current_track());

For your case joswef, no idea. It sounds specific enough to be a specific bug and not some general case of corruption.

[joswef]

You’re likely right. I haven’t modified any code of the dev version at all; it’s as is. I’m unsure what I’m doing to cause the bug but I’m keeping a note of what I’ve been listening to and logging the scrobbles manually until a new dev version is released.

[Trzyzet]

I came back to using my old last.fm account and found this for uploading .scrobbler.log:
https://github.com/jeselnik/rb-scrobbler

[Bilgus]

Trzyzet Cool!

hooded_paladin are you just wanting it to flush on shutdown then?
edit: yeah that was a bug should be fixed now

[Trzyzet]

Alright, plugin for eros/surfans/etc. has the same issue as mentioned previously - when plugin is working and you will connect device to USB device freezes.
OS on the PC tries to mount the device but with no success and when you unplug the player it will crash with

Code: [Select]

*PANIC*
mount: 0and damages the FAT filesystem on the SD card. Luckily FS is fixable by the windows or linux tools.
.scrobbler.log generated by the plugin is not working with any of the apps mentioned here, on the wiki and even the ones I tried to find.

Error looks like this:

Code: [Select]

panic: runtime error: index out of range [5] with length 1
EDIT: I attached the file generated by the plugin. I just added *.txt extension.

[Bilgus]

the log looks ok. to me versus the spec
http://web.archive.org/web/20180415061851/http://www.audioscrobbler.net/wiki/Portable_Player_Logging

is this the very latest dev version crashing on USB unplug?

does the battery bench plugin act this way too?

[Trzyzet]

Previously I had like 2 week old build, now installed a fresh one. It does exactly the same.
And yes, battery bench plugin behaves the same. Unable to mount partition and mount: 0 panic screen when unplugged.

[Bilgus]

if the bench plugin does it too i wonder how old the bug is

does this happen 3.15 as well?

maybe from the USB rewrite?