Roger,
The OEM profile color range below the checker goes from 0 to a bit less
then 2 while the profile I made goes from 0 to a bit less then 9. No
question this will and is showing on screen. Very easy to see.
Yves
On 12/23/2019 9:44 AM, graxx@xxxxxxxxxxxx wrote:
Yves,
The first question that comes to my mind is this: does this "difference"
shows up on your monitor, when you convert from AdobeRGB to Argyll vs RR
profile?
Please send both profiles to me, off list, when you get the chance.
/ Ruggero
-----Original Message-----
From: argyllcms-bounce@xxxxxxxxxxxxx <argyllcms-bounce@xxxxxxxxxxxxx> On
Behalf Of Yves Gauvreau
Sent: December 23, 2019 8:50 AM
To: argyllcms@xxxxxxxxxxxxx
Subject: [argyllcms] Profile analysis and correction
The following 2 images
https://www.dropbox.com/s/pga46o3sppmqrid/ColorCheckerC_Adobe2OEMRREtchin.pn
g?dl=0
https://www.dropbox.com/s/dho11m20rbr0npr/ColorCheckerC_Adobe2YGRREtchin.png
?dl=0
are the results of Gamut vision Analyze a "simulated color checker"
The first image, ColorCheckerC_Adobe2OEMRREtchin.png is this test for a
source profile of Adobe RGB to a Red River Palo Duro Etching paper using a
destination profile made by Chromix using the M3 filter (OEM profile).
The second image, ColorCheckerC_Adobe2YGRREtchin.png is the same test, using
the same paper but I made the destination profile using an I1 Studio and
Argyll tools (~1000 patches)
For both test, I use the colorimetric intent and black point compensation.
My profile as about 8 times more delta L* then the OEM one? Same target,
same paper, same inks and same printer, why such a difference? Can I, if not
fix it, at least reduce this difference to a minimum?
I have other metric I could show if of any help.
Thanks,
Yves
