Custom Resolution Utility (CRU)

[ToastyX]

(09-21-2023 05:28 PM)sofakng Wrote:  I've just purchased an HDMI dummy plug and a DisplayPort dummy plug.

However, when I copy the EDID from my monitor (3440x1440@160) both plugs refuse to show that resolution even though it's the exact same EDID.

I think the dummy plugs only contain a simple I2C EEPROM so is there something else that is needed for the GPU to allow these higher resolutions?

I've also attached the EDID if that helps?

EDIT: I've also run restart-all.exe, reset64.exe, rebooted, etc. They all seem to work but these higher resolutions don't show up. I've also tried adding my macOS resolutions (3456x2160@120) but it refuses to show up as well.

Pixel clock limits still apply to dummy plugs. DisplayPort dummy plugs tend to be just passive DisplayPort to single-link DVI adapters internally, so they're limited to 165 MHz. HDMI dummy plugs should support up to 600 MHz pixel clock if you include both the HDMI and HDMI 2.x data blocks, but that's still not enough for 3440x1440 @ 160 Hz. You'd have to use a lower refresh rate.

[JasonMT]

Hi, I have noticed I cannot change Peak brightness in Windows 11 with CRU (Max luminance) if I have an ICC advanced color profile activated in Color Management. Is this to be expected?

[sofakng]

(09-22-2023 05:52 PM)ToastyX Wrote:  Pixel clock limits still apply to dummy plugs. DisplayPort dummy plugs tend to be just passive DisplayPort to single-link DVI adapters internally, so they're limited to 165 MHz. HDMI dummy plugs should support up to 600 MHz pixel clock if you include both the HDMI and HDMI 2.x data blocks, but that's still not enough for 3440x1440 @ 160 Hz. You'd have to use a lower refresh rate.

Why does the pixel clock limit apply to a dummy plug? Can't we just define anything and pretend it's an HDMI 2.1 plug with much higher limits?

Why would an HDMI dummy plug have a different limit than an actual HDMI 2.1 display?

Doesn't LG OLEDs define 4K120 resolutions in the EDID?

(thanks so much for helping!!)

[ToastyX]

(09-23-2023 03:09 PM)sofakng Wrote:  Why does the pixel clock limit apply to a dummy plug? Can't we just define anything and pretend it's an HDMI 2.1 plug with much higher limits?

Why would an HDMI dummy plug have a different limit than an actual HDMI 2.1 display?

Doesn't LG OLEDs define 4K120 resolutions in the EDID?

(thanks so much for helping!!)

HDMI 2.1 requires special back and forth communication that a dummy plug might not support. I don't remember if HDMI 2.0 does as well, but there are HDMI 2.0 plugs on the market. If you can only get up to 340 MHz pixel clock, then it doesn't support HDMI 2.0.

[ToastyX]

(09-23-2023 04:25 AM)JasonMT Wrote:  Hi, I have noticed I cannot change Peak brightness in Windows 11 with CRU (Max luminance) if I have an ICC advanced color profile activated in Color Management. Is this to be expected?

I wouldn't know. That sounds like either a Windows limitation, or maybe something needs to be in the color profile. I wouldn't think the color profile should matter though.

[sofakng]

(09-23-2023 03:31 PM)ToastyX Wrote:  HDMI 2.1 requires special back and forth communication that a dummy plug might not support. I don't remember if HDMI 2.0 does as well, but there are HDMI 2.0 plugs on the market. If you can only get up to 340 MHz pixel clock, then it doesn't support HDMI 2.0.

Do you have any suggested resources I can use to research this?

I’d love to be able to build a dongle for people that supports 4K/120 HDR without needing anything else.

I’ve ordered a CAT24C208 EEPROM which supports segment pointers so it should support 512 byte EDID.

However it sounds like I need to figure out to trick the source into allowing higher pixel clocks…

[Dinkles]

Hey,
I’m wondering if anyone can help me.

I have a AG493UCX monitor with a 5120x1440@120hz native resolution.

However, the monitor/windows appears to believe the native resolution is 3840x1080 which is a huge issue for a number of reasons.

For example,
When I switch to my other monitor and return to this monitor (via NCP) windows resets the resolution to 3840x1080.

When I play a game using NIS the game is actually downscaled to 3840x1080 then stretched up to 5120x1440 which looks beyond awful and really makes NIS unusable.

The monitor works perfectly at 5120x1440@120hz
The monitors native resolution is 5120x1440@120hz
I am using DP

The monitor basically tells windows (for some unknown reason) that its native res is 3840x1080 and this causes me so many issues. If there is any way to use CRU to change the “recommended” resolution or simply have it always default to 5120 that would be great.

I tried using CRU and simply changing the resolutions to 5120, however the numbers turn red and don’t allow me to save them, even though I am using the correct resolution and timings.

I googled the issue and found a Reddit post that led here, is there anyone here who can help me out with how to get this 5120x1440 monitor to simply recognise and register its actual “recommended” resolution by default.

That’s folks, and also thanks for creating CRU as I just used it on my C3 to delete the 4k resolutions that were also causing issues with scaling, so thanks for that info, the tool and the guide.

49” AG493UCX
Windows 10
RTX 3080
Latest Nvidia Driver / Window up to date etc.

[ToastyX]

(09-24-2023 09:25 PM)Dinkles Wrote:  The monitor basically tells windows (for some unknown reason) that its native res is 3840x1080 and this causes me so many issues. If there is any way to use CRU to change the “recommended” resolution or simply have it always default to 5120 that would be great.

I tried using CRU and simply changing the resolutions to 5120, however the numbers turn red and don’t allow me to save them, even though I am using the correct resolution and timings.

The monitor probably does report the correct native resolution, but the graphics driver is not reporting it correctly to Windows. I can check what the monitor reports if you run this and post the test.txt file here: https://www.monitortests.com/EDID-test.zip

CRU currently doesn't have a way to change the native resolution above 4095x4095 because of standards limitations, and newer standards weren't fully adopted by graphics drivers the last time I checked, so I couldn't find a way to make it work without deleting every other resolution.

[ToastyX]

(09-23-2023 06:14 PM)sofakng Wrote:  Do you have any suggested resources I can use to research this?

I’d love to be able to build a dongle for people that supports 4K/120 HDR without needing anything else.

I’ve ordered a CAT24C208 EEPROM which supports segment pointers so it should support 512 byte EDID.

However it sounds like I need to figure out to trick the source into allowing higher pixel clocks…

HDMI is proprietary and the standard is not freely available, which makes this information hard to find.

[Dinkles]

(09-26-2023 02:07 AM)ToastyX Wrote:  

(09-24-2023 09:25 PM)Dinkles Wrote:  The monitor basically tells windows (for some unknown reason) that its native res is 3840x1080 and this causes me so many issues. If there is any way to use CRU to change the “recommended” resolution or simply have it always default to 5120 that would be great.

I tried using CRU and simply changing the resolutions to 5120, however the numbers turn red and don’t allow me to save them, even though I am using the correct resolution and timings.

The monitor probably does report the correct native resolution, but the graphics driver is not reporting it correctly to Windows. I can check what the monitor reports if you run this and post the test.txt file here: https://www.monitortests.com/EDID-test.zip

CRU currently doesn't have a way to change the native resolution above 4095x4095 because of standards limitations, and newer standards weren't fully adopted by graphics drivers the last time I checked, so I couldn't find a way to make it work without deleting every other resolution.

Thanks toasty,
I’ll run this after work and post the results shortly.

Will it assist much though if we are unable to set native res above 4095?

If the nVidia driver is picking it up wrong, can we amended that so the driver/card/monitor recognise the “actual” recommended resolution of 5120 as its honestly so frustrating having the monitor reset every time I switch to my other monitor and not being able to use things like scaling etc as they all try to scale to the incorrect “recommended” resolution.

You’d think nVidia/Microsoft and AOC could get the basics.

I’ll run this asap and post the results..