sleep mode behavior

[Opus4]

Originally posted by Hector
When put to sleep Sage only iconifies to the system tray. TV out and the 350 OSD all work fine. From the TV side nothing has changed. On the computer side Sage is iconifed to the tray.

So I again I ask. Has the behavior for sleep changed or is this a known bug in the release version?

I still have no idea if it was intentional or not, but I can see it too now with my Xcard. I was able to make modifications so that the Hauppauge remote can now control SageTV even when it does not have focus [see How to control SageTV w/o focus (Hauppauge or other remotes)], & got it to send output to the TV while it was sleeping in the sys tray.

I think it is something that simply isn't checked while sleeping & it only works because the 350 & Xcard have their own direct TV out, with no need for a video playback window. Intentional or not, I doubt it is a high priority.

- Andy

[Karen0302]

Andy,

I tried you SendMessage program / -Event combo for controlling SageTV without needing focus. Seems to work great! Worst case so far is about a .5 second delay from pressing the remote button until SageTV acts on the command.

One interesting thing is happening however. When using Girder, it didn't seem to matter what the Sleep mode actually was. now however, it seems that using your SendMessage makes Sleep work like Sleep. In other words, now it appears that if SageTV is in Sleep Mode, you must bring it out of Sleep mode before it will recognize any other commands.

Karen

[Crowdx42]

When I set Sage to sleep using the PVR 350 out it also still works until I actually take it out of sleep and then the video stops, only when I select a new show does it start to play again.
Patrick

[Opus4]

Originally posted by Karen0302
I tried you SendMessage program / -Event combo for controlling SageTV without needing focus. Seems to work great! Worst case so far is about a .5 second delay from pressing the remote button until SageTV acts on the command.

Yes, like the readme notes, there can be a small delay before you see the response, though it shouldn't be too long after you press a button one time... at least, not until you leave the remote idle for a long time & the SendMessage program gets swapped out of memory. Using SageTV's own -event parameter is much slower, due to the size of that exe.

One interesting thing is happening however. When using Girder, it didn't seem to matter what the Sleep mode actually was. now however, it seems that using your SendMessage makes Sleep work like Sleep. In other words, now it appears that if SageTV is in Sleep Mode, you must bring it out of Sleep mode before it will recognize any other commands.

Oh yeah. The reason this is happening to you is that when you sleep SageTV via the Hauppauge remote, I have irremote.ini leave SageTV mode. Therefore, it won't send commands to SageTV again until you use the remote to wake it. However, if you put it to sleep via the main menu button, then the remote will stay in SageTV mode & you can still send commands to it.

Edit: Thanks for the comment, btw. I updated my other thread to say how I was able to try this.

- Andy

[Karen0302]

Andy,

Having the remote leave SageTV mode was a mean and nasty trick!!! For shame, for shame, for shame!!!

Karen

[Opus4]

Originally posted by Karen0302
Having the remote leave SageTV mode was a mean and nasty trick!!! For shame, for shame, for shame!!!

- Andy.

PS: [Edit: that means: LMAO, btw...]

[Karen0302]

Andy,

Seriously though, now that I have removed youe somewhat late 'April Fools Joke' everything is working just good job and created a very useful utility program. And ... you also saved me $20!!!!! Not a bad bonus feature!!!!

Karen

[Opus4]

Originally posted by Karen0302
Seriously though, now that I have removed youe somewhat late 'April Fools Joke'

Actually, there is a 'serious' purpose to doing the mode switch -- it puts the remote back to the default mode & allows me to use it to control other applications more easily & it allows others to wake SageTV regardless of what other application has focus after that. But, if all you are using it for is SageTV, then just set it to use "mode(SageTV)" & leave it there all the time.

Anyway... glad you found it useful.

- Andy

[Hector]

Originally posted by Opus4
I still have no idea if it was intentional or not, but I can see it too now with my Xcard. I was able to make modifications so that the Hauppauge remote can now control SageTV even when it does not have focus [see How to control SageTV w/o focus (Hauppauge or other remotes)], & got it to send output to the TV while it was sleeping in the sys tray.

I think it is something that simply isn't checked while sleeping & it only works because the 350 & Xcard have their own direct TV out, with no need for a video playback window. Intentional or not, I doubt it is a high priority.

- Andy

It basically killed a bug workaround.

It's a different behavior than pre-RC 2.0 versions so its not simply a by product of the 350 OSD. But from what I gather from the new docs the sleep mode behavior may have changed.

If that's the case, the problem with that is that it now makes it more problematic to work around the VERY annoying bug that doesn't handle the pvr-350 decoder properly.

Formerly putting Sage in sleep mode would release the pvr-350 decoder which allow you to use the decoder on the card with other player software; in short a bug workaround that was managable because you could leave Sage running.

Now because of this bug/behavior change (sleep) to workaround the video decoder bug you have to quit Sage to release the decoder (which is necessary to circumvent the bug) and this effectively kills scheduling and the ENcoder. Plus you have to remember to restart the software.

Ideally the decoder bug would have been fixed prior to release since it is a loss of feature functionality.

peace . . .