Custom Resolution Utility (CRU)

[JayBee]

(02-09-2022 04:16 PM)ToastyX Wrote:  

(02-09-2022 01:41 AM)JayBee Wrote:  Still convinced it has something to do with the big amount of data in the EDID report, as all devices with EDID copy function I tested with it also had issues (usually breaking several features).

Where are you seeing a big amount of data? The EDID dump looks perfectly fine, and CRU reads everything just fine. I also checked with edid-decode, and it didn't report any issues. The crash is definitely an NVIDIA driver bug as other people with NVIDIA GPUs have reported the issue with some displays.

What changes are you making? The only potential issue I see is the 4:2:0 capability map defines the first 8 TV resolutions as 4:2:0 resolutions, but if you have at least 8 TV resolutions, then the data is still valid, although maybe not what you want. You can delete the capability map if you're not using 4:2:0.

Here, the error the AW EDID Editor is giving me.
I also got the same type of error on another EDID app (I don't remember the name). I do understand those app are old and probably don't support it tho.

I get that you say it's an issue with the drivers, but then that doesn't explain why did it work only once for me on my old windows, and never again (with the same old drivers from the exact same installer, with a clean install). Also as I stated before, once I got it working, it did continue working even when I updated the drivers. Tbh I did so many tests back then that I have no idea what I could have done that would have made it work.
I tend to believe it's more an issue with something special getting messed up in the drivers when changing anything, as my TV already caused crashes on my PC before without any drivers modifications. Maybe the Gsync, or HDR? No idea.

And as for what I modify, right now I am trying to remove the 4096x2160 res from the EDID. But as I said, modifying ANYTHING in it results in a crash. Heck even modifying something, modifying it back and then restarting the display drivers is still making it crash.
It seems to me that any modification to it corrupts it for some reasons.
I also tried modifying only the sound settings, changing the default res, removing hdr, changing color settings... nothing helps.

[SPEED]

(02-08-2022 03:12 PM)SPEED Wrote:  

(02-08-2022 02:55 PM)ToastyX Wrote:  

(02-08-2022 02:30 PM)SPEED Wrote:  Just tried now, picture 3 and 4. I deleted the 4k at 120 hz from CTA-861 and manually added it in through displayid 1.3 and as can be seen in the pictures, now i don't have the option to chose it in windows settings. If i edit the tv resolution from CTA-861 i only have 2 options, resolution and refresh rate which even if it would work it would not fix my issues as from my knowledge i have to play around with blanking to fix max vram at idle, picture 1. If i'm trying to edit the resolution from the main screen detailed resolutions, i only can go up to 65 hz as anything above that will become red, picture 2. And i even tried that to see if 65 will show up, but no it doesn't.

I'm reading that the 5700 XT does not support HDMI 2.1, which means the only way to get 4K @ 120 Hz is with YCbCr 4:2:0, and the only way to get YCbCr 4:2:0 is with TV resolutions, so there's no way to do what you want. HDMI 2.0 is limited to 600 MHz pixel clock, so nothing beyond that will be listed. You might have better luck with a DisplayPort 1.4 to HDMI 2.1 active adapter.

Updated my previous post, hmm, i see, at the moment with just the drivers pixel format is indeed 4k YCbCr 4:2:0 at 8 bpc and 120 hz. That's strange, i mean it's kind of a recent video card and it doesn't support HDMI 2.1 as it's been around for years now, before the 5700xt was released. So there's nothing i can do except of course if they fix their drivers or go down to 2k. Either way thank you for all your help.

Update, had a look around and i think i will try the option that you mentioned, DisplayPort 1.4 to HDMI 2.1. What do you think, will i have to use cru to fix my vram issue or will it work directly without me fiddling around?

For anyone having vram issues with radeon cards up to 5700 XT that don't support hdmi 2.1 and want to use 4k at 120 hz with cru, there is no solution as using displayport 1.4 to hdmi 2.1 will disable vrr and freesync/gsync for the moment. Some cable manufacturers say they will fix the issue in the future.

The problem i'm having at the moment with cru and 2k is that my image is very blurry when using a custom resolution and refresh rate through cru, the default 2k ones don't have this problem. This are the settings that i'm using :

[ToastyX]

(02-11-2022 08:12 AM)SPEED Wrote:  The problem i'm having at the moment with cru and 2k is that my image is very blurry when using a custom resolution and refresh rate through cru, the default 2k ones don't have this problem. This are the settings that i'm using :

Differences in scaling quality are usually one of these:
1. GPU scaling vs. display scaling
2. RGB/YCbCr 4:4:4 vs. YCbCr 4:2:2/4:2:0
3. TV scaling differently at 8 bpc vs. 10/12 bpc
4. TV scaling differently at specific refresh rates or with certain timing parameters. The standard refresh rates for TVs are 24/25/30/50/60/100/120 Hz.

[ToastyX]

(02-11-2022 07:30 AM)JayBee Wrote:  Here, the error the AW EDID Editor is giving me.
I also got the same type of error on another EDID app (I don't remember the name). I do understand those app are old and probably don't support it tho.

AW EDID Editor is choking on the HDR static metadata block and then calculating the total size incorrectly, adding two detailed resolutions that aren't there. Deltacast and EEditGold read it without complaints. There is nothing wrong with the EDID, so I don't know what is triggering the crash. Crashes can only be driver bugs or hardware issues.

[kimaya_xd]

Hello there!

I have Lenovo Thinkpad L480. I tried overclocking it through CRU but nothing seems to be working. I have followed the steps correctly and spent hours repeating the same. Intel's graphic command center does not let me go above 60hz. Moreover, under Advanced graphic settings, I only get two profiles i.e 48hz and 60hz although Intel's command center show under information tab that my screen supports upto 75hz.

Any sort of help will be appreciated.

[EnVy_a_]

When i go on stretched resolution with cru, i get a black screen for 2-3 seconds when tabbing out. How can I fix this. i have disabled and enabled full screen resolutions, changed the display scaling settings but nothing fixes it. It is fine in 1920x1080.

[ToastyX]

(02-12-2022 10:24 PM)EnVy_a_ Wrote:  When i go on stretched resolution with cru, i get a black screen for 2-3 seconds when tabbing out. How can I fix this. i have disabled and enabled full screen resolutions, changed the display scaling settings but nothing fixes it. It is fine in 1920x1080.

The only way to avoid that is to use GPU scaling or never switch resolutions.

[ToastyX]

(02-12-2022 08:15 PM)kimaya_xd Wrote:  I have Lenovo Thinkpad L480. I tried overclocking it through CRU but nothing seems to be working. I have followed the steps correctly and spent hours repeating the same. Intel's graphic command center does not let me go above 60hz. Moreover, under Advanced graphic settings, I only get two profiles i.e 48hz and 60hz although Intel's command center show under information tab that my screen supports upto 75hz.

If no changes will take effect, then Intel's driver doesn't allow EDID overrides for your laptop.

[SeeNoWeevil]

So Nvidia made some changes with how they work with EDIDs in the 5.11 drivers. This seemed to completely break HDMI output for me on my screen. They posted about this as a known issue affecting some displays, claiming it was something to do with problems with the EDID.

Now on this screen I was using CRU to remove the 4096 mode as the driver would incorrectly select this when scaling was enabled.

Eventually I managed to get this driver working by resetting all my CRU changes and then re-removing the mode I didn't want. Is it possible there's something about the changes CRU makes that these new drivers don't like?

Nvidia's post about it is here
https://www.nvidia.com/en-us/geforce/for...2/3213074/


Thanks

[ToastyX]

(02-14-2022 11:05 PM)SeeNoWeevil Wrote:  So Nvidia made some changes with how they work with EDIDs in the 5.11 drivers. This seemed to completely break HDMI output for me on my screen. They posted about this as a known issue affecting some displays, claiming it was something to do with problems with the EDID.

Now on this screen I was using CRU to remove the 4096 mode as the driver would incorrectly select this when scaling was enabled.

Eventually I managed to get this driver working by resetting all my CRU changes and then re-removing the mode I didn't want. Is it possible there's something about the changes CRU makes that these new drivers don't like?

CRU fixes checksums when it makes changes, so this issue shouldn't affect CRU.