Re: Photoshop Gamut warning vs ColorThink
Re: Photoshop Gamut warning vs ColorThink
- Subject: Re: Photoshop Gamut warning vs ColorThink
- From: "dpascale" <email@hidden>
- Date: Sun, 24 Feb 2008 15:15:08 -0500
Thanks Klaus,
You can define an acceptance threshold with a litle bit of awk voodoo.
I hope no animals were harmed while developing this formula!
I dowloaded three versions of AWK interpreters for Windows, but none wants
to work so far with the example your provide.
After analysing the various AWK error messages and a bit of search, I came
to the conclusion that the problem is NOT your example.
Part of the problem lies in the use of double-quotes vs quotes in Windows
when assigning an AWK script in a command line.
I will post the solution if I find it (Anybody familiar with AWK on
Windows?).
However, your command line script does work as is on a Mac (Well, Macs are
Unix beasts after all!)
I then assigned the output to a file by adding
output.txt
at the end of the script code.
Looking at the output file, I saw what this script does, and I realized that
I can always use the xicclu utility as is, without the AWK voodoo trick,
such as:
xicclu -fif -ia -l330 -a /your/profile.icc < /your/colors.txt> output.txt
which gives and output of the form:
81.347000 -0.048000 0.061000 [Lab] -> Lut -> 0.883449 0.885760 0.858346
[RGB] Lim 2.627555
91.081000 -0.046000 0.054000 [Lab] -> Lut -> 0.966177 0.966232 0.945948
[RGB] Lim 2.878357
100.000000 -0.001000 0.000000 [Lab] -> Lut -> 1.000000 0.999855 0.977977
[RGB] Lim 2.977832 (clip)
[Actual 95.142660 -0.171855 0.128800, deltaE 4.862051]
with two lines of info/data when there is clipping, and filter/order the
deltaE afterwards using Excel, but first using an ASCII editor in order to
place the Actual value and the deltaE on the same line as the Lab and RGB
values (i.e. by removing the RETURN after (clip) ).
Using AWK indirectly made me better understand xicclu, interesting!
Thanks,
Danny Pascale
email@hidden
----- Original Message -----
From: "Klaus Karcher" <email@hidden>
To: "colorsync-users" <email@hidden>
Sent: Sunday, February 24, 2008 7:40 AM
Subject: Re: Photoshop Gamut warning vs ColorThink
dpascale wrote:
A method with "no tolerance" will tend to reject more colors than what
could be "accepted". For instance, I am willing to live with a 1 Delta-E
difference (any formula you choose) between file and print (and probably
more in many cases). In practice, this means that patches tagged as
clipped with xicclu are acceptable for me when measured, and I verified,
with a test file, that it happens. However, now I know why this happens.
You can define an acceptance threshold with a litle bit of awk voodoo.
This nice little line of code will only baa about colors with Delta E >
5.0:
xicclu -fif -ia -l330 -a /your/profile.icc < /your/colors.txt | awk
'{if($5=="deltaE") {sub(/]/,"",$6); if((0.0+$6) > 5.0) print last ": " $0
"]"; else next} else last=$0}'
It's a good idea to execute the following line of code on non-English
systems before using awk with xicclu to avoid decimal separator issues:
LANG=C LC_ALL=C; export LANG LC_ALL
Klaus
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden