Re: create a "child" profile (-> Device Link Profile)
Re: create a "child" profile (-> Device Link Profile)
- Subject: Re: create a "child" profile (-> Device Link Profile)
- From: Henrik Holmegaard <email@hidden>
- Date: Sat, 17 Nov 2001 11:19:09 +0100
Rich Schwab <email@hidden> wrote:
I would like to find out if I can create a "child" profile from two "parent"
profiles. Taking a profile of something I want to simulate such as a press
or matchprint, then taking a profile of the given printer someone is using
and generate a third profile by combining the two that would be then applied
at the workstation during output in order to accurately simulate the first
device.
You are describing what is technically called a Device Link Profile.
A DLP has pros and cons covered in the on-line iQueue manual on
www.gretagmacbeth.com.
Among the cons is that a DLP may not be embedded and does not support
a return simulation transform to the profile connection space.
This means that a DLP is for the transformation into the final space only.
a. if you use it for RGB source to CMYK output, then you wind up with
untagged CMYK which you don't know what to do with,
b. if you use it for CMYK output space to CMYK proof space, then you
want to flush to data from the RIP anyway, so it doesn't matter that
what you wind up with is untagged CMYK.
Because a simulation transfrom back to the profile connection space
is not supported, applications like Photoshop that rely on monitor
previews don't support DLP's as a transform from the PCS to the
monitor space would be undefined.