Custom Resolution Utility (CRU)

[ToastyX]

(07-01-2022 02:11 PM)caRc Wrote:  i dont really know if everyone still active there but i have a problem, cru works when i set custom resolution higher than 800x600 but it doesnt work when i made it below than it any solution? (i use amd btw)

Windows does not list resolutions below 800x600 in the display settings, but they are available for programs to use.

[caRc]

(07-01-2022 09:05 PM)ToastyX Wrote:  

(07-01-2022 02:11 PM)caRc Wrote:  i dont really know if everyone still active there but i have a problem, cru works when i set custom resolution higher than 800x600 but it doesnt work when i made it below than it any solution? (i use amd btw)

Windows does not list resolutions below 800x600 in the display settings, but they are available for programs to use.

so is there a way that you can set it below for program?

[ToastyX]

(07-02-2022 03:40 AM)caRc Wrote:  so is there a way that you can set it below for program?

You set the resolution in the program.

[IIISi Z16 HF LE]

(07-02-2022 02:31 PM)ToastyX Wrote:  

(07-02-2022 03:40 AM)caRc Wrote:  so is there a way that you can set it below for program?

You set the resolution in the program.

HI toastyX
I have little bit progressed .
I have purcahsed more advanced usb-c to hdmi 2.1 adapter Sabrent
Now I can enable HDR on mine Sam TV and windows 11 showing in resolution I can now select 100Hz or 120Hz for 4k but when I select it it just reverts back to 60Hz .
I don't really know whow to use yours soft I have tried to do detailed resolution top one But I tried 4k@120 bit won't let me from all drop down options all red.. Only when I tried 4k@75Hz it allowed select exact reduced. BUt I have restarted windows but it is not showing 4k@75Hz option in windows refresh rate settings.
How can I add ? Or I was wondering how to do 4k@120 but with limited colour sdepth 8bit and dinamic range to limited and output color format to 444 or 422
But you don't include these options in your soft?

[kibato9999]

Hi guys just got myself a new LG 32 inch 32GN63T UltraGear QHD 165Hz Monitor.
I have always used CRU to disable TV resolutions on my monitors and it has always worked but I have done the exact same way I have been doing for the past many years now and its not working for I always do this so that I can use Nvidia Super Resolution scaling otherwise it will always try and scale from a 1080P resolution even though my native is 1440P.

I have already deleted all resolutions that I would normally delete but nothing seems to change.

If anyone can help me it would be highly appreciated.

[IIISi Z16 HF LE]

[quote='kibato9999' pid='13635' dateline='1657141329']
Hi guys just got myself a new LG 32 inch 32GN63T UltraGear QHD 165Hz Monitor.
I have always used CRU to disable TV resolutions on my monitors and it has always worked but I have done the exact same way I have been doing for the past many years now and its not working for I always do this so that I can use Nvidia Super Resolution scaling otherwise it will always try and scale from a 1080P resolution even though my native is 1440P.

I have already deleted all resolutions that I would normally delete but nothing seems to change.

If anyone can help me it would be highly appreciated.

Your phots you submitted there are not visible they cannot be magnified..
Use atachment choose file and add atachment on the right

[Nintendo Maniac 64]

Just a simple question - how is the value for the exact refresh rate rounded in CRU?

Basically I noticed that sometimes mpv "Display FPS" will exactly match that CRU described including the three decimal places (e.g. both saying 72.000) but, for other refresh rates/resolutions, CRU will list as being exactly 0.001 Hz less, e.g. CRU stating that a refresh rate is 75.000Hz but mpv listing it as 75.001

I don't suppose this means that CRU always just rounds down, e.g. 75.00064Hz is listed as 75.000 in CRU?

(it may be worth mentioning that I'm actually using the Linux version of mpv; I've discovered that CRU running through WINE is quite useful on Linux for calculating much more exact refresh rates since the normal "cvt" command on Linux generates modes that are not all that exact, e.g. 74.857 rather than the 75.00Hz that it the cvt command claims - for this reason I don't suppose there's a way to have CRU directly output an xorg/xrandr-compatible modeline rather than what I've been doing of manually adding the corresponding CRU values together to essentially manually create a custom modeline?)

[kibato9999]

(07-07-2022 02:12 PM)IIISi Z16 HF LE Wrote:  [quote='kibato9999' pid='13635' dateline='1657141329']
Hi guys just got myself a new LG 32 inch 32GN63T UltraGear QHD 165Hz Monitor.
I have always used CRU to disable TV resolutions on my monitors and it has always worked but I have done the exact same way I have been doing for the past many years now and its not working for I always do this so that I can use Nvidia Super Resolution scaling otherwise it will always try and scale from a 1080P resolution even though my native is 1440P.

I have already deleted all resolutions that I would normally delete but nothing seems to change.

If anyone can help me it would be highly appreciated.

Your phots you submitted there are not visible they cannot be magnified..
Use atachment choose file and add atachment on the right

Thanks I have added in the attachment on this reply and have edited my original post.

[ToastyX]

(07-06-2022 09:02 PM)kibato9999 Wrote:  Hi guys just got myself a new LG 32 inch 32GN63T UltraGear QHD 165Hz Monitor.
I have always used CRU to disable TV resolutions on my monitors and it has always worked but I have done the exact same way I have been doing for the past many years now and its not working for I always do this so that I can use Nvidia Super Resolution scaling otherwise it will always try and scale from a 1080P resolution even though my native is 1440P.

I have already deleted all resolutions that I would normally delete but nothing seems to change.

You need to read the section about extension blocks in the first post.

[ToastyX]

(07-07-2022 05:36 PM)Nintendo Maniac 64 Wrote:  Just a simple question - how is the value for the exact refresh rate rounded in CRU?

Basically I noticed that sometimes mpv "Display FPS" will exactly match that CRU described including the three decimal places (e.g. both saying 72.000) but, for other refresh rates/resolutions, CRU will list as being exactly 0.001 Hz less, e.g. CRU stating that a refresh rate is 75.000Hz but mpv listing it as 75.001

I don't suppose this means that CRU always just rounds down, e.g. 75.00064Hz is listed as 75.000 in CRU?

(it may be worth mentioning that I'm actually using the Linux version of mpv; I've discovered that CRU running through WINE is quite useful on Linux for calculating much more exact refresh rates since the normal "cvt" command on Linux generates modes that are not all that exact, e.g. 74.857 rather than the 75.00Hz that it the cvt command claims - for this reason I don't suppose there's a way to have CRU directly output an xorg/xrandr-compatible modeline rather than what I've been doing of manually adding the corresponding CRU values together to essentially manually create a custom modeline?)

It's truncated (rounded down). This is intentional because I wanted to make sure 60.000 Hz means it's at least 60 Hz and not something like 59.9995 Hz. I thought about changing the actual value to conventional rounding, but then there would be a mismatch with the value in the text box, which is meant to be a minimum, so the text box would still have to be rounded down to produce the same actual value. CRU doesn't currently save the entered value because only the actual value based on the pixel clock is in the EDID, so it generates an entered value when editing an existing resolution. I want to make CRU 2.0 preserve the entered values and timing option to make it less confusing, so I might change the rounding then.

The cvt program rounds the pixel clock down to a multiple of 0.25 MHz because that's what the CVT standard says to do. I chose to ignore that part for CRU because I wanted more precision.

I also wanted to make it possible to export modelines to a file, but this is too complicated to implement with the current design of CRU because detailed resolutions can be in several places with different types of extension blocks. CRU 2.0 will make this much easier to implement because it will be able to consolidate all the resolutions in one list. I also thought about making the "Copy" button put the modeline in the clipboard, but I wasn't sure how useful that would be for a Windows program.