foo_scrobble: Queuing scrobble (Unauthenticated)
Found 0 plays in last.fm (since last recorded scrobble) of The Donald
foo_scrobble: Requesting auth token
foo_scrobble: Received auth token: l5ddvT183mazWLqa3NmNmd9s2k_mnzQZ
foo_scrobble: Requesting session key
foo_scrobble: New session key: xRnifLPucw9JW3rpdMv9ZNNhRlINfPeQ
foo_scrobble: Queuing scrobble (Unauthenticated)

foo_scrobble: Scrobbling failed (error: 9, Please re - authenticate.)

...

Good morning everyone, 

Yesterday afternoon we experienced a brief outage at our datacentre which unfortunately caused many connected api keys / active sessions to get automatically logged out. The root issue has now been resolved, but if you've been affected by this, then I'm afraid you will need to reconnect and re-authenticate all of the applications connected to your Last.fm account.  We apologise for any inconvenience caused by this. 

You can view your connected applications in your settings here: https://www.last.fm/settings/applications  If the app(s) you're using are not listed, they will need to be reconnected - please follow each app's instructions for how to do this.  You can also find more information on how to connect to the most popular scrobblers here and here.

  Note that if an app says you're connected, but still doesn't work or gives you an error, you may need to first disconnect it and then re-auth again.  Failing this, you may need to do a fresh reinstall of the app, or reset it (e.g. you may need to do this if you're using the foo_scrobble component, detailed steps can be found here ). 

Please also note that to fix the problem we had to roll back a configuration setting at 1am this morning which would have logged everyone out of everything again -- if you had successfully reconnected all of your apps last night, then I'm afraid you may find that you've been logged out once again, and will need to reconnect one more time. 

Once again, we're sorry for any inconvenience this disruption has caused.

foo_scrobble: Scrobbling failed (error: 9, Please re - authenticate.)

foo_scrobble: Queuing scrobble (Unauthenticated)

How do you actually install this? The read me file is the most useless thing I've seen in my entire life. "Tools > Last.fm Scrobbling" doesn't exist since there's no clear way for me to interpret where to actually place the files from foo_scrobble.

How do you actually install this? The read me file is the most useless thing I've seen in my entire life. [...]

I get

Code: [Select]

foo_scrobble: Scrobbling failed (error: 9, Please re - authenticate.)

on startup.

and

Code: [Select]

foo_scrobble: Queuing scrobble (Unauthenticated)

after a track is played.

I have reauthorized the plugin, no luck. It won't scrobble.

Since yesterday I'm getting some strange scrobble behavior. Whenever I edit a tag from a track that's being played the scrobble count adds up on the site (it happens even live when looking at the now scrobbling list on last.fm). With each separate tag edit a scrobble of the playing track gets added.
I'm not really sure if it's the component's fault because I've made several big changes to foobar. I've updated to Foobar 1.5 (coming from 1.4.6) and also updates Columns UI to 1.3.0 beta. 1 (coming from 1.1).

For now I would want to see if anyone can replicate this using the latest foobar with columns ui. The problem is very consistent, I don't edit tags and nothing wrong happens but as soon as I edit a tag on a playing song an extra scrobble is counted. It seems as if each time an edit gets confirmed a scrobble gets send and finished (scrobbel counted) but the current playing track is still in the process of being scrobbled without being finished (until the track actually ends and thus the scrobble counted).