Reply to thread

Message: <blockquote data-quote="Marcus Venturi" data-source="post: 932024" data-attributes="member: 121570">I was also affected by the in depth discussed issue. I tried various solutions, but none worked for me. I have a self-made HTPC that has an internal display with 1024x768 Resolution attached to the second port of my NVIDIA graphics adapter which displays the output of the MPDisplay++ plugin. And this makes the problem even worse, because when the TV is not available Windows directs both outputs to the internal screen. All attempts to modify the resolution of the dummy driver will not succeed, because it is not used in this case, as there is a "fallback" display - the internal one. In my opinion this is not a problem of MediaPortal, but a problem of Windows 7, as a lot of other people - especially with multi monitor set up - are affected by this problem caused by the hotplug services of Windows 7. For most devices, - especially for USB-devices - hot plugging makes sense, but in case of a TV this does not make any sense, because a HTPC is always connected to the same TV. There should be an option in Windows to turn the hotplug stuff for monitors off, but there isn't. Some have written that there will be a fix in the code of MediaPortal. But a assume, that this fix will do something like this: If the HTPC is turned on before the TV, Windows will tell MediaPortal, that the resolution has changed to 1024x768. MediaPortal will trash all the Direct3D-stuff and recalulate everything for the new resolution. A few seconds (or miliseconds) later Window recognizes the TV an tells MediaPortal, that the resolution has changed to 1920x1080 and MediaPortal will trash all the Direct3D-stuff again and recalculate everything again for the "old" new resolution. Don't get me wrong - this is stupid - but it's not the fault of MediaPortal it's a fault of Windows 7. How can one avoid this? The answer is simple: Just by taking Windows 7 the chance to detect that the TV is plug or unpluged! The hotplug detection for DVI and HDMI works - as already mentioned in this forum - over a "hot plug detect" wire in the cable. If this wire wasn't there, windows would not be able to detect wether the TV/monitor is pluged/unpluged. Today I went to a shop and got a DVI to HDMI cable. I attached it to DVI port of my NVidia card and the HDMI port of my TV just to check if it works. It worked, but the resolution problem after standby was still there. Then I removed pin 16 (with pliers) of the DVI cable which is the "hot plug detection" pin. See details about the DVI-pins here: <a href="http://en.wikipedia.org/wiki/Digital_Visual_Interface" target="_blank">http://en.wikipedia.org/wiki/Digital_Visual_Interface</a> Afterwards I attached it to my HTPC and - guess what - the resolution problem was gone. I started my HPTC about 10 times from standby with the TV off and there were no resolution problems again.</blockquote>

Verification