Skip to main content
Topic: foo_scrobble (Read 14663 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foo_scrobble

Reply #50
Hi gix, I have the same problem as stealthswor, it's saying "Unauthenticated" even though I am.
When I dis- and reconnected, the console said this:
Code: [Select]
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)
No errors, no nothing.

Edit: And on startup, this is what it says:
Code: [Select]
foo_scrobble: Scrobbling failed (error: 9, Please re - authenticate.)


Re: foo_scrobble

Reply #52
I haven't gotten the opportunity yet to check if it works again, but I've heard that people are having this problem with other scrobblers as well and that last.fm is just having trouble right now, apparently. So the problem is probably on last.fm's part.

Re: foo_scrobble

Reply #53
You may have to reauthorize foo_scrobble again.

via Twitter
Quote from: Last.fm Official Response
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.

Re: foo_scrobble

Reply #54
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.

Re: foo_scrobble

Reply #55
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.

Re: foo_scrobble

Reply #56
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.

An easy way is to open up the Foobar2000 preferences and navigate to the Components section. Click the install button and browse to the file. Apply. Restart. Done.

Re: foo_scrobble

Reply #57
How do you actually install this? The read me file is the most useless thing I've seen in my entire life. [...]
No need to be rude. The readme there is mostly for the development side, but I'll change it. You install this component like any other. If you have a default foobar2000 installation, you can just double-click .fb2k-component files and foobar2000 installs them. The second way, also described at "How to install a component", is to use the Install button in the foobar2000 preferences dialog. You can also just drag the .fb2k-component file onto the component list in the foobar2000 preferences.

Re: foo_scrobble

Reply #58
Thx for this nice component :)

Re: foo_scrobble

Reply #59
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.

same issue here with Queuing scrobble (Unauthenticated) error

Re: foo_scrobble

Reply #60
so i just checked my brother's computer to see if the component was working on his and it is. the difference was that he hadn't updated to 1.3.1 and was still on 1.1.0. tried 1.1.0 on my computer and the Queuing scrobble (Unauthenticated) error went away. it's now scrobbling the way it's supposed to.

Re: foo_scrobble

Reply #61
I got 1.3.1 working by removing it, installing it again, clearing authorization and requesting it again.

Re: foo_scrobble

Reply #62
worked over here too. now why didn't I think of that?

Re: foo_scrobble

Reply #63
Just tried to install this for the first time and am getting "Could not load component "foo_scrobble.fb2k-component": I/O error (win32 #87)"

Re: foo_scrobble

Reply #64
Hi.  First, a disclaimer: The issue I'm about to describe occurs on a system running fb2k in wine on funtoo linux.  That said, I have not reproduced the conditions on a Windows system, and may affect those as well.  I recently switched over to foo_scrobble since finding some 800 scrobbles in the submit queue that I didn't know about.  Since changing over, I've had a number of fb2k crashes (which are usually very rare).  I have intermittent ISP connection errors on this system, and the crashes happen when the internet connection is down.  I can only conclude that foo_scrobble is reacting poorly when it can't connect to the last.fm servers.  Has any one else seen this?  Can someone other user here try to reproduce?

Thanks.

Re: foo_scrobble

Reply #65
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).

 

Re: foo_scrobble

Reply #66
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).
I'm seeing the exact same thing since updating to foobar 1.5:
Play song A
-> Last.fm shows A is being listened to
Update title of A to B while song is playing
-> Last.fm shows A was scrobbled and B is being listened to.
Update title of B to A
-> Last.fm shows A was scrobbled, B was scrobbled, and A is being listened to
Song Ends
-> Last.fm shows A was scrobbled, B was scrobbled, then A was scrobbled

My guess is that a lifecycle hook was updated for 1.5 and foo_scrobble isn't handling it the same way.

 
SimplePortal 1.0.0 RC1 © 2008-2019