Re: gamut compression sending quark to Lambda?
Re: gamut compression sending quark to Lambda?
- Subject: Re: gamut compression sending quark to Lambda?
- From: Henrik Holmegaard <email@hidden>
- Date: Sun, 19 Aug 2001 09:23:04 +0200
Any idea what happened to the gamut? Is there some sort of "merge"
program feeding the Lambda that is somehow the culprit? Or is it
Quark? Which colorspace and dpi is best for printing straight
photography on a Lambda?
Only QuarkXPress 4.11 will emit RGB PostScript. The RGB recipes are
robbed of their ICC profile color specification when QuarkXPress 4.11
translates its internal data structures into PostScript, because
PostScript does not support the ICC color space specification format.
If the Quark CMS 2.1 is not turned OFF, QuarkXPress 4.11 will only
emit CMYK PostScript. If the Quark CMS 2.1 is turned OFF, but
Printing Color is not set to Composite RGB, QuarkXPress will still
only emit CMYK PostScript (but the emitted CMYK will not be color
managed by your simulation and final output CMYK production profile,
but by the internal QuarkXPress 320% UCR RGB to CMYK conversion).
If your Lambda receives the emaciated, pale and flat 320% UCR
separation produced by the internal QuarkXPress conversion, it has to
convert that CMYK into RGB. Just as with QuarkXPress, color modes can
be converted color managed or with global defaults.
The most likely cause is that either your client or the Lambda
operator failed to set QuarkXPress up to emit the original RGB values
in its PostScript.
If you wish to check this, ask to have the client and the operator
independently print the file using the Acrobat PPD and the Virtual
Printer. Then distill the PostScript with 'Leave Colors Unchanged'
and check in Adobe InProduction. If you do not see the image listed
as 'deviceRGB', but it lists as 'deviceCMYK', then you have the cause.