Audio Scrobbler Glitch

[mnzy]

Since 1.0 of decibel-audio-player there seems to be a glitch with the Audio Scrobbler plug-in.
On last.fm for example it registers what's playing right now but it is not taking it on the "last played"-list.
I don't know if it is last.fm's fault though.
It works with other players.

[Anonym25712 (anonym25712)]

What do you call the "last played" list? Do you mean the recently listened tracks? It works flawlessly for me.

[mnzy (monzone-deactivatedaccount)]

Yes that is what i mean.
While listening to music it's showing: "Listening now using Decibel" on top and underneath the song i'm playing,
but it does not take them into the "Recently Listened Tracks"-list. I got this since upgrading to 1.0.
Maybe it is somehow my fault, but i can't imagine how.

[mnzy (monzone-deactivatedaccount)]

Ok, i got rid of it by completely throwing all decibel related files off the system, a simple complete removal of the package was not enough.

But today it started again.
I moved my PC and after that it asked me for the password of the key ring (which it normally doesn't), after entering it, the problem started again.

[Ananda (ananda-samaddar-vfemail)]

I can confirm that this happens to me too. Now listening works but submitting tracks doesn't. I'm using 1.0 on Arch Linux. The source code is vanilla unpatched direct from the decibel home page.

[Ananda (ananda-samaddar-vfemail)]

Ok here's some further information. It seems to be related to when you mess about with tracks in your library so it could be a last.fm bug. I removed and added tracks to my library so Decibel's scrobbling stopped working as described above. I then tried scrobbling with the official last.fm client on Windows and it worked. I then switched back to Decibel and again submitting tracks worked again. So I don't know if this helps but Decibel's submitting is now working.

[mnzy (monzone-deactivatedaccount)]

I got the problem again, this time on my new Fedora 10.
It just doesn't take the tracks into the "Recently Played"-list.

I've added the log, the only suspicious line is
[090317114119] INFO [AudioScrobbler] 28 track(s) left in cache
i guess when you close it.
Tell me, if i can get you more info.

[mnzy (monzone-deactivatedaccount)]

I just wanted to say, that i still have this problem.
My guess is, that it has something to do with autologin to Ubuntu.
Because of that you get asked for your keyring-password after the music is playing already.

I still hope somebody finds a solution for this or atleast a way i can help to track it down :)

[Anonym25712 (anonym25712)]

Does this happen with some specific tracks?

The other day, I got a similar problem because some tags were incorrect and could not be submitted to Last.fm. As a result, since the tracks on top of the cache queue were being stuck there, nothing was submitted at all.

[Anonym25712 (anonym25712)]

This is what happens:
 1) A track with very bad tags is added to the cache queue
 2) This tracks is always rejected by Last.fm during submission
 3) New tracks are added to the cache queue as time passes
 4) They all get stuck in the cache queue since the oldest track (submitted first) is always rejected

Note that while this track is rejected by Last.fm during the standard submission process, it is accepted for the "listening now" submission. No idea why.

This should be fixed on trunk.

[Anonym25712 (anonym25712)]

See v1.01