Am 21.05.08, 11:16 -0500 schrieb Steve Mills:
> On May 21, 2008, at 11:10:15, Case, Isaac wrote:
>
> > Sorry for coming in on this much later, but what exactly are you
> > trying
> > to do?
> >
> > It looks like you're trying to softproof what rgb prints from the
> > proofer would look like, if the proofer was emulating the printer.
> >
> > Is that correct?
>
>
> That sounds correct. We soft proof to the screen what the resulting
> document would look like when printed to a proofer, taking the printer
> into account. The input space can be rgb, cmyk, grey, xyz, or Lab.
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.
kind regards
Kai-Uwe Behrmann
--
developing for colour management
www.behrmann.name + www.oyranos.org
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/lcms-user
