GoCubs Wrote: > It also seems to cause my server to briefly hang while it's trying to > send the data... as a side note, could AudioScrobbler be updated to > use Asysnc http calls?
I've been noticing brief hangs lately, but I've never quite pinned it down to the Scrobbler... The plugin is much much better at doing async submission than it used to be, but there is still a window where it can block for a few seconds. The block is supposed to be at most five seconds, which should be long enough to be covered by all the players buffers except the original SliMP3. However your trace shows that block lasting more like 9 seconds (it's the interval between the "Trying to connect" line and the "connected"). Any perl wizards fancy taking a look at this? I've never been able to get rid of this window, try as I might. If you are experiencing mid-track drop-outs, you can turn off async submission. The plugin will then submit synchronously (which can take a long time) but will do so between tracks rather than in the middle. Might be less annoying, depending. See the readme to see how to do this. Also - to answer the original question - the plugin keeps a list of any tracks for which submission has failed. It's almost human readable: look for a file called PendingSongList_userid. It's in /tmp on Linux, not quite sure where it ends up on Windows... If that accumulates tracks then the submissions haven't been succesful - but the plugin will keep trying. Ian -- iwp ------------------------------------------------------------------------ iwp's Profile: http://forums.slimdevices.com/member.php?userid=409 View this thread: http://forums.slimdevices.com/showthread.php?t=18305 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
