> I tested lcms-internal and -external XYZ profiles. There is > an quality drawback with XYZ with lcms default settings.
Hi Kai-Uwe, I think the problem is that the precalculated device link uses only a n-dimensional CLUT table, but no input and output tables. However, finding optimal input and output tables (which e.g. make the CLUT grid as flat as possible, to minimize interpolation error) for the general case, i.e. for an arbitrarry profile chain is computationally expensive (you basically need to perform numerical optimization), and I guess, you're not happy either, if the accuracy is good, but if cmsCreateTransform() takes several minutes. Such an expensive computation would be acceptable for profile creation, but not at runtime, when a profile gets applied. I think, the only reasonable trade-off might be probably to use some heuristics for creating input and output tables for the device link. I've seen, that Marti has already implemented an optimization for RGB -> RGB transforms, which could be probably extended for XYZ. Marti? Regards, Gerhard -- Superg�nstige DSL-Tarife + WLAN-Router f�r 0,- EUR* Jetzt zu GMX wechseln und sparen http://www.gmx.net/de/go/dsl ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Lcms-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/lcms-user
