- This topic has 4 replies, 2 voices, and was last updated 4 years, 10 months ago by
.
-
Posts
-
Hello, I have a Spyder5Pro and on 2 laptops from different manufacturers and find that both have the same issue. Using the latest DisplayCal on Windows 10 (3.8.2), when laptops are calibrated, the calibration shows a near 6500K whitepoint. And appears to be correct when profile is loaded within windows manually. When the displaycal auto loader is enabled however, the colors skew red immediately and repeatedly. On both laptops different levels show red, but the E*00 go giant and the white point is over 7200k. Without the profile selector the colorchecker shows the same result with E*00 but the white point is much closer.
Hi,
- Open DisplayCAL.
- Select “Laptop” under settings.
- Select an appropriate measurement mode (when in doubt, white LED).
- Click “Calibrate & Profile”.
- When the process is finished, install the profile. At this point the calibration is active, and color managed applications can use the profile.
Note that it doesn’t make a visible difference if you use the Windows built-in calibration loader or the DisplayCAL loader (the latter will be slightly more accurate though).
Trying now. I have been trying to set a manual white point of 6500k, but apparently that reverts laptop settings. Thanks for the advice.
Hrm, it ran, and the white point is a 7k still, but the measured vs assumed whitepoint is at 10.83 and the Max E*00 is at 8+. Laptop is a Lenovo Y740 15 inch with 144hz dolby vision HDR (fakeish HDR).
measured vs assumed whitepoint is at 10.83
This just means the native whitepoint is not close to the daylight locus, which is expected when not adjusting the whitepoint (recommended for laptops, as they usually are already limited in achievable contrast).
Max E*00 is at 8+
What verification chart? Did you use a simulation profile? This usually just means the chosen simulation is out of gamut for the display.
