PowerScheduler++ test versions (3 Viewers)

[nikigraus]

Re: PowerScheduler++ Test Version 1.2.5.5 for MP 1.2.x / 1.3 Alpha

Hi michael_t and doveman

I don't think it's a problem of Windows. I looked at the lines in the log

2011-12-26 16:05:55.636538 [PS StandbyWakeup(13)]: PS: SetStandbyMode(StandbyAllowed)
2011-12-26 16:05:55.636538 [PS StandbyWakeup(13)]: PS: System is idle and may go to standby
2011-12-26 16:05:55.637538 [PS StandbyWakeup(13)]: PS: Active standby is disabled - standby is handled by Windows
2011-12-26 16:06:01.467872 [(5)]: PS: RegisterRemote tag: 1, uris: http://localhost:31458/1252eb20_6464_445a_ab21_7bf7163e470a/bwsfqpnlzi5cmjff8otwesz0_25.rem, http://localhost:31458/1252eb20_6464_445a_ab21_7bf7163e470a/bwsfqpnlzi5cmjff8otwesz0_25.rem
2011-12-26 16:06:01.474872 [(5)]: PS: User activity on local client detected at 16:05:45
2011-12-26 16:06:02.542933 [PowerEventThread(9)]: OnPowerEvent: PowerStatus: Suspend
2011-12-26 16:06:02.542933 [PowerEventThread(9)]: OnPowerEventHandler: PowerStatus: Suspend
2011-12-26 16:06:02.544934 [PowerEventThread(9)]: TvController.OnSuspend()

At 16:05:55 PowerScheduler allows Windows to go to standby.
Then just in the meantime, Windows decides to fall asleep, just before PS reports that there is user activity. Maybe it was too late then and Windows was already going to standby.

If PS really would have tried to prevent standby, there should be a call to SetStandbyMode(StandbyPrevented)?

Or am I misinterpreting something?

Regards, Daniel

 

[michael_t]

AW: Re: PowerScheduler++ Test Version 1.2.5.5 for MP 1.2.x / 1.3 Alpha

Hi michael_t and doveman

I don't think it's a problem of Windows. I looked at the lines in the log

2011-12-26 16:05:55.636538 [PS StandbyWakeup(13)]: PS: SetStandbyMode(StandbyAllowed)
2011-12-26 16:05:55.636538 [PS StandbyWakeup(13)]: PS: System is idle and may go to standby
2011-12-26 16:05:55.637538 [PS StandbyWakeup(13)]: PS: Active standby is disabled - standby is handled by Windows
2011-12-26 16:06:01.467872 [(5)]: PS: RegisterRemote tag: 1, uris: http://localhost:31458/1252eb20_6464_445a_ab21_7bf7163e470a/bwsfqpnlzi5cmjff8otwesz0_25.rem, http://localhost:31458/1252eb20_6464_445a_ab21_7bf7163e470a/bwsfqpnlzi5cmjff8otwesz0_25.rem
2011-12-26 16:06:01.474872 [(5)]: PS: User activity on local client detected at 16:05:45
2011-12-26 16:06:02.542933 [PowerEventThread(9)]: OnPowerEvent: PowerStatus: Suspend
2011-12-26 16:06:02.542933 [PowerEventThread(9)]: OnPowerEventHandler: PowerStatus: Suspend
2011-12-26 16:06:02.544934 [PowerEventThread(9)]: TvController.OnSuspend()

At 16:05:55 PowerScheduler allows Windows to go to standby.
Then just in the meantime, Windows decides to fall asleep, just before PS reports that there is user activity. Maybe it was too late then and Windows was already going to standby.

User activity was detected by PS++ client at 16:05:45. So it should have been detected by Windows too. But why did Windows enter standby 15 seconds later? I really do not understand it.

If PS really would have tried to prevent standby, there should be a call to SetStandbyMode(StandbyPrevented)?
Or am I misinterpreting something?

Since PS++ relies on Windows to recognize user activity and reset the idle timeout, there is no call to SetStandbyMode in this case.

Michael

 

[nikigraus]

Re: PowerScheduler++ Test Version 1.2.5.5 for MP 1.2.x / 1.3 Alpha

Okay I see.
What was the activity exactly? Have you used the remote to control MediaPortal? Maybe an IR command is not recognized by Windows as a user action?

 

[doveman]

Re: PowerScheduler++ Test Version 1.2.5.5 for MP 1.2.x / 1.3 Alpha

Okay I see.
What was the activity exactly? Have you used the remote to control MediaPortal? Maybe an IR command is not recognized by Windows as a user action?

I was browsing through my Music. Even if an IR command isn't recognised, I would have thought the cursor/menus changing should have been (or PS++ should signal it as user activity to Windows).

 

[nikigraus]

Re: PowerScheduler++ Test Version 1.2.5.5 for MP 1.2.x / 1.3 Alpha

Okay I see.
What was the activity exactly? Have you used the remote to control MediaPortal? Maybe an IR command is not recognized by Windows as a user action?

I was browsing through my Music. Even if an IR command isn't recognised, I would have thought the cursor/menus changing should have been (or PS++ should signal it as user activity to Windows).

I don't think Windows recognizes menu changing as user activity automatically, unlike Mouse or Keyboard inputs.
I will try to find out if that happens on my machine too. I use IRTrans as IR input, what do you use?

 

[michael_t]

AW: Re: PowerScheduler++ Test Version 1.2.5.5 for MP 1.2.x / 1.3 Alpha

I think you are right, Windows does not recognize MP menu or window changing as user activity. And it might be that it also does not recognize remotes if they are handled by special drivers and not as Windows HID. I did never get this kind of error, because I am using a MCE compatible remote...
I see no problem in adding a system call into the next version of PS++ that resets the Windows idle timeout on each MP user activity.

Michael

 

[nikigraus]

Re: AW: Re: PowerScheduler++ Test Version 1.2.5.5 for MP 1.2.x / 1.3 Alpha

I think you are right, Windows does not recognize MP menu or window changing as user activity. And it might be that it also does not recognize remotes if they are handled by special drivers and not as Windows HID. I did never get this kind of error, because I am using a MCE compatible remote...
I see no problem in adding a system call into the next version of PS++ that resets the Windows idle timeout on each MP user activity.

Michael

That sounds reasonable.
Thanks for your work!
Will PS++ become part of the official MP release sometimes?

 

[michael_t]

AW: Re: AW: Re: PowerScheduler++ Test Version 1.2.5.5 for MP 1.2.x / 1.3 Alpha

Will PS++ become part of the official MP release sometimes?

I don't know... Some time ago the MP dev team contacted me. They were thinking about replacing PS with PS++ for the 1.3 version, but I did not hear anything more since that time...

Michael

 

[doveman]

Re: PowerScheduler++ Test Version 1.2.5.5 for MP 1.2.x / 1.3 Alpha

I don't think Windows recognizes menu changing as user activity automatically, unlike Mouse or Keyboard inputs.I will try to find out if that happens on my machine too. I use IRTrans as IR input, what do you use?

I'm using my Hauppauge remote, so it just uses the Remote section in MP config (and HCWHelper.exe I think).

I think you are right, Windows does not recognize MP menu or window changing as user activity. And it might be that it also does not recognize remotes if they are handled by special drivers and not as Windows HID. I did never get this kind of error, because I am using a MCE compatible remote...
I see no problem in adding a system call into the next version of PS++ that resets the Windows idle timeout on each MP user activity.

Michael

That sounds like a good solution. Thanks.

 

[michael_t]

AW: Re: PowerScheduler++ Test Version 1.2.5.5 for MP 1.2.x / 1.3 Alpha

doveman

Could you please test this test version 1.2.5.6 if it fixes your problem with standby?

Michael