- This topic has 4 replies, 2 voices, and was last updated 10 years, 4 months ago by
.
-
Posts
-
Howdy!
I am hoping someone can help a noob with a handful of questions. I have a xrite i1 display pro.
I had a few questions about corrections and calibration in general. I am auto importing correction into x-rite, but I’m not sure it’s right. The correction seems to be for a glossy apple display where as I am calibrating the CCFL matte LCD of my laptop. I think the auto is failing because my display device is called Color LCD which seems to match the name of Apple’s display. I’m not sure if this matters. I’ve only tried the laptop screen so far. When I view profile information, it seems to show the Apply Glossy Display on all profiles whether I had corrections enabled or not..
- Are corrections monitor specific or just to that type? I had thought the correct was needed just for back light type (ccfl vs wled etc.) but now I’m not sure. My laptop monitor is a CCFL TN LCD but I also have a couple LED TN and a couple LED IPS. I have found many corrections for various IPS displays but not many for TN.
- Does this mean I’m profiling to standards as read by the colorimeter but with no way of knowing if those results actually match the real world? (essentially all my results would be “results as read by colorimeter + error from lack of or bad correction”
- Assuming I can’t find the right specific correction, what’s the best next step? For example I added generic CCFL correction and that seems to be for an IPS. Would it be better to use an as close as possible correction vs none at all? What’s the best option if I can’t justify purchasing a spectrophotometer to generate a correction?
- Could somebody recommend settings for a laptop that only has brightness control? (no color) Max brightness reads about 140 CDM^2. One “tick” lower with function key reads 118 so I left it max. When I ran uncalibrated report, it had the values below. That means native whitepoint is around 5600 right? Would be results be to calibrate at native vs trying to force 6500? (unless I’m grossly misunderstanding). I would ideally use curves + matrix right? What about black point correction?
Here was uncalibrated report:
12:36:01,328 Uncalibrated response:
12:36:01,329 Black level = 0.2059 cd/m^2
12:36:01,331 50% level = 27.29 cd/m^2
12:36:01,332 White level = 140.16 cd/m^2
12:36:01,334 Aprox. gamma = 2.36
12:36:01,335 Contrast ratio = 681:1
12:36:01,335 White chromaticity coordinates 0.3300, 0.3426
12:36:01,338 White Correlated Color Temperature = 5606K, DE 2K to locus = 2.8
12:36:01,338 White Correlated Daylight Temperature = 5607K, DE 2K to locus = 2.2
12:36:01,338 White Visual Color Temperature = 5536K, DE 2K to locus = 2.7
12:36:01,339 White Visual Daylight Temperature = 5662K, DE 2K to locus = 2.1
12:36:01,341 Effective Video LUT entry depth seems to be 8 bits
12:36:01,342 Black drift was 0.000000 DE
12:36:01,342 White drift was 0.000000 DE
12:36:01,344 The instrument can be removed from the screen.- Will having i1 profile software installed as well cause conflict?
- Maybe I’m blind but is there a donate page somewhere?
Thanks everyone!
Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.Could somebody recommend settings for a laptop that only has brightness control? (no color) Max brightness reads about 140 CDM^2. One “tick” lower with function key reads 118 so I left it max. When I ran uncalibrated report, it had the values below. That means native whitepoint is around 5600 right? Would be results be to calibrate at native vs trying to force 6500?
Skip interactive adjustment, use “As measured” for whitepoint (native).
I would ideally use curves + matrix right?
The most accurate choice is the default (XYZLUT + matrix).
I read somewhere else that curves + matrix was more widely supported versus XYZLUT and thus better for general use not focusing on managed color aware applications. So is that incorrect or am I misunderstanding anything?
I read somewhere else that curves + matrix was more widely supported versus XYZLUT and thus better for general use not focusing on managed color aware applications.
That’s the case for some applications, but nowadays the situation is somewhat better than it was a few years ago. Also, an XYZ LUT + Matrix profile, as the name implies, also contains curves + matrix tags, so applications that cannot use the LUT can fall back to those. Those that do support LUT profiles however, will use the more accurate LUT tags, and thus I think it’s usually “worth it” to create a LUT profile.
