Custom Resolution Utility (CRU)

[ToastyX]

(11-29-2023 10:58 AM)Shaunuss Wrote:  Thanks man I created a detailed resolution, I also created a standard resolution. I even tried adding one in under extension blocks as a TV resolution. None of it works.

Please see my test.txt attached.

My display adapter is AMD Radeon RX 6800M

This is documented in the first post: AMD/ATI's driver also listens to the maximum TMDS clock in the "HDMI support" data block (in the CTA-861 extension block). Make sure it's enabled and set to 340 MHz.

[ToastyX]

(11-29-2023 07:42 AM)Sunlighthell Wrote:  Hi, I've been using CRU for almost 3 years, however recently I'm encountering strange issues when trying to use it.
For example I want to use CRU to delete TV resolutions from NVCP to be able to use DLDSR properly. It worked pretty well in the past but now if I do this or any other alteration through CRU like change VRR range I'm ending up without Display settings in NVCP like on screenshot. I'm on windows 11 now but before I migrated to it I got same behavior on win10 (win11 is clean install).
I have dual screen setup. Monitor I'm trying to edit is G27QC from Gigabyte. I also noticed that for some reason it has 3840x2160 listed as TV resolution when it's only 1440p monitor. Currently connected through HDMI but DP 1.2 have same issues. GPU is RTX 3080
https://i.imgur.com/KgLV0HY.png
EDIT1:Found someone with similar issue: https://www.nvidia.com/en-us/geforce/for...4090-afte/
EDIT2: Like user in the link above I decided to try install older drivers, fix things in CRU and then install newer version. I used DDU, uninstalled current drivers, however I forgot to unplug internet so Windows being smart installed older Nvidia drivers (I have these disabled via Group Policy but apparently windows don't care). Windows installed 416.34 I believe. Well fine. I opened CRU and removed TV-resolutions, restarted driver, checked NVCP and my display settings were there. Updated driver to current 546.17 and nothing changed.
So I highly suspect that newer drivers have bugs/incompatibility with CRU (and even windows maybe because I was having another issue affecting explorer.exe with specific driver versions). Because I first encountered these issues on windows 10 in mid june after some new NVidia driver (cannot remember version)

This is an NVIDIA driver bug and should be reported to them. If you're removing 3840x2160 or 4096x2160, make sure to also remove the resolutions from the HDMI data block.

[Shaunuss]

(11-29-2023 02:55 PM)ToastyX Wrote:  

(11-29-2023 10:58 AM)Shaunuss Wrote:  Thanks man I created a detailed resolution, I also created a standard resolution. I even tried adding one in under extension blocks as a TV resolution. None of it works.

Please see my test.txt attached.

My display adapter is AMD Radeon RX 6800M

This is documented in the first post: AMD/ATI's driver also listens to the maximum TMDS clock in the "HDMI support" data block (in the CTA-861 extension block). Make sure it's enabled and set to 340 MHz.

Thanks man! Your info got the resolution selectable in Windows but the TV rejects it. I assume Samsung has their firmware set to say no to any non standard resolutions. I don't see any way around this. Thanks for your help!

[funtomi]

I have a new installation of windows 11
the graphics card is intel 4400hd
cpu: Intel® Core™ i3-4130 CPU @ 3.40GHz 3.40 GHz
monitor: Samsung U28R550 (3840 x 2160 px) connected via DVI-D to HDMI cable

my problem is that I can't display higher resolution than 1920x1080 in windows, even though in LINUX both 2560x1440 at 60hz and 3840x2160 at 30hz work without problems

[attachment=1297]

[ToastyX]

(12-01-2023 05:43 PM)funtomi Wrote:  I have a new installation of windows 11
the graphics card is intel 4400hd
cpu: Intel® Core™ i3-4130 CPU @ 3.40GHz 3.40 GHz
monitor: Samsung U28R550 (3840 x 2160 px) connected via DVI-D to HDMI cable

my problem is that I can't display higher resolution than 1920x1080 in windows, even though in LINUX both 2560x1440 at 60hz and 3840x2160 at 30hz work without problems

That can only be a graphics driver issue. Did you install the Intel graphics driver?

[funtomi]

(12-02-2023 04:38 PM)ToastyX Wrote:  That can only be a graphics driver issue. Did you install the Intel graphics driver?

It's an old Haswell processor with Intel HD4400 integrated graphics and intel doesn't make new drivers for it anymore. Windows itself installed the latest version. Maybe if I could find some alternative drivers.

[ToastyX]

(12-03-2023 02:26 PM)funtomi Wrote:  It's an old Haswell processor with Intel HD4400 integrated graphics and intel doesn't make new drivers for it anymore. Windows itself installed the latest version. Maybe if I could find some alternative drivers.

The issue might be because you're using a DVI-HDMI cable. Technically a DVI port can act as an HDMI port, but single-link DVI normally should not exceed 165 MHz pixel clock, so the driver might not be allowing that on the DVI port even though the hardware is technically capable. You would have to use straight HDMI or an active DisplayPort to HDMI adapter to avoid that limitation.

[funtomi]

the interesting thing is that everything works under linux, so the cable is OK.
I can add 2560x1440, 60i (interlaced) resolution via CRU, but when I switch to this resolution the image on the monitor is broken

[jeffeh12133]

(11-29-2023 12:12 AM)ToastyX Wrote:  

(11-28-2023 05:05 PM)jeffeh12133 Wrote:  3) So by default with fresh CRU display settings there are some settings preloaded from the EDID via nvidia which are confusing. Why does a DisplayPort-connected monitor to a PC have CTA-861 data blocks such as "Colorimetry" (with xvYCC, bt2020, and other modes checked + md0), "Audio formats", "Speaker setup" and "HDR Static Metadata". Isn't a VESA DisplayPort supposed to support all of these in a PlugnPlay fashion? Perhaps these are for connecting the monitor to a console I'm assuming? It makes no sense to have Colorimetry for example when I read that it's strictly an HDMI setting. Was curious about that.

CTA-861 data blocks are not specific to HDMI. DisplayPort supports colorimetry, audio, and HDR.

So on a true 8-bit monitor you'd recommend setting colorimetry to "Default RGB" or "sRGB"? Would they be supported? By default it only checkmarks the first two xvYCC and BT2020RGB, there is no checkmarks for the Default RGB or sRGB. Should I enable them and uncheck the others to force the monitor to run 8-bit RGB full?

[ToastyX]

(12-05-2023 07:08 AM)jeffeh12133 Wrote:  So on a true 8-bit monitor you'd recommend setting colorimetry to "Default RGB" or "sRGB"? Would they be supported? By default it only checkmarks the first two xvYCC and BT2020RGB, there is no checkmarks for the Default RGB or sRGB. Should I enable them and uncheck the others to force the monitor to run 8-bit RGB full?

That doesn't matter. The colorimetry color spaces have nothing to do with the output color format, and I'm not sure Windows even uses the colorimetry information. Just make sure the YCbCr 4:4:4/4:2:2 color formats are disabled if you only want RGB.