New version failing to scrobble to Last.fm?

  1. Steveo

    hello. since upgrading to the newest version (3.1.3), it seems like it isn't effectively audioscrobbling my songs played to Last.fm. I can't tell if this is an issue with Synergy or with the Last.fm service, which you never seem to know if it's working properly or not... Has anyone else had this issue? thanks.

  2. Greg Hurrell

    Nobody has reported any issues. To investigate the problem further you should try turning on Audioscrobbler logging.

    You can also rule out possible local causes by performing some of the basic troubleshooting hints mentioned here:

    https://wincent.dev/s/bugs/

  3. Yaniv

    mine stopped scrobbling as well. ok, i turned on scrobbler logging... what now, wincent? thanks

  4. Greg Hurrell

    Well, look at the Console and see if any errors are reported. The Console can be found at /Applications/Utilities/Console

  5. Yaniv

    ha! it's working again! i guess it was only an extra-long hiccup of the last.fm servers... thanks anyway.

  6. tinsun

    I often have trouble when the computer has been sleeping overnight, since 3.1.3 it seems to happen more often, but it may have to do with the unresponsive last.fm servers. What do you think?

    2007-06-26 13:26:41.721 Synergy[2352] Audioscrobbler: Enqueuing object: { 

       WOAlbum = "Pebbles & Ripples"; 
   WOArtist = "Bonnie \"Prince\" Billy"; 
   WODate = "2007-06-26 11:26:41"; 
   WOLength = 299; 
   WOMBID = ""; 
   WOTrack = "Babylon System";

    } 2007-06-26 13:26:41.721 Synergy[2352] Audioscrobbler: Number of items currently on the queue: 45 2007-06-26 13:26:41.721 Synergy[2352] Audioscrobbler: Queue was non-empty, last attempt failed: processing item 2007-06-26 13:26:41.721 Synergy[2352] Audioscrobbler: Will handle next item on the queue after delay (Audioscrobbler specified delay in seconds: 1) 2007-06-26 13:26:42.721 Synergy[2352] Audioscrobbler: Submission previously failed, will retry 2007-06-26 13:26:42.722 Synergy[2352] Audioscrobbler: Will perform submission using URL: http://87.117.229.205:80/protocol_1.1 2007-06-26 13:26:42.722 Synergy[2352] Audioscrobbler: Submission as URL-encoded string is: u=username_removed&s=ea9b601fd2e88b2bb64327bb552386bc&a[0]=Schoolly%20D&t[0]=Here%20We%20Go%20Again&b[0]=Smoke%20Some%20Kill&m[0]=&l[0]=167&i[0]=2007-06-25%2019%3A25%3A36 2007-06-26 13:26:42.722 Synergy[2352] Audioscrobbler: Submission as data is: <753d7375 6767615f 61766472 61672673 3d656139 62363031 66643265 38386232 62623634 33323762 62353532 33383662 6326615b 305d3d53 63686f6f 6c6c7925 32304426 745b305d 3d486572 65253230 57652532 30476f25 32304167 61696e26 625b305d 3d536d6f 6b652532 30536f6d 65253230 4b696c6c 266d5b30 5d3d266c 5b305d3d 31363726 695b305d 3d323030 372d3036 2d323525 32303139 25334132 35253341 3336> 2007-06-26 13:26:42.722 Synergy[2352] Audioscrobbler: Starting connection attempt 2007-06-26 13:26:42.722 Synergy[2352] Audioscrobbler: Waiting for submission response 2007-06-26 13:27:57.725 Synergy[2352] NSURLConnection for URL http://87.117.229.205:80/protocol_1.1 returned error: timed out

  7. Greg Hurrell

    Looks like the connection is timing out, which is an indication of a network connectivity problem somewhere between your machine and the last.fm servers. There's nothing much you can do about this, other than wait; Synergy will keep retrying and eventually the queued-up tracks will be submitted.

Reply

This topic is now closed.

topic index