Humm... the respose to your question would be "build a 1-RGB devicelink", but at thatThe main reason is just that I want to be familair with LCMS API and to gain
point, and despite my answer may sound a bit dumb, why to use a CMM at all?
All the complexity of CMM is supposed to be used to make separations for real inks, and this implies a lot of factors from ink-limiting, gamut remapping, gray replacement and so. Hence, if you want 1-RGB why to go across all this overheat but simply do a 255 - component?. This will for sure be faster that going across the CMM.
The only situation this would make sense (in a color-managed world, of course) would be if you have a printer under windows and the driver is operating in RGB space, and you want to profile this printer in a pseudo-cmyk. But in such case, you would loose all black channel ... your best option is to profile it in RGB, IMHO.
Or am I missing something?
Regards,
Marti.
better understanding how things are actually working. The secondary reason is
to provide a generic API locally to the a set of classes in a framework.
eg. if profiles are missing, I'd expect buffer to be linearly transformed automatically
but it's certain that I'll use abstract class for that no matter if LCMS can actually do that
or not. (ie., I just want to know how to do it with LCMS)
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Lcms-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/lcms-user
