▲

[saga]

Maybe your scrobbler cache broke at some point. Delete the file xmp-scrobbler.cache from XMPlay's directory and try again.

[murakami]

I have a problem which might be due to how the plugin recognizes musicbrainz info. It ends up scrobbling the wrong album if the song which is scrobbled is featured on multiple albums on last.fm. Does anyone have a solution?

[saga]

The plugin should send the album information, if there's any in your tags. If there's no match on last.fm, it's their problem.

[murakami]

I guess i could give an specific example to help explain my problem better. I have the song audience killer loop by dir en grey which is featured on Vulgar, one of their albums. When i scrobble it might happen that it is instead scrobbled to another DNG album called Decade 2003-2007, even though the album in my library has Vulgar in the album tags.

[raina]

I think the plugin is well aware of the right album and as saga said, should send the correct data to Last.fm. As such there's nothing to be done on the scrobbling end. Do you find that when using another player, you get the correct album displayed in Last.fm? If so, it must be because the rest of the world is probably using newer APIs by now and xmp-scrobbler should be updated or replaced to catch up.

[murakami]

Yes, as a matter of fact i use foobar2000 quite often and it's scrobbler component foo_audioscrobbler. After adjusting field remappings and removing musicbrainz tags from my files just in case, it scrobbles everything correctly. I'm pretty sure it is also using the most recent scrobbling API.

[Dotpitch]

It ends up scrobbling the wrong album if the song which is scrobbled is featured on multiple albums on last.fm.

I think the plugin is well aware of the right album and as saga said, should send the correct data to Last.fm.

xmp-scrobbler will also send the MusicBrainz ID along with the other tags. I think Last.fm does its own lookup of the MBID and always uses the same entry on that list, regardless of what album you were actually playing. You can avoid this by removing the MBID from the tags, so Last.fm has to trust your artist/album/title info.

[SilverDogg]

im having the same problem iris is having. i get the error message stating playback was submitted previously.

ive tried deleting the cache, didnt work.
ive tried reinstalling xmp-scrobbler, didnt work.
i tried with both 0.9.6 and 0.9.7pre, didnt work.

dont really know what more there is to try? even older versions? a completely fresh install of xmplay and xmp-scrobbler perhaps?

[Dotpitch]

im having the same problem iris is having. i get the error message stating playback was submitted previously.

So it keeps saying that, for each track you play? What Windows do you have, and where did you delete the cache? Could you post a part of xmp-scrobbler.log?

[SilverDogg]

yup, each track.

windows 8, had the same problem on my win 7 computer, but that seems to have fixed itself somehow  .

deleted the cache in /xmplay/

Code SelectExpand

2013-09-22 18:09:06 [INFO] Hello, this is xmp-scrobbler Pre-0.9.7.
2013-09-22 18:09:10 [INFO] There are 0 entries in cache.
2013-09-22 18:09:11 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-22 18:09:11 [INFO] The current track is "Hanging By A Thread" by Billy Talent.
2013-09-22 18:09:13 [INFO] Successfully connected to the Last.fm server.
2013-09-22 18:11:05 [INFO] Track added to cache for submission.
2013-09-22 18:11:05 [INFO] Preparing to submit 1 track from cache.
2013-09-22 18:11:06 [INFO] Submission succeeded.
2013-09-22 18:13:04 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-22 18:13:04 [INFO] The current playback was already submitted in the previous XMPlay execution.
2013-09-22 18:17:30 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-22 18:17:30 [INFO] The current playback was already submitted in the previous XMPlay execution.

[Dotpitch]

Is it correct that your track doesn't have an album tag? Could you clear the cache and then play some tracks which do have an album tag?

[SilverDogg]

nope its not correct. all my files have the correct tags. then again i dont know how musicbrainz work, but everything i rip through eac gets tagged.

deleted the cache again and actually thought it would work this time, but once again i was let down.

Code SelectExpand

2013-09-25 12:26:17 [INFO] Hello, this is xmp-scrobbler Pre-0.9.7.
2013-09-25 12:26:46 [INFO] There are 0 entries in cache.
2013-09-25 12:26:46 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-25 12:26:46 [INFO] The current track is too short to be submitted (must be at least 30 seconds long).
2013-09-25 12:26:48 [INFO] Successfully connected to the Last.fm server.
2013-09-25 12:27:13 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-25 12:27:13 [INFO] The current track is "Let's Just Say (Air Fortress-With Extra Whipped Creme)" by Advantage: proGrammar.
2013-09-25 12:27:46 [INFO] Track added to cache for submission.
2013-09-25 12:27:46 [INFO] Preparing to submit 1 track from cache.
2013-09-25 12:27:46 [INFO] Submission succeeded.
2013-09-25 12:29:14 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-25 12:29:14 [INFO] The current playback was already submitted in the previous XMPlay execution.
2013-09-25 12:31:20 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-25 12:31:20 [INFO] The current playback was already submitted in the previous XMPlay execution.
2013-09-25 12:32:46 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-25 12:32:46 [INFO] The current playback was already submitted in the previous XMPlay execution.

[Dotpitch]

You can ignore the MusicBrainz message, it won't stop the plugin from scrobbling. Could you enable the debug log (in the configuration of xmp-scrobbler)? Let's hope that gives some clues...

[SilverDogg]

Code SelectExpand

2013-09-26 11:45:56 [DEBUG] The track has been closed.
2013-09-26 11:45:56 [DEBUG] A new track has been opened.
2013-09-26 11:45:56 [DEBUG] Fetching the track data.
2013-09-26 11:45:56 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-26 11:45:56 [DEBUG] Track data fetch ended.
2013-09-26 11:45:56 [DEBUG] PlayTime: 346 Start: 02013-09-26 11:45:56 [INFO] The current playback was already submitted in the previous XMPlay execution.
2013-09-26 11:51:11 [DEBUG] The track has been closed.
2013-09-26 11:51:11 [DEBUG] A new track has been opened.
2013-09-26 11:51:11 [DEBUG] Fetching the track data.
2013-09-26 11:51:11 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-26 11:51:11 [DEBUG] Track data fetch ended.
2013-09-26 11:51:11 [DEBUG] PlayTime: 314 Start: 02013-09-26 11:51:11 [INFO] The current playback was already submitted in the previous XMPlay execution.
2013-09-26 11:55:59 [DEBUG] The track has been closed.
2013-09-26 11:56:00 [DEBUG] A new track has been opened.
2013-09-26 11:56:00 [DEBUG] Fetching the track data.
2013-09-26 11:56:00 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-26 11:56:00 [DEBUG] Track data fetch ended.
2013-09-26 11:56:00 [DEBUG] PlayTime: 287 Start: 02013-09-26 11:56:00 [INFO] The current playback was already submitted in the previous XMPlay execution.
2013-09-26 12:01:21 [DEBUG] The track has been closed.
2013-09-26 12:01:22 [DEBUG] A new track has been opened.
2013-09-26 12:01:22 [DEBUG] Fetching the track data.
2013-09-26 12:01:22 [INFO] No valid MusicBrainz ID found, consider using MusicBrainz taggers to tag this file properly.
2013-09-26 12:01:22 [DEBUG] Track data fetch ended.
2013-09-26 12:01:22 [DEBUG] PlayTime: 321 Start: 02013-09-26 12:01:22 [INFO] The current playback was already submitted in the previous XMPlay execution.

didnt get anything out of this myself, but perhaps you can?


edit: just thought of something. i moved my entire xmplay-folder from \program\ to \music\ some time ago, could this perhaps be the reason for breaking the scrobbling?

[Dotpitch]

didnt get anything out of this myself, but perhaps you can?

Hmm, no, that doesn't really tell us anything.

i moved my entire xmplay-folder from \program\ to \music\ some time ago, could this perhaps be the reason for breaking the scrobbling?

I don't think so, xmp-scrobbler uses relative paths.

[edit]
What did you set your 'Delay info fetch' to? Default is 10.
[/edit]

[SilverDogg]

it was actually not started at all right now. was set to 0 (but off). setting it on 10 and starting it worked like a charm.

thank you very much for the help!

[Dotpitch]

setting it on 10 and starting it worked like a charm. thank you very much for the help!

You're welcome . I'm glad it's solved by something so simple!

[raina]

Hmm... Anybody else experiencing crashes with Windows 10 (Pro 64-bit)?

[sat0ri]

Hmm... Anybody else experiencing crashes with Windows 10 (Pro 64-bit)?

It started crashing today and I'm on Windows 7 x64.

[Maddieman]

Hi, this is Jon from Last.fm.

The crashing is most likely due to changes we've made to our API this week.  You can read about this problem here:
https://getsatisfaction.com/lastfm/topics/xmp-scrobbler-for-xmplay-returns-phrase-debug-unable-to-handshake-sleeping

Before it crashes, what we're seeing in the xmp-scrobbler.log is:

2015-08-20 15:20:50   [DEBUG] A new track has been opened.
2015-08-20 15:20:50   [DEBUG] Initializing the submission library...
2015-08-20 15:20:50   [DEBUG] Operating through proxy: localhost:8888
2015-08-20 15:20:50   [DEBUG] Loading cache file.
2015-08-20 15:20:50   [DEBUG] Cache loaded, scheduling handshake.
2015-08-20 15:20:50   [DEBUG] Audio info: 2 channels, 96000 Hz.
2015-08-20 15:20:52   [DEBUG] Handshake response: client up to date.

(Previously it was reporting "[DEBUG] Handshake failed: Invalid client." )

It's running through proxy so we can trace the requests, and what I'm seeing Charles is:

1 UPTODATE
2 04e2e9d9f71c4fd4cfaec45444c4ebc3
3 http://post2.audioscrobbler.com/protocol_1.1
4 INTERVAL 1
5

Which seems ok? Unfortunately xmplay is crashing before any further requests or logs are made, so it's hard to determine what exactly is going wrong.  Another issue is that it appears to be using a deprecated version of a deprecated version of our scrobbling protocol (scrobble 1.1., as opposed to 1.2, or 2.0 )

We have a couple of people looking into this, but if possible we'd very much like to have the source code of the latest version of the plugin for reference (Pre-0.9.7.).  Thanks in advance.