Re: Article on Photoshop CS4 and DeviceLink profile
Re: Article on Photoshop CS4 and DeviceLink profile
- Subject: Re: Article on Photoshop CS4 and DeviceLink profile
- From: Kai-Uwe Behrmann <email@hidden>
- Date: Thu, 4 Dec 2008 10:06:21 +0100 (CET)
Date: Wed, 03 Dec 2008 16:02:48 +0100
From: Koch Karl <email@hidden>
"When you select a rendering intent, where is it applied? On the way
from working space to PCS, on the way back, or in both directions? I
haven?t found out yet. If you want to apply the abstract profile on
the way from your working space to an output space, you need to
transform another time ? you lose flexibility and each transformation
costs image quality."
I'd say for a simple input to output colour space conversion the
A2B_rendering_intent -> B2A_rendering_intent tables would be selected by a
CMM. Correct? Whats the issue of deploying a following scheme(?):
A2B_rendering_intent -> A2B0_abstract -> B2A_rendering_intent
For a null abstract profile the result should be the same as for a direct
source to ouput rendering with the same intent.
In case the two rendering intents would be selectable separately, the
scheme would become the following (which I do not remember to have seen
anywhere, except for proofing):
A2B_rendering_intentA -> PCS
PCS -> B2A_rendering_intentB
For merging abstract profiles into editing to output device space
conversions I completely agree with you. Thats a good thing. E.g. any
application, which has on the fly "look" profile capabilities should have
this. But I do not see the relation to the rendering intent selection.
kind regards
Kai-Uwe Behrmann
--
developing for colour management
www.behrmann.name + www.oyranos.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden