I wish I could find the combination of things that made my setup do what X is describing. I am really starting to miss this. Maybe now that the TV room is done, I can spend some time playing around with the setting to see if I can find this. It really works great when it worked.
Hey X, about how long before it kicks in for you. That may help clue us in on where to be looking.

Don't know for sure I'd say somewhere around 10 to 15 minutes.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Hi Xsecrets,

Is it possible that it is your that you mentioned a little while back? That is about the only piece that is different.

I am more curious although it would be a nice feature. Even lcd monitors "burn it", not a real burn but something happens to them.

Mike

Well it's been a while, but as I recall it worked the same way when I was connected svid I'll have to test it on my other box that is still svideo, though we really don't use that one too much so I'll have to make a conscious effort to test it.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Hey X, not to change the subject of this thread, but are you using a VGA to Component Adapter? I have another thread I posted last week about this, and it has gotten no response. Which one do you use, and have you needed a new modeline just for it? I am currently using VGA to a plasma, and would like to use the component video. Does it work well for you? With this is mind, it really may be that you are using the VGA out instead of S-Video, I know that when I was using a computer monitor with a frontend the screen blanking worked, but with S-Video on that same machine it did not. However, there was also an upgrade between there too.

I am using vga -> component converter I am using the audoathority or audiogalaxy whatever that is very popular. I am just using the standard 720p modeline you find everywhere right now, and I have used the standard 1080i modeline before nvidia screwed up the 1080i output. As far as the picture quality it is great. I get quite a bit of overscan on the desktop which I correct with the mythtv size adjustments, but the video is not very overscanned at all. and yes I am using vga out from the myth box.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Not to overload the Myth team with any more than necessary, but this would seem to be a pretty important issue, given the propensity of most displays to experience "burn-in" or something similar.

While the coding of full-fledged screensavers would be more of a luxury than anything else, couldn't a screen-blanking configuration option be done fairly easily? Is that on the radar for (imminent) future changes?

_________________
-= Domino =-
Major Newbie

Xsecrets, just curious, is xscreensaver running on your myth box? Does the "timeout" setting in ~mythtv/.xscreensaver correspond to the timeout you see for the screen to blank? If yes does it still blank if you kill xscreensaver?

The screen has never blanked for me. I see there is a default ~mythtv/.xscreensaver file on my RA16 machine even though the xscreensaver package isn't installed.

I have looked at the "wake up to record" stuff lately, and there are a few gotchas to getting it to work. It relies on the backend shutting down because it detects that it is idle (defined as no frontends connected for some period of time). It has a hack that means when the box boots, it tries to detect if it was coming up automatically by seeing how long to the next recording, and if it thinks it is coming up automatically, it wont start the frontend, and the backend will shut down after the recording because it is "idle". If the frontend shut down after it detected an idle timeout, this would not be necessary.

It would be great if the frontend had a configurable command that would run when idle in the menus for some time. People who wanted screen savers could run a screen saver command. People who want to implement "wakeup to record" could just kill the frontend when idle, and the backend would shut the box down.