I have tried everything in my power to help eliminate these error messages with various setting changes in squeezebox server such as:
-Power On Resume: Stop at power off/Reset playlist at power on -Changing the player's Audio MP3 Streaming Method to Direct Streaming -Disable UPnP Client -Server priority= -6 Above Normal I have also added multiple fully registered accounts to Slacker and Sirius Radio (I had to pay more for these extra accounts) and added these secondary accounts to separate Squeezebox clients. I'm not sure which of these helped or not, but the frequency of getting these error messages (mentioned in the thread title) are less frequent. I can't pinpoint what is left to eliminate these errors once in for all; however, I am hoping that Andy could please offer any suggestions that could prevent these errors. I still think it would be a good idea for Andy to take a closer look at the way clients start/stop audio streams; and, see if there's a provision that could be made on mysqueeebox.com to flush old audio streams (even if the audio stream is already stopped on the client). As long as the music service provider doesn't continuing to receive a "ghost"/stray audio stream caused by a squeezebox/client audio stream anomaly in TCP sockets, we should be fine. All I'm hoping for Andy (I know its a PITA), but having an extra provision to cleanly stop any previous audio streams under a user account for respective music service (that's not heard on the client), it would be greatly appreciated by not only the end user; but, also by the Internet service provider as well. This would also help reduce issues on mysqueezebox with audio stream leaks which can prevent having to restart thebackend (possibly caused by audio stream leaks such as this). Of course, the above pararaph is all pure speculation. Not knowing the techical reasons behind having a backend mysquezebox.com "proxy", in general it makes sense to move over these functionalities to the user's personal mysqueezebox server... where the user can manually enter their username/passwords for each music service. This would reduce lag time, less dependancies, less money/time/resources to maintain mysqueezebox.com; and just offer an auto-updater for squeezebox.com server for critical changes. Bottom line, this would also reducethe likelyhood of unaccounted for audio streams going into the mysqueezebox.com abyss due to Internet connetion hickups, timeouts, etc since there's an extra component that's in between the users's squeezebox server and each music service provider. Anyway, please.. in the short term goal at least add a provision to use a more agressive method to cut off any previous "ghost"/remnant audio connections to the respective music service (caused by TCP/IP connetion "hickups" not recovered correctly) before starting a new song/station from the same service provider. Thanks for your time to help improve the reliability of your service. Sincerely, Michael Anonymous Senior Network Engineer from a Federal Government Agency -- mkanet ------------------------------------------------------------------------ mkanet's Profile: http://forums.slimdevices.com/member.php?userid=7965 View this thread: http://forums.slimdevices.com/showthread.php?t=71255 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
