Custom Resolution Utility (CRU)

[ToastyX]

(01-21-2014 03:48 AM)JonnyRedHed Wrote:  For me and my setup, my highest res is 2560x1440@75 (in games only), native should be 1080p, but now 2560x1440 shows in NV control panel (native) and in windows (recommended). 2560x1440 is at the top of CRU. Does setting something at the top of the CRU list automatically mark it as 'native' in the NV control panel and 'recommended' in the windows panel. (Win7)

The first detailed resolution in the EDID is considered the native/recommended resolution. It doesn't affect how the resolution is sent to the monitor. It's mainly used to determine the default resolution to use when one hasn't been set, like when you first plug in the monitor.

(01-21-2014 03:48 AM)JonnyRedHed Wrote:  Is there a way to mark any entry as native, such as 1920x1080 (1080p) for me on my plasma screen. Does it matter?

No. Don't you have to make 2560x1440 native to work around the 16-bit color issue? If you're using 2560x1440 for games, then you want it to be the default resolution anyway.

(01-21-2014 03:48 AM)JonnyRedHed Wrote:  I found with CRU on my system that the NV HD audio seems to go into a sort of error if I edit my CRU listing and re-import the hdmi-audio.dat file again. Upon reboot the Nvidia TV output says 'Digitaloutput-4' and the sample rate format section drop down is greyed out and locked to 16bit 48khz. I then remove the NV HD audio driver, reset CRU, reboot, and add all entries again and import the hdmi-audio.dat file again, reboot. I did have 4 entries which might have caused it, using just 3 entries seems to all work, add a 4th to the top CRU section and my HD audio goes into error like I mention above.

CRU can't save the monitor name if there are four detailed resolutions, but I don't see why that would affect audio. NVIDIA has too many weird driver issues.