The condition for preventing standby is an OR on all the standby handlers (active streams, controller active, network, processes, active shares, ...). If any of these signals activity, automatic standby is prevented. Why would you like to ignore active streams handler? It signals activity only if the server is streaming to any of the attached clients (local or remote). So ignoring it could make the server go to standby while media is being watched on a client...Ok. So I assume that the final condition to keep the server alive is an AND between Inspecting PowerController Inspecting Remote Client Inspecting Active Streams Inspecting TV Controller Inspecting Processes Inspecting Active Network Inspecting Active Shares Inspecting EPG Grabbing
As "Inspecting Active Streams" is on when I'm watching TV (and accessory also "Inspecting Active Network") what you think about adding an option to bypass "Inspecting Active Streams"? By defaut the plugin pay attention to that condition and with this option selected, it bypass this inspection.
Thanks for your feedback!
This issue should better be posted in a general help thread, since I do not think it has something to do with PS++. But I only assume this, because I (and anybody else) cannot have an idea what went wrong with your installation unless you provide log files covering the crash. Search in the wiki (or look at the first post in this thread) how to provide logs.Hello everyone,
I just did a fresh install of windows 8 x64 Pro on my HTPC and set up MP 1.4.0 (D/L it yesterday 6/23/2013). Configured MP for Client & Server. Being on the cutting edge is fun, but can be frustrating (I feel like I am on the cutting edge, but I am really a few paces back). I configured PowerScheduler ++ for the HTPC setting and used the Plug and Play setting. To test it out I walked away from MP when it was on the home screen and 30 minutes later it was sleeping. I then clicked on the space bar and the computer jumped to life, but MP crashed and gave me an error. I need to make sure that I check this one more time. I can confirm that I have turned OFF the fast resume function on my machine.
Before I try this again, is there anything that I need to keep in mind since I am using MP 1.4.0 and windows 8 x64 Pro that I may have missed in the configuration and set up? Are others having problems with this?
If there are answers in a Wiki somewhere I have not been able to find them so a link would be very helpful.
Thank you
-S
Sorry. I made a big mistake. It's remote client i want to bypass and of course when watching TV the active stream will keep server alive. And yes it's an OR... shame on me ;-)
The condition for preventing standby is an OR on all the standby handlers (active streams, controller active, network, processes, active shares, ...). If any of these signals activity, automatic standby is prevented. Why would you like to ignore active streams handler? It signals activity only if the server is streaming to any of the attached clients (local or remote). So ignoring it could make the server go to standby while media is being watched on a client...Ok. So I assume that the final condition to keep the server alive is an AND between Inspecting PowerController Inspecting Remote Client Inspecting Active Streams Inspecting TV Controller Inspecting Processes Inspecting Active Network Inspecting Active Shares Inspecting EPG Grabbing
As "Inspecting Active Streams" is on when I'm watching TV (and accessory also "Inspecting Active Network") what you think about adding an option to bypass "Inspecting Active Streams"? By defaut the plugin pay attention to that condition and with this option selected, it bypass this inspection.
Thanks for your feedback!
Michael
I assume you mean "active streams" by "remote client"? Then I gave you my thoughts in my last post...Michael,
Have you thought about my new option idea? Bypassing the "remote client" check?
Thank you.
...Why would you like to ignore active streams handler? It signals activity only if the server is streaming to any of the attached clients (local or remote). So ignoring it could make the server go to standby while media is being watched on a client...
Otherwise (if you mean "remote client activity"): There is often no way for the server to see, if and why a remote client needs the server. But the client always signals its activity to the server and the server keeps alive as long as any remote client is active. Bypassing this would mean to standby the server while it might still be needed...