Dandyman wrote: > I have an issue if I leave the Laptop running and the desktop auto-locks > after a while. The Squeezelite-X Window is not getting updated. I can > hear the music playing, I can pause and stop music. But I don't see what > is currently playing because the progress bar doesn't update. > The visual is stuck on some music that was played while I was at the > laptop. > > This problem only happens if I use Material Skin.
Can you describe in more detail? What do you mean by "auto-lock"? You might mean the screen locks or you might mean the computer goes into standby or sleep. If you are still hearing music, then I'm guessing the computer is still awake. Are you saying when you wake the computer or regain access to the desktop that then you can pause and start the music, but that the SLX running material skin has stopped updating? I guess I am not understanding precisely what you are seeing. That said, since the beginning of SLX development, I have faced an issue with computer sleep/wake. The problem is I basically have two applications running, SLX and squeezelite. I cannot predict which will wake up first. If the client computer has been sleeping for more than 5 minutes, The LMS server will "forget" that player. In this case it takes a while longer for the LMS Server and the squeezelite player to reconnect, long after SLX has woken up. IF the Material Skin polls the server for ino on the player, it will fail for awhile until the player regains consciousness and is reconnected to the server. For a long time, my solution was to go ahead and terminate the squeezelite process upon sleep, and then restart the player process upon wake. That way things are more orderly. But that introduced another problem. The Squeezelite process can only be successfully started if an operator is present (e.g. you touch the computer to wake it, like the keyboard or mouse). If the computer is woke with a timer or a WOL packet, the computer will wake, SLX will start squeezelite and squeezelite will abort. The way you would see this is when your computer wakes up in the middle of the night, say, to perform a backup. What you see the next day when you wake up your computer is that squeezelite says it aborted. (It really aborted in the middle of the night during the unattended wake.) But it looks bad. So in 2.1.2, I went back to the first method, but I intended to make it work better by detecting when the player does eventually re-connect to the server and then refreshing the browser (among other things). So that is why I am particularly interested in the precise details of what you are seeing. Thanks. I may need to go back to the previous way. (I'll do some testing). R Greg Dawson Squeezelite-X ------------------------------------------------------------------------ rgdawson's Profile: http://forums.slimdevices.com/member.php?userid=65236 View this thread: http://forums.slimdevices.com/showthread.php?t=108550 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
