Custom Resolution Utility (CRU)

[ToastyX]

(11-01-2020 09:27 PM)botounacruzeta Wrote:  The original EDID seems to be located at

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\ACI27EC\1&8713bca&0&UID0\Device Parameters]

in the EDID key.

That's the first block of the last active EDID, not necessarily the original. It will be the original after running reset-all.exe and restarting, but it won't be after creating an override and restarting.

(11-01-2020 09:27 PM)botounacruzeta Wrote:  The reason I've thought about comparing them is the start bytes were the same.

But then, after some point, the bytes were different.

The only differences are:

1. CRU always sets the image size in mm in the detailed resolutions to 1/4th the resolution for consistency because the size is not used for anything and I didn't want to add fields to the detailed resolutions dialog that have no effect. This shouldn't be a problem because it does the same thing to the detailed resolutions in the extension block, and the control panel opens fine with the edited extension block.

2. CRU doesn't include the serial number or range limits by default because they use up detailed resolution slots, and they have no effect except for the range limits with FreeSync monitors, in which case CRU includes the range limits by default. The PG279Q is a G-SYNC monitor, but G-SYNC doesn't require the range limits to function. If you enable the serial number and range limits, CRU always includes the range limits first, name second, and serial number third so the most important one is first, and the less important ones can be "pushed off" the list when adding detailed resolutions. The original EDID has the serial number first, range limits second, and name third, but the order shouldn't matter, and the bytes are the same for each.

3. CRU does not set the number of native resolutions in the extension block, while the original EDID has it set to 1. This is the small change that I had you test, so this isn't the problem.

Other than that, the checksums at the end of each block are different because of the changes, but they are correct. As far as I can tell, this is a driver bug because there is nothing wrong with the EDID override that CRU creates, and possibly any change to the first block would trigger the problem. CRU also makes these changes after importing a file, which is why the override is different from the original.

[botounacruzeta]

(11-01-2020 11:28 PM)ToastyX Wrote:  CRU always includes the range limits first, name second, and serial number third so the most important one is first, and the less important ones can be "pushed off" the list when adding detailed resolutions. The original EDID has the serial number first, range limits second, and name third, but the order shouldn't matter, and the bytes are the same for each.

While testing, I thought about the order, but CRU doesn't allow to order "serial", "range limits", and "name".

Anyway, now with the problem fixed (after I have applied the "fix"), CRU shows range limits first, name second, and serial number, although I don't know if it shows the real order, or it will always show in the order it will include (if I save).

(11-01-2020 11:28 PM)ToastyX Wrote:  3. CRU does not set the number of native resolutions in the extension block, while the original EDID has it set to 1. This is the small change that I had you test, so this isn't the problem.

Is it the first byte in the hex string of

[Monitor.AddReg]
HKR,EDID_OVERRIDE,"0"

in the inf file?

If yes, I tried to change it in the inf file, and CRU displayed an error message when importing the file (probably because of the checksum, that wasn't changed)

(11-01-2020 11:28 PM)ToastyX Wrote:  Other than that, the checksums at the end of each block are different because of the changes, but they are correct. As far as I can tell, this is a driver bug because there is nothing wrong with the EDID override that CRU creates, and possibly any change to the first block would trigger the problem. CRU also makes these changes after importing a file, which is why the override is different from the original.

I really don't know why this issue is rare. It can be a combination of driver and specific hardware or settings.

Because I suppose if it was the driver alone, a lot of CRU users will be complaining about it.

Maybe it's related to this specific monitor...I don't know.

[ToastyX]

(11-02-2020 01:08 AM)botounacruzeta Wrote:  Anyway, now with the problem fixed (after I have applied the "fix"), CRU shows range limits first, name second, and serial number, although I don't know if it shows the real order, or it will always show in the order it will include (if I save).

It always shows the order that it will save as. It's a bit awkward because CRU didn't originally have a way to edit these, or else I would have probably designed it to be like the data blocks in the extension block.

(11-02-2020 01:08 AM)botounacruzeta Wrote:  Is it the first byte in the hex string of

[Monitor.AddReg]
HKR,EDID_OVERRIDE,"0"

The "0" is the block number, and the 0x01 is the data type (REG_BINARY). Everything after that is the data. CRU doesn't care about the checksum because it will calculate it when saving anyway.

[Fourgoblin]

I have a displayport 1.4 to hdmi 2.1 adapter that I use to get 4k120hz on my tv. Nvidia control panel does not allow 4k120hz as a native resolution so I tried to use CRU to force it as it works as a custom resolution. When I try to set the refresh rate to 120hz at 4k on CRU the refresh rate turns red and does not allow me to set it. How do I fix this?

[ToastyX]

(11-04-2020 06:35 PM)Fourgoblin Wrote:  I have a displayport 1.4 to hdmi 2.1 adapter that I use to get 4k120hz on my tv. Nvidia control panel does not allow 4k120hz as a native resolution so I tried to use CRU to force it as it works as a custom resolution. When I try to set the refresh rate to 120hz at 4k on CRU the refresh rate turns red and does not allow me to set it. How do I fix this?

EDID detailed resolutions are limited to 655.35 MHz pixel clock. The only way to add 3840x2160 @ 120 Hz is either in a TV resolutions data block in a CEA-861 extension block, or as a detailed resolution in a DisplayID data block.

[artur7]

Hi everyone. Is it possible to enable HDR for non-HDR elements (like desktop) with the help of this software? When I enable HDR, it automatically decreases the brightness of the monitor if I have a solid black background, or that's more important if I watch a movie and there's a night sky for example. I mean, it decreases the brightness when there's something dark on the whole screen. I guess HDR just turns off for that moment and then turns on again. So... Is this a bug or a feature? The monitor: 15.6" IPS 1920x1080 FHD 240hz, nVidia GeForce RTX 2060 6 GB.

[Fourgoblin]

(11-04-2020 07:37 PM)ToastyX Wrote:  

(11-04-2020 06:35 PM)Fourgoblin Wrote:  I have a displayport 1.4 to hdmi 2.1 adapter that I use to get 4k120hz on my tv. Nvidia control panel does not allow 4k120hz as a native resolution so I tried to use CRU to force it as it works as a custom resolution. When I try to set the refresh rate to 120hz at 4k on CRU the refresh rate turns red and does not allow me to set it. How do I fix this?

EDID detailed resolutions are limited to 655.35 MHz pixel clock. The only way to add 3840x2160 @ 120 Hz is either in a TV resolutions data block in a CEA-861 extension block, or as a detailed resolution in a DisplayID data block.

I added it as both of those blocks but the option still does not appear in nvidia control panel or in display adapter properties

[joevt]

(11-04-2020 06:35 PM)Fourgoblin Wrote:  I have a displayport 1.4 to hdmi 2.1 adapter that I use to get 4k120hz on my tv. Nvidia control panel does not allow 4k120hz as a native resolution so I tried to use CRU to force it as it works as a custom resolution. When I try to set the refresh rate to 120hz at 4k on CRU the refresh rate turns red and does not allow me to set it. How do I fix this?

Do you have 48 Gbps HDMI 2.1 cable?

Do you have an RTX card? I think the adapter can use DSC to get 4K 120Hz. I don't know if it can do chroma sub sampling, etc.

What timing are you using to get 4K 120Hz (pixel clock)? 8bpc max for HBR3 without DSC is 1080 MHz but you probably have to go lower to allow headroom. If you have DSC then there should be no problem.

[Fourgoblin]

(11-05-2020 01:53 PM)joevt Wrote:  

(11-04-2020 06:35 PM)Fourgoblin Wrote:  I have a displayport 1.4 to hdmi 2.1 adapter that I use to get 4k120hz on my tv. Nvidia control panel does not allow 4k120hz as a native resolution so I tried to use CRU to force it as it works as a custom resolution. When I try to set the refresh rate to 120hz at 4k on CRU the refresh rate turns red and does not allow me to set it. How do I fix this?

Do you have 48 Gbps HDMI 2.1 cable?

Do you have an RTX card? I think the adapter can use DSC to get 4K 120Hz. I don't know if it can do chroma sub sampling, etc.

What timing are you using to get 4K 120Hz (pixel clock)? 8bpc max for HBR3 without DSC is 1080 MHz but you probably have to go lower to allow headroom. If you have DSC then there should be no problem.

Yes I have a 48Gbps 2.1 cable and a RTX 2080 super. These are the last settings I tried but still no luck. [img][/img][img][/img] [img][/img][img][/img]

[ToastyX]

(11-05-2020 05:12 PM)Fourgoblin Wrote:  Yes I have a 48Gbps 2.1 cable and a RTX 2080 super. These are the last settings I tried but still no luck.

Where's the original extension block? You probably need it for DSC to work.