Quote:
Originally Posted by madshi
You said that the forums suggested that the GPU drivers have handed over an important part of the render chain to the OS. I can't find that in any of the links you posted?
|
Ok, it mentions in all 3 threads that HDR has never worked in creators update using a driver built for WDDM 2.2, which is pretty much every driver past the one I mentioned (looks like nevcairiel has been involved in this topic if i'm not mistaken, and he may have a more technical answer for you).
If you run the nvidia HDR sdk (
https://developer.nvidia.com/high-dy...ay-development , link to sdk at the bottom of the page) in drivers lower than 378.92, the api triggers HDr mode. After driver 378.92, the api does not work, because of the way nvidia tried to hand over control using wddm 2.2 to the os I believe)
Another thread on this issue
http://www.avsforum.com/forum/26-hom...-thread-3.html
"Windows 10 Redstone 2 (aka the Creators Update) now supports native HDR effects and that it takes control of this Function when a WDDM 2.2 driver is detected."
I'm using the insider program, and I am on the latest 16199 build, and its still the same story.
K
Update:
Re Win 10 Tv and Movie App. Using the latest nvidia driver 382.33 on Win 10 16199 build. NCP set as default colour settings, HDR slider in OS on, it plays 10bit HDR Hevc fine and in HDR mode. Kodi using Madvr, FSE dx11, win 10 api, crashes and reboots.