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 thought I'd just save a step > and do it all at once. Well that's an interesting idea, and I can't think of any reason why it shouldn't work - so when you say it seems to have no effect, what results are you expecting to see, and what are you actually getting? Unless your working space profile has a smaller gamut than that of your source image (or a different white point, and you're using absolute-colorimetric) then you wouldn't expect to see any significant change in the image. Oh - and it's worth verifying that you're providing the profiles in the right order - that trips up more than a few people! The first profile should be that of the image, the second should be that of the monitor, and the third should be that of the device being simulated - the working space in your case. > Should I be using cmsCreateMultipleProfileTransform() instead, or really > break it down into two separate transforms, one during load and one > during display? In theory any of the three should work. If you're keeping your source image in its native space and building a transform specifically for it, is there any special reason you don't want to transform directly from source -> monitor profiles? All the best, -- Alastair M. Robinson ------------------------------------------------------------------------- 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
