Custom Resolution Utility (CRU)
|
12-23-2020, 01:14 AM
Post: #5501
|
|||
|
|||
RE: Custom Resolution Utility (CRU) | |||
12-23-2020, 04:03 AM
Post: #5502
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-22-2020 02:44 AM)ToastyX Wrote: Yes, I mean the firmware in the monitor could be faulty and making it produce a bad signal that's causing NVIDIA's driver to crash, which would also be a bug in NVIDIA's driver. If it also happens with HDMI, then I would suspect a hardware problem. Thanks ToastyX Robbie I will proceed with trial HDMI cable and monitor firmware. I do not know what to make of the (CRU?) driver detecting a new monitor. I hope solution is monitor firmware, there is also chatter of nvidia addressing this issue but with 10xx series GPU's not 3070. But if it happens on HDMI and monitor firmware does not fix I may be trying to source another expensive GPU. I have sent you $10 tip via Paypal from Matthew Pool. I appreciate the free software and assistance with my troubleshooting. |
|||
12-24-2020, 11:50 AM
Post: #5503
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-22-2020 09:33 PM)ToastyX Wrote:(12-22-2020 04:40 PM)jarkid Wrote: But what has confused me is that in some games, it's very fine. but in other games, it's not okay. Don't know why. Why shouldn't it be always abnormal for every game, but only for a specific game? Any clues?If the monitor doesn't handle FreeSync correctly, then the problem might depend on the frame rate of the game. ToastyX, Thank you for your kindly help... 1. According to your experience, do you know which blanking setting most manufacturers use? LCD standard or LCD native for 144hz or other RR higher than 60hz? 2. You explained that there's no visual effect between different blanking settings. But the blanking for LCD is the waiting time. If I have a longer blanking, doesn't that mean my screen need more time to response, so that I'd have a lower refresh rate? p.s. if my monitor is faulty, then I have to buy another one... |
|||
12-25-2020, 12:53 AM
Post: #5504
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
I've been using Dolby Atmos for Home Theatre as a workaround to get 5.1 sound from my Nvidia card to my LG TV (optical out to a receiver)
Today I used CRU to attempt to enable 5.1 output via LPCM. This didn't work unfortunately, so I set LPCM sound back to 2.0 vs 5.1 in CRU and rebooted. Now, even after reinstalling Nvidia drivers, deleting monitor and rebooting, reinstalling Dolby Access, I am still unable to output 5.1 sound through Dolby Atmos as I had been previously. It only detects 2 channels. How can I completely undo everything that CRU may have altered? I have already used reset-all.exe in safe mode. Thanks! |
|||
12-25-2020, 03:01 AM
Post: #5505
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-25-2020 12:53 AM)afxwinter Wrote: I've been using Dolby Atmos for Home Theatre as a workaround to get 5.1 sound from my Nvidia card to my LG TV (optical out to a receiver)CRU only creates EDID overrides. Running reset-all.exe removes all EDID overrides and resets the Windows display settings. If there's no * next to the "(active)" status, then there is no EDID override installed. CRU doesn't change any audio settings. It only describes what the monitor can do. |
|||
12-25-2020, 03:02 AM
Post: #5506
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-24-2020 11:50 AM)jarkid Wrote: 1. According to your experience, do you know which blanking setting most manufacturers use? LCD standard or LCD native for 144hz or other RR higher than 60hz?1. That depends. Monitors usually use the CVT-RB standard, which is what "LCD standard" uses except for TV resolutions. One exception is 1920x1080 @ 144 Hz monitors, which use non-standard timing parameters to fit within HDMI and dual-link DVI bandwidth. "LCD native" is non-standard, but it happens to match the CEA/CTA standard for 1920x1080 @ 120 Hz, which is what TVs use. The next version of CRU will have separate timing options for TVs. 2. No, the pixel clock is also increased, so the visible (non-blanking) part actually refreshes slightly faster with a longer blanking. The refresh rate remains the same. |
|||
12-25-2020, 01:59 PM
(Last edited: 12-25-2020, 02:10 PM by jarkid)
Post: #5507
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-25-2020 03:02 AM)ToastyX Wrote:(12-24-2020 11:50 AM)jarkid Wrote: 1. According to your experience, do you know which blanking setting most manufacturers use? LCD standard or LCD native for 144hz or other RR higher than 60hz?1. That depends. Monitors usually use the CVT-RB standard, which is what "LCD standard" uses except for TV resolutions. One exception is 1920x1080 @ 144 Hz monitors, which use non-standard timing parameters to fit within HDMI and dual-link DVI bandwidth. "LCD native" is non-standard, but it happens to match the CEA/CTA standard for 1920x1080 @ 120 Hz, which is what TVs use. The next version of CRU will have separate timing options for TVs. Dear ToastyX, thanks for your explanation. I am using a new monitor right now, and I will observe if the problem would still exist. |
|||
12-27-2020, 02:20 AM
Post: #5508
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
I was mainly trying to use CRU to enable 7.1 DD+ passthrough ARC from my Samsung Q70 TV. By default, the control panel->sound->Samsung->speaker setup only showed Stereo. But the device properties show it supports DD(5.1) and DD+(7.1), which both should work through ARC (and they do work from the native netflix app on the TV).
So I ran a HDMI cable from a second port on my GFX card to my receiver directly, and looked at that 'monitor' in CRU in the extension block Speaker Setup to see what was checked (that connection allows 7.1 speakers). Then I edited the Samsung in CRU to check those same speakers. Then rebooted. But this doesn't seem to have had any effect. I also tried exporting those settings as an INF and doing the advanced boot with driver signing disabled, etc. Still didn't do anything... only shows Stereo as an option. I also tried changing the order of supported formats to move PCM to the bottom and move DD+ to the top, since the TV is still only receiving PCM from the computer. But this also had no effect. Is there anything obvious I'm doing wrong maybe? Thank you! |
|||
12-27-2020, 05:51 AM
(Last edited: 12-27-2020, 05:52 AM by jarkid)
Post: #5509
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-25-2020 03:02 AM)ToastyX Wrote:(12-24-2020 11:50 AM)jarkid Wrote: 1. According to your experience, do you know which blanking setting most manufacturers use? LCD standard or LCD native for 144hz or other RR higher than 60hz?1. That depends. Monitors usually use the CVT-RB standard, which is what "LCD standard" uses except for TV resolutions. One exception is 1920x1080 @ 144 Hz monitors, which use non-standard timing parameters to fit within HDMI and dual-link DVI bandwidth. "LCD native" is non-standard, but it happens to match the CEA/CTA standard for 1920x1080 @ 120 Hz, which is what TVs use. The next version of CRU will have separate timing options for TVs. Hi ToastyX, I just bought a new 24" IPS monitor with 75hz to test, and here is the default setting which is sought by CRU: https://imgur.com/a/y5eniuC The default 75hz setting is in "Standard resolutions". Unfortunately, the short flickering STILL exists with this monitor when I am running an Android simulator with a specific game. So I guess the setting uses the LCD standard, too. Now I created another LCD native setting(longer blanking time for 75hz), and it's all right. So I guess that the older monitor is not faulty. This is my desktop enviroment, I am in my windows while the program is running there: https://imgur.com/a/KYXf8sr so I am guessing the program just needs more blanking time for the video card to work perfectly, is that possible? |
|||
12-27-2020, 03:14 PM
Post: #5510
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-27-2020 05:51 AM)jarkid Wrote: so I am guessing the program just needs more blanking time for the video cardNo, that's not normal. Something is wrong with the video card then. What does the flickering look like? Are you overclocking the video card at all? Have you tried another cable? |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 118 Guest(s)