Custom Resolution Utility (CRU)

[Kapten]

(12-18-2024 11:53 PM)ToastyX Wrote:  

(12-18-2024 07:35 PM)Kapten Wrote:  Indeed, the monitor has the latest firmware. It happens on any Hz above 60. I have the options 60, 75, 100, 120 or 240Hz on the monitor in windows display settings but anything other than 60 causes the screen error.

Have the latest GPU driver as well. Even did DDU and installed it again with no luck.

Honestly it sounds like something is wrong with the monitor because this should be plug and play with your GPU, or it could be an issue with the GPU, but I see lots of people complaining about issues with the G95SC. Either contact Samsung support so they can troubleshoot and replace it if necessary, or return the monitor and get a different model.

Yea that's what I figured, had two technicians here before where the first one replaced the motherboards without anything improving and the second one replacing the entire panel. That worked for a while until the monitor went into sleep mode and I woke it up again... I'll contact them again I guess.
Thanks a bunch for trying to help!

[charpour]

First post here , hi all!
I was wondering if someone could help me with the issue I’m having. I have a 4090 and an LG OLED C1 and I’m trying to create a custom ultra wide resolution (3840x1600).
Using cru, I created a DisplayID 1.3 detailed resolution of 3840x1600 and 120hz (CVT standard). Restarted the driver and I was able to select the new resolution. Desktop changed to the new resolution, however I find it impossible to change active signal mode of windows to 3840x1600, it keeps showing 3840x2160. Tried to change gpu scaling settings from Nvidia control panel, list modes and apply in display properties, nothing works. Could you please advise me if I’m doing something wrong or if there’s some bug somewhere ?
Much appreciated

[647830]

Hello all,
Thank you for this wonderful software and all the good work.

My set-up: Win10 Pro / Nvidia GTX1080 (442.74 / 64bits) / MPC-BE – MadVR / JVC DLA-RS46 (X35).

I am trying to set-up Custom Resolutions 3840x2160 at various frequencies (23, 24, 25, 30, 59, 60). Such resolutions are already available in Windows and NVidia CP, but require optimization to avoid significant drop/repeat frames.

I have tried to use MadVR for this but it does not work as it triggers the “JVC pink bug”, so I have probably no other option than doing it manually with CRU/PCC as explained here, but I need more clarity on it and therefore I am raising questions (sorry if they are stupid, I am quite a newbie…).

What I did so far:
- In CRU, main page, I have deleted all detailed resolutions and standard resolutions, and created an extension block CTA-861 to which I added data blocks HDMI, HDMI 2.0, colorimetry, video capability, HDR static metadata according to https://www.avsforum.com/threads/nvi...tions.3127652/

- With CRU, I then added detailed resolutions within the extension block for 3840x2160 as per above, using the “automatic HDTV” as a start and then going “manual”.

Question 1: So far, is it correct what I did please?

Now I am trying to optimize the detailed resolutions above mentioned. So, starting with the 3840x2160 @23(.976):

- In PCC: input 3840 x 2160 @ 24 / 1.001, 6 decimals, rest is default. It gives me 3960 x 2184 with pixel clock 207.36.

- In CRU, under extension block, and its detailed resolution 3840x2160@23p, I have entered the above as follows: 3960 and 2184 under “total horizontal” and “total vertical” (keeping active vertical and active horizontal unchanged at 3840 and 2160 respectively) and 207.36 under “Pixel clock”. Then restarted the driver.

- Then I read a 23.976 video with MPC-BE / MadVR and after 30 min it says “1 repeat frame every 4.38 minutes”.

- I then calculated the new frequency to aim for:
4.38 min = 4.38 x 60 = 262.8 sec, then 1 / (23.976 x 262.8) = 0.0001587076676 and then (1 – 0. 0001587076676) x 23.976 = 23.97219482 Mhz

- Then in PCC I input 3840 x 2160 and 23.97219482, 6 decimals. It gives: 4016 x 2192 for a pixel clock of 211.028957 MHz.

- Back to CRU under extension block, and its detailed resolution 3840x2160@23p, I have entered the above as follows: 4016 and 2192 under “total horizontal” and “total vertical” (keeping active vertical and active horizontal unchanged at 3840 and 2160 respectively) and 211.028957 under “Pixel clock”. Then restarted the driver.

Question 2: is this correct so far?

- Play again a 23.976 video, it gives 1 frame repeat every 4.40 min or 264 sec, not much of an improvement but now starts the iteration … and the tricky part for me as I might take the wrong numbers:

Calculating again the new frequency to target:
1/ (23.97219482 x 264) = 0.0001580113467

Question 3: on the above am I correct taking the previously calculated frequency and not 23.976?

And then 1 - 0.0001580113467 gives 0.9998419887, and to get to the new frequency I do: 23.97219482 x 0.9998419887 = 23.96840694

Question 4: am I correct here using 23.97219482 and not 23.976?

Then inputing this in PCC 4016 x 2192 and 23.97219482 then iterate with CRU etc.?

Question 5: in PCC, I have to input 4016 x 2192 (and NOT 3840 x 2160) together with 23.97219482 ?

Many thanks to you all

[ToastyX]

(12-24-2024 11:12 AM)647830 Wrote:  Question 3: on the above am I correct taking the previously calculated frequency and not 23.976?

And then 1 - 0.0001580113467 gives 0.9998419887, and to get to the new frequency I do: 23.97219482 x 0.9998419887 = 23.96840694

Question 4: am I correct here using 23.97219482 and not 23.976?

Then inputing this in PCC 4016 x 2192 and 23.97219482 then iterate with CRU etc.?

Question 5: in PCC, I have to input 4016 x 2192 (and NOT 3840 x 2160) together with 23.97219482 ?

Many thanks to you all

I don't have a procedure for what you're doing, so I can't advise on the math, but for the pixel clock calculator, you should only enter the resolution you want, not the totals, and the pixel clock decimal places should be whatever precision you can enter with CRU, which is 2 for EDID and DisplayID 1.3, and 3 for DisplayID 2.0. You can enter a new target refresh rate if that helps with tweaking, but make sure "Rate / 1.001" is unchecked first.

Also in the existing extension block, make sure the resolution you want to tweak doesn't exist in the TV resolutions and HDMI data blocks, and when adding a new extension block, you shouldn't need to copy the data blocks from the first extension block. You only need the data blocks in the first extension block. You don't really need to delete all the resolutions either, but you can if you don't want them. Just make sure to also check the existing extension block.

One thing to note about detailed resolutions is EDID detailed resolutions (in the main window and CTA-861 extension blocks) have front porch limits, so "Automatic HDTV" for 24/25/50 Hz will use CVT-RB instead of the expected CTA-861 standard. DisplayID extension blocks don't have that limitation, and DisplayID 2.0 will give you 3 decimal places, which might help with hitting your target refresh rate if the GPU can handle that precision. You can also try "Native HDTV" to use the lower front porch for 60 Hz, which gives you more headroom to play with the totals.

[ToastyX]

(12-23-2024 06:25 PM)charpour Wrote:  First post here , hi all!
I was wondering if someone could help me with the issue I’m having. I have a 4090 and an LG OLED C1 and I’m trying to create a custom ultra wide resolution (3840x1600).
Using cru, I created a DisplayID 1.3 detailed resolution of 3840x1600 and 120hz (CVT standard). Restarted the driver and I was able to select the new resolution. Desktop changed to the new resolution, however I find it impossible to change active signal mode of windows to 3840x1600, it keeps showing 3840x2160. Tried to change gpu scaling settings from Nvidia control panel, list modes and apply in display properties, nothing works. Could you please advise me if I’m doing something wrong or if there’s some bug somewhere ?
Much appreciated

Are you using CVT or CVT-RB? You should be using CVT-RB. If scaling is set to display in the NVIDIA control panel, then any resolution @ refresh rate listed in CRU is supposed to be sent to the display. If not, then it's an NVIDIA driver bug. The regular Windows display settings will always try to scale, so you have to go into the display adapter properties and list all modes, or use the NVIDIA control panel to change the resolution, but you mentioned this already.

[ditchmagnet]

Hi, first post here. I've used CRU in the past to get some more out of some laptop monitors I've had. I'm trying now on a desktop screen (HyperX Armada 25). Default clock is 240hz and I'm unable to even go 1 hz above that. The screen displays a message that the input signal is out of range. I'm wondering if this is something that the firmware is blocking since I find that hard to believe, so maybe there is nothing I can do, but hoping there might be something I can try?

Thanks.

[ToastyX]

(12-26-2024 05:18 PM)ditchmagnet Wrote:  Hi, first post here. I've used CRU in the past to get some more out of some laptop monitors I've had. I'm trying now on a desktop screen (HyperX Armada 25). Default clock is 240hz and I'm unable to even go 1 hz above that. The screen displays a message that the input signal is out of range. I'm wondering if this is something that the firmware is blocking since I find that hard to believe, so maybe there is nothing I can do, but hoping there might be something I can try?

It's common for firmware to block higher refresh rates, especially if the monitor already supports high refresh rates. Laptop screens are different because they normally don't have scalers, so there is often nothing blocking higher refresh rates from being sent to the panel, but the panel controller can't always handle higher refresh rates, and you're still limited by the bandwidth of the interface.

[ditchmagnet]

(12-26-2024 05:36 PM)ToastyX Wrote:  

(12-26-2024 05:18 PM)ditchmagnet Wrote:  Hi, first post here. I've used CRU in the past to get some more out of some laptop monitors I've had. I'm trying now on a desktop screen (HyperX Armada 25). Default clock is 240hz and I'm unable to even go 1 hz above that. The screen displays a message that the input signal is out of range. I'm wondering if this is something that the firmware is blocking since I find that hard to believe, so maybe there is nothing I can do, but hoping there might be something I can try?

It's common for firmware to block higher refresh rates, especially if the monitor already supports high refresh rates. Laptop screens are different because they normally don't have scalers, so there is often nothing blocking higher refresh rates from being sent to the panel, but the panel controller can't always handle higher refresh rates, and you're still limited by the bandwidth of the interface.

ok, so I guess I'm out of luck on this display. Thanks for responding, and thanks for all your work!

[dbbenq]

Hello there! hoping for some help as I do struggle figuring out whats going on here.

I am trying to make freesync work on a BenQ XL2546, the monitor is hooked via HDMI 2.0 to a laptop which has an iGPU (VEGA Ryzen 5000 series) and does recognize the monitor as a VRR capable monitor.

However when enabling VRR it will black screen on any game or application, it will work fine if VRR is disabled on the AMD driver, furthermore it did work for a random and brief time (around 2 hours) until I decided to launch CS2, which then completely broke it again.

Not sure if I am missing something. Thanks for reading!

[ToastyX]

(12-28-2024 12:37 AM)dbbenq Wrote:  Hello there! hoping for some help as I do struggle figuring out whats going on here.

I am trying to make freesync work on a BenQ XL2546, the monitor is hooked via HDMI 2.0 to a laptop which has an iGPU (VEGA Ryzen 5000 series) and does recognize the monitor as a VRR capable monitor.

However when enabling VRR it will black screen on any game or application, it will work fine if VRR is disabled on the AMD driver, furthermore it did work for a random and brief time (around 2 hours) until I decided to launch CS2, which then completely broke it again.

Not sure if I am missing something. Thanks for reading!

Is that happening only on the laptop or does it work fine on other systems? Try unplugging the monitor's power for a minute to reset it. If that works but then it happens again, the monitor is defective.