Closed fishstik closed 6 years ago
First up - thanks for such a detailed explanation!
Can confirm this behavior.
Last.fm: track.scrobble response:
<?xml version="1.0" encoding="utf-8"?>
<lfm status="ok">
<scrobbles ignored="1" accepted="0">
<scrobble>
<track corrected="0">1.four.sokro?????</track>
<artist corrected="0">onitram.</artist>
<album corrected="0" />
<albumArtist corrected="0"></albumArtist>
<timestamp>1519241809</timestamp>
<ignoredMessage code="1"></ignoredMessage>
</scrobble>
</scrobbles>
</lfm>
We're sending it correctly - It's last.fm ignoring :/ Could be to do with the duration we're sending.
Why do you think it's the issue? The extension just shows Last.fm response and this is expected behaviour (for this track, of course).
I just tried to scrobble it using OpenWebScrobbler, but with no success.
I noticed a scrobble on SoundCloud not going through, and it looks like it's being ignored deliberately (either by the connector or Last.fm) because of unusual characters. The original track data from sc is Artist: onitram. Title: 1.four.sokro?????. This was unknown to Last.fm so I edited it to Artist: onitram Title 1.four.sokro????? (just removing the dot after the artist name). I then got the green "Now Playing" icon. Then when it came time to scrobble, the red 'ignore' icon popped up.
Expected behavior
Scrobble titles no matter how weird they are.
Current behavior
Scrobble is ignored with red X icon and "Ignored --- " tooltip. Clicking icon doesn't do anything.
Possible solution
I thought the "Looking up
Steps to reproduce (for bugs)
Environment
Screenshot: