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 display, but I thought I'd just save a step > and do it all at once. > > Should I be using cmsCreateMultipleProfileTransform() instead, or really > break it down into two separate transforms, one during load and one > during display?
If you just want to display your images, there is no reason to proof them. A typical editing (working) colour space covers pretty all display colours. I'd guess someone will have less of a chance to see a difference, if a intermediate editing profile (proofing) was applied or not. Your source and editing working spaces are too large to make a difference compared to the display profile. In case there is a difference then thats bad. Then your editing profile should cover a larger gamut. It would be a completely different issue, if you try to simulate a cinema look with a proofing profile. That would make sense. kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
