Hi,
It seems ok. cmsCreateProofingTransform is a good choice to do that.
Make sure cmsFLAGS_SOFTPROOFING is specified, you can also use
jpegicc with -p option to check the functionality. On the other hand, if
all
input gamut is encompassed by the workspace, yous should see no difference.
Regar
Am 17.07.08, 07:57 -0500 schrieb Paul Miller:
> Okay, I'm not really trying to do proofing. I'm trying to do the image
> profile -> working space -> monitor space in one step. Technically, I
> should probably be doing file profile->working profile during load, then
> working -> monitor during di
Hi :)
Paul Miller wrote:
> Okay, I'm not really trying to do proofing. I'm trying to do the image
> profile -> working space -> monitor space in one step. Technically, I
> should probably be doing file profile->working profile during load, then
> working -> monitor during display, but I though
Mike Russell wrote:
> From: "Paul Miller" <[EMAIL PROTECTED]>
>
> [re proofing a working space profile]
>> That makes sense. So is what I'm trying to do "right", or should I be
>> using a different method?
>
> I can only think of one situation where what you are doing would make
> sense. If you
From: "Paul Miller" <[EMAIL PROTECTED]>
[re proofing a working space profile]
> That makes sense. So is what I'm trying to do "right", or should I be
> using a different method?
I can only think of one situation where what you are doing would make
sense. If you have one of the relatively new mon
Can someone tell me if I'm doing this workflow properly? When I use
cmsCreateProofingTransform, the "proof" transform doesn't seem to make
any difference.
I get the file profile from a JPEG file, the monitor profile from
CMGetSystemProfile(), and my working profile is selected from a list of
a
