home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Products
TV-Server
PowerScheduler++ test versions
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="michael_t" data-source="post: 709249" data-attributes="member: 85139"><p><strong>AW: Re: AW: Re: PowerScheduler++ Version 1.2.0.10 (RC1)</strong></p><p></p><p>Well, this is much more than a new feature. If implemented properly it would need a rework of PowerScheduler(++), because the main focus of the plugin is now to prevent standby when it is not appropriate (e.g. while a user is watching media or the system is recording). The proposed philosophy would require PS(++) not only to prevent unwanted standby but to handle standby actively depending on different system states:</p><ol> <li data-xf-list-type="ol">There is no automatic standby after some time of user or system inactivity. The HTPC will only go to standby when the user presses power off / remote off.</li> <li data-xf-list-type="ol">When the HTPC is in standby it will wakeup automatically for scheduled recordings, EPG grabbing etc. and goto standby again afterwards. When it is on it will do scheduled recordings etc. but not go to standby afterwards.</li> <li data-xf-list-type="ol">When you press power off / remote off while the HTPC is recording (or performing some other activity preventing power off) it will go to away mode and only go to standby after all activities preventing power off are finished.</li> <li data-xf-list-type="ol">When the HTPC woke up from standby automatically for scheduled recordings, EPG grabbing etc. or is in away mode and there is any user activity on the system it will not goto standby again but stay on until the user presses power off / remote off.</li> </ol><p>Of course it should still be possible to define an idle timeout for automatic standby, if wanted. Then the system states would be like this:</p><ol> <li data-xf-list-type="ol">There is an automatic standby after some time of user or system inactivity. The HTPC will also go to standby when the user presses power off / remote off.</li> <li data-xf-list-type="ol">When the HTPC is in standby it will wakeup automatically for scheduled recordings, EPG grabbing etc. and goto standby again afterwards. When it is on it will do scheduled recordings etc. and go to standby after the defined idle timeout.</li> <li data-xf-list-type="ol">When you press power off / remote off while the HTPC is recording (or performing some other activity preventing power off) it will go to away mode and only go to standby after all activities preventing power off are finished.</li> <li data-xf-list-type="ol">When the HTPC woke up from standby automatically for scheduled recordings, EPG grabbing etc. or is in away mode and there is any user activity on the system it will goto standby again after some time of user or system inactivity or when the user presses power off / remote off.</li> </ol><p>This is all thought for a single-seat scenario. In multi-seat an active remote client (i.e. needing the TV-server) could be handled like a server activity preventing power off (e.g. active shares). But I am not sure if there are no side effects. I really have to design that carefully before realizing it. Any ideas / comments are welcome.</p><p></p><p>Michael</p></blockquote><p></p>
[QUOTE="michael_t, post: 709249, member: 85139"] [b]AW: Re: AW: Re: PowerScheduler++ Version 1.2.0.10 (RC1)[/b] Well, this is much more than a new feature. If implemented properly it would need a rework of PowerScheduler(++), because the main focus of the plugin is now to prevent standby when it is not appropriate (e.g. while a user is watching media or the system is recording). The proposed philosophy would require PS(++) not only to prevent unwanted standby but to handle standby actively depending on different system states: [LIST=1] [*]There is no automatic standby after some time of user or system inactivity. The HTPC will only go to standby when the user presses power off / remote off. [*]When the HTPC is in standby it will wakeup automatically for scheduled recordings, EPG grabbing etc. and goto standby again afterwards. When it is on it will do scheduled recordings etc. but not go to standby afterwards. [*]When you press power off / remote off while the HTPC is recording (or performing some other activity preventing power off) it will go to away mode and only go to standby after all activities preventing power off are finished. [*]When the HTPC woke up from standby automatically for scheduled recordings, EPG grabbing etc. or is in away mode and there is any user activity on the system it will not goto standby again but stay on until the user presses power off / remote off. [/LIST] Of course it should still be possible to define an idle timeout for automatic standby, if wanted. Then the system states would be like this: [LIST=1] [*]There is an automatic standby after some time of user or system inactivity. The HTPC will also go to standby when the user presses power off / remote off. [*]When the HTPC is in standby it will wakeup automatically for scheduled recordings, EPG grabbing etc. and goto standby again afterwards. When it is on it will do scheduled recordings etc. and go to standby after the defined idle timeout. [*]When you press power off / remote off while the HTPC is recording (or performing some other activity preventing power off) it will go to away mode and only go to standby after all activities preventing power off are finished. [*]When the HTPC woke up from standby automatically for scheduled recordings, EPG grabbing etc. or is in away mode and there is any user activity on the system it will goto standby again after some time of user or system inactivity or when the user presses power off / remote off. [/LIST] This is all thought for a single-seat scenario. In multi-seat an active remote client (i.e. needing the TV-server) could be handled like a server activity preventing power off (e.g. active shares). But I am not sure if there are no side effects. I really have to design that carefully before realizing it. Any ideas / comments are welcome. Michael [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
TV-Server
PowerScheduler++ test versions
Contact us
RSS
Top
Bottom
