STV Import: Sleep Timer

[CB_2005]

Originally Posted by flachbar

For the global timer, make sure you use
plugins/df/SleepTimer/global_timer=22:30

Do you use the default STV, or SageMC ?

Dirk

Looks like I forgot to stop the Sage Service.. I just only shutting down the sage application itself before. The deletion problem has been fixed.

I think I'm running Sage MC.... that's what the sage splash screen says when it starts anyway.

I'm still not finding the "sleepTimer/link_to_OSD=true" anywhere in my .properties files. I added it manually, but it still didn't take.


I even tried adding it to both properties files (for good measure), but no dice.

[dflachbart]

Originally Posted by CB_2005

Looks like I forgot to stop the Sage Service.. I just only shutting down the sage application itself before. The deletion problem has been fixed.

Mhh, strange ...
If you are using SageTV as a service, the property file used by plugins is SageClient.properties. Exiting the UI application should be sufficient, stopping the service should not be necessary ...

Originally Posted by CB_2005

I'm still not finding the "sleepTimer/link_to_OSD=true" anywhere in my .properties files. I added it manually, but it still didn't take.

It seems the import must have failed then. I can have a look at it if you send me debug logs:

- exit SageTV UI
- add (or edit) debug_logging=TRUE (all caps) to the SageClient.properties file
- add (or edit) plugins/df/debug_level=1 in SageClient.properties
- restart the UI
- load the base STV without the import (either SageTV3.xml if you are using the default, or SageMC_169.xml if using SageMC)
- repeat the import
- post your sagetvclient_0.txt (as an attachment)
- you can reset the debug values to false/0 after you are done

Dirk

[CB_2005]

Odd... I'm not sure what happened either. I just did the import over again and everything seemed to import properly. Something is probably screwy on my end.

So far, everything is looking awesome. Thank you for everything.

[CB_2005]

Just a heads up..

I'm running the Sleep Timer plugin and it locked up Sage the other day.

Sage happened to be on the screen where I was viewing my current recordings (malore style) when the Sleep timer kicked in. When I turned on my TV the next morning, I saw that the plugin was saying that Sage will go to sleep in 9 seconds. Sage was frozen, even the clock in the upper right still said 10:30pm.

The timer was stuck as 9 seconds; the remote wouldn't work. I had to plug a USB keyboard into the system and 'End Task' on sage. The system was fine, Sage was the only thing frozen. I restarted Sage and it's been fine since.

I've been making sure that I don't leave Sage on that screen at night 'just in case'.

Hopefully this was an isloate incident, but I wanted to post a head up anyway.

Over all, I'm loving the plugin.

[dflachbart]

Originally Posted by CB_2005

Just a heads up..

I'm running the Sleep Timer plugin and it locked up Sage the other day.

Sage happened to be on the screen where I was viewing my current recordings (malore style) when the Sleep timer kicked in. When I turned on my TV the next morning, I saw that the plugin was saying that Sage will go to sleep in 9 seconds. Sage was frozen, even the clock in the upper right still said 10:30pm.

The timer was stuck as 9 seconds; the remote wouldn't work. I had to plug a USB keyboard into the system and 'End Task' on sage. The system was fine, Sage was the only thing frozen. I restarted Sage and it's been fine since.

I've been making sure that I don't leave Sage on that screen at night 'just in case'.

Hopefully this was an isloate incident, but I wanted to post a head up anyway.

Over all, I'm loving the plugin.

Hi CB_2005,

I tried several times to reproduce this here, but without any luck. And in general I can't really imagine how the sleep timer could lock up, it should not interfere with other Sage functionality (especially at the time when it is just counting down the clock...). But then, who knows ... I just think it is may be much more likely that this happened by coincidence. Thanks for the info though.

Dirk

[CB_2005]

Wierd.. I got another lock up last night. I'm starting to think my install is just corrupt. I'm probably going to try to reinstalll the plugin the next chance I get.

Anyway.. here's the scenerio in case it's helpful to you.

I was watching Stargate SG1 last night. It was a favorite as well as Stargate Atlantis which comes on right afterward.

So, I started watching SG1 about 30 minutes after it had started. At 10:30, I get an alert that the system will be entering Sleep in xx seconds. Since I'm still watching SG1, I selected 'Extend Sleep by 15 minutes' from the menu. Once I did that, the spinning sage icon started spinning very quickly and the timer on the box stopped at 14 seconds.

We ended up watching the last 10 minutes of SG1 with sleep box still on the screen. I didn't want to restart sage because I was afraid it may affect the Atlantis recording in the background.

After SG1 was done playing, Sage just froze.. It didn't start playing Atlantis athough it was next show on the channel. So, I left the room. The wife was still in the room working on her laptop. About 15 minutes after I had left the room, Sage decided to starting playing Atlantis. The sudden noise coming from the TV scared the wife half to death. She didn't think it was funny, but I was laughing to hard that I nearly p*ssed myself, heh.

Anyway, we just turned off the TV and went to bed after that. When I checked on Sage this morning, the sleep dialog is still on the screen and the closing credits for ScIFi are froozen on the screen... however the spinning sage icon is spinning slower than it was before

Attached is a screenshot incase it's helpful at all....

[jbilich]

The sleep timer is working great. It puts Sage to sleep perfectly. But I have my computer hooked up to a BenQ monitor, so I'd like to put the entire computer to sleep when the Sleep Timer puts sage to sleep. I figured the easiest way would be through the command line prompt so I up the prompt to put the CPU to sleep.

When I go to Start>Run and type:
C:\WINDOWS\system32\rundll32.exe powrprof.dll,SetSuspendState

The computer goes to sleep just like I want. So I tried adding this to the Sage.Properties file just like the instructions said. I added:

plugins/df/SleepTimer/cmd=C\:\\WINDOWS\\system32\\rundll32.exe powerproof.dll,SetSuspendState

I tried it out and Sage went to sleep just like it should, but the computer did not go to sleep. Am I just supposed to add the plugins/df/... line right below the other plugin/df/sleeptimer lines?

Some help here would be much appreciated. Thanks!!

[dflachbart]

Hi jbilich,

Originally Posted by jbilich

The sleep timer is working great. It puts Sage to sleep perfectly. But I have my computer hooked up to a BenQ monitor, so I'd like to put the entire computer to sleep when the Sleep Timer puts sage to sleep. I figured the easiest way would be through the command line prompt so I up the prompt to put the CPU to sleep.

When I go to Start>Run and type:
C:\WINDOWS\system32\rundll32.exe powrprof.dll,SetSuspendState

The computer goes to sleep just like I want. So I tried adding this to the Sage.Properties file just like the instructions said. I added:

plugins/df/SleepTimer/cmd=C\:\\WINDOWS\\system32\\rundll32.exe powerproof.dll,SetSuspendState

For command line arguments you have to use a separate property:

plugins/df/SleepTimer/cmd=C\:\\WINDOWS\\system32\\rundll32.exe
plugins/df/SleepTimer/cmd_args=powerproof.dll,SetSuspendState

I thought I mentioned this in the instructions, but I might have missed it, I'll check the page. Btw, there's also a nice freeware utility for such purposes, nircmd, you might wanna check it out ...

Originally Posted by jbilich

I tried it out and Sage went to sleep just like it should, but the computer did not go to sleep. Am I just supposed to add the plugins/df/... line right below the other plugin/df/sleeptimer lines?

No, the order really doesnt matter


Dirk

[jbilich]

Yeah I think you did mention that. I'm not that well versed in the whole technical side of the command line, so I guess I missed that. I'll give it a try. Thanks for the speedy reply

[jbilich]

Well I just gave it a try and still nothing. I just added the code you posted to the Sage.Properties file and saved it:

plugins/df/SleepTimer/cmd=C\:\\WINDOWS\\system32\\rundll32.exe
plugins/df/SleepTimer/cmd_args=powerproof.dll,SetSuspendState

Am I missing something??

[gplasky]

Make sure you stopped the Sage service and quit the Sage app.

Gerry

[jbilich]

Why would I need to quit sage?? When I enter the text in the command line it puts the computer to sleep regardless of what's running. Why would that make a difference?? Thanks

[dflachbart]

Originally Posted by jbilich

Why would I need to quit sage?? When I enter the text in the command line it puts the computer to sleep regardless of what's running. Why would that make a difference?? Thanks

Gerry meant that the changes you made in the Properties file will only take effect if you quit Sage first, then edit the file, and restart Sage.

Dirk

[geogecko]

jbilich. Don't be afraid to shut down the Sage UI, if using service mode. That is one of the nice things about using service mode. Since SM is taking care of your recordings, if the UI crashes, you can safely kill it, and restart it without affecting the recordings going on. Now, that doesn't mean you won't lose your place in the recording (where you left off), but that's pretty easy to fix...

flachbar. Nice plug-in. I was just browsing the forums, and found it. I probably don't need it, since we normally just shut Sage off before going to bed, but it's a nice function, nonetheless!

[jbilich]

Originally Posted by flachbar

Gerry meant that the changes you made in the Properties file will only take effect if you quit Sage first, then edit the file, and restart Sage.

Dirk

Ahh ok yes I misunderstood what you were saying Gerry. I can't remember if I did shut it down or what. Thanks for the advice. I'll give it a try after work today.

[gplasky]

Sorry I wasn't clear. Sometimes people forget to shut down the service and just edit the properties file. Unfortunately the change doesn't stick. Hope that will take care of it for you.

Gerry

[cavalli]

I like the import and have tested it with my k/b (via OSD and menus) and it works just fine. Now I just want to make it work with my remote.

The comskip import uses 'custom4' and 'custom5' as their incoming keys to trigger 'next' and 'previous' commercial break (if I understand what I have configured on this machine.)

Is it possible to have custom1-custom3 be used as a default to trigger this function? I'd like to be able to configure the 'sleep' button on my universal remote to send the appropriate key to activate the sleep dialog?

Thanks!

[dflachbart]

Originally Posted by cavalli

Is it possible to have custom1-custom3 be used as a default to trigger this function? I'd like to be able to configure the 'sleep' button on my universal remote to send the appropriate key to activate the sleep dialog?

Thanks!

Take a look at the menu shortcut import, this will allow you to map the Sleep Timer menu to any custom1-5 button ...

Dirk

[ke6guj]

I noticed that in the DL area, there is Sleep Timer v0.9 but it isn't listed in this thread. I tried that to see if it would import into SageMC 6.10a. It didn't completely import, just like Sleep Timer v0.8 wouldn't.

It doesn't add into the options menu like it did in earlier SageMC's. I was able to access it via a Custom menu link, so I am ok for now.

[dflachbart]

Originally Posted by ke6guj

I noticed that in the DL area, there is Sleep Timer v0.9 but it isn't listed in this thread. I tried that to see if it would import into SageMC 6.10a. It didn't completely import, just like Sleep Timer v0.8 wouldn't.

It doesn't add into the options menu like it did in earlier SageMC's. I was able to access it via a Custom menu link, so I am ok for now.

Working on it ...


Dirk