Originally Posted by GlenC
Are you not reading my posts or just don't want to consider the process.?
Not rocket science, Glen. Because I don't agree, you claim I don't understand. I do. And I don't agree.
Here is a logical counterargument:
How can you possibly determine any type of required input offset without some starting reference point? By your method, you can only calibrate one input at one scan rate.
To the contrary, by turning the Color slider down to zero, you can use *any* input to adjust white balance and grayscale because you are guaranteeing that NO errant color has been introduced up to that point
. The service-mode settings for WB/grayscale are global, not input-specific, and they exist in only one place: the SBRT, xDRV, and xCUT settings.
Having gotten this right, you can now turn Color up again and use the input-class-specific
settings of CBOF and CROF, plus the adjustments in 2170P-3/UBOF thru UHOF, to fix any offsets that exist at those inputs by whatever method. Clear and simple.
The entire explanation of my procedure points out the flaw in your method.
Sorry, repetition ("Look, look, mine *is* better than yours") is not counterargument.
Perfect, I think not, "acceptable to your eye only", yes, I would agree.
And for what other purpose is this entertainment device being adjusted? The fiction that 6500K *exactly* is all that is acceptable is sheer nonsense! Heaven help the poor chap whose set is not exactly 6500K, and the neigbors find out. Think of the ridicule and finger-pointing! If the white point on my set is 6341K and whites appear white, it is
perfect. Such small deviations from the industry-standard do not affect the perception of colors to any significant degree -- the rather adaptive eye/brain combination sees to that, and the variations among real-world program sources swamp small deviations completely. In my business, I have calibrated numerous color monitors for graphic artists involved in color pre-press. That
is a critical application. Watching CSI/Miami, the evening news, Gladiator? I think not! Perspective, folks, perspective.
Glen, if you want to discuss/defend the business
of ISF calibration, start another thread. This thread is to help folks understand the effects of the myriad service-menu codes and how adventuresome folks might adjust them to improve their sets and fix problems. Those who simply want someone to come out and calibrate everything and don't particularly want to get their hands dirty or clutter their brain (don't start!) with niggling details, will look for a local ISF tech to do the job. I don't do my own brake jobs anymore, either. One trades $$ for trouble. ISF calibration, its training, the required equipment investment -- all consitute a potentially profitable business with an up-front investment
whose practicing individuals charge dearly for their work. For the folks who need it, the results are likely fabulous! But it's a business
, Glen, not a religion.