From: John G. <joh...@gm...> - 2010-09-14 20:17:55
|
Oh, I may be in luck. I didn't see the API in the lcms1 docs but I do see them in the lcms source. Ok, I'm off to code it! On Tue, Sep 14, 2010 at 11:51 AM, John Green <joh...@gm...>wrote: > That looks just about perfect. But, it is a lcms2 solution. I've tried > using LCMS2 but I'm crashing. (I know I have to fix that but I'm under a > tight deadline.) Is there an LCMS1 solution? It's a real shame, the proposed > solution is super elegant. > > And of course, Thanks! > > > On Sun, Sep 12, 2010 at 1:00 PM, <mar...@li...> wrote: > >> >> Hi, >> >> >> I would create a abstract profile consisting of a set of curves and place >>> that inbetweeen the src and dest ones. >>> src -> abstract -> dest >>> >> >> This is a good approach, and you can use the curves on the device space as >> well >> src -> dest -> curves >> >> Just use cmsCreateLinearizationDeviceLink() to create a profile with >> your curves, and then join all profiles together with >> cmsCreateMultiprofileTransform. It is fast and easy, and need not to >> worry on profile internals. >> >> Regards >> Marti >> > > |