Custom Resolution Utility (CRU)
|
11-09-2024, 05:56 AM
Post: #8591
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-08-2024 06:04 AM)dotcomma Wrote: It has HDMI 2.1, but since it is not possible to raise min VRR range above 48Hz I'm not using it, as I need more than 100Hz min range. Or do you know about some workaround for these HDMI 2.1 limits? Min range cannot go above 48Hz and max range cannot go below 100 if I'm not mistaken.That's true for HDMI 2.1 VRR. Maybe it would be better to disable VRR if flicker is a problem. |
|||
11-09-2024, 05:29 PM
(Last edited: 11-09-2024, 05:43 PM by Audioboxer)
Post: #8592
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(10-24-2024 05:24 PM)ToastyX Wrote:(10-22-2024 12:02 PM)Audioboxer Wrote: Hi guys just signing up to say I've noticed Windows now reporting 400 instead of 1000 like it was previously. Been using CRU since I got my G8 and it's been fine changing peak brightness, but doesn't seem to be working now.Well either NVIDIA's driver is ignoring the change or there's something else overriding it. What happens if you delete the HDR10+ data block? Have you tried the Windows HDR Calibration app? Sorry for delay getting back to you, if I delete this it just comes back again on a restart. For now I think I'll just have to use the Windows calibration app and save a profile, as for some reason the behaviour around CRU has changed and using a custom value is being ignored. Some games like Alan Wake 2 will pull peak brightness from whatever System - Display - Advanced display states. With some digging online, especially in topics about my monitor, there may be some Nvidia driver issues going on https://www.reddit.com/r/ultrawidemaster...are_button |
|||
11-09-2024, 11:04 PM
(Last edited: 11-09-2024, 11:20 PM by funkerwolf)
Post: #8593
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(10-15-2024 05:48 AM)ToastyX Wrote:good night, I decided to double-check and unfortunately, 75Hz mode now works only through displayport, but not through hdmi as it should be, I really don't want to use this stillborn standard, as only one problem it causes - banal when you turn off the monitor, it disappears from the system and in the same anydesk just on the output black square Malevich. on the old drivers all ok, what for sabotage of current technologies I do not understand. but it's like the driver ignores the custom modes now.(10-15-2024 04:49 AM)funkerwolf Wrote:You didn't set the max TMDS clock in the HDMI data block like I said to do. You said it was all in place.(10-14-2024 10:49 PM)ToastyX Wrote:(10-11-2024 08:29 PM)funkerwolf Wrote:That was the old URL. I have an updated version here: https://www.monitortests.com/edid-test.zip(09-27-2024 12:07 AM)ToastyX Wrote: Show me what you have. Run this and post the test.txt here: https://www.monitortests.com/EDID-test.zip And the most not clear to me still, if displayport is supposedly a more modern standard, then why it does not have half of the settings that are available through hdmi? |
|||
11-10-2024, 06:02 PM
(Last edited: 11-10-2024, 06:02 PM by Audioboxer)
Post: #8594
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
ToastyX, here is what could be a noobish question for you.
I've just switched from DP to HDMI on my Samsung G8 because I finally picked up a HDMI 2.1 cable. I also wanted to see if I could reproduce the current behaviour I have where editing the monitor max luminance didn't seem to be changing in Windows system settings anymore. New issue though, if I edit this It actually bricks me getting into Windows. As soon as login screen should appear the monitor just goes black/no signal and begins its 60 second timeout timer. Spent the last few hours tearing my hair out thinking the HDMI cable was faulty/reinstalling drivers after cleaning in safe mode and finally figured out it was simply any time I edited max luminance it would brick the monitor from displaying anything once Windows loaded (after a restart from editing). Maybe this is me not understanding editing under HDMI is different from DP, or is it something else??? Cheers |
|||
11-11-2024, 08:17 PM
Post: #8595
|
|||
|
|||
RE: Custom Resolution Utility (CRU) | |||
11-13-2024, 11:06 AM
(Last edited: 11-13-2024, 03:19 PM by Audioboxer)
Post: #8596
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-11-2024 08:17 PM)ToastyX Wrote:(11-10-2024 06:02 PM)Audioboxer Wrote: It actually bricks me getting into Windows. As soon as login screen should appear the monitor just goes black/no signal and begins its 60 second timeout timer.Is the computer frozen (does caps lock respond)? Do you have any other monitors connected? The computer is not frozen, it proceeds to boot into Windows (I can tell because my camera does Windows Hello and it'll flash then log me in). It's just a black screen on the monitor post BIOS/boot logo. Or well, the screen will go black after it times out. Only way to get it back is to boot into safe mode and reset entries via CRU reset bat file. If I unplug HDMI and plug it back in it still isn't working, occasionally I'll get repeated sounds like the plug in new device sound. Never had this behaviour on DP only HDMI. |
|||
Yesterday, 07:24 PM
Post: #8597
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-10-2024 06:02 PM)Audioboxer Wrote: ToastyX, here is what could be a noobish question for you. Current CRU version does not support all EDID extension datablocks on latest HDMI 2.1 high refresh monitors, wait for new CRU version which should support it. |
|||
Yesterday, 08:20 PM
(Last edited: Yesterday, 08:20 PM by Audioboxer)
Post: #8598
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(Yesterday 07:24 PM)dotcomma Wrote:(11-10-2024 06:02 PM)Audioboxer Wrote: ToastyX, here is what could be a noobish question for you. Thanks, that will be what it is then as it's an HDMI 2.1 monitor. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 89 Guest(s)