|
Custom Resolution Utility (CRU)
|
|
07-27-2016, 12:19 AM
Post: #2162
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(07-26-2016 09:30 PM)Asterra Wrote: Hey all. I was pointed to this app during the course of my attempts to fix a color subsampling issue I'm having with my new Nvidia card. It's apparently a very old, well-established flaw with how Nvidia handles HDTVs as opposed to monitors. The drivers essentially assume the TV can't handle 4:4:4 and thus refuse to pass full color to the display device under any circumstance.Are you talking about RGB 4:4:4 or YCbCr 4:4:4? RGB should always be available. What color formats does the NVIDIA control panel let you set? (07-26-2016 09:30 PM)Asterra Wrote: One fellow says he fixed this problem by opening CRU, editing his 1080p profile to the "LCD - Reduced" preset, and restarting.Using the "LCD reduced" timing parameters might cause the driver to treat it as a PC resolution, which would force RGB 4:4:4, so that might be what he was seeing. If you're not seeing any changes, did you make sure to choose the "Custom extension block" option? NVIDIA doesn't support the "Default extension block" option and will ignore any changes unless you override the extension block. If you need YCbCr 4:4:4, you need to add an HDMI support data block in the custom extension block, or import one of the hdmi.dat files in the main post. (07-26-2016 09:30 PM)Asterra Wrote: He recommended I ask here to see if any of the experts might have insight into what I could try. Originally, all I was seeking was a valid method for modifying the EDID for this TV in Nvidia's drivers, in order to trick the drivers into believing they were dealing with a monitor.TVs and monitors are treated the same way. There's nothing in the EDID that indicates whether it's a TV or a monitor. The driver might treat TV resolutions differently if there's an HDMI support data block, but that applies to monitors as well. |
|||
|
|
« Next Oldest | Next Newest »
|