Posts: 175
Joined: Sep 2013
Reputation:
2
2015-09-01, 10:01
(This post was last modified: 2015-09-01, 10:02 by MadScientist.)
I assume you are using the latest Win 10-compatible Intel drivers?
Can't you force the Samsung to use limited range? That would seem an essential part of the fix.
I haven't moved to Win 10 yet but I did have a similar issue when I updated the Intel driver on my Win 8.1 HTPC. I toggled the driver settings a few times to ensure that both application and display settings were on full range and that fixed the issue.
Posts: 103
Joined: Feb 2014
Reputation:
1
Uoppi
Senior Member
Posts: 103
2015-09-01, 13:05
(This post was last modified: 2015-09-01, 13:08 by Uoppi.)
Yes it's the latest Intel driver.
The strange part is that just yesterday I did manage to get it working after I created a 60 Hz custom resolution (to replace the 59 Hz Windows defaults to). But today it's suddenly not limited anymore when the TV's at 24 Hz. The HDMI black level is at the Low setting (meaning limited for Samsung, I believe).
I guess I could try forcing driver to full range via registry.
Posts: 103
Joined: Feb 2014
Reputation:
1
Uoppi
Senior Member
Posts: 103
I just got proper black levels for a short while by using the EnableRGBFullRange registry hack but as soon as I updated Kodi to Jarvis Alpha 1, the black levels are messed up again (Kodi menus very dark, black range starting from 0).
I have no idea why it's sometimes working and sometimes not. If it's a driver issue I would expect other Win 10 + HD 3500 graphics users reporting similar problems.
Posts: 175
Joined: Sep 2013
Reputation:
2
2015-09-01, 16:28
(This post was last modified: 2015-09-01, 16:34 by MadScientist.)
Is Jarvis now on DX11? I found the DX11 builds messed up my black levels - brightness too high compared to menus. It's a problem with DXVA2 which I had to disable
Posts: 10,607
Joined: Oct 2011
Reputation:
645
jjd-uk
Team-Kodi Member
Posts: 10,607
2015-09-01, 17:23
(This post was last modified: 2015-09-01, 17:23 by jjd-uk.)
Yes the DX11 work was merged at the beginning of July so is in any v16 builds since then.
Posts: 175
Joined: Sep 2013
Reputation:
2
In that case the OP latest problem might be DX11 related. Try disabling DXVA2
Posts: 103
Joined: Feb 2014
Reputation:
1
Uoppi
Senior Member
Posts: 103
2015-09-01, 23:19
(This post was last modified: 2015-09-01, 23:22 by Uoppi.)
This is starting to go way over my head: it seems as if the "limited range" function of Kodi is working in reverse when DXVA2 is enabled with DX11.
With 1) driver set to full range, 2) TV to limited and 3) limited range UNticked in Kodi, I seem to get normal limited range blacks on my regular TV brightness setting.
Whereas with limited range TICKED in Kodi, I have to lower brightness by 10+! Precisely the opposite of what I would expect.