RytisT wrote: ↑
Mon Feb 10, 2020 7:18 am
but clients sometimes send files with ISO Coated or Web Coated swop, and so on... so, I don't suppose DeviceLink will work if I'll have a different color space every time?
Ok so let's examine this in more detail. Imagine a customer sends in a PDF that has a Output Intent or an image that is tagged with a JapanColor2011Coated ICC profile. Looking at the ICC web site (http://www.color.org/registry/index.xalter
) that profile has a Maximum Ink Coverage of 350% and a K separation maximum of 80% and a TVI (Dot gain) of 14%
Now the really interesting thing (stay with me), is that Fogra 39 is not an ICC Profile. It's a data set, from which you can make an ICC Profile. ISO Coated v2 is a prime example (there are others). So there are actually many profiles that can be Fogra 39!
Take one as an example. The documentation for the ISO Coated v2 ECI profile says
The ECI offset profile ISOcoated_v2_eci.icc is based on the characterization dataset “FOGRA39L.txt” applicable to for the following
reference printing conditions according to the international standard ISO 12647-2:2004/ Amd 1:
The profile was generated using Heidelberg PrintOpen 5.2 with the following settings:
Black length 9 (starting point 10%)
Black width 10
Total dot area 330%
Maximum Black 95%
So this profile will color separate an image in a completely different way to the Japanese profile. Different Ink Coverage (330% instead of 350%), and different Max Black (95% vs 80%). The dot gain will also be different. So the actual color separations created by the profiles will be different.
So ideally after conversion, what you want is for the color separation attributes to match that of your target profile, but the image to still maintain the same visual appearance it had when you received it. That is what a Devicelink can give you.
The issue as you say is that you would need a Devicelink for every possible combination of potential source ICC profile to your target ICC profile.
There are tools that will do this. Alwan Color, GMG and Colorlogic can do this. They either build and cache Devicelinks on the fly when they get a profile combination they haven't seen before. Or they just have a hell of a lot of profiles.
It really depends how far you want to go with this.
If you do decide to go down this path you can then look at using Devicelinks for Ink Saving, which is another use for them.
Not just lowering tac, but replacing CMY with K based on Gray Balance to reduce the amount of colored ink needed to print the job.