Custom Resolution Utility (CRU)

[ToastyX]

(07-12-2025 07:42 PM)French Toast Wrote:  Sorry for late response I am using 100% HDMI 2.0 monitor-24" MSI Optix G24C4 GPU is Intel Core i5 11400H Tiger Lake
MSI Katana GF66 - laptop 144hz at 1920x1080 and I tried the pixel clock thing for nividia but it says file too large or something

also tried with other patop 144.01hz showed automatically worked like magic it has to be something with this laptop cable n monitor work

You are hitting some sort of pixel clock limit on the laptop's end from the Intel GPU. I don't see any indication that the monitor supports HDMI 2.0. 1920x1080 @ 144 Hz is possible with HDMI 1.4, but the pixel clock is limited to 340 MHz. I don't know how that translates to 134 Hz because you didn't mention what timing parameters you used. "Exact" and "CVT-RB2" both keep the pixel clock under 340 MHz. Intel GPUs historically limited HDMI 1.4 to 300.99 MHz, but your laptop supposedly supports HDMI 2.1, so it should be able to handle the full 340 MHz for HDMI 1.4. If not, try adding an HDMI 2.x data block in the CTA-861 extension block.

[ToastyX]

(07-10-2025 10:13 AM)Nickatron Wrote:  I am unable to replicate the downscaling behavior in the "detailed resolution" slot. I can get resolutions higher than 1984x1240 to appear by lowering the refresh rate to 50hz and 30hz, but when switching to them, windows shows both "desktop mode" and "active signal mode" have switched to the resolution I want to downscale from (OBS was able to record during resolution changes).

It would be great to get the Intel PC working again, as that is the device the SSD died in, but in place of that the AMD system would be great too. I appreciate any assistance!

CRU doesn't deal with scaling, so it's all up the graphics driver. AMD and NVIDIA will not scale down resolutions in the EDID, but they have VSR and DSR for scaling down higher resolutions. Intel doesn't have an equivalent feature, but I've heard some people getting it to work with CRU somehow. Setting the scaling to "maintain aspect ratio" doesn't always work, but I haven't seen the lower refresh rate trick before, so maybe that's the key.

[cru_user]

Hi )
I use you Custom Resolotion Utility , and I can not understand why this so ,when I not use Custom Resolution Utility , my display size detect as 698 mm x 393 mm and 31,5 inc and serial number N9LMQS120007 with 2560x1440 with 93 ppi , when I use Custom Resolution Utility , my display size 640 mm x 360 mm and 28.9 inch , also modiufy serial number to 323916843009 , and also modify ppi from 93 to 102 , why so ? How I can fix this with use Custom Resolution Utility ?

[ToastyX]

(07-18-2025 11:41 AM)cru_user Wrote:  Hi )
I use you Custom Resolotion Utility , and I can not understand why this so ,when I not use Custom Resolution Utility , my display size detect as 698 mm x 393 mm and 31,5 inc and serial number N9LMQS120007 with 2560x1440 with 93 ppi , when I use Custom Resolution Utility , my display size 640 mm x 360 mm and 28.9 inch , also modiufy serial number to 323916843009 , and also modify ppi from 93 to 102 , why so ? How I can fix this with use Custom Resolution Utility ?

Screen size and image size are two different things. CRU doesn't change the screen size in the EDID. For detailed resolutions, CRU just puts a generic value for the image size because it's not used for anything, which is what's being reported in the screen shot. The PPI is being calculated from the image size. CRU doesn't include the serial number by default to allow one more slot for detailed resolutions. You can include the serial number using the "Edit..." button at the top. I don't know where it's getting 323916843009 from because that's not a valid ID serial number.

CRU wasn't originally intended to be a complete EDID editor, so it handled certain things automatically to make things simpler. I'm currently rewriting CRU from scratch to be a complete EDID editor, so the new version won't make these changes. I hope to release a test version later this year.

[cru_user]

ToastyX
I do not agree with you , PPI not link with working resolution , for example my work resolution is 2000x1125 , this because my eyes do not have perfect vision)
and if I add custom resolution in nVIDIA drivers , PPI as was 93 , so was leave 93 , but if I use CRU , PPI It changes even if work resolution leave 2560x1440 ) because modify monitor size from 31,5 inch to 28.9 inch )
also , I very want , to you save compatibility with Windows 7 and older , and do expand resolution tables from 6 to 8-12 and add function create over-size resolution such as 2640x1485 , 2880x1620 with automaticaly fit to base resolution for monitor for example user creating 3200x1800 and this will work as nVIDIA DSR or same technology )
also , If you want , you can give to me test builds , I good tester ) , only english not my native languarge , because I can be not accuracy in description detect bugs and problems ) but I try be clear in discription problem )

As for serial number , this do in here

323916843009
-----16843009

serial formed from this values

[ToastyX]

(07-18-2025 02:01 PM)cru_user Wrote:  ToastyX
I do not agree with you , PPI not link with working resolution , for example my work resolution is 2000x1125 , this because my eyes do not have perfect vision)
and if I add custom resolution in nVIDIA drivers , PPI as was 93 , so was leave 93 , but if I use CRU , PPI It changes even if work resolution leave 2560x1440 ) because modify monitor size from 31,5 inch to 28.9 inch )

I'm saying the PPI reported by the program you are using is calculated from the reported image size. It's not the actual PPI. The actual PPI would increase with lower resolutions. The NVIDIA control panel is not an EDID editor, so it would not change the reported image size. This image size is only informational. Windows does not use the image size information for anything, which is why I didn't include it and just set generic values. The new version will let you edit the image size, but that won't affect anything.

(07-18-2025 02:01 PM)cru_user Wrote:  also , I very want , to you save compatibility with Windows 7 and older , and do expand resolution tables from 6 to 8-12 and add function create over-size resolution such as 2640x1485 , 2880x1620 with automaticaly fit to base resolution for monitor for example user creating 3200x1800 and this will work as nVIDIA DSR or same technology )
also , If you want , you can give to me test builds , I good tester ) , only english not my native languarge , because I can be not accuracy in description detect bugs and problems ) but I try be clear in discription problem )

The new version will still work with Windows Vista/7/8. CRU is an EDID editor, so the number of resolutions is limited by what fits in the EDID and extension blocks. The EDID only deals with what the monitor supports, so it can't implement something like DSR. Scaling is controlled by the GPU, so the GPU's driver has to provide that functionality.

(07-18-2025 02:01 PM)cru_user Wrote:  As for serial number , this do in here

323916843009
-----16843009

serial formed from this values

I don't know where it's getting the 3239 part from. That wouldn't be in the EDID. Also 16843009 is just 0x01010101 in hex, which means the monitor just reported a generic value, so the 3239 is not supposed to be there. Windows doesn't use the serial number for anything either, so it doesn't really matter anyway.