Hi,
>That sounds correct. We soft proof to the screen what the resulting
>document would look like when printed to a proofer, taking the printer
>into account. The input space can be rgb, cmyk, grey, xyz, or Lab.
Ok, now I understand. This "double proofing" capability is not in the
LittleCM
On May 23, 2008, at 09:11:43, Kai-Uwe Behrmann wrote:
> Forgot to mention where to find this source file:
> http://cinepaint.cvs.sourceforge.net/cinepaint/cinepaint-project/cinepaint/app/cms.c?revision=1.42&view=markup&pathrev=MAIN
Yes, I did eventually find it the other day. But it doesn't real
Am 21.05.08, 20:57 +0200 schrieb Kai-Uwe Behrmann:
> If you want a chain like, you might want to look at CinePaint's sources as
> a living example:
>
> input[scanner,camera,image] profile ->
> manipulation/effects profile(s) ->
> simulation/proofing profile ->
> local output[printer,d
I'm still awaiting suggestions for correcting the problem described
below. Note that I've also tried using cmsCreateProofingTransform
rather than creating a 2nd device link profiles and then calling
cmsCreateMultiprofileTransform. Same result.
On May 21, 2008, at 09:57:40, Steve Mills wrote
