Another "Traditional" Vendor
Another "Traditional" Vendor
- Subject: Another "Traditional" Vendor
- From: G BALLARD <email@hidden>
- Date: Wed, 06 Jun 2001 09:45:20 -0700
Greetings,
I am working on a write to communicate the CMS theory to a vendor who still
works a closed-shop workflow. He having problems with my Tiff (my Iris
proofs have no black, whites are all blown out, numbers confirm in PSD --
this is a good file).
Any editors who can make this better...welcome.
In an "Emulate PSD 4" workflow, a "traditional" analogy:
Photoshop 4 will assume that (my) 2.2 gamma Adobe RGB is in (your) 1.8 gamma
Monitor RGB, and will ignore the embedded file. That, in a nutshell, is
where the problem appears to be occurring.
Since device-independent RGB isn't handled properly by versions of Photoshop
prior to 5.0, the CMYK produced from an Adobe RGB file, in a "traditional"
workflow, will be misrepresented in that manner.
The obvious fix is to Save your PSD 4 CMYK settings as a Separation Table
(an .ast file), then load it in PSD 5x (CMYK SetUp>Tables>Load). Then do
the conversion. (Thank you Bruce Frazer, again.)
IN MY PREFERRED FIX (is this correct?):
Determine what ICC or Separation Table your SCANNER uses to to define its
CMYK for the Iris RIP.
With that scanner profile, PSD 6 can easily Convert my RGB right into that
scanner Profile (or whatever scanner uses) and your workflow will treat my
pixel file like it came directly from your scanner.
At that point, the embedding is no longer an issue -MY COLOR- is in your
native workflow.
In any ICC-savvy conversion -- a Separation Table or ICC profile is needed
for the proofing device used. How else would I get my color into CMYK,
accurately, without an appropriate CMYK SetUp for the specific paper, ink,
press combination?
This is why I provide vendors with my legacy RGB -- so there is only ONE
conversion -- conversions degrade color information.
I could deliver my pixels in "U.S. Web Coated (SWOP) 2" -- and cross my
fingers -- but I would expect you have more accurate Separation Tables and
ICCs for your specific output devices (your monitor, for example).
But that is a ColorSync (had to get that in there;) issue...
I thank you in advance for any help here.
G. BALLARD