Sage client: Is this an HDMI handshake issue?

[Kirby]

So I have been fighting a problem with my new Sage client build, and thought its finally time to ask for help.

See my client specs in my signature.

It is connected to my Onkyo AVR via HDMI, and then to my Panasonic Plasma, also HDMI. I have my Logitech Harmony One set to turn off the TV and AVR only, leaving the HTPC running at all times, on whatever SageTV screen I happen to be on at the time.

Occasionally, when I power up the system (not sure if the Harmony does the TV or AVR first) the SageTV Client app will be missing from the taskbar and from "Running Applications" in the Task Manager. The process is still there though, actually 2 SageTV Client processes, one using just a few K of memory, and the other using 300-500M usually. Only way to recover at this point is to kill the process (larger one) and then restart Sage Client.

Other times upon power up, the TV will display 1/4 of the Sage GUI in the upper left quadrant (if you split the screen into 4 pieces, 2x2 grid) and the other three quadrants will be the dekstop background. I've had mixed results on recovering from this, sometimes power cycling the TV will fix it, other times the power cycles will make SageTV crash.

I'm thinking its a HDMI handshake issue or similar. Anyone else experienced this type of behavior? Ideas on how to fix it?

I do not own a HDMI Detective so if thats the answer, I will have to purchase one.

[BobPhoenix]

I've noticed this myself. I have my server connected directly to the TV with HDMI. What I've had to do is make sure I close out of SageTV before I turn off the TV for more than a few minutes. I also switch from full screen to windowed before I close so that the SageTV window opens up in windowed mode. I just haven't had a chance to research a solution. So if someone else offers up a solution that works for you I would appreciate knowing it as well. If it is a handshake problem maybe a EDID emulator will help.

[panteragstk]

Disable FSE and always on top. That should fix it. I had that issue and I believe that is what solved it. For some reason when sage tries to check for screen resolution it comes back as 1024x768 when no display is currently on. When you turn your display back on windows registers a resolution change which makes directx freak out. I solved that issue by using the power off timer that makes sage sleep after a specific amount of time.

[Kirby]

Thanks, I have made both changes. If that doesnt fix it, you will just have to send me a copy of the Ortus XML to try out!