[argyllcms] New session with EyeOnePro
- From: Roger Breton <graxx@xxxxxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Wed, 06 Jun 2007 22:43:31 -0400
Just tried with the EyeOnePro. I chose not to go any further than the
dispcal stage: I figure if I can't get good grays at that stage then it's
not worth going further on to generate a target, reading it and creating a
profile.
Here's the transcript of this session:
> G4:~ rogerbreton$ dispcal -v -c1 -m -qh -gl -yl -t5000 Eizo_i1
> Setting up the instrument
> Instrument Type: Eye-One Pro
> Serial Number: 102242
> Firmware version: 101
> CPLD version: 101
> Date manufactured: 30-4-2002
> U.V. filter ?: No
> Measure Ambient ?: No
> Tot. Measurement Count: 33915
> Remission Spot Count: 6369
> Remission Scan Count: 1020
> Date of last Remission spot cal: Tue Mar 27 19:21:52 2007
> Remission Spot Count at last cal: 6367
> Total lamp usage: 7555.877930
> Place the instrument on it's reflective white reference Serial no. 102242,
> and then hit any key to continue,
> or hit Esc, ^C or Q to abort:
> Calibration complete
>
> Place instrument on test window.
> Hit Esc, ^C or Q to give up, any other key to continue:
> Display type is LCD
> Target white = 5000.000000 degrees kelvin Daylight spectrum
> Target brightness = native brightness
> Target gamma = L* curve
> Commencing device calibration
> patch 6 of 6
> Black = XYZ 0.33 0.35 0.47
> Red = XYZ 57.96 29.36 2.15
> Green = XYZ 41.52 84.41 12.18
> Blue = XYZ 16.58 11.12 90.42
> White = XYZ 113.71 122.29 102.36
> patch 96 of 96
> Initial native brightness target = 122.293217 cd/m^2
> Had to scale brightness from 122.293217 to 110.955288 to fit within gamut
> Target white value is XYZ 106.992998 110.955288 91.503086
> Target black point = 0.314037 0.326245 0.480179
> Gamma curve offset = 0.049056, Gamma curve power = 1.933596
> Creating initial calibration curves...
> patch 96 of 96
> Brightness error = -1.263238 cd/m^2
> White point error = 0.764861 deltaE
> Maximum neutral error (@ 0.004234) = 3.820377 deltaE
> Average neutral error = 1.091184 deltaE
> Computing update to calibration curves...
> patch 96 of 96
> Brightness error = -0.644860 cd/m^2
> White point error = 0.267178 deltaE
> Maximum neutral error (@ 0.000000) = 4.661392 deltaE
> Average neutral error = 0.844739 deltaE
> Computing update to calibration curves...
> patch 96 of 96
> Brightness error = -0.624944 cd/m^2
> White point error = 0.119956 deltaE
> Maximum neutral error (@ 0.000000) = 8.108667 deltaE
> Average neutral error = 1.050216 deltaE
> Computing update to calibration curves...
> patch 96 of 96
> Brightness error = -0.562094 cd/m^2
> White point error = 0.079272 deltaE
> Maximum neutral error (@ 0.009727) = 7.941367 deltaE
> Average neutral error = 1.276602 deltaE
> Computing update to calibration curves...
> The instrument can be removed from the screen.
I don't quite understand the algorithms behind dispcal but one this is clear
to me. When dispcal iterates with "Computing initial curves" and then
"Computing update to calibration curves", it is clear dispcal is iterating
to minimize some criteria. Maybe the Avg neutral error? I don't know. But it
is clear to me that, as dispcal throws its 96 patches on screen, from 1 to
96, starting with the darkest ones, the color I see on this Eizo is not
neutral at all. I don't think it comes from my instrument as I don't get bad
neutrals with other packages I use with the same instrument. But, clearly,
there is something that fools dispcal into thinking that the values it gets
from the instrument are what they are. Here's what's going on: from patch 1
to patch 96, the color progresse from black to pinkish gray to pinkish
white.
Thank's in advance for any help,
Roger Breton | Laval, Canada | graxx@xxxxxxxxxxxx
http://pages.infinit.net/graxx
Other related posts:
