Triode;614767 Wrote: > Just to explain the above - these entries are not playback, they are > used to build the metadata for a track. Specifically if you have a > large playlist and stop/restart the server then the plugin with fetch > details of each track from the helper app as only the url is stored by > the server. Its normal to get large numbers of them and ideally they > happen rapidly one after each other (1.3.1 adds a queue in the server > so not all the queuing is done in the helper app) > > > > These errors means that the server can't find the information to allow > writing of the playlist information to disk. If you have a long > playlist then you need to increase the playlist size in the spotify > settings page to exceed it. > > > > This could definately be a problem. The plugin bypasses the normal > server audio handling and sends the audio stream as flac from the > helper app direct to the player (after verifying that it is a player > which it is streaming to). This means that even if you only stream > 160k from spotify, this is converted to flac (upto 1M) by the helper > app and sent over your local network at this rate. Hence you do need > good bandwidth on your local network.
A useful and comprhensive answer as usual, with some good tips (playlist size esp.) I have a set of homeplugs kicking about that I may try if I get this again - but the good news (for me definitely) is that after 36 hours of on and off usage, using a variety of ways to access Spotify (not just playlists but also search, individual tracks...) there has been no repeat of any rebuffering issue. So far so good - in fact,fantastic. -- 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
