Whenever I've done an upgrade that has forced a server rescan, it's never told me that's what it's going to do. My player becomes totally unresponsive during a rescan, which I imagine would be quite alarming if you didn't know what was going on. It's certainly not the first impression of the new version that you want users to have!
Max Triode Wrote: > >> Did that. And updated firmware. Slimserver took more than three > seconds > >> to respond to any request via the remote with the new version. > Since > >> then I have been trying to revert to my previous SS version, > without > >> success so far (lots of Squeezebox can't find SlimServer). > >> MC > > > > Is this after allowing the server to rescan all of your music (which > may take quite a while with a large library). As the database > version changes between releases it is likely that at startup with a > new version it needs to rescan the whole library to build a > consitent new database. > > I would be interested in seeing what the Server Response Time graph in > 6.2 shows after rescanning has completed [in Server and > Network Health]. -- max.spicer The wild things roared their terrible roars and gnashed their terrible teeth and rolled their terrible eyes and showed their terrible claws but Max stepped into his private boat and waved good-bye _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
