On May 21, 2008, at 12:16:16, Case, Isaac wrote:
> How is this different than what you're doing?
Because you're calling cmsCreateMultiprofileTransform with 4 profiles
with 1 rendering intent, and I'm calling it with 2 device link
profiles with possibly different intents between each of the 4
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[printe
I just made up a quick test to see if I understand how it works (where
p1 and p2 are two different cmyk profiles). Compiled and ran fine.
How is this different than what you're doing?
#include "lcms.h"
#include
typedef struct _RGB_ {
BYTE r,g,b;
} RGB;
int main()
{
cmsHPR
I dont remember exactly, but thought to have seen a API to select the
interpolator in Lcms, without touching the Lcms source code.
kind regards
Kai-Uwe Behrmann
--
developing for colour management
www.behrmann.name + www.oyranos.org
Am 20.05.08, 14:43 -0400 schrieb Case, Isaac:
> Never mind,
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
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?
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?
Isaac Case
Software Engineer
PCDT Color Workflow Team
Xerox Corpor
On May 8, 2008, at 19:15:12, Alastair M. Robinson wrote:
> What you probably could do is create the individual stages of your
> transform with cmsCreateTransform(), convert these transforms to
> DeviceLinks with cmsTransform2DeviceLink(), and then chain the
> devicelinks together using cmsCreateMu
