Triode;613942 Wrote: > Well the log entries don't seem to match up exactly in time, but this > indicates that the first time you tried to browse a playlist, the > helper app did not get all the data from spotify and hence times out. > This occurs 3 times and then the server restarts the helper app. This > causes it to connect to a different server at the spotify end which may > then work (can't see from the log). > > At a similar time there is something else going on which is not related > to spotify: > > Code: -------------------- > > > [11-02-25 22:15:29.9274] Slim::Utils::Scanner::scanDirectory (320) Found 12128 files in E:\My EMusic > [11-02-25 22:15:36.4514] Slim::Utils::Scanner::scanDirectory (357) ERROR SCANNING E:\My EMusic\7digital\Johnny Cash > CANNING E:\My EMusic\paul_simon\Mrs. Robinson.wma: Track is DRM-protected > [11-02-25 22:17:38.6855] Slim::Utils::Scanner::scanDirectory (357) ERROR SCANNING E:\My EMusic\paul_simon\The Boxer.wma: Track is DRM-protected > [more of these - not relevant?] > -------------------- > > > > I don't know what caused this. > > However it does not explain what you are saying about the players > disconnecting. At present when spotify does not respond, you get a > frozen menu on a classic player with an animating progress dial which > clears once it gives up retrying - at present this is 4 * 35 seconds - > after this an error should be displayed and control pass back to the > menus. I am thinking I will reduce the retrys to 3 (can't change the > timeout as its within the server code) > > Which player type is this on?
this is on a Squeezebox, but have also had it on a Duet with the same server. An automatic rescan of the library is going on at the same time - I've now changed the setting so that this is scheduled at a different time. now I know what you need I'll post log entries from both logs if it happens again. Maybe each time it happened was due to a combination of external events (for example: Spotify server response/library scan errors...) rather than a single issue. I think reducing the retries would be a good idea. From a user point of view it is frustrating just waiting - I'd rather know there was a problem sooner rather than later. Unless waiting longer gives a chance of fixing the prob of course... thanks for looking at it though. -- trautigan ------------------------------------------------------------------------ trautigan's Profile: http://forums.slimdevices.com/member.php?userid=17162 View this thread: http://forums.slimdevices.com/showthread.php?t=79706 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
