Florian Höch wrote
because around a decade ago Adobe decided they would no longer support absolute colorimetric for RGB display profiles (you can select it, but it'll use relative colorimetric behind your back).
It's starting to make sense!! Hmm.... With our Epson7900 printers, "AdobeRGB White" gets inked when we print Absolute colorimetric from photoshop. I did a quick check on the numbers. When I print using photoshops "Absolute colorimetric" into our Epson Premium Luster 260 (CMYK) printer colorspace, "AdobeRGB White" gets sent to our RIP as 0,1,2,0 CMYK . So Judging by both the CMYK numbers I'm getting for "AdobeRGB White", and how the resulting print hues looks _very_ similar to my 5000K monitor when the print is viewed in a GTI viewing booth, it would appear.... That with the printer colorspace profiled as a CMYK space and Adobe doing the Absolute transform from AdobeRGB to the printer colorspace, what I effectively get is a relative colorimetric transform from AdobeRGB's D65 white into D50 white, followed by an Absolute Colorimetric transform from this D50 space into the CMYK printer color space. BUT... I would expect that if the printer colorspace were to be profiled as an RGB space, then the same Adobe "Absolute Colorimetric" print pipeline would result in "AdobeRGB White" remaining un-inked on the print. And so the print would then take on a colder appearance compared with me having via a CMYK printer profile. Because now, with an RGB profile as the destination, it would be Relative Colorimetric all the way to the cold paper white of Epson Premium Luster 260. Gosh! I think the fog is lifting at last! Thanks everyone for the great feedback. Regards Peter Miles
Previously I wrote... So Judging by both the CMYK numbers (0,1,2,0 CMYK) I'm getting (when printing) "AdobeRGB White", and how the resulting print hues looks _very_ similar to my 5000K monitor when the print is viewed in a GTI viewing booth, it would appear.... That with the printer colorspace profiled as a CMYK space and Adobe doing the Absolute transform from AdobeRGB to the printer colorspace, what I effectively get is a relative colorimetric transform from AdobeRGB's D65 white into D50 white, followed by an Absolute Colorimetric transform from this D50 space into the CMYK printer color space. <end snip> ..and this also makes sense of other issues I have encountered. Recently an artists work required very accurate solid-color print matches to real-wold samples, for a installation called "∆E2000 1.1" (see http://shaunwaughphotography.blogspot.co.nz/search/label/2014). We used SpectraShop4 to take readings of the bright orange of Agfa boxes and calculate the RGB values needed to match the colors of each box. The orange color we measured was outside both sRGB and AdobeRGB and so we ended up using ProPhotoRGB as our source colorspace. Using Spectrshop4 to compare the original spectral sample from the box to a reading from the print we made to match it (printed absolute colorimetric from photoshop), I was surprised to see that there was only Delta E2000 1.1 between them. Thats the best match to a real-world sample our facility has been able to make using calculations alone. (i'm sure the 'Pro's' out there can get much closer than this) On reflection, I reasonably sure tit's a combination of the way we have set up our printer, and having used a source colorspace (ProPhotoRGB) having a D50 white point. With the way we have set up our printer, the first half of the Adobe's "Absoulte Colorimetric" print pipeline leaves the D50 of ProPhotoRGB untouched. And then Adobe does a 'Real' absolute transform from that into our printers CMYK colorspace, which is why I think we came so close to hitting the color 'out of the box', so to speak. Previously, with other artists work that might have benefited from hitting specific colors measured from real-world objects, I'd used smaller RGB spaces (AdobeRGB) and not being happy with the results, not realizing the consequences of those spaces being D65 for our printer set-up. So recently I'd begun exploring SpectraShop4 a bit more and noticed how the calculated RGB values from spectral readings of the neutral samples in a Color Checker Chart became approximately R=G=B only when the illuminant for the observer viewing condition matched the white point of the colorspace I was calculating the RGB values for. Which now makes sense. And that got me to thinking about the color of gray and if equal RGB values really are neutral. Anyway next time I need to hit specific colors from measurements made from real-world objects i'll use D50 editing spaces. (as long I'm printing from photoshop, absolute colorimetric, and into a CMYK printer colorspace). I'd like to learn to use Argyll, but need to get to grips with using command line interface. Thanks again for all the help Best Regards Peter ________________________________
Peter,
I'd like to learn to use Argyll, but need to get to grips with using command line interface.
There is a GUI for Argyll... http://dispcalgui.hoech.net/ Mark
Nick, DOH! Mark On Wed, Sep 3, 2014 at 12:04 AM, Nick Dunmur <info@nickdunmur.com> wrote:
On 2 Sep 2014, at 14:55, Mark Stegman wrote:
There is a GUI for Argyll...
...only, AFAIK, for use as part of display colour management.
kind regards
Nick __________
dUNMUR | photographer info<at>nickdunmur.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Colorsync-users mailing list (Colorsync-users@lists.apple.com) Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/colorsync-users/mark.stegman%40gmail...
This email sent to mark.stegman@gmail.com
On 2 Sep 2014, at 15:24, Mark Stegman wrote:
DOH!
:-) Never mind - it works well as a GUI for that element of it. I haven't seen or heard of anything more comprehensive for people (like me) who are very much less command-line savvy. kind regards Nick __________ dUNMUR | photographer info<at>nickdunmur.com
participants (4)
-
Mark Stegman
-
Nick Dunmur
-
Peter Miles
-
Peter Miles