- This topic has 1 reply, 2 voices, and was last updated 3 years, 5 months ago by
.
-
Posts
-
Whenever I calibrate a monitor out-of-the-box, I always do a pre-cal verification to see how bad it is, but the verification always assumes a target white point that’s within 50K of whatever the monitor is doing – is there a way to override this and force the verification to assume D65?
It’s a bit misleading when a native white point is, say, 6820K, and the verification assumes 6800K, when I’m shooting for D65!
Whenever I calibrate a monitor out-of-the-box, I always do a pre-cal verification to see how bad it is, but the verification always assumes a target white point that’s within 50K of whatever the monitor is doing – is there a way to override this and force the verification to assume D65?
It’s a bit misleading when a native white point is, say, 6820K, and the verification assumes 6800K, when I’m shooting for D65!
Because you are reading it in the wrong way. Default test /vs assumed whitepoint) is WHITENESS TEST (color tint), the important test (a* axis).
To check against D65 since you are testing out of the box behavior just validate display driver ICC or simulated profile (& use simulation as display profile) and check “display profile white vs measured white” (additional statistics).
Of course all greys in measurement repost will be evaluated vs native white to check color tint, not “vs D65 reference greys”, because doing it vs D65 will be stupid (Calman verification is stupid for monitors). It is totally useless to verify grey colors vs D65, grey must be neutral to its white, and you can validate if your WP is close to whatever you set as profile WP in display profile.
