PowerScheduler++ test versions (3 Viewers)

[michael_t]

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

Because of a serious bug in the previous alpha versions concerning the execution of external commands, the reinitialisation of the TV controller and the stability of PS++ after a resume it is strongly recommended to update to the new version 1.2.5.9.

Michael

 

[Wbunaarf]

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

Hi,

I've been using ps++ for quite a long time now, but with the change in to 1.2.5 to rely solely on windows on power management I more or less stopped following the development. Since it's now (yeah, I know, I'm late) again possible to let MP handle standby I decided it was time to test a new version (1.2.5.8).

PowerScheduler++ 1.2.5.0:
[...]
- Removed unnecessary advanced options in config ("Extensive logging", "Allowed standby hours", "Check interval", "Pre-Wakeup-Time", "Pre-No-Shutdown-Time", "PowerScheduler++ forces system to go to standby when idle")

In which ways do you think these are 'unnecessary'? I agree that the log level is better of following MP's global level, but at least the pre-times (in case your setup needs some extra time to become ready) seems sensible to me. Also, is it just me or did you remove the 'Only allow standby on home screen' as well? If so, that would be really unfortunate.

I haven't been able to test much on the combined server/client yet, but on a dedicated client I have problems with the system going to sleep even though it's not idle. The attached logs first show MP immediately suspending upon startup, I then resume and just let it sit there. After ~1 minute, rather than the 5 I've set it to, the system again suspends. I then again resume and once again it suspends after ~1 minute. Finally I resume it but this time I keep jumping around in menus to try and prevent suspend, but alas... After the usual ~1 minute it again goes to sleep.

Not related to this particular version, but is it possible to detect when leaving away mode? I, as well as many others, have the problem that the sound is muted when coming back. It would greatly improve the waf if it could be automatically unmuted.

Edit: Retested with 1.2.5.9 and the behaviour didn't change.
Edit 2: The server/client behaves as it should and waits 5 minutes before going to sleep.

//W

 

[michael_t]

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

...I haven't been able to test much on the combined server/client yet, but on a dedicated client I have problems with the system going to sleep even though it's not idle. The attached logs first show MP immediately suspending upon startup, I then resume and just let it sit there. After ~1 minute, rather than the 5 I've set it to, the system again suspends. I then again resume and once again it suspends after ~1 minute. Finally I resume it but this time I keep jumping around in menus to try and prevent suspend, but alas... After the usual ~1 minute it again goes to sleep.

Thank you for reporting this bug. It only appears if you have "PS++ forces standby" enabled and are on a remote client. I have to admit that I did never test such a configuration. I fixed the bug in the attached (preliminary) version 1.2.5.10 and would be glad to get some feedback from you before I publish it.

Not related to this particular version, but is it possible to detect when leaving away mode? I, as well as many others, have the problem that the sound is muted when coming back. It would greatly improve the waf if it could be automatically unmuted.

It can be detected (and is being detected by PS++) and it would be possible to unmute the sound after leaving away mode. I think about it for the next version...

Michael

 

[Wbunaarf]

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

Thank you for reporting this bug. It only appears if you have "PS++ forces standby" enabled and are on a remote client. I have to admit that I did never test such a configuration. I fixed the bug in the attached (preliminary) version 1.2.5.10 and would be glad to get some feedback from you before I publish it.

My pleasure!

I've done some limited testing with the attached version, and I'm happy to say that it seems to work just fine. My timeout of 5 minutes is respected and pressing a key resets the timer as it should.

[Leaving away mode...]

It can be detected (and is being detected by PS++) and it would be possible to unmute the sound after leaving away mode. I think about it for the next version...

Excellent! Thinking about it ps++ should, if possible, probably check the state before going away and not unmute if it was manually set so.


Could you please comment on the removed options (especially 'Only allow standby on home screen')?

//W

 

[michael_t]

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

Could you please comment on the removed options (especially 'Only allow standby on home screen')?
//W

I removed it, because I see no real use in a different behaviour of MP wether I am in the home screen or navigating in some plugin (playing media is someting else of course). Another aspect to consider is that this would be the one and only configuration option on a single-seat setup and the only reason to provide a client config at all (now there is a message box telling that all configuration is made on the server). But if many users of PS++ think it is useful, I could add it again to the client config.

Michael

 

[stradivarius]

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

What about waking up the system (for automatic recording) without display?

It would really be nice to wake the system up already in "away mode"!

This way it would really resemble to a pvr.....

May be this is already there, but I didn't find it.

Cheers

 

[michael_t]

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

PS(++) does not wakeup a system in a special mode, it simply programs a wake timer that wakes up the system at the scheduled time and signals a RESUMEAUTOMATIC event to all running processes. If there is no user action causing the wakeup (or afterwards) the system should stay in a mode with display deactivated (similar to away mode). But with MediaPortal there is always a RESUMESUSPEND event too on wakeup, which indicates a user action (though there was none) and the display gets activated. I have no way to prevent this with PS++ or to distinguish an automatic wakeup from a user triggered one, so I am afraid you have to take it as it is...

Michael

 

[Wbunaarf]

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

Could you please comment on the removed options (especially 'Only allow standby on home screen')?
//W

I removed it, because I see no real use in a different behaviour of MP wether I am in the home screen or navigating in some plugin (playing media is someting else of course).

Well... Personally I used this feature as a simple way to prevent standby when I so desire (for example if I stepped away from the computer for a while perhaps to go downstairs and check something on the server and then return upstairs) or even when remoting to another machine to check something. Other usecases I suppose could be if you have myemulators spawn an emulator or Moving Pictures spawn (eg) PowerDVD to play a Blu-Ray.

Another aspect to consider is that this would be the one and only configuration option on a single-seat setup and the only reason to provide a client config at all (now there is a message box telling that all configuration is made on the server).

I do understand this aspect, but I don't think it's a major problem.

I'm also a bit curious about the other removed features.

Did you hardcode a pre-wakeup time or what time is now being set? Here's a user with a one minute delay before MP is responding and here's another one with a more moderate delay. If one uses an STB rather than a PC tuner it can also take quite a while (in some cases actually several minutes) before it's available.

The Pre-No-Shutdown-Time is also a pretty useful feature. I have my machine set to go to sleep after 5 minutes, but if it's 10 minutes until the next recording (or rather 10-'pre-recording'-'whatever pre-wakeup is set to') I really don't want it to suspend. The wear on the hardware can be quite a bit larger than whatever you might save in electricity.

I have no opinion on 'Check interval' since I don't really know what it does.

'Allowed Standby Hours' can also be a very useful feature. If you have several clients in your house, and several persons using them as well, not allowing suspend between eg 18.00 and 22.00 when these persons perhaps are most likely to use the system may be wanted. There's really not much use suspending just to resume a few minutes later.

But if many users of PS++ think it is useful, I could add it again to the client config.

No idea. I don't know how many are using the devel branch (versus the stable branch which still got these options), but removing features is rarely popular...

//W

 

[michael_t]

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

@all

Are there already experiences with the audio unmute feature of the latest version?

Michael

 

[doveman]

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

@all

Are there already experiences with the audio unmute feature of the latest version?

Michael

Hi Michael

I'm not someone who used the mute feature, so I can't really test to see if it works better now I'm afraid. I just wanted to point out that if you only update the first post, rather than post a new message, the forum doesn't seem to alert me (or anyone else I presume) that the thread has been updated, so I only became aware you'd posted the latest version when I got alerted to your last post.

By the way, I've been having a problem with my remote not working after resume recently. I don't recall this being a problem before so I wonder if you've changed anything in PS++ that might be connected. The remote is part of the TV card which is working fine after resume now (you appear to have fixed PS++ so it properly restarts TVServer with the "Reinitialise" option as this wasn't working before, so thanks!). I tried setting a "Delay when restarting MP after resume" of 10 seconds, but that didn't fix it, so I'm trying 20 seconds now.

Strangely, last time I tested, after MP had restarted and I killed it by opening MP config, then closed config and restarted MP, the remote still didn't work, but then I killed it with ALT+F4 (which is what I normally do) and restarted it and then it worked.

https://forum.team-mediaportal.com/bugreports-74/remote-not-working-after-resume-105085/