PowerScheduler++ test versions (4 Viewers)

[doveman]

This is only true if you manually stop the playback or do some other user action. If the movie playback terminates because it reaches the movie's end, this is no activity for Windows.

Michael

OK, but from what you said "PS++ only handles standby, i.e prevents the PC from going to S3 or S4 while it is busy. This is done by calling SetThreadExecutionState (ES_SYSTEM_REQUIRED|ES_CONTINUOS) e.g. as long as a movie is beeing played" it would appear that PS++ calls something whilst a movie is being played that tells Windows it's busy, which should mean that Windows will only go into standby xx minutes (where xx is set in Windows Power Options) after it last received such a "busy" message, so whether the movie playback terminating automatically because it reached the end counts as activity should be irrelevant.

 

[michael_t]

...This is done by calling SetThreadExecutionState (ES_SYSTEM_REQUIRED|ES_CONTINUOS) e.g. as long as a movie is beeing played" it would appear that PS++ calls something whilst a movie is being played that tells Windows it's busy, which should mean that Windows will only go into standby xx minutes (where xx is set in Windows Power Options) after it last received such a "busy" message, so whether the movie playback terminating automatically because it reached the end counts as activity should be irrelevant.

The ES_CONTINUOS option lets the Windows idle counter untouched (keeps continuosly running), i.e. it will not be reset to begin counting down again.
Note: It is easily possible to change PS++'s behaviour by resetting the Windows idle counter (as you assumed is already done), but the way PS++ is implemented now is the way that all other media players work...

Michael

 

[doveman]

The ES_CONTINUOS option lets the Windows idle counter untouched (keeps continuosly running), i.e. it will not be reset to begin counting down again.
Note: It is easily possible to change PS++'s behaviour by resetting the Windows idle counter (as you assumed is already done), but the way PS++ is implemented now is the way that all other media players work...

Ah, thanks for explaining that. I would very much like to see PS++ use the alternative behaviour (maybe an option?) if you can find the time to implement it.

 

[Jay_UK]

Hi there,

+1

I agree, any user activity (including playing/watching/listening to content) in the MePo client should reset the idle counter.

J.

 

[Dragy]

Nevermind, fixed it by typing localhost in the TV Server section in the MePo config (I think I didn't had that section before? )

I am using ForTheRecord with TV Server and I think this causes that the PowerScheduler++ client thinks that the TV Server is not installed. To be clear, the TV Server IS installed and I have configured PS++.
I still get this:

 

[doveman]

Any idea why standby didn't work here? It seems that TvTimeShiftPositionWatcher might have prevented it, but I don't understand why that was being triggered as I haven't watched TV since 10:00 this morning.

 

[mm1352000]

Logs say:

2012-07-07 11:18:42.935957 [PS StandbyWakeup(14)]: PS: Active standby is disabled - standby is handled by Windows

 

[Luca Brasi]

@Dragy
Have a look here: Link

 

[doveman]

Logs say:

2012-07-07 11:18:42.935957 [PS StandbyWakeup(14)]: PS: Active standby is disabled - standby is handled by Windows

Yes, but PS++ still prevents standby if it decides there's been MP activity and it seems this TvTimeShiftPositionWatcher was what it considered to be activity.

 

[mm1352000]

@doveman: PS++ is not preventing standby... at least according to the TV Server logs.
For a while I see:

2012-07-07 10:00:45.969450 [PS StandbyWakeup(14)]: PS: StandbyWakeupThread triggered by check interval
2012-07-07 10:00:45.981451 [PS StandbyWakeup(14)]: PS: LoadSettings()
2012-07-07 10:00:46.034454 [PS StandbyWakeup(14)]: PS: SetWakeupTimer()
2012-07-07 10:00:46.035454 [PS StandbyWakeup(14)]: PS: Inspecting PowerController:
2012-07-07 10:00:46.038454 [PS StandbyWakeup(14)]: PS: Inspecting ScheduledRecordings:
2012-07-07 10:00:46.041454 [PS StandbyWakeup(14)]: PS: Inspecting XmlTvImport:
2012-07-07 10:00:46.050455 [PS StandbyWakeup(14)]: PS: Inspecting Client Plugin:
2012-07-07 10:00:46.051455 [PS StandbyWakeup(14)]: PS: No pending events found in the future which should wakeup the system
2012-07-07 10:00:46.052455 [PS StandbyWakeup(14)]: PS: CheckForStandby()
2012-07-07 10:00:46.053455 [PS StandbyWakeup(14)]: PS: Inspecting PowerController:
2012-07-07 10:00:46.054455 [PS StandbyWakeup(14)]: PS: Inspecting RemoteClient:
2012-07-07 10:00:46.054455 [PS StandbyWakeup(14)]: PS: Inspecting ActiveStreams:
2012-07-07 10:00:46.055455 [PS StandbyWakeup(14)]: PS: Inspecting ControllerActive:
2012-07-07 10:00:46.058455 [PS StandbyWakeup(14)]: PS: Inspecting ProcessActive:
2012-07-07 10:00:46.059455 [PS StandbyWakeup(14)]: PS: Inspecting ActiveNetwork:
2012-07-07 10:00:46.060455 [PS StandbyWakeup(14)]: PS: Inspecting ActiveShares:
2012-07-07 10:00:46.070456 [PS StandbyWakeup(14)]: PS: Inspecting Client Plugin (User Interface): StandbyPrevented
2012-07-07 10:00:46.071456 [PS StandbyWakeup(14)]: PS: SetStandbyMode(StandbyPrevented)
2012-07-07 10:00:46.072456 [PS StandbyWakeup(14)]: PS: System is busy and should not go to standby

In that case, the client is preventing standby. However, after some time I start seeing:

2012-07-07 10:50:10.825030 [PS StandbyWakeup(14)]: PS: StandbyWakeupThread triggered by check interval
2012-07-07 10:50:10.830030 [PS StandbyWakeup(14)]: PS: LoadSettings()
2012-07-07 10:50:10.906035 [PS StandbyWakeup(14)]: PS: SetWakeupTimer()
2012-07-07 10:50:10.908035 [PS StandbyWakeup(14)]: PS: Inspecting PowerController:
2012-07-07 10:50:10.913035 [PS StandbyWakeup(14)]: PS: Inspecting ScheduledRecordings:
2012-07-07 10:50:10.918035 [PS StandbyWakeup(14)]: PS: Inspecting XmlTvImport:
2012-07-07 10:50:10.927036 [PS StandbyWakeup(14)]: PS: Inspecting Client Plugin:
2012-07-07 10:50:10.928036 [PS StandbyWakeup(14)]: PS: No pending events found in the future which should wakeup the system
2012-07-07 10:50:10.929036 [PS StandbyWakeup(14)]: PS: CheckForStandby()
2012-07-07 10:50:10.930036 [PS StandbyWakeup(14)]: PS: Inspecting PowerController:
2012-07-07 10:50:10.931036 [PS StandbyWakeup(14)]: PS: Inspecting RemoteClient:
2012-07-07 10:50:10.933036 [PS StandbyWakeup(14)]: PS: Inspecting ActiveStreams:
2012-07-07 10:50:10.934036 [PS StandbyWakeup(14)]: PS: Inspecting ControllerActive:
2012-07-07 10:50:10.937037 [PS StandbyWakeup(14)]: PS: Inspecting ProcessActive:
2012-07-07 10:50:10.938037 [PS StandbyWakeup(14)]: PS: Inspecting ActiveNetwork:
2012-07-07 10:50:10.939037 [PS StandbyWakeup(14)]: PS: Inspecting ActiveShares:
2012-07-07 10:50:10.949037 [PS StandbyWakeup(14)]: PS: Inspecting Client Plugin:
2012-07-07 10:50:10.950037 [PS StandbyWakeup(14)]: PS: Check whether the next event is almost due
2012-07-07 10:50:10.952037 [PS StandbyWakeup(14)]: PS: SetStandbyMode(StandbyAllowed)
2012-07-07 10:50:10.953037 [PS StandbyWakeup(14)]: PS: System changed from busy state to idle state
2012-07-07 10:50:10.954037 [PS StandbyWakeup(14)]: PS: System is idle and may go to standby
2012-07-07 10:50:10.956038 [PS StandbyWakeup(14)]: PS: Active standby is disabled - standby is handled by Windows

This is in tv.log. To me that indicates a configuration problem, because PS is saying the system is idle. I'm no PS expert though - just reading the logs at face value...

Maybe I'm misinterpreting? If so, I apologise.

mm