(2018-06-20, 21:00)spencerjford Wrote: (2018-06-20, 12:26)mclingo Wrote: FYI -
HDR toggle no longer works with latest two versions of AMD drivers, i've had to go back to 18.2.2, mainly for other reaosns though, later driver may work but 18.5.2 and 18.6.1 no longer trigger the HDR mode on TV's.
I've logged this with AMD and added a bug report on MADVR in case there is a workaround that MADSHI can apply.
Doesnt with with windows 10 1709 or 1803.
Odd, it still engages HDR on my machine with 18.5.2 and disengages (rx480) it. And i'm on 1803. But i have that blown out reds like you reported with SDR material and dx11 presentation path. Does 18.2.2 not give that blown out reds?
ok, this is odd. If I untick DIRECT3D11 in madvr my HDR toggle still works, this essentially fixes my blown reds problem, i couldnt get HDR to trigger at all without DIRECT3d11 enabled before, I am now using 18.3.4 though, still cant get 18.5.2 or 18.6.1 to toggle HDR though.
EDIT - i spoke too soon, it works using MPC-HC without DIRECT3D11 enabled in MADVR but doesnt work in KODI DS, for some reason KODI DS needs DIRECT3D11 enabled to get HDR, anyone any idea why this is?
EDIT 2 - ok, i've calibrated MADVR for BT2020 and I now get a normal picture, reds are fine, it should be DCi-P3 but is still way too red, the fact that setting MADVR to BT2020 fixes the blown reds suggests to me something in the driver is forcing SDR into a high colour gamut when MADVR is deployed or MADVR is reading SDR as HDR and triggering a higher colout gamut or something, no idea but i'm back to a fulling working system now.
So i'm using the following.
Latest MADVR 09214
latest LAV 0.72
AMD driver 18.3.4 (may still have to drop back to 18.2.2 as i'm not sure how stable this is)
using native D3D decoding.
3D and HDR triggers work, both start and stop with no loss of HDMI input.
DIRECt3d11 ticked
windowed mode in KODI DS on
FSE on in MADVR
refresh rate switching done by KODI DS
color space 4:4:4 full RDB 8 bit (switches to relevant 10 bit modes automatically)