(2017-05-02, 04:03)Soli Wrote: for Windows it would be logical to follow madvr's lead and autodetect if vcgt is included in the 3DLUT or not, and if included then reset the GPU 1DLUT accordingly when loading the 3DLUT.
I tried the colour management feature of Kodi, because now with Kodi 18 it is implemented in a stable release (Kodi 18 x64, Windows 10).
It seems that vcgt is simply ignored by Kodi. I use a system wide icm file made by displaycal and vcgt is used and applied by displaycal´s profile loader. Madvr does it correctly and uses my 3DLUT, resets vcgt during playback, resets vcgt after closing.
When using a 3DLUT within Kodi I have to manually reset the vcgt (or use displaycal´s profile switcher and create an exception).
But even when going this way, at the moment Kodi´s 3DLUT feature seems to be broken.
My 3DLUT made by displaycal delivers perfect results when checked with displaycal, when checked with HCFR and when checked by measuring the output of MPC HC when using madvr. All measurements are consistent.
When measuring Kodi´s output I get different (wrong) results.
Everything is ok when using no 3DLUT, so when colour management is deactivated in KODI I get right numbers when measuring output for no calibration (no icm file loaded) or when measurimg KODI´s output for using simply vcgt (icm file loaded in Windows).
So at the moment the 3DLUT feature seems to be broken in Kodi 18 for Windows (at least for me) beside the fact that vcgt is not respected.
I hope this could be fixed someday.
At the moment I either live with simple 1DLUT calibration (icm file loaded, vcgt loaded, colour management disabled in KODI) or I have to use DSPlayer with madVR or I use external player MPC HC as working workarounds.
Why implementing broken features in a final version of a software?