summaryrefslogtreecommitdiff
path: root/doc/Environment.html
diff options
context:
space:
mode:
authorJörg Frings-Fürst <debian@jff-webhosting.net>2015-05-01 16:24:15 +0200
committerJörg Frings-Fürst <debian@jff-webhosting.net>2015-05-01 16:24:15 +0200
commita30ba67504ffd12c4db499adbb5ce47a7d1f6036 (patch)
tree9ae1a7e3849dda6bbb5c578232f6f2fa5b2e7e7e /doc/Environment.html
parent89e99e8a827859729729dfc92d74be4a8f96f1a4 (diff)
parent094535c010320967639e8e86f974d878e80baa72 (diff)
New release 1.7.0
Diffstat (limited to 'doc/Environment.html')
-rw-r--r--doc/Environment.html209
1 files changed, 175 insertions, 34 deletions
diff --git a/doc/Environment.html b/doc/Environment.html
index 66dbbe2..d02bf6c 100644
--- a/doc/Environment.html
+++ b/doc/Environment.html
@@ -2,9 +2,9 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
- charset=ISO-8859-1">
+ charset=windows-1252">
<meta http-equiv="content-type" content="text/html;
- charset=ISO-8859-1">
+ charset=windows-1252">
<meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I)
[Netscape]">
<title>Argyll Environment Variables</title>
@@ -15,7 +15,7 @@
</u></h2>
The following environment variables affect behaviour:<br>
<br>
- <span style="font-weight: bold;">ARGYLL_NOT_INTERACTIVE</span><br>
+ <span style="font-weight: bold;"><a name="ARGYLL_NOT_INTERACTIVE"></a>ARGYLL_NOT_INTERACTIVE</span><br>
<br>
<div style="margin-left: 40px;">Normally Argylls tools expect that
they are directly interacting with a user, and use a couple of
@@ -43,8 +43,25 @@
interactive mode.<br>
</div>
<span style="font-weight: bold;"></span><br>
- <span style="font-weight: bold;">ARGYLL_COLMTER_CAL_SPEC_SET</span><br>
- <span style="font-weight: bold;">ARGYLL_COLMTER_COR_MATRIX</span><br>
+ <b><a name="ARGYLL_3D_DISP_FORMAT"></a>ARGYLL_3D_DISP_FORMAT<br>
+ </b>
+ <blockquote>This overrides the default 3D visualisation file format
+ for tools such as <a href="iccgamut.html">iccgamut</a> or <a
+ href="viewgam.html">viewgam</a>. Set to<b> </b><b>VRML</b> or <b>X3D
+
+
+
+ </b>or <b>X3DOM</b>, which will result in <b>.wrl</b>, <b>.x3d</b>
+ and <b>.x3d.html</b> files respectively. See <a href="3dformat">3d
+
+
+
+ Viewing Format</a>.<br>
+ </blockquote>
+ <b><br>
+ </b> <span style="font-weight: bold;"><a
+ name="ARGYLL_COLMTER_CAL_SPEC_SET"></a>ARGYLL_COLMTER_CAL_SPEC_SET</span><br>
+ <span style="font-weight: bold;"><a name="ARGYLL_COLMTER_COR_MATRIX"></a>ARGYLL_COLMTER_COR_MATRIX</span><br>
<br>
<div style="margin-left: 40px;">Both of these can be used to set a
default <span style="font-weight: bold;">CCMX</span> or <span
@@ -56,31 +73,147 @@
<br>
</div>
<br>
- <span style="font-weight: bold;">ARGYLL_MIN_DISPLAY_UPDATE_DELAY_MS<br>
+ <span style="font-weight: bold;"><a
+ name="ARGYLL_MIN_DISPLAY_UPDATE_DELAY_MS"></a>ARGYLL_MIN_DISPLAY_UPDATE_DELAY_MS<br>
<br>
</span>
<div style="margin-left: 40px;"><span style="font-weight: bold;"><span
style="font-weight: bold;"><span style="font-weight: bold;"></span></span></span>Normally
- a delay of 200 msec is allowed between changing a patch color on a
- display, and reading the color with an instrument, although some
- instruments (ie. i1d3, i1pro, ColorMunki) will automatically
- measure and set an appropriate delay during instrument
- calibration. In rare situations this delay may not be sufficient
- (ie. some TV's with extensive image processing features turned
- on), and a larger delay can be set using the <span
- style="font-weight: bold;"><span style="font-weight: bold;"><span
- style="font-weight: bold;"></span></span></span>ARGYLL_MIN_DISPLAY_UPDATE_DELAY_MS
- environment variable, ie. ARGYLL_MIN_DISPLAY_UPDATE_DELAY_MS=400
- would set a 400 msec minimum delay.<br>
- </div>
- <span style="font-weight: bold;"><br>
- ARGYLL_IGNORE_XRANDR1_2<br>
- <br>
- </span>
+
+a
+
+
+
+ delay of 200 msec is allowed between changing a patch color in
+ software, and that change appearing in the displayed color itself.
+ For some instuments (ie. i1d3, i1pro, ColorMunki, Klein K10-A)
+ ArgyllCMS will automatically measure and set an appropriate update
+ delay during instrument calibration. In rare situations this delay
+ may not be sufficient (ie. some TV's with extensive image
+ processing features turned on), and a larger delay can be set
+ using the <span style="font-weight: bold;"><span
+ style="font-weight: bold;"><span style="font-weight: bold;"></span></span></span>ARGYLL_MIN_DISPLAY_UPDATE_DELAY_MS
+
+
+
+
+
+environment
+
+
+
+ variable, ie. ARGYLL_MIN_DISPLAY_UPDATE_DELAY_MS=400 would set a
+ 400 msec minimum delay.<br>
+ <span style="font-weight: bold;"><br>
+ </span></div>
+ <span style="font-weight: bold;"></span><span style="font-weight:
+ bold;"><span style="font-weight: bold;"><a
+ name="ARGYLL_DISPLAY_SETTLE_TIME_MULT"></a>ARGYLL_DISPLAY_SETTLE_TIME_MULT</span></span><br>
+ <blockquote> Normally the display technology type determines how
+ long is allowed between when a patch color change appears on the
+ display, and when that change has settled down, and as actually
+ complete within measurement tolerance. A CRT or Plasma display for
+ instance, can have quite a long settling delay due to the decay
+ characteristics of the phosphor used, while an LCD can also have a
+ noticeable settling delay due to the liquid crystal response time
+ and any response time enhancement circuitry. [ Instruments without
+ a display technology type selection such as spectrometers assume a
+ worst case.].<br>
+ The ARGYLL_DISPLAY_SETTLE_TIME_MULT environment variable allows
+ the rise and fall times of the model to be scaled to extend or
+ reduce the settling time. For instance,
+ ARGYLL_DISPLAY_SETTLE_TIME_MULT=2.0 would double the settling
+ time, while ARGYLL_DISPLAY_SETTLE_TIME_MULT=0.5 would halve it.<br>
+ </blockquote>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"><span
+ style="font-weight: bold;"><span style="font-weight: bold;"><span
+ style="font-weight: bold;"><span style="font-weight:
+ bold;"><span style="font-weight: bold;"><span
+ style="font-weight: bold;"><span style="font-weight:
+ bold;"><span style="font-weight: bold;"><span
+ style="font-weight: bold;"><span
+ style="font-weight: bold;"><a
+ name="ARGYLL_CREATE_WRONG_VON_KRIES_OUTPUT_CLASS_REL_WP"></a>ARGYLL_CREATE_WRONG_VON_KRIES_OUTPUT_CLASS_REL_WP<br>
+ </span></span></span></span></span></span></span></span></span></span></span></span>
+ <blockquote>By default ArgyllCMS uses the Bradford sharpened cone
+ Chromatic adaption matrix in adapting the measured, absolute
+ colorimetric test data to the <b>PCS</b> (Profile Connection
+ Space) relative colorimetric D50 white point for all profile
+ types. This makes the profile handling consistent with the widely
+ deployed (HP &amp; Microsoft) sRGB and AdobeRGB profiles, as well
+ as being recommended practice in modelling chromatic
+ adaption.&nbsp; The ICC profile format though, specifies the use
+ of a non-cone space XYZ adaptation (so called "Wrong Von Kries"
+ chromatic adaptation) [ ICC Specification<br>
+ ICC.1:2001-04 (ICCV2.4) Annex A, pp 66, equations A.1, A.2 &amp;
+ A.3 ], so ArgyllCMS profiles have a very slight incompatibility
+ with ICC profiles created strictly according to the ICC
+ specifications, depending on how close to white Output (i.e.
+ print) profiles media white is to the perfect diffuser. (Note that
+ CMM's that strictly follow the ICC specifications have much more
+ gross incompatibilities due to this, when dealing with the HP
+ &amp; Microsoft sRGB and AdobeRGB profiles.) By setting this
+ environment variable, Output (i.e. print) profiles will be created
+ that better conform to the ICC specification, and&nbsp; therefore
+ have better inter-interoperability with some other CMMs, at the
+ cost of poorer color behavior.<br>
+ See also the <a href="ArgyllCMS_arts_tag.html">ArgyllCMS 'arts'
+ tag</a>.<br>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"><span
+ style="font-weight: bold;"><span style="font-weight: bold;"><span
+ style="font-weight: bold;"><span style="font-weight:
+ bold;"></span></span></span></span></span></span></blockquote>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"><span
+ style="font-weight: bold;"><span style="font-weight: bold;"><span
+ style="font-weight: bold;"><span style="font-weight:
+ bold;"><span style="font-weight: bold;"><span
+ style="font-weight: bold;"><span style="font-weight:
+ bold;"><a
+ name="ARGYLL_CREATE_DISPLAY_PROFILE_WITH_CHAD"></a>ARGYLL_CREATE_DISPLAY_PROFILE_WITH_CHAD<br>
+ </span></span></span></span></span></span></span></span></span>
+ <blockquote>The ICC V2 format originally provided no clear mechanism
+ for Display profiles to use a modern chromatic adaptation
+ transform in dealing with the D65 white point of typical displays.
+ Profile makers ended up taking two different approaches :- one was
+ to use a Bradford chromatic transform for the media (display)
+ white to PCS D50 (this approach being used by the widely deployed
+ HP &amp; Microsoft sRGB and AdobeRGB profiles, as well as
+ ArgyllCMS profiles by default), and the other was to apply the
+ Bradford transform to the measurement data and then disable
+ Absolute Intent for display profiles by setting the
+ mediaWhitePoint tag to D50. The latter approach was supplemented
+ later on with the introduction of the ChromaticAdapation ('chad')
+ tag, but this did not restore the Absolute Colorimetric capability
+ to Display profiles. The latter approach has also been adopted
+ more formally in the ICC V4 specifications. To improve restore the
+ Absolute Intent for such profiles, ArgyllCMS will make use of the
+ 'chad' tag in such profiles when Absolute Colorimetric intent is
+ requested, but by default does not create such profiles. Setting
+ this environment variable causes it to create Display profiles in
+ the fashion dictated by the ICC V4 spec. :- setting the
+ mediaWhitePoint tag to D50 and storing the display media white to
+ D50 matrix in the 'chad' tag. (This approach has slightly poorer
+ accuracy for Absolute Intent than ArgyllCMS's default.) <br>
+ </blockquote>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"><span
+ style="font-weight: bold;"><a
+ name="ARGYLL_CCAST_DEFAULT_RECEIVER"></a>ARGYLL_CCAST_DEFAULT_RECEIVER<br>
+ </span></span></span>
+ <blockquote>By default the ChromeCast test patch source uses a
+ special receiver application that gets the test patch data
+ directly. By setting this environment variable to true, the
+ default Google ChromeCast receiver will be used, making use of a
+ local web server to provide the images. This is slower than the
+ special reciever, but can be used as a fallback.<br>
+ </blockquote>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"><span
+ style="font-weight: bold;"><a name="ARGYLL_IGNORE_XRANDR1_2"></a>ARGYLL_IGNORE_XRANDR1_2<br>
+ <br>
+ </span></span> </span>
<div style="margin-left: 40px;">On an X11 system, if this is <span
style="font-weight: bold;"></span>set (ie. set it to "yes"),
then the presence of the XRandR 1.2 extension will be ignored, and
@@ -89,37 +222,45 @@
implementations.<br>
<br>
</div>
- <span style="font-weight: bold;">ARGYLL_DISABLE_I1PRO2_DRIVER<br>
+ <span style="font-weight: bold;"><a
+ name="ARGYLL_DISABLE_I1PRO2_DRIVER"></a>ARGYLL_DISABLE_I1PRO2_DRIVER<br>
<br>
</span>
- <div style="margin-left: 40px;">There is now partial support for the
- Eye-One Pro Rev E (aka Eye-One Pro 2) instrument, but a Rev E can
- be operated in legacy mode if the environment variable
+ <div style="margin-left: 40px;">There is now support for most of the
+ the Eye-One Pro Rev E (aka Eye-One Pro 2) instrument features, but
+ a Rev E can be operated in legacy mode if the environment variable
ARGYLL_DISABLE_I1PRO2_DRIVER is set (ie. set it to "yes").<br>
</div>
<span style="font-weight: bold;"></span><br>
- <span style="font-weight: bold;">XDG_CACHE_HOME<br>
+ <span style="font-weight: bold;"><a name="XDG_CACHE_HOME"></a>XDG_CACHE_HOME<br>
<span style="font-weight: bold;"><br>
</span></span>
<div style="margin-left: 40px;">Argyll tries to follow the <a
href="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
- Base Directory Specification</a>, and uses the <span
+
+
+
+Base
+
+
+
+ Directory Specification</a>, and uses the <span
style="font-weight: bold;">XDG_CACHE_HOME</span> environment
- variable to place per instrument calibration information (Eye-One
- Pro and ColorMunki instruments).<br>
+ variable to place per instrument calibration information, and
+ .ccmx and .ccss files.<br>
</div>
<br>
- <span style="font-weight: bold;">XDG_CONFIG_DIRS<br>
- XDG_DATA_DIRS<span style="font-weight: bold;"><br>
+ <span style="font-weight: bold;"><a name="XDG_CONFIG_DIRS"></a>XDG_CONFIG_DIRS<br>
+ <a name="XDG_DATA_DIRS"></a>XDG_DATA_DIRS<span style="font-weight:
+ bold;"><br>
<span style="font-weight: bold;"></span></span></span><br>
<div style="margin-left: 40px;">On Unix type operating systems,
configuration and profiles for displays are placed relative to
these environment variables.<br>
</div>
- <br>
- &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp; <br>
+ &nbsp;&nbsp;&nbsp;&nbsp; &nbsp; <br>
<br>
See <a href="Performance.html">Performance Tuning</a> for other
variables.<br>