Reply to thread

Message

There is a different solution to this, one that I use on my HTPC.

The important factor to realise is that Windows will not sleep or hibernate the system whilst a recording is in progress. If the sleep or hibernation timeout is set to a very small value (e.g. one minute), the system will sleep or hibernate one minute after the unattended recording has finished. I think that this is the outcome that you want.

The problem with using a very short sleep or hibernation timeout is that if you leave MP on a menu or with video paused in order (say) to make a cup of coffee, Windows will sleep or hibernate the system one minute after you have left the room. This is probably not the outcome that you want.

So the solution is to vary the sleep or hibernation timeout according to the state of the system. When you start using the system, your script should set the timeout to a large value (e.g. one hour). When you have finished using the system, the script should set the timeout to a small value and allow Windows to sleep or hibernate the system.

I wrote a tool in the C programming language to control this, but I prototyped it using a BAT file, so I think that you could do similar from an AutoHotKey script. I originally used the presence or absence of a display screen to decide how to set the timeout, and this is what the prototype BAT version checks. The refined C version checks a USB hub powered via an IR remote-controlled mains socket switched on and off by my Harmony 650 remote control.

I still have the prototype BAT version and can post it if you are interested in exploring this solution further.

-- from CyberSimian in the UK

<blockquote data-quote="CyberSimian" data-source="post: 1242664" data-attributes="member: 141969">There is a different solution to this, one that I use on my HTPC.The important factor to realise is that Windows will not sleep or hibernate the system whilst a recording is in progress.&nbsp; If the sleep or hibernation timeout is set to a very small value (e.g. one minute), the system will sleep or hibernate one minute after the unattended recording has finished.&nbsp; I think that this is the outcome that you want.The problem with using a very short sleep or hibernation timeout is that if you leave MP on a menu or with video paused in order (say) to make a cup of coffee, Windows will sleep or hibernate the system one minute after you have left the room.&nbsp; This is probably not the outcome that you want.So the solution is to vary the sleep or hibernation timeout according to the state of the system.&nbsp; When you start using the system, your script should set the timeout to a large value (e.g. one hour).&nbsp; When you have finished using the system, the script should set the timeout to a small value and allow Windows to sleep or hibernate the system.I wrote a tool in the C programming language to control this, but I prototyped it using a BAT file, so I think that you could do similar from an AutoHotKey script.&nbsp; I originally used the presence or absence of a display screen to decide how to set the timeout, and this is what the prototype BAT version checks.&nbsp; The refined C version checks a USB hub powered via an IR remote-controlled mains socket switched on and off by my Harmony 650 remote control.I still have the prototype BAT version and can post it if you are interested in exploring this solution further.-- from CyberSimian in the UK</blockquote>

[QUOTE="CyberSimian, post: 1242664, member: 141969"] There is a different solution to this, one that I use on my HTPC. The important factor to realise is that Windows will not sleep or hibernate the system whilst a recording is in progress. If the sleep or hibernation timeout is set to a very small value (e.g. one minute), the system will sleep or hibernate one minute after the unattended recording has finished. I think that this is the outcome that you want. The problem with using a very short sleep or hibernation timeout is that if you leave MP on a menu or with video paused in order (say) to make a cup of coffee, Windows will sleep or hibernate the system one minute after you have left the room. This is probably [b]not[/b] the outcome that you want. So the solution is to vary the sleep or hibernation timeout according to the state of the system. When you start using the system, your script should set the timeout to a large value (e.g. one hour). When you have finished using the system, the script should set the timeout to a small value and allow Windows to sleep or hibernate the system. I wrote a tool in the C programming language to control this, but I prototyped it using a BAT file, so I think that you could do similar from an AutoHotKey script. I originally used the presence or absence of a display screen to decide how to set the timeout, and this is what the prototype BAT version checks. The refined C version checks a USB hub powered via an IR remote-controlled mains socket switched on and off by my Harmony 650 remote control. I still have the prototype BAT version and can post it if you are interested in exploring this solution further. -- from CyberSimian in the UK [/QUOTE]