Ben,
This is what I do.
profcheck –v2 –k –w name.ti3 profile.icm >logfile.log (This will generate a
table that can be exported into Excel to find out which patches had a large
error allowing for possible re-reading. It will also create file for VRML
visualization.)
Once you have the logfile in Excel you can see which exact patches have the bad
errors. It may be something as simple as a misread of a patch and you just
have to read that line again.
From: argyllcms-bounce@xxxxxxxxxxxxx [mailto:argyllcms-bounce@xxxxxxxxxxxxx] On ;
Behalf Of 0815xl@xxxxxx
Sent: Monday, March 26, 2018 4:57 PM
To: argyllcms@xxxxxxxxxxxxx
Subject: [argyllcms] Aw: Re: creating "pre-conditioned" patches
Hi,
how can I find out which of my colors have the bad CIEDE2000?
And how is the procedure when I get the icc from the pre-conditioned patches.
Do I have to calculate <https://www.argyllcms.com/doc/average.html> (average)
with the first icc?
Thank you in advance,
Ben
Gesendet: Montag, 26. März 2018 um 10:57 Uhr
Von: "Alexey Gribunin" <Gribunin@xxxxxxx <mailto:Gribunin@xxxxxxx> >
An: argyllcms@xxxxxxxxxxxxx <mailto:argyllcms@xxxxxxxxxxxxx>
Betreff: [argyllcms] Re: creating "pre-conditioned" patches
Hello!
I would say it's something wrong with your measurements.
Max errors(CIEDE2000) 33 is really too much!
Can you show your measurements?
Best regards,
Alexey Gribunin.
Profile check complete, errors(CIEDE2000): max. = 32.953106, avg. =
1.672565, RM S = 4.190481
