Computer sleeps "early" when video paused

[teedublu]

The EventGhost 'reset idle timer' does not reset the OS idle timer -- it's an EG timer. But I did resolve the problem by using 'emulate keystroke' for the primary navigation buttons, stop and pause.

TW

[Pinan]

Great idea teedublu. That should work well.

So far LCDWriter is doing the trick for me.

Two solutions.

[owilsky]

Originally Posted by teedublu

The EventGhost 'reset idle timer' does not reset the OS idle timer -- it's an EG timer. But I did resolve the problem by using 'emulate keystroke' for the primary navigation buttons, stop and pause.

TW

Can you elaborate? What keystroke do you emulate? And when?

When I press pause on my remote EventGhost sends a Ctrl-S to SageTV. This is a keystroke. But 5 minutes later my machine goes to standby, so some dummy keystroke must be repeated maybe every minute while playback is paused.

[Pinan]

Originally Posted by owilsky

Can you elaborate? What keystroke do you emulate?

Originally Posted by teedublu

. . .stop and pause.

Seems he's using the above.

[teedublu]

I used emulated keystrokes for 7 butttons: up, down, left, right, ok, stop, pause.

The EG Sage plugin does not send keystrokes to Sage (it sends basically an application command -- not all commands in Sage have a keystroke defined). At least that's true for the current version of EG. I read that on EG forum I think. So I disabled the Sage command for those 7 buttons (didn't delete the command, so it can be restored later) and then added an emulated keystroke action instead, which is then configured for the desired keystroke.

I'm using a cheap MCE remote (IR receiver driver says eHome). To configure, I press a button on the remote, an event is captured in the EG log, I copy it to the desired Sage plugin command's macro. There you can leave the plugin's Sage command, or disable it and put in the emulate keystroke action instead.

I looked up the keystroke command in the Sage manual.

I have my sleep-suspend timer set rather long -- plenty long enough for the "pause break"....

TW

[Pinan]

This forum needs a Thumbs Up button.

Neat post teedublu.

[Pinan]

babgvant: Although LCD Writer seems to be working to stop the early Standby, these 3 errors are showing up in Event Viewer:

1. System.Runtime.InteropServices.COMException (0x80010002): Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementEventWatcher.Initialize()
at System.Management.ManagementEventWatcher.Start()
at LcdWriter.Shared.VacuumFluorescentDisplay..ctor() - 0665fe84-01e4-4c65-9e6b-c3958fef01d2

~~~~~~~~

2. Service cannot be started. System.TypeInitializationException: The type initializer for 'LcdWriter.Shared.VacuumFluorescentDisplay' threw an exception. ---> System.Runtime.InteropServices.COMException (0x80010002): Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
at LcdWriter.Shared.VacuumFluorescentDisplay..ctor()
at LcdWriter.Shared.VacuumFluorescentDisplay..cctor()
--- End of inner exception stack trace ---
at LcdWriter.Shared.VacuumFluorescentDisplay.GetInstance()
at LcdWriter.Service.LcdService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

~~~~~~~~

3. Faulting application lcdwriterservice.exe, version 1.0.0.1, stamp 4c50abe7, faulting module kernel32.dll, version 5.1.2600.5781, stamp 49c4f482, debug? 0, fault address 0x00012afb.

Any ideas?

[babgvant]

Originally Posted by Pinan

babgvant: Although LCD Writer seems to be working to stop the early Standby, these 3 errors are showing up in Event Viewer:

1. System.Runtime.InteropServices.COMException (0x80010002): Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementEventWatcher.Initialize()
at System.Management.ManagementEventWatcher.Start()
at LcdWriter.Shared.VacuumFluorescentDisplay..ctor() - 0665fe84-01e4-4c65-9e6b-c3958fef01d2

~~~~~~~~

2. Service cannot be started. System.TypeInitializationException: The type initializer for 'LcdWriter.Shared.VacuumFluorescentDisplay' threw an exception. ---> System.Runtime.InteropServices.COMException (0x80010002): Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
at LcdWriter.Shared.VacuumFluorescentDisplay..ctor()
at LcdWriter.Shared.VacuumFluorescentDisplay..cctor()
--- End of inner exception stack trace ---
at LcdWriter.Shared.VacuumFluorescentDisplay.GetInstance()
at LcdWriter.Service.LcdService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

~~~~~~~~

3. Faulting application lcdwriterservice.exe, version 1.0.0.1, stamp 4c50abe7, faulting module kernel32.dll, version 5.1.2600.5781, stamp 49c4f482, debug? 0, fault address 0x00012afb.

Any ideas?

The first one is a problem with WMI on your PC, not 100% sure about #2 but it could be the same thing.

Besides the messages are there any issues?

[TwistedMelon]

Originally Posted by timg11

I have the computer's power management settings to go into sleep after 30 minutes.

While I had a show paused, and SageTV running full-screen, the computer went into sleep after about 5 minutes.

Does you computer ever go to sleep sooner than the 30 minutes you have set up when running any other application other than SageTV? *Something* is putting your machine to sleep.

So somewhere there's either some setting at 5 minutes or a bug. The bug could be in the OS (or some other software you have running that can put the OS to sleep) or in Sage.

I don't think working around this by generating input events is the right thing to do, since if it's a bug in Sage, it's not going to get fixed if it doesn't get reported and found.

You might want to check the power settings in your BIOS and make sure they're set to allow all control at the OS level. Then double-check your OS settings. Even if Sage didn't have the ability to keep the machine awake, your system should only be going down after 30 minutes without input, not 5. There's something amiss.

[Pinan]

Originally Posted by babgvant

The first one is a problem with WMI on your PC, not 100% sure about #2 but it could be the same thing.

Besides the messages are there any issues?

Nothing going wrong, that I can tell. Just kept getting the pop-ups saying "a while ago you had this problem...etc". I selected "Leave me alone next time".

I'll keep checking Event Viewer over time. None of these occurred before using LCD Writer though. No biggie. Just wondered if you would know.

Thanks for the reply.

[babgvant]

Originally Posted by Pinan

Nothing going wrong, that I can tell. Just kept getting the pop-ups saying "a while ago you had this problem...etc". I selected "Leave me alone next time".

I'll keep checking Event Viewer over time. None of these occurred before using LCD Writer though. No biggie. Just wondered if you would know.

Thanks for the reply.

It's definitely LcdWriter. If it stops working we can try to figure out why.

[Fuzzy]

Originally Posted by TwistedMelon

Does you computer ever go to sleep sooner than the 30 minutes you have set up when running any other application other than SageTV? *Something* is putting your machine to sleep.

So somewhere there's either some setting at 5 minutes or a bug. The bug could be in the OS (or some other software you have running that can put the OS to sleep) or in Sage.

I don't think working around this by generating input events is the right thing to do, since if it's a bug in Sage, it's not going to get fixed if it doesn't get reported and found.

You might want to check the power settings in your BIOS and make sure they're set to allow all control at the OS level. Then double-check your OS settings. Even if Sage didn't have the ability to keep the machine awake, your system should only be going down after 30 minutes without input, not 5. There's something amiss.

The problem he's seeing is that sage is preventing windows from going to sleep when playing or recording, but NOT resetting the idle timer. So, as soon as Sage released the sleep-hold, windows puts it to sleep right away. The reason it doens't do this for everyone, is is depends on your remote control setup. If it is using send-messages, or interacting with sage directly, it will not reset the windows idle timeout. If it, instead, is an HID remote (media center style), than it WILL be resetting the idle timer.

[robk]

I use the Hauppauge remote with a USB-UIRT (receive only - tuning is FW) and I also have the problem of a paused movie allows the computer to sleep in a few minutes. Any other fixes or work-arounds (LCDWriter didn't work for me, maybe because I use a Parallel port display with LCDSmartie)? I checked all power off timers in cmos setup and Win7, they are all OK, at least 30 minutes.
Thanks!

Rob

PS- I was thinking crazy thoughts like using a 555 timer to "hit" the pause key on another hidden Hap remote every minute for the duration of the pause. The hidden remote could be triggered "on" when it receives a pause from the real remote (using a simple ir receiver), and quit when it receives a "play" from the real remote. That would probably keep Win7 from sleeping. It wouldn't be difficult to put together, but it's ridiculous.

[Fuzzy]

perhaps ot would be best if sage could continue keeping the pc awake during paused playback.

[robk]

That's what I was hoping for. How difficult would it be to have SageTV control the idle timer during pause?
Rob

[Fuzzy]

Sage would have to just NOT release the hold it puts on windows. It's not something a community dev could change though, as it's in the sagetv for windows core.

[robk]

My nutso idea is looking better... Actually, all I'd have to do is modify a remote to keep repeating "pause" once a minute after it is pressed until "Play" is pressed. In a half hour, I'd only gain a few seconds with each frame advance. It's pretty simple but should work!
PS I've got several Hap remotes, I think I'll try it.

[Fuzzy]

yeah, probably a lot easier to use something like girder to keep it awake then hacking up some hardware.

[robk]

I'm a lot better with hardware than I am with software, been building stuff since I was 10, almost 50 years, just a hobby. Anyway, it gets me out of the office and into the garage "lab" where I feel at home...

[TwistedMelon]

This sounds like a bug in Sage that needs to be reported. Why hack around a problem that's apparently so very easy to fix in SageTV?

Report the problem through the appropriate form if it hasn't already been. Otherwise, the discussion of input event hacks isn't really something that belongs in the beta forum.