The VideoLAN Forums

So, from searching this forum, it seems that I have to have the 0.9.0 for last.fm support. Only, I've tried the latest couple nightlies (11-18, 11-17, the exes), and enabling audioscrobbler in the prefs in them doesn't update last.fm with my listening history. I tried manually editing vlcrc, but it's got and my username and pass uncommented, which as far as I can tell, SHOULD mean audioscrobbler works. So, what am I doing wrong that is making scrobbling not work, and what do I need to do to make it work?

please set the verbosity level to 2 in the preferences
and look in the messages window (ctrl+m) for audioscrobbler messages

btw are you listening local audio files (on your harddisk) ?

Yeah, it's local media files. I installed the newest nightly, 11-19, and here's the messages from playing an MP3, with a bit of trimming for clearly irrelevant stuff. Also, Irealize something in there is my password, but I dunno which string it is, and it's not plaintext, so I'm not worried enough to snip. Snipped my username tho. And it just continues that over and over pretty endlessly. Plus, it doesn't retain the audioscrobbler activation between program runs. Every time I open VLC, I have to go into the prefs and reactivate the audioscrobbler interface. It remembers my username and pass however.

Your password is "hashed", then concatenated to a hash sent by the server, then hashed again, so we can't do anything with that, we can't guess your password, nor use that hash to fake authentication

main debug: connection: Resource temporarily unavailable
>> Looks strange
main debug: connection succeeded (socket = 4804)
audioscrobbler debug: Handshake successfull
>> But it succeeds so we don't care

main debug: connection succeeded (socket = 4820)
audioscrobbler debug: Authentication failed, handshaking again
>> There is 3 possibilities

1/ There was a "BADSESSION" answer, from the audioscrobbler specification at http://www.audioscrobbler.net/development/protocol/

BADSESSION
This indicates that the Session ID sent was somehow invalid, possibly because another client has performed a handshake for this user. On receiving this, the client should re-handshake with the server before continuing.

Do you have another program using last.fm which is running ?

2/ VLC couldn't find the string "OK" in the answer, and if it is the case there are 2 possibilities:

2a/

All other responses should be treated as a hard failure.
An error may be reported to the user, but as with other messages this should be kept to a minimum.

So there was an unspecified problem.

OR

2b/
The 1024 bytes buffer which contains the answer is too small << that would be VERY bad, but from the tests I made it is sufficient

Please confirm that you don't have another program running some last.fm authentication, if not, I will provide you a binary with a larger buffer size, and extended debug, so we can sort that

From the protocol:

The body of the server response will consist of a single \n (ASCII 10) terminated line. The client should process the first line of the body to determine the action it should take

That means the "OK" string should be in the first 2 bytes of the answer, so it seems like it's one of the 2 first cases.

And it just continues that over and over pretty endlessly. Plus, it doesn't retain the audioscrobbler activation between program runs. Every time I open VLC, I have to go into the prefs and reactivate the audioscrobbler interface. It remembers my username and pass however.

In some cases, the audioscrobbler plugin unloads itself, but it shouldn't be removed of the config. Can you verify your vlcrc file after quitting VLC ?

P.S.
On http://www.last.fm/user/funman , almost every song has been submitted with VLC
So maybe we have a specific windows bug, we'll see.

I've stuck with the 11-19 nightly, as I don't want to go changing the executable in the middle of trouble shooting. If you'd like me to keep trying on the current nightly, let me know and I'll upgrade it.
I've checked the windows startup folder, both RUN registry keys, the windows service list, and the taskmanager, and don't see anything that looks to be last.fm. I even made sure to not log into the last.fm website while VLC was up. It still didn't work. The error messages look about the same to me, other than this one has an error message too big. maybe it is buffer size? I'm not a coder, I dunno.
One other thing, from reading the other threads, I thought that the audioscrobbler submitted data for a file once it was 50% player, or hit 240 seconds? Did I misunderstand that? From watching the messages, it's not trying to submit until the song is over, regardless of the length of the song.
Edited to add-Oh, and audioscrobbler is loading ok, even tho when I look in the prefs via the GUI, audioscrobbler isn't checked under the interfaces. *shrug* whatev.

Logging in the website shouldn't harm, I do it often.

There has been an update to audioscrobbler code when it was updated to protocol 1.2 and now the songs are submitted when they end, it's much easier and cleaner to do so.

I will have a look at errors reporting, and will make error messages more precise, and eventually give the errors reported by last.fm server, so we can figure what is going wrong.
I keep you informed when the windows builds will be updated.

Are you using 32 bits or 64 bits architecture ?

I keep you informed when the windows builds will be updated.

Cool, thanks!

Are you using 32 bits or 64 bits architecture ?

32

Ok I changed a bit the messages: http://trac.videolan.org/vlc/changeset/23254

But the change was to late for trunk-20071123-0001 so please try a newer version (like 20071124, which will be ready the 2007, Nov 24th at midnight french time) and paste the logs.

http://nightlies.videolan.org/build/win ... 1124-0001/ should be helpful

hi,
i've just switched from 0.8.6 to http://nightlies.videolan.org/build/win ... -win32.exe, mainly because of last.fm support.
however, it does not work. this is what i get after each song in messages window:

audioscrobbler error: last.fm handshake failed: Database too busy - try later.

i'm using it couple of days already, is it possible that it's always too busy?