Custom Resolution Utility (CRU)
|
12-24-2015, 05:12 AM
Post: #1887
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-23-2015 05:28 AM)zamar19 Wrote: Thanks again. I'll follow your advice. Why YCbCr 4:4:4 has a better chance to show 4:4:4 than FullRGB 4:4:4, despite Full & Limited RGB are the only options in FirePro CC for 4K reso, while YCbCr 4:4:4 options also show up for lower reso? Does it require lower bandwidth - your Color Correction article doesn't mention it? See this monitor EDID below.That's not my article. RGB 4:4:4 should work, but the TV might be converting it to YCbCr 4:2:2 internally. YCbCr 4:4:4 uses the same amount of bandwidth as RGB 4:4:4. The EDID shows YCbCr 4:4:4 support is already enabled in the default extension block. If you can't select it at 3840x2160, then that's a driver or hardware limitation. (12-23-2015 05:28 AM)zamar19 Wrote: How adding 4:4:4 output and 10-bit color would add to required bandwidth? Will it still fit into ~400 Mhz limit, or these specs don't affect it much? FirePro CC shows DPF choice 8, 10, 12bpc for the monitor at lower reso, but only 8bpc for 4K@30Hz, so is it restricted by the DP-to-HDMI adapter bandwidth? Would it allow switching to 4K 10-bit via Dual DVI?I don't know where you got 400 MHz from. AMD cards are normally limited to 297 MHz, which is just enough for 3840x2160 @ 30 Hz. That's assuming 4:4:4 output and 8-bit color. 10-bit color would require more bandwidth, so that would only be available at lower resolutions. (12-23-2015 05:28 AM)zamar19 Wrote: In Radeon cards, if only DFP CD options are shown, but no GPU 10-bit option, then the driver won't send a 10-bit signal regardless what signal you select for the monitor to accept. Does CRU allow to activate the GPU option in Radeon, not only DFP option? In FirePro I can set it now to 10-bit pixel out, but the display blacks out (not implemented in current Win 10 driver & insufficient bandwidth?).That's a FirePro feature. That option is not available with Radeon cards. (12-23-2015 05:28 AM)zamar19 Wrote: Also, how setting Wide Gamut Profile or ICC in Windows Color Management - Advanced - Device Profile and CRU may add into this? This monitor 10-bit panel supports Color Gamut & Saturation Level 72% of NTSC CRT level, so it seems qualified as Standard rather than Wide Gamut RGB. How much extra bandwidth requires Wide Gamut to pass wider color saturation values range from GPU? May be none, if each pixel saturation is passed as one value? I assume, Wide Gamut option would appear in FirePro CC Pixel Format settings if supported by the monitor, or does one need to add it in Custom extension block? Should it be supported by the video card and driver too, and what would confirm such support? Would using YCbCr 4:4:4 limit the monitor Color Gamut range compare to FullRGB 4:4:4?Gamut has nothing to do with the pixel format or color depth. Gamut is a physical characteristic that describes how the display outputs color. It's not part of the pixel data. Color profiles are not installed automatically. Windows always assumes sRGB. You have to install a color profile or create one using a calibration device. (12-23-2015 05:28 AM)zamar19 Wrote: Do you plan to add an ICC Profile for this monitor? Its gettings quite popular due to low cost. Pls consider adding more Color Gamut info to this ICC article, since most users wouldn't know the difference btw Color Depth (pixel bitness affecting number of intensity shades per reproducible color) and Color Gamut (measuring min and max saturation intensity of each color, and affecting saturation level of each color shade), and how visible on a given monitor Gamut is affected not only by ICC, but GPU color settings and available ports bandwidth.That's not my site. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 52 Guest(s)