GSoC CM collaboration

[Kai-Uwe Behrmann]

Am 04.03.08, 00:33 +1100 schrieb Graeme Gill:
> Kai-Uwe Behrmann wrote:
> > - a ICC profile container attached to window content
> 
> I don't thing that's a good approach, as it would necessitate
> incorporating the CMM deeply into things. Better to pass down
> a device link and leave the CMM higher up the stack. This
> then allows an open choice of CMM's and linking approaches
> (intents, smart linking, tuning etc), as well as supporting
> device links.

This brings the CMM into the applications and the rending backend. For 
what benefit? How does device link profile avoid the presence of a CMM 
down the path?
As well, when a user wants to be able to select globaly a certain CMM and 
his application opts in for colour management, as should be the default, 
then there will be CMM specifics down the path in any case.

> > In addition to this, then the application should be able to opt out for 
> > colour management down the rendering path.
> 
> Essential to allow for calibration and profiling.

Agreed. And not only. 
For instance it makes to bypass graphic gamma tables for preventing the 
LUTs in reducing tonal differenciation to otherwise fine grained 16-bit or 
HDR data.
 
> Graeme Gill.

kind regards
Kai-Uwe Behrmann
-- 
developing for colour management 
www.behrmann.name + www.oyranos.org