Custom Resolution Utility (CRU)

[ToastyX]

(07-08-2022 09:21 AM)IIISi Z16 HF LE Wrote:  I find your software complicated.. nvidia c panel has it best and stupid intel has blocked all custmizations including colour formats and dynamic ranges
Where I should add it ? DisplayID extension block to add resolutions greater than 655.35 MHz pixel clock as explained in the first post which section ?

CRU is an EDID editor, and EDIDs are complicated because they are a mishmash of several different standards created over the years. When CRU was first conceived, HDMI 2.x didn't exist, DisplayID wasn't in use, and the first 4K displays could only do 30 Hz. The EDID standard can't define detailed resolutions greater than 655.35 MHz pixel clock, so 4K @ 100/120 Hz has to be defined either using TV resolutions or using a DisplayID extension block.

All you have to do is add an extension block and set the type to DisplayID. Either 1.3 and 2.0 should work. Then you can add detailed resolutions by adding a data block in the extension block. If the resolutions you add don't appear in Windows after restarting, then either there's a driver limitation or a hardware limitation. Usually the limit is a pixel clock limit. If you can add a resolution up to 600 MHz pixel clock but not anything above, then I would consider that a driver bug because it's incorrectly applying the HDMI 2.0 limit to a DisplayPort/USB-C adapter. Try adding 3840x2160 @ 55 Hz and see if that appears. If nothing you add appears no matter what, then the EDID override is being ignored by the driver for some reason, which I would also consider a driver bug. I'm only familiar with AMD and NVIDIA, so I'm not sure what limitations Intel has. Intel didn't even support EDID overrides until a few years ago, and there have been cases where EDID overrides are ignored, usually with laptop screens, but it's supposed to work with extenal displays.

I want to make CRU 2.0 simpler by consolidating all the resolutions into one list and managing extension blocks automatically, but that will require a complete rewrite and redesign. That's about all I can do to make things simpler without hiding things.

And yes, DisplayPort 1.4 has less bandwidth than HDMI 2.1. DisplayPort 1.4 can handle up to 1080 MHz pixel clock without compression, while HDMI 2.1 can handle at least 1782 MHz at 48 Gbps. 7680x4320 @ 60 Hz is only possible with DisplayPort 1.4 when using compression.