Last.fm Scrobbler help

Post a reply

Visual Confirmation

To prevent automated access and spam, you are required to confirm that you are human. Please place a check mark next to all images of monkeys or apes. If you cannot see any images, please contact the Board Administrator.

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Last.fm Scrobbler help

Re: Last.fm Scrobbler help

Post by Peke » Mon Feb 12, 2018 4:36 pm

Hi,
It is like username and pwd are not set correctly and/or cache got corrupted I do not see authentication just direct submit. can you please delete cache file ("c:\Users\<USERNAME>\AppData\Roaming\MediaMonkey\LastFM_Cache.dat")?

Re: Last.fm Scrobbler help

Post by soulpatchguy » Sun Feb 11, 2018 11:17 pm

Peke wrote:Hi,
What do you see in Last.fm Log file? I do not have such issue as seen from profile in my signature.


I downgraded to Last.fm Scrobbler 1.0.2.29 yesterday and ran Media Monkey as admin. Here is my log file.

Code: Select all
11/02/2018 11:42:43.117: select Songs.ID from Songs where Songs.id=114564 AND Songs.TrackType in (2)
11/02/2018 11:45:45.407: Last.FM: Player got Command wParam (1001)
11/02/2018 11:45:45.441: Last.FM: Submit Started at 1518378345
11/02/2018 11:45:45.460: Last.FM: Player got Command wParam (2)
11/02/2018 11:45:45.467: Last.FM: Player got Command wParam (1)
11/02/2018 11:45:45.474: Last.FM: Player got Command wParam (1)
11/02/2018 11:45:45.480: Last.FM: Player got Command wParam (1)
11/02/2018 11:45:45.571: Last.FM: Player got Command wParam (1)
11/02/2018 11:45:45.578: Last.FM: Player got Command wParam (0)
11/02/2018 11:45:45.584: Last.FM: Player got Command wParam (2)
11/02/2018 11:47:47.256: Last.FM: Player got Command wParam (1001)
11/02/2018 11:47:47.271: Last.FM: Player got Command wParam (2)
11/02/2018 11:47:47.278: Last.FM: Player got Command wParam (1)
11/02/2018 11:47:47.285: Last.FM: Player got Command wParam (1)
11/02/2018 11:47:47.292: Last.FM: Player got Command wParam (1)
11/02/2018 11:47:47.341: Last.FM: Player got Command wParam (1)
11/02/2018 11:47:47.348: Last.FM: Player got Command wParam (0)
11/02/2018 11:47:47.355: Last.FM: Player got Command wParam (2)
11/02/2018 11:50:37.624: Last.FM: Player got Command wParam (1001)
11/02/2018 11:50:37.640: Last.FM: Player got Command wParam (2)
11/02/2018 11:50:37.689: Last.FM: Player got Command wParam (1)
11/02/2018 11:50:37.696: Last.FM: Player got Command wParam (1)
11/02/2018 11:50:37.702: Last.FM: Player got Command wParam (1)
11/02/2018 11:50:37.781: Last.FM: Player got Command wParam (1)
11/02/2018 11:50:37.788: Last.FM: Player got Command wParam (0)
11/02/2018 11:50:37.795: Last.FM: Player got Command wParam (2)
11/02/2018 11:56:06.506: Last.FM: Player got Command wParam (1001)

Re: Last.fm Scrobbler help

Post by Peke » Sun Feb 11, 2018 7:59 pm

Hi,
What do you see in Last.fm Log file? I do not have such issue as seen from profile in my signature.

Re: Last.fm Scrobbler help

Post by soulpatchguy » Sun Feb 11, 2018 2:29 am

I just noticed that Media Monkey stopped scrobbling to Last.fm on January 6, 2018. I haven't changed any settings although on that day I connected Last.fm for Android to my account and the last songs scrobbled were from my phone, not Media Monkey on my computer. It says Service status: Submission enabled. I tried disconnecting Last.fm for Android but that didn't help. The last day Media Monkey on my computer scrobbled was Nov 17, 2017.

Re: Last.fm Scrobbler help

Post by Jlexa » Mon Jul 24, 2017 4:48 am

When I submit cached tracks to Last.fm, then some songs including such symbols as ä, å, ø in their titles, aren't displayed correctly on my Last.fm profile. Is there any solution to this problem? I hope I'm not the only one who ran into this. Thank you for attention.

Re: Last.fm Scrobbler help

Post by Jlexa » Mon Jul 24, 2017 4:46 am

Hi! Greetings from Russia. I would like to apologize in advance for my English. I hope that you will correctly understand me. I'm an old MediaMonkey user.
I ran into several problems related to the work of the plugin.
1. Periodically I notice that plugin scrobbles not all songs that I play. Scrobbler for some reason skips one random separate song, but not two in a row. I've noticed this since I started to keep statistics of my plays using AlbumPlays.
Offline mode helps me out giving an opportunity to cache played tracks. Thus scrobbling is performed on 100%, however...
2. When I send cached tracks to Last.fm, then some songs including such symbols as ä, å, ø and so on in their titles, aren't displayed correctly.
I use the latest version of the player and plugin. I listen to music on two computers. On one of them is installed Windows 7 and Windows 8 on the other. The problem is observed when listening from both computers. The problem occurs when listening from both computers.
Is there any solution to this problem?
I hope I'm not the only one who ran into this.
Thank you for attention. :D

Re: Last.fm Scrobbler help

Post by Galdoran » Mon Jun 12, 2017 12:50 pm

[SOLVED]
Downgraded to 1.0.2.29 per Stigg's suggestion, but still wasn't submitting scrobbles - just caching.
But with 1.0.2.29 there is a log file that indicated an error: Handshake Bad System Clock Time
Searched back through forums and found a couple references regarding this error, one suggested changing the Short Date format (Win 7) - tried that but still not the solution.
So, then noticed that my system clock time was 2 minutes faster than another system in my office.

Re-synched Internet Time with time.nist.gov and ... TA-DA!
All cached tracks submitted and everthing is now updating and scrobbling properly!
Re-installed 1.1.0.41 and it is working fine as well, so not really a version problem, except for the lack of a clear error indication in 1.1.0.41.

So, I'm guessing that my system time glitched out while trying to synch overnight on June 8 (as it was previously scrobbling fine June 7)

Re: Last.fm Scrobbler help

Post by Lowlander » Mon Jun 12, 2017 11:29 am

1.1.0.41 has been working well here. My problem has been on Android, but it seems last.fm is rejecting scrobbles there on occasion.

Try Last.fm Scrobbler 1.0.2.29

Post by Stigg » Sun Jun 11, 2017 9:04 pm

To those having problems, try Last.fm Scrobbler 1.0.2.29.
I still use 1.0.2.29 to this day without any problems as I was always having problems with 1.1.0.41.

Re: Last.fm Scrobbler help

Post by Galdoran » Sun Jun 11, 2017 5:07 pm

June 8/2017 - This same issue started happening to me as well: Scrobbling seemed to have stopped.
Scrobbling from my iPhone app works and updates my profile as always, but not with MM any more.

MediaMonkey 4.1.16.1836 / Last.fm Scrobbler 1.1.0.41

Service staus: Failed (cached Track)
Tracks scrobbled: 0/0
Now Playing shared: 0/0
Tracks cached: 171

Pressing the Clean Cache button doesn't seem to do anything.

Checked that the icon status is Green.
Tried switching to Yellow for a song or two:
Service staus: OK (cached Track)
then back to Green to see if it would submit, but same Failed status.

Tried lower case Username as suggested in earlier posts.
Tried changing Last.FM password.

Tried the re-install process that sn0skier said worked for him.

Anyone got any other suggestions?

Re: Last.fm Scrobbler help

Post by sn0skier » Thu Jun 08, 2017 4:18 pm

I was having a problem where tracks were being cahced but not submitted. I had the same debug error as user Khazidhea:

Khazidhea wrote:Hi,

Events: Destroying TScriptExec: C:\Program Files (x86)\MediaMonkey\Scripts\Auto\!LastFM.Options.vbs



I solved the problem by uninstalling the Extension, closing MediaMonkey, running MediaMonkey as administrator, reinstalling the extension without the "Only install for current user" option. This solved my problem (and I was even able to use the old LastFM_Cache file in the new install to scrobble the tracks that didn't get scrobbled from before).

A simple uninstall and reinstall did not work, but it's possible I uninstalled incorrectly, so it might work for someone else.

Re: Last.fm Scrobbler help

Post by loubat » Sun Apr 30, 2017 5:16 pm

Forcen wrote:Is it green for enable, red for disable and yellow for cache? I think this is it based on how the setting changes but not sure...
If it is like a traffic light then it makes sense but the normal last.fm logo is red.
EDIT: looks like it's explained in the service status in settings.

lol, yeah the red logo messed with my brain too. But you're right, it's like a traffic light. Green for go, Yellow for cache, Red for stop.

Re: Last.fm Scrobbler help

Post by Forcen » Sun Apr 30, 2017 11:39 am

Is it green for enable, red for disable and yellow for cache? I think this is it based on how the setting changes but not sure...
If it is like a traffic light then it makes sense but the normal last.fm logo is red.
EDIT: looks like it's explained in the service status in settings.

Re: Last.fm Scrobbler help

Post by rachaelc1878 » Mon Apr 24, 2017 4:53 am

About 3 days ago MediaMonkey stopped scrobbling to last.fm. No idea why and I have no idea how to fix it. Any help would be great.

Last.fm Scrobbler 1.1.0.41

Post by julesc » Tue Feb 07, 2017 2:36 pm

I'm trying to get the scrobbler working but without luck. I can play and scrobble without difficulty through Winamp but nothing seems to work with the Mediamonkey add-on. I have tried clearing the cache, deleting the files in the Roaming/App file and reinstalling but nothing doing. At one stage it was scrobbling to the cache but at handshake stage I was getting a 'bad time clock' message (although the clock was fine and working with Winamp). Any help greatly appreciated.

Top