Hi,
>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.
Ok, now I understand. This "double proofing" capability is not in the
LittleCM
On May 23, 2008, at 09:11:43, Kai-Uwe Behrmann wrote:
> Forgot to mention where to find this source file:
> http://cinepaint.cvs.sourceforge.net/cinepaint/cinepaint-project/cinepaint/app/cms.c?revision=1.42&view=markup&pathrev=MAIN
Yes, I did eventually find it the other day. But it doesn't real
Am 21.05.08, 20:57 +0200 schrieb Kai-Uwe Behrmann:
> 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,d
I'm still awaiting suggestions for correcting the problem described
below. Note that I've also tried using cmsCreateProofingTransform
rather than creating a 2nd device link profiles and then calling
cmsCreateMultiprofileTransform. Same result.
On May 21, 2008, at 09:57:40, Steve Mills wrote
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
Pix.r,outPix.g,outPix.b);
}
return 0;
}
Isaac Case
Software Engineer
PCDT Color Workflow Team
Xerox Corporation
p 585.265.5472
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:lcms-user-
> [EMAIL PROTECTED] On Behalf Of Steve Mills
> Sent: Wednesday
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?
Xerox Corporation
p 585.265.5472
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:lcms-user-
> [EMAIL PROTECTED] On Behalf Of Steve Mills
> Sent: Wednesday, May 21, 2008 10:58 AM
> To: lcms-user lcms-user
> Subject: Re: [Lcms-user] Confused about cmsCreateMultiprofileTr
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
On vendredi 16 mai 2008, Steve Mills wrote:
> Well that certainly seems confusing, or at least it does when coming
> from the ColorSync world, and given the order of the parameters. So in
> this case, I'd provide the printer profile as the "prooferProfile" and
> the monitor profile as the "o
On May 16, 2008, at 09:56:46, Marti Maria wrote:
> So, it goes input -> Proofed device -> Output. You can call proofer
> to the
> output device if you prefer to do that.
> See my other post on multiprofile transforms for more details
Well that certainly seems confusing, or at least it does whe
for more details
Regards
Marti Maria
The littleCMS project
www.littlecms.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Mills
Sent: Friday, May 16, 2008 4:42 PM
To: lcms-user lcms-user
Subject: Re: [Lcms-user] Confused about cmsCreateMulti
On May 16, 2008, at 09:08:06, Frédéric wrote:
> From TUTORIAL.TXT file, you can read:
Ah, I didn't check there, since a "tutorial" is used to show one how
to use something, not to *explain* the API. That's what I'd expect
from a file named LCMSAPI.TXT.
I'm still looking for an answer about
Le 16/5/2008, "Steve Mills" <[EMAIL PROTECTED]> a écrit:
>Nobody has an answer for this? Supplying the cmsFLAGS_SOFTPROOFING
>flag doesn't make any difference in this respect, but then I don't
>fully understand (nor do the docs explain) why the
>cmsFLAGS_SOFTPROOFING flag needs to be given, when
On May 13, 2008, at 17:32:25, Steve Mills wrote:
> OK, so now I'm trying to use cmsCreateProofingTransform and am
> getting an error that the output format space does not match the
> output profile's space. I don't understand why it's checking the
> *output* profile's space against the outpu
Am 09.05.08, 16:12 +0200 schrieb Marti.Maria:
> Do you need proofer AND monitor combined? Why? If you really need 4 profiles
> (because abstract profiles, etc) you may consider using
> cmsTrasform2Devicelink, but I would not recommend to use that unless really
> needed, because may result in loss
On May 10, 2008, at 09:14:19, Marti.Maria wrote:
> Ok, that makes sense. However, this is not currently implemented in
> lcms.
> Only one intent is allowed in multiprofile transforms and two
> intents are allowed in proofing transforms.
> Of course you can do it by yourself, using low-level fu
reateProofingTransform works.
Hope this helps
All the best
Marti Maria
The littleCMS project
www.littlecms.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Mills
Sent: Friday, May 09, 2008 4:24 PM
To: lcms-user lcms-user
On May 9, 2008, at 09:12:54, Marti.Maria wrote:
>> The user can supply the intent between each profile.
>
> No. At least not in lcms cmsCreateMultiprofileTransform, which
> forces you a
> single intent.
> This is not intrinsically bad, as mixing intents makes no sense in
> all but
> softproofi
ge-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Mills
Sent: Friday, May 09, 2008 3:03 PM
To: lcms-user lcms-user
Subject: Re: [Lcms-user] Confused about cmsCreateMultiprofileTransform error
On May 9, 2008, at 02:18:26, Marti.Maria wrote:
> CreateMultiprofileTra
On May 8, 2008, at 19:15:12, Alastair M. Robinson wrote:
> Well, reading the API documentation for
> cmsCreateMultiprofileTransform(), I see:
> - Colorspaces must be paired with the exception of
> Lab/XYZ, that can be interchanged.
> So I guess that means you can't directly create an RGB
On May 9, 2008, at 02:18:26, Marti.Maria wrote:
> CreateMultiprofileTransform needs colorspaces to match between
> profiles.
> So, if you use
>
> Input, printer, monitor,
>
> You are connecting the profiles in this way:
>
> RGB -> Input -> Lab - > Printer -> CMYK -> *Monitor*
>
> When reaching t
Hi,
CreateMultiprofileTransform needs colorspaces to match between profiles.
So, if you use
Input, printer, monitor,
You are connecting the profiles in this way:
RGB -> Input -> Lab - > Printer -> CMYK -> *Monitor*
When reaching the monitor, space is CMYK and since the profile is RGB that
is
Hi,
>> In my first test after adding support for lcms, I'm getting
>> "cmsCreateMultiprofileTransform: ColorSpace mismatch" from line 1935
>> in cmsCreateMultiprofileTransform. I'm building the xform with the
>> same list of profiles as we would when using ColorSync (although
>> they're in cmsHPRO
On May 7, 2008, at 10:11:01, Steve Mills wrote:
> I'm in the midst of adding lcms support to our portable code. The Mac
> build already uses ColorSync, built on semiportable classes that the
> portable code can talk to. Our app is a page layout app. The user can
> choose the printer and proofer pr
27 matches
Mail list logo
