Custom Resolution Utility (CRU)
|
11-07-2023, 04:27 AM
Post: #7721
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-05-2023 11:57 AM)MoonDoggy Wrote:(11-04-2023 07:54 PM)KukoCL Wrote: Hello!, Woah, i didn't even think that it could be the cable because it was "original" from Samsung. I always watch LTT but i didn't see that video. I know it's a little off topic, but do you have an nvidia card with updated drivers connected to that G9?, i'm having terrible random flicker with artifacts once in a while but only happens when i'm idling, like reading on my browser or using Telegram. |
|||
11-07-2023, 02:58 PM
(Last edited: 11-07-2023, 07:16 PM by wyup)
Post: #7722
|
|||
|
|||
![]()
Hi, thanks for this amazing utility and support.
I want to sync laptop screen and external projector with the same exact vertical refresh frequency rate so in duplicated/clone screen mode I get the best results for video playback and minimum drift from standard 60 Hz refreshing rate. I have noticed in the past that running cloned screens with slightly different default refreshing rates makes the actual refreshing rate of external screen to be in between both, instead of exact native. By default my laptop screen specifies 60.307 Hz refresh rate and my external DLP projector 60 Hz. If I run external only, playback stats report exact 60.000 Hz, but when I run in dual clone mode it gets like 60.100 or so. I have copied external monitor parameters to laptop screen and it works, but I get a jagged line in playback stats, and sometimes not exact 60.000 Hz. I'd like to get straight a/v lines as normal. Am I doing right? What do you advise? Maybe replace laptop monitor params with Automatic PC and 60.00 Hz? Or equalling black porch/blanking between screens? I'd like to run clone mode and 60.000 Hz on both, so playback is as stable as possible with minimum repeated frames and judder. One laptop has 1600x900 screen and another laptop has 1920x1080. Both are connected to the same 1920x1080 DLP projector. |
|||
11-08-2023, 03:56 AM
Post: #7723
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-07-2023 02:58 PM)wyup Wrote: I want to sync laptop screen and external projector with the same exact vertical refresh frequency rate so in duplicated/clone screen mode I get the best results for video playback and minimum drift from standard 60 Hz refreshing rate. I have noticed in the past that running cloned screens with slightly different default refreshing rates makes the actual refreshing rate of external screen to be in between both, instead of exact native.CRU has an "Exact" timing option that can make the refresh rates match perfectly, and "Automatic PC/HDTV" also happen to be exact at 1920x1080 @ 60 Hz and 1600x900 @ 60 Hz, but there's still no guarantee that the displays will be synchronized because the refreshes could start at different times and stay offset from each other, and the hardware clock might not match perfectly at different pixel clocks even if the refresh rate is mathematically the same. You'll have to try it and see what happens. |
|||
11-08-2023, 03:56 AM
Post: #7724
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-07-2023 02:36 AM)N8TM8T Wrote: I recently upgraded to a 7900XTX to run my 144Hz 4k display, and in an attempt to lower the idle power draw, I increased the Extension Block's Vertical Blanking to the point where it allowed my GPU's VRAM to downclock, solving my power draw issue.Unless something changed with newer GPUs, normally it's not possible to change the memory clock if you have multiple displays with different resolutions or refresh rates because the displays won't be synchronized, although in theory this could work if the displays support variable refresh rate. The memory clock must change while all of the monitors are in the vertical blanking period between refreshes to be able to retrain the memory without seeing artifacts. You might be seeing an artifact of the memory clock changing when it's not supposed to, which would be a bug on AMD's end, or maybe changing the timing parameters affected variable refresh rate support in the monitor in some way, although I don't know if that affects the desktop. Try increasing the front porch instead of the back porch, and try increasing the lower end of the variable refresh rate range. |
|||
11-08-2023, 03:57 AM
Post: #7725
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-06-2023 02:53 PM)opa99 Wrote: Happens on all three resolutions I have tried, including the 3840x2160.You said the setup works with any other source than the PC, so ARC should be sufficient unless the TV is doing something different when passing audio from the PC to the AVR. What happens if you set the channels to 8 instead of 6? For the lower resolutions, there needs to be enough horizontal blanking to transmit the audio format. The default 3840x2160 should have enough. |
|||
11-08-2023, 05:25 AM
(Last edited: 11-08-2023, 05:31 AM by KukoCL)
Post: #7726
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-05-2023 09:42 PM)ToastyX Wrote:(11-04-2023 07:54 PM)KukoCL Wrote: I've been reading in these forums and reddit about solving screen brightness flickering because of VRR, so all i want to do is to change the Variable Refresh Rate range but i can't figure out how to do it.Are you using DisplayPort or HDMI? What GPU? Sorry i just read your answer. It's displayport 1.4 and an RTX 4080. Maybe i'm wrong but i think the problem is that CRU doesn't support 5120 pixels width (the width of my screen) so it shows blank values. Thank you for your software and all your help you give here ![]() |
|||
11-08-2023, 05:44 PM
Post: #7727
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-08-2023 03:57 AM)ToastyX Wrote:(11-06-2023 02:53 PM)opa99 Wrote: Happens on all three resolutions I have tried, including the 3840x2160.You said the setup works with any other source than the PC, so ARC should be sufficient unless the TV is doing something different when passing audio from the PC to the AVR. What happens if you set the channels to 8 instead of 6? For the lower resolutions, there needs to be enough horizontal blanking to transmit the audio format. The default 3840x2160 should have enough. Thank you ToastyX for reminding me to also reflect or at least read what I wrote earlier. ![]() After doing that, I realized that I also wrote that when adding a spatial filter (Dolby Atmos for home theater) in Windows settings, 5.1 audio is transmitted all the way to the receiver. Although compressed (Windows is encoding LPCM 5.1 to lossy Atmos 5.1). This leads me to think that maybe CRU did exactly what I asked it to do, but it is the limitation of the TV/ARC, since in all other cases (spatial filters disabled) I understand that PC is always transmitting LPCM, and ARC can only carry LPCM 2.0, so if the TV is not encoding it before sending, it will not be transmitted in 5.1/7.1 to the receiver over ARC. Nevertheless, I did check the blanking, and I must say I do not understand what that means, but it reads: 3840x2160: 560 pixels, 90 lines 3840x1500: 160 pixels, 43 lines I have also attached screenshots of all the parameters for these two resolutions in detailed resolutions window. |
|||
11-08-2023, 09:14 PM
(Last edited: 11-08-2023, 09:29 PM by wolik)
Post: #7728
|
|||
|
|||
![]()
Hello.
I am unhappy owner of 8K 65QN900B since one day. Problem: I cannot activate DLDSR. How can I delete 7680 and 4096 resolutions? On my old monitor 4K KS9500 I could delete with CRU "4096" successfully. Now three fields are empty. I hope if I delete these two resolutions then DLDSR will be available again. Or I am too "Sweet Summer Child?" ![]() ![]() |
|||
11-09-2023, 01:03 AM
Post: #7729
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(10-26-2023 09:51 PM)ToastyX Wrote:(10-26-2023 01:27 PM)Dinkles Wrote: Still as soon as I import the previously working profile into CRU (or remove them manually) the monitor simply crashes the PC or stops it booting?That's 100% an NVIDIA driver bug and needs to be reported to them. I'm not sure what triggers the bug because it's not anything that CRU is doing wrong. It triggers when any EDID override is present but doesn't always happen. In your case it didn't happen and then it did. Someone clued me in that it might be related to what resolution was last set in Windows or the NVIDIA control panel before restarting. In his case, he was trying to delete 4096x2160 and had to set the resolution to 1920x1080 @ 60 Hz before restarting to avoid the problem, but you're doing the opposite and trying to keep the higher resolution. If you just fresh installed a driver after DDU or ran reset-all.exe, then Windows has no record of a last set resolution for the monitor, so try changing the resolution to let Windows save something before restarting. I've just created a forum topic on the official Nvidia forums in regards to this EDID override system hang. The last supported driver from all of my tests is 528.02. Or at least anything at or above version 530 is borked for my system. The hangs at startup turn off my USB devices. If I enable Bootlogging from Msconfig, the file has nothing in it but a few gibberish characters. The system is crashing before Windows can really do much of anything. Booting to safe mode and removing the driver or just deleting the EDID profile will resolve the issue. I have a RTX 2080ti paired with a Dell S2719DGF (Freesync). Nvidia will probably tell me to shove it since I don't have a certified Gsync Compatible monitor. The thing is, I've been narrowing the range of the monitor from 40-144hz to 90-144hz with this utility since 2020 without issue to eliminate brightness flickering. The wonders of building a pandemic era machine. Nvidia must be aware of EDID overrides. Their Quadro series allows editing the EDID from within NVCP. Oh well, for now I'm sticking to 528.02 and allowing myself to continue using this wonderful utility. |
|||
11-09-2023, 04:10 AM
Post: #7730
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-08-2023 05:25 AM)KukoCL Wrote: It's displayport 1.4 and an RTX 4080.No, CRU shows what the driver says it's receiving from the monitor, but NVIDIA's driver has been doing strange things with certain monitors lately such as modifying the EDID that it reports to Windows vs. what the monitor is actually reporting, which is also why CRU is not showing the extension blocks. The driver also ignores EDID overrides for those monitors, so CRU would have no effect. The active monitor is the only entry that's being used, but the presence of other entries with different data suggests the EDID changed at some point, maybe because of some setting you changed in the monitor, or if you tried HDMI, that would be a separate entry, or NVIDIA changed the EDID that it's reporting to Windows in a newer driver version. The other entries suggest either VRR was not enabled in the monitor, or the VRR range is being reported using another method. Run this and post the test.txt file here so I can see what's being reported: https://www.monitortests.com/EDID-test.zip |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 66 Guest(s)