Custom Resolution Utility (CRU)
|
08-05-2024, 10:58 PM
(Last edited: 08-06-2024, 12:10 AM by kurtdh)
Post: #8321
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Can anyone help? I have a FO32U2P 4k 240hz OLED monitor. In display settings I have my desktop successfully set to 4k 240hz, however when I load CRU 1.5.2, my monitor isn't listing any 240hz modes. Screenshot is attached. How can I have it detect a 240hz mode so I can edit it correctly?
https://imgur.com/a/hF85tHQ EDIT: I figured out using a DisplayPort cable instead of a HDMI 2.1 now shows "Display ID 1.3: 1 data block" under extension blocks and properly shows the 4k 240hz resolution. How come CRU detects it properly with a DisplayPort cable but not an HDMI 2.1 cable? I would much prefer to use HDMI 2.1, so if any of you could provide assistance or a fix to have it detect properly with HDMI 2.1? |
|||
08-06-2024, 01:19 AM
Post: #8322
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-05-2024 10:58 PM)kurtdh Wrote: Can anyone help? I have a FO32U2P 4k 240hz OLED monitor. In display settings I have my desktop successfully set to 4k 240hz, however when I load CRU 1.5.2, my monitor isn't listing any 240hz modes. Screenshot is attached. How can I have it detect a 240hz mode so I can edit it correctly?The issue is there is a hidden extension block because of the extension override data block that HDMI 2.1 introduced, which complicates extension block handling because now there are two places to determine the extension block count. Last time I looked into implementing this, NVIDIA's driver was broken and wasn't reporting the EDID correctly, which complicated matters. That issue might have been fixed since you can read the first extension block, but last I heard, NVIDIA's driver has another issue that causes EDID overrides to be ignored if display stream compression is active, which 4K @ 240 Hz would require. I do plan to implement the extension override data block, but I don't have the hardware to test if any of this is fixed. It will help if I can see what the driver is reporting. Run this and post the test.txt here: https://www.monitortests.com/EDID-test.zip |
|||
08-06-2024, 03:51 AM
Post: #8323
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-06-2024 01:19 AM)ToastyX Wrote:(08-05-2024 10:58 PM)kurtdh Wrote: Can anyone help? I have a FO32U2P 4k 240hz OLED monitor. In display settings I have my desktop successfully set to 4k 240hz, however when I load CRU 1.5.2, my monitor isn't listing any 240hz modes. Screenshot is attached. How can I have it detect a 240hz mode so I can edit it correctly?The issue is there is a hidden extension block because of the extension override data block that HDMI 2.1 introduced, which complicates extension block handling because now there are two places to determine the extension block count. Last time I looked into implementing this, NVIDIA's driver was broken and wasn't reporting the EDID correctly, which complicated matters. That issue might have been fixed since you can read the first extension block, but last I heard, NVIDIA's driver has another issue that causes EDID overrides to be ignored if display stream compression is active, which 4K @ 240 Hz would require. I do plan to implement the extension override data block, but I don't have the hardware to test if any of this is fixed. It's attached. I can't seem to get CRU to work even with DisplayPort. If I double click on display id 1.3 in extension blocks, double click detailed resolutions, select 3840x2160 @ 239.999 Hz (the resolution/hertz my Windows desktop is using). Then I change the hertz to some random number like 88. I click OK three times to exit CRU, I run restart64.exe, but my Windows desktop remains at 240hz. Am I doing something wrong, or are you saying that CRU doesn't work with my monitor? (Aorus FO32U2P)? |
|||
08-06-2024, 04:33 AM
Post: #8324
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-06-2024 03:51 AM)kurtdh Wrote: I can't seem to get CRU to work even with DisplayPort. If I double click on display id 1.3 in extension blocks, double click detailed resolutions, select 3840x2160 @ 239.999 Hz (the resolution/hertz my Windows desktop is using). Then I change the hertz to some random number like 88. I click OK three times to exit CRU, I run restart64.exe, but my Windows desktop remains at 240hz. Am I doing something wrong, or are you saying that CRU doesn't work with my monitor? (Aorus FO32U2P)?I'm saying NVIDIA ignores any changes for monitors with display stream compression (DSC). NVIDIA also doesn't support custom resolutions or DSR/DLDSR with DSC. This is something NVIDIA would need to fix, so at this point adding support for the extension override data block wouldn't make a difference other than being able to see the data. I need to see the test.txt with the monitor connected to HDMI so I can see the extension blocks. Then I can give you a file with the extension block not hidden. |
|||
08-06-2024, 05:45 AM
Post: #8325
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-06-2024 04:33 AM)ToastyX Wrote:(08-06-2024 03:51 AM)kurtdh Wrote: I can't seem to get CRU to work even with DisplayPort. If I double click on display id 1.3 in extension blocks, double click detailed resolutions, select 3840x2160 @ 239.999 Hz (the resolution/hertz my Windows desktop is using). Then I change the hertz to some random number like 88. I click OK three times to exit CRU, I run restart64.exe, but my Windows desktop remains at 240hz. Am I doing something wrong, or are you saying that CRU doesn't work with my monitor? (Aorus FO32U2P)?I'm saying NVIDIA ignores any changes for monitors with display stream compression (DSC). NVIDIA also doesn't support custom resolutions or DSR/DLDSR with DSC. This is something NVIDIA would need to fix, so at this point adding support for the extension override data block wouldn't make a difference other than being able to see the data. Ok here is test with HDMI connected to the FO32U2P. So you're saying any monitor that uses DSC won't work with CRU at all? I didn't know that was a limitation. What good is this file to you if you can't fix it? Just so I can see info but not change it? |
|||
08-06-2024, 01:16 PM
Post: #8326
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-06-2024 05:45 AM)kurtdh Wrote: Ok here is test with HDMI connected to the FO32U2P. So you're saying any monitor that uses DSC won't work with CRU at all? I didn't know that was a limitation. What good is this file to you if you can't fix it? Just so I can see info but not change it?The issue is specific to NVIDIA and is mentioned in the first post. Hopefully NVIDIA will fix it eventually or I find some workaround. Meanwhile this works for custom resolutions but not custom refresh rates: https://www.monitortests.com/forum/Threa...Editor-SRE You can import this file in CRU to see the extension block: ![]() Here is a file for HDMI with DSC disabled: ![]() Can you check if importing the second file and restarting has any effect? If it works, 3840x2160 @ 200/240 Hz should be disabled, but 165 Hz should be available. Run the EDID-test.exe afterwards and post the test.txt. I just want to check if it's actually ignoring the EDID override completely or if it's just not allowing custom resolutions with DSC. Last time I checked it was ignoring EDID overrides completely unfortunately. In theory it should be possible to work around this for HDMI by using a programmable EDID emulator device with a file exported from CRU, but I don't know if any can handle the HDMI 2.1 bandwidth and two extension blocks, and the programmable ones tend to be expensive. |
|||
08-06-2024, 08:14 PM
(Last edited: 08-06-2024, 08:17 PM by Jen)
Post: #8327
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Good day ToastyX
![]() So I have several questions about HDMI 1.4 and pixel clock limits. Im currently using a dual gpu system (non mux) with an intel uhd 630 and gtx 1650, and I wanted to know if custom resolutions above 300 or 340 mhz would work, since the hdmi out comes from the intel gpu. Im aware there isn't a pixel clock patcher for intel, but I think I heard you mention something about HDMI support display block a while ago. Would setting the max TMDS clock bypass this? I just want to make sure since my new 1440p 360hz monitor still hasn't arrived and I plan to use a custom resolution of 1920x1080@250 for competetive gaming, since that's the max on hdmi 1.4 at 10bit with yuv 4:2:0. I used this tool to figure that out: https://tomverbeure.github.io/video_timings_calculator Also Regarding this tool, the 1920x1080@250 is 543 mhz, obviously far higher than the advertised limit for udh630 and hdmi 1.4; however, It claims that it's possible to work either way. Is this because it doesn't count the gpu pixel clock limit or is this a program error? Thanks in advance ![]() |
|||
08-06-2024, 08:53 PM
Post: #8328
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-06-2024 08:14 PM)Jen Wrote: Im currently using a dual gpu system (non mux) with an intel uhd 630 and gtx 1650, and I wanted to know if custom resolutions above 300 or 340 mhz would work, since the hdmi out comes from the intel gpu. Im aware there isn't a pixel clock patcher for intel, but I think I heard you mention something about HDMI support display block a while ago. Would setting the max TMDS clock bypass this? I just want to make sure since my new 1440p 360hz monitor still hasn't arrived and I plan to use a custom resolution of 1920x1080@250 for competetive gaming, since that's the max on hdmi 1.4 at 10bit with yuv 4:2:0.Well the pixel clock limit is assuming 8 bpc 4:4:4. 4:2:0 uses half the bandwidth, so in theory it can be done, but in reality there isn't a way to add custom 4:2:0 resolutions for HDMI 1.4 other than 3840/4096x2160 @ 50/60 Hz. Technically 4:2:0 wasn't supported until HDMI 2.0, but some drivers implemented 4:2:0 for 3840/4096x2160 to allow 50/60 Hz with HDMI 1.4. |
|||
08-06-2024, 09:02 PM
Post: #8329
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Alright I see. Thank you so much for your support
![]() I'll see what can I do with yuv 4:2:2 instead |
|||
08-07-2024, 12:27 AM
(Last edited: 08-07-2024, 12:31 AM by kurtdh)
Post: #8330
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-06-2024 01:16 PM)ToastyX Wrote:(08-06-2024 05:45 AM)kurtdh Wrote: Ok here is test with HDMI connected to the FO32U2P. So you're saying any monitor that uses DSC won't work with CRU at all? I didn't know that was a limitation. What good is this file to you if you can't fix it? Just so I can see info but not change it?The issue is specific to NVIDIA and is mentioned in the first post. Hopefully NVIDIA will fix it eventually or I find some workaround. Meanwhile this works for custom resolutions but not custom refresh rates: https://www.monitortests.com/forum/Threa...Editor-SRE Can I import both of those files, or is it just one or the other? To be clear, you want me to hook up HDMI, import the second file, do nothing else in CRU, reboot, run edid-test.exe and post the test.txt file correct? Also, 165hz won't work with 10-bit color without DSC correct, so I would have to be using 8 bit in order to use 165hz with no DSC? Also, do I need to use restart64 after I do the import? Is the import and restart64 actually what will disable DSC on my monitor? |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 144 Guest(s)