Custom Resolution Utility (CRU)

[ToastyX]

(10-05-2022 09:08 AM)simon52min Wrote:  What i 'd like to do is connect a virtual display device through the hdmi interface of the 3070 graphics card, to create a virtual desktop of 2560 * 1440 @ 165Hz, or 3440 * 1441 @ 144Hz

You need HDMI 2.1 with FRL for those resolutions. All the emulators I know only do HDMI 2.0.

[ToastyX]

(10-04-2022 07:54 PM)Peppe90 Wrote:  I agree, that should be a obvious feature on any GPU.
So you're saying that's better to edit the EDID file when it is not mounted, then when the edit is done I'll mount it with Nvidia CP. If something's not right, I'll unmount it, make other modifications and so on.
This way I'll also edit only the actual EDID txt, no modifications will be made on registry, right?

Yes, but NVIDIA stores its settings in the registry.

[Peppe90]

(10-06-2022 02:21 PM)ToastyX Wrote:  Yes, but NVIDIA stores its settings in the registry.

Ok, maybe tommorrow I'll get some time to try it.

One last thing. What about polarity? With automatic CRT I get:

720x576i/720x480i: horizontal - / Vertical +
1440x480i: - / -

I'm using the EDID extracted the from the HD CRT (Philips 32PW9551/12) as a base. It has PAL/NTSC res. with - / - (they're not interlaced btw) and 720p/1080i are + / +

The UMSA have a jumper for setting positive or negative sync. It's just one jumper though, I don't know if it's about horizontal or vertical sync.

[ToastyX]

(10-06-2022 07:18 PM)Peppe90 Wrote:  One last thing. What about polarity? With automatic CRT I get:

720x576i/720x480i: horizontal - / Vertical +
1440x480i: - / -

1440x480i/576i is normally -/-. You have to enter 1440 for interlaced resolutions. It doesn't do anything special for 720.

[takla]

(10-06-2022 02:21 PM)ToastyX Wrote:  

(10-05-2022 11:45 PM)takla Wrote:  Can CRU edit the chromaticity coordinates?

No, but you can export a file and use an EDID editor to edit the values, and then import it back into CRU with "Import complete EDID" enabled. You can use any editor except Phoenix: https://www.monitortests.com/blog/list-of-edid-editors/

I do want to add editing the color coordinates to CRU 2.0.

Thanks. I'll give it a try. I'm thrilled for CRU 2.0

[simon52min]

(10-06-2022 02:21 PM)ToastyX Wrote:  

(10-05-2022 09:08 AM)simon52min Wrote:  What i 'd like to do is connect a virtual display device through the hdmi interface of the 3070 graphics card, to create a virtual desktop of 2560 * 1440 @ 165Hz, or 3440 * 1441 @ 144Hz

You need HDMI 2.1 with FRL for those resolutions. All the emulators I know only do HDMI 2.0.

Can you tell me in detail what is the difference between the HDMI 2.1 and the HDMI2.0 emulator? I had added CTA-861 block via cru tool, and add data block hdmi2.1 support. Is there a parameter that is not set correctly?

[ToastyX]

(10-08-2022 03:50 AM)simon52min Wrote:  Can you tell me in detail what is the difference between the HDMI 2.1 and the HDMI2.0 emulator? I had added CTA-861 block via cru tool, and add data block hdmi2.1 support. Is there a parameter that is not set correctly?

You can't add FRL support with CRU. The device has to support it. HDMI 2.0 is limited to 600 MHz pixel clock.

[egagah]

(09-18-2022 02:28 PM)ToastyX Wrote:  

(09-18-2022 02:05 AM)egagah Wrote:  I have dual monitor setup and RTX2070super as below:
PRISM+ X270 PRO (running at 2560x1440 @ 119.988Hz)
AOC2402 24G2W1G4 (running at 1920x1080 @ 120.000 Hz)
NVIDIA driver vers. 516.94

When I set my PRISM+ to 59.951Hz, my gpu can downclock, but at 119.988, it won't downclock. Both monitors can go to 144Hz but I dare not set this since the GPU will never down clock at those Hz.

Problem arise is for the PRISM+ monitor, the target resolution of 1440p 120Hz above is only found under Extension blocks, and in here, even adding just 10 to the blanking vertical lines will cause the following events AFTER using restart64:
1) PRISM+ goes totally dark
2) AOC flashes quickly, mouse move super slow, flash again, repeat 3-5 times, then PC freezes.
A restart after above event will cause the pc to load up to the login screen where it just freezes the moment the windows time appears on the AOC screen (PRISM+ stays dark the entire time).

Normally for the GPU to clock down with multiple monitors, both monitors have to be perfectly synchronized so the vertical blanking periods happen at the same time, but this is hard when the resolutions don't match. I don't know how it clocks down at 59.951 Hz because that doesn't match the other monitor exactly. Freezing would be an NVIDIA driver bug, but that might be happening if the monitor isn't staying connected properly. If the PRISM+ can't handle custom parameters, that makes it much more difficult to synchronize both monitors, and I can't even guarantee synchronizing them would allow the GPU to clock down because the driver might not handle all cases where the resolutions are different. If the PRISM+ can handle a very slight tweak to the timing parameters, making all the parameters and the pixel clock a multiple of 4 would allow making a 1920x1080 equivalent by multiplying the parameters by 0.75 and the pixel clock by 0.5625. Technically these two are perfectly synchronized:




You should also check the TV resolutions and delete 1920x1080 @ 120 Hz if it's in there. I don't know if that's enough blanking for the GPU to clock down, but if it isn't, I'm not sure what you can do if the PRISM+ won't accept higher vertical totals.

Hi ToastyX,

Is me again. So I was experimenting to see if I could get both monitors to be at 144Hz and not have GPU ramp up. I only manage to achieve 1 of the 2 monitors to be 144Hz, the other one shall be 60Hz. I'm guessing this is what you were talking about when you mentioned different resolutions causing issue with syncing and hence back to high memory clocks again right? Right now, the PRISM+ 2160p is 144Hz and the AOC 1080p is 60Hz exactly.

Both monitors are set to the CVT-RB Standard. I wanted to try the RB2 settings but the PRISM+ 2160p one shows red on the refresh rate (can only take up to 110Hz). So I left both at RB.

You reckon there are anything else I can try?

[IAmOrion]

Hi There, I only recently stumbled across this utility - It worked for me when I tested it under Windows 11 21H2, but seemingly, after auto-updating to Windows 11 22H2 (...and the plethora of headaches that bought with it!) CRU no longer shows my custom resolutions in the windows display settings resolution drop down. I downloaded the latest 1.5.2 version (Previously I used 1.5.1) - I ran reset-all.exe, I rebooted, I then ran CRU and added my custom resolution. I then ran restart.exe and restart64.exe then decided to reboot again for good measure, but alas, my newly created resolution still doesn't show. For what it's worth, I'm thinking it's a Windows 22H2 thing because my AMD Radeon software that also has a custom resolution function that previously worked, also no longer works and won't show any custom resolutions in windows display settings.

[ToastyX]

(10-12-2022 09:44 AM)IAmOrion Wrote:  Hi There, I only recently stumbled across this utility - It worked for me when I tested it under Windows 11 21H2, but seemingly, after auto-updating to Windows 11 22H2 (...and the plethora of headaches that bought with it!) CRU no longer shows my custom resolutions in the windows display settings resolution drop down. I downloaded the latest 1.5.2 version (Previously I used 1.5.1) - I ran reset-all.exe, I rebooted, I then ran CRU and added my custom resolution. I then ran restart.exe and restart64.exe then decided to reboot again for good measure, but alas, my newly created resolution still doesn't show. For what it's worth, I'm thinking it's a Windows 22H2 thing because my AMD Radeon software that also has a custom resolution function that previously worked, also no longer works and won't show any custom resolutions in windows display settings.

I'm not aware of any issues with 22H2. Use the latest version of DDU to clean out all the old drivers: https://www.wagnardsoft.com/forums/viewtopic.php?t=4142

Then install the latest AMD driver: https://www.amd.com/en/support/kb/releas...in-22-10-1