just a quick question on Use a fullscreen window

I was a bit too fast to say all is ok.

At least the system now suspends correctly, but when resuming EventGhost doesn't seem to forward remote control events to XMBC and the sound went missing. Gah!

The audio problem seems to related to the HDMI control function itself, and EventGhost seems to have a life on it own. The most annoying thing is that have this working on another system based on a similar PC with same sw config but with an older AVR...

(2012-08-10 18:24)Jbravo Wrote:  I was a bit too fast to say all is ok.

At least the system now suspends correctly, but when resuming EventGhost doesn't seem to forward remote control events to XMBC and the sound went missing. Gah!

The audio problem seems to related to the HDMI control function itself, and EventGhost seems to have a life on it own. The most annoying thing is that have this working on another system based on a similar PC with same sw config but with an older AVR...

Can you make eventghost do a logout / login after the machine resumes?

I've never messed with eventghost so I'm not sure what it can do.

Edit: Or even better, you might be able to use DevCon to restart system devices while the machine is running and if eventghost can do command line, tell it to restart the display service or audio service or whatever.

I have usedEventGhost to some extent, but on machines running 24/7. EventGhost usually starts working when clickning ( with mouse) on screen or toggle window/fullscreen. This doesn't relate to full screen window or true full screen.

If it works on an older avr, I'd think that it was something with the way the avr negotiates with hdmi. I know mine does weird things if I tinker with advanced picture settings in the avr and I think it's because it must introduce a small enough signal display to confuse my video card and force it to shuffle things around.

If your avr is the culprit, I'd try changing all the video settings to "a straight wire to the tv" if that makes any sense. There's probably some signal changing feature in the avr that isn't present in the older one.

Just to make absolutely sure it's the avr, you might try connecting this pc to the old htr just to be certain that the problem doesn't exist on the old one.

The difference between the AVRs is that when the old AVR is turned off, windows still sees the HDMI display (visible in Nvidia Control Panel). But when the new AVR is turned off, the HDMI display is lost and a dummy display is added instead. So there is a difference in behaviour.

I think there is a problem when XBMC is moved between the displays in full screen mode. The more normal case is that XBMC is moved from display(2) to display(1) when display(2) is turned off, but in this specfic case display(1) is just replaced by another display(1) .

Perhaps a developer could comment on this?

When enabling HDMI control on the new AVR, the HDMI display is also kept in windows and standby works. However, the stupid AVR directs audio to the tv on resume...switching inputs on the AVR recover this (audio is sent over optical spdif for other reasons).

Did test the tweak in advanced settings without any luck, in my case there is only one display so it make sense.

EventGhost will be removed in favor of the MCERemote plugin.

As far as I know, "hdmi control" is for sending remote signals and stuff through hdmi cables. Does your htr have a setting that lets you specify which input gets it's audio from where? If it's set to auto, it might just detect the spdif signal first and use it.

HDMI control obviously let the TV control the AVR in other ways as well, found a button on the TV remote named "Theatre" that toggles "sound system" on/off. When on audio is output via AVR if off audio is output via TV. When using the Bluray player audio defaults to the AVR, but the Bluray player supports HDMI control, the PC doesn't.

I disabled HDMI control on the TV, and now the audio is always played via AVR!

So now everything works (keeping my fingers crossed).

Still working :-)

I would appreciate a developer's comment on this;

When the AVR is turned off the HDMI display is removed and is replaced with a PC (VGA) display (no monitor is connected ), verified this with remote login via TightVNC. When running in true full screen I assume XBMC is moved(?) to the active dummy display. But when this happens XBMC will NOTenter standby automatically any more. No indications in the log why.

In my case enabling HDMI pass-through solved the issue but far from all AVRs have this possiblity. So the above may be a potential problem for other users as well.

Another work around is to run in full screen window mode, which is not recommended (BTW doesn't XBMC default to full screen window mode?).

(2012-08-11 11:32)Jbravo Wrote:  Another work around is to run in full screen window mode, which is not recommended (BTW doesn't XBMC default to full screen window mode?).

I always run mine in the default, full screen window. Doesn't seem to have any issues.

Glad to hear it's working properly.