Custom Resolution Utility (CRU)
|
08-31-2016, 01:20 AM
Post: #2265
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-28-2016 02:52 AM)scy1192 Wrote: Just wondering, what algorithm do you use to determine the correct values? I've noticed that none of the standards (CVT, GTF, DMT) that I can use in the NVidia Control Panel spit out the same numbers, and yours always works better (fewer artifacts) with my QX2710 so I just set it to manual and copy the numbers over."LCD standard" should be the same as "CVT reduced blank" except for TV resolutions like 1920x1080 @ 60 Hz, which uses the CEA standard because that's more common (even with computer monitors). "LCD native" just uses the 60 Hz "LCD standard" timing parameters for all refresh rates. This works better when adding higher refresh rates with some LCD monitors and TVs. This is also what is filled in by default when clicking the "Add..." button. "LCD reduced" uses non-standard timing parameters to reduce the pixel clock for certain resolutions by reducing the totals. For example, it will keep 1920x1080 @ 72-77 Hz under the 165 MHz pixel clock limit for single-link DVI using timing parameters that I've found work with many LCD monitors. "CRT standard" should be the same as the "CVT" standard. It is mostly useful for CRT monitors, and it also works for adding lower resolutions with LCD monitors. "GTF" isn't included in CRU, although I did write the code for it. It is an old standard that has been replaced by the CVT standard. "DMT" doesn't make sense as a timing option because the DMT standard only defines timing parameters for specific resolutions and refresh rates. "LCD standard" uses the DMT standard for 1360x768 @ 60 Hz and 1366x768 @ 60 Hz because those are common with LCD monitors and TVs, and the DMT standard for 1920x1080 @ 60 Hz is the same as the CEA standard. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 118 Guest(s)