Custom Resolution Utility (CRU)

[jaylumx]

(10-23-2020 01:23 AM)ToastyX Wrote:  

(10-23-2020 01:12 AM)jaylumx Wrote:  I then find out the pixel clock border for 8/10 bit colour and modify the custom resolution timings so that the pixel clock is below it which allows me to select 4k 96hz 4:4:4 at 10 bit colour......but it breaks Madvr. In Madvr, a new identification is used but it nullifies all my wide gamut colours and HDR formats as well as displaying only 8 bit colour (as opposed to 8/10/12 bit originally) and while displaying HDR video as SDR.

I tried transferring the CRU timings to the NVCP but again 10 bit colour did not stick when I applied it.

Any thoughts on how to solve this problem Toastyx?

There might be other information in the default DisplayID extension block that might be needed for HDR, but CRU can't read the extension block because NVIDIA's driver won't provide more than one extension block. If you can find some way to dump the full EDID with the DisplayID extension block, then you can import it into CRU. If you have access to an AMD GPU, it should be able to read it. If not, maybe there's some way using Linux.

I have managed to get hold of Monitor asset manager by Entech. Will this allow me to dump the full edid with displayID - btw it is the only edid manager i found that allowed me to save the extension block information - If so, what are the steps i would take with CRU to circumvent Nvidia's limitation of only reading one extension block?