Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_audioscrobbler 1.4.7 (Read 914012 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

foo_audioscrobbler 1.4.7

Reply #50
Just released foo_audioscrobbler 1.3.4 which is a maintenance release compiled with the new SDK.

foo_audioscrobbler 1.4.7

Reply #51
Hi,
great plugin!

Is there a special reason why tracks are not submitted one at a time, and instead in batches of five?

edit: Nevermind, that was just because I had updated from 1.3.2 -> 1.3.4

Thanks!
Pusk is the new Start.

foo_audioscrobbler 1.4.7

Reply #52
I play a fair amount of my classical music off vinyl, CD and SACD and use mp3s just over 30secs long to submit what I have been listening to.  Today I had to upgrade foobar and the audioscrobbler plugin as the old version I was using stopped working.  The new version doesn't seem to like files that are only just over 30 seconds long,  they don't submit and no warning or reason is given.  Have you increased the minimum track length to above 30 seconds for some reason? 

In case anyone thinks I just want to spam the system, my profile is here: http://www.last.fm/user/spod_mandel
I don't exactly submit an excessive amount of music.

This does make the new version of foobar2000 essentially unusable for me.  Just discovered why the old version wasn't working, so am using that again for now.

foo_audioscrobbler 1.4.7

Reply #53
When you say "over 30 seconds", are they over 31 seconds too, because that's the minimum length for submitting.

foo_audioscrobbler 1.4.7

Reply #54
When you say "over 30 seconds", are they over 31 seconds too, because that's the minimum length for submitting.


Nope, are about 30.5 seconds long.  Are you saying 31 seconds is the offical last.fm policy or just what is specified in the foobar plugin?

foo_audioscrobbler 1.4.7

Reply #55
...

how do i fix it. i open the console and get

"[16:03:58] Handshaking: Client up to date.
[16:03:58] Submit interval set to 1 seconds.
[16:03:58] Handshake successful.
[16:04:00] Startup time : 0:11.672720
[16:09:07] Submitting 16 cached tracks to Audioscrobbler...
[16:09:07] Submission failed: bad authorization.
[16:13:50] Submitting 17 cached tracks to Audioscrobbler...
[16:13:50] Submission failed: bad authorization."

foo_audioscrobbler 1.4.7

Reply #56
Are you using foo_audioscrobbler 1.3.4? I'm asking because the latest version should re-handshake if it gets BADAUTH as reply.


When you say "over 30 seconds", are they over 31 seconds too, because that's the minimum length for submitting.


Nope, are about 30.5 seconds long.  Are you saying 31 seconds is the offical last.fm policy or just what is specified in the foobar plugin?

Mandel, there is a rounding issue for tracks between 30 and 31 seconds in the current version of the plugin. I'll fix it to the next release.

foo_audioscrobbler 1.4.7

Reply #57
well nice done.

but as i dont have internet at my music-pc i´d really really like an plugin with all these statistic-features offline available!

foo_audioscrobbler 1.4.7

Reply #58
well nice done.

but as i dont have internet at my music-pc i´d really really like an plugin with all these statistic-features offline available!


There are two components called foo_playcount, an "official" and an "unofficial" one. I never tried them, but they may provide the features you're looking for.

foo_audioscrobbler 1.4.7

Reply #59
Are you using foo_audioscrobbler 1.3.4? I'm asking because the latest version should re-handshake if it gets BADAUTH as reply.

I have the same problem with foo_audioscrobbler 1.3.4:

Code: [Select]
Handshaking: Client up to date.
Submit interval set to 1 seconds.
Handshake successful.
.
.
Submitting track to Audioscrobbler...
Submission succeeded.
.
.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.

 

foo_audioscrobbler 1.4.7

Reply #60
I have had problems submitting tracks for the last two days:

Quote
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.
Not submitting. Cache contains 25 tracks.
Handshaking: Client up to date.
Handshake successful.
Submission failed: bad authorization.

There's more from where that came from, anyone else having the same problems?

foo_audioscrobbler 1.4.7

Reply #61
I had the same problem yesterday.

Did you install the shiny new last.m client? If so, uninstalling the client helped in my case.

foo_audioscrobbler 1.4.7

Reply #62
I can't get it to work... keep getting:
Code: [Select]
Not submitting. Cache contains 5 tracks.
Cannot connect to server.


I ran ethereal, and it seems that it's getting a 404 error for the ip address 62.216.251.200, which according to a whois belongs to last.fm. Could they have changed the server?


foo_audioscrobbler 1.4.7

Reply #64
Apparently, the submission server is down, so that COULD be the issue...

And to go a bit off topic - I totaly hate last.fm's new app. Why the hell shoud I have two players open? Hate that stuff.

foo_audioscrobbler 1.4.7

Reply #65
Last.fm's submission server is currently down:

Quote
Submissions Server
# Status: OFFLINE


You can check the server status here:
http://www.last.fm/forum/21713/_/51596


EDIT:
And I totally agree with you, Hellspam.
Especially as there seem to be submission problems when using the app (e.g. as radio player) and still having the dll for foobar (listening to my music). Well, no radio for me then...

foo_audioscrobbler 1.4.7

Reply #66
[EDIT] It was just a matter of patience... Working perfectly, thanks! [/EDIT]
_______ ___ __ _

Yeah, I'm getting the same thing guys... And Last.FM says their server is up... I'm using 1.3.4 with fbk 0.9.2

Code: [Select]
Startup time : 0:00.118958
Cannot connect to server.
Not submitting. Cache contains 16 tracks.
Handshaking: Client up to date.
Submit interval set to 1 seconds.
Handshake successful.
Submitting 10 of 17 cached tracks to Audioscrobbler...
Cannot connect to server.

foo_audioscrobbler 1.4.7

Reply #67
Give it some time, it's probably overloaded from everybody submitting all their cached tracks.

foo_audioscrobbler 1.4.7

Reply #68
Florian, are you also the author of the official plugin on Last.fm and is your version 1.3.2 of the plugin the same as version 1.3.2 that's currently available on Last.fm? I wonder which one I should use (official 1.3.2 or unofficial 1.3.4).

It does the same as the new beta Audioscrobbler, except that you won't need to run the additional Audioscrobbler application in the system notification area.
Do you plan to update the stand-alone plugin to use the new protocol introduced with the Last.fm software?

foo_audioscrobbler 1.4.7

Reply #69
Florian, are you also the author of the official plugin on Last.fm and is your version 1.3.2 of the plugin the same as version 1.3.2 that's currently available on Last.fm? I wonder which one I should use (official 1.3.2 or unofficial 1.3.4).

Yes, version 1.3.2 is also from me, but Russ is a little bit slow with updating the downloads section  You can safely use version 1.3.4 of foo_audioscrobbler.

Quote
It does the same as the new beta Audioscrobbler, except that you won't need to run the additional Audioscrobbler application in the system notification area.
Do you plan to update the stand-alone plugin to use the new protocol introduced with the Last.fm software?

I'm not aware of a new protocol version and I'm still using version 1.1. Can you please point me to the new spec?

foo_audioscrobbler 1.4.7

Reply #70
I'm not aware of a new protocol version and I'm still using version 1.1. Can you please point me to the new spec?

I have no spec but I found this post: http://www.last.fm/forum/34905/_/135053
Quote from: Russ link=msg=0 date=
Old-style plugin authors: I can change your old plugin forum into a group forum if you wish to continue supporting it. Alternatively, I can help you port your plugin to the new Audioscrobbler Client protocol.
That made me assume that there is a new protocol of some sort.

foo_audioscrobbler 1.4.7

Reply #71
I have no spec but I found this post: http://www.last.fm/forum/34905/_/135053
Quote from: Russ link=msg=0 date=
Old-style plugin authors: I can change your old plugin forum into a group forum if you wish to continue supporting it. Alternatively, I can help you port your plugin to the new Audioscrobbler Client protocol.
That made me assume that there is a new protocol of some sort.

Yes, but it is the new protocol for talking to the official Audioscrobbler client application. The protocol for talking with the severs wasn't changed.

foo_audioscrobbler 1.4.7

Reply #72
Then never mind.

foo_audioscrobbler 1.4.7

Reply #73
Would it be posible to add an option to enable submitting tracks from Audio CDs even if "Only submit tracks from the Media Library" is enabled.

foo_audioscrobbler 1.4.7

Reply #74
Getting bad auth messages like others. The last.fm page says the submission server is up. Wondered if anyone else is seeing these issues?