Custom Resolution Utility (CRU)

[bcec]

(11-05-2014 02:35 AM)ToastyX Wrote:  Do you happen to have four detailed resolutions defined? I just remembered an issue with NVIDIA's driver where audio wouldn't work properly if you have four detailed resolutions.

Mm, yes I was trying to add 4 resolutions, 23.976, 24, 29.97, and 30.

(11-05-2014 02:35 AM)ToastyX Wrote:  I'm also trying to figure out what you're trying to do. The original problem seems like a signal quality issue or an issue with the receiver not handling higher pixel clocks, not an issue with incorrect timing parameters. The receiver doesn't change the timing parameters according to your EDID dumps, so what timing parameters are you using to fix the problem?

I am setting timings I got from TV's edid, so I am not really trying to send something different. So for instance, take 23Hz. By default, I get erratic video signal drops. It happens on the desktop too, so it is not related to playing a video or running a program. But if I create a custom resolution using nVidia while specifying manual timings, then I no longer get video signal drops. It's worth nothing that this doesn't happen if computer is directly connected to the TV.

For timings, these are the values:

Active Pixels: 3840x2106
Front porch: 176x8
Sync width: 88x10
Total Pixels: 4400x2250
Polarity: Positive x Positive

(11-05-2014 02:35 AM)ToastyX Wrote:  You also won't be able to separate 23/24 Hz and 29/30 Hz with CRU. I would advise importing the hdmi-bitstream.dat file to wipe out all the resolutions in the extension block. Then you can try adding 23/24 Hz and 29/30 Hz separately using the NVIDIA control panel.

Mmm, that's a bummer. I was hoping to create at least 3 resolutions, 23.976, 24 and 29.97. Through nVidia, when I create 23.976, I can no longer create one for 24. And when I create 29.97, I think that is saved for 30 directly and not 29.