Posts: 315
Joined: Dec 2012
Reputation:
1
2016-02-24, 12:55
(This post was last modified: 2016-02-24, 12:55 by deletedpenguin.)
I came here to report the same issue. For me, it's when I deactivate the screensaver. Out of curiosity, what your hardware config? I'm running Kodi at 1080p on a Intel NUC that's attached to a Samsung 4k TV.
Windowing Kodi (backslash) then going fullscreen again generally fixes it.
Posts: 47
Joined: May 2010
Reputation:
0
I'm running kodi 16 on a B75 chipset with an i3 2220T with integrated graphics. My tv is a Panasonic x10 running 1080p and my AV is a yamaha RX-A830. My parents have a similar setup i5 3th gen with intel graphics 2500 hooked up to a 4k TV. They are experiencing the same problem. Remote control in both cases is a harmony one.
As you write changing resolution back and forth or windowing and then back resolves it however this is very irritating.
Posts: 59
Joined: Apr 2012
Reputation:
6
2016-02-24, 14:44
(This post was last modified: 2016-02-24, 14:52 by Scythe42.)
This is pretty much normal on Windows when using a Display Port or HDMI connection. When a connection is "lost" (e.g. machine sleeping, or a display removed, AVR turned off etc) the resolution of the screen is reset to usually 640x480 (depending on setup and GPU they might not follow that standard). As a consequence windows on a display are automatically resized by the operating system. And this is in full compliance with the related standards of the given connection protocol.
Kodi is missing a check here if the resolution changed and adjust the window size accordingly automatically to the new resolution after certain events broadcasted by the OS. Kodi can track this and adjust the Window size accordingly back to the new resolution given the D3D backbuffer is large enough. In this case of course it large enough as Windows just forced the app to resize to a smaller size when no display was available anymore to display stuff at the position and resolution until the full connection between GPU and display is fully "powered up" again.
To properly deal with this Kodi has to listen to message that displays/GPUs have been disconnected/reconnected and resize the application accordingly
Nearly all MediaPlayer/MediaCenter Apps suffer from this problem and you see it also in most normal apps as well. I provided a patch some years ago for MediaPortal to deal with this issue. No, not able to provide one for Kodi as I am not very familiar with the codebase here.
There are some registry keys were you can override the default resolution that Windows will fallback to, but this will not work on all setups as not all GPU drivers honor these settings and favor what the OS tells them and not overriding it (which IMHO is correct). Also some AVRs even announce their own stuff here. And some, including some HDMI switches, override that stuff completely as they are always power up and keep a connection alive. But yeah, its not any hardware problem but an application problem to deal with that scenario.
Overall not a hard problem to solve but very nasty to get it right for all usual setups as well as dealing with various "special cases" related to AVRs.
Posts: 59
Joined: Apr 2012
Reputation:
6
The Pin19 trick, or using some HDMI Splitter/Switch that do similar things, works for some users as a workaround who are seeing these issues. But it is not guaranteed to solve the problem in all cases.
But yeah, its a valid hardware workaround to prevent involved hardware in the Display Port/HDMI connection seeing device removal information in various setups.Usually it is enough to use that "hack" on the cable from the HTPC, but sometimes beside HTPC -> AVR, AVR -> Display needs it as well.
The firmware in some older AVR or TVs had tons of problems with device removal and addition and this is where the "hack" originates and was common outside the HTPC world as well.
Give it a shot if it works for you for now until Team Kodi find some time to deal with that issue. Just tape off the pin in your HDMI chain one step at a time and see what happens.
Posts: 47
Joined: May 2010
Reputation:
0
I'll try that and report back. Are team kodi aware of the issue or should you report it somewhere?
Posts: 315
Joined: Dec 2012
Reputation:
1
Yeah, a double "\" has been my solution to this. Not ideal, but it works. Thanks all for the insight into what causes this.
Posts: 1,390
Joined: Jun 2011
Reputation:
38
k4sh1n
Posting Freak
Posts: 1,390
Try and perform an EDID overide with moninfo.
Posts: 34
Joined: May 2012
Reputation:
0
jht3
Junior Member
Posts: 34
been experiencing this with Jarvis since i installed it
but i have been having video and audio issues since many versions ago. usually a reboot is my fix. i ultimately believe this is due to my non-standard setup:
panasonic viera<-->hdmi cat5e converter<-->hdmi switch<-->amd apu
after putting it off for months, i finally installed the custom .inf generated by MonInfo. i hope it stabilizes my setup.
