<html><body bgcolor="#FFFFFF"><div>Games likely need a passthrough.<br><br>On May 3, 2011, at 11:13 AM, Ann McCarthy <<a href="mailto:almccart@lexmark.com">almccart@lexmark.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>"We want to go with a explicite opt-out approach. All content shall be colour managed by default (typical sRGB). A robust mechanism<br>for disabling system colour management is a pre condition for that scheme to work."<br clear="all">
<div>Please can we avoid this idea that colour management can or should be "disabled."</div><div> </div><div>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. </div>
<div> </div><div>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.</div><div> </div>
<div>Best regards,</div>
<div>Ann L McCarthy</div>
<div>Imaging Systems R&D</div>
<div>Lexmark International, Inc.</div><br>
<br><br><div class="gmail_quote">On Mon, May 2, 2011 at 3:26 AM, Kai-Uwe Behrmann <span dir="ltr"><<a href="mailto:ku.b@gmx.de"><a href="mailto:ku.b@gmx.de">ku.b@gmx.de</a></a>></span> wrote:<br><blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;" class="gmail_quote">
Am 29.04.11, 15:20 -0600 schrieb Chris Murphy:<div class="im"><br>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;" class="gmail_quote">
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.<br>
<br>
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.<br>
</blockquote>
<br></div>
We want to go with a explicite opt-out approach. All content shall be colour managed by default (typical sRGB). A robust mechanism<br>
for disabling system colour management is a pre condition for that scheme to work.<div class="im"><br>
<br>
kind regards<br>
Kai-Uwe Behrmann<br>
-- <br>
developing for colour management <a href="http://www.behrmann.name" target="_blank"><a href="http://www.behrmann.name">www.behrmann.name</a></a> + <a href="http://www.oyranos.org" target="_blank"><a href="http://www.oyranos.org">www.oyranos.org</a></a><br>
<br>
_______________________________________________<br></div><div><div></div><div class="h5">
openicc mailing list<br>
<a href="mailto:openicc@lists.freedesktop.org" target="_blank"><a href="mailto:openicc@lists.freedesktop.org">openicc@lists.freedesktop.org</a></a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/openicc" target="_blank"><a href="http://lists.freedesktop.org/mailman/listinfo/openicc">http://lists.freedesktop.org/mailman/listinfo/openicc</a></a><br>
</div></div></blockquote></div><br>
</div></blockquote></body></html>