[argyllcms] Re: Large errors during printer profile check
- From: BC Rider <bcrider99@xxxxxxxxxxx>
- To: "argyllcms@xxxxxxxxxxxxx" <argyllcms@xxxxxxxxxxxxx>
- Date: Wed, 26 Feb 2014 18:47:01 -0800
>
>> Maybe newer chartread with ColorMunki give bigger read errors in some
>> cases?
>
> If you suspect version 1.6.3 then suggest dropping back to 1.6.2 to
> verify nothing hasn't been corrupted in v1.6.3. v1.6.2 is well proven and
> definitely
> doesn't have the problems you are encountering.
>
> Could it be a Ubuntu problem? My tests are all assuming Windows 7.
>
I had time so did a comparison of v1.6.2 with v1.6.3.
I downloaded and installed v1.6.3 then rescanned my last target
set (Red River Metallic). Around 1500 patches on a 290cm x 330cm sheet.
I used the same chartread command as before:
- chartread -v -B -L -T0.2 RR_Epson3880_Metallic
During operation Chartread flagged errors three times: Two were due to
"inconsistent results" and one due to "too many patches". All cleared with
a single rescan of the line.
I then compared the sample values in the .ti3 file with those taken a couple
months
earlier using v1.6.2. Colverify produced these results:
Verify results:
Total errors: peak = 0.241827, avg = 0.035801
Worst 10% errors: peak = 0.241827, avg = 0.125524
Best 90% errors: peak = 0.082837, avg = 0.025910
avg err X 0.000014, Y 0.000013, Z 0.000012
avg err L* 0.011505, a* 0.016908, b* 0.023820
I then made a new profile and Colprof finale profile check gave these results:
- peak err = 2.481701, avg err = 0.485129, RMS = 0.571661.
Conclusion: The new Chartread (v1.6.3) seems OK. I'm using the Munki with
Windows 7, 64 bit.
As an aside, I was surprised the results were so similar given the target set
has been
sitting exposed on my side desk for the past couple months and I had to wipe
off the dust
and dirt (including a bit of "scrubbing" in one particularly dirty spot).
Other related posts:
