[Openicc] Color Management for Ubuntu

[Ann McCarthy]

OK - that makes sense. This could be satisfied by allowing for an under the
hood application switch in which an app can choose performance rather than
color transform for display.  Sufficient?

Best regards,
Ann L McCarthy
Imaging Systems R&D
Lexmark International, Inc.



On Tue, May 3, 2011 at 2:47 PM, Chris Murphy <lists at colorremedies.com>wrote:

> Games likely need a passthrough.
>
>
> On May 3, 2011, at 11:13 AM, Ann McCarthy <almccart at lexmark.com> wrote:
>
> "We want to go with a explicite opt-out approach. All content shall be
> colour managed by default (typical sRGB). A robust mechanism
> for disabling system colour management is a pre condition for that scheme
> to work."
> Please can we avoid this idea that colour management can or should be
> "disabled."
>
> Definitely we need an explicit path for building profiles -- a control that
> says 'I am building a profile, printing/displaying a test chart' or
> something like that very obvious. This is a function that has to be part of
> a color managed system.  Depending on the device, whether it is a printer or
> a scanner or a display that is being profiled at the time, the processing
> path for that 'test chart' process should be configured differently. For
> example, when building a scanner profile -- you probably still want a good
> display profile to be used for viewing assessment of the scan result, you
> just don't want an existing scan profile to be used.
>
> When not building profiles, are there scenarios when users want to see
> uncorrected uncontrolled device behavior?  I cannot think of such scenarios.
> Please provide examples of such situations.
>
> Best regards,
> Ann L McCarthy
> Imaging Systems R&D
> Lexmark International, Inc.
>
>
>
> On Mon, May 2, 2011 at 3:26 AM, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
>
>> Am 29.04.11, 15:20 -0600 schrieb Chris Murphy:
>>
>>  I thought we were discussing this "how to" in the context of the CPD (I
>>> think I have that right-the common print dialog). And also within
>>> GhostScript.
>>>
>>> And also still unresolved is whether this is an opt-in color management
>>> in the print pipeline or opt-out. And I think to answer that we need to know
>>> the same thing for dispay compensation sonwe don't have a disconnect between
>>> display and print by default.
>>>
>>
>> We want to go with a explicite opt-out approach. All content shall be
>> colour managed by default (typical sRGB). A robust mechanism
>> for disabling system colour management is a pre condition for that scheme
>> to work.
>>
>>
>> kind regards
>> Kai-Uwe Behrmann
>> --
>> developing for colour management www.behrmann.name + www.oyranos.org
>>
>> _______________________________________________
>> openicc mailing list
>> openicc at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/openicc
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openicc/attachments/20110503/2fcc0639/attachment.html>