Perhaps you should copy your emails into the bug report, to ensure that everyone who is seeing this issue, and more importantly the developers, see them.
>I have seen sporadic instances of a reboot cycle, but only on wireless >SQBen. I have never seen a previously connected to slimserver, wired >SQB spontaneously reboot. > I only have wireless SBs. I haven't tried a wired connection direct to the server yet. I need to find a crossover cable. Have you seen the issue with a direct connection? I can't recall seeing the problem with streaming radio, but I don't often play many radio streams, and then they are generally live feeds (one "track"), thus don't have transitions. I don't recall seeing the SB screen freeze up either. Only the occasional sporadic reboot. >Finally, I have an mp3 file that plays fine in a player like >foobar2000, but locks up slimserver/softsqueeze on windows at the >transition like other random tracks. The difference being that this >particular track *always* locks at the transition while other tracks do >not. > Have you tried playing the track on a different SB? Perhaps you could consider attaching it to the bug report? >Check the NIC drivers on your server. I believe I have the latest. >Are there any messages in the Administrative Tools event log around the time >that the SQB has trouble? No. >Look at services to make sure you don't have a >sqld (MySQL) running from an older version of slimserver (check the >folder name of the service properties "dir /x"). I run my own MySQL instance, not the built-in Slimserver instance. >For softsqueeze, make >sure you are using the MP3 Plugin and not the JLayer one. Make sure >Audio/Audio Mixer is set to the correct sound card. > All configured fine. >Use a crossover cable to connect your slimserver and the SQB directly. >Let the slimserver play (no plugins, no web browser open, no debugging >and no network statistics) until you get the problem. Graduate to only >the slimserver and a wired SQB3 on your network. If you don't get the >transition problems after a week or two of playing, then work your way >forwards by adding things that you use normally. Hopefully you'll find >a device with a faulty NIC/driver on the network or a bad plugin. > That was the next thing I was going to try out - eliminating the wireless connection, and then the router. Phil _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
