Hi, Frédéric Mantegazza wrote:
> The *proof* device needs to be in RGB space, I agree, but not the > *destination* profile. Usually, proofing is done to see how a print image > will look like. So, it has sens to have a destination profile in CMYK > space. One thing I found when learning about proofing transforms was that I got very confused regarding which profile is the "proof" profile, and which is the "output" profile. Does "destination" refer to the device on which the image will ultimately be printed, or the device displaying the proof? Similarly, does "proof" refer to the device on which you're viewing the proof, or the device whose behaviour you're trying to proof? I wonder if you have them the wrong way round? "Destination" - i.e. the second profile supplied to cmsCreateProofingTransform() should be the monitor profile, and "proof", the third profile, should be that of the output device whose behaviour is being simulated. All the best, -- Alastair M. Robinson ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
