Re: Harlequin RIP Output Profile Problems
Re: Harlequin RIP Output Profile Problems
- Subject: Re: Harlequin RIP Output Profile Problems
- From: Glenn Kowalski <email@hidden>
- Date: Tue, 19 Dec 2000 10:09:31 -0500
Henrik Holmegaard wrote:
>I was going to see if a DeviceLink profile would do better since the
RIP accepts them, but the DL profile I created was 8 megs and I had
no way of transferring the file to the PC while I was there.
Use Steve Upton's ColorThink, the stuff you are using is obviously broken.
Yep, as Steve pointed out, I was using ColorThink. I'm going to try a
different CMM.
Be aware that if you feed PostScript pages into the device link, all
the objects on the page must be in the color space you chose as the
source when building the device link profile. Whether that color
space is ColorMatchRGB.ICC or MyGlossyPosISO.ICC doesn't matter, just
as long as it's the same for all objects.
Yep, I've already planned for this. The client is going to be working
in the color space of their Dupont Waterproof system.
I know the profiles are good because I can turn them off in the RIP
and do a Profile to Profile in Photoshop and then output to the Kodak
with good results.
There were (and are?) reports of problems with the implementation in
Harlequin RIPs. You should not color manage in the RIP, use an ICC
color server that encodes the device color specification, or
cross-render in a layout or other application that does this. Then
your results are reproducible across applications every time.
Using a color server was my intent (pun intended) from the beginning.
I'm going to be setting up ICC Autoflow. I was just hoping I could
get the RIP to behave because it's easier for the users from an
interface point of view. Trying to do it "right" might end up to just
be a waste of time if the Harlequin can't handle ICC profiles
correctly.
--
Glenn Kowalski
Macintosh Systems Consultant
Studio 405
www.studio405.com