track.scrobble is broken

  • 5
  • Problem
  • Updated 1 year ago
track.scrobble remains broken since the conversion in August.
1. Scrobble corrections no longer generate any feedback; eg. If I scrobble an artist tag of "Nick Cave and the Bad Seeds" it is "corrected to "Nick Cave & the Bad Seeds", but the scrobble feedback xml does not reflect this adjustment:<artist corrected="0">Nick Cave and the Bad Seeds</artist><album corrected="0">Push the Sky Away</album><albumArtist corrected="0">Nick Cave and the Bad Seeds</albumArtist>
should be <artist corrected="1">Nick Cave & the Bad Seeds</artist> etc

2. Scrobble rejections no longer supply an error message in the xlm response, there used to be a rejection reason returned as a attribute:
<ignoredMessage code="1"></ignoredMessage>
should be something like <ignoredMessage code="1">Artist name failed filter: Various Artists</ignoredMessage>

3. An scrobble submission with an *AlbumArtist* tag begining with the string "Various Artists" is now rejected. It used be that an Artist tag of "Various Artists" was rejected, and I can accept this, but you should not be applying this rule to the AlbumArtist tag, as it often used to collect together tracks from compilation albums. This behaviour changed with the new web site.
Photo of Barry4679

Barry4679

  • 43 Posts
  • 12 Reply Likes

Posted 2 years ago

  • 5
Photo of shiitake

shiitake

  • 1 Post
  • 0 Reply Likes
I'm also seeing this issue. I'm getting a response that the scrobble was ignored but there is not info as to why. 
<?xml version="1.0" encoding="utf-8"?>
<lfm status="ok">
    <scrobbles ignored="1" accepted="0">
        <scrobble>
            <track corrected="0">No Children</track>
            <artist corrected="0">The Mountain Goats</artist>
            <album corrected="0" />
            <albumArtist corrected="0"></albumArtist>
            <timestamp>1442416084</timestamp>
            <ignoredMessage code="1"></ignoredMessage>
    
        </scrobble>
  
    </scrobbles>
</lfm>
Photo of Devin

Devin

  • 1 Post
  • 0 Reply Likes
I am also having the same issue

<?xml version="1.0" encoding="utf-8"?><lfm status="ok">
  <scrobbles ignored="1" accepted="0">
    <scrobble>
      <track corrected="0">Gentleman</track>
      <artist corrected="0">Psy</artist>
      <album corrected="0" />
      <albumArtist corrected="0"></albumArtist>
      <timestamp>1468604141317</timestamp>
      <ignoredMessage code="1"></ignoredMessage>
    </scrobble>
  </scrobbles>
</lfm>
(Edited)
Photo of don paper

don paper

  • 3 Posts
  • 0 Reply Likes
Anyone found the solution?Im also having the same issue
(Edited)
Photo of Daniel Pinto

Daniel Pinto

  • 1 Post
  • 0 Reply Likes
DITTO
Photo of Barry4679

Barry4679

  • 43 Posts
  • 12 Reply Likes
I am still having both issues (no longer any rejection message, nor any tag correction message). It has been like that for 12 months now. I have asked in multiple threads during the year, but they have made zero response to any of my queries. I have no idea if they even recognise it as an issue.

It has broken functionality in my scrobbler.

It doesn't appear that they have retained anybody with enough skills to work on the core of the product. They are just doing fluffy stuff around the edges.

What gets me is the refusal to confirm issues, or to say whether the api is now permanently altered. Now matter how patiently you have waited for things to settle down, or how politely you ask, you get nothing. .... a year!

I feel for the people working in what must be a crap job in there, picking up the pieces. But IMO they are doing a crap job of that crap job. ie. not keeping their api customers|partners|whatever in the loop. 

I looked at LFM's Alexa stats the other day. LFM were 1,331st in the USA based upon page views when this beta was prematurely implemented. They have now dropped down to 2,163rd. The number of sites linking to them have dropped by 8% over the year. ... no prizes for guessing why; they have zero respect for their supporters. ... It's happening on your watch James Scott.