Hello, it looks like cmsTransform2DeviceLink() generated device linke profiles can not handle as many profile combinations like raw cmsHTRANSFORM can for unbound colour conversions of float images it at all. My impression is, that is in part because of there is no cmsSigDToB0Tag written out by the cmsTransform2DeviceLink() call. cmsTransform2DeviceLink() exports only a A2B0/mAB tag.
To overcome that, there come two directions to my mind: a: cmsTransform2DeviceLink() could obtain a new flag to write cmsSigDToB0Tag/mpet itself. Then the various parametric curve types could be converted as needed to the ICC mpet known types inside lcms. b: add an API to export cmsPipeline element from cmsHTRANSFORM. And users can add that after processing with cmsWriteTag() to the cmsTransform2DeviceLink() obtained profile. Anyway. It appears like using cmsTransform2DeviceLink() for unbound colour transforms needs some changes in lcms. What do you think? Which direction would you prefere? I would be glad to write a patch set. kind regards Kai-Uwe ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
