On May 21, 2008, at 13:57:10, Kai-Uwe Behrmann wrote: > 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,display] profile > > I have slightly changed the terminology to better fit what we do in > CinePaint. > > Look at app/cms.c:cms_create_transform() . > > I am about exporting the same functionality into the Oyranos library > for a > more straight forward API, even though the lcms API is already nice. > The default transform engine in the Oyranos CMS will be almost based > on > Lcms.
I changed my code to call cmsCreateProofingTransform as the last step instead of creating a 2nd device link profile and creating the final xform with cmsCreateMultiprofileTransform. But I still get the same error "Device link is operating on wrong colorspace on output". In IsProperColorSpace, Space is PT_RGB, lUsePCS is true, and hProfile's cms is PT_CMYK. IsProperColorSpace is being called from CreateDeviceLinkTransform(p- >InputProfile, p->OutputFormat, TRUE). I want to make sure there isn't a typo in the lcms code and that should be sending p- >OutputProfile instead. _________________________________________________________ Steve Mills Me: 952-401-6255 Senior Software Architect MultiAd [EMAIL PROTECTED] www.multi-ad.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
