diff options
Diffstat (limited to 'doc')
44 files changed, 12198 insertions, 4393 deletions
diff --git a/doc/3dformat.html b/doc/3dformat.html new file mode 100644 index 0000000..e60a432 --- /dev/null +++ b/doc/3dformat.html @@ -0,0 +1,109 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> + <head> + <title>3D viewing file format</title> + <meta http-equiv="content-type" content="text/html; + charset=windows-1252"> + <meta name="author" content="Graeme Gill"> + </head> + <body> + <h2><b>3D Viewing Format<br> + </b></h2> + Gamut and other 3D output visualisations can be created in one of 3 + formats:<br> + <br> + <b>VRML</b><br> + A legacy web 3D file format, using the <b>.wrl</b> + file extension.<br> + Either a standalone viewer of a web browser + plugin is needed to view the file.<br> + <br> + <b>X3D</b><br> + A current web 3D file format modeled after VRML, + using the <b>.x3d</b> file extension.<br> + Either a standalone viewer of a web browser + plugin is needed to view the file.<br> + <br> + <b>X3DOM</b><br> + An HTML file using a javascript viewer and an X3D + scene, using the <b>.x3d.html</b> file extension.<br> + Any web browser supporting javascript and WebGL + can be used to display this.<br> + <br> + By default ArgyllCMS tools will output VRML format, but the defaul + can be overridden by setting the environment variable<br> + <b>"ARGYLL_3D_DISP_FORMAT"</b> to <b>"VRML"</b>, <b>"X3D"</b> or <b>"X3DOM"</b><br> + <br> + Note that the X3DOM file has references to the x3dom.css and + x3dom.js support files in the same directory as the created + .x3d.html file, and the tools will create a copy of these files in + that directory if they don't exist. These two files must be copied + with the .x3d.html if it is moved somewhere else.<br> + <br> + To check if your browser supports X3DOM, try <a + href="http://www.x3dom.org/check/">this test page</a>.<br> + <br> + X3DOM navigation in Web browser:<br> + <p>"Examine" - default viewing mode, which can be<br> + re-activate this mode by pressing the "e" key.</p> + <table style="border-collapse:collapse" border="1" width="350px"> + <tbody> + <tr> + <th>Function</th> + <th>Mouse Button</th> + </tr> + </tbody><tbody> + <tr> + <td>Rotate</td> + <td>Left / Left + Shift</td> + </tr> + <tr> + <td>Pan</td> + <td>Mid / Left + Ctrl</td> + </tr> + <tr> + <td>Zoom</td> + <td>Right / Wheel / Left + Alt</td> + </tr> + <tr> + <td>Set center of rotation</td> + <td>Double-click left</td> + </tr> + </tbody> + </table> + <br> + <br> + <table style="border-collapse:collapse" border="1" width="350px"> + <thead><tr> + <th>Function</th> + <th>Key</th> + </tr> + </thead> + <tbody> + <tr> + <td>Reset view</td> + <td>r</td> + </tr> + <tr> + <td>Show all</td> + <td>a</td> + </tr> + <tr> + <td>Upright</td> + <td>u</td> + </tr> + </tbody> + </table> + <br> + <br> + <br> + <br> + <br> + <br> + <br> + <br> + <br> + <br> + <br> + </body> +</html> diff --git a/doc/ArgyllCMS_arts_tag.html b/doc/ArgyllCMS_arts_tag.html new file mode 100644 index 0000000..826aa30 --- /dev/null +++ b/doc/ArgyllCMS_arts_tag.html @@ -0,0 +1,165 @@ +<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en"> +<html> + <head> + <meta http-equiv="Content-Type" content="text/html; + charset=windows-1252"> + <meta http-equiv="content-type" content="text/html; + charset=windows-1252"> + <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I) + [Netscape]"> + <title>Argyll 'arts' ICC tag</title> + </head> + <body> + <br> + <h2> <u>ArgyllCMS's 'arts' (Absolute to media Relative Transform + Space matrix) ICC tag (V1.0)<br> + </u></h2> + ArgyllCMS uses a registered (private) ICC tag to solve a long + standing Display profile compatibility issue. <br> + <br> + Other CMM and profile creation providers are most welcome to + implement this tag to improve ICC profile color behavior and + interoperability.<br> + <h2>The problem</h2> + 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. V2 profile makers + ended up taking three different approaches :- <br> + <ol> + <li>Use a Bradford chromatic transform for the media (display) + white to PCS D50 conversion. This was used in creating the + widely deployed HP & Microsoft sRGB profile, as well as the + AdobeRGB profile. This provides a good chromatic adaptation, but + Absolute Colorimetric will have errors if the profile is used + with a CMM that implements the the ICC specified "Wrong Von + Kries" chromatic adaptation to map relative colorimetric back to + absolute colorimetric rather than using the Bradford transform + it was created with. <br> + </li> + <li>Use the ICC specified "Wrong Von Kries" chromatic transform + from D65 to D50. This leads to poor relative colorimetric + behavior (the most important case), but gives correct Absolute + Colorimetric behavior.<br> + </li> + <li>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, since the 'chad' tag is not + formally part of the specified mechanism for implementing + Absolute Colorimetric. Unfortunately, this approach has been + adopted in the ICC V4 specifications</li> + </ol> + The ICC standard "Wrong Von Kries" chromatic transform for media + white to/from PCS D50 has disadvantages in regard to color behavior + for Output (i.e. print) profiles as well as Display profiles though. + With most normal, white media this is not of great significance, + since the white point shift is small, but it grows in significance + as the color of the paper differs from white (i.e. tinted papers).<br> + <br> + For all these reasons, and in the pursuit of the best possible color + quality, ArgyllCMS uses the more color accurate Bradford chromatic + transform for all profiles types instead of the the ICC standard + "Wrong Von Kries" transform. This improves compatibility with the + (extremely common use case) of HP & Microsoft sRGB, and AdobeRGB + profiles where the color behavior of Bradford vs. "Wrong Von Kries" + is more critical; provides good color behavior for creating Display + profiles while giving accurate Absolute Colorimetric Intent + behavior; slightly improves the quality of Output profiles, most + noticeable with tinted stock, while having minimum incompatibility + with Output profiles created for normal, white printed media by + other profiling programs because the white point shift is typically + small. But to enable perfect compatibility of ArgyllCMS Output (i.e. + print) profiles with other CMM's, the default behavior can be + changed by using the <a +href="Environment.html#ARGYLL_CREATE_WRONG_VON_KRIES_OUTPUT_CLASS_REL_WP">ARGYLL_CREATE_WRONG_VON_KRIES_OUTPUT_CLASS_REL_WP</a> + environment variable.<br> + <br> + So the problem is that it is impossible to know for sure whether an + ArgyllCMS create profile, ICC V2 Display profile, or other ICC + profiles has used a Bradford or "Wrong Von Kries" chromatic + transform in computing Absolute to/from Relative white point + transform.<br> + <h2>The solution</h2> + The ArgyllCMS SigAbsToRelTransSpace 'arts' tag holds a 3x3 matrix in + the first 9 elements<sup>*</sup> of a SigS15Fixed16ArrayType in the + usual ICC order (i.e. the same element order as the + ChromaticAdaptationTag 'chad' tag). This matrix holds the Sharpened + Cone space transform that the Media White point to/from PCS D50 + chromatic Von Kries transform is computed in, rather than the "Wrong + Von Kries" transform specified by ICC.1:2001-04 (ICCV2.4) Annex A, + pp 66, equations A.1, A.2 & A.3. So by default ArgyllCMS will + write an 'arts' tag with the Bradford matrix in it: <br> + <blockquote> sig 'arts'<br> + type 'sf32'<br> + S15Fixed16Array:<br> + No. elements = 9<br> + 0: 0.89509583<br> + 1: 0.26640320<br> + 2: -0.16140747<br> + 3: -0.75019836<br> + 4: 1.71350098<br> + 5: 0.03669739<br> + 6: 0.03889465<br> + 7: -0.06849670<br> + 8: 1.02960205<br> + </blockquote> + In contrast, ICC standard behavior is the equivalent of a unit + matrix.<br> + <br> + [ Note that ArgyllCMS will write an 'arts' tag containing a Bradford + matrix even for Display profile written using the 'chad' tag where + the the MediaWhitePointTag is set to D50, representing the cone + space used in computing the 'chad' tag. (see <a + href="Environment.html#ARGYLL_CREATE_DISPLAY_PROFILE_WITH_CHAD">ARGYLL_CREATE_DISPLAY_PROFILE_WITH_CHAD</a>) + i.e. for Display profiles, the 'chad' tag is regarded as just an + alternate means of representing the true Media White Point. ]<br> + <br> + On reading a profile, ArgyllCMS uses the following logic to set its + Media white to/from PCS D50 chromatic transform:<br> + <br> + if 'arts' tag is present:<br> + use it to compute + absolute <-> media relative white point transform.<br> + else:<br> + if ArgyllCMS created + profile (ICC header Profile Creator signature = 'argl')<br> + or V2 Display + profile && Media W.P. != D50:<br> + + use Bradford matrix to compute absolute <-> media relative + white point transform.<br> + else:<br> + + use unity matrix to compute absolute <-> media relative white + point transform.<br> + <br> + The 'arts' tag need not be written if the profile contains no 'wtpt' + MediaWhitePointTag tag.<br> + <br> + This provides a safe level of backwards compatibility, together with + the elimination of all ambiguity when the 'arts' tag is present, + allowing CMM and profile creators to use the preferred Bradford (or + other Sharpened Cone) space for Von Kries chromatic adaptation of + the media white point to/from PCS D50.<br> + <h2>Conclusion</h2> + The 'arts' tag allows unambiguous use of the recommended Bradford + cone space transform in computing the Absolute Colorimetric (Media + Relative) to/from Relative Colorimetric (PCS D50) chromatic + transform in ICC profiles, while for the first time also providing + an unambiguously means of marking the use of the Bradford transform + in the very widely used standard sRGB and AdobeRGB colorspaces. If + widely adopted, the use of "Wrong Von Kries" chromatic transform in + ICC profiles could be safely abandoned.<br> + <br> + * If the SigS15Fixed16ArrayType has more than 9 elements, then just + the first 9 should be interpreted as a 3x3 matrix, and any elements + beyond that should be ignored.<br> + <br> + <br> + <br> + <br> + <br> + </body> +</html> diff --git a/doc/ArgyllDoc.html b/doc/ArgyllDoc.html index 98e730d..f7a0141 100644 --- a/doc/ArgyllDoc.html +++ b/doc/ArgyllDoc.html @@ -10,9 +10,9 @@ <title>Argyll Documentation Top</title>
</head>
<body>
- <h1> Argyll CMS documentation index (V1.6.3)<br>
+ <h1> Argyll CMS documentation index (V1.7.0)<br>
</h1>
- Date: 26th January 2014<br>
+ Date: 1st May 2015<br>
Author: Graeme Gill
<h2><u><a name="Intro"></a>Introduction</u></h2>
ArgyllCMS is an ICC compatible color management system, available as
@@ -29,21 +29,29 @@ wide selection of rendering intents. It also includes code for the
fastest portable 8 bit raster color conversion engine available
anywhere, as well as support for fast, fully accurate 16 bit
- conversion. Device color gamuts can also be viewed and compared
- using a VRML viewer. Comprehensive documentation is provided for
- each major tool, and a general guide to using the tools for typical
- color management tasks is also available. A mailing list provides
- support for more advanced usage.<br>
- <p>This is Version 1.6.3, a bug fix update to V1.6.2 released on 8th
- November 2013. The first public release of icclib was in November
- 1998, and of Argyll was in October 2000. Code development
- commenced in 1995. See <a href="ChangesSummary.html">Changes
- Summary</a> for an overview of changes since the last release.
- Changes between revisions is detailed in the <b>log.txt</b> file
- that accompanies the source code. </p>
+ conversion. Device color gamuts can also be viewed and compared with
+ a modern Web browser using X3DOM . Comprehensive documentation is
+ provided for each major tool, and a general guide to using the tools
+ for typical color management tasks is also available. A mailing list
+ provides support for more advanced usage.<br>
+ <p>This is Version 1.7.0, a feature and bug fix update to V1.6.3.
+ The first public release of icclib was in November 1998, and of
+ Argyll was in October 2000. Code development commenced in 1995.
+ See <a href="ChangesSummary.html">Changes Summary</a> for an
+ overview of changes since the last release. Changes between
+ revisions is detailed in the <b>log.txt</b> file that accompanies
+ the source code. </p>
<p>The latest source code is available from <a
href="http://www.argyllcms.com/">here</a>.<br>
</p>
+ <p><font color="#cc0000"><span style="font-weight: bold;">Please
+ note that instruments are being driven by ArgyllCMS drivers,
+ and that any problems or queries regarding instrument<br>
+ operation </span><span style="font-weight: bold;">should be
+ directed to the Argyll's author(s) or the Argyll mailing list,
+ and not to any</span> <span style="font-weight: bold;">other
+ party.</span></font> </p>
+ <p> </p>
<h2><a href="ColorManagement.html">An Introduction to Color
Management</a></h2>
<p>A great introduction for non technical people is Steve Upton's <a
@@ -65,6 +73,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + discussion</a> of what color management is, and why we need it,
together with a brief overview of the ICC profile format.<br>
@@ -131,9 +164,65 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - Tele-Spectro-Radiometer<br>
<br>
+ Klein:<br>
+ <br>
+ <a href="instruments.html#k10a">K10-A</a> + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ - Display Colorimeter. Reported also to work with
+ the K-1, K-8 and K-10.<br>
+ <br>
X-Rite:<br>
<a href="instruments.html#DTP20">DTP20 "Pulse"</a> @@ -197,6 +286,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - "swipe" type reflective spectrometer, that can be used untethered.<br>
<a href="instruments.html#DTP22">DTP22 Digital
@@ -261,6 +375,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - spot type reflective spectrometer.<br>
<a href="instruments.html#DTP41">DTP41</a> @@ -324,6 +463,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - spot and strip reading reflective spectrometer.<br>
<a href="instruments.html#DTP41">DTP41T</a>
@@ -389,6 +553,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - spot and strip reading reflective/transmissive spectrometer.<br>
<a href="instruments.html#dtp51">DTP51</a> @@ -452,6 +641,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - strip reading reflective colorimeter.<br>
<a href="instruments.html#DTP92">DTP92</a> @@ -515,6 +729,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - CRT display colorimeter.<br>
<a href="instruments.html#DTP94">DTP94</a> <font
@@ -639,6 +878,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - display colorimeter. (Treated as a Eye-One Display 2)<br>
<a href="instruments.html#i1d">CalMAN X2</a>
@@ -703,6 +967,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - display colorimeter. (Treated as a Eye-One Display 2)<br>
<a href="instruments.html#Huey">Huey</a>
@@ -776,6 +1065,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + [The Sequel Chroma 4 may also work.]<br>
<br>
@@ -841,6 +1155,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - see <a href="instruments.html#i1d">Eye-One Display</a><br>
<br>
@@ -911,6 +1250,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + [The Spyder 1 has also been reported as working, but this has not
been confirmed.]<br>
@@ -924,6 +1288,12 @@ - display colorimeter (Note
that the user must <a href="oeminst.html">supply</a> calibration
data)<br>
+ <a href="instruments.html#spyd5">Spyder 5</a>
+
+
+ - display colorimeter (Note
+ that the user must <a href="oeminst.html">supply</a> calibration
+ data)<br>
<br>
Other:<br>
<span class="titre"><a
@@ -988,6 +1358,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - display colorimeter</span><br>
<a href="instruments.html#ColorHug">ColorHug</a> @@ -1036,6 +1431,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + - display colorimeter<br>
<span style="font-weight: bold;"></span><span class="titre"><br>
@@ -1045,10 +1465,10 @@ Other instruments can be supported indirectly, since patch result
files created by other packages can be imported into Argyll.<br>
<br>
- Please <span style="font-weight: bold;">note</span> the <b><a
- href="Installing.html">installation instructions</a></b> for
- each platform - they contain important information for getting your
- instruments working.<br>
+ Please <span style="font-weight: bold;">note</span> the <big><b><a
+ href="Installing.html">installation instructions</a></b></big>
+ for each platform - they contain important information for getting
+ your instruments working.<br>
<p>If you've decided to buy a color instrument because Argyll
supports it, please let the dealer and manufacturer know that "<span
style="font-weight: bold;">You bought it because Argyll CMS
@@ -1074,26 +1494,39 @@ available to users interacting with them remotely through a
computer network, without providing the source code. Nothing other
than your agreement and compliance with the Affero GNU License
- grants you permission to use, modify or distribute Argyll source
- code, executables or its derivative works. You could be sued for
- copyright infringement if you use or distribute Argyll without a
- valid license. The <span style="font-weight: bold;">Affero GNU</span>
- license <span style="font-weight: bold;">prohibits</span>
+ grants you permission to use, modify or distribute ArgyllCMS
+ source code, executables or its derivative works. You could be
+ sued for copyright infringement if you use or distribute ArgyllCMS
+ without a valid license. The <span style="font-weight: bold;">Affero + + + + + + + + + + + + +
+ GNU</span> license <span style="font-weight: bold;">prohibits</span>
extending these tools<span style="font-weight: bold;"></span>
(i.e. by combining them with other programs or scripts that make
- use of, depend on, or work with the Argyll code) and distributing
- them, unless the all the elements of the extensions are also made
- available under a GPL compatible license. It is permissible to
- provide Argyll tools with other non GPL components if the elements
- of the package are not related, such that the packaging is mere
- aggregation. For all the gory details, please read the
- accompanying <a href="License.txt">license</a>. </p>
+ use of, depend on, or work with the ArgyllCMS code) and
+ distributing them, unless all the elements of the extensions are
+ also made available under a GPL compatible license. It is
+ permissible to provide ArgyllCMS tools with other non GPL
+ components if the elements of the package are not related, such
+ that the packaging is mere aggregation. For all the gory details,
+ please read the accompanying <a href="License.txt">license</a>. </p>
Note that unlike many commercial ICC profiling tools, the profiles
- created using Argyll, are not subject to any claims or restrictions
- of Argyll's author(s), but are assumed to be the copyright property
- of the person who gathers the characterization data, and causes the
- profiles to be created.
- <p>The Argyll CMS is Copyright 1995 - 2013 Graeme W. Gill, and is
+ created using ArgyllCMS, are not subject to any claims or
+ restrictions of ArgyllCMS's author(s), but are assumed to be the
+ copyright property of the person who gathers the characterization
+ data, and causes the profiles to be created.
+ <p>The ArgyllCMS is Copyright 1995 - 2015 Graeme W. Gill, and is
made available under the terms of the Affero GNU General Public
License Version 3, as detailed in the <a href="License.txt">License.txt</a>
file. Documentation is licensed under the terms of the GNU Free
@@ -1194,6 +1627,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + the jcnf library in <span style="font-weight: bold;">jcnf</span>/, @@ -1255,20 +1713,45 @@ + + + + + + + + + + + + + + + + + + + + + + + + + the files <span style="font-weight: bold;">spectro/xdg_bds.*</span>,
<span style="font-weight: bold;">spectro/aglob.*</span> and the
ucmm library in <span style="font-weight: bold;">ucmm</span>/ are
- Copyright 1995 - 2011 Graeme W. Gill, and available according to
+ Copyright 1995 - 2015 Graeme W. Gill, and available according to
the "MIT" license granted in the icc/License.txt and
cgats/License.txt files, and the licenses at the top of
ucmm/ucmm.c and jcnf/jcnf.c.<br>
</p>
<p>The yajl library in <span style="font-weight: bold;">jcnf/yajl</span>
- is Copyright 2007-2009, Lloyd Hilaiel and is licensed according to
- the Berkeley-style License granted in the jcnf/yajl/COPYING files.
- The yajl library has been repackaged and modified slightly for
- convenience.<br>
+ is Copyright (c) 2007-2014, Lloyd Hilaiel <me@lloyd.io> and
+ is used under an ISC License granted in the yajl/COPYING files.
+ The yajl library has been repackaged and modified slightly to adds
+ some features and for packaging and build convenience.<br>
</p>
<p> The TIFF library included in this distribution for convenience,
has its own copyright and license detailed in tiff/COPYRIGHT (an
@@ -1286,7 +1769,18 @@ the detailed copyright and licensing conditions.<br>
</p>
<p>The mongoose web server software is Copyright (c) 2004-2011
- Sergey Lyubka, and is licensed under an "MIT" license. </p>
+ Sergey Lyubka, and is licensed under an "MIT" license.<br>
+ </p>
+ <p>The axTLS library is Copyright (c) 2008, Cameron Rich, and the
+ license is detailed in ccast/axTLS/LICENSE file (an "MIT"/"BSD"
+ like license).<br>
+ It is not used for any security sensitive purpose, but is used
+ purely to communicate with the ChromeCast.<br>
+ </p>
+ <p>The <a href="http://www.x3dom.org/">X3DOM</a> x3dom.css and
+ x3dom.js files are Copyright (C) 2009 X3DOM and licensed dual
+ "MIT" and "GPL" license. See plot/X3DOM_LICENSE.txt.<br>
+ </p>
<h2><span style="text-decoration: underline; color: rgb(51, 0, 51);"><a
name="ProjType"></a>What sort of project is this ? (re:
contributions)<br>
@@ -1388,6 +1882,31 @@ calibration + + + + + + + + + + + + + + + + + + + + + + + + + and profiling is <a href="http://hoech.net/dispcalGUI/">dispcalGUI</a>
by Florian Höch. Others can be found with a suitable <a
@@ -1459,6 +1978,31 @@ href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&a + + + + + + + + + + + + + + + + + + + + + + + + + -? </b>(or some other unrecognized flag, if the "?" character is
treated specially in your shell, i.e. try "--" on OS X zsh).<br>
@@ -1537,6 +2081,31 @@ href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&a + + + + + + + + + + + + + + + + + + + + + + + + + Verbose mode<br>
-d
@@ -1601,6 +2170,31 @@ href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&a + + + + + + + + + + + + + + + + + + + + + + + + + Choose a depth 0-4<br>
-r
@@ -1665,6 +2259,31 @@ href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&a + + + + + + + + + + + + + + + + + + + + + + + + + Use a random depth<br>
-f
@@ -1732,6 +2351,31 @@ href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&a + + + + + + + + + + + + + + + + + + + + + + + + + Manual<br>
infile
@@ -1796,6 +2440,31 @@ href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&a + + + + + + + + + + + + + + + + + + + + + + + + + Input file<br>
outfile
@@ -1924,6 +2593,9 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> <br>
<a href="evalInputTargets.html">Evaluating input targets</a><br>
<br>
+ <a href="ArgyllCMS_arts_tag.html">ArgyllCMS's Absolute to media
+ Relative Transform Space matrix ('arts') ICC tag</a><br>
+ <br>
<h2><b><u><font><b><u><font size="+2"><a name="Flow"></a>Flow
diagram of Major Tools:</font></u></b></font></u></b></h2>
<br>
@@ -2008,6 +2680,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span><big>Generate a profiling test target values .ti1 file. </big><br
style="font-family: monospace;">
@@ -2073,6 +2770,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + film recorder TIFF files from Argyll .ti1 file. </big><br
style="font-family: monospace;">
@@ -2138,6 +2860,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a PS, EPS or TIFF file containing test patch values, ready for
printing.</big></small>
@@ -2205,6 +2952,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a test chart using an instrument to create a .ti3 data file.</big><span
style="font-family: monospace;"> </span><br style="font-family:
@@ -2271,6 +3043,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + and read colorimetric values from a display </big><br
style="font-family: monospace;">
@@ -2336,6 +3133,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + film colorimetric values using a SpectroScanT (Deprecated ?)</big><br
style="font-family: monospace;">
@@ -2401,6 +3223,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span><big>Convert a TIFF image of a test chart into .ti3
device values. <br>
@@ -2471,6 +3318,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + the reading of a device using an ICC or MPP profile. <br>
</big></small><small><a style="font-family: monospace;"
@@ -2540,6 +3412,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span><big>Convert Colorblind format CMY/RGB test chart into
Argyll .ti3 CGATS format. </big><br style="font-family:
@@ -2606,6 +3503,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Kodak Colorflow format CMYK test chart into Argyll .ti3 CGATS
format. </big><br style="font-family: monospace;">
@@ -2671,12 +3593,38 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + - </span><big>Convert Gretag/Logo/X-Rite or other format RGB or CMYK
- test chart results into Argyll .ti3 CGATS format. </big><br
- style="font-family: monospace;">
- <a style="font-family: monospace;" href="fakeCMY.html">fakeCMY</a><span
- style="font-family: monospace;"> + </span><big>Convert Gretag/Logo/X-Rite/Barbieri or other format
+ RGB or CMYK test chart results into Argyll .ti3 CGATS format. </big></small><br
+ style="font-family: monospace;">
+ <small><big><small><a style="font-family: monospace;"
+ href="ls2ti3.html">ls2ti3</a><span style="font-family:
+ monospace;"> </span><big>Convert @@ -2699,6 +3647,12 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> +
+ LightSpace format RGB .bcs test chart results into Argyll
+ .ti3 CGATS format.</big></small></big><br>
+ <a style="font-family: monospace;" href="fakeCMY.html">fakeCMY</a><span
+ style="font-family: monospace;"> + @@ -2737,12 +3691,6 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> -
- </span><big>Create a fake Argyll .ti3 CMY data file from a CMYK
- profile, as a basis of creating a CMY to CMYK separation<br>
- </big></small><small><a style="font-family: monospace;"
- href="average.html">average</a><span style="font-family:
- monospace;"> </span><big>Average @@ -2789,6 +3737,13 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> +
+ </span><big>Create a fake Argyll .ti3 CMY data file from a CMYK
+ profile, as a basis of creating a CMY to CMYK separation<br>
+ </big></small><small><a style="font-family: monospace;"
+ href="average.html">average</a><span style="font-family:
+ monospace;"> </span><big>Average + @@ -2803,7 +3758,8 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - / Merge two measurement data files</big></small><br>
+ or Merge two or more measurement data files, or average patches
+ within a single file.</big></small><br>
<h3>Creating Device Profiles</h3>
<small><a style="font-family: monospace;" href="colprof.html">colprof</a><span
style="font-family: monospace;"> @@ -2867,6 +3823,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Create an ICC profile from the .ti3 test data. <br>
<small><a style="font-family: monospace;" href="mppprof.html">mppprof</a><span
@@ -2931,6 +3912,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Create a Model Printer Profile (MPP) from the .ti3
test data. <br>
@@ -2996,6 +4002,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Regenerate a device profiles B2A table data by
inverting the A2B table.
@@ -3062,6 +4093,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Link two device ICC profiles to create a device
link profile.
@@ -3129,6 +4185,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Color convert a TIFF or JPEG file using a sequence
of ICC device, device link, abstract profiles and calibration files.
@@ -3194,6 +4275,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + calibration curves to an ICC profile.<br>
<small><a style="font-family: monospace;" href="icclu.html">icclu </a><span
@@ -3258,6 +4364,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Lookup individual color values through any ICC
profile table. <br>
@@ -3323,6 +4454,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Lookup individual color values forward or inverted
though an ICC profile or CAL table. <br>
@@ -3388,6 +4544,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Lookup individual color values though an MPP
profile. Also create MPP gamut files/views.<br>
@@ -3453,6 +4634,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a TIFF file to monochrome using an ICC device profile <br>
<h3>Color Tweaking tools<br>
@@ -3526,6 +4732,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a gamut file or VRML file of the color gamut of an ICC profile. <br>
<small><a style="font-family: monospace;" href="tiffgamut.html">tiffgamut</a><span
@@ -3590,6 +4821,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a gamut file or VRML file of the color gamut of a TIFF or JPEG
image. <br>
@@ -3655,6 +4911,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Convert one or more gamuts into a VRML 3D
visualization file. Compute an intersection.<br>
@@ -3722,6 +5003,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Dump the contents of an ICC profile as text. <br>
<small><a style="font-family: monospace;" href="profcheck.html">profcheck</a><span
@@ -3786,8 +5092,34 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + - an ICC profile against .ti3 test chart data. <br>
+ an ICC profile against .ti3 test chart data, create pruned .ti3
+ file.<br>
<small style="font-family: monospace;"><a href="invprofcheck.html">invprofcheck</a> @@ -3849,6 +5181,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </small>Check ICC forward against inverse lookup. <br>
<small><a style="font-family: monospace;" href="splitti3.html">splitsti3</a><span
@@ -3912,6 +5269,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a CGATS file (ie. a .ti3) into two parts randomly to verify
profiling. <br>
@@ -3980,6 +5362,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + an MPP profile against .ti3 test chart data. <br>
<small><a style="font-family: monospace;" href="spotread.html">spotread</a><span
@@ -4043,6 +5450,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + an instrument to read a single spot color value. <br>
<small><a style="font-family: monospace;" href="colverify.html">colverify</a><span
@@ -4050,6 +5482,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + matching of CIE in two CGATS/.ti3 files (also view differences as
VRML)<br>
@@ -4114,6 +5571,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a synthetic input, display or output calibration (<a
href="File_Formats.html#.cal">.cal</a>)file.
@@ -4179,6 +5661,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a Spectrometer to create a Colorimeter Correction Matrix
(CCMX) or a Colorimeter Calibration Spectral Set (CCSS)
@@ -4246,6 +5753,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + an embedded ICC profile from a TIFF or JPEG file.<br>
</small><small><a style="font-family: monospace;"
@@ -4316,14 +5848,39 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + or uninstall display profile, set display calibration from profile
or .cal file, test displace and dispwin access to a display.<br>
<small><a style=" font-family: monospace;" href="oeminst.html">oeminst</a><span
style="font-family: monospace;">
</span></small>Install Instrument manufacturers files for the
- Spyder 2, EDR or CCSS calibration files for i1d3 or Spyder 4,
- CCMX files for colorimeters.<br>
+ Spyder 2, EDR or CCSS calibration files for i1d3 or Spyder 4 or
+ 5, CCMX files for colorimeters.<br>
<small><a style="font-family: monospace;" href="specplot.html">specplot</a><span
style="font-family: monospace;"> </span><span
style="text-decoration: underline; font-family: monospace;"></span></small> @@ -4387,6 +5944,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Plot a spectrum (.sp, .cmf, .ccss) and calculate CCT and VCT.<br>
<small><a style="font-family: monospace;" href="spec2cie.html">spec2cie</a><span
@@ -4452,10 +6034,34 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + - spectral .ti3 readings into CIE XYZ or L*a*b* readings. Apply FWA,
- plot spectrums.<small><a style="font-family: monospace;"
- href="oeminst.html"></a></small><br>
+ reflective spectral .ti3 readings into CIE XYZ and D50 L*a*b*
+ readings. Apply FWA, plot spectrums.<br>
<h2><b><u><font size="+2"><a name="AlphList"></a>Main Tools
Alphabetic Listing:</font></u></b></h2>
@@ -4520,6 +6126,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + calibration curves to an ICC profile.<br>
<small><a style="font-family: monospace;" href="average.html">average</a><span
@@ -4584,8 +6215,34 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + - </span><big>Average / Merge two measurement data files</big></small><br>
+ </span></small><small><big>Average or Merge two or more
+ measurement data files, or average patches within a single file.</big></small><br>
<small><a style="font-family: monospace;" href="cb2ti3.html">cb2ti3</a><span
style="font-family: monospace;"> @@ -4648,6 +6305,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Convert Colorblind format CMY/RGB test chart into
Argyll .ti3 CGATS format. <br>
@@ -4713,6 +6395,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Color convert a TIFF or JPEG file using a sequence
of ICC device, device link, abstract profiles and calibration files.<br>
@@ -4777,6 +6484,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a Spectrometer to create a Colorimeter Correction Matrix
(CCMX) or a Colorimeter Calibration Spectral Set (CCSS)
@@ -4843,6 +6575,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a test chart using an instrument to create a .ti3 data file. <br>
<small><a style="font-family: monospace;" href="collink.html">collink</a><span
@@ -4907,6 +6664,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Link two device ICC profiles to create a device
link profile. <br>
@@ -4972,6 +6754,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Create an ICC profile from the .ti3 test data.<br>
<font size="-1"><a style="font-family: monospace;"
@@ -5037,6 +6844,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + matching of CIE in two CGATS/.ti3 files (also view differences as
VRML)<br>
@@ -5105,6 +6937,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + and read colorimetric values from a display <br>
<small><a style="font-family: monospace;" href="dispwin.html">dispwin</a><span
@@ -5170,6 +7027,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + or uninstall display profile, set display calibration from profile
or .cal file, test displace and dispwin access to a display.<br>
@@ -5236,6 +7118,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + an embedded ICC profile from a TIFF or JPEG file.<br>
</small><small><a style="font-family: monospace;"
@@ -5305,6 +7212,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Create a fake Argyll .ti3 CMY data file from a CMYK
profile, as a basis of creating a CMY to CMYK separation <br>
@@ -5370,6 +7302,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + the reading of a device using an ICC or MPP profile. <br>
<small><a style="font-family: monospace;" href="filmread.html">filmread</a><span
@@ -5434,6 +7391,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + film colorimetric values using a SpectroScanT (Deprecated ?)<br>
<small><a style="font-family: monospace;" href="filmtarg.html">filmtarg</a><span
@@ -5498,6 +7480,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + film recorder TIFF files from Argyll .ti1 file. <br>
<small><a style="font-family: monospace;" href="greytiff.html">greytiff</a><span
@@ -5562,6 +7569,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a TIFF file to monochrome using an ICC device profile <small><a
style="font-family: monospace;" href="oeminst.html"></a></small><br>
@@ -5627,6 +7659,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Dump the contents of an ICC profile as text. <br>
<small><a style="font-family: monospace;" href="iccgamut.html">iccgamut</a><span
@@ -5691,6 +7748,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a gamut file or VRML file of the color gamut of an ICC profile. <br>
<small><a style="font-family: monospace;" href="icclu.html">icclu </a><span
@@ -5755,6 +7837,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Lookup individual color values through any ICC
profile table. <br>
@@ -5819,6 +7926,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + an instrument to measure an illuminant spectrum, and estimate its UV
content.<br>
@@ -5887,9 +8019,125 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Kodak Colorflow format CMYK test chart into Argyll .ti3 CGATS
format. <br>
+ <small><big><small><a style="font-family: monospace;"
+ href="file:///D:/src/argyll/doc/ls2ti3.html">ls2ti3</a><span
+ style="font-family: monospace;"> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ </span><big>Convert LightSpace format RGB .bcs test chart
+ results into Argyll .ti3 CGATS format.</big></small></big></small><br>
<small><a style="font-family: monospace;" href="mppcheck.html">mppcheck</a><span
style="font-family: monospace;"> </span></small>Check @@ -5952,6 +8200,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + an MPP profile against .ti3 test chart data. <br>
<small><a style="font-family: monospace;" href="mpplu.html">mpplu</a><span
@@ -6016,6 +8289,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Lookup individual color values though an MPP
profile. Also create MPP gamut files/views. <br>
@@ -6081,14 +8379,39 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Create a Model Printer Profile (MPP) from the .ti3
test data. <br>
<small><a style=" font-family: monospace;" href="oeminst.html">oeminst</a><span
style="font-family: monospace;">
</span></small>Install Instrument manufacturers files for the
- Spyder 2, EDR or CCSS calibration files for i1d3 or Spyder 4,
- CCMX files for colorimeters.<br>
+ Spyder 2, EDR or CCSS calibration files for i1d3 or Spyder 4 or
+ 5, CCMX files for colorimeters.<br>
<small><a style="font-family: monospace;" href="printcal.html">printcal</a><span
style="font-family: monospace;"> </span></small>Create @@ -6150,6 +8473,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a printer calibration .cal file from a .ti3 data file<small><big>.</big></small><br>
<small><a style="font-family: monospace;" href="printtarg.html">printtarg</a><span
@@ -6214,6 +8562,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a PS, EPS or TIFF file containing test patch values, ready for
printing.</big></small><br>
@@ -6279,8 +8652,34 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + - an ICC profile against .ti3 test chart data. <br>
+ an ICC profile against .ti3 test chart data, create pruned .ti3
+ file.<br>
<small><a style="font-family: monospace;" href="refine.html">refine</a><span
style="font-family: monospace;">
</span></small>Creates an
@@ -6348,6 +8747,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Regenerate a device profiles B2A table data by
inverting the A2B table. <br>
@@ -6413,6 +8837,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Convert a TIFF image of a test chart into
.ti3 device values. <br>
@@ -6479,9 +8928,34 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + - spectral .ti3 readings into CIE XYZ or L*a*b* readings. Apply FWA,
- plot spectrums.<br>
+ reflective spectral .ti3 readings into CIE XYZ and D50 L*a*b*
+ readings. Apply FWA, plot spectrums.<br>
<small><a style="font-family: monospace;" href="specplot.html">specplot</a><span
style="font-family: monospace;"> </span><span
style="text-decoration: underline; font-family: monospace;"></span></small> @@ -6545,6 +9019,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Plot a spectrum (.sp, .cmf, .ccss) and calculate CCT and VCT.<br>
<small><a style="font-family: monospace;" href="splitti3.html">splitsti3</a><span
@@ -6608,6 +9107,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a CGATS file (ie. a .ti3) into two parts randomly to verify
profiling. <br>
@@ -6672,6 +9196,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + an instrument to read a single spot color value. <small><a
style="font-family: monospace;" href="oeminst.html"></a></small><br>
@@ -6736,6 +9285,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a synthetic input, display or output calibration (<a
href="File_Formats.html#.cal">.cal</a>)file.<br>
@@ -6801,6 +9375,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + the reading of a device using a synthetic device model. </big></small><br>
<small><a style="font-family: monospace;" href="targen.html">targen</a><span
@@ -6865,6 +9464,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Generate a profiling test target values .ti1 file.
<br>
@@ -6930,6 +9554,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + a gamut file or VRML file of the color gamut of a TIFF or JPEG
image. <br>
@@ -6999,10 +9648,35 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + - </span></small><small><big>Convert Gretag/Logo/X-Rite or other
- format RGB or CMYK test chart results into Argyll .ti3 CGATS
- format.</big></small> <br>
+ </span></small><small><big>Convert Gretag/Logo/X-Rite/Barbieri or
+ other format RGB or CMYK test chart results into Argyll .ti3
+ CGATS format.</big></small> <br>
<font size="-1"><a style="font-family: monospace;"
href="viewgam.html">viewgam</a><span style="font-family:
monospace;"> </span></font>Convert @@ -7065,6 +9739,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + one or more gamuts into a VRML 3D visualization file. Compute an
intersection.<br>
@@ -7130,6 +9829,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + </span></small>Lookup individual color values forward or inverted
though an ICC profile or CAL table. <br>
@@ -7222,6 +9946,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Device test values <br>
<a href="File_Formats.html#.ti2">.ti2</a> @@ -7285,6 +10034,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Device test values & chart layout <br>
<a href="File_Formats.html#.ti3">.ti3</a> @@ -7348,6 +10122,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Device test values & CIE tristimulus/spectral results <a
href="ti3_format.html">Format details.</a><br>
@@ -7415,6 +10214,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Test chart recognition template. <a href="cht_format.html">Format
details.</a> <br>
@@ -7479,6 +10303,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + 3D gamut surface description <br>
<a href="File_Formats.html#.sp">.sp</a> @@ -7542,6 +10391,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Illuminant spectral description <br>
<a href="File_Formats.html#.cmf">.cmf</a>
@@ -7613,6 +10487,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Standard text based data exchange format <br>
<a href="File_Formats.html#ICC">ICC</a> @@ -7676,6 +10575,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + International Color Consortium profile format <br>
<a href="File_Formats.html#MPP">MPP</a> @@ -7739,6 +10663,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Model device profile format <br>
<a href="File_Formats.html#TIFF">TIFF</a> @@ -7802,6 +10751,31 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Tag Image File Format raster files. <br>
<a href="File_Formats.html#JPEG">JPEG</a> @@ -7865,9 +10839,38 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Joint Photographic Experts Group, JPEG File Interchange Format
raster files. <br>
+ <a href="file:///D:/src/argyll/doc/ucmm.html">ucmm</a>
+ Unix micro Color Management Module convention and
+ configuration file format and <span style="color: rgb(204, 0, 0);
+ font-weight: bold;">Profile Locations</span>.<br>
<a href="File_Formats.html#VRML">VRML</a> @@ -7929,13 +10932,39 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> + + + + + + + + + + + + + + + + + + + + + + + + + Virtual Reality Modelling Language 3D file format. <br>
+ <a href="File_Formats.html#X3D">X3D</a>
+ Open
+ standards file format to represent 3D scenes using XML.<br>
+ <a href="File_Formats.html#X3DOM">X3DOM</a>
+ Open-source framework and runtime for 3D graphics on the Web.<br>
<br>
- <a href="ucmm.html">ucmm</a> Unix micro
- Color Management Module convention and configuration file format and
- <span style="color: rgb(204, 0, 0); font-weight: bold;">Profile
- Locations</span>.<br>
<h2><u>Errors, Corrections and Omissions:</u></h2>
<script language="JavaScript">
@@ -7965,6 +10994,6 @@ document.write("<a href=" + v6 + ">" + "Let me know" + "</a>") </script> If you notice any errors, corrections needed or omissions in
the current documentation, please contact the author.<br>
<br>
-
+ <br>
</body>
</html>
diff --git a/doc/CMP_Digital_Target-3.jpg b/doc/CMP_Digital_Target-3.jpg Binary files differdeleted file mode 100644 index b6502d5..0000000 --- a/doc/CMP_Digital_Target-3.jpg +++ /dev/null diff --git a/doc/CMP_Digital_Target-4.jpg b/doc/CMP_Digital_Target-4.jpg Binary files differnew file mode 100644 index 0000000..f8cb7a9 --- /dev/null +++ b/doc/CMP_Digital_Target-4.jpg diff --git a/doc/ChangesSummary.html b/doc/ChangesSummary.html index 82d083f..d0eee96 100644 --- a/doc/ChangesSummary.html +++ b/doc/ChangesSummary.html @@ -16,6 +16,53 @@ <h1> Summary of Argyll CMS Changes since last release</h1> <h3>For a <span style="text-decoration: underline;">complete</span> and more detailed list of changes, please see the log.txt file.</h3> + <h1>[V1.6.3 -> V1.7.0] 1st May 2015</h1> + <ul> + <li>Improved gamut mapping to reduce unnecessary changes to less + saturated colors such as skin tones.</li> + <li>Add support for DataColor Spyder 5.</li> + <li>Add support for ColorHug2 colorimeter.</li> + <li>Add support for Klein K10-A colorimeter.</li> + <li>Added Google ChromeCast as a test patch generator for Video + displays.</li> + <li>Added ls2ti3 tool to convert LightSpace .bcs files to .ti3.</li> + <li>Added IRIDAS .cube 3DLut format support to collink.</li> + <li>Add X3D and X3DOM support as an alternative to VRML, and make + X3DOM the default.</li> + <li>Add better cross compatibility with non-Argyll ICC profiles + using ArgyllCMS 'arts' tag to mark 'wtpt' Absolute Colorimetric + chromaticity transform, as well as implement proper absolute + colorimetric intent for Display profiles use the 'chad' tag. + Note that the standard ICC profiles provided by ArgyllCMS in the + ref directory (such as sRGB etc.) now include an 'arts' tag.</li> + <li>Ignore any patches that have zero values for creating Display + profiles, unless they are for device zero. </li> + <li>Fix various instrument communications problems for JETI + specbos, DTP20, DTP92 & DTP94.</li> + <li>Fix gestaltSystemVersion warning on OS X 10.10.</li> + <li>Fix very major bug in illumread. It wasn't actually working at + all since V1.4.0.</li> + <li>Added collink -I[gG][:p.p]:x.x options that allows an output + offset gamma curve be targetted instead of BT1886.</li> + <li>Added dispcal and collink -b black point hack. This forces the + input zero to map to the output zero for well behaved displays, + reducing dependence on the instrument accuracy for a very dark + black point.</li> + <li>Added preset list of display techologies to select from in + ccxxmake.</li> + <li>Added a -P prune option to profcheck, that creates a .ti3 file + pruned of any patches that have a delta E fit error greater than + a threshold. This may be of use in eliminating bad reading + values from a measurement set.</li> + <li>Added histogram plot option -h to both profcheck and verify.</li> + <li>Added a dispread & fakeread -Z option to set the number of + bits to quantize the test values to. </li> + <li>Fixed bug in targen - the -V dark emphasis wasn't being + applied to OFPS generated points.</li> + <li>Make sure that if an instrument display reading is interrupted + by a forced calibration, that the user is asked to place it back + on the display before resuming the measurements.</li> + </ul> <h1>[V1.6.2 -> V1.6.3] 26th January 2014</h1> <ul> <li>Added ProPhoto.icm and ProPhotoLin.icm to ref profiles.</li> @@ -874,6 +921,9 @@ + + + </span>for systems with > 3Gig Ram.</li> <li>Add support for the Eye-One Monitor spectrometer.</li> <li>Added -L option to <span style="font-weight: bold;">printtarg</span> @@ -907,6 +957,9 @@ + + + and memory usage issues.</li> <li>Fixed issues with Eye-One Pro Rev B timeouts.</li> <li>Added new option to collink -fk, that forces 000K input to K diff --git a/doc/ColorManagement.html b/doc/ColorManagement.html index 50505cd..3adcbe8 100644 --- a/doc/ColorManagement.html +++ b/doc/ColorManagement.html @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> - <meta content="text/html; charset=ISO-8859-1" + <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <title>Color Management</title> <meta content="Graeme W. Gill" name="author"> @@ -30,8 +30,8 @@ with the interaction of human vision and devices, allowing for such fundamental vision characteristics as white point adaptation and other phenomena. It should also allow the human end purposes to - influence the choice between tradeoffs in dealing with - practical device limitations.<br> + influence the choice of tradeoffs in dealing with practical + device limitations.<br> <br> The key means of implementing color management is to have a way of relating what we see, to the numbers that each device uses to @@ -40,13 +40,14 @@ The human eye is known to have 3 type of receptors responsible for color vision, the long, medium and short wavelength receptors. Because there are 3 receptors, human color perception is a 3 - dimensional phenomena, and therefore at least 3 channels are - necessary when communicating color information. Any device capable - of sensing or reproducing color must therefore have at least 3 - channels, and any numerical representation of a full range of colors - must have at least 3 components and hence may be interpreted as a - point in a 3 dimensional space. Such a representation is referred to - as a <span style="font-weight: bold;">Color Space</span>. <br> + dimensional phenomena, and therefore at least 3 information channels + are necessary when communicating color information. Any device + capable of sensing or reproducing color must therefore have at least + 3 channels, and any numerical representation of a full range of + colors must have at least 3 components and hence may be interpreted + as a point in a 3 dimensional space. Such a representation is + referred to as a <span style="font-weight: bold;">Color Space</span>. + <br> <br> Typically color capture and output devices expose their native color spaces in their hardware interfaces. The native color space is @@ -69,13 +70,13 @@ style="font-weight: bold;">CMYK</span>). This is because a Cyan filters out Red wavelengths, Magenta filters out Green wavelengths, and Yellow filters out Blue wavelengths, allowing these colorants to - independently control how much RGB is emitted. Because it's - impossible to make filters that perfectly block C, M or Y - wavelengths without overlapping each other, C+M+Y filters together - tend to let some light through, making for an imperfect black. - Augmenting with an additional Black filter allows improving Black, - but the extra channel greatly complicates the choice of values to - create any particular color. <br> + independently control how much RGB is reflected or transmitted. + Because it's impossible to make filters that perfectly block C, M or + Y wavelengths without overlapping each other, C+M+Y filters together + tend to let some light from broadband light sources through, making + for an imperfect black. Augmenting with an additional Black filter + allows improving Black, but the extra channel greatly complicates + the choice of colorant values to create any particular color. <br> <br> Many color devices have mechanisms for changing the way they respond to or reproduce color, and such features are called <span @@ -133,9 +134,8 @@ style="font-weight: bold;">Named</span> profiles represent color <span style="text-decoration: underline;">anchor points</span>. <span style="font-weight: bold;">Device Link</span> and <span - style="font-weight: bold;">Abstract</span> profiles represent <span - style="text-decoration: underline;">journeys</span> between anchor - points.<br> + style="font-weight: bold;">Abstract</span> profiles represent <u>connections</u> + or journeys between anchor points.<br> <br> <span style="font-weight: bold;">Device</span><br> <br> @@ -184,9 +184,8 @@ Two basic models can be used in ICC profiles, a <span style="font-weight: bold;">Matrix/shaper</span> model and a <span style="font-weight: bold;">cLUT</span> (Color Lookup Table) model. - Models often contain several optional processing elements that are - applied one after the other in order to provide an overall - transformation. <br> + Models often contain several processing elements that are applied + one after the other in order to provide an overall transformation. <br> <br> The Matrix/Shaper model consists of a set of per channel lookup curves followed by a 3x3 matrix. The curves may be defined as a @@ -234,8 +233,8 @@ common white point (D50), to facilitate ease of matching colors amongst devices with different white points. Other viewing condition effects (ie. image luminance level, viewing surround luminance and - flare/glare) can be modeled using (for example) using CIECAM02 to - modify XYZ values.<br> + flare/glare) can be modeled using (for example) CIECAM02 to modify + XYZ values.<br> <br> Another limitation relates to spectral assumptions. CIE XYZ uses a Standard Observer to convert spectral light values into XYZ values, diff --git a/doc/Compiling.html b/doc/Compiling.html index b4fcd7c..942e15e 100644 --- a/doc/Compiling.html +++ b/doc/Compiling.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 Compiling</title> @@ -35,7 +35,7 @@ X.Org X11 libXinerama development package<br> X.Org X11 libXrandr development package<br> X.Org X11 libXScrnSaver A.K.A. libxss-dev - development package + development package<br> <h5><span style="text-decoration: underline;">Setup JAM:</span><br> </h5> Argyll makes use of a build system called <a @@ -90,7 +90,11 @@ setup a jam shell script to invoke it something like this: "ajam -f~/src/argyll/Jambase $*", and to make sure that my script is ahead of Apples jam in my $PATH. The makeall.ksh script or - Makefile will run Jam with the -f flag.</p> + Makefile will run Jam with the -f flag.<br> + </p> + <p>Also on Linux and OSX you may have to make sure that certain + environment variables such as <b>HOSTTYPE</b> are exported, so + that other programs can see them.</p> <p>You may also have to set the appropriate environment variable to tell the Jambase which compiler you are using.<br> </p> @@ -111,7 +115,8 @@ remove everything that has been built, run <span style="font-weight: bold;">jam clean</span>. On Linux/OS X you could also just try running make, and the makefile will invoke - jam.<br> + jam, or the makeall.ksh shell script file or the makeall.bat file + can be used to invoke jam.<br> </p> <p>Something to watch on the Intel versions of OS X 10.4, is that your shell environment variable $MACHTYPE may be incorrect. On @@ -149,22 +154,25 @@ latter SDK to be able to incorporate the necessary function calls to access display and color profiles on Win2K and latter, so this may not work "out of the box".</p> - <p>I've also successfully compiled using Microsoft VC++ 8.0 and VC++ - 9.0 Express (the free Microsoft compiler) plus the Microsoft - Platform SDK February 2008. To get this to work though, I had to - create my own batch file to setup the SDK environment variables <span - style="font-weight: bold;">MSSdk</span> etc., because the batch - files provided with the SDK got confused by the presence of VC++6, - and didn't notice that VC++8 or 9 was configured.</p> + <p>I've also successfully compiled using Microsoft VC++ 8.0, VC++ + 9.0 and VC++ 10.0 Express (the free Microsoft compiler) plus the + Microsoft Platform SDK February 2008. To get this to work though, + I had to create my own batch file to setup the SDK environment + variables <span style="font-weight: bold;">MSSdk</span> etc., + because the batch files provided with the SDK got confused by the + presence of VC++6, and didn't notice that VC++8, 9 or 10 was + configured.</p> <p>Note that for some hard to fathom reason VC++ 9.0 refused to install on my Win2K development machine, so I had to install it on a WinXP machine and then copy the installation back to Win2K, and manually complete the installation. There seems to be no reason for this limitation, since the VC++9 compiler/linker etc. seems quite happy to run on Win2K.</p> - <p>I haven't attempted to compile for Win64, and currently the - Jambase isn't setup for cross compilation, nor have I tried to - setup a native build environment yet on Vista64.<br> + <p>I have succeeded in cross compiling for Win64 using + x86_64-w64-mingw32-gcc, but currently the Jambase isn't setup for + cross compilation and I used a hack to build the native + executables with a native compiler before invoking the usual Jam + compilation in the cross environment.<br> </p> </body> </html> 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 & Microsoft) sRGB and AdobeRGB profiles, as well + as being recommended practice in modelling chromatic + adaption. 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 & + 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 + & 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 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 & 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> - <br> + <br> <br> See <a href="Performance.html">Performance Tuning</a> for other variables.<br> diff --git a/doc/FWA.html b/doc/FWA.html index c1d4c6d..c6b1f4b 100644 --- a/doc/FWA.html +++ b/doc/FWA.html @@ -3,7 +3,7 @@ <head> <title>Fluorescent Whitener Additive Compensation</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> </head> <body> <h2><u>Fluorescent Whitener Additive Compensation (FWA Compensation)</u></h2> @@ -179,13 +179,13 @@ specifying the same illuminant, and (optionally) the same observer model.<br> <br> - In practice it is possible to compensate for the color shift that + [ In practice it is possible to compensate for the color shift that results in viewing the media under non-D50 illumination or using a non 1931_2 observer, or allowing for FWA effects without severe incompatibility because all rendering intents except absolute rendering normalize to the media color, rendering the media white as white, even though the absolute values are not measured using a D50 - illuminant.<br> + illuminant. ]<br> <h3>Using FWA compensation for single, general use profiles</h3> For creating ICC profiles that will be interchanged with other unknown ICC profiles, or used with non-print source or destination diff --git a/doc/File_Formats.html b/doc/File_Formats.html index aa0f4f4..1741701 100644 --- a/doc/File_Formats.html +++ b/doc/File_Formats.html @@ -25,6 +25,8 @@ <a href="#MPP">MPP</a><br> <a href="#TIFF">TIFF</a><br> <a href="#VRML">VRML</a><br> + <a href="#X3D">X3D</a><br> + <a href="#X3DOM">X3DOM</a><br> <br> <h2><a name=".ti1"></a>.ti1</h2> Target Information 1 data. This is an ASCII text, <a href="#CGATS">CGATS</a>, @@ -176,7 +178,29 @@ these can be viewed with a suitable standalone VRML viewer, or a plug in for a web browser. VRML97 is International Standard ISO/IEC 14772-1:1997. See <a href="http://www.vrml.org/">http://www.vrml.org/</a> - for more information.<br> + for more information. See <a href="3dformat.html">3D Viewing Format</a> + for switching to VRML output format.<br> + <br> + <h3><a name="X3D"></a>X3D</h3> + X3D is a royalty-free ISO standard XML-based file format for + representing 3D computer graphics. It is successor to the Virtual + Reality Modeling Language (VRML). See <a + href="http://www.web3d.org/">http://www.web3d.org/</a> for more + information. See <a href="3dformat.html">3D Viewing Format</a> for + switching X3D output format.<br> + <br> + <h3><a name="X3DOM"></a>X3DOM</h3> + X3DOM is an open-source framework and runtime for 3D graphics on the + Web. It can be freely used for non-commercial and commercial + purposes, and is dual-licensed under MIT and GPL license. The + javascript runtime displays embeded X3D files in browsers that + support WebGL.<br> + See <a href="http://www.x3dom.org/">http://www.x3dom.org/</a> for + more information about this format.<br> + To check if your browser supports X3DOM, try <a + href="http://www.x3dom.org/check/">this test page</a>.<br> + For more information about ArgyllCMS use of it, see <a + href="3Dformat.html">3D Viewing Format</a>.<br> <br> <br> <br> diff --git a/doc/Installing.html b/doc/Installing.html index a759044..79d8ade 100644 --- a/doc/Installing.html +++ b/doc/Installing.html @@ -2,22 +2,20 @@ <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 Installation</title> </head> <body> - <h1> - <u>Installing the software</u></h1> + <h1> <u>Installing the software</u></h1> <br> Argyll doesn't come with any installation programs or scripts, so installation is a manual process. Because things are mostly self-contained, this isn't particularly onerous. In general the - steps - are:<br> + steps are:<br> <br> 1) Provide somewhere for the executables to reside<br> 2) Provide a means of the shell finding the executables<br> @@ -28,22 +26,19 @@ system:<br> <br> <span style="font-weight: bold;"><a href="Installing_MSWindows.html">Microsoft + Windows</a><br> <a href="Installing_OSX.html">Apple OS X</a><br> <a href="Installing_Linux.html">Linux/UNIX X11</a><br> <br> - </span>If you have a Spyder 2, Spyder 4, Xrite i1 DisplayPro or + </span>If you have a Spyder 2, Spyder 4 or 5, Xrite i1 DisplayPro or ColorMunki Display colorimeter, please also see <a href="oeminst.html">oeminst</a>.<br> <br> <p><br> - - <br> - - <br> - - <br> - - </p> + <br> + <br> + <br> + </p> </body> </html> diff --git a/doc/Installing_Linux.html b/doc/Installing_Linux.html index 608ff7d..a26d64c 100644 --- a/doc/Installing_Linux.html +++ b/doc/Installing_Linux.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 Installation on Linux</title> @@ -46,6 +46,11 @@ + + + + + the <span style="font-weight: bold;">/etc/rc.local</span> startup script. You may also have to run <span style="font-weight: bold;">xset @@ -53,6 +58,11 @@ + + + + + b 100 1000 100</span> in your local setup, if you are running in an X11 environment. You can check that the system bell is operating by doing an "echo ^G", where ^G is ctrl-G.<br> @@ -172,45 +182,88 @@ probably need to disable libmtp (look in the udev configuration).<br> <br> The <b>JETI</b> specbos <span style="font-weight: bold;">1211</span><span - style="font-weight: bold;"> </span>and <b>1201</b> makes use of - the <a href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI Virtual - COM Port Drivers</a> (VCP), that should come with any recent - version of Linux.<br> + style="font-weight: bold;"> </span>and <b>1201</b>, and the <b>Klien + + + + + K10A</b> makes use of the <a + href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI Virtual COM + Port Drivers</a> (VCP), that should come with any recent version + of Linux. You may have to add yourself to the <b>dialout</b> group + to be able to open the instrument.<br> <br> <span style="font-weight: bold;"></span> <hr style="width: 100%; height: 2px;"> <h5><span style="color: rgb(204, 51, 204);"><a name="None"></a>No device configuration needed:</span></h5> - Some systems have in place a security configuration such that + A few systems have in place a security configuration such that anyone logging in at the console of a machine has access to all the local devices.<span style="color: rgb(204, 51, 204);"><span style="font-weight: bold;"><br> </span></span> <h5><span style="color: rgb(204, 51, 204);"><a name="udev1"></a>USB - instruments access using udev:<br> + instruments access using udev with existing </span><span + style="color: rgb(204, 51, 204);"><span style="font-weight: + bold;"><font color="#330033">/etc/udev/rules.d</font> or</span> + <font color="#330033"> /usr/lib/udev/rules.d/69-cd-sensors.rules</font> + file.<br> </span></h5> - <span style="color: rgb(204, 51, 204);"> </span>Most recent systems - use udev to manage device names and permissions, but by default - color instruments may not be accessible to normal system users.<br> + <span style="color: rgb(204, 51, 204);"> </span>Recent Fedora based + systems include Gnome Color Manager, which comes with a udev rule + for color instruments. You can check this by looking for the <span + style="font-weight: bold;">/etc/udev/rules.d</span> or in <b>/usr/lib/udev/rules.d/69-cd-sensors.rules</b> + file. If this exists and is up to date enough to include the + instrument you want to use, then all you have to do is add yourself + to the <b>colord</b> group, ie:<br> + <br> + sudo usermod -a -G colord $USER<br> + <br> + If the <b>69-cd-sensors.rules</b> file is out of date and does not + include the latest instruments supported by Argyll, then the + simplest thing to do is to replace the <b>69-cd-sensors.rules</b> + file with the <span style="font-weight: bold;">usb/</span><span + style="font-weight: bold;">55-Argyll.rules</span>. You will need + to do this as root, and set the owner as root, group root, + permissions 644. You may need to re-plug in your instrument to get + changes to the udev rules recognised.<br> + <h5><span style="color: rgb(204, 51, 204);"><a name="udev2"></a>USB + instruments access using udev, with no existing <font + color="#330033">/etc/udev/rules.d</font> or <font + color="#330033">/usr/lib/udev/rules.d/69-cd-sensors.rules</font> + file.<br> + </span></h5> + Most recent systems use udev to manage device names and permissions, + but by default color instruments may not be accessible to normal + system users.<br> To solve this a udev rule file needs to be added that modifies the group and permission of any Color Measurement Instruments, and you may then need to add yourself to that group.<br> <br> + First check whether other rules are in <span style="font-weight: + bold;">/etc/udev/rules.d</span> or in <b>/usr/lib/udev/rules.d</b>, + and use the appropriate directory.<br> + (You may also want to check in that directory whether + 55-Argyll.rules or some other .rules file that is setup to enable + color instruments already exists in that directory.)<br> + <br> <span style="font-weight: bold;"></span>Copy the file <span style="font-weight: bold;">usb/</span><span style="font-weight: bold;">55-Argyll.rules</span> from the binary or source distribution into <span style="font-weight: bold;">/etc/udev/rules.d/55-Argyll.rules</span> - with owner root, group root, permissions 644.<br> - (There may already be a file that handles some of the color - instruments as part of your installation. You need to check though - that it is up to date.)<br> + or <span style="font-weight: bold;">/usr/lib/udev/rules.d/55-Argyll.rules + + + + </span>(as appropriate) with owner root, group root, + permissions 644.<br> <br> If you are on an <span style="font-weight: bold;">older system</span> that uses a udev that doesn't recognize the syntax used in 55-Argyll.rules, or that doesn't have rules to create the libusb /dev/bus/usb/00X/00Y device entries, you should install the <span - style="font-weight: bold;">usb/45-Argyll.rules</span> file - instead.<br> + style="font-weight: bold;">usb/45-Argyll.rules</span> file instead + - See below.<br> <br> On recent systems the new rules file will be notices as soon as you plug the instrument in again.<br> @@ -221,128 +274,15 @@ + + + + + <b>/sbin/udevcontrol reload_rules</b> or <span style="font-weight: bold;">/sbin/udevstart</span> or reboot to get the new file noticed.<br> <br> - ----------------- cut here ---------------------<br> - # udev rule to recognize instruments and make them accessible to - user applications.<br> - # Copy this to /etc/udev/rules.d/55-Argyll.rules<br> - <br> - # Skip all this to speed things up if it'a not a usb add.<br> - ACTION!="add", GOTO="argyll_rules_end"<br> - SUBSYSTEM!="usb", GOTO="argyll_rules_end"<br> - <br> - # Recognize the color measurement devices<br> - <br> - # Colorimtre HCFR<br> - ATTRS{idVendor}=="04db", ATTRS{idProduct}=="005b", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - <br> - # MonacoOPTIX (Same as i1 Display 1)<br> - ATTRS{idVendor}=="0670", ATTRS{idProduct}=="0001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - <br> - # HueyL (not tested)<br> - ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # HueyL (not tested)<br> - ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5010", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # i1Display 3<br> - ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5020", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # ColorMunki Smile<br> - ATTRS{idVendor}=="0765", ATTRS{idProduct}=="6003", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # DTP20<br> - ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d020", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # DTP92Q (not tested)<br> - ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d092", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # DTP94<br> - ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d094", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - <br> - # i1Pro<br> - ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2000", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # i1Monitor<br> - ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # i1Display<br> - ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2003", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # i1 io table (not tested)<br> - ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2004", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # Huey<br> - ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2005", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # i1 iSis (not tested)<br> - ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2006", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # ColorMunki<br> - ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2007", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - <br> - # Spyder 1<br> - ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0100", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # Spyder 2<br> - ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0200", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # Spyder 3<br> - ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0300", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - # Spyder 4<br> - ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0400", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - <br> - # ColorHug, old and new<br> - ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="f8da", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - ATTRS{idVendor}=="273f", ATTRS{idProduct}=="1001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"<br> - <br> - <br> - # Let udev-acl manage these devices, if it's available<br> - TEST=="/var/run/ConsoleKit/database", - ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1"<br> - <br> - # Otherwise, restrict access to members of the plugdev group,<br> - # which the user may have to add to the system.<br> - ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}!="*?", - MODE="660", GROUP="plugdev"<br> - <br> - # Set ID_VENDOR and ID_MODEL acording to VID and PID<br> - IMPORT{program}="usb-db %p"<br> - <br> - LABEL="argyll_rules_end"<br> - ----------------- cut here ---------------------<br> - <br> (You may want to refer to <a href="http://reactivated.net/writing_udev_rules.html">this document</a> for more guidance on modifying udev rules, as well as @@ -352,50 +292,48 @@ href="http://www.google.com/search?hl=en&q=man+udev&btnG=Search&meta <span style="font-weight: bold;">YOU THEN MAY NEED TO:</span><br> <br> If your system is <span style="font-weight: bold;">not</span> using - the new ACL to manage device access for console users (the file <span - style="font-weight: bold;">/lib/udev/udev-acl</span> doesn't exist - on your system), then you will <span style="text-decoration: - underline;">need to add</span> yourself to the <span - style="font-weight: bold;">plugdev</span> group, if you are not - already a member of it. You can do this either by using a "Users and - Groups" system administration tool, or on the command line running - as root:<br> + the ACL to manage device access for console users (the file <span + style="font-weight: bold;">/var/run/ConsoleKit/database</span> + doesn't exist on your system), then you will <span + style="text-decoration: underline;">need to add</span> yourself to + the <span style="font-weight: bold;">colord</span> group, if you + are not already a member of it. You can do this either by using a + "Users and Groups" system administration tool, or on the command + line running as root:<br> <br> - sudo usermod -a -G plugdev yourusernamehere<br> + sudo usermod -a -G colord $USER<br> <br> or<br> su root<br> - usermod -a -G plugdev yourusernamehere<br> + usermod -a -G colord $USER<br> <br> (If the usermod program isn't found as root, it might be in /usr/sbin, ie. use /usr/sbin/usermod .... etc.<br> If usermod doesn't recognize the -a flag try "usermod -A - plugdev yourusernamehere".<br> + colord $USER".<br> If this doesn't work you will have to run "id yourusername" to list the current supplemental<br> - groups, and add them plus plugdev using just "usermod -G + groups, and add them plus colord using just "usermod -G group1,group2,... yourusername")<br> <br> - You may find that the <span style="font-weight: bold;">plugdev</span> - group doesn't exist on your system, and if so you will need to - create it:<br> + You may find that the <b>colord</b><b></b> group doesn't exist on + your system, and if so you will need to create it:<br> <br> - sudo groupadd -r plugdev<br> + sudo groupadd -r colord<br> <br> - and then add yourself to the plugdev group.<br> + and then add yourself to the <b>colord</b> group.<br> <br> You may have to log out and then in again for the groups to become effective.<br> <br> You can check whether the instrument is being recognized and set to - the plugdev group by comparing the output of <span + the colord group by comparing the output of <span style="font-weight: bold;">ls -l -R /dev/bus/usb</span> without and then with the instrument plugged in.<br> <br> You can test whether your instrument is accessible by plugging it in and then running "spotread -?" and looking for it listed after the <span style="font-weight: bold;">-c</span> option.<br> - <span style="font-weight: bold;"></span> <h5><span style="color: rgb(204, 51, 204);"><a name="hotplug"></a>USB instruments @@ -404,6 +342,11 @@ instruments + + + + + access using hotplug:<br> </span></h5> Under <span style="font-weight: bold;">much older versions of Linux</span>, @@ -419,78 +362,6 @@ instruments with owner root, group root, permissions 644.<span style="font-weight: bold;"></span><br> <br> - ----------------- cut here ---------------------<br> - # hotplug device mapping to handling script.<br> - # Copy this to /etc/hotplug/usb/Argyll.usermap<br> - #<br> - # Detect instruments by their USB VID and PID<br> - #<br> - # DTP20<br> - Argyll 0x0003 0x0765 0xd020 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # DTP92Q - not tested<br> - Argyll 0x0003 0x0765 0xd092 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # DTP94<br> - Argyll 0x0003 0x0765 0xd094 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # MonacoOPTIX (Same as i1 Display 1)<br> - Argyll 0x0003 0x0670 0x0001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # i1 Display<br> - Argyll 0x0003 0x0971 0x2003 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # i1 Display 3<br> - Argyll 0x0003 0x0765 0x5020 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # i1 Monitor<br> - Argyll 0x0003 0x0971 0x2001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # i1 Pro<br> - Argyll 0x0003 0x0971 0x2000 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # ColorMunki<br> - Argyll 0x0003 0x0971 0x2007 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # ColorMunki Smile<br> - Argyll 0x0003 0x0765 0x6003 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # Colorimtre HCFR<br> - Argyll 0x0003 0x04DB 0x005B 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # Spyder 2<br> - Argyll 0x0003 0x085C 0x0200 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # Spyder 3<br> - Argyll 0x0003 0x085C 0x0300 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # Spyder 4<br> - Argyll 0x0003 0x085C 0x0400 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # Huey<br> - Argyll 0x0003 0x0971 0x2005 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - #<br> - # ColorHug<br> - Argyll 0x0003 0x04D8 0xF8DA 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - Argyll 0x0003 0x273F 0x1001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000<br> - ----------------- cut here ---------------------<br> <br> (For even older versions, append the lines above to <span style="font-weight: bold;">/etc/hotplug/usb.usermap</span>, and @@ -502,49 +373,37 @@ instruments with owner root, group root, permissions 744.<span style="font-weight: bold;"></span><br> <br> - ----------------- cut here ---------------------<br> - #!/bin/sh<br> - # Copy to /etc/hotplug/usb/Argyll<br> - #<br> - # Argyll hotplug script. Adds the USB devices to the plugdev group.<br> - if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]<br> - then<br> - chgrp plugdev "${DEVICE}"<br> - chmod 660 "${DEVICE}"<br> - fi<br> - ----------------- cut here ---------------------<br> - <br> <span style="font-weight: bold;">YOU THEN NEED TO:</span><br> <br> You will then <span style="text-decoration: underline;">need to add</span> - yourself to the <span style="font-weight: bold;">plugdev</span> + yourself to the <span style="font-weight: bold;">colord</span> group, if you are not already a member of it. You can do this either by using a "Users and Groups" system administration tool, or on the command line running as root:<br> <br> - sudo usermod -a -G plugdev yourusernamehere<br> + sudo usermod -a -G colord $USER<br> <br> or<br> su root<br> - usermod -a -G plugdev yourusernamehere<br> + usermod -a -G colord $USER<br> <br> <br> (If the usermod program isn't found as root, it might be in /usr/sbin, ie. use /usr/sbin/usermod .... etc.<br> If usermod doesn't recognize the -a flag try "usermod -A - plugdev yourusernamehere".<br> + colord $USER".<br> If this doesn't work you will have to run "id yourusername" to list the current suplemental<br> - groups, and add plugdev using just "usermod -G + groups, and add colord using just "usermod -G group1,group2,... yourusername")<br> <br> - You may find that the <span style="font-weight: bold;">plugdev</span> + You may find that the <span style="font-weight: bold;">colord</span> group doesn't exist on your system, and if so you will need to create it:<br> <br> - sudo groupadd -r plugdev<br> + sudo groupadd -r colord<br> <br> - and then add youself to the plugdev group.<br> + and then add youself to the colord group.<br> <br> You may have to log out and then in again for the groups to become effecive.<br> @@ -561,6 +420,11 @@ instruments + + + + + access:</span><br> </h5> If you have a serial instrument then you may find that by default @@ -573,16 +437,16 @@ instruments administration tool, or on the command line using "usermod":<br> <br> su root<br> - usermod -a -G tty,uucp yourusernamehere<br> + usermod -a -G tty,uucp $USER<br> <br> or<br> <br> - sudo usermod -a -G tty,uucp yourusernamehere<br> + sudo usermod -a -G tty,uucp $USER<br> <br> (If the usermod program isn't found as root, it might be in /usr/sbin, ie. use /usr/sbin/usermod .... etc.<br> If usermod doesn't recognize the -a flag try "usermod -A - plugdev yourusernamehere".<br> + colord $USER".<br> If this doesn't work you will have to run "id yourusername" to list the current suplemental<br> groups, and add a tty or uucp group using just "usermod -G diff --git a/doc/Installing_MSWindows.html b/doc/Installing_MSWindows.html index c08e16d..40dcd2c 100644 --- a/doc/Installing_MSWindows.html +++ b/doc/Installing_MSWindows.html @@ -31,7 +31,8 @@ You should also configure your %PATH% environment variable to give access to the executables from your command line environment.<br> <br> - For <span style="font-weight: bold;">Windows 8</span>, look in<br> + For <span style="font-weight: bold;">Windows 8</span> & <b>8.1</b>, + look in<br> <span style="font-weight: bold;"></span>Desktop -> Settings -> Control Panel -> System And Security -> System -> Advanced System Settings -> Environment Variables<br> @@ -60,9 +61,9 @@ <br> So if the current value of PATH is "%SystemRoot%\system32;%SystemRoot%" and you unpacked Argyll version - 1.6.3 in <span style="font-weight: bold;">d:\bin\</span>, then you + 1.7.0 in <span style="font-weight: bold;">d:\bin\</span>, then you would modify PATH to be - "%SystemRoot%\system32;%SystemRoot%;d:\bin\Argyll_V1.6.3\bin", - + "%SystemRoot%\system32;%SystemRoot%;d:\bin\Argyll_V1.7.0\bin", - i.e. you append the path to the Argyll binaries to your PATH, separated by the ';' character. The change will take effect when you start a new command shell, which you start from Start @@ -77,14 +78,14 @@ doc sub-directory, and instrument USB drivers in the usb directory.<br> <br> <span style="font-weight: bold;">NOTE: </span><span - style="font-weight: bold;">Vista 64/Windows 7 & 8 64 bit</span> - and <span style="font-weight: bold;">Beep</span> prompt<span - style="font-weight: bold;">: </span>Microsoft (in its infinite - wisdom) has removed the built in speaker driver, and now relies on - systems having a sound card and speakers's installed and turned on - to hear system beeps. So if you're wondering where the beeps have - gone when using <a href="chartread.html">chartread</a>, now you - know.<span style="font-weight: bold;"></span><br> + style="font-weight: bold;">Vista 64/Windows 7, 8 & 8.1 + 64 bit</span> and <span style="font-weight: bold;">Beep</span> + prompt<span style="font-weight: bold;">: </span>Microsoft (in its + infinite wisdom) has removed the built in speaker driver, and now + relies on systems having a sound card and speakers's installed and + turned on to hear system beeps. So if you're wondering where the + beeps have gone when using <a href="chartread.html">chartread</a>, + now you know.<span style="font-weight: bold;"></span><br> <br> <span style="font-weight: bold;">NOTE: Microsofts generic VGA Driver</span> does not appear to support setting the display VideoLUTs. You will @@ -134,7 +135,7 @@ <br> If you are using the <b>JETI</b> specbos <span style="font-weight: bold;">1211</span><span style="font-weight: bold;"> </span>or <b>1201</b>, - then you may need to install the <a + or the <b>Klein K10A</b> then you may need to install the <a href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI Virtual COM Port Drivers</a> (VCP), if they are not already on your system.<br> <br> @@ -147,7 +148,8 @@ <a href="#WIN2K">Windows 2000</a><br> <br> <hr style="width: 100%; height: 2px;"><a name="WIN8"></a><font - size="+1"><span style="font-weight: bold;">Windows 8</span></font><br> + size="+1"><span style="font-weight: bold;">Windows 8 & 8.1</span></font><font + size="+1"><span style="font-weight: bold;"></span></font><br> <br> <span style="color: rgb(51, 153, 153);"><span style="color: rgb(0, 0, 0); text-decoration: underline;"><span style="font-weight: @@ -164,7 +166,13 @@ <br> <span style="text-decoration: underline;">To install the Argyll driver for the first instrument:</span><br> - (Plug in instrument)<br> + Settings -> Power -> <span + style="font-weight: bold;">Hold Shift Key down and click</span> + "Restart" -> Troubleshoot -> Advanced Options -> Startup + Settings -> Restart -><br> + (After Reboot) -> "Disable Driver Signature + Enforcement" (number 7 on the list)<br> + (After system starts, Plug in instrument)<br> Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager -><br> Other Devices -> <instrument being @@ -191,7 +199,13 @@ <br> <span style="text-decoration: underline;">To install the Argyll Driver:</span><br> - (Plug in instrument)<br> + Settings -> Power -> <span + style="font-weight: bold;">Hold Shift Key down and click</span> + "Restart" -> Troubleshoot -> Advanced Options -> Startup + Settings -> Restart -><br> + (After Reboot) -> Disable Driver Signature + Enforcement" (number 7 on the list)<br> + (After system starts, Plug in instrument)<br> Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager<br> (Locate the instrument in the device list. It may diff --git a/doc/Installing_OSX.html b/doc/Installing_OSX.html index 8a17291..fb01e4a 100644 --- a/doc/Installing_OSX.html +++ b/doc/Installing_OSX.html @@ -1,313 +1,354 @@ -<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en"> -<html> - <head> - <meta http-equiv="Content-Type" content="text/html; - charset=ISO-8859-1"> - <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> - <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I) - [Netscape]"> - <title>Argyll Installation on Apple OS X</title> - </head> - <body> - <h1> <u>Installing the software on Apple OS X<br> - </u></h1> - <br> - You will need to unpack the downloaded file in the location you have - chosen to hold the executable files. Typically this might be in <span - style="font-style: italic;">/usr/bin</span>, or perhaps <span - style="font-style: italic;">$HOME/bin/</span>, or <i>even $HOME.</i><br> - <br> - You can unpack it by control-click on the downloaded file and “Open - With” BOMArchiveHelper or Archive Utility. Drag the resulting folder - to where you want it, e.g. into your home folder (/Users/usrnam - where usrnam is your username).<br> - <br> - Alternatively you can unpack it on the command line using the - command <span style="font-weight: bold;">tar -zxf</span> <span - style="font-weight: bold;">archivename.tgz</span>, which will - create a directory <span style="font-weight: bold;">Argyll_VX.X.X</span>, - where X.X.X is the version number, and the executables will be in <span - style="font-weight: bold;">Argyll_VX.X.X/bin</span>. <br> - <br> - Open a Terminal shell. This will be in - Applications->Utilities->Terminal (Dragging it to the dock is - a good idea to make it more accessible).<br> - <br> - You will have to configure your $PATH environment variable to give - access to the executable from your command line environment, by - editing your <span style="font-weight: bold;">.profile</span> file. - You can do this using a graphical editor, by using the open command:<br> - <br> - ~$open .profile<br> - <br> - or by using some other editor, such as <span style="font-weight: - bold;">vi</span>.<br> - <br> - And add a line similar to the following line to your .path file<br> - <br> - PATH=$PATH:$HOME/Argyll_VX.X.X/bin<br> - <br> - where "$HOME/Argyll_VX.X.X/bin" is the path to the executable - directory.<br> - <br> - If you are unfamiliar with how to do this, consult an appropriate - tutorial, e.g. <<a -href="http://heather.cs.ucdavis.edu/matloff/public_html/UnixAndC/Unix/ShellIntro.pdf">ShellIntro</a>>. -The -.tgz -file -also -contains -several -useful -reference - - - - files (such as scanner chart recognition templates, sample - illumination spectrum etc.) in the ref sub-directory, as well as all - the current documentation in a doc sub-directory.<br> - <br> - For most devices there is nothing special to do. Plug in and go. - Some devices may not work without some extra help though:<br> - <h3><a name="ColorMunki"></a><span style="text-decoration: - underline;">X-Rite ColorMunki</span></h3> - Some version of X-Rite's ColorMunki drivers released between 2009 - and 2011 install an X-Rite daemon that runs as root and grabs the - device, preventing any other programs (such as Argyll) from opening - them. Latter versions seem to be more cooperative, and don't suffer - from this problem. There are three ways of working around this - problem:<br> - <br> - 1) Turn off the X-Rite service for the ColorMunki. See <<a - class="moz-txt-link-freetext" -href="http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980">http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980</a>>.<br> - <br> - 2) Run all Argyll programs that need to access the instrument as - root. For instance:<br> - <br> - sudo spotread<br> - <br> - and then you will be asked for the root password.<br> - While these methods will work, they are incovenient. <br> - <br> - 3) Alter the X-Rite drivers Daeomon so that it runs under your user - account.<br> - <br> - To do this you need to edit the script that controls the X-Rite - Daemon.<br> - <br> - cd ~<br> - whoami<br> - cp - /Library/LaunchDaemons/com.xrite.device.colormunki.plist temp.plist<br> - open temp.plist<br> - <br> - and add one child below the root:<br> - <br> +<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
+<html>
+ <head>
+ <meta http-equiv="Content-Type" content="text/html;
+ charset=windows-1252">
+ <meta http-equiv="content-type" content="text/html;
+ charset=windows-1252">
+ <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I)
+ [Netscape]">
+ <title>Argyll Installation on Apple OS X</title>
+ </head>
+ <body>
+ <h1> <u>Installing the software on Apple OS X<br>
+ </u></h1>
+ <br>
+ You will need to unpack the downloaded file in such a way that the
+ files it contains end up in the location you have chosen to hold its
+ contents.<br>
+ <br>
+ If you want to install it system wide, then you probably want to
+ unpack it in the <i>/Applications</i> folder, so that it ends up in
+ the <i>/Applications/Argyll_VX.X.X</i> folder.<br>
+ Another option is just to install it somewhere under your $HOME
+ folder, such as <span style="font-style: italic;">$HOME/</span><i>Argyll_VX.X.X</i>
+ or <span style="font-style: italic;">$HOME/</span><i>bin/Argyll_VX.X.X</i>,
+ depending on how you like to organize your applications and utility
+ programs. ($HOME is the shell symbolic name for your home folder,
+ typically /Users/<i>username</i>. Another abbreviation for it is the
+ ~ character.)<br>
+ <br>
+ You can unpack it by control-click on the downloaded file and “Open
+ With” BOMArchiveHelper or Archive Utility. Drag the resulting folder
+ to where you want it, e.g. into <i>/Applications</i>, <i>$HOME</i>
+ or <i>$HOME/bin</i>.<br>
+ <br>
+ Alternatively you can unpack it on the command line using the
+ command <span style="font-weight: bold;">tar -zxf</span> <span
+ style="font-weight: bold;">archivename.tgz</span>, which will
+ create a folder <span style="font-weight: bold;">Argyll_VX.X.X</span>
+ in your current folder, where X.X.X is the version number, and the
+ executables will be in <span style="font-weight: bold;">Argyll_VX.X.X/bin</span>
+ sub-folder.<br>
+ <br>
+ Open a Terminal shell. This will be in
+ Applications->Utilities->Terminal (Dragging it to the dock is
+ a good idea to make it more accessible).<br>
+ <br>
+ You should configure your $PATH environment variable to give the
+ shell access to the executable from your command line environment
+ without having to spell out the whole path every time, by editing
+ your <span style="font-weight: bold;">.profile</span> file, which
+ will be in your $HOME folder. You can open a graphical editor on
+ this file by using the open command:<br>
+ <br>
+ open $HOME/.profile<br>
+ <br>
+ or alternatively, use some other text editor that you are familiar
+ with.<br>
+ <br>
+ Add a line similar to the following line to your .profile file:<br>
+ <br>
+ PATH=$PATH:/Applications/Argyll_VX.X.X/bin<br>
+ <br>
+ where "/Applications/Argyll_VX.X.X/bin" is the path to the folder
+ that contains the ArgyllCMS executables.<br>
+ Save your changes and exit the editor.<br>
+ <br>
+ If you want further guidance in setting up and using a command line
+ environment, then please consult an appropriate tutorial, e.g. <<a
+href="http://heather.cs.ucdavis.edu/matloff/public_html/UnixAndC/Unix/ShellIntro.pdf">ShellIntro</a>>.<br>
+ <br>
+ The .tgz file also contains several useful reference files (such as
+ scanner chart recognition templates, sample illumination spectrum
+ etc.) in the <b>ref</b> sub-folder, as well as all the current
+ documentation in a <b>doc</b> sub-folder.<br>
+ <br>
+ For most devices there is nothing special to do. Plug in and go.
+ Some devices may not work without some extra help though:<br>
+ <h3><a name="ColorMunki"></a><span style="text-decoration:
+ underline;">X-Rite ColorMunki</span></h3>
+ Some version of X-Rite's ColorMunki drivers released between 2009
+ and 2011 install an X-Rite daemon that runs as root and grabs the
+ device, preventing any other programs (such as Argyll) from opening
+ them. Latter versions seem to be more cooperative, and don't suffer
+ from this problem. There are three ways of working around this
+ problem:<br>
+ <br>
+ 1) Turn off the X-Rite service for the ColorMunki. See <<a
+ class="moz-txt-link-freetext"
+href="http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980">http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980</a>>.<br>
+ <br>
+ 2) Run all Argyll programs that need to access the instrument as
+ root. For instance:<br>
+ <br>
+ sudo spotread<br>
+ <br>
+ and then you will be asked for the root password.<br>
+ While these methods will work, they are inconvenient. <br>
+ <br>
+ 3) Alter the X-Rite drivers Daeomon so that it runs under your user
+ account.<br>
+ <br>
+ To do this you need to edit the script that controls the X-Rite
+ Daemon.<br>
+ <br>
+ cd ~<br>
+ whoami<br>
+ cp
+ /Library/LaunchDaemons/com.xrite.device.colormunki.plist temp.plist<br>
+ open temp.plist<br>
+ <br>
+ and add one child below the root:<br>
+ <br>
<span style="text-decoration: underline;">Item Type - Value - </span><br> - UserName + + + + + +
+ Value
+ </span><br>
+ UserName
string - myusername<br> - <br> - where "myusername" is your username shown by whoami, and save the - file. You then need to copy the modified file back: <br> - <br> - sudo cp temp.plist - /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br> - <br> - You will then need to restart the machine for this change to take - effect, or invoke the following commands:<br> - <br> - sudo launchctl unload - /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br> - sudo launchctl load - /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br> - <br> - <span style="font-weight: bold;">NOTE</span> that after running - Argyll tools, you may have to turn the X-Rite service off then on - again, or disconnect and reconnect the instrument.<br> - <br> - <h3><a name="ColorMunki"></a><span style="text-decoration: - underline;">X-Rite EyeOne Pro</span><br> - </h3> - Some version of X-Rite's EyeOne Pro drivers drivers released between - 2009 and 2011 install an X-Rite daemon that runs as root and grabs - the device, preventing any other programs (such as Argyll) from - opening them. Latter versions seem to be more cooperative, and don't - suffer from this problem. There are three ways of working around - this problem:<br> - <br> - 1) Turn off the X-Rite service for the EyeOne Pro. See <<a - class="moz-txt-link-freetext" -href="http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980">http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980</a>>.<br> - <br> - 2) Run all Argyll programs that need to access the instrument as - root. For instance:<br> - <br> - sudo spotread<br> - <br> - and then you will be asked for the root password.<br> - While these methods will work, they are inconvenient. <br> - <br> - 3) Alter the X-Rite drivers Daemon so that it runs under your user - account.<br> - <br> - To do this you need to edit the script that controls the X-Rite - Daemon.<br> - <br> - cd ~<br> - whoami<br> - cp - /Library/LaunchDaemons/com.xrite.device.i1.plist temp.plist<br> - open temp.plist<br> - <br> - and add one child below the root:<br> - <br> + + + + + +
+ myusername<br>
+ <br>
+ where "myusername" is your username shown by whoami, and save the
+ file. You then need to copy the modified file back: <br>
+ <br>
+ sudo cp temp.plist
+ /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br>
+ <br>
+ You will then need to restart the machine for this change to take
+ effect, or invoke the following commands:<br>
+ <br>
+ sudo launchctl unload
+ /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br>
+ sudo launchctl load
+ /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br>
+ <br>
+ <span style="font-weight: bold;">NOTE</span> that after running
+ Argyll tools, you may have to turn the X-Rite service off then on
+ again, or disconnect and reconnect the instrument.<br>
+ <br>
+ <h3><a name="ColorMunki"></a><span style="text-decoration:
+ underline;">X-Rite EyeOne Pro</span><br>
+ </h3>
+ Some version of X-Rite's EyeOne Pro drivers drivers released between
+ 2009 and 2011 install an X-Rite daemon that runs as root and grabs
+ the device, preventing any other programs (such as Argyll) from
+ opening them. Latter versions seem to be more cooperative, and don't
+ suffer from this problem. There are three ways of working around
+ this problem:<br>
+ <br>
+ 1) Turn off the X-Rite service for the EyeOne Pro. See <<a
+ class="moz-txt-link-freetext"
+href="http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980">http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980</a>>.<br>
+ <br>
+ 2) Run all Argyll programs that need to access the instrument as
+ root. For instance:<br>
+ <br>
+ sudo spotread<br>
+ <br>
+ and then you will be asked for the root password.<br>
+ While these methods will work, they are inconvenient. <br>
+ <br>
+ 3) Alter the X-Rite drivers Daemon so that it runs under your user
+ account.<br>
+ <br>
+ To do this you need to edit the script that controls the X-Rite
+ Daemon.<br>
+ <br>
+ cd ~<br>
+ whoami<br>
+ cp
+ /Library/LaunchDaemons/com.xrite.device.i1.plist temp.plist<br>
+ open temp.plist<br>
+ <br>
+ and add one child below the root:<br>
+ <br>
<span style="text-decoration: underline;">Item Type - Value - </span><br> - UserName + + + + + +
+ Value
+ </span><br>
+ UserName
string - myusername<br> - <br> - where "myusername" is your username shown by whoami, and save the - file. You then need to copy the modified file back: <br> - <br> - sudo cp temp.plist - /Library/LaunchDaemons/com.xrite.device.i1.plist<br> - <br> - You will then need to restart the machine for this change to take - effect, or invoke the following commands:<br> - <br> - sudo launchctl unload - /Library/LaunchDaemons/com.xrite.device.i1.plist<br> - sudo launchctl load - /Library/LaunchDaemons/com.xrite.device.i1.plist<br> - <br> - <span style="font-weight: bold;">NOTE</span> that after running - Argyll tools, you may have to turn the X-Rite service off then on - again, or disconnect and reconnect the instrument.<br> - <br> + + + + + +
+ myusername<br>
+ <br>
+ where "myusername" is your username shown by whoami, and save the
+ file. You then need to copy the modified file back: <br>
+ <br>
+ sudo cp temp.plist
+ /Library/LaunchDaemons/com.xrite.device.i1.plist<br>
+ <br>
+ You will then need to restart the machine for this change to take
+ effect, or invoke the following commands:<br>
+ <br>
+ sudo launchctl unload
+ /Library/LaunchDaemons/com.xrite.device.i1.plist<br>
+ sudo launchctl load
+ /Library/LaunchDaemons/com.xrite.device.i1.plist<br>
+ <br>
+ <span style="font-weight: bold;">NOTE</span> that after running
+ Argyll tools, you may have to turn the X-Rite service off then on
+ again, or disconnect and reconnect the instrument.<br>
+ <br>
<h3><a name="specbos"></a><span style="text-decoration: underline;">JETI specbos - 1201 and 1211</span><br> - </h3> - <br> - If you are using the <b>JETI</b> specbos <span style="font-weight: - bold;">1211</span><span style="font-weight: bold;"> </span>and <b>1201</b>, - then you may need to install the <a - href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI Virtual COM - Port Drivers</a> (VCP), if they are not already on your system.<br> - <br> - <h3><a name="HCFR"></a><u>HCFR Colorimeter</u></h3> - The default OS X class drivers will grab this device, preventing - Argyll from accessing it. To overcome this, you need to install a - codeless kernel extension if you wish to use the HCFR colorimeter, - that prevents this from happening. From the command line you need to - create a directory called Argyll.kext somewhere convenient, and then - place in it one file called Info.plist, containing the following:<br> - <br> - ----------------- cut here ---------------------<br> - <?xml version="1.0" encoding="UTF-8"?><br> - <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST - 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"><br> - <plist version="1.0"><br> - <dict><br> - - <key>CFBundleDevelopmentRegion</key> - <string>English</string><br> - - <key>CFBundleGetInfoString</key> <string>Libusb - USB device Shield</string><br> - - <key>CFBundleIdentifier</key> - <string>com.libusb.USB_Shield</string><br> - - <key>CFBundleInfoDictionaryVersion</key> - <string>6.0</string><br> - <key>CFBundleName</key> - <string>Libusb USB device Shield</string><br> - - <key>CFBundlePackageType</key> - <string>KEXT</string><br> - <key>CFBundleSignature</key> - <string>????</string><br> - <key>CFBundleVersion</key> - <string>6.0</string><br> - - <key>IOKitPersonalities</key><br> - <dict><br> - - <key>HCFR</key><br> - <dict><br> - - <key>CFBundleIdentifier</key> - <string>com.apple.driver.AppleUSBComposite</string><br> - - <key>IOClass</key> - <string>AppleUSBComposite</string><br> - - <key>IOProviderClass</key> - <string>IOUSBDevice</string><br> - - <key>idVendor</key> - <integer>1243</integer><br> + + + + + +
+ 1201 and 1211</span> and <u>Klein K10A</u><br>
+ </h3>
+ <br>
+ If you are using the <b>JETI</b> specbos <span style="font-weight:
+ bold;">1211</span><span style="font-weight: bold;"> </span>and <b>1201</b>,
+ or the <b>Klein K10A</b> then you may need to install the <a
+ href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI Virtual COM
+ Port Drivers</a> (VCP), if they are not already on your system.<br>
+ <br>
+ <h3><a name="HCFR"></a><u>HCFR Colorimeter</u></h3>
+ The default OS X class drivers will grab this device, preventing
+ Argyll from accessing it. To overcome this, you need to install a
+ codeless kernel extension if you wish to use the HCFR colorimeter,
+ that prevents this from happening. From the command line you need to
+ create a folder called Argyll.kext somewhere convenient, and then
+ place in it one file called Info.plist, containing the following:<br>
+ <br>
+ ----------------- cut here ---------------------<br>
+ <?xml version="1.0" encoding="UTF-8"?><br>
+ <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST
+ 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"><br>
+ <plist version="1.0"><br>
+ <dict><br>
+
+ <key>CFBundleDevelopmentRegion</key>
+ <string>English</string><br>
+
+ <key>CFBundleGetInfoString</key> <string>Libusb
+ USB device Shield</string><br>
+
+ <key>CFBundleIdentifier</key>
+ <string>com.libusb.USB_Shield</string><br>
+
+ <key>CFBundleInfoDictionaryVersion</key>
+ <string>6.0</string><br>
+ <key>CFBundleName</key>
+ <string>Libusb USB device Shield</string><br>
+
+ <key>CFBundlePackageType</key>
+ <string>KEXT</string><br>
+ <key>CFBundleSignature</key>
+ <string>????</string><br>
+ <key>CFBundleVersion</key>
+ <string>6.0</string><br>
+
+ <key>IOKitPersonalities</key><br>
+ <dict><br>
+
+ <key>HCFR</key><br>
+ <dict><br>
+
+ <key>CFBundleIdentifier</key>
+ <string>com.apple.driver.AppleUSBComposite</string><br>
+
+ <key>IOClass</key>
+ <string>AppleUSBComposite</string><br>
+
+ <key>IOProviderClass</key>
+ <string>IOUSBDevice</string><br>
+
+ <key>idVendor</key>
+ <integer>1243</integer><br>
- <key>idProduct</key> - <integer>91</integer><br> - - </dict><br> - </dict><br> - - <key>OSBundleCompatibleVersion</key> - <string>1.8</string><br> - <key>OSBundleLibraries</key><br> - <dict><br> - - <key>com.apple.kernel.iokit</key> - <string>6.0</string><br> - </dict><br> - </dict><br> - </plist><br> - ----------------- cut here ---------------------<br> - <br> - (You can also copy this from the source installation in - usb/Argyll.kext)<br> - <br> - You then need to install it by using:<br> - <br> - sudo cp -R Argyll.kext /System/Library/Extensions<br> - <br> - supplying the appropriate root password when prompted.<br> - Reboot the system to activate the extension.<br> - <br> - <p><br> - </p> - </body> -</html> + + + + + +
+ <key>idProduct</key>
+ <integer>91</integer><br>
+
+ </dict><br>
+ </dict><br>
+
+ <key>OSBundleCompatibleVersion</key>
+ <string>1.8</string><br>
+ <key>OSBundleLibraries</key><br>
+ <dict><br>
+
+ <key>com.apple.kernel.iokit</key>
+ <string>6.0</string><br>
+ </dict><br>
+ </dict><br>
+ </plist><br>
+ ----------------- cut here ---------------------<br>
+ <br>
+ (You can also copy this from the source installation in
+ usb/Argyll.kext)<br>
+ <br>
+ You then need to install it by using:<br>
+ <br>
+ sudo cp -R Argyll.kext /System/Library/Extensions<br>
+ <br>
+ supplying the appropriate root password when prompted.<br>
+ Reboot the system to activate the extension.<br>
+ <br>
+ <p><br>
+ </p>
+ </body>
+</html>
diff --git a/doc/K10A.jpg b/doc/K10A.jpg Binary files differnew file mode 100644 index 0000000..1a93349 --- /dev/null +++ b/doc/K10A.jpg diff --git a/doc/Scenarios.html b/doc/Scenarios.html index e82a8a4..7b5899f 100644 --- a/doc/Scenarios.html +++ b/doc/Scenarios.html @@ -75,6 +75,11 @@ handled when calibration is being used<br>
</a></h4>
<h4> <a href="#LP1">Linking Profiles</a></h4>
+ <p> <b><a href="#LP2">Image dependent gamut
+ mapping using device links</a></b><br>
+ </p>
+ <p> <b><a href="#LP2">Soft Proofing Link</a></b><br>
+ </p>
<h4> <a href="#TR1">Transforming colorspaces of raster files</a></h4>
<h4></h4>
<h4> <a href="#TV1">Creating Video Calibration 3DLuts</a></h4>
@@ -164,6 +169,17 @@ + + + + + + + + + + + and profiling a display that doesn't have VideoLUT access</a>.<br>
<br>
@@ -231,6 +247,17 @@ + + + + + + + + + + + -r</span> for an LCD display, or <span style="text-decoration:
underline; color: rgb(204, 51, 204);">dispcal -yc -r</span> for a
@@ -602,6 +629,17 @@ + + + + + + + + + + + (<span style="font-weight: bold;">-Iw</span>) changes by doing on
the fly calibrations during the measurements. Instrument black level
@@ -661,6 +699,17 @@ + + + + + + + + + + + Correction Matrix</a>. These are specific to a particular
Colorimeter and Display make and model combination, although a
@@ -818,6 +867,17 @@ + + + + + + + + + + + SG</a> charts:<br>
<br>
@@ -875,37 +935,6 @@ -
- HCT</a> :<br>
- <br>
- <img alt="HutchColor HCT" src="HCT.jpg" style="width: 182px; height:
- 140px;"><br>
- <br>
- <br>
- and <a
-href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.html">Christophe - - - - - - - - - - - - - - - - - - - - - - @@ -917,6 +946,24 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm +
+ HCT</a> :<br>
+ <br>
+ <img alt="HutchColor HCT" src="HCT.jpg" style="width: 182px; height:
+ 140px;"><br>
+ <br>
+ <br>
+ and <a href="http://www.cmp-color.fr/DT3.html">Christophe
+ Métairie's Digital TargeT 003</a> and <a
+ href="http://www.cmp-color.fr/digital%20target.html">Christophe
+ Métairie's Digital Target - 4</a> :<br>
+ <br>
+ <img alt="CMP_DT_003" src="CMP_DT_003.jpg" style="width: 186px;
+ height: 141px;"> <img style="width: 203px; height: 140px;"
+ alt="CMP_Digital_Target-4" src="CMP_Digital_Target-4.jpg"
+ height="140" width="203"><br>
+ <br>
+ and the <a href="http://www.silverfast.com/show/dc-targets/en.html">LaserSoft @@ -928,9 +975,6 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm -
- Métairie's Digital TargeT 003</a> and <a
-href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.html">Christophe @@ -976,35 +1020,20 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm - Métairie's Digital Target - 3</a> :<br>
+ Imaging DCPro Target</a>:<br>
<br>
- <img alt="CMP_DT_003" src="CMP_DT_003.jpg" style="width: 186px;
- height: 141px;"> <img style="width: 203px; height: 140px;"
- alt="CMP_Digital_Target-3" src="CMP_Digital_Target-3.jpg"><br>
+ <img style="width: 153px; height: 122px;" alt="LaserSoft DCPro
+ Target" src="LSDC.jpg"><br>
<br>
- and the <a href="http://www.silverfast.com/show/dc-targets/en.html">LaserSoft - - - - - - - - - - - - - - - - - - - - - - + The Datacolor <a
+ href="http://spyder.datacolor.com/product-cb-spydercheckr.php">SpyderCheckr</a>:<br>
+ <br>
+ <img style=" width: 146px; height: 109px;" alt="Datacolor
+ SpyderCheckr" src="SpyderChecker.jpg"><br>
+ <br>
+ One of the QPcard's:<br>
+ <a
+ href="http://www.qpcard.com/en_b2c/color-reference-cards/qpcard201.html">QPcard @@ -1027,21 +1056,6 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm -
- Imaging DCPro Target</a>:<br>
- <br>
- <img style="width: 153px; height: 122px;" alt="LaserSoft DCPro
- Target" src="LSDC.jpg"><br>
- <br>
- The Datacolor <a
- href="http://spyder.datacolor.com/product-cb-spydercheckr.php">SpyderCheckr</a>:<br>
- <br>
- <img style=" width: 146px; height: 109px;" alt="Datacolor
- SpyderCheckr" src="SpyderChecker.jpg"><br>
- <br>
- One of the QPcard's:<br>
- <a
- href="http://www.qpcard.com/en_b2c/color-reference-cards/qpcard201.html">QPcard @@ -1069,6 +1083,9 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm +
+ 201</a>: <a
+href="http://www.qpcard.com/en_b2c/color-reference-cards/instant-camera-raw-profiling-with-qpcard-202.html">QPcard @@ -1080,9 +1097,6 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm -
- 201</a>: <a
-href="http://www.qpcard.com/en_b2c/color-reference-cards/instant-camera-raw-profiling-with-qpcard-202.html">QPcard @@ -1246,6 +1260,17 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t + + + + + + + + + + + header</a>, and appending <a href="SG_footer.txt">this footer</a>,
making sure there are no blank lines inserted in the process.
@@ -1289,8 +1314,8 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t file should be used, and the cie reference <span
style="font-weight: bold;"></span>files come with the chart.<br>
<br>
- For the Christophe Métairie's Digital Target-3 chart with 570
- patches, the <span style="font-weight: bold;">ref/CMP_Digital_Target-3.cht</span>
+ For the Christophe Métairie's Digital Target-4 chart with 570
+ patches, the <span style="font-weight: bold;">ref/CMP_Digital_Target-4.cht</span>
file should be used, and the cie reference <span
style="font-weight: bold;"></span>files come with the chart.<br>
<br>
@@ -1367,6 +1392,17 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t + + + + + + + + + + + documentation</a>).<br>
<br>
@@ -1809,6 +1845,17 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t + + + + + + + + + + + scanner or camera must be configured and used exactly the same
as it was when it was profiled.</span></big><br>
@@ -1947,6 +1994,17 @@ then + + + + + + + + + + + it can save considerable processing time and space if the -b flag is
used, and the -S flag not used.<br>
@@ -1972,6 +2030,12 @@ then If you know what colorspace your originals are in, use that as the
argument to <span style="font-weight: bold;">-S</span>.<br>
<br>
+ If your viewing environment for the display and print doesn't match
+ the ones implied by the <a href="colprof.html#c">-cmt</a> and <a
+ href="colprof.html#d">-dpp</a> options, leave them out, and
+ evaluate what, if any appearance transformation is appropriate for
+ your environment at a later stage.<br>
+ <br>
Make sure you check the delta E report at the end of the profile
creation, to see if the sample data and profile is behaving
reasonably. Depending on the type of device, and the consistency of
@@ -2062,6 +2126,17 @@ then + + + + + + + + + + + and then used <a href="xicclu.html#g">xicclu</a> to explore the
effect of the parameters.<br>
@@ -2516,6 +2591,17 @@ chart, + + + + + + + + + + + and/or to have it included in .ti3 file.<br>
<a href="cctiff.html#p2">cctiff</a> @@ -2571,6 +2657,17 @@ an + + + + + + + + + + + image file.<br>
<a href="applycal.html#p1">applycal</a> @@ -2618,6 +2715,17 @@ an + + + + + + + + + + + To incorporate calibration into an ICC profile.<br>
<a href="chartread.html#I">chartread</a> @@ -2673,6 +2781,17 @@ a + + + + + + + + + + + profile chart.<br>
<br>
@@ -2721,16 +2840,22 @@ a <br>
To apply color management and calibration to a raster image:<br>
<br>
- <a href="cctiff.html">cctiff</a> <a
- href="cctiff.html#p1">Source2Destination.icm</a> <a
- href="cctiff.html#p2">PrinterA_c.cal</a> <a href="cctiff.html#p3">infile.tif</a>
- <a href="cctiff.html#p4">outfile.tif</a><br>
+ <a href="file:///D:/src/argyll/doc/cctiff.html">cctiff</a>
+ <a href="file:///D:/src/argyll/doc/cctiff.html#p1">Source.icm</a> <a
+ href="file:///D:/src/argyll/doc/cctiff.html#p1">PrinterA.icm</a> <a
+ href="file:///D:/src/argyll/doc/cctiff.html#p2">PrinterA_c.cal</a>
+ <a href="file:///D:/src/argyll/doc/cctiff.html#p3">infile.tif</a> <a
+ href="file:///D:/src/argyll/doc/cctiff.html#p4">outfile.tif</a><br>
+ <br>
or<br>
- <a href="cctiff.html">cctiff</a> <a
- href="cctiff.html#p1">Source2Destination.icm</a> <a
- href="cctiff.html#p2">PrinterA_c.cal</a> <a href="cctiff.html#p3">infile.jpg</a>
- <a href="cctiff.html#p4">outfile.jpg</a><br>
<br>
+ <a href="file:///D:/src/argyll/doc/cctiff.html">cctiff</a>
+ <a href="file:///D:/src/argyll/doc/cctiff.html#p1">Source.icm</a> <a
+ href="file:///D:/src/argyll/doc/cctiff.html#p1">PrinterA_c.icm</a>
+ <a href="file:///D:/src/argyll/doc/cctiff.html#p3">infile.tif</a> <a
+ href="file:///D:/src/argyll/doc/cctiff.html#p4">outfile.tif</a><br>
+ <br>
+ [ Note that cctiff will also process JPEG raster images. ]<br>
<br>
Another useful tool is <a href="synthcal.html">synthcal</a>, that
allows creating linear or synthetic calibration files for disabling
@@ -2738,6 +2863,11 @@ a Similarly, <a href="fakeread.html">fakeread</a> also supports
applying calibration curves and embedding them in the resulting .ti3
file<br>
+ <br>
+ If you want to create a pre-conditioning profile for use with <a
+ href="targen.html#c">targen -c</a>, then use the PrinterA.icm
+ profile, <b>NOT</b> PrinterA_c.icm that has calibration curves
+ applied.<br>
<h4><a name="PC6"></a>How profile ink limits are handled when
calibration is being used.</h4>
Even though the profiling process is carried out on top of the
@@ -2808,6 +2938,11 @@ a <a href="collink.html#p2">DestinationProfile.icm</a> <a
href="collink.html#p3">Source2Destination.icm</a><br>
<br>
+ [ If your viewing environment for the display and print doesn't
+ match the ones implied by the <a href="colprof.html#c">-cmt</a> and
+ <a href="colprof.html#d">-dpp</a> options, leave them out, and
+ evaluate what, if any appearance transformation is appropriate for
+ your environment at a later stage. ]<br>
<br>
In <a href="collink.html#G">inverse output table gamut mapping mode</a>,
the pre-computed intent mappings inside the profiles are not used,
@@ -2848,6 +2983,53 @@ a for the type of device the profile represents, and the conditions
under which it will be viewed.<br>
<br>
+ <h3><a name="LP3"></a>Image dependent gamut mapping using device
+ links<br>
+ </h3>
+ When images are stored in large gamut colorspaces (such as. L*a*b*
+ or ProPhoto, etc.), then using the colorspace gamut as the source
+ gamut for gamut mapping is generally a bad idea, as it leads to
+ overly compressed and dull images. The correct approach is to use a
+ source gamut that represents the gamut of the images themselves.
+ This can be created using tiffgamut, and an example workflow is as
+ follows:<br>
+ <br>
+ <a href="tiffgamut.html">tiffgamut</a> -f80 -pj -cmt ProPhoto.icm
+ image.tif<br>
+ <br>
+ <a href="collink.html">collink</a> <a href="collink.html#v">-v</a>
+ <a href="collink.html#q">-qh</a> <a href="collink.html#G">-G</a> <a
+ href="collink.html#Gp">image.gam</a> <a href="collink.html#si">-ip</a>
+ <a href="collink.html#c">-cmt</a> <a href="collink.html#d">-dpp</a>
+ <a href="collink.html#p1">ProPhoto.icm</a> <a
+ href="file:///D:/src/argyll/doc/collink.html#p2">RGBDestinationProfile.icm</a>
+ <a href="file:///D:/src/argyll/doc/collink.html#p3">Source2Destination.icm</a><br>
+ <br>
+ <a href="file:///D:/src/argyll/doc/cctiff.html">cctiff</a> <a
+ href="file:///D:/src/argyll/doc/cctiff.html#p1">Source2Destination.icm</a>
+ <a href="file:///D:/src/argyll/doc/cctiff.html#p3">image.tif</a> <a
+ href="file:///D:/src/argyll/doc/cctiff.html#p4">printfile.tif</a><br>
+ <br>
+ The printfile.tif is then send to the printer without color
+ management, (i.e. in the same way the printer characterization test
+ chart was printed), since it is in the printers native colorspace.<br>
+ <br>
+ You can adjust how conservatively the image gamut is preserved using
+ the tiffgamut -f parameter. Omitting it or using a larger value (up
+ to 100) preserves the color gradations of even the lesser used
+ colors, at the cost of compressing the gamut more.<br>
+ Using a smaller value will preserve the saturation of the most
+ popular colors, at the cost of not preserving the color gradations
+ of less popular colors.<br>
+ <br>
+ You can create a gamut that covers a set of source images by
+ providing more than one image file name to tiffgamut. This may be
+ more efficient for a group of related images, and ensures that
+ colors are transformed in exactly the same way for all of the
+ images.<br>
+ <br>
+ The arguments to collink should be appropriate for the output device
+ type - see the collink examples in the above section.<br>
<h3><a name="LP2"></a>Soft Proofing Link</h3>
Often it is desirable to get an idea what a particular devices
output will look like using a different device. Typically this might
@@ -2872,6 +3054,11 @@ a the viewing conditions and assumes adaptation to the differences in
the luminence range, but otherwise not attempting to compress or
change the gamut.<br>
+ <br>
+ If your viewing environment for the display and print doesn't match
+ the ones implied by the <a href="collink.html#c">-cpp</a> and <a
+ href="collink.html#d">-dmt</a> options, then either leave them out
+ or substitute values that do match your environment.<br>
<hr size="2" width="100%"><br>
<h3><a name="TR1"></a>Transforming colorspaces of raster files</h3>
@@ -2938,16 +3125,31 @@ a </h5>
Argyll's normal test patch display will be used by default, as long
as any video encoding range considerations are dealt with (see
- Signal encoding below). An alternative when working with MadVR V
- 0.86.9 or latter, is to use the madTPG to display the patches in
- which case the MadVR video encoding range setting will operate. This
- can give some quality benefits due to MadVR's use of dithering. To
- display patches using MadVR rather than Argyll, start madTPG and
- then use the option "-d madvr" in dispcal, dispread and dispwin.
- Leave the MadTPG "VideoLUT" and "3dluts" buttons in their
- default (enabled) state, as the various tools will
- automatically take care of disabling the 3dLut and/or calibration
- curves as needed.<br>
+ Signal encoding below).<br>
+ <br>
+ An alternative when working with MadVR V 0.86.9 or latter, is to use
+ the madTPG to display the patches in which case the MadVR video
+ encoding range setting will operate. This can give some quality
+ benefits due to MadVR's use of dithering. To display patches using
+ MadVR rather than Argyll, start madTPG and then use the option "<b>-d + + +
+ madvr</b>" in dispcal, dispread and dispwin. Leave the MadTPG
+ "VideoLUT" and "3dluts" buttons in their default (enabled)
+ state, as the various tools will automatically take care of
+ disabling the 3dLut and/or calibration curves as needed.<br>
+ <br>
+ Another option is to use a <a
+ href="http://en.wikipedia.org/wiki/Chromecast">ChromeCast</a>
+ using the option "<b>-dcc</b>" in dispcal, dispread and dispwin.
+ Note that the ChromeCast as a test patch source is probably the<b>
+ least accurate</b> of your choices, since it up-samples the test
+ patch and transforms from RGB to YCC and back, but should be
+ accurate within ± 1 bit. You may have to modify any firewall to
+ permit port 8081 to be accessed on your machine if it falls back to
+ the Default receiver (see <a href="Installing.html">installation
+ instructions</a> for your platform).
<h5>2) White point calibration & neutral axis calibration.</h5>
A Device Link is capable of embodying all aspects of the
calibration, including correcting the white point and neutral axis
@@ -2982,6 +3184,17 @@ a package could be used, or ArgyllCMS <a href="dispcal.html">dispcal</a>'s + + + + + + + + + + + interactive adjustment mode can be used to set the white point.
Note that while adjusting the neutral axis for neutrality may
@@ -3004,7 +3217,18 @@ a and 3dLut will set the final response. If this approach is
taken, then the resulting calibration file should be provided to
dispread as the <a href="dispcal.html#k">-k parameter</a> or <a
- href="dispcal.html#K">-K parameter</a>. See also below <b>Choice
+ href="dispcal.html#K">-K parameter</a>. See also below <b>Choice + + + + + + + + + + +
of where to apply display per channel calibration curves.</b></li>
<li>Choose one of the Absolute Colorimetric intents in collink
(ie. -i aw). This greatly reduces flexibility, and may not be
@@ -3087,8 +3311,12 @@ a scale full range RGB values to Video levels for the TV. If the
latter is not possible, then use the -E options on dispcal and
dispread. (See <b>Signal encoding</b> bellow for more details on
- this). Don't use the -E options on dispcal and dispread if you are
- using MadVR to display test patches using the "-d madvr" option.<br>
+ this). It may also improve the accuracy of the display profile if
+ you use the <a href="dispread.html#Z">dispread -Z</a> option to
+ quantize the test values to the precision of the display
+ system. Don't use the -E options on dispcal and dispread, nor
+ the -Z option on dispread if you are using MadVR to display test
+ patches using the "-d madvr" option.<br>
<br>
Once the profile has been created, it is possible to then use the
resulting Device Link/3DLut with signal encoding other than full
@@ -3206,9 +3434,9 @@ a near black will get clipped to the display black point, loosing
shadow detail. To avoid this, some sort of black point mapping is
usually desirable. There are two mechanisms available in collink:
- a) BT.1886 black point mapping, or b) using one of the smart gamut
- mapping intents that does black point mapping (e.g. la, p, pa, ms
- or s).<br>
+ a) Custom EOTF with input and/or output black point mapping, or b)
+ using one of the smart gamut mapping intents that does black point
+ mapping (e.g. la, p, pa, ms or s).<br>
</p>
<h5>8) Viewing conditions adjustment and gamut mapping</h5>
<p> </p>
@@ -3223,30 +3451,56 @@ a practice that much video material is adjusted to look as intended
when displayed on a reference monitor having a display gamma of
somewhere between 2.2 and 2.4, viewed in a dim viewing
- environment. The modern standard covering the display transfer
- curve is <a
+ environment. The modern standard covering the display EOTF
+ (Electro-Optical Transfer Curve) is <a
href="http://www.itu.int/rec/R-REC-BT.1886-0-201103-I">BT.1886</a>,
- which defines a pure power 2.4 curve with a black point offset. So
- another means of making the viewing adjustment is to apply the
- BT.1886-like response to Rec709 encoded material. Collink supports
- this using the <a href="collink.html#I">-I b</a>, and allows some
- control over the degree of viewing conditions adjustment by
- overriding the BT.1886 gamma using the <a
- href="collink.html#Ib">-I b:g.g</a> parameter. This is the <b>recommended</b>
- approach to start with, since it gives good results with a single
- parameter.<br>
+ which defines a pure power 2.4 curve with an input offset and
+ scale applied to account for the black point offset while
+ retaining dark shadow tonality. So another means of making the
+ viewing adjustment is to use the BT.1886-like EOTF for Rec709
+ encoded material. Collink supports this using the <a
+ href="collink.html#I">-I b</a>, and allows some control over the
+ degree of viewing conditions adjustment by overriding the BT.1886
+ gamma using the <a href="collink.html#Ib">-I b:g.g</a>
+ parameter. This is the <b>recommended</b> approach to start with,
+ since it gives good results with a single parameter.<br>
</p>
+ <p>The addition of a second optional parameter <a
+ href="file:///D:/src/argyll/doc/collink.html#Ib">-I b:p.p:g.g</a>
+ allows control over the degree of black point offset accounted for
+ as an output offset, as opposed to input offset Once the effective
+ gamma value has been chosen to suite the viewing conditions and
+ set the overall contrast for mid greys, increasing the proportion
+ of black offset accounted for in the output of the curve is a way
+ of reducing the deep shadow detail, if it is being overly
+ emphasized. </p>
<p> An alternate approach to making this adjustment is to take
advantage of the viewing conditions adjustment using the CIECAM02
model available in collink. Some control over the degree of
viewing conditions adjustment is possible by varying the viewing
condition parameters. </p>
<p>A third alternative is to combine the two approaches. The source
- is defined as Rec709 rendered to a model BT.1886 display in dim
- viewing conditions, and then CIECAM02 is used to adjust for the
- actual display viewing conditions. Once again, control over the
- degree of viewing conditions adjustment is possible by varying the
- viewing condition parameters. </p>
+ is defined as Rec709 primaries with a BT.1886-like EOTF display in
+ dim viewing conditions, and then CIECAM02 is used to adjust for
+ the actual display viewing conditions. Once again, control over
+ the degree of viewing conditions adjustment is possible by varying
+ the viewing condition parameters<br>
+ </p>
+ <p><br>
+ </p>
+ <p><b>9) Correcting for any black point inaccuracy in the display
+ profile</b><br>
+ </p>
+ <p>Some video display devices have particularly good black points,
+ and any slight raising of the black due to innacuracies in the
+ display profile near black can be objectionable. As well as using
+ the <a href="targen.html#V">targen -V flag</a> to improve
+ accuracy near black during profiling, if the display is known to
+ be well behaved (ie. that it's darkest black is actually at RGB
+ value 0,0,0), then the <a href="collink.html#b">collink -b</a>
+ flag can be used, to force the source RGB 0,0,0 to map to the
+ display 0,0,0.<br>
+ </p>
<h5>Putting it all together:</h5>
In this example we choose to create a display calibration first
using dispcal, and create a simple matrix profile as well:<br>
@@ -3282,7 +3536,7 @@ a <br>
The display can then be measured:<br>
<br>
- <tt>dispread -v -k TV.cal TV</tt><br>
+ <tt>dispread -v -k -Z8 TV.cal TV</tt><br>
<br>
or using madTPG:<br>
<br>
@@ -3312,14 +3566,14 @@ a BT.1886 black point and viewing conditions adjustment, say one of
the following:<br>
<br>
- <tt> collink -v -Ib:2.4 -G -ir Rec709.icm TV.icm
+ <tt> collink -v -Ib:2.4 -b -G -ir Rec709.icm TV.icm
HD.icm # dark conditions</tt><tt><br>
- </tt><tt> collink -v -Ib -G -ir
+ </tt><tt> collink -v -Ib -b -G -ir
Rec709.icm TV.icm HD.icm # dim conditions - good
default</tt><tt><br>
- </tt><tt> collink -v -Ib:2.1 -G -ir Rec709.icm TV.icm
+ </tt><tt> collink -v -Ib:2.1 -b -G -ir Rec709.icm TV.icm
HD.icm # mid to dim conditions</tt><tt><br>
- </tt><tt> collink -v -Ib:2.0 -G -ir Rec709.icm TV.icm
+ </tt><tt> collink -v -Ib:2.0 -b -G -ir Rec709.icm TV.icm
HD.icm # mid to light conditions</tt><br>
<br>
or you could do it using pure CIECAM02 adjustment and a black point
@@ -3400,7 +3654,7 @@ a <br>
For PC use, where the encoding is full range RGB:<br>
<br>
- <tt>collink -v -3e -Ib -G -ir -a TV.cal Rec709.icm TV.icm
+ <tt>collink -v -3e -Ib -b -G -ir -a TV.cal Rec709.icm TV.icm
HD.icm </tt><br>
<br>
For correct operation both the 3DLut HD.txt and the per channel
@@ -3416,8 +3670,8 @@ a will probably be processing TV RGB levels, or YCbCr encoded signals
that it converts to/from RGB internally, so<br>
<br>
- <tt>collink -v -3e -et -Et -Ib -G -ir -a TV.cal Rec709.icm
- TV.icm HD.icm </tt><br>
+ <tt>collink -v -3e -et -Et -Ib -b -G -ir -a TV.cal
+ Rec709.icm TV.icm HD.icm </tt><br>
<br>
in this case just the HD.txt file needs installing on the eeColor,
but make sure that the original linear "first1*.txt files are
@@ -3441,10 +3695,21 @@ a normal desktop and MadVR, then it is recommended that you install
the display ICC profile and use the -H option:<br>
<br>
- <tt> collink -v -3m -et -Et -Ib -G -ir -H TV.cal
- Rec709.icm TV.icm HD.icm</tt><tt><br>
+ <tt> collink -v -3m -et -Et -Ib -b -G -ir -H
+ TV.cal Rec709.icm TV.icm HD.icm</tt><tt><br>
</tt><tt> </tt><tt><br>
- </tt><tt> collink -v -3m -et -Et -Ib -G -ir </tt><tt><tt>-H + </tt><tt> collink -v -3m -et -Et -Ib -b -G -ir </tt><tt><tt>-H + + + + + + + + + + + @@ -3458,7 +3723,18 @@ a TV.cal </tt>EBU3213_PAL.icm TV.icm SD_PAL.icm</tt><tt><br>
</tt><tt> </tt><tt><br>
- </tt><tt> collink -v -3m -et -Et -Ib -G -ir </tt><tt><tt>-H + </tt><tt> collink -v -3m -et -Et -Ib -b -G -ir </tt><tt><tt>-H + + + + + + + + + + + @@ -3476,10 +3752,21 @@ a curves using dithering, and allow it to set the graphics card to
linear by using the -a option:<br>
<br>
- <tt> collink -v -3m -et -Et -Ib -G -ir -a TV.cal
- Rec709.icm TV.icm HD.icm</tt><tt><br>
+ <tt> collink -v -3m -et -Et -Ib -b -G -ir -a
+ TV.cal Rec709.icm TV.icm HD.icm</tt><tt><br>
</tt><tt> </tt><tt><br>
- </tt><tt> collink -v -3m -et -Et -Ib -G -ir </tt><tt><tt>-a + </tt><tt> collink -v -3m -et -Et -Ib -b -G -ir </tt><tt><tt>-a + + + + + + + + + + + @@ -3493,7 +3780,18 @@ a TV.cal </tt>EBU3213_PAL.icm TV.icm SD_PAL.icm</tt><tt><br>
</tt><tt> </tt><tt><br>
- </tt><tt> collink -v -3m -et -Et -Ib -G -ir </tt><tt><tt>-a + </tt><tt> collink -v -3m -et -Et -Ib -b -G -ir </tt><tt><tt>-a + + + + + + + + + + + @@ -3544,11 +3842,12 @@ a <p> targen -v -d3 -e1 -m6 -f0 -W verify<br>
</p>
<p>We make sure there is at least one white patch usin g -e1, a 20%
- increment grid using -m6, no full spread patches, and create a
- VRML 3d visualization of the point set using the -W flag. It is
- good to take a look at the verifyd.wrl file using a VRML viewer.
- You may want to create several test sets that look at particular
- aspects, ie. neutral axis response, pure colorant responses, etc.<br>
+ increment grid using -m6, no full spread patches, and create an
+ X3DOM 3d visualization of the point set using the -W flag. It is
+ good to take a look at the verifyd.x3d.html file using a Web
+ browser. You may want to create several test sets that look at
+ particular aspects, ie. neutral axis response, pure colorant
+ responses, etc.<br>
</p>
<p>Next we create a reference file by simulating the expected
response of the perfect video display system. Assuming the collink
@@ -3556,12 +3855,12 @@ a would:<tt><tt><br>
</tt></tt></p>
<p><tt><tt> copy verify.ti1 ref.ti1<br>
- fakeread -v -b TV.icm Rec709.icm ref<br>
+ fakeread -v -b -Z8 TV.icm Rec709.icm ref<br>
</tt></tt></p>
<p>You should adjust the parameters as necessary, so that the
reference matches the link options. For instance, if your link
- options included "-I b:2.15" then the equivalent fakeread option
- "-b 2.15:TV.icm" should be used, etc.<br>
+ options included "-I b:0.2:2.15" then the equivalent fakeread
+ option "-b 0.2:2.15:TV.icm" should be used, etc.<br>
</p>
<hr size="2" width="20%">
<p>A sanity check we can make at this point is to see what the
@@ -3569,12 +3868,13 @@ a simulating the reproduction of this test set:<br>
</p>
<p><tt> copy verify.ti1 checkA.ti1</tt><tt><br>
- fakeread -v -et -p HD.icm -Et TV.icm checkA<br>
+ fakeread -v -et -Z8 -p HD.icm -Et TV.icm checkA<br>
</tt></p>
<p>If you used collink -a, then the calibration incorporated in the
device link needs to be undone to match what the display profile
expects:</p>
- <p><tt> fakeread -v -et -p HD.icm -Et -K TV.cal TV.icm checkA</tt></p>
+ <p><tt> fakeread -v -et -Z8 -p HD.icm -Et -K TV.cal TV.icm
+ checkA</tt></p>
<p><tt>and then you can verify:<br>
</tt></p>
<p><tt> colverify -v -n -w -x ref.ti3 checkA.ti3<br>
@@ -3590,10 +3890,10 @@ a <p><tt> v</tt><tt>erify -v -N -w -x ref.ti3 checkA.ti3</tt><br>
</p>
<p>This will give a numerical report of the delta E's, and also
- generate a VRML plot of the errors in L*a*b* space. The important
- thing is to take a look at the checkA.wrl file, to see if gamut
- clipping is occurring - this is the case if the large error
- vectors are on the sides or top of the gamut. Note that the
+ generate an X3DOM plot of the errors in L*a*b* space. The
+ important thing is to take a look at the checkA.x3d.html file, to
+ see if gamut clipping is occurring - this is the case if the large
+ error vectors are on the sides or top of the gamut. Note that the
perfect cube device space values become a rather distorted cube
like shape in the perceptual L*a*b* space. If the vectors are
small in the bulk of the space, then this indicates that the link
@@ -3612,22 +3912,23 @@ a </p>
<p><tt> iccgamut -ff -ia Rec709</tt><tt><br>
</tt><tt> iccgamut -ff -ia TV.icm</tt><tt><br>
- </tt><tt> viewgam -i Rec709.gam TV.gam gamuts.wrl</tt><br>
+ </tt><tt> viewgam -i Rec709.gam TV.gam gamuts</tt><br>
</p>
- <p>and look at the gamuts.wrl file, as well as taking notice of % of
- the video volume that the display intersects. The VRML solid
+ <p>and look at the gamuts.x3d.html file, as well as taking notice of
+ % of the video volume that the display intersects. The X3DOM solid
volume will be the video gamut, while the wire frame is the
display gamut. If you are not targetting D65 with your display,
you should use iccgamut <b>-ir</b> instead of <b>-ia</b>, so as
to align the white points.<br>
</p>
<hr size="2" width="20%">
- <p>The main check is to actually measure the display response and
- compare it against the reference. Make sure the display is setup
- as you would for video playback and then use dispread:<br>
+ <p>The main verification check is to actually measure the display
+ response and compare it against the reference. Make sure the
+ display is setup as you would for video playback and then use
+ dispread:<br>
</p>
<p><tt> copy verify.ti1 checkB.ti1</tt><tt><br>
- </tt><tt> dispread -v checkB</tt><br>
+ </tt><tt> dispread -v -Z8 checkB</tt><br>
</p>
<p>You would add any other options needed (such as <b>-y</b> etc.)
to set your instrument up properly. If you are using madTPG, then
diff --git a/doc/VideoEOTFs.html b/doc/VideoEOTFs.html new file mode 100644 index 0000000..526477c --- /dev/null +++ b/doc/VideoEOTFs.html @@ -0,0 +1,47 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> + <head> + <title>Video Electro Optical Transfer Functions</title> + <meta http-equiv="content-type" content="text/html; + charset=windows-1252"> + </head> + <body> + <h2><u>Video Electro-Optical Transfer Functions<br> + </u></h2> + <h3>Introduction</h3> + hgskajghjsahgjhgas <br> + <br> + <h3>Encoding verses decoding & Viewing conditions<br> + </h3> + kjshkjhsakdhakj<br> + <br> + <h3>Log-Log plots</h3> + jhjkhkjhkjhkh<br> + <br> + perceptual errors - DE2000 1 DE lines plotted on a log-log + graph <br> + <h3>"Pure Gamma" curves<br> + </h3> + They don't exist, unless your display has a perfect, zero black. But + even if it does have a perfect black, the black as seen by your eye + won't be perfect unless you are in a pitch black room and the + display is all black, because any stray light in the room or from + other non-black elements on the display will dilute the perfect + black due to glare.<br> + <br> + ksjdhiksahdkajsl<br> + <br> + <h3>Output Offset Black</h3> + <h3>Input Offset Black<br> + </h3> + sdjhkashdkjas<br> + <br> + BT.1886<br> + <br> + hjsdjhgsajgda<br> + <br> + <br> + <br> + <br> + </body> +</html> @@ -22,6 +22,7 @@ Environment.html Scenarios.html FWA.html FWA_measure.jpg +VideoEOTFs.html instruments.html ArgyllFlow.jpg ArgyllFlowThumb.jpg @@ -53,13 +54,16 @@ Chroma4.jpg ColorMunki.jpg ColorMunkiCreate.jpg i1pro2.jpg +K10A.jpg iccgamutmapping.html +3dformat.html gamutmapping1.jpg monitorcontrols.html gamma.html calvschar.html WideGamutColmters.html CrushedDisplyBlacks.html +ArgyllCMS_arts_tag.html i1proDriver.html i1proDriver.xls i1proHiRes.html @@ -136,7 +140,7 @@ SG_footer.txt i1scan14.jpg HCT.jpg CMP_DT_003.jpg -CMP_Digital_Target-3.jpg +CMP_Digital_Target-4.jpg colorchecker.jpg SpyderChecker.jpg LSDC.jpg diff --git a/doc/average.html b/doc/average.html index 31adf9b..231df92 100644 --- a/doc/average.html +++ b/doc/average.html @@ -1,43 +1,53 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> -<head> - <title>average</title> - <meta http-equiv="content-type" - content="text/html; charset=ISO-8859-1"> - <meta name="author" content="Graeme Gill"> -</head> -<body> -<h2><b>spectro/average</b></h2> -<h3>Summary</h3> -Average or merge two or more <a href="File_Formats.html#.ti3">.ti3</a> -measurement -files.<br> -<h3>Usage</h3> -<small><span style="font-family: monospace;"></span></small><small> -<span style="font-family: monospace;"></span></small><small><span - style="font-family: monospace;"></span></small><span - style="font-family: monospace;">usage: average [-options] input1.ti3 -input2.ti3 ... output.ti3</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> -v -Verbose</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> -m -Merge rather than average</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> input1.ti3 -First input file</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> input2.ti3 -Second input file</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> ... -etc.</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> output.ti3 -Resulting averaged or merged output file</span><br> -<br> -<br> -All keywords and other table data will be taken from the first input -file. By default the input files are averaged, but they can be merged -by using the <span style="font-weight: bold;">-m</span> flag.<br> -<br> -The fields must be the same and in the same order. For averaging, the -device values must be the same and in the same order.<br> -<br> -</body> + <head> + <title>average</title> + <meta http-equiv="content-type" content="text/html; + charset=windows-1252"> + <meta name="author" content="Graeme Gill"> + </head> + <body> + <h2><b>spectro/average</b></h2> + <h3>Summary</h3> + Average or merge two or more <a href="File_Formats.html#.ti3">.ti3</a> + measurement + files.<br> + If only one input file is provided, all the patches with the same + device values will be average together.<br> + <h3>Usage</h3> + <small><span style="font-family: monospace;"></span></small><small> + <span style="font-family: monospace;"></span></small><small><span + style="font-family: monospace;"></span></small><span + style="font-family: monospace;">usage: average [-options] + input1.ti3 + input2.ti3 ... output.ti3</span><br style="font-family: + monospace;"> + <span style="font-family: monospace;"> -v + Verbose</span><br style="font-family: monospace;"> + <span style="font-family: monospace;"> -m +Merge + rather than average</span><br style="font-family: monospace;"> + <span style="font-family: monospace;"> input1.ti3 +First + input file</span><br style="font-family: monospace;"> + <span style="font-family: monospace;"> input2.ti3 +Second + input file</span><br style="font-family: monospace;"> + <span style="font-family: monospace;"> ... + etc.</span><br style="font-family: monospace;"> + <span style="font-family: monospace;"> output.ti3 +Resulting + averaged or merged output file</span><br> + <br> + <br> + All keywords and other table data will be taken from the first input + file. By default the input files are averaged, but they can be + merged + by using the <span style="font-weight: bold;">-m</span> flag.<br> + <br> + The fields must be the same and in the same order. For averaging, + the + device values must be the same and in the same order.<br> + <br> + </body> </html> diff --git a/doc/ccxxmake.html b/doc/ccxxmake.html index 8ef31b7..f83afc8 100644 --- a/doc/ccxxmake.html +++ b/doc/ccxxmake.html @@ -3,7 +3,7 @@ <head> <title>ccxxmake</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> @@ -41,8 +41,7 @@ subsequent measurements on that Display using such Colorimeters, by using it with the <a href="dispcal.html#X">dispcal</a>, <a href="dispread.html#X">dispread</a> and <a href="spotread.html#X">spotread</a> - -X option, or it can be <a - href="oeminst.html">installed</a>, and + -X option, or it can be <a href="oeminst.html">installed</a>, and will then appear in the available display type selection (<b>-y</b> option).<br> <br> @@ -53,7 +52,7 @@ style="font-weight: bold;">ccmx</span> (Colorimeter Correction Matrix) files.<br> <h3>Usage Summary</h3> - <small style="font-family: monospace;">ccxxmake [-options] + <small style="font-family: monospace;">ccxxmake -t dtech [-options] correction.ccmx<br> </small><small style="font-family: monospace;"> <a href="#v">-v</a> @@ -71,6 +70,9 @@ + + + Verbose mode</small><br> <a href="#S">-S</a> Create @@ -91,6 +93,9 @@ rather + + + than CCMX<br> <a href="#f">-f file1.ti3[,file2.ti3]</a> @@ -114,6 +119,9 @@ two + + + .ti3 files rather than measure.<br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><font style="font-family: monospace;" size="-1"><a href="#display">-display @@ -132,6 +140,9 @@ two + + + displayname</a> [X11 only] Choose X11 display name</font><br style="font-family: monospace;"> <font style="font-family: monospace;" size="-1"></font><font @@ -163,6 +174,9 @@ m + + + for VideoLUT access.</font><br style="font-family: monospace;"> <font style="font-family: monospace;" size="-1"> <a href="#d">-d @@ -180,6 +194,9 @@ m + + + n</a> Choose the @@ -203,6 +220,9 @@ list + + + (default 1)</font><br> <span style="font-family: monospace;"> <a href="#dweb">-dweb[:port]</a> @@ -224,6 +244,9 @@ list + + + Display via a web server at port (default 8080)</span><br> <span style="font-family: monospace;"> <a href="#dmadvr">-dmadvr</a> @@ -236,31 +259,23 @@ list - [MSWin] Display via MadVR Video Renderer</span><br - style="font-family: monospace;"> - <font style="font-family: monospace;" size="-1"> </font><font - style="font-family: monospace;" size="-1"><a href="#p">-p</a> - - - - + [MSWin] Display via MadVR Video Renderer</span><br> + <tt> </tt><tt><a href="#dcc">-dcc[:n]</a> + </tt><tt>Display via n'th ChromeCast (default 1, ? for list)</tt><br + style="font-family: monospace;"> + <font style="font-family: monospace;" size="-1"> </font><font + style="font-family: monospace;" size="-1"><a href="#p">-p</a> - Use telephoto mode (ie. for a projector) (if available)</font><br - style="font-family: monospace;"> - <font size="-1"><span style="font-family: monospace;"><a - href="#y">-y X</a> - - @@ -273,13 +288,14 @@ list + Use telephoto mode (ie. for a projector) (if available)</font><br + style="font-family: monospace;"> + <tt></tt><tt><font size="-1"><a href="#y">-y X</a> + + - Display type - instrument specific list to choose from.</span></font><font - style="font-family: monospace;" size="-1"> (CCMX)</font><br - style="font-family: monospace;"> - <font style="font-family: monospace;" size="-1"> <a href="#P">-P @@ -295,8 +311,13 @@ list - ho,vo,ss[,vs]</a> Position test - window and scale it</font><br style="font-family: monospace;"> + Display type - instrument specific list to choose from.</font></tt><tt> + (CCMX)</tt><tt><br> + </tt><tt> <a href="#z">-z disptype</a> + Different display type for spectrometer (see -y)</tt><tt><br> + </tt><tt> </tt><tt> </tt><tt><a href="#P">-P ho,vo,ss[,vs]</a></tt><tt> + Position test window and scale it</tt><br style="font-family: + monospace;"> <font style="font-family: monospace;" size="-1"> ho,vi: 0.0 @@ -320,6 +341,9 @@ center, + + + 1.0 = right/bottom etc.</font><br style="font-family: monospace;"> <font style="font-family: monospace;" size="-1"> ss: @@ -344,6 +368,9 @@ normal, + + + 2.0 = double etc.</font><br> <font size="-1"><span style="font-family: monospace;"> @@ -355,6 +382,9 @@ normal, + + + ss,vs: = optional horizontal, vertical scale.</span></font><br style="font-family: monospace;"> <font style="font-family: monospace;" size="-1"> </font><font @@ -375,6 +405,9 @@ normal, + + + Fill whole screen with black background</font><br style="font-family: monospace;"> <small style="font-family: monospace;"> <span @@ -402,6 +435,9 @@ on + + + test window<br> </small><font style="font-family: monospace;" size="-1"> <a href="#N">-N</a> @@ -420,6 +456,9 @@ on + + + Disable initial calibration of instrument</font><small style="font-family: monospace;"> if possible<br> </small><span style="font-family: monospace;"> </span><font @@ -440,6 +479,9 @@ on + + + Use high resolution spectrum mode (if available)</font><font style="font-family: monospace;" size="-1"></font><br style="font-family: monospace;"> @@ -459,6 +501,9 @@ on + + + "command"</a> Invoke shell "command" each time a color is set<br> </font><small style="font-family: monospace;"> <a href="#o">-o @@ -491,6 +536,9 @@ sequence + + + combination steps (default 3)</font><br style="font-family: monospace;"> <font style="font-family: monospace;" size="-1"> <a href="#W">-W @@ -509,6 +557,9 @@ sequence + + + n|h|x</a> Override serial @@ -532,6 +583,9 @@ n + + + none, h = HW, x = Xon/Xoff</font><br style="font-family: monospace;"> <small style="font-family: monospace;"> <a href="#D">-D [level]</a> @@ -558,31 +612,226 @@ overall - escription</small><br> + + + + description</small><br> <small style="font-family: monospace;"> <a href="#I">-I "displayname"</a> </small><span style="font-family: monospace;">Set display make and model - description</span><small style="font-family: monospace;"><br> - </small><small style="font-family: monospace;"><a href="#T">-T + description</span><small style="font-family: monospace;"> + (optional)<br> + </small><small style="font-family: monospace;"><a href="#T">-t + + + dtech</a> + + Set display technology type<br> + + c + + + CRT<br> + + m + + + Plasma<br> + + l + + + LCD<br> + + 1 + + + LCD CCFL<br> + + 2 + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + CCFL IPS<br> + + 3 + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + CCFL VPA<br> + + 4 + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + CCFL TFT<br> + + L + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + CCFL Wide Gamut<br> + + 5 + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + CCFL Wide Gamut IPS<br> + + 6 + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + CCFL Wide Gamut VPA<br> + + 7 + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + CCFL Wide Gamut TFT<br> + + e + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + White LED<br> + + 8 + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + White LED IPS<br> + + 9 + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + White LED VPA<br> + + a + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + White LED TFT<br> + + b + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + RGB LED<br> + + b + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + RGB LED IPS<br> + + c + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + RGB LED VPA<br> + + d + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + RGB LED TFT<br> + + h + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + RG Phosphor<br> + + e + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + RG Phosphor IPS<br> + + f + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + RG Phosphor VPA<br> + + g + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LCD + RG Phosphor TFT<br> + + o + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LED + OLED<br> + + a + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>LED + AMOLED<br> + + p + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>DLP + Projector<br> + + h + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>DLP + Projector RGB Filter Wheel<br> + + i + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>DPL + Projector RGBW Filter Wheel<br> + + j + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>DLP + Projector RGBCMY Filter Wheel<br> + + u + + + </small><small style="font-family: monospace;"><small + style="font-family: monospace;"> </small>Unknown<br> + </small> <tt> <a href="#U">-U c</a> + - "displaytech"</a> </small><span - style="font-family: monospace;">Set display technology description</span> - (ie. CRT, LCD etc.)<small style="font-family: monospace;"></small><br> - <tt> <a href="#U">-U c</a> @@ -601,9 +850,15 @@ overall + + + Override refresh, non-refresh display mode</span></font><br> <tt> <a href="#YR">-Y R:<i>rate</i></a> + + + Override measured refresh rate with rate Hz</tt><br> <font size="-1"><span style="font-family: monospace;"> </span><a style=" font-family: monospace;" href="#YA">-<font size="-1">Y</font>A</a><span @@ -706,6 +961,9 @@ overall + + + 1,2</span> . Some experimentation may be needed using <a href="dispwin.html">dispwin</a> on such systems, to discover what screen has access to the VideoLUT hardware, and which screens the @@ -726,7 +984,9 @@ overall URL will be printed once the server is started, or you could run <span style="font-weight: bold;">ipconfig</span> (MSWin) or <span style="font-weight: bold;">/sbin/ifconfig</span> (Linux or OS X) - and identify an internet address for your machine that way.<br> + and identify an internet address for your machine that way. You may + have to modify any firewall to permit port 8080 to be accessed on + your machine.<br> <br> <a name="dmadvr"></a><span style="font-weight: bold;">-dmadvr</span> [MSWin only] causes test patches to be displayed using the MadVR @@ -735,6 +995,14 @@ overall rendering does not need or support VideoLUT access. Test patch colors <u>will</u> be processed by the MadVR 3dLut.<br> <br> + <a name="dcc"></a><span style="font-weight: bold;">-dcc</span> or <b>-dcc:<i>no</i></b> + causes test patches to be displayed using and available <a + href="http://en.wikipedia.org/wiki/Chromecast">ChromeCast</a> to + your TV. Use <b>-dcc:?</b> to display a list of ChromeCasts on your + local network. You may have to modify any firewall to permit port + 8081 to be accessed on your machine if it falls back to the Default + receiver.<br> + <br> <a name="p"></a>The <span style="font-weight: bold;">-p</span> flag allows measuring in telephoto mode, using instruments that support this mode, e.g. the ColorMunki. Telephoto mode is one for taking @@ -767,6 +1035,12 @@ overall Installed CCMX files will automatically select the appropriate base type.<br> <br> + <a name="z"></a>The <b>-z</b> flag allows setting a different + Display Type for the reference spectral instrument, such as refresh + or non-refresh type, if it supports it. You may have to use this if + you are setting a specific base type for the colorimeter using -y, + and the spectrometer doesn't have this display type.<br> + <br> <a name="P"></a> The <span style="font-weight: bold;">-P</span> parameter allows you to position and size the test patch window. By default it is places in the center of the screen, and sized @@ -829,6 +1103,9 @@ overall + + + of particular instruments</a> for more details. This may give better accuracy for display measurements.<br> <br> @@ -895,32 +1172,26 @@ overall included in the parameter, and not mistaken for the start of another flag, or as a final command line parameter. <br> <br> - <a name="I"></a>The <b>-I</b> parameter allows setting of the - display description string in the resulting <span + <a name="I"></a>The <b>-I</b> parameter allows optional setting of + the display description string in the resulting <span style="font-weight: bold;">ccmx/ccss</span> file. Since the default display description is probably very generic, it is <span style="font-weight: bold;">highly recommended</span> that a - description of the make and model of the display be provided here, - or set a display technology description using <span - style="font-weight: bold;">-T</span> (see below). The default or - given display description will be printed before the menu. With most - command line shells, it will be necessary to enclose the parameter - with double quotes, so that spaces and other special characters are - included in the parameter, and not mistaken for the start of another - flag, or as a final command line parameters.<br> + description of the make and model of the display be provided here. + The default or given display description will be printed before the + menu. With most command line shells, it will be necessary to enclose + the parameter with double quotes, so that spaces and other special + characters are included in the parameter, and not mistaken for the + start of another flag, or as a final command line parameters.<br> <br> - <a name="T"></a>The <b>-T</b> parameter allows setting of the - display technology description string in the resulting <span - style="font-weight: bold;">ccmx/ccss</span> file. The - applicability of the calibration mainly depends on the technology - type of the display, so a description of the technology (ie. "CRT", - "LCD", "LCD + backlight type + LCD type", etc.) is <span - style="font-weight: bold;">highly recommended</span>, because it - can make the calibration more widely usable. With most command line - shells, it will be necessary to enclose the parameter with double - quotes, so that spaces and other special characters are included in - the parameter, and not mistaken for the start of another flag, or as - a final command line parameters.<br> + <a name="T"></a>The <b>-t</b> parameter allows setting of the + display technology type from the available list. You can get a usage + that includes the list using "ccxxmake -??". This is a required + parameter, since it conveys information about the refresh type and + settling time of the display. If the specific details of the display + are not known (i.e. backlight type, pannel type etc.), then choose + the next most generic type. If none of these are applicable, choose + "Unknown".<br> <br> <a name="U"></a>The <b>-U</b> parameter allows setting of the user interface selection character this display type can be selected by, @@ -939,13 +1210,15 @@ overall + + + <b>-Y n</b> options overrides the refresh display mode set by the <a - href="spotread.html#y">-y display type - selection</a>, with <b>-Y</b><span style="font-weight: bold;"> r</span> - forcing refresh display mode, and <b>-Y n</b> forcing a non-refresh - display mode. Not all instruments support a display measurement - refresh mode, or the ability to override the mode set by the display - type selection.<br> + href="spotread.html#y">-y display type selection</a>, with <b>-Y</b><span + style="font-weight: bold;"> r</span> forcing refresh display mode, + and <b>-Y n</b> forcing a non-refresh display mode. Not all + instruments support a display measurement refresh mode, or the + ability to override the mode set by the display type selection.<br> <br> <a name="YR"></a> The -<span style="font-weight: bold;">Y R:<i>rate</i></span> options overrides calibration of the instrument refresh rate. This diff --git a/doc/collink.html b/doc/collink.html index 778b682..edd58b1 100644 --- a/doc/collink.html +++ b/doc/collink.html @@ -3,7 +3,7 @@ <head> <title>collink</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> @@ -51,6 +51,15 @@ + + + + + + + + + Verbose<br> </span></small><small><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#A">-A "manufacturer"</a><span @@ -105,6 +114,15 @@ existing + + + + + + + + + profile, rather than link (Debug option)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -143,6 +161,15 @@ clut + + + + + + + + + res. set by -q</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#n">-n</a><span @@ -175,6 +202,15 @@ preserve + + + + + + + + + device curves in result</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -232,6 +268,15 @@ Include + + + + + + + + + abstract profile in link</span></small><br> <small><span style="font-family: monospace;"><small><span style="font-family: monospace;"> </span><a @@ -242,6 +287,15 @@ Include <a href="H">-H file.cal</a> + + + + + + + + + Append calibration curves to 3dlut<br style="font-family: monospace;"> </span> <span style="font-family: monospace;"> </span><a @@ -275,6 +329,15 @@ Mode + + + + + + + + + (default)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#g">-g [src.gam]</a><span @@ -311,6 +374,15 @@ Gamut + + + + + + + + + Mapping Mode using inverse outprofile A2B [optional source gamut]</span><br style="font-family: monospace;"> <br style="font-family: monospace;"> @@ -351,6 +423,15 @@ s + + + + + + + + + = saturation, a = absolute colorimetric</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -388,6 +469,15 @@ s + + + + + + + + + = saturation, a = absolute colorimetric</span><br style="font-family: monospace;"> <br style="font-family: monospace;"> @@ -428,6 +518,15 @@ a + + + + + + + + + Absolute Colorimetric (in Jab) [ICC Absolute Colorimetric]<br> aw @@ -458,6 +557,15 @@ aw + + + + + + + + + Absolute Colorimetric (in Jab) with scaling to fit white point<br style="font-family: monospace;"> </span><span style="font-family: monospace;"> @@ -489,6 +597,15 @@ aa + + + + + + + + + Absolute Appearance</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> r @@ -519,6 +636,15 @@ r + + + + + + + + + White Point Matched Appearance [ICC Relative Colorimetric]</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -550,6 +676,15 @@ la + + + + + + + + + Luminance matched Appearance</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -581,6 +716,15 @@ p + + + + + + + + + Perceptual (Preferred) [ICC Perceptual]<br> </span></small><small><span style="font-family: monospace;"> pa @@ -610,6 +754,15 @@ pa + + + + + + + + + - Perceptual Appearance</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"></span><span @@ -642,6 +795,15 @@ ms + + + + + + + + + Saturation</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> s @@ -672,6 +834,15 @@ s + + + + + + + + + Enhanced Saturation [ICC Saturation]</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -703,6 +874,15 @@ al + + + + + + + + + Absolute Colorimetric (Lab)<br> @@ -726,15 +906,32 @@ al + + + + + + + + + rl - White Point Matched Colorimetric (Lab)</span><span style="font-family: monospace;"></span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#w">-w [J,a,b]</a><span style="font-family: monospace;"> Use forced - whitepoint hack [optional color to map the white to]</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;"> </span><a + whitepoint hack [optional color to map the white to]<br> + <a href="#b">-b</a> + + + + + + + Use RGB->RGB forced black point hack<br style="font-family: + monospace;"> + </span> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#c">-c <i>viewcond</i></a><span style="font-family: monospace;"> set source viewing conditions for CIECAM02,</span><br style="font-family: @@ -768,6 +965,15 @@ either + + + + + + + + + an enumerated choice, or a parameter</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -804,6 +1010,15 @@ either + + + + + + + + + an enumerated choice, or a parameter:value change<br> </span></small><small><span style="font-family: monospace;"> pp - Practical @@ -838,6 +1053,15 @@ either + + + + + + + + + pe - Print evaluation environment (CIE 116-1995)<br> </span></small><small><span style="font-family: monospace;"> @@ -868,6 +1092,15 @@ either + + + + + + + + + pc - Critical print evaluation environment (ISO-3664 P1)</span></small><small><span style="font-family: monospace;"></span><span style="font-family: monospace;"></span><span style="font-family: monospace;"></span><span @@ -906,6 +1139,15 @@ either + + + + + + + + + mb - Monitor in bright work environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -955,6 +1197,15 @@ n + + + + + + + + + = auto, a = average, m = dim, d = dark,</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -986,6 +1237,15 @@ n + + + + + + + + + c = transparency (default average)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -1017,6 +1277,15 @@ Adapted + + + + + + + + + white point as XYZ (default media white)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -1048,6 +1317,15 @@ Adapted + + + + + + + + + white point as x, y</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> a:adaptation @@ -1078,6 +1356,15 @@ Adaptatation + + + + + + + + + luminance in cd.m^2 (default 50.0)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -1110,6 +1397,15 @@ Background + + + + + + + + + of image luminance (default 20)<br> l:imagewhite Image white in cd.m^2 if surround = auto (default 250)</span></small><br @@ -1145,6 +1441,15 @@ light + + + + + + + + + % of image luminance (default 0)<br> </span></small> </span><span style="font-family: monospace;"> @@ -1166,6 +1471,15 @@ light + + + + + + + + + g:X:Y:Z Glare color as XYZ (default media white)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -1184,6 +1498,15 @@ light + + + + + + + + + g:x:y Glare color as x, y</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -1217,6 +1540,15 @@ source + + + + + + + + + total ink limit, 0 - 400% (estimate by default)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -1250,6 +1582,15 @@ source + + + + + + + + + total ink limit, 0 - 100% (estimate by default)</span><br style="font-family: monospace;"> <br style="font-family: monospace;"> @@ -1290,6 +1631,15 @@ t + + + + + + + + + = transfer K from source to destination, e = retain K of destination B2A table</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -1321,6 +1671,15 @@ z + + + + + + + + + = zero K, h = 0.5 K, x = maximum K, r = ramp K (default)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -1355,6 +1714,15 @@ p + + + + + + + + + = black level generation curve parameters</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -1390,6 +1758,15 @@ q + + + + + + + + + = transfer source K to dual curve limits</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -1428,6 +1805,15 @@ destination + + + + + + + + + total ink limit, 0 - 400% (estimate by default)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -1461,6 +1847,15 @@ destination + + + + + + + + + total ink limit, 0 - 100% (estimate by default)<br> <a href="#3">-3 flag</a> @@ -1483,6 +1878,15 @@ destination + + + + + + + + + Create "3DLut" output file as well as devlink<br> e @@ -1506,6 +1910,15 @@ destination + + + + + + + + + eeColor .txt file</span></small><br> <tt> m @@ -1517,9 +1930,17 @@ destination + + + + + + + + + MadVR .3dlut file</tt><br> - <small><span style="font-family: monospace;"><small><span - style="font-family: monospace;"> <a href="#Ib">-I b</a> + <tt> <a href="#Ib">-I B</a> @@ -1527,6 +1948,23 @@ destination + Use BT.1886 source EOTF with technical gamma 2.4</tt><tt><br> + </tt><tt> <a href="#Ib">-I b:g.g</a> + Use + BT.1886-like source EOTF with effective gamma g.g</tt><tt><br> + </tt><tt><a href="#Ib">-I b:p.p:g.g</a> + Use effective gamma g.g source EOTF + with p.p prop. output black point offset</tt><small><span + style="font-family: monospace;"><small><span style="font-family: + monospace;"></span></small></span></small><br> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"><tt> <a + href="file:///D:/src/argyll/doc/collink.html#Ib">-I + g:g.g</a> + Use + effective gamma g.g source EOTF with all output black + point offset</tt><br> + </span></small> <a href="#e">-e flag</a> @@ -1540,10 +1978,6 @@ destination - Apply BT.1886-like mapping with effective gamma 2.2 to input</span></small><br> - <small><span style="font-family: monospace;"><small><span - style="font-family: monospace;"> <a href="#Ib">-I - b:g.g</a> @@ -1557,13 +1991,11 @@ destination - Apply BT.1886-like mapping with effective gamma g.g to - input<br> - </span></small></span></small> <a href="#IB">-I B</a> - + Video encode input as:<br> + <a href="#E">-E flag</a> @@ -1574,9 +2006,6 @@ destination - Apply BT.1886 mapping with technical gamma 2.4 to input</span></small><br> - <small><span style="font-family: monospace;"><small><span - style="font-family: monospace;"> <a href="#IB">-I B:g.g</a> @@ -1590,14 +2019,17 @@ destination - Apply BT.1886-like mapping with technical gamma g.g to input<br> - </span></small> <a href="#e">-e flag</a> + Video encode output as:</span></small><small><span + style="font-family: monospace;"><small><span style="font-family: + monospace;"><br> + + n @@ -1612,12 +2044,13 @@ destination - Video encode input as:<br> - <a href="#E">-E flag</a> + normal RGB 0..1 levels (default)<br> + + t @@ -1634,13 +2067,15 @@ destination - Video encode output as:</span></small><small><span - style="font-family: monospace;"><small><span style="font-family: - monospace;"><br> - - n + RGB (16-235)/255 "TV" levels</span></small></span></small><br> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"><small><span + style="font-family: monospace;"><small><span + style="font-family: monospace;"> + T + @@ -1648,9 +2083,6 @@ destination - normal RGB 0..1 levels (default)<br> - - t @@ -1660,7 +2092,9 @@ destination - RGB (16-235)/255 "TV" levels<br> + + + RGB (16-235)/255 "TV" levels, clip WTW [Input Only]</span></small></span></small><br> 6 @@ -1672,6 +2106,15 @@ destination + + + + + + + + + Rec601 YCbCr SD (16-235,240)/255 "TV" levels<br> 7 @@ -1684,6 +2127,15 @@ destination + + + + + + + + + Rec709 1125/60Hz YCbCr HD (16-235,240)/255 "TV" levels<br> 5 @@ -1696,6 +2148,15 @@ destination + + + + + + + + + Rec709 1250/50Hz YCbCr HD (16-235,240)/255 "TV" levels<br> 2 @@ -1708,6 +2169,15 @@ destination + + + + + + + + + Rec2020 YCbCr UHD (16-235,240)/255 "TV" levels<br> C @@ -1720,6 +2190,15 @@ destination + + + + + + + + + Rec2020 Constant Luminance YCbCr UHD (16-235,240)/255 "TV" levels<br> @@ -1733,6 +2212,15 @@ destination + + + + + + + + + xvYCC Rec601 YCbCr Rec709 Prims. SD (16-235,240)/255 "TV" levels<br> @@ -1746,6 +2234,15 @@ destination + + + + + + + + + xvYCC Rec709 YCbCr Rec709 Prims. HD (16-235,240)/255 "TV" levels<br> </span></small> </span></small> <small><span @@ -1779,7 +2276,16 @@ gamut - gammap_p.wrl and gammap_s.wrl diagostics</span></small><small><br> + + + + + + + + + + gammap_p.x3d.html and gammap_s.x3d.html diagostics</span></small><small><br> <span style="font-family: monospace;"></span></small><span style="font-family: monospace;"> <span style="text-decoration: underline;"><span style="font-style: @@ -1814,6 +2320,15 @@ ICC + + + + + + + + + profile. A </span><small><span style="font-family: monospace;">TIFF @@ -1841,6 +2356,15 @@ ICC + + + + + + + + + or JPEG file with embedded profile may be used here.</span></small><br style="font-family: monospace;"> <span style="font-family: monospace;"><span @@ -1876,6 +2400,15 @@ ICC + + + + + + + + + profile. </span><span style="font-family: monospace;">A </span><small><span style="font-family: monospace;">TIFF or JPEG file with embedded profile may be used here.</span></small><br style="font-family: @@ -1972,6 +2505,15 @@ ICC + + + + + + + + + Override clut res. set by <b>-q</b><br> <br> This sets the basic quality of the resulting link, by choosing the @@ -2108,26 +2650,22 @@ ICC the <a href="tiffgamut.html"> tiffgamut</a> tool. More <a href="#GG">details</a> about the gamut mapping, inverse AtoB mode.<br> <br> - The gamut provided to the <span style="font-weight: bold;">-g</span> - or <span style="font-weight: bold;">-G</span> flag should be in the - same colorspace that <span style="font-weight: bold;">collink</span> - is using internally to connect the two profiles. For all intents - except the last one (no. <span style="font-weight: bold;">7</span>), - - - - - - - - - - - - - - - + <a name="Gp"></a>The gamut provided to the <span + style="font-weight: bold;">-g</span> or <span style="font-weight: + bold;">-G</span> flag should be in the same colorspace that <span + style="font-weight: bold;">collink</span> is using internally to + connect the two profiles. For all intents except the last one (no. <span + style="font-weight: bold;">7</span>), the space should be Jab + appearance space, with the viewing conditions generally being those + of the source profile viewing conditions. The source profile will + normally be the one used to create a source image gamut using <span + style="font-weight: bold;">tiffgamut</span>.<br> + <br> + <u><a name="ss"></a> Simple mode gamut mapping options:</u><br> + <br> + <a name="si"></a> <b>-i</b> <i>in_intent</i> + + @@ -2139,18 +2677,6 @@ ICC - the space should be Jab appearance space, with the viewing - conditions generally being those of the source profile viewing - conditions. The source profile will normally be the one used to - create a source image gamut using <span style="font-weight: bold;">tiffgamut</span>.<br> - <br> - <u><a name="ss"></a> Simple mode gamut mapping options:</u><br> - <br> - <a name="si"></a> <b>-i</b> <i>in_intent</i> - - - - @@ -2307,6 +2833,13 @@ ICC in fine tuning paper emulation in absolute colorimetric mapping mode.<br> <br> + <a name="b"></a> The <b>-b</b> flag forces RGB source 0,0,0 to map + to RGB destination 0,0,0. This may be useful for Video + proofing/calibration purposes, where the source is a standard + colorspace such as Rec709, and the display device is well behaved + with black at 0,0,0. By forcing the black mapping, any slight + raising of the black due to display profile tolerances is avoided.<br> + <br> <a name="c"></a><a name="d"></a> The <b>-c</b> and <b>-d</b> options allow specification of the viewing conditions for the source and destination colorspaces respectively. The viewing condition @@ -2415,6 +2948,15 @@ ICC + + + + + + + + + _______ enle<br> | @@ -2445,6 +2987,15 @@ ICC + + + + + + + + + /<br> | @@ -2475,6 +3026,15 @@ ICC + + + + + + + + + /<br> | @@ -2505,6 +3065,15 @@ ICC + + + + + + + + + /<br> | @@ -2535,6 +3104,15 @@ ICC + + + + + + + + + /<br> stle | ------/<br> @@ -2571,6 +3149,15 @@ White &nb + + + + + + + + + Black<br> <br> </tt>For minimum sensitivity of printed output to the lighting @@ -2698,15 +3285,78 @@ White &nb There is more information on the <a href="Scenarios.html">Typical Usage Scenarios</a> page.<br> <b><br> - <a name="Ib"></a></b>The <b>-I b</b> flag applies extra input - processing, applying <a - href="http://www.itu.int/rec/R-REC-BT.1886-0-201103-I">BT.1886</a>-like + <a name="Ib"></a></b>The <b>-I [b|B|g|G][:p.p][:g.g]</b> series + of options, substitutes an alternative EOTF (Electro-Optical + Transfer Function) for the one specified by the matrix input + profile. This is typically used for creating Video display + emulations.<br> + <br> + The basic curve is a pure power curve with scaling and a combination + of input black offset and/or output black offset. The choice of flag + determines the way the power value is interpreted, and the default + balance between input and output black offset handling.<br> + <br> + The lower case <b>b</b> and <b>g</b> flags use an effective power + value specification, where the 50% input maps to the same output + value as a pure power curve with a perfect black. These are the + recommended flags to use, since this means that the overall contrast + of the reproduction will not be affected so much by differences and + variations in the black level, or how the black level is accounted + for. The default effective power value is 2.2.<br> + <br> + The upper case <b>B</b> and <b>G</b> flags use a technical power + value specification, where the power value is the actual one that + will be used. The end result will vary much more with the black + level of the display though. The default technical power value is + 2.4.<br> + <br> + The <b>b</b> and <b>B</b> flags default to the black level being + accounted for as a full input offset, where the power curve is + shifted and scaled to match the black point, preserving the black + shadow tonality. This is what <a + href="http://www.itu.int/rec/R-REC-BT.1886-0-201103-I">BT.1886</a> + uses.<br> + <br> + The <b>g</b> and <b>G</b> flags default to the black level being + accounted for as a full output offset, where the power curve is + scaled to allow for the black point, losing some black shadow + tonality with higher black points. This is what many people think of + as a "pure" power curve, even though this is not possible unless the + display has a perfect zero black level.<br> + <br> + The optional <b>:g.g</b> value is the power to be used. This will + be an effective value if the <b>b</b> or <b>g</b> flags is used, + or the technical value if the <b>B</b> or <b>G</b> flag is used. + This is the primary way to make an allowance for the brightness of + the viewing environment for Video . Darker viewing environments + probably need a larger gamma value, while lighter viewing + environments probably need a lower value.<br> + <br> + The second optional <b>:p.p</b> value is the proportion of black + value that should be accounted for as output offset (the gamma value + must also be specified after this). This defaults to 0.0 for the <b>b</b> + and <b>B</b> flags, and 1.0 for the <b>g</b> and <b>G</b> flags, + but by specifying it explicitly as a value between 0.0 and 1.0, a + hybrid curve characteristic can be obtained. Setting a hybrid value + is a way of maintaining black shadow tonality while being able to + control how much detail is retained in those shadows. An appropriate + value may depend on exactly how the video material was mastered.<br> + <br> + Illustrative combinations are:<br> + <br> + <b>-I b</b><b> + </b>Full + input offset (BT.1886 like) with effective gamma of 2.2<b><br> + </b><b>-I g</b><b> + + </b>Full output offset with effective gamma of 2.2<b><br> + </b><b></b><b>-I B</b><b> @@ -2714,41 +3364,107 @@ White &nb - video gamma mapping using an effective gamma of 2.2 by default, and - overridable using <b>-I b:g.g</b> where <b>g.g</b> is the gamma. - The gamma is an effective gamma, meaning that its effect on 50% - input is the same as that of a pure power curve, in spite of any - black offset added by BT.1886. This has the benefit of making the - overall effect of brightness independent of the black level of the - display. Setting an effective gamma other than 2.2 is one way of - making the viewing condition adjustment for the different conditions - of video encoding and decoding, or for modelling the source - colorspace as a rendering on a video display. This would be used as - an alternative to using gamut mapping mode and setting explicit - input and output viewing conditions, or in combination with - appearance adjustments. BT.1886 will only work with matrix type - input profiles. The default value of 2.2 is probably suitable for - dim viewing conditions, and it may be desirable to override this - default if your viewing conditions are darker or lighter. For - lighter conditions, try "-I b:2.2". For darker conditions, try "-I - b:2.6".<br> + </b>Full input offset (BT.1886 like) with technical gamma of 2.4. + This exactly implements the BT.1886 specification.<b><br> + </b><b>-I G</b> + + + + + + + + Full output offset with technical gamma of 2.2<br> <br> - <b><a name="IB"></a></b>The <b>-I B</b> flag applies extra input - processing, applying <a - href="http://www.itu.int/rec/R-REC-BT.1886-0-201103-I">BT.1886</a> - video gamma mapping using the BT.1886 gamma of 2.4 by default, and - overridable using <b>-I b:g.g</b> where <b>g.g</b> is the gamma. - The gamma is the technical gamma, or power applied to the input - image, and this means that its effect on 50% input will depend on - the black level of the display, making the overall brightness - somewhat unpredictable. For a more predictable effect, use <b>-I b</b>.<br> + <b>-I b</b><b>:2.3</b><b> + + + + + + + + </b>Full input offset (BT.1886 like) with effective gamma of 2.3<b> + <br> + </b><b> -I g:2.3</b><b> + + + + + + + + </b>Full output offset with effective gamma of 2.3<b><br> + </b><b> -I B:2.35</b><b> + + + + + + + + </b>Full input offset (BT.1886 like) with technical gamma of 2.35<br> + <b> -I G:2.35</b> + + + + + + + + Full output offset with technical gamma of 2.35<br> + <br> + <b>-I b</b><b>:0.4:2.3</b> + 60% input offset, 40% output offset with effective gamma of 2.3<b></b><br> + <b> -I g:0.4:2.3</b><b> </b> + + + + + + + + Same as above.<b><br> + </b><b> -I B:0.4:2.35</b> 60% input + offset, 40% output offset with technical gamma of 2.35 <b><br> + </b><b> -I G:0.4:2.35</b> Same as + above.<br> <b><br> <a name="e"></a></b>The <b>-e</b> <i>flag</i> applies a Video encoding to the input. See below<b> and</b> <a href="#E"><b>-E</b></a> for the list of encodings.<br> <br> + <br> <small><span style="font-family: monospace;"><small><span - style="font-family: monospace;"> + style="font-family: monospace;"><small><span + style="font-family: monospace;"><small><span + style="font-family: monospace;"><small><span + style="font-family: monospace;"><small><span + style="font-family: monospace;"> + T + + + + + + + + + + + + + + + + + + + + RGB (16-235)/255 "TV" levels, clip WTW + [Input Only]<br> + </span></small></span></small></span></small></span></small> + x @@ -2759,6 +3475,15 @@ White &nb + + + + + + + + + xvYCC Rec601 YCbCr Rec709 Prims. SD (16-235,240)/255 "TV" levels<br> @@ -2772,6 +3497,15 @@ White &nb + + + + + + + + + xvYCC Rec709 YCbCr Rec709 Prims. HD (16-235,240)/255 "TV" levels</span></small></span></small><br> <br> @@ -2785,6 +3519,13 @@ White &nb as UHD Rec2020, or Digital Cinema SMPTE431 P3, then the corresponding ICC profile should be provided as the source profile.<br> <br> + The <b>-e T</b> option uses the same encoding as <b>-e t</b>, but + rather than handling WTW (Whiter Than White, or out of range values) + using extrapolation, it clips them to the valid range. This can be + useful if you are dealing with source material that has WTW values, + but your TV or Video display clips these out of range values in a + way that alters the hue.<br> + <br> <b><a name="E"></a></b>The <b>-E</b> <i>flag</i> applies a Video encoding to the output. The possible encoding are:<br> <br> @@ -2800,6 +3541,15 @@ White &nb + + + + + + + + + normal RGB 0..1 full range levels (default)<br> t @@ -2812,8 +3562,22 @@ White &nb - RGB (16-235)/255 "TV" levels<br> - + + + + + + + + + + RGB (16-235)/255 "TV" levels</span></small></span></small><small><span + style="font-family: monospace;"><small><span style="font-family: + monospace;"></span></small></span></small><br> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"><small><span + style="font-family: monospace;"></span></small> + 6 @@ -2824,6 +3588,15 @@ White &nb + + + + + + + + + Rec601 YCbCr SD (16-235,240)/255 "TV" levels<br> 7 @@ -2836,6 +3609,15 @@ White &nb + + + + + + + + + Rec709 1125/60Hz YCbCr HD (16-235,240)/255 "TV" levels<br> 5 @@ -2848,6 +3630,15 @@ White &nb + + + + + + + + + Rec709 1250/50Hz YCbCr HD (16-235,240)/255 "TV" levels<br> 2 @@ -2860,6 +3651,15 @@ White &nb + + + + + + + + + Rec2020 YCbCr UHD (16-235,240)/255 "TV" levels<br> C @@ -2872,12 +3672,22 @@ White &nb + + + + + + + + + Rec2020 Constant Luminance YCbCr UHD (16-235,240)/255 "TV" - levels<br> - </span></small></span></small><br> - <br> + levels</span></small></span></small><br> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"></span></small></span></small><br> + The <b>T</b> <br> <b><a name="P"></a></b>The <b>-P</b> option causes a diagnostic 3D - <a href="File_Formats.html#VRML">VRML</a> plots to be created that + <a href="File_Formats.html#X3DOM">X3DOM</a> plots to be created that illustrate the gamut mapping generated.<br> <br> <a name="p1"></a>The <i><b>inprofile</b></i> argument specifies the @@ -2921,6 +3731,15 @@ White &nb + + + + + + + + + Usage Scenarios</a> page.<br> <br> <br> diff --git a/doc/colprof.html b/doc/colprof.html index 022f984..b3b6df2 100644 --- a/doc/colprof.html +++ b/doc/colprof.html @@ -38,6 +38,14 @@ + + + + + + + + Verbose mode<br> <a href="#A">-A "manufacturer"</a> Set the manufacturer description string<br> @@ -66,6 +74,14 @@ + + + + + + + + Default intent: Perceptual, Rel. Colorimetric, Saturation, Abs. Colorimetric</small></tt><tt><br> @@ -99,6 +115,14 @@ + + + + + + + + Don't create input (Device) shaper curves<br> </small></tt><tt><small> <a href="#np">-np</a> @@ -128,13 +152,22 @@ + + + + + + + + Don't create output (PCS) shaper curves<br> </small></tt><tt><small> <a href="#nc">-nc</a> Don't put the input .ti3 data in the profile</small></tt><tt><br> </tt><tt> </tt><tt><small> <a href="#k">-k zhxr</a> - Black generation: z = zero K,<br> + Black Ink generation: z = + zero K,<br> @@ -170,6 +203,14 @@ x + + + + + + + + max K, r = ramp K<br> <a href="#kp">-k p stle stpo enpo enle shape</a><br> @@ -206,6 +247,14 @@ White + + + + + + + + - 1.0<br> @@ -242,6 +291,14 @@ Wh + + + + + + + + 0.0 - Bk 1.0<br> @@ -278,6 +335,14 @@ Wh + + + + + + + + 0.0 - Bk 1.0<br> @@ -313,6 +378,14 @@ Black + + + + + + + + 0.0 - 1.0<br> @@ -349,6 +422,14 @@ concave, + + + + + + + + 1.0-2.0 convex<br> <a href="#K">-K parameters</a> @@ -365,6 +446,14 @@ concave, + + + + + + + + Same as -k, but target is K locus rather than K value itself<br> <a href="#l">-l <i>tlimit</i></a> override CMYK total ink limit, 0 - 400% @@ -408,6 +497,14 @@ cLUT + + + + + + + + x = XYZ cLUT, X = display XYZ cLUT + matrix<br> @@ -443,6 +540,14 @@ s + + + + + + + + shaper+matrix, m = matrix only,<br> @@ -479,6 +584,14 @@ S + + + + + + + + single shaper+matrix<br> <a href="#u">-u</a> @@ -500,6 +613,14 @@ S + + + + + + + + If input profile, auto scale WP to allow extrapolation</small></tt><tt><br> </tt><tt> </tt><tt><small><small> <a href="#uc">-uc</a> @@ -538,12 +659,36 @@ and + + + + + + + + primaries to be +ve</tt><tt><br> + <a href="#B">-B X,Y,Z</a> + + + + + + + Display Black Point override hack<br> <a href="#V">-V demphasis</a> + + + + + + + + Degree of dark region cLUT grid emphasis 1.0-3.0 (default 1.00 = none)<br> </tt><tt> </tt><tt><small><small><a href="#f">-f [<i>illum</i>]</a> @@ -563,6 +708,14 @@ and + + + + + + + + M0, M1, M2, </small></small></tt><tt><small><small><small>A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp ]</small></small></small></tt><tt><br> </tt><tt><small><small><small><small> <a href="#i">-i <i>illum</i></a> @@ -579,6 +732,14 @@ and + + + + + + + + Choose illuminant for computation of CIE XYZ from spectral data & FWA:<br> @@ -605,6 +766,14 @@ D50M2, + + + + + + + + D65, F5, F8, F10 or file.sp</small></small></small><br> <a href="#o">-o <i>observ</i></a> Choose CIE Observer for spectral data:<br> @@ -632,6 +801,14 @@ D50M2, + + + + + + + + 1931_2 </small></tt><tt><small>(def.)</small></tt><tt><small>, 1964_10, S&B 1955_2, shaw, J&V 1978_2<br> <a href="#r">-r avgdev</a> @@ -671,6 +848,14 @@ for + + + + + + + + given source<br> <a href="#S">-S src.icc</a> @@ -696,6 +881,14 @@ for + + + + + + + + Apply gamut mapping to output profile perceptual and saturation B2A table<br> <a href="#nP">-nP</a> @@ -722,6 +915,14 @@ for + + + + + + + + Use colormetric source gamut to make output profile perceptual table<br> <a href="#nS">-nS</a> @@ -748,6 +949,14 @@ for + + + + + + + + Use colormetric source gamut to make output profile saturation table<br> <a href="#g">-g src.gam</a> @@ -782,6 +991,14 @@ for + + + + + + + + Override gamut mapping intent for output profile saturation table:<br> </small></tt><tt><small> @@ -824,6 +1041,14 @@ for + + + + + + + + pa - Perceptual Appearance</small></tt><tt><br> </tt><tt> </tt><tt><small> @@ -849,6 +1074,14 @@ for + + + + + + + + ms - Saturation<br> s - Enhanced Saturation [ICC @@ -867,6 +1100,14 @@ for + + + + + + + + rl - White Point Matched Colorimetric (Lab)<br> <a href="#c">-c viewcond</a> @@ -892,6 +1133,14 @@ for + + + + + + + + set input viewing conditions for output profile CIECAM02 gamut mapping,<br> @@ -918,6 +1167,14 @@ for + + + + + + + + either an enumerated choice, or a parameter<br> <a href="#d">-d viewcond</a> @@ -943,6 +1200,14 @@ for + + + + + + + + set output viewing conditions for output profile CIECAM02, gamut mapping<br> @@ -969,6 +1234,14 @@ for + + + + + + + + either an enumerated choice, or a parameter:value change<br> @@ -994,6 +1267,14 @@ for + + + + + + + + Also sets out of gamut clipping CAM space.<br> @@ -1019,6 +1300,14 @@ for + + + + + + + + Enumerated Viewing Conditions:<br> </small></tt><tt><small> pp - Practical Reflection Print (ISO-3664 @@ -1073,6 +1362,14 @@ for + + + + + + + + c = transparency (default average)<br> @@ -1111,6 +1408,14 @@ for + + + + + + + + g:glare Glare light % of ambient (default 1)</span><br style="font-family: monospace;"> @@ -1150,7 +1455,15 @@ for - Create gamut gammap_p.wrl and gammap_s.wrl diagostics<br> + + + + + + + + + Create gamut gammap_p.x3d.html and gammap_s.x3d.html diagostics<br> </small></tt><tt><small> <a href="#O">-O outputfile</a> Override @@ -1176,6 +1489,14 @@ Override + + + + + + + + the default output filename & extension.</small></tt><tt><br> </tt><tt> </tt><tt><small> <a href="#p1"><i>inoutfile</i></a> Base name for @@ -1322,6 +1643,14 @@ the + + + + + + + + device and CIE/spectral sample data and calibration curves used to create a profile is stored in the <span style="font-weight: bold;">'targ'</span> text tag in the resulting ICC profile. To suppress this and make the @@ -1348,6 +1677,14 @@ the + + + + + + + + </span>flag. <span style="font-weight: bold;">Note</span> that this will then preclude final calibrated device value ink limits from being computed for the resulting profile in subsequent use (ie. <a @@ -1409,6 +1746,14 @@ the + + + + + + + + | _______ enle<br> @@ -1435,6 +1780,14 @@ the + + + + + + + + | /<br> @@ -1460,6 +1813,14 @@ the + + + + + + + + | /<br> @@ -1485,6 +1846,14 @@ the + + + + + + + + | /<br> @@ -1510,6 +1879,14 @@ the + + + + + + + + | /<br> stle | ------/<br> @@ -1543,6 +1920,14 @@ White &nb + + + + + + + + Black<br> </tt> <br> For minimum sensitivity of printed output to the lighting spectrum, @@ -1708,6 +2093,26 @@ White &nb black and primary values, so as to work with these programs, but this will reduce the accuracy of the profile.<br> <br> + <b><a name="B"></a>-B X,Y,Z</b> This option is for display profiles + only, and allows overriding the black point of the resulting + profile. The XYZ value is in absolute instrument measurement units. + This option should be used only in special circumstances, for + instance if the display has a very low black point and the + instrument is not capable of measuring the black point accurately or + consistently. In this case a manual estimate of the black point + could be made and provided as the argument to -B. It may also be + useful for displays with black points that approach perfect black + (ie. Plasma or OLED) where a value of 0,0,0 may be more accurate + than typical instrument measurements. A value that is too different + to the default computed black point will likely result in a profile + with strange behavior near black.<br> + <b>Note</b> that the default contents of the .ti3 created by <a + href="dispread.html">dispread</a> is normalised to be 100 for the + white point Y value, and similarly values returned by icclu -ia -px + are normalized to a white Y value of 1.0, which is not what the <b>-B</b> + option expects, so some care needs to be taken in specifying and + evaluating the resulting black point XYZ values.<br> + <br> <a name="V"></a>The <b>-V demphasis</b> parameter allows sets the degree to which cLUT grid spacing should emphasize the accuracy of modelling the device response in the dark regions, over that of the @@ -1735,14 +2140,14 @@ White &nb Ultra Violet to the one the instrument actually used in the measurement. There are two ways this can be used:<br> <br> - The first and most common is to use the <b>-f</b> flag with the <b>-i</b> - illuminant parameter, to make the color values more accurately - reflect their appearance under the viewing illuminant. This will - work accurately if you specify the <span style="text-decoration: - underline;">actual illuminant spectrum you are using to view the - print</span>, using the <span style="font-weight: bold;"><span - style="font-weight: bold;">-i</span></span> flag. If you are - doing proofing, you need to apply this to <span + <b>The first and most useful</b> is to use the <b>-f</b> flag with + the <b>-i</b> illuminant parameter (i.e. "<b>-f -i D50"</b>), to + make the color values more accurately reflect their appearance under + the viewing illuminant. This will work accurately if you specify the + <span style="text-decoration: underline;">actual illuminant spectrum + you are using to view the print</span>, using the <span + style="font-weight: bold;"><span style="font-weight: bold;">-i</span></span> + flag. If you are doing proofing, you need to apply this to <span style="text-decoration: underline;">both your source profile, and your destination profile</span>. Note that it is not sufficient to specify an illuminant with the same white point as the one you are @@ -1772,6 +2177,14 @@ White &nb + + + + + + + + Violet</span> spectral content, otherwise FWA compensation won't work properly. This means you ideally need to measure your illuminant spectrum using an instrument that can measure down to @@ -1785,6 +2198,7 @@ White &nb ref/D50_X.X.sp set of illuminant spectra are the D50 spectrum with different levels of U.V. added or subtracted, ref/D50_1.0.sp being the standard D50 illuminant, and may be somewhere to start.<br> + <br> [Note: Generally using <span style="font-weight: bold;">-f</span> with the standard (<b>-i) </b>D50 illuminant spectrum will predict that the device will produce bluer output than the default of not @@ -1797,13 +2211,14 @@ White &nb result will be, as the overall color correction compensates for the blueness. The opposite will happen for an input profile.]<br> <br> - The second way of using the <b>-f</b> flag is to provide it with a - instrument simulation illuminant spectrum parameter, in addition to - the default D50 or <b>-i</b> parameter CIE XYZ - calculation illuminant<b></b>. This more complicated scenario - simulates the measurement of the spectral reflectance of the samples - under a particular instrument illuminant, then computes the CIE XYZ - values of that reflectance spectrum under the default D50 or <b>-i</b> + <b>The second way</b> of using the <b>-f</b> flag is to provide it + with a instrument simulation illuminant spectrum parameter, in + addition to the default D50 or <b>-i</b> parameter CIE XYZ + calculation illuminant (i.e. "<b>-f M1"</b>, or "<b>-f A -i D65"</b> + etc.). This more complicated scenario simulates the <u>measurement</u> + of the spectral reflectance of the samples under a particular + instrument illuminant, then <u>computes</u> the CIE XYZ values of + that reflectance spectrum under the default D50 or <b>-i</b> parameter illuminant. This is <u>not</u> used to give a more accurate real world result, but to provide simulations of various standardized measurement conditions. For instance, to reproduce ISO @@ -1817,10 +2232,10 @@ White &nb equivalent to<b> -f D50</b><br> <b>-f M2</b> equivalent to<b> -f D50M2</b><b><br> - </b><br> - Note that using <span style="font-weight: bold;">-f</span> <b>M2</b> - gives a result that is comparable to that of a U.V. cut filter - instrument. See also the discussion <a href="FWA.html">About + <br> + </b> Note that using <span style="font-weight: bold;">-f</span> + <b>M2</b> gives a result that is comparable to that of a U.V. cut + filter instrument. See also the discussion <a href="FWA.html">About Fluorescent Whitening Agent compensation</a>.<br> <br> <a name="i"></a> The <b>-i</b> parameter allows specifying a @@ -2064,7 +2479,7 @@ White &nb been applied) into the device gamut. <br> <br> <b><a name="P"></a></b>The <b>-P</b> option causes diagnostic 3D <a - href="File_Formats.html#VRML">VRML</a> plots to be created that + href="File_Formats.html#X3DOM">X3DOM</a> plots to be created that illustrate the gamut mappings generated for the perceptual and saturation intent tables.<br> <br> diff --git a/doc/colverify.html b/doc/colverify.html index 3f8bc72..daebbdd 100644 --- a/doc/colverify.html +++ b/doc/colverify.html @@ -3,7 +3,7 @@ <head> <title>colverify</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> @@ -24,46 +24,75 @@ Normalise + + + each files reading to white Y<br> -N Normalise + + + each files reading to white XYZ<br> + -m + Normalise each files reading to its white X+Y+Z<br> + -M + Normalise both files reading to mean white XYZ<br> -D Use + + + D50 100.0 as L*a*b* white reference<br> -c + + + Show CIE94 delta E values<br> -k Show CIEDE2000 delta E values<br> + -h + + + Plot a histogram of delta E's<br> -s Sort patch value by error<br> -w - create VRML vector visualisation (measured.wrl)<br> + + + + create X3DOM vector visualisation (measured.x3d.html)<br> </small></tt><tt><small> -W - create VRML marker & vector visualisation - (measured.wrl)</small></tt><tt><br> + create X3DOM marker & vector visualisation + (measured.x3d.html)</small></tt><tt><br> </tt><tt> </tt><tt><small> -x - Use VRML axes<br> + + + + Use X3DOM axes<br> </small></tt><tt><small><small>-f [illum] Use Fluorescent Whitening Agent compensation [opt. simulated inst. illum.:<br> + + + M0, M1, M2, A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp]<br> -i illum @@ -72,12 +101,18 @@ Use + + + A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp<br> -o observ Choose CIE Observer for spectral data:<br> </small><small> + + + 1931_2 </small><small>(def.)</small><small>, 1964_10, S&B 1955_2, shaw, J&V 1978_2<br> -L profile.icm Skip any first file out of @@ -103,6 +138,14 @@ Use to the XYZ of white for each set before comparison. White is assumed to be the patch with the largest Y value.<br> <br> + The <b>-m</b> flag causes the two sets of values to be normalized + to the X+Y+Z of white for each set before comparison. White is + assumed to be the patch with the largest Y value.<br> + <br> + The <b>-M</b> flag causes the two sets of values to be normalized + to the average XYZ of the whites from each set before comparison. + White is assumed to be the patch with the largest Y value.<br> + <br> The <b>-D</b> flag causes the white reference point for the conversion to L*a*b* to be D50 with a Y value of 100%. By default the sample with the largest Y value is found, and the L*a*b* white @@ -122,11 +165,14 @@ Use CIEDE2000 delta E has a closer correspondence with perceived color differences than either CIE76 or CIE94 delta E values.<br> <br> + The <b>-h</b> flag will display a histogram plot of the fit delta + E's. The X scale is delta E, the Y scale is %<br> + <br> If the <b>-s </b>flag is used in combination with the <b>-v</b> flag, then the test point by test point output will be sorted from worst to best.<br> <br> - The <b>-w</b> creates a <a href="File_Formats.html#VRML">VRML</a> + The <b>-w</b> creates a <a href="File_Formats.html#X3DOM">X3DOM</a> 3D visualization of the differences between the test points in D50 L*a*b* space, each difference being shown as a line vector. If the <span style="font-weight: bold;">-W</span> flag is used, then the target @@ -135,7 +181,7 @@ Use CGATS file) by using the same file for both "target" and "measured" values.<br> <br> - The <b>-x</b> flag adds Lab axes to the VRML output.<br> + The <b>-x</b> flag adds Lab axes to the X3DOM output.<br> <br> The <b>-f</b> flag enables Fluorescent Whitening Agent (FWA) compensation. This only works if spectral data is available and, the @@ -180,10 +226,10 @@ Use The same parameter value should be used as was used during the creation of the profile.<br> <br> - The <b>-L</b><b> profile.icm</b> parameter causes colverify to ignore - any patches from the first file that are out of gamut according to - the profile. This can be useful in evaluating accuracy without - tainting it by impossible to reach colors.<br> + The <b>-L</b><b> profile.icm</b> parameter causes colverify to + ignore any patches from the first file that are out of gamut + according to the profile. This can be useful in evaluating accuracy + without tainting it by impossible to reach colors.<br> <br> The <b>-X</b><b> file.ccmx</b> option applies the given 3x3 calibration matrix to the values from the second file before doing diff --git a/doc/dispcal.html b/doc/dispcal.html index e23a8d0..993124d 100644 --- a/doc/dispcal.html +++ b/doc/dispcal.html @@ -1,28 +1,28 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<html> - <head> - <title>dispcal</title> - <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> - <meta name="author" content="Graeme Gill"> - </head> - <body> - <h2><b>spectro/dispcal</b></h2> - <h3>Summary</h3> - Given calibration target information [white point, maximum - brightness, and response curve ("gamma")], display a series of test - patches on the display, and using the colorimetric values read, - create a calibration lookup tables that make the display meet the - desired target. The type of instrument is determined by the - communication port selected. Emission and display measurement - instruments are supported.<br> - <h3>Usage</h3> - <font size="-1"><span style="font-family: monospace;">dispcal - [-options]</span><i style="font-family: monospace;"> inoutfile</i><br - style="font-family: monospace;"> - <span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#v">-v [n]</a><span - style="font-family: monospace;"> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+ <head>
+ <title>dispcal</title>
+ <meta http-equiv="content-type" content="text/html;
+ charset=windows-1252">
+ <meta name="author" content="Graeme Gill">
+ </head>
+ <body>
+ <h2><b>spectro/dispcal</b></h2>
+ <h3>Summary</h3>
+ Given calibration target information [white point, maximum
+ brightness, and response curve ("gamma")], display a series of test
+ patches on the display, and using the colorimetric values read,
+ create a calibration lookup tables that make the display meet the
+ desired target. The type of instrument is determined by the
+ communication port selected. Emission and display measurement
+ instruments are supported.<br>
+ <h3>Usage</h3>
+ <font size="-1"><span style="font-family: monospace;">dispcal
+ [-options]</span><i style="font-family: monospace;"> inoutfile</i><br
+ style="font-family: monospace;">
+ <span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#v">-v [n]</a><span
+ style="font-family: monospace;">
@@ -57,17 +57,29 @@ - Verbose mode<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> </span><a style="font-family: monospace;" - href="#display">-display displayname</a><span - style="font-family: monospace;"> [X11 only] Choose X11 display - name<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> <a href="#dnm">-d n[,m]</a> - - [X11 only]Choose the display from the following list (default - 1),<br> + + + + + + + + + + + +
+ Verbose mode<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
+ href="#display">-display displayname</a><span
+ style="font-family: monospace;"> [X11 only] Choose X11 display
+ name<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> <a href="#dnm">-d n[,m]</a>
+
+ [X11 only]Choose the display from the following list (default
+ 1),<br>
and optionally @@ -110,8 +122,20 @@ for - VideoLUT access.</span></font><br> - <font size="-1"><span style="font-family: monospace;"> <a + + + + + + + + + + + +
+ VideoLUT access.</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> <a
href="#d">-d n</a> Choose the @@ -154,7 +178,19 @@ list - 1)</span></font><br> + + + + + + + + + + + +
+ 1)</span></font><br>
<span style="font-family: monospace;"> <a href="#dweb">-dweb[:port]</a> @@ -188,8 +224,20 @@ list - Display via a web server at port (default 8080)</span><br> - <span style="font-family: monospace;"> <a href="#dmadvr">-dmadvr</a> + + + + + + + + + + + +
+ Display via a web server at port (default 8080)</span><br>
+ <span style="font-family: monospace;"> <a href="#dmadvr">-dmadvr</a>
@@ -207,12 +255,34 @@ list - [MSWin] Display via MadVR Video Renderer</span><br - style="font-family: monospace;"> - <font size="-1"><span style="font-family: monospace;"></span><span - style="font-family: monospace;"></span><span style="font-family: - monospace;"></span> <span style="font-family: monospace;"></span></font><small - style="font-family: monospace;"><span style="font-family: + + + + + + + + + + + +
+ [MSWin] Display via MadVR Video Renderer</span><br>
+ <tt> </tt><tt><a href="#dcc">-dcc[:n]</a> + + + + + + + +
+ </tt><tt>Display via n'th ChromeCast (default 1, ? for list)</tt><br
+ style="font-family: monospace;">
+ <font size="-1"><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"></span><span style="font-family:
+ monospace;"></span> <span style="font-family: monospace;"></span></font><small
+ style="font-family: monospace;"><span style="font-family:
monospace;"></span><a style="font-family: monospace;" href="#c">-c @@ -247,36 +317,48 @@ list - listno</a><span style="font-family: monospace;"> - Set communication port from - the following list (default 1)<br> - </span></small><font size="-1"><span style="font-family: - monospace;"> </span><a style="font-family: monospace;" - href="#r">-r</a><span style="font-family: monospace;"> - - Report on the calibrated display then - exit</span></font><font size="-1"><span style="font-family: - monospace;"></span><span style="font-family: monospace;"></span><span - style="font-family: monospace;"></span><span style="font-family: - monospace;"><br> - </span></font><font size="-1"><span style="font-family: - monospace;"> </span><a style="font-family: monospace;" - href="#R">-R</a><span style="font-family: monospace;"> - - Report on the uncalibrated display then - exit</span></font><font size="-1"><span style="font-family: - monospace;"></span></font><br> - <font size="-1"><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#m">-m</a><span - style="font-family: monospace;"> - - </span></font><font size="-1"><span - style="font-family: monospace;">Skip</span><span - style="font-family: monospace;"> adjustment of the monitor - controls</span></font><br> - <font size="-1"><span style="font-family: monospace;"><a - href="#o">-o [profile.icm]</a> Create - fast matrix/shaper profile [different filename to outfile.icm]<br> + + + + + + + + + + + +
+ listno</a><span style="font-family: monospace;">
+ Set communication port from
+ the following list (default 1)<br>
+ </span></small><font size="-1"><span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
+ href="#r">-r</a><span style="font-family: monospace;">
+
+ Report on the calibrated display then
+ exit</span></font><font size="-1"><span style="font-family:
+ monospace;"></span><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"></span><span style="font-family:
+ monospace;"><br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
+ href="#R">-R</a><span style="font-family: monospace;">
+
+ Report on the uncalibrated display then
+ exit</span></font><font size="-1"><span style="font-family:
+ monospace;"></span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#m">-m</a><span
+ style="font-family: monospace;">
+
+ </span></font><font size="-1"><span
+ style="font-family: monospace;">Skip</span><span
+ style="font-family: monospace;"> adjustment of the monitor
+ controls</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"><a
+ href="#o">-o [profile.icm]</a> Create
+ fast matrix/shaper profile [different filename to outfile.icm]<br>
<a href="#O">-O description</a> @@ -311,7 +393,19 @@ list - Fast ICC Profile Description string (Default "outfile")<br> + + + + + + + + + + + +
+ Fast ICC Profile Description string (Default "outfile")<br>
<a href="#u">-u</a> Update previous @@ -354,11 +448,23 @@ ICC - profile VideoLUTs</span><span style="font-family: monospace;"></span><span - style="font-family: monospace;"></span><br style="font-family: - monospace;"> - <span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#q">-q [lmh]</a><span + + + + + + + + + + + +
+ profile VideoLUTs</span><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"></span><br style="font-family:
+ monospace;">
+ <span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#q">-q [lmh]</a><span
style="font-family: monospace;"> @@ -393,7 +499,19 @@ ICC - Quality - Low, Medium (def), High<br> + + + + + + + + + + + +
+ Quality - Low, Medium (def), High<br>
<a href="#p">-p</a> @@ -417,9 +535,21 @@ ICC - Use telephoto mode (ie. for a projector) (if available)<br> - </span></font><font size="-1"><span style="font-family: - monospace;"><a href="#y">-y X</a> + + + + + + + + + + + +
+ Use telephoto mode (ie. for a projector) (if available)<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"><a href="#y">-y X</a>
@@ -454,11 +584,23 @@ ICC - Display type - instrument specific list to choose from.</span></font><font - size="-1"><span style="font-family: monospace;"><br - style="font-family: monospace;"> - </span><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#t">-t [temp]</a><span + + + + + + + + + + + +
+ Display type - instrument specific list to choose from.</span></font><font
+ size="-1"><span style="font-family: monospace;"><br
+ style="font-family: monospace;">
+ </span><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#t">-t [temp]</a><span
style="font-family: monospace;"> White Daylight @@ -501,9 +643,21 @@ in - deg. K (deflt.)<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> </span><a style="font-family: monospace;" + + + + + + + + + + + +
+ deg. K (deflt.)<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
href="#T">-T [temp]</a><span style="font-family: monospace;"> White Black @@ -546,10 +700,22 @@ temperaturee - in deg. K</span></font><br style="font-family: monospace;"> - <font size="-1"><span style="font-family: monospace;"></span><span - style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#w">-w x,y</a><span + + + + + + + + + + + +
+ in deg. K</span></font><br style="font-family: monospace;">
+ <font size="-1"><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#w">-w x,y</a><span
style="font-family: monospace;"> @@ -584,10 +750,22 @@ temperaturee - Set the target white point as chromaticity coordinates</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#b">-b bright</a><span + + + + + + + + + + + +
+ Set the target white point as chromaticity coordinates</span><br
+ style="font-family: monospace;">
+ <span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#b">-b bright</a><span
style="font-family: monospace;"> @@ -622,10 +800,22 @@ temperaturee - Set the target white brightness in cd/m^2</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#g">-g gamma</a><span + + + + + + + + + + + +
+ Set the target white brightness in cd/m^2</span><br
+ style="font-family: monospace;">
+ <span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#g">-g gamma</a><span
style="font-family: monospace;"> @@ -660,8 +850,20 @@ temperaturee - Set the target response curve gamma (Def. 2.4)</span><br - style="font-family: monospace;"> + + + + + + + + + + + +
+ Set the target response curve gamma (Def. 2.4)</span><br
+ style="font-family: monospace;">
<span style="font-family: monospace;"> @@ -696,8 +898,20 @@ temperaturee - Use "-gl" for L*a*b* curve</span><br style="font-family: - monospace;"> + + + + + + + + + + + +
+ Use "-gl" for L*a*b* curve</span><br style="font-family:
+ monospace;">
<span style="font-family: monospace;"> @@ -732,7 +946,19 @@ temperaturee - Use "-gs" for sRGB curve<br> + + + + + + + + + + + +
+ Use "-gs" for sRGB curve<br>
Use "-g709" @@ -775,7 +1001,19 @@ use - -a as well!)<br> + + + + + + + + + + + +
+ -a as well!)<br>
@@ -810,8 +1048,20 @@ use - Use "-g240" for SMPTE 240M curve </span></font><font size="-1"><span - style="font-family: monospace;">(should use -a as well!)</span></font><br> + + + + + + + + + + + +
+ Use "-g240" for SMPTE 240M curve </span></font><font size="-1"><span
+ style="font-family: monospace;">(should use -a as well!)</span></font><br>
<font size="-1"><span style="font-family: monospace;"> @@ -846,6 +1096,18 @@ use + + + + + + + + + + + +
Use "-G2.4 -f0" for BT.1886</span></font> @@ -873,12 +1135,24 @@ use - <br> - <font size="-1"><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#G">-G gamma</a><span - style="font-family: monospace;"> - - Set the target response curve actual technical gamma<br> + + + + + + + + + + + +
+ <br>
+ <font size="-1"><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#G">-G gamma</a><span
+ style="font-family: monospace;">
+
+ Set the target response curve actual technical gamma<br>
<a href="#f">-f [degree]</a> Amount of @@ -921,7 +1195,19 @@ output - offset (default all output offset)<br> + + + + + + + + + + + +
+ offset (default all output offset)<br>
<a href="#a">-a ambient</a> @@ -956,19 +1242,39 @@ output - Use viewing condition adjustment for ambient in Lux<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> <a href="#k">-k factor</a> - - Amount to try and correct black point hue. Default 1.0, LCD - default 0.0<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> <a href="#A">-A rate</a> - - Rate of blending from neutral to black point. Default 4.0</span></font><br> - <font size="-1"><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#B">-B bkbright</a><span - style="font-family: monospace;"> + + + + + + + + + + + +
+ Use viewing condition adjustment for ambient in Lux<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> <a href="#k">-k factor</a>
+
+ Amount to try and correct black point hue. Default 1.0, LCD
+ default 0.0<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> <a href="#A">-A rate</a>
+
+ Rate of blending from neutral to black point. Default 4.0<br>
+ <a href="#bhack">-b</a> + + + + + +
+ Use forced black point hack<br>
+ </span></font> <font size="-1"><span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
+ href="#B">-B bkbright</a><span style="font-family: monospace;"> @@ -1002,11 +1308,23 @@ output - Set the target black brightness in cd/m^2</span></font><br - style="font-family: monospace;"> - <font size="-1"><span style="font-family: monospace;"></span><span - style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#e">-e [n]</a><span + + + + + + + + + + + +
+ Set the target black brightness in cd/m^2</span></font><br
+ style="font-family: monospace;">
+ <font size="-1"><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#e">-e [n]</a><span
style="font-family: monospace;"> @@ -1041,11 +1359,23 @@ output - Run n verify passes on final curves<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> </span><a style="font-family: monospace;" - href="#z">-<font size="-1">z</font></a><span style="font-family: - monospace;"> + + + + + + + + + + + +
+ Run n verify passes on final curves<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
+ href="#z">-<font size="-1">z</font></a><span style="font-family:
+ monospace;">
@@ -1080,12 +1410,24 @@ output - Run only verify pass on installed calibration curves</span></font><br - style="font-family: monospace;"> - <font size="-1"><span style="font-family: monospace;"></span><span - style="font-family: monospace;"> <a href="#P">-P - ho,vo,ss[,vs]</a> Position test window - and scale it</span><br style="font-family: monospace;"> + + + + + + + + + + + +
+ Run only verify pass on installed calibration curves</span></font><br
+ style="font-family: monospace;">
+ <font size="-1"><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"> <a href="#P">-P
+ ho,vo,ss[,vs]</a> Position test window
+ and scale it</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> ho,vi: 0.0 @@ -1128,7 +1470,19 @@ center, - = right/bottom etc.</span><br style="font-family: monospace;"> + + + + + + + + + + + +
+ = right/bottom etc.</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> ss: 0.5 @@ -1171,8 +1525,20 @@ normal, - = double etc.<br> - </span></font><font size="-1"><span style="font-family: + + + + + + + + + + + +
+ = double etc.<br>
+ </span></font><font size="-1"><span style="font-family:
monospace;"> @@ -1194,9 +1560,21 @@ normal, - ss,vs: = optional horizontal, vertical scale.</span></font><br> - <font size="-1"><span style="font-family: monospace;"> <a - href="#F">-F</a> + + + + + + + + + + + +
+ ss,vs: = optional horizontal, vertical scale.</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> <a
+ href="#F">-F</a>
@@ -1231,10 +1609,22 @@ normal, - Fill whole screen with black background</span></font><font - size="-1"><span style="font-family: monospace;"></span></font><br> - <font size="-1"><span style="font-family: monospace;"> </span></font><font - size="-1"><span style="font-family: monospace;"><a href="#E">-E</a> + + + + + + + + + + + +
+ Fill whole screen with black background</span></font><font
+ size="-1"><span style="font-family: monospace;"></span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> </span></font><font
+ size="-1"><span style="font-family: monospace;"><a href="#E">-E</a>
@@ -1248,12 +1638,24 @@ normal, - </span></font><small><span style="font-family: monospace;">Video - encode output as (16-235)/255 "TV" levels</span></small><br - style="font-family: monospace;"> - <font size="-1"><span style="font-family: monospace;"></span><span - style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#n">-n</a><span + + + + + + + + + + + +
+ </span></font><small><span style="font-family: monospace;">Video
+ encode output as (16-235)/255 "TV" levels</span></small><br
+ style="font-family: monospace;">
+ <font size="-1"><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#n">-n</a><span
style="font-family: monospace;"> [X11 @@ -1296,13 +1698,25 @@ on - test window<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> </span><a style="font-family: monospace;" - href="#J">-J</a><span style="font-family: monospace;"> - - Run instrument calibration first<br> - </span></font><font size="-1"><span style="font-family: + + + + + + + + + + + +
+ test window<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
+ href="#J">-J</a><span style="font-family: monospace;">
+
+ Run instrument calibration first<br>
+ </span></font><font size="-1"><span style="font-family:
monospace;"> <a href="#N">-N</a> @@ -1337,17 +1751,29 @@ on - Disable initial calibration of instrument if possible</span></font><br> - <font size="-1"><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#H">-H</a><span - style="font-family: monospace;"> - - Use high resolution spectrum mode (if - available)<br> - </span></font><font size="-1"><span style="font-family: - monospace;"></span><span style="font-family: monospace;"><br> - </span></font><font size="-1"><span style="font-family: - monospace;"><span style="text-decoration: underline;"></span><a + + + + + + + + + + + +
+ Disable initial calibration of instrument if possible</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#H">-H</a><span
+ style="font-family: monospace;">
+
+ Use high resolution spectrum mode (if
+ available)<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"></span><span style="font-family: monospace;"><br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"><span style="text-decoration: underline;"></span><a
href="#X1">-X file.ccmx</a> @@ -1382,8 +1808,20 @@ on - Apply Colorimeter Correction Matrix</span></font><br> - <span style="font-family: monospace;"> <a href="#X2">-X + + + + + + + + + + + +
+ Apply Colorimeter Correction Matrix</span></font><br>
+ <span style="font-family: monospace;"> <a href="#X2">-X
file.ccss</a> Use Colorimeter @@ -1421,13 +1859,25 @@ Calibration - Spectral Samples for calibration</span><font size="-1"><span - style="font-family: monospace;"><br> - </span></font><small><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#Q">-Q <i>observ</i></a><span - style="font-family: monospace;"> - Choose CIE Observer for spectrometer or CCSS - colorimeter data:</span><br style="font-family: monospace;"> + + + + + + + + + + + +
+ Spectral Samples for calibration</span><font size="-1"><span
+ style="font-family: monospace;"><br>
+ </span></font><small><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#Q">-Q <i>observ</i></a><span
+ style="font-family: monospace;">
+ Choose CIE Observer for spectrometer or CCSS
+ colorimeter data:</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> @@ -1462,10 +1912,22 @@ Calibration - 1931_2 </span></small><small><span - style="font-family: monospace;">(def.)</span></small><small><span - style="font-family: monospace;">, 1964_10, S&B 1955_2, shaw, - J&V 1978_2, 1964_10c<br> + + + + + + + + + + + +
+ 1931_2 </span></small><small><span
+ style="font-family: monospace;">(def.)</span></small><small><span
+ style="font-family: monospace;">, 1964_10, S&B 1955_2, shaw,
+ J&V 1978_2, 1964_10c<br>
<a href="#I">-I b|w</a> @@ -1500,42 +1962,78 @@ Calibration - Drift compensation, Black: -Ib, White: -Iw, Both: -Ibw</span></small><br> + + + + + + + + + + + +
+ Drift compensation, Black: -Ib, White: -Iw, Both: -Ibw</span></small><br>
<small><span style="font-family: monospace;"><tt> <a href="#YR">-Y + + + + + + + + + + + +
R:<i>rate</i></a> - Override measured refresh rate with rate Hz<br> - </tt> </span></small><font size="-1"><span - style="font-family: monospace;"></span><a style=" font-family: - monospace;" href="#YA">-<font size="-1">Y</font> A</a><span - style="font-family: monospace;"> - - Use non-adaptive integration time mode (if - available).</span></font><br> - <font size="-1"><span style="font-family: monospace;"> </span><a - style=" font-family: monospace;" href="#Yp">-<font size="-1">Y</font> - <font size="-1">p</font></a><span style="font-family: - monospace;"> - - Don't wait for the instrument to be placed on - the display</span></font><br> - <small><span style="font-family: monospace;"> </span></small><font - size="-1"><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#C">-C "command"</a><span - style="font-family: monospace;"> - Invoke shell - "command" each time a color is set</span></font><br> - <font size="-1"><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#M">-M "command"</a><span - style="font-family: monospace;"> - Invoke shell - "command" each time a color is measured</span></font><font - size="-1"><span style="font-family: monospace;"></span><span - style="font-family: monospace;"></span></font><br> - <font size="-1"><span style="font-family: monospace;"> <a + + + + + + + + + + + +
+ Override measured refresh rate with rate Hz<br>
+ </tt> </span></small><font size="-1"><span
+ style="font-family: monospace;"></span><a style=" font-family:
+ monospace;" href="#YA">-<font size="-1">Y</font> A</a><span
+ style="font-family: monospace;">
+
+ Use non-adaptive integration time mode (if
+ available).</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> </span><a
+ style=" font-family: monospace;" href="#Yp">-<font size="-1">Y</font>
+ <font size="-1">p</font></a><span style="font-family:
+ monospace;">
+
+ Don't wait for the instrument to be placed on
+ the display</span></font><br>
+ <small><span style="font-family: monospace;"> </span></small><font
+ size="-1"><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#C">-C "command"</a><span
+ style="font-family: monospace;">
+ Invoke shell
+ "command" each time a color is set</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#M">-M "command"</a><span
+ style="font-family: monospace;">
+ Invoke shell
+ "command" each time a color is measured</span></font><font
+ size="-1"><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"></span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> <a
href="#W">-W n|h|x</a> Override serial @@ -1578,11 +2076,23 @@ none, - h = HW, x = Xon/Xoff</span></font><font size="-1"><span - style="font-family: monospace;"></span></font><br> - <font size="-1"><span style="font-family: monospace;"> </span></font><font - size="-1"><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#D">-D [level]</a><span + + + + + + + + + + + +
+ h = HW, x = Xon/Xoff</span></font><font size="-1"><span
+ style="font-family: monospace;"></span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> </span></font><font
+ size="-1"><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#D">-D [level]</a><span
style="font-family: monospace;"> @@ -1617,11 +2127,23 @@ none, - Print debug diagnostics to stderr</span></font><br - style="font-family: monospace;"> - <font size="-1"><span style="font-family: monospace;"></span><span - style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#p1"><i>inoutfile</i></a><span + + + + + + + + + + + +
+ Print debug diagnostics to stderr</span></font><br
+ style="font-family: monospace;">
+ <font size="-1"><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#p1"><i>inoutfile</i></a><span
style="font-family: monospace;"> @@ -1656,78 +2178,90 @@ none, - </span><span style="font-family: monospace;">Base name for created - or updated </span></font><font size="-1"><a style="font-family: - monospace;" href="cal_format.html">.cal</a><span - style="font-family: monospace;"></span></font><font size="-1"><span - style="font-family: monospace;"> and <a - href="File_Formats.html#ICC">.icm</a> output files</span></font><br> - <br> - <h3>Comments<br> - </h3> - This is the tool is used for adjusting and calibrating a display to - reach specified target behaviour, and optionally profiling it. - For best results on a CRT, you should run this against a neutral - grey desktop background, and avoid having any bright images or - windows on the screen at the time you run dispcal. You could also - use the <span style="font-weight: bold;">-B</span> option to black - the whole screen out, although this will make it impossible to - control dispcal unless you have more than one display.<br> - <br> - <a name="v"></a> The <b>-v</b> flag reports progress information, - as well as other statistics about the progress of calibration. A - numerical argument greater than 1 gives greater verbosity. 2 will - give per step adjustment and repeat information, while 3 will give - even greater technical detail.<br> - <br> - <a name="display"></a>When running on a UNIX based system that used - the X11 Windowing System, <b>dispcal</b> will by default use the - $DISPLAY environment variable to determine which local or remote - display and screen to read from. This can be overridden by supplying - an X11 display name to the <span style="font-weight: bold;">-display</span> - option. Note that if Xinerama is active, you can't select the screen - using $DISPLAY or -display, you have to select it using the <span - style="font-weight: bold;">-d</span> parameter.<br> - <br> - <a name="d"></a> By default the main display will be the location of - the test window. If the system has more than one display or screen, - an alternate display/screen can be selected with the <span - style="font-weight: bold;">-d</span> parameter. If you invoke <span - style="font-weight: bold;">dispcal</span> so as to display the - usage information (i.e. "dispcal -?" or "dispcal --"), then the - discovered displays/screens will be listed. Multiple displays may - not be listed, if they appear as a single display to the operating - system (ie. the multi-display support is hidden in the video card - driver). On UNIX based system that used the X11 Windowing System, - the <span style="font-weight: bold;">-d</span> parameter will - override the screen specified by the $DISPLAY or parameter.<br> - <br> - <span style="font-weight: bold;">Note</span> that if VideoLUTs for a - display are not accessible (i.e. no hardware calibration - capability), <span style="font-weight: bold;">dispcal</span> will - will issue a warning, but continue creating a calibration based on - the display "as-is" rather than its native response. See the <a - href="dispcal.html#o">-o</a> flag for an explanation of the - implications of having no access to the VideoLUTs.<br> - <br> - On X11 the inability to access VideoLUTs could be because you are - trying to access a remote display, and the remote display doesn't - support the XF86VidMode extension, or perhaps you are running - multiple monitors using NVidia TwinView, or MergedFB, and trying to - access anything other than the primary monitor. TwinView and - MergedFB don't properly support the XF86VidMode extension for - multiple displays. You can use <a href="dispwin.html#r">dispwin -r</a> - to test whether the VideoLUTs are accessible for a particular - display. See also below, on how to select a different display for - VideoLUT access. Also note that dispcal will fail if the Visual - depth doesn't match the VideoLUT depth. Typically the VideoLUTs have - 256 entries per color component, so the Visual generally needs to be - 24 bits, 8 bits per color component.<br> - <br> - <a name="dnm"></a>Because of the difficulty cause by TwinView and - MergedFB in X11 based systems, you can optionally specify a separate - display number after the display that is going to be used to present - test patches, for accessing the VideoLUT hardware. This must be + + + + + + + + + + + +
+ </span><span style="font-family: monospace;">Base name for created
+ or updated </span></font><font size="-1"><a style="font-family:
+ monospace;" href="cal_format.html">.cal</a><span
+ style="font-family: monospace;"></span></font><font size="-1"><span
+ style="font-family: monospace;"> and <a
+ href="File_Formats.html#ICC">.icm</a> output files</span></font><br>
+ <br>
+ <h3>Comments<br>
+ </h3>
+ This is the tool is used for adjusting and calibrating a display to
+ reach specified target behaviour, and optionally profiling it.
+ For best results on a CRT, you should run this against a neutral
+ grey desktop background, and avoid having any bright images or
+ windows on the screen at the time you run dispcal. You could also
+ use the <span style="font-weight: bold;">-B</span> option to black
+ the whole screen out, although this will make it impossible to
+ control dispcal unless you have more than one display.<br>
+ <br>
+ <a name="v"></a> The <b>-v</b> flag reports progress information,
+ as well as other statistics about the progress of calibration. A
+ numerical argument greater than 1 gives greater verbosity. 2 will
+ give per step adjustment and repeat information, while 3 will give
+ even greater technical detail.<br>
+ <br>
+ <a name="display"></a>When running on a UNIX based system that used
+ the X11 Windowing System, <b>dispcal</b> will by default use the
+ $DISPLAY environment variable to determine which local or remote
+ display and screen to read from. This can be overridden by supplying
+ an X11 display name to the <span style="font-weight: bold;">-display</span>
+ option. Note that if Xinerama is active, you can't select the screen
+ using $DISPLAY or -display, you have to select it using the <span
+ style="font-weight: bold;">-d</span> parameter.<br>
+ <br>
+ <a name="d"></a> By default the main display will be the location of
+ the test window. If the system has more than one display or screen,
+ an alternate display/screen can be selected with the <span
+ style="font-weight: bold;">-d</span> parameter. If you invoke <span
+ style="font-weight: bold;">dispcal</span> so as to display the
+ usage information (i.e. "dispcal -?" or "dispcal --"), then the
+ discovered displays/screens will be listed. Multiple displays may
+ not be listed, if they appear as a single display to the operating
+ system (ie. the multi-display support is hidden in the video card
+ driver). On UNIX based system that used the X11 Windowing System,
+ the <span style="font-weight: bold;">-d</span> parameter will
+ override the screen specified by the $DISPLAY or parameter.<br>
+ <br>
+ <span style="font-weight: bold;">Note</span> that if VideoLUTs for a
+ display are not accessible (i.e. no hardware calibration
+ capability), <span style="font-weight: bold;">dispcal</span> will
+ will issue a warning, but continue creating a calibration based on
+ the display "as-is" rather than its native response. See the <a
+ href="dispcal.html#o">-o</a> flag for an explanation of the
+ implications of having no access to the VideoLUTs.<br>
+ <br>
+ On X11 the inability to access VideoLUTs could be because you are
+ trying to access a remote display, and the remote display doesn't
+ support the XF86VidMode extension, or perhaps you are running
+ multiple monitors using NVidia TwinView, or MergedFB, and trying to
+ access anything other than the primary monitor. TwinView and
+ MergedFB don't properly support the XF86VidMode extension for
+ multiple displays. You can use <a href="dispwin.html#r">dispwin -r</a>
+ to test whether the VideoLUTs are accessible for a particular
+ display. See also below, on how to select a different display for
+ VideoLUT access. Also note that dispcal will fail if the Visual
+ depth doesn't match the VideoLUT depth. Typically the VideoLUTs have
+ 256 entries per color component, so the Visual generally needs to be
+ 24 bits, 8 bits per color component.<br>
+ <br>
+ <a name="dnm"></a>Because of the difficulty cause by TwinView and
+ MergedFB in X11 based systems, you can optionally specify a separate
+ display number after the display that is going to be used to present
+ test patches, for accessing the VideoLUT hardware. This must be
specified as a single string, e.g. <span style="font-weight: bold;">-d @@ -1762,257 +2296,284 @@ none, - 1,2</span> . Some experimentation may be needed using <a - href="dispwin.html">dispwin</a> on such systems, to discover what - screen has access to the VideoLUT hardware, and which screens the - test patches appear on. You may be able to calibrate one screen, and - then share the calibration with another screen. Profiling can be - done independently to calibration on each screen.<br> - <br> - <a name="dweb"></a><span style="font-weight: bold;">-dweb</span> or - <span style="font-weight: bold;">-dweb:port</span> starts a - standalone web server on your machine, which then allows a local or - remote web browser to display the the color test patches. By default - port <span style="font-weight: bold;">8080</span> is used, but this - can be overridden by appending a <span style="font-weight: bold;">:</span> - and the port number i.e. <span style="font-weight: bold;">-dweb:8001</span>. - The URL will be <span style="font-weight: bold;">http://</span> - then name of the machine or its I.P. address followed by a colon and - the port number - e.g something like <span style="font-weight: - bold;">http://192.168.0.1:8080</span>. If you use the verbose - option (<span style="font-weight: bold;">-v</span>) then a likely - URL will be printed once the server is started, or you could run <span - style="font-weight: bold;">ipconfig</span> (MSWin) or <span - style="font-weight: bold;">/sbin/ifconfig</span> (Linux or OS X) - and identify an internet address for your machine that way. <b>JavaScript</b> - needs to be enabled in your web browser for this to work.<br> - <br> - Note that if you use this method of displaying test patches, that - there is no access to the display VideoLUTs and that the colors will - be displayed with 8 bit per component precision, and any - screen-saver or power-saver will not be disabled. You will also be - at the mercy of any color management applied by the web browser, and - may have to carefully review and configure such color management. - See the <a href="#o">-o</a> flag for an explanation of the - implications of having no access to the VideoLUTs.<br> - <br> - <a name="dmadvr"></a><span style="font-weight: bold;">-dmadvr</span> - [MSWin only] causes test patches to be displayed using the MadVR - video renderer. Note that you may have to start the video playback - software and load a video clip in pause for this to work. MadVR - rendering does not need or support VideoLUT access, but be aware - that the state of the Graphics Card VideoLUTs may affect the - results, and therefore may have to be set appropriately using - dispwin. Test patch colors will <u>not</u> be processed by the - MadVR 3dLut by default.<br> - <br> - <a name="c"></a> <span style="font-weight: bold;">-c</span> The - instrument is assumed to communicate through a USB or serial - communication port, and the port can be selected with the <b>-c</b> - option, if the instrument is not connected to the first port. If you - invoke <span style="font-weight: bold;">dispcal</span> so as to - display the usage information (i.e. "dispcal -?" or "dispcal --"), - then the discovered USB and serial ports will be listed. On - UNIX/Linux, a list of all possible serial ports are shown, but not - all of them may actually be present on your system.<br> - <br> - <a name="r"></a> The -<span style="font-weight: bold;">r</span> and - <span style="font-weight: bold;"><a name="R"></a>-R </span>flags - perform a quick measurement of current display behaviour, reports - and then exits. If the <span style="font-weight: bold;">-r</span> - flag is used the measurement are taken using the currently loaded - calibration (Video LUT) curves, and in the case of MadVR renderer - test patch display the Color Management 3dLut. If <span - style="font-weight: bold;">-R</span> is use, then the uncalibrated - ("raw" or "native") behaviour is measured (ie. no VideoLut or CM). - Reported are: <br> - <br> - Black Brightness in cd/m^2<br> - White Brightness in cd/m^2<br> - The approximate Gamma<br> - The white point x,y chromaticity co-ordinates<br> - The correlated color temperature in Kelvin, and - the CIEDE200 to the Black Body locus.<br> - The correlated Daylight temperature in Kelvin, - and the CIEDE200 to the Daylight locus.<br> - The visual color temperature in Kelvin, and the - CIEDE200 to the Black Body locus.<br> - The visual Daylight temperature in Kelvin, and - the CIEDE200 to the Daylight locus.<br> - The visual color temperature in Kelvin<br> - (for <span style="font-weight: bold;">-R </span>"raw":)<br> - The apparent VideoLUT entry number of significant - bits.<br> - <br> - Note that the correlated color temperature is the temperature of a - black body radiator that has the closest color to the white point - measured using the traditional CIE 1960 UCS space color difference - formula. The correlated daylight temperature is a similar thing, - except the CIE daylight locus is used. The visual color temperature - values are calculated similarly to the correlated color - temperatures, but using the modern CIEDE2000 color difference - formula to calculate a better visual approximation to the closest - temperature to the displays white point. There will be no difference - between the UCS and CIEDE2000 temperatures if the display white - point actually lies on the particular locus.<br> - <br> - <a name="m"></a> The -<span style="font-weight: bold;">m</span> - option skips the usual process of adjusting the display monitor - contrast, brightness and white point controls, and skips straight to - calibration.<br> - <br> - <a name="o"></a><span style="font-weight: bold;">-o [</span><span - style="font-style: italic;">profile.icm</span><span - style="font-weight: bold;">]</span> Normally <span - style="font-weight: bold;">dispcal</span> creates just a - calibration file, which can then be used for subsequent - characterization using <a href="dispread.html">dispread</a> and - profiling using <a href="colprof.html">colprof</a>. If the <span - style="font-weight: bold;">-o</span> flag is used, <span - style="font-weight: bold;">dispcal</span> will also create a - shaper/matrix profile. By default it will create a profile named <span - style="font-weight: bold;">inoutfile.icm</span>, but a differently - named file can be created or updated by specifying the name after - the <span style="font-weight: bold;">-o</span> flag. If the <span - style="font-weight: bold;">-u</span> flag is used with <span - style="font-weight: bold;">-o</span>, then the ICC profile <span - style="font-weight: bold;">vcgt</span> calibration curves will be - updated.<br> - <br> - Note that if VideoLUT access is not possible for the display, that - hardware calibration is not possible. dispcal will create - calibration curves anyway with a warning, and if a profile is - created, it will not contain a 'vcgt' tag, but instead will have the - calibration curves incorporated into the profile itself. If - calibration parameters are chosen that change the displays white - point or brightness, then this will result in a slightly unusual - profile that has a white point that does not correspond with - R=G=B=1.0. Some systems may not cope properly with this type of - profile. See the <a href="Scenarios.html#PM7">tutorial</a> for a - further explanation.<br> - <br> - <a name="O"></a>The <b>-O</b> parameter allows setting of the - shaper/matrix profile description tag. The parameter should be a - string that describes the device and profile. With most command line - shells, it will be necessary to enclose the parameter with double - quotes, so that spaces and other special characters are included in - the parameter, and not mistaken for the start of another flag, or as - a final command line parameter. Many programs that deal with ICC - profiles use the description tag to identify a profile, rather than - the profile filename, so using a descriptive string is important in - being able to find a profile. By default, the profile file name will - be used as the description.<br> - <br> - <a name="u"></a><span style="font-weight: bold;">-u</span> Normally - <span style="font-weight: bold;">dispcal</span> creates a new - calibration file and optional profile, based on the requested - targets and the response of the display. This can take a fair amount - of time, particularly if a high quality level has been selected, so - to speed up the process of keeping a display in calibration the <span - style="font-weight: bold;">-u</span> flag can be used. This uses - the same calibration targets as the previous calibration but does a - smaller number of refinement passes, enough to improve the accuracy - of the calibration to account for drift in the device. If the <span - style="font-weight: bold;">-o</span> flag is used as well, then - the ICC profile <span style="font-weight: bold;"></span>will have - its vcgt tag updated with the new calibration. This keeps the - profile up to date with the display. Normally <span - style="font-weight: bold;">dispcal -u</span> will use the same - quality level that was specified in the previous calibration, but - this can be overridden using the <span style="font-weight: bold;">-q</span> - flag. Any options that attempt to change the calibration target (ie. - white point, brightness, gamma etc.) will be ignored. Adjustment of - the display monitor controls is skipped. A profile cannot be updated - if the display does not support hardware calibration (no VideoLUT - access).<br> - <br> - <a name="q"></a> Quality - Low, Medium (def), High. The <span - style="font-weight: bold;">-q</span> flag determines how much time - and effort to go to in calibrating the display. The higher the - quality, the more test readings will be done, the more refinement - passes will be done, the tighter will be the accuracy tolerance, and - the more detailed will be the calibration of the display. The result - will ultimately be limited by the accuracy of the instrument, the - repeatability of the display and instrument, and the resolution of - the Video Lookup table entries and Digital or Analogue output - (RAMDAC).<br> - <br> - <a name="p"></a>The <span style="font-weight: bold;">-p</span> flag - allows measuring in telephoto mode, using instruments that support - this mode, e.g. the ColorMunki. Telephoto mode is one for taking - emissive measurements from a distance (ie. telespectometer, - tele-colorimeter) mode, and typically would be used for measuring - projector type displays. If a device does not support a specific - telephoto mode, then the normal emissive mode may be suitable for - measuring projectors.<br> - <br> - <a name="y"></a> The <span style="font-weight: bold;">-y</span> - flag allows setting the Display Type. The selection typically - determines two aspects of of the instrument operation: <span - style="font-weight: bold;">1)</span> It may set the measuring mode - to suite <a - href="http://en.wikipedia.org/wiki/Comparison_of_display_technology"><span - style="font-weight: bold;">refresh</span> or <span - style="font-weight: bold;">non-refresh</span> displays</a>. - Typically only LCD (Liquid Crystal) displays have a non-refresh - nature. <span style="font-weight: bold;">2)</span> It may select an - instrument calibration matrix suitable for a particular display - type. The selections available depends on the type and model of - instrument, and a list of the options for the discovered instruments - will be shown in the <a href="ArgyllDoc.html#CmdLine">usage</a> - information. For more details on what particular instruments support - and how this works, see <a href="instruments.html">Operation of - particular instruments</a>. <b>3)</b> Any installed CCSS files - (if applicable), or CCMX files. These files are typically created - using <a href="ccxxmake.html">ccxxmake</a>, and installed using <a - href="oeminst.html">oeminst</a>. The default and Base Calibration - types will be indicated in the usage.<br> - <br> - <a name="t"></a><span style="text-decoration: underline;"></span> <span - style="font-weight: bold;">-t</span> Set the target white point - locus to the equivalent of a Daylight spectrum of the given - temperature in degrees Kelvin. By default the white point target - will be the native white of the display, and it's color temperature - and delta E to the daylight spectrum locus will be shown during - monitor adjustment, and adjustments will be recommended to put the - display white point directly on the Daylight locus. If a Daylight - color temperature is given as an argument to <span - style="font-weight: bold;">-t</span>, then this will become the - target of the adjustment, and the recommended adjustments will be - those needed to make the monitor white point meet the target. - Typical values might be 5000 for matching printed output, or - 6500, which gives a brighter, bluer look. A white point temperature - different to that native to the display may limit the maximum - brightness possible.<br> - <br> - <a name="T"></a><span style="text-decoration: underline;"></span> <span - style="font-weight: bold;">-T</span> Same functionality as - the <span style="font-weight: bold;">-t</span> option, except the - white point locus will be the Black Body, or Planckian locus, rather - than the Daylight locus. While these two white point loci are quite - close, they are subtly different. If a temperature is given as an - argument, this will become the Black Body target temperature during - adjustment.<br> - <br> - <a name="w"></a><span style="font-weight: bold;">-w</span> An - alternative to specifying a white point target in Daylight or - Black Body degrees Kevin, is to specify it in chromaticity - co-ordinates. This allows the white point to be a color other than - one on the Daylight or Black Body. Note that the x,y numbers must be - specified as a single string (no space between the numbers and the - comma).<br> - <br> - <a name="b"></a><span style="font-weight: bold;">-b</span> Set - the target brightness of white in cd/m^2. If this number cannot be - reached, the brightest output possible is chosen, consistent with - matching the white point target. Note that many of the instruments - are not particularly accurate when assessing the absolute display - brightness in cd/m^2. <span style="font-weight: bold;">NOTE</span> - that some LCD screens behave a little strangely near their absolute - white point, and may therefore exhibit odd behavior at values just - below white. It may be advisable in such cases to set a brightness - slightly less than the maximum such a display is capable of.<br> - <br> + + + + + + + + + + + +
+ 1,2</span> . Some experimentation may be needed using <a
+ href="dispwin.html">dispwin</a> on such systems, to discover what
+ screen has access to the VideoLUT hardware, and which screens the
+ test patches appear on. You may be able to calibrate one screen, and
+ then share the calibration with another screen. Profiling can be
+ done independently to calibration on each screen.<br>
+ <br>
+ <a name="dweb"></a><span style="font-weight: bold;">-dweb</span> or
+ <span style="font-weight: bold;">-dweb:port</span> starts a
+ standalone web server on your machine, which then allows a local or
+ remote web browser to display the the color test patches. By default
+ port <span style="font-weight: bold;">8080</span> is used, but this
+ can be overridden by appending a <span style="font-weight: bold;">:</span>
+ and the port number i.e. <span style="font-weight: bold;">-dweb:8001</span>.
+ The URL will be <span style="font-weight: bold;">http://</span>
+ then name of the machine or its I.P. address followed by a colon and
+ the port number - e.g something like <span style="font-weight:
+ bold;">http://192.168.0.1:8080</span>. If you use the verbose
+ option (<span style="font-weight: bold;">-v</span>) then a likely
+ URL will be printed once the server is started, or you could run <span
+ style="font-weight: bold;">ipconfig</span> (MSWin) or <span
+ style="font-weight: bold;">/sbin/ifconfig</span> (Linux or OS X)
+ and identify an internet address for your machine that way. <b>JavaScript</b>
+ needs to be enabled in your web browser for this to work. You may
+ have to modify any firewall to permit port 8080 to be accessed on
+ your machine.<br>
+ <br>
+ Note that if you use this method of displaying test patches, that
+ there is no access to the display VideoLUTs and that the colors will
+ be displayed with 8 bit per component precision, and any
+ screen-saver or power-saver will not be disabled. You will also be
+ at the mercy of any color management applied by the web browser, and
+ may have to carefully review and configure such color management.
+ See the <a href="#o">-o</a> flag for an explanation of the
+ implications of having no access to the VideoLUTs.<br>
+ <br>
+ <a name="dmadvr"></a><span style="font-weight: bold;">-dmadvr</span>
+ [MSWin only] causes test patches to be displayed using the MadVR
+ video renderer. Note that you may have to start the video playback
+ software and load a video clip in pause for this to work. MadVR
+ rendering does not need or support VideoLUT access, but be aware
+ that the state of the Graphics Card VideoLUTs may affect the
+ results, and therefore may have to be set appropriately using
+ dispwin. Test patch colors will <u>not</u> be processed by the
+ MadVR 3dLut by default.<br>
+ <br>
+ <a name="dcc"></a><span style="font-weight: bold;">-dcc</span> or <b>-dcc:<i>no</i></b>
+ causes test patches to be displayed using and available <a
+ href="http://en.wikipedia.org/wiki/Chromecast">ChromeCast</a> to
+ your TV. Use <b>-dcc:?</b> to display a list of ChromeCasts on your
+ local network. Note that the ChromeCast as a test patch source is
+ probably the<b> least accurate</b> of your choices, since it
+ up-samples the test patch and transforms from RGB to YCC and back,
+ but should be accurate within ± 1 bit. You may have to modify any
+ firewall to permit port 8081 to be accessed on your machine if it
+ falls back to the Default receiver (see <a href="Installing.html">installation +
+ instructions</a> for your platform).<br>
+ <br>
+ <a name="c"></a> <span style="font-weight: bold;">-c</span> The
+ instrument is assumed to communicate through a USB or serial
+ communication port, and the port can be selected with the <b>-c</b>
+ option, if the instrument is not connected to the first port. If you
+ invoke <span style="font-weight: bold;">dispcal</span> so as to
+ display the usage information (i.e. "dispcal -?" or "dispcal --"),
+ then the discovered USB and serial ports will be listed. On
+ UNIX/Linux, a list of all possible serial ports are shown, but not
+ all of them may actually be present on your system.<br>
+ <br>
+ <a name="r"></a> The -<span style="font-weight: bold;">r</span> and
+ <span style="font-weight: bold;"><a name="R"></a>-R </span>flags
+ perform a quick measurement of current display behaviour, reports
+ and then exits. If the <span style="font-weight: bold;">-r</span>
+ flag is used the measurement are taken using the currently loaded
+ calibration (Video LUT) curves, and in the case of MadVR renderer
+ test patch display the Color Management 3dLut. If <span
+ style="font-weight: bold;">-R</span> is use, then the uncalibrated
+ ("raw" or "native") behaviour is measured (ie. no VideoLut or CM).
+ Reported are: <br>
+ <br>
+ Black Brightness in cd/m^2<br>
+ White Brightness in cd/m^2<br>
+ The approximate Gamma<br>
+ The white point x,y chromaticity co-ordinates<br>
+ The correlated color temperature in Kelvin, and
+ the CIEDE200 to the Black Body locus.<br>
+ The correlated Daylight temperature in Kelvin,
+ and the CIEDE200 to the Daylight locus.<br>
+ The visual color temperature in Kelvin, and the
+ CIEDE200 to the Black Body locus.<br>
+ The visual Daylight temperature in Kelvin, and
+ the CIEDE200 to the Daylight locus.<br>
+ The visual color temperature in Kelvin<br>
+ (for <span style="font-weight: bold;">-R </span>"raw":)<br>
+ The apparent VideoLUT entry number of significant
+ bits.<br>
+ <br>
+ Note that the correlated color temperature is the temperature of a
+ black body radiator that has the closest color to the white point
+ measured using the traditional CIE 1960 UCS space color difference
+ formula. The correlated daylight temperature is a similar thing,
+ except the CIE daylight locus is used. The visual color temperature
+ values are calculated similarly to the correlated color
+ temperatures, but using the modern CIEDE2000 color difference
+ formula to calculate a better visual approximation to the closest
+ temperature to the displays white point. There will be no difference
+ between the UCS and CIEDE2000 temperatures if the display white
+ point actually lies on the particular locus.<br>
+ <br>
+ <a name="m"></a> The -<span style="font-weight: bold;">m</span>
+ option skips the usual process of adjusting the display monitor
+ contrast, brightness and white point controls, and skips straight to
+ calibration.<br>
+ <br>
+ <a name="o"></a><span style="font-weight: bold;">-o [</span><span
+ style="font-style: italic;">profile.icm</span><span
+ style="font-weight: bold;">]</span> Normally <span
+ style="font-weight: bold;">dispcal</span> creates just a
+ calibration file, which can then be used for subsequent
+ characterization using <a href="dispread.html">dispread</a> and
+ profiling using <a href="colprof.html">colprof</a>. If the <span
+ style="font-weight: bold;">-o</span> flag is used, <span
+ style="font-weight: bold;">dispcal</span> will also create a
+ shaper/matrix profile. By default it will create a profile named <span
+ style="font-weight: bold;">inoutfile.icm</span>, but a differently
+ named file can be created or updated by specifying the name after
+ the <span style="font-weight: bold;">-o</span> flag. If the <span
+ style="font-weight: bold;">-u</span> flag is used with <span
+ style="font-weight: bold;">-o</span>, then the ICC profile <span
+ style="font-weight: bold;">vcgt</span> calibration curves will be
+ updated.<br>
+ <br>
+ Note that if VideoLUT access is not possible for the display, that
+ hardware calibration is not possible. dispcal will create
+ calibration curves anyway with a warning, and if a profile is
+ created, it will not contain a 'vcgt' tag, but instead will have the
+ calibration curves incorporated into the profile itself. If
+ calibration parameters are chosen that change the displays white
+ point or brightness, then this will result in a slightly unusual
+ profile that has a white point that does not correspond with
+ R=G=B=1.0. Some systems may not cope properly with this type of
+ profile. See the <a href="Scenarios.html#PM7">tutorial</a> for a
+ further explanation.<br>
+ <br>
+ <a name="O"></a>The <b>-O</b> parameter allows setting of the
+ shaper/matrix profile description tag. The parameter should be a
+ string that describes the device and profile. With most command line
+ shells, it will be necessary to enclose the parameter with double
+ quotes, so that spaces and other special characters are included in
+ the parameter, and not mistaken for the start of another flag, or as
+ a final command line parameter. Many programs that deal with ICC
+ profiles use the description tag to identify a profile, rather than
+ the profile filename, so using a descriptive string is important in
+ being able to find a profile. By default, the profile file name will
+ be used as the description.<br>
+ <br>
+ <a name="u"></a><span style="font-weight: bold;">-u</span> Normally
+ <span style="font-weight: bold;">dispcal</span> creates a new
+ calibration file and optional profile, based on the requested
+ targets and the response of the display. This can take a fair amount
+ of time, particularly if a high quality level has been selected, so
+ to speed up the process of keeping a display in calibration the <span
+ style="font-weight: bold;">-u</span> flag can be used. This uses
+ the same calibration targets as the previous calibration but does a
+ smaller number of refinement passes, enough to improve the accuracy
+ of the calibration to account for drift in the device. If the <span
+ style="font-weight: bold;">-o</span> flag is used as well, then
+ the ICC profile <span style="font-weight: bold;"></span>will have
+ its vcgt tag updated with the new calibration. This keeps the
+ profile up to date with the display. Normally <span
+ style="font-weight: bold;">dispcal -u</span> will use the same
+ quality level that was specified in the previous calibration, but
+ this can be overridden using the <span style="font-weight: bold;">-q</span>
+ flag. Any options that attempt to change the calibration target (ie.
+ white point, brightness, gamma etc.) will be ignored. Adjustment of
+ the display monitor controls is skipped. A profile cannot be updated
+ if the display does not support hardware calibration (no VideoLUT
+ access).<br>
+ <br>
+ <a name="q"></a> Quality - Low, Medium (def), High. The <span
+ style="font-weight: bold;">-q</span> flag determines how much time
+ and effort to go to in calibrating the display. The higher the
+ quality, the more test readings will be done, the more refinement
+ passes will be done, the tighter will be the accuracy tolerance, and
+ the more detailed will be the calibration of the display. The result
+ will ultimately be limited by the accuracy of the instrument, the
+ repeatability of the display and instrument, and the resolution of
+ the Video Lookup table entries and Digital or Analogue output
+ (RAMDAC).<br>
+ <br>
+ <a name="p"></a>The <span style="font-weight: bold;">-p</span> flag
+ allows measuring in telephoto mode, using instruments that support
+ this mode, e.g. the ColorMunki. Telephoto mode is one for taking
+ emissive measurements from a distance (ie. telespectometer,
+ tele-colorimeter) mode, and typically would be used for measuring
+ projector type displays. If a device does not support a specific
+ telephoto mode, then the normal emissive mode may be suitable for
+ measuring projectors.<br>
+ <br>
+ <a name="y"></a> The <span style="font-weight: bold;">-y</span>
+ flag allows setting the Display Type. The selection typically
+ determines two aspects of of the instrument operation: <span
+ style="font-weight: bold;">1)</span> It may set the measuring mode
+ to suite <a
+ href="http://en.wikipedia.org/wiki/Comparison_of_display_technology"><span
+ style="font-weight: bold;">refresh</span> or <span
+ style="font-weight: bold;">non-refresh</span> displays</a>.
+ Typically only LCD (Liquid Crystal) displays have a non-refresh
+ nature. <span style="font-weight: bold;">2)</span> It may select an
+ instrument calibration matrix suitable for a particular display
+ type. The selections available depends on the type and model of
+ instrument, and a list of the options for the discovered instruments
+ will be shown in the <a href="ArgyllDoc.html#CmdLine">usage</a>
+ information. For more details on what particular instruments support
+ and how this works, see <a href="instruments.html">Operation of
+ particular instruments</a>. <b>3)</b> Any installed CCSS files
+ (if applicable), or CCMX files. These files are typically created
+ using <a href="ccxxmake.html">ccxxmake</a>, and installed using <a
+ href="oeminst.html">oeminst</a>. The default and Base Calibration
+ types will be indicated in the usage.<br>
+ <br>
+ <a name="t"></a><span style="text-decoration: underline;"></span> <span
+ style="font-weight: bold;">-t</span> Set the target white point
+ locus to the equivalent of a Daylight spectrum of the given
+ temperature in degrees Kelvin. By default the white point target
+ will be the native white of the display, and it's color temperature
+ and delta E to the daylight spectrum locus will be shown during
+ monitor adjustment, and adjustments will be recommended to put the
+ display white point directly on the Daylight locus. If a Daylight
+ color temperature is given as an argument to <span
+ style="font-weight: bold;">-t</span>, then this will become the
+ target of the adjustment, and the recommended adjustments will be
+ those needed to make the monitor white point meet the target.
+ Typical values might be 5000 for matching printed output, or
+ 6500, which gives a brighter, bluer look. A white point temperature
+ different to that native to the display may limit the maximum
+ brightness possible.<br>
+ <br>
+ <a name="T"></a><span style="text-decoration: underline;"></span> <span
+ style="font-weight: bold;">-T</span> Same functionality as
+ the <span style="font-weight: bold;">-t</span> option, except the
+ white point locus will be the Black Body, or Planckian locus, rather
+ than the Daylight locus. While these two white point loci are quite
+ close, they are subtly different. If a temperature is given as an
+ argument, this will become the Black Body target temperature during
+ adjustment.<br>
+ <br>
+ <a name="w"></a><span style="font-weight: bold;">-w</span> An
+ alternative to specifying a white point target in Daylight or
+ Black Body degrees Kevin, is to specify it in chromaticity
+ co-ordinates. This allows the white point to be a color other than
+ one on the Daylight or Black Body. Note that the x,y numbers must be
+ specified as a single string (no space between the numbers and the
+ comma).<br>
+ <br>
+ <a name="b"></a><span style="font-weight: bold;">-b</span> Set
+ the target brightness of white in cd/m^2. If this number cannot be
+ reached, the brightest output possible is chosen, consistent with
+ matching the white point target. Note that many of the instruments
+ are not particularly accurate when assessing the absolute display
+ brightness in cd/m^2. <span style="font-weight: bold;">NOTE</span>
+ that some LCD screens behave a little strangely near their absolute
+ white point, and may therefore exhibit odd behavior at values just
+ below white. It may be advisable in such cases to set a brightness
+ slightly less than the maximum such a display is capable of.<br>
+ <br>
<a name="g"></a><span style="font-weight: bold;">-g gamma</span> Set @@ -2048,13 +2609,25 @@ Set - the target response curve gamma. This is normally an exponential - curve (output = input ^gamma), and defaults to 2.4 on MSWindows and - Macintosh OS X 10.6 or latter and Linux/Unix (which is typical of a - CRT type displays real response), and 1.8 on a Macintosh (prior to - OS X 10.6). Four pre-defined curves can be used as well: the sRGB - colorspace response curve, which is an exponent curve with a - straight segment at the dark end and an overall response of + + + + + + + + + + + +
+ the target response curve gamma. This is normally an exponential
+ curve (output = input ^gamma), and defaults to 2.4 on MSWindows and
+ Macintosh OS X 10.6 or latter and Linux/Unix (which is typical of a
+ CRT type displays real response), and 1.8 on a Macintosh (prior to
+ OS X 10.6). Four pre-defined curves can be used as well: the sRGB
+ colorspace response curve, which is an exponent curve with a
+ straight segment at the dark end and an overall response of
approximately gamma 2.2 (<span style="font-weight: bold;">-gs</span>), the @@ -2090,64 +2663,76 @@ the - L* curve, which is the response of the CIE L*a*b* perceptual - colorspace (<span style="font-weight: bold;">-gl</span>). the REC - 709 video standard response curve (<span style="font-weight: bold;">-g709</span>) - and the SMPTE 240M video standard response curve (<span - style="font-weight: bold;">-g240</span>) <br> - <br> - <span style="font-weight: bold;">Note</span> that a real display - can't reproduce any of these ideal curves, since it will have a - non-zero black point, whereas all the ideal curves assume zero light - at zero input. In the case of a gamma curve target, dispcal uses an - actual technical power curve shape that aims for the same relative - output at 50% input as the ideal gamma power curve. To allow for the - non-zero black level of a real display, by default <span - style="font-weight: bold;">dispcal</span> will offset the target - curve values so that zero input gives the actual black level of the - display (output offset). This ensures that the target curve better - corresponds to the typical natural behavior of displays, but it may - not be the most visually even progression from display minimum, but - this behavior can be changed using the <span style="font-weight: - bold;">-f</span> option (see below).<br> - <br> - <span style="font-weight: bold;">Also note</span> that many color - spaces are encoded with, and labelled as having a gamma of - approximately<span style="font-weight: bold;"> 2.2</span> (ie. sRGB, - REC 709, SMPTE 240M, Macintosh OS X 10.6), but are actually intended - to be displayed on a display with a typical CRT gamma of <span - style="font-weight: bold;">2.4</span> viewed in a darkened - environment. This is because this <span style="font-weight: bold;">2.2</span> - gamma is a source gamma encoding in bright viewing conditions such - as a television studio, while typical display viewing conditions are - quite dark by comparison, and a contrast expansion of (approx.) - gamma 1.1 is desirable to make the images look as intended. So if - you are displaying images encoded to the sRGB standard, or - displaying video through the calibration, just setting the gamma - curve to sRGB or REC 709 (respectively) is probably <span - style="font-weight: bold;">not what you want!</span> What you - probably want to do, is to set the gamma curve to about gamma 2.4, - so that the contrast range is expanded appropriately, or <span - style="text-decoration: underline; font-weight: bold;">alternatively</span> - use sRGB or REC 709 or a gamm of 2.2 but <span style="font-weight: - bold;">also</span> use the <span style="font-weight: bold;">-a</span> - parameter to specify the actual ambient viewing conditions, so that - <span style="font-weight: bold;">dispcal</span> can make an - appropriate contrast enhancement. If your instrument is capable of - measuring ambient light levels, then you can do so during the - interactive display control adjustment. See - <http://www.color.org/sRGB.xalter> for details of how sRGB is - intended to be used.<br> - <br> - It is hard to know whether Apple Macintosh computers prior to OS X - 10.6 should also have such an adjustment, since it is not really - possible to know whether colors labelled as being in such a - colorspace are actually encoded in that gamma with the expectation - that they will be displayed on a display with that actual response, - or whether they are intended to be displayed on a display that - contrast expands by a power 1.1. Both situations might be the - case, depending on how source material is created!<br> - <br> + + + + + + + + + + + +
+ L* curve, which is the response of the CIE L*a*b* perceptual
+ colorspace (<span style="font-weight: bold;">-gl</span>). the REC
+ 709 video standard response curve (<span style="font-weight: bold;">-g709</span>)
+ and the SMPTE 240M video standard response curve (<span
+ style="font-weight: bold;">-g240</span>) <br>
+ <br>
+ <span style="font-weight: bold;">Note</span> that a real display
+ can't reproduce any of these ideal curves, since it will have a
+ non-zero black point, whereas all the ideal curves assume zero light
+ at zero input. In the case of a gamma curve target, dispcal uses an
+ actual technical power curve shape that aims for the same relative
+ output at 50% input as the ideal gamma power curve. To allow for the
+ non-zero black level of a real display, by default <span
+ style="font-weight: bold;">dispcal</span> will offset the target
+ curve values so that zero input gives the actual black level of the
+ display (output offset). This ensures that the target curve better
+ corresponds to the typical natural behavior of displays, but it may
+ not be the most visually even progression from display minimum, but
+ this behavior can be changed using the <span style="font-weight:
+ bold;">-f</span> option (see below).<br>
+ <br>
+ <span style="font-weight: bold;">Also note</span> that many color
+ spaces are encoded with, and labelled as having a gamma of
+ approximately<span style="font-weight: bold;"> 2.2</span> (ie. sRGB,
+ REC 709, SMPTE 240M, Macintosh OS X 10.6), but are actually intended
+ to be displayed on a display with a typical CRT gamma of <span
+ style="font-weight: bold;">2.4</span> viewed in a darkened
+ environment. This is because this <span style="font-weight: bold;">2.2</span>
+ gamma is a source gamma encoding in bright viewing conditions such
+ as a television studio, while typical display viewing conditions are
+ quite dark by comparison, and a contrast expansion of (approx.)
+ gamma 1.1 is desirable to make the images look as intended. So if
+ you are displaying images encoded to the sRGB standard, or
+ displaying video through the calibration, just setting the gamma
+ curve to sRGB or REC 709 (respectively) is probably <span
+ style="font-weight: bold;">not what you want!</span> What you
+ probably want to do, is to set the gamma curve to about gamma 2.4,
+ so that the contrast range is expanded appropriately, or <span
+ style="text-decoration: underline; font-weight: bold;">alternatively</span>
+ use sRGB or REC 709 or a gamm of 2.2 but <span style="font-weight:
+ bold;">also</span> use the <span style="font-weight: bold;">-a</span>
+ parameter to specify the actual ambient viewing conditions, so that
+ <span style="font-weight: bold;">dispcal</span> can make an
+ appropriate contrast enhancement. If your instrument is capable of
+ measuring ambient light levels, then you can do so during the
+ interactive display control adjustment. See
+ <http://www.color.org/sRGB.xalter> for details of how sRGB is
+ intended to be used.<br>
+ <br>
+ It is hard to know whether Apple Macintosh computers prior to OS X
+ 10.6 should also have such an adjustment, since it is not really
+ possible to know whether colors labelled as being in such a
+ colorspace are actually encoded in that gamma with the expectation
+ that they will be displayed on a display with that actual response,
+ or whether they are intended to be displayed on a display that
+ contrast expands by a power 1.1. Both situations might be the
+ case, depending on how source material is created!<br>
+ <br>
<a name="G"></a><span style="font-weight: bold;">-G gamma</span> As @@ -2183,98 +2768,110 @@ As - explained above, the gamma value provided to the <span - style="font-weight: bold;">-g</span> option is used to set and - actual response curve that makes an allowance for the non-zero black - of the actual display, and will have the same relative output at 50% - input as the ideal gamma power curve, and so best matches typical - expectations. The <span style="font-weight: bold;">-G</span> option - is an alternative that allows the <span style="font-weight: bold;">actual</span> - power to be specified instead, meaning that when combined with the - displays non-zero black value, the response at 50% input will - probably not match that of the ideal power curve with that gamma - value.<br> - <br> - <a name="f"></a><span style="font-weight: bold;">-f [degree]</span>: - As explained in for the <span style="font-weight: bold;">-g</span> - and <span style="font-weight: bold;">-G</span> options, real - displays do not have a zero black response, while all the target - response curves do, so this has to be allowed for in some way. The - default way of handling this (equivalent to -f 1.0) is to - allow for this at the output of the ideal response curve, by - offsetting and scaling the output values.<span style="font-weight: - bold;"></span> This defined a curve that will match the responses - that many other systems provide and may be a better match to the - natural response of the display, but will give a less visually even - response from black<span style="font-weight: bold;"></span>. The - other alternative is to offset and scale the input values into the - ideal response curve so that zero input gives the actual non-zero - display response. This ensures the most visually even progression - from display minimum, but might be hard to achieve since it is - different to the naturally response of a display. A subtlety is to - provide a split between how much of the offset is accounted for as - input to the ideal response curve, and how much is accounted for at - the output, and this can be done by providing a parameter <span - style="font-weight: bold;">-f degree</span>, where the degree is - 0.0 accounts for it all as input offset, and 1.0 accounts for all of - it as output offset. If <span style="font-weight: bold;">-f</span> - is used without a specified degree, a degree of 0.0 is assumed, the - opposite of the default. <span style="font-weight: bold;">Note</span> - that using all input offset (degree == 0.0) is equivalent to the use - of the <span style="font-weight: bold;">BT.1886</span> transfer - function.<br> - <br> - <a name="a"></a><span style="font-weight: bold;">-a ambient</span>: - As explained for the <span style="font-weight: bold;">-g</span> - parameter, often colors are encoded in a situation with viewing - conditions that are quite different to the viewing conditions of a - typical display, with the expectation that this difference in - viewing conditions will be allowed for in the way the display is - calibrated. The <span style="font-weight: bold;">-a</span> option - is a way of doing this. By default <span style="font-weight: bold;">dispcal</span> - will not make any allowances for viewing conditions, but will - calibrate to the specified response curve, but if the <span - style="font-weight: bold;">-a</span> option is used, or the - ambient level is measured during the interactive display controls - portion of the calibration, an appropriate viewing conditions - adjustment will be performed. For a gamma value or sRGB, the - original viewing conditions will be assumed to be that of the sRGB - standard viewing conditions, while for REC 709 and SMPTE 240M they - will be assumed to be television studio viewing conditions. By - specifying or measuring the ambient lighting for your display, a - viewing conditions adjustment based on the CIECAM02 color appearance - model will be made for the brightness of your display and the - contrast it makes with your ambient light levels. <br> - <br> - <a name="k"></a><span style="font-weight: bold;">-k factor</span>: - Normally this will be set automatically, based on the measured black - level of the display. A <span style="font-weight: bold;">-k</span> - factor of 1.0 will make all colors down the neutral axis (R=G=B) - have the same hue as the chosen white point. Near the black point, - red, green or blue can only be added, not subtracted from zero, so - the process of making the near black colors have the desired hue, - will <span style="font-weight: bold;">lighten</span> them to some - extent. For a device with a good contrast ratio or a black point - that has nearly the same hue as the white, this should not affect - the contrast ration too severely. If the device contrast ratio is - not so good, and the native black hue is noticeably different to - that of the chosen white point (which is often the case for <span - style="font-weight: bold;">LCD</span> type displays, or <span - style="font-weight: bold;">CRT</span> type displays with one - channel which has a poor level of black), this could have a - noticeably detrimental effect on an already limited contrast ratio, - and result in a black that is not as good as it can be, and a lower - <span style="font-weight: bold;">-k</span> factor should be used. <span - style="font-weight: bold;">-k</span> values can range between 0.0 - (no correction of black) to 1.0 (full correction of black). If less - than full correction is chosen, then the resulting calibration - curves will have the target white point down most of the curve, but - will then blend over to the native or compromise black point that is - blacker, but not of the right hue. The rate of this blend can be - controlled with the <span style="font-weight: bold;">-A</span> - parameter (see below). For applications where maximum contrast ratio - is important (such as <b>Video</b>), use <b>-k0</b>. <br> - <br> + + + + + + + + + + + +
+ explained above, the gamma value provided to the <span
+ style="font-weight: bold;">-g</span> option is used to set and
+ actual response curve that makes an allowance for the non-zero black
+ of the actual display, and will have the same relative output at 50%
+ input as the ideal gamma power curve, and so best matches typical
+ expectations. The <span style="font-weight: bold;">-G</span> option
+ is an alternative that allows the <span style="font-weight: bold;">actual</span>
+ power to be specified instead, meaning that when combined with the
+ displays non-zero black value, the response at 50% input will
+ probably not match that of the ideal power curve with that gamma
+ value.<br>
+ <br>
+ <a name="f"></a><span style="font-weight: bold;">-f [degree]</span>:
+ As explained in for the <span style="font-weight: bold;">-g</span>
+ and <span style="font-weight: bold;">-G</span> options, real
+ displays do not have a zero black response, while all the target
+ response curves do, so this has to be allowed for in some way. The
+ default way of handling this (equivalent to -f 1.0) is to
+ allow for this at the output of the ideal response curve, by
+ offsetting and scaling the output values.<span style="font-weight:
+ bold;"></span> This defined a curve that will match the responses
+ that many other systems provide and may be a better match to the
+ natural response of the display, but will give a less visually even
+ response from black<span style="font-weight: bold;"></span>. The
+ other alternative is to offset and scale the input values into the
+ ideal response curve so that zero input gives the actual non-zero
+ display response. This ensures the most visually even progression
+ from display minimum, but might be hard to achieve since it is
+ different to the naturally response of a display. A subtlety is to
+ provide a split between how much of the offset is accounted for as
+ input to the ideal response curve, and how much is accounted for at
+ the output, and this can be done by providing a parameter <span
+ style="font-weight: bold;">-f degree</span>, where the degree is
+ 0.0 accounts for it all as input offset, and 1.0 accounts for all of
+ it as output offset. If <span style="font-weight: bold;">-f</span>
+ is used without a specified degree, a degree of 0.0 is assumed, the
+ opposite of the default. <span style="font-weight: bold;">Note</span>
+ that using all input offset (degree == 0.0) is equivalent to the use
+ of the <span style="font-weight: bold;">BT.1886</span> transfer
+ function.<br>
+ <br>
+ <a name="a"></a><span style="font-weight: bold;">-a ambient</span>:
+ As explained for the <span style="font-weight: bold;">-g</span>
+ parameter, often colors are encoded in a situation with viewing
+ conditions that are quite different to the viewing conditions of a
+ typical display, with the expectation that this difference in
+ viewing conditions will be allowed for in the way the display is
+ calibrated. The <span style="font-weight: bold;">-a</span> option
+ is a way of doing this. By default <span style="font-weight: bold;">dispcal</span>
+ will not make any allowances for viewing conditions, but will
+ calibrate to the specified response curve, but if the <span
+ style="font-weight: bold;">-a</span> option is used, or the
+ ambient level is measured during the interactive display controls
+ portion of the calibration, an appropriate viewing conditions
+ adjustment will be performed. For a gamma value or sRGB, the
+ original viewing conditions will be assumed to be that of the sRGB
+ standard viewing conditions, while for REC 709 and SMPTE 240M they
+ will be assumed to be television studio viewing conditions. By
+ specifying or measuring the ambient lighting for your display, a
+ viewing conditions adjustment based on the CIECAM02 color appearance
+ model will be made for the brightness of your display and the
+ contrast it makes with your ambient light levels. <br>
+ <br>
+ <a name="k"></a><span style="font-weight: bold;">-k factor</span>:
+ Normally this will be set automatically, based on the measured black
+ level of the display. A <span style="font-weight: bold;">-k</span>
+ factor of 1.0 will make all colors down the neutral axis (R=G=B)
+ have the same hue as the chosen white point. Near the black point,
+ red, green or blue can only be added, not subtracted from zero, so
+ the process of making the near black colors have the desired hue,
+ will <span style="font-weight: bold;">lighten</span> them to some
+ extent. For a device with a good contrast ratio or a black point
+ that has nearly the same hue as the white, this should not affect
+ the contrast ratio too severely. If the device contrast ratio is not
+ so good, and the native black hue is noticeably different to that of
+ the chosen white point (which is often the case for <span
+ style="font-weight: bold;">LCD</span> type displays, or <span
+ style="font-weight: bold;">CRT</span> type displays with one
+ channel which has a poor level of black), this could have a
+ noticeably detrimental effect on an already limited contrast ratio,
+ and result in a black that is not as good as it can be, and a lower
+ <span style="font-weight: bold;">-k</span> factor should be used. <span
+ style="font-weight: bold;">-k</span> values can range between 0.0
+ (no correction of black) to 1.0 (full correction of black). If less
+ than full correction is chosen, then the resulting calibration
+ curves will have the target white point down most of the curve, but
+ will then blend over to the native or compromise black point that is
+ blacker, but not of the right hue. The rate of this blend can be
+ controlled with the <span style="font-weight: bold;">-A</span>
+ parameter (see below). For applications where maximum contrast ratio
+ is important (such as <b>Video</b>), use <b>-k0</b>. <br>
+ <br>
<a name="A"></a><span style="font-weight: bold;">-A rate</span>: If @@ -2310,153 +2907,175 @@ If - the black point is not being set completely to the same hue as the - white point (ie. because the <span style="font-weight: bold;">-k</span> - factor is less than 1.0), then the resulting calibration curves will - have the target white point down most of the curve, but will then - blend over to the native or compromise black point that is blacker, - but not of the right hue. The rate of this blend can be controlled - with the <span style="font-weight: bold;">-A</span> parameter. The - default value 4.0, which results in a target that switches from the - white point target to the black, moderately close to the black - point. While this typically gives a good visual result with the - target neutral hue being maintained to the point where the crossover - to the black hue is not visible, it may be asking too much of some - displays (typically LCD type displays), and there may be some visual - effects due to inconsistent color with viewing angle. For this - situation a smaller value may give a better visual result (e.g. try - values of 3.0 or 2.0. A value of 1.0 will set a pure linear blend - from white point to black point). If there is too much coloration - near black, try a larger value, e.g. 6.0 or 8.0.<br> - <br> - <a name="B"></a><span style="font-weight: bold;">-B</span> Set - the target brightness of black in cd/m^2. Setting too high a value - may give strange results as it interacts with trying to achieve the - target "advertised" gamma curve shape. You could try using -f 1 if - this causes a problem.<br> - <br> - <a name="e"></a><span style="font-weight: bold;">-e [n]</span> Run <span - style="font-weight: bold;">n</span> verify passes on the final - curves. This is an extra set of instrument readings, that can be - used to estimate how well the device will match the targets with the - computed calibration curves. Note that the usefulness of the - verification is sometimes limited by the repeatability of the device - & instrument readings. This is often evident for CRT displays, - which (due to their refresh rate) flicker. More than one - verification pass can be done by providing the parameter <span - style="font-weight: bold;">n</span>, and by then comparing the - successive verifications, some idea of the repeatability can be - ascertained. The verification uses a fixed number of semi-random - test values to test the calibration.<br> - <br> - <a name="z"></a><span style="font-weight: bold;">-z</span> Run - verify pass on the display as it is currently setup (currently - installed LUT curves). This will use the usual input parameters to - establish the expected (target) characteristic. <span - style="font-weight: bold;">Note</span> that if the initial - calibration was modified due to it being out of gamut of the - display, verify will show the resulting discrepancy. You can use <a - href="dispwin.html">dispwin</a> to load a <span - style="font-weight: bold;">.cal</span> file into the display - before running dispcal <span style="font-weight: bold;">-z</span>. - Note that if you set an Ambient light level interactively during the - calibration, you need to enter the same number that was measured and - set using the <span style="font-weight: bold;">-a</span> parameter - for verify.<br> - <br> - <a name="P"></a> The <span style="font-weight: bold;">-P</span> - parameter allows you to position and size the test patch window. By - default it is places in the center of the screen, and sized - appropriately for the type of instrument. The <span - style="font-weight: bold;">ho</span> and <span - style="font-weight: bold;">vo</span> values govern the horizontal - and vertical offset respectively. A value of 0.0 positions the - window to the far left or top of the screen, a value of 0.5 - positions it in the center of the screen (the default), and 1.0 - positions it to the far right or bottom of the screen. If three - parameters are provided, then the <span style="font-weight: bold;">ss</span> - parameter is a scale factor for the test window size. A value of 0.5 - for instance, would produce a half sized window. A value of 2.0 will - produce a double size window. If four parameters are provided, then - the last two set independent horizontal and vertical scaling - factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be - specified as a single string (no space between the numbers and the - comma). For example, to create a double sized test window at the top - right of the screen, use <span style="font-weight: bold;">-P 1,0,2</span> - . To create a window twice as wide as high: <span - style="font-weight: bold;">-P 1,0,2,1</span>.<br> - <br> - <a name="F"></a> The <span style="font-weight: bold;">-F</span> - flag causes the while screen behind the test window to be masked - with black. This can aid black accuracy when measuring CRT displays - or projectors.<br> - <br> - <a name="E"></a> The <span style="font-weight: bold;">-E</span> - flag causes the display test values to be scaled to the Video RGB - encoding range of (16-235)/255. This also modifies the resulting - calibration curve behavior downstream of dispcal. If a calibration - curve created using -E gets installed or converted to an ICC profile - 'vcgt' tag in the process of creating a profile in dispcal or - colprof, the incoming full range values will first have the - calibration curve applied and then be scaled to the Video encoding - range (16-235)/255.<br> - <br> - <a name="n"></a><span style="font-weight: bold;">-n</span> When - running on a UNIX based system that used the X11 Windowing System, <b>dispcal</b> - normally selects the override redirect so that the test window will - appear above any other windows on the display. On some systems this - can interfere with window manager operation, and the <b>-n</b> - option turns this behaviour off.<br> - <br> - <a name="J"></a> The -<span style="font-weight: bold;">J</span> - option runs through the black and sensor relative calibration - routines for the Xrite DTP92 and DTP94 instruments, the black level - calibration for the Eye-One Display 1, and a CRT frequency - calibration for the Eye-One Display 2. For the black calibration the - instrument should be placed on an opaque, black surface, and any - stray light should be avoided by placing something opaque over the - instrument. If a Spectrolino is being used, then a white and black - calibration will always be performed before the instrument can be - placed on the display, unless the <a href="dispcal.html#N">-N</a> - flag is used. Generally it is not necessary to do a calibration - every time an instrument is used, just now and again. There is also - no point in doing a CRT frequency calibration, as this will be - done automatically at the commencement of patch reading, and will be - lost between runs.<br> - <br> - <a name="N"></a> <span style="font-weight: bold;">-N</span> Any - instrument that requires regular calibration will ask for - calibration on initial start-up. Sometimes this can be awkward if - the instrument is being mounted in some sort of measuring jig, or - annoying if several sets of readings are being taken in quick - succession. The -<span style="font-weight: bold;">N</span> - suppresses this initial calibration if a valid and not timed out - previous calibration is recorded in the instrument or on the host - computer. It is advisable to only use this option on the second and - subsequent measurements in a single session.<br> - <br> - <a name="H"></a> The -<span style="font-weight: bold;">H</span> - option turns on high resolution spectral mode, if the instrument - supports it, such as the Eye-One Pro. See <a - href="instruments.html">Operation of particular instruments</a> - for more details. This may give better accuracy for display - measurements.<br> - <br> - <a name="X1"></a> The -<span style="font-weight: bold;">X <span - style="font-style: italic;">file.ccmx</span></span> option reads - a <a href="File_Formats.html#.ccmx">Colorimeter Correction Matrix</a> - from the given file, and applies it to the colorimeter instruments - readings. This can improve a colorimeters accuracy for a particular - type of display. A list of contributed <span style="font-weight: - bold;">ccmx</span> files is <a href="ccmxs.html">here</a>.<br> - <br> - <a name="X2"></a> The -<span style="font-weight: bold;">X <span - style="font-style: italic;">file.ccss</span></span> option reads - a <a href="File_Formats.html#.ccss">Colorimeter Calibration - Spectral Sample</a> from the given file, and uses it to set the - colorimeter instruments calibration. This will only work with - colorimeters that rely on sensor spectral sensitivity calibration - information (ie. the X-Rite <span style="font-weight: bold;">i1d3</span>, + + + + + + + + + + + +
+ the black point is not being set completely to the same hue as the
+ white point (ie. because the <span style="font-weight: bold;">-k</span>
+ factor is less than 1.0), then the resulting calibration curves will
+ have the target white point down most of the curve, but will then
+ blend over to the native or compromise black point that is blacker,
+ but not of the right hue. The rate of this blend can be controlled
+ with the <span style="font-weight: bold;">-A</span> parameter. The
+ default value 4.0, which results in a target that switches from the
+ white point target to the black, moderately close to the black
+ point. While this typically gives a good visual result with the
+ target neutral hue being maintained to the point where the crossover
+ to the black hue is not visible, it may be asking too much of some
+ displays (typically LCD type displays), and there may be some visual
+ effects due to inconsistent color with viewing angle. For this
+ situation a smaller value may give a better visual result (e.g. try
+ values of 3.0 or 2.0. A value of 1.0 will set a pure linear blend
+ from white point to black point). If there is too much coloration
+ near black, try a larger value, e.g. 6.0 or 8.0.<br>
+ <br>
+ <a name="bhack"></a>The <b>-b</b> flag forces source 0,0,0 to map
+ to destination 0,0,0. This may be useful with displays that have a
+ very dark black point, and with an instrument is unable to measure
+ it precisely, and where it is known in some other way that the
+ display is very well behaved from black (i.e. that it has no "dead
+ zone" above zero device input). Using this option with a display
+ that is not well behaved, may result in a loss of shadow detail.
+ This will override any <b>-k</b> factor.<br>
+ <br>
+ <a name="B"></a><span style="font-weight: bold;">-B</span> Set
+ the target brightness of black in cd/m^2 (i.e. the absolute Y
+ value). Setting too high a value may give strange results as it
+ interacts with trying to achieve the target "advertised" gamma curve
+ shape. You could try using -f 1 if this causes a problem.<br>
+ <br>
+ <a name="e"></a><span style="font-weight: bold;">-e [n]</span> Run <span
+ style="font-weight: bold;">n</span> verify passes on the final
+ curves. This is an extra set of instrument readings, that can be
+ used to estimate how well the device will match the targets with the
+ computed calibration curves. Note that the usefulness of the
+ verification is sometimes limited by the repeatability of the device
+ & instrument readings. This is often evident for CRT displays,
+ which (due to their refresh rate) flicker. More than one
+ verification pass can be done by providing the parameter <span
+ style="font-weight: bold;">n</span>, and by then comparing the
+ successive verifications, some idea of the repeatability can be
+ ascertained. The verification uses a fixed number of semi-random
+ test values to test the calibration.<br>
+ <br>
+ <a name="z"></a><span style="font-weight: bold;">-z</span> Run
+ verify pass on the display as it is currently setup (currently
+ installed LUT curves). This will use the usual input parameters to
+ establish the expected (target) characteristic. <span
+ style="font-weight: bold;">Note</span> that if the initial
+ calibration was modified due to it being out of gamut of the
+ display, verify will show the resulting discrepancy. You can use <a
+ href="dispwin.html">dispwin</a> to load a <span
+ style="font-weight: bold;">.cal</span> file into the display
+ before running dispcal <span style="font-weight: bold;">-z</span>.
+ Note that if you set an Ambient light level interactively during the
+ calibration, you need to enter the same number that was measured and
+ set using the <span style="font-weight: bold;">-a</span> parameter
+ for verify.<br>
+ <br>
+ <a name="P"></a> The <span style="font-weight: bold;">-P</span>
+ parameter allows you to position and size the test patch window. By
+ default it is places in the center of the screen, and sized
+ appropriately for the type of instrument, or 10% of the width of the
+ display if the display size is unknown.. The <span
+ style="font-weight: bold;">ho</span> and <span
+ style="font-weight: bold;">vo</span> values govern the horizontal
+ and vertical offset respectively. A value of 0.0 positions the
+ window to the far left or top of the screen, a value of 0.5
+ positions it in the center of the screen (the default), and 1.0
+ positions it to the far right or bottom of the screen. If three
+ parameters are provided, then the <span style="font-weight: bold;">ss</span>
+ parameter is a scale factor for the test window size. A value of 0.5
+ for instance, would produce a half sized window. A value of 2.0 will
+ produce a double size window. If four parameters are provided, then
+ the last two set independent horizontal and vertical scaling
+ factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be
+ specified as a single string (no space between the numbers and the
+ comma). For example, to create a double sized test window at the top
+ right of the screen, use <span style="font-weight: bold;">-P 1,0,2</span>
+ . To create a window twice as wide as high: <span
+ style="font-weight: bold;">-P 1,0,2,1</span>.<br>
+ <br>
+ <a name="F"></a> The <span style="font-weight: bold;">-F</span>
+ flag causes the while screen behind the test window to be masked
+ with black. This can aid black accuracy when measuring CRT displays
+ or projectors.<br>
+ <br>
+ <a name="E"></a> The <span style="font-weight: bold;">-E</span>
+ flag causes the display test values to be scaled to the Video RGB
+ encoding range of (16-235)/255. This also modifies the resulting
+ calibration curve behavior downstream of dispcal. If a calibration
+ curve created using -E gets installed or converted to an ICC profile
+ 'vcgt' tag in the process of creating a profile in dispcal or
+ colprof, the incoming full range values will first have the
+ calibration curve applied and then be scaled to the Video encoding
+ range (16-235)/255.<br>
+ <br>
+ <a name="n"></a><span style="font-weight: bold;">-n</span> When
+ running on a UNIX based system that used the X11 Windowing System, <b>dispcal</b>
+ normally selects the override redirect so that the test window will
+ appear above any other windows on the display. On some systems this
+ can interfere with window manager operation, and the <b>-n</b>
+ option turns this behaviour off.<br>
+ <br>
+ <a name="J"></a> The -<span style="font-weight: bold;">J</span>
+ option runs through the black and sensor relative calibration
+ routines for the Xrite DTP92 and DTP94 instruments, the black level
+ calibration for the Eye-One Display 1, and a CRT frequency
+ calibration for the Eye-One Display 2. For the black calibration the
+ instrument should be placed on an opaque, black surface, and any
+ stray light should be avoided by placing something opaque over the
+ instrument. If a Spectrolino is being used, then a white and black
+ calibration will always be performed before the instrument can be
+ placed on the display, unless the <a href="dispcal.html#N">-N</a>
+ flag is used. Generally it is not necessary to do a calibration
+ every time an instrument is used, just now and again. There is also
+ no point in doing a CRT frequency calibration, as this will be
+ done automatically at the commencement of patch reading, and will be
+ lost between runs.<br>
+ <br>
+ <a name="N"></a> <span style="font-weight: bold;">-N</span> Any
+ instrument that requires regular calibration will ask for
+ calibration on initial start-up. Sometimes this can be awkward if
+ the instrument is being mounted in some sort of measuring jig, or
+ annoying if several sets of readings are being taken in quick
+ succession. The -<span style="font-weight: bold;">N</span>
+ suppresses this initial calibration if a valid and not timed out
+ previous calibration is recorded in the instrument or on the host
+ computer. It is advisable to only use this option on the second and
+ subsequent measurements in a single session.<br>
+ <br>
+ <a name="H"></a> The -<span style="font-weight: bold;">H</span>
+ option turns on high resolution spectral mode, if the instrument
+ supports it, such as the Eye-One Pro. See <a
+ href="instruments.html">Operation of particular instruments</a>
+ for more details. This may give better accuracy for display
+ measurements.<br>
+ <br>
+ <a name="X1"></a> The -<span style="font-weight: bold;">X <span
+ style="font-style: italic;">file.ccmx</span></span> option reads
+ a <a href="File_Formats.html#.ccmx">Colorimeter Correction Matrix</a>
+ from the given file, and applies it to the colorimeter instruments
+ readings. This can improve a colorimeters accuracy for a particular
+ type of display. A list of contributed <span style="font-weight:
+ bold;">ccmx</span> files is <a href="ccmxs.html">here</a>.<br>
+ <br>
+ <a name="X2"></a> The -<span style="font-weight: bold;">X <span
+ style="font-style: italic;">file.ccss</span></span> option reads
+ a <a href="File_Formats.html#.ccss">Colorimeter Calibration
+ Spectral Sample</a> from the given file, and uses it to set the
+ colorimeter instruments calibration. This will only work with
+ colorimeters that rely on sensor spectral sensitivity calibration
+ information (ie. the X-Rite <span style="font-weight: bold;">i1d3</span>,
or the DataColor <span style="font-weight: bold;">Spyder4</span>).This can improve @@ -2494,481 +3113,493 @@ a - colorimeters accuracy for a particular type of display.<br> - <br> - <a name="Q"></a> The <b>-Q</b> flag allows specifying a tristimulus - observer, and is used to compute PCS (Profile Connection Space) - tristimulus values from spectral readings or using a colorimeter - that has CCSS capability. The following choices are available:<br> - <b> 1931_2</b> selects the standard CIE 1931 2 degree - observer. The default.<br> - <b>1964_10</b> selects the standard CIE 1964 10 degree - observer.<br> - <b>1955_2</b> selects the Stiles and Birch 1955 2 degree - observer<br> - <b>1978_2 </b>selects the Judd and Voss 1978 2 degree - observer<br> - <b>shaw</b> selects the Shaw and Fairchild 1997 2 degree - observer<br> - <b>1964_10c</b> selects a version of the CIE 1964 10 degree - observer that has been adjusted using a 3x3 matrix to better agree - with the 1931 2 degree observer.<br> - <br> - <span style="font-weight: bold;">NOTE</span> that if you select - anything other than the default 1931 2 degree observer, that the Y - values will not be cd/m^2, due to the Y curve not being the CIE 1924 - photopic V(λ) luminosity function.<br> - <br> - <a name="I"></a> The -<span style="font-weight: bold;">I <span - style="font-style: italic;">b|w</span></span> options invoke - instrument black level, and display white level compensation - (respectively). Instrument black level drift compensation attempts - to combat instrument black calibration drift by using a display - black test patch as a reference. If an instrument is not - acclimatised sufficiently to the measurement conditions, changes in - temperature can affect the black readings. Display white level drift - compensation attempts to combat changes in display brightness as it - warms up by measuring a white patch every so often, and using it to - normalise all the other readings. If just instrument black drift - compensation is needed, use <span style="font-weight: bold;">-Ib</span>. - If just display white level compensation is needed, use <span - style="font-weight: bold;">-Iw</span>. If both are needed, use <span - style="font-weight: bold;">-Ibw</span> or <span - style="font-weight: bold;">-Iwb</span>.<span style="font-weight: - bold;"> </span><br> - <br> - <a name="YR"></a> The -<span style="font-weight: bold;">Y R:<i>rate</i></span> - options overrides calibration of the instrument refresh rate. This - may be useful if the instrument supports this function and the - refresh rate cannot be accurately calibrated from the display - itself.<br> - <br> - <a name="YA"></a> The -<span style="font-weight: bold;">Y A</span> - option uses a non-adaptive integration time emission measurement - mode, if the instrument supports it, such as the Eye-One Pro or - ColorMunki. By default an adaptive integration time measurement mode - will be used for emission measurements, but some instruments support - a fixed integration time mode that can be used with display devices. - This may give increased consistency and faster measurement times, - but may also give less accurate low level readings.<br> - <br> - <a name="Yp"></a> The -<span style="font-weight: bold;">Y p</span> - option skips asking the user to place the instrument on the display. - Normally a grey patch is displayed, and then the user is asked to - confirm that the instrument is in place, so that readings can - commence. This flag disables that check. This may be useful in - automating certain operations.<br> - <br> - <a name="C"></a> The -<span style="font-weight: bold;">C</span> <span - style="font-weight: bold;">"command" </span>option allows a - method of relaying each test value to some other display than that - on the system running dispcal (for instance, a photo frame, PDA - screen etc.), by causing the given command to be invoked to the - shell, with six arguments. The first three arguments are the RGB - test color as integers in the range 0 to 255, the second three - parameters are the RGB test color as floating point numbers in the - range 0.0 to 1.0. The script or tool should relay the given color to - the screen in some manner (e.g. by generating a raster file of the - given color and sending it to the display being profiled), before - returning. Note that a test window will also be created on the - system running dispread.<br> - <br> - <a name="M"></a> The -<span style="font-weight: bold;">M</span> <span - style="font-weight: bold;">"command" </span>option allows a - method of gathering each test value from some external source, such - as an instrument that is not directly supported by Argyll. The given - command is involked to the shell, with six arguments. The first - three arguments are the RGB test color as integers in the range 0 to - 255, the second three parameters are the RGB test color as floating - point numbers in the range 0.0 to 1.0. The script or tool should - create a file called <span style="font-weight: bold;">"command.meas</span>" - that contains the XYZ values for the given RGB (or measured from the - test window) in cd/m^2 as three numbers separated by spaces, before - returning. If the command returns a non-zero return value, dispcal - will abort. Note that a test window will also be created on the - system running dispcal.<br> - <br> - <a name="W"></a>The <b>-W</b> <span style="font-weight: bold;">n|h|x</span> - parameter overrides the default serial communications flow control - setting. The value <span style="font-weight: bold;">n</span> turns - all flow control off, <span style="font-weight: bold;">h</span> - sets hardware handshaking, and <span style="font-weight: bold;">x</span> - sets Xon/Xoff handshaking. This commend may be useful in workaround - serial communications issues with some systems and cables. <br> - <br> - <a name="D"></a>The <b>-D</b> flag causes communications and other - instrument diagnostics to be printed to stdout. A level can be set - between 1 .. 9, that may give progressively more verbose - information, depending on the instrument. This can be useful in - tracking down why an instrument can't connect.<br> - <br> - <a name="p1"></a><span style="font-weight: bold;">inoutfile</span> - The final parameter on the command line is the base filename for the - <a href="cal_format.html">.cal</a> file and the optional ICC - profile. Normally this will be created (or an existing file will be - overwritten). If the <span style="font-weight: bold;">-u</span> - flag is used, then these files will be updated. If a different ICC - profile name needs to be specified, do so as an argument to the <span - style="font-weight: bold;">-o</span> flag.<br> - <br> - <span style="font-weight: bold;">NOTE</span> that on an X11 system, - if the environment variable <span style="font-weight: bold;">ARGYLL_IGNORE_XRANDR1_2</span> - is set (ie. set it to "yes"), then the presence of the XRandR 1.2 - extension will be ignored, and other extensions such as Xinerama and - XF86VidMode extension will be used. This may be a way to work around - buggy XRandR 1.2 implementations.<br> - <br> - <hr style="width: 100%; height: 2px;"> - <h2><a name="Adjustment"></a>Discussion and guide to display control - adjustment:</h2> - <br> - The adjustment of the display controls (brightness, contrast, R, G - & B channel controls etc.) is very dependent on the particular - monitor. Different types and brands of monitors will have different - controls, or controls that operate in different ways. Some displays - have almost no user controls, and so you may well be best skipping - display adjustment, and going straight to calibration.<br> - <br> - Almost all LCD displays lack a real <span style="font-weight: - bold;">contrast</span> control. Those that do present such a - control generally fake it by adjusting the video signal. For this - reason it is usually best to set an LCD's <span style="font-weight: - bold;">contrast</span> control at its neutral setting (ie. the - setting at which it doesn't change the video signal). Unfortunately, - it can be hard to know what this neutral setting is. On some - displays it is 50%, others 75%. If the LCD display has a "reset to - factory defaults" mode, then try using this first, as a way of - setting the <span style="font-weight: bold;">contrast</span> - control to neutral. The LCD <span style="font-weight: bold;">brightness</span> - control generally adjusts the level of backlighting the display - gets, which affects the maximum brightness, and also tends to raise - or lower the black level in proportion, without changing the - displays response curve shape or overall contrast ratio. If your LCD - display has a <span style="font-weight: bold;">backlight</span> - control as well as a <span style="font-weight: bold;">brightness</span> - control, then the brightness control is also probably being faked, - and you are probably better off setting it to it's neutral setting, - and using the <span style="font-weight: bold;">backlight</span> - control in place of <span style="font-weight: bold;">brightness</span> - in the following adjustments.<br> - <br> - Some high end displays have the ability to mimic various standard - colorspaces such as sRGB or AdobeRGB. You could choose to calibrate - and profile the display in such an emulation mode, although you - probably don't want to fight the emulations white point and gamma. - To get the best out of such a display you really want to choose it's - "Native Gamut" setting, whatever that is called. Note that some - people have reported bad experiences in trying to use "6-axis custom - controls" on displays such as the Dell U2410, so attempting to use - such a mode should be approached with caution. Ideally such a mode - should be used to give just the underlying native display response, - but the settings to achieve this may be very difficult to determine, - and/or it may not be possible, depending on how such a mode distorts - the RGB signals.<br> - <br> - On CRT based displays, the <span style="font-weight: bold;">brightness</span> - control generally adjusts the black level of the display (sometimes - called the <span style="font-weight: bold;">offset</span>), and as - a side effect, tends to change the maximum brightness too. A CRT <span - style="font-weight: bold;">contrast</span> control generally - adjusts the maximum brightness (sometimes called <span - style="font-weight: bold;">gain</span>) without affecting the - black level a great deal. On a CRT both the <span - style="font-weight: bold;">brightness</span> and <span - style="font-weight: bold;">contrast</span> controls will tend to - affect the shape or gamma of the display response curve.<br> - <br> - Many displays have some sort of color temperature adjustment. This - may be in the form of some pre-set color temperatures, or in the - form of individual Red, Green and Blue channel gain adjustments. - Some CRT displays also have R, G & B channel offset adjustments - that will affect the color temperatures near black, as well as - affect the individual channels curve shape. The color temperature - adjustment will generally affect the maximum brightness, and may - also affect the black level and the shape of the display response - curves.<br> - <br> - Some special (expensive) LCD displays may have a white point - adjustment that changes the color of the backlight. If you do not - have one of these types of LCD displays, then attempting to change - the white point of the display (even if it appears to have a "<span - style="font-weight: bold;">white point selection</span>" or <span - style="font-weight: bold;">R/G/B</span> "<span style="font-weight: - bold;">gain</span>" controls") may not be a good idea, as once - again these controls are probably being faked by manipulating the - signal levels. Even if you do manage to change the white point - significantly, it may do things like change the mid tone color too - dramatically, or create a display response that is hard to correct - with calibration, or results in side effects such as quantization - (banding) or other undesirable effects. You may have to try out - various controls (and your aim points for the display calibration), - to decide what is reasonable to attempt on an LCD display.<br> - <br> - Due to the variety of controls as well as the interaction between - them, it can be an iterative process to arrive at a good monitor - set-up, before proceeding on to calibrating and profiling a display. - For this reason, <span style="font-weight: bold;">dispcal</span> - offers a menu of adjustment modes, so that the user can - interactively and iteratively adjust the display controls to meet - the desired targets.<br> - <br> - 1) Black level (CRT: Brightness)<br> - 2) White point (Color temperature, R,G,B, Gain/Contrast)<br> - 3) White level (CRT: Gain/Contrast, LCD: - Brightness/Backlight)<br> - 4) Black point (R,G,B, Offset/Brightness)<br> - 5) Check all<br> - 6) Measure and set ambient for viewing condition adjustment<br> - 7) Continue on to calibration<br> - 8) Exit<br> - <br> - There are four basic adjustment modes. Normally one would proceed - through them in the order above, then perhaps repeat the first - adjustment, before checking the overall settings. The White point - and White level modes operate slightly differently, depending on - whether a white target point has been set using the <span - style="font-weight: bold;">-t -T</span> or <span - style="font-weight: bold;">-w</span> options, and on whether a - brightness target has been set using the <span style="font-weight: - bold;">-b</span> option.<br> - <br> - <br> - The first mode lets you adjust the black level of a CRT display. - Given the current white level, it calculates a value that should - produce a 1% display brightness if the black level is set correctly. - After doing some initial measurements, it will show the target - brightness value (in cd/m^2) on one line, and then underneath it - will show continuously updated readings from the display. The left - most character will switch from '\' to '/' or back again each time a - reading is updated. Some instruments can be quite slow in measuring - dark colors, and it's best to wait for a reading update before - changing the controls more than once. Underneath the target value is - displayed the current reading, and to the right of this is a '+', - '-' or '=' symbol, which gives a hint as to which way to adjust the - brightness control to improve the match to the target.<br> - <br> - <small style="font-weight: bold;"><span style="font-family: - monospace;"> Adjust CRT brightness to get target level. - Press space when done.</span><br style="font-family: monospace;"> - <span style="font-family: monospace;"> Target - 0.60</span><br style="font-family: monospace;"> - <span style="font-family: monospace;"> / Current 0.68 - -</span></small><br> - <br> - Once happy with the adjustment, press space to go back to the menu.<br> - <br> - <br> - The second mode lets you adjust the color of the white point of the - display. If a target white point has been set, it will show the - target brightness value (in cd/m^2) on one line, together with the - target chromaticity co-ordinates for the white point, and then - underneath it will show continuously updated readings from the - display. The left most character will switch from '\' to '/' or back - again each time a reading is updated. Underneath the target - brightness value is displayed the current reading, and then the - current chromaticity co-ordinate values. To the right of this is the - current delta E of the white point from the target, and further to - the right are hints '+', '-' or '=' as to which direction to - adjust the individual Red, Green and Blue gain settings to move the - white point in the direction of the target, and reduce the delta E. - If the symbol is doubled, then this channel will have the greatest - effect. If you do not have individual channel gain controls, then - try choosing amongst color temperature pre-sets, to find one with - the lowest delta E. Depending on the stability of the display, the - coarseness of the controls, and the repeatability of the instrument, - you may not be able to get a perfectly zero delta E.<br> - <br> - <small style="font-weight: bold;"><span - style="font-family: monospace;">Adjust R,G & B gain to get - target x,y. Press space when done.<br> - Target B 60.00, x 0.3451, y 0.3516<br> - / Current B 60.05, x 0.3426, y 0.3506 DE - 1.4 R+ G+ B--</span><span style="font-family: - monospace;"></span></small><br> - <br> - If you did not set a white point target, then the information shown - is a little different - it will show the initial white point value, - as well as the color temperature, and the CIEDE2000 of the white - point to either the Daylight or Black Body locus (depending on - whether the <span style="font-weight: bold;">-T</span> flag was - set). The constantly updated values show the same thing, and the - Red, Green and Blue control hints show the direction to adjust the - controls to place the white point on the locus. The control that - will have the most direct effect on the color temperature will be - the Blue, while the Green will most directly move the white point - towards or away from the locus, thereby reducing the delta E of the - white point to the locus (but there is interaction).<br> - <br> - <small style="font-weight: bold;"><span style="font-family: - monospace;">Adjust R,G & B gain to desired white point. - Press space when done.</span><br style="font-family: monospace;"> - <span style="font-family: monospace;"> Initial B 47.25, x - 0.3417, y 0.3456, CDT 5113 DE 6.9</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;">\ Current B 47.38, x 0.3420, - y 0.3460 CDT 5104 DE 6.7 R-- G+ B-</span></small><br> - <br> - The brightness value is just there as a guide to what effect - the adjustment is having on the overall brightness. Usually the - white level brightness is adjusted using the next adjustment mode. - Once happy with the adjustment, press space to go back to the menu.<br> - <br> - <br> - The third mode lets you adjust the brightness of white on the - display. If you set a target brightness using the <span - style="font-weight: bold;"><span style="font-weight: bold;">-b</span></span> - parameter, it will show the target brightness value (in cd/m^2) on - one line, and then underneath it will show continuously updated - readings from the display. The left most character will switch from - '\' to '/' or back again each time a reading is updated. Underneath - the target value is displayed the current reading, and to the right - of this is a '+', '-' or '=' symbol, which gives a hint as to which - way to adjust the CRT contrast or LCD brightness control to improve - the match to the target.<br> - <br> - <small style="font-weight: bold;"><span - style="font-family: monospace;">Adjust CRT Contrast or LCD - Brightness to get target level. Press space when done.<br> - Target 60.00<br> - / Current 59.96 +</span><span style="font-family: - monospace;"></span></small><br> - <br> - If you did not set a brightness target, it will show the initial - brightness as the target, and the current brightness, which you can - then set any way you want:<br> - <br> - <small style="font-weight: bold;"><span style="font-family: - monospace;">Adjust CRT Contrast or LCD Brightness to desired - level. Press space when done.</span><br style="font-family: - monospace;"> - <span style="font-family: monospace;"> Initial 47.32</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;">/ Current 47.54</span></small><br> - <br> - Once happy with the adjustment, press space to go back to the menu.<br> - <br> - <br> - The fourth mode lets you adjust the color of the black point of the - display, if the display has Red, Green and Blue channel offset - controls. It will show the target 1% brightness value (in cd/m^2) on - one line, together with the target chromaticity co-ordinates for the - black point, and then underneath it will show continuously updated - readings from the display. The left most character will switch from - '\' to '/' or back again each time a reading is updated. Underneath - the target brightness value is displayed the current reading, and - then the current chromaticity co-ordinate values. To the right of - this is the current delta E of the black point from the target, and - further to the right are hints '+', '-' or '=' as to which - direction to adjust the individual Red, Green and Blue offset - settings to move the black point in the right direction. If the - symbol is doubled, then this channel will have the greatest effect. - <br> - <br> - <span style="font-family: monospace;"><span style="font-weight: - bold;"> Adjust R,G & B offsets to get target x,y. - Press space when done.<br> - Target B 0.60, x 0.3451, y 0.3516<br> - \ Current B 0.62, x 0.2782, y 0.2331 DE - 10.3 R+ G++ B-</span></span><small - style="font-weight: bold;"><span style="font-family: monospace;"></span><span - style="font-family: monospace;"></span></small><br> - <br> - The 1% brightness value is just there as a guide to what - effect the adjustment is having on the 1% brightness level. The - combined channel offsets may have an effect on this in combination - with the CRT brightness control. Press space to go back to the menu.<br> - <br> - <br> - The fifth selection checks on the overall settings. If targets - have been set, it will be like:<br> - <br> - <small style="font-weight: bold;"><span style="font-family: - monospace;"> Target Brightness = 50.00, Current = 47.44, - error = -5.1%<br> - Target 50% Level = 10.32, Current = 8.10, - error = -4.4%<br> - Target Near Black = 0.47, Current = 0.68, - error = 0.4%<br> - Target white = x 0.3458, y 0.3586, Current = x 0.3420, y - 0.3454, error = 7.55 DE<br> - Target black = x 0.3458, y 0.3586, Current = x 0.2908, y - 0.2270, error = 29.69 DE</span><span style="font-family: - monospace;"></span></small><br> - <br> - or if no targets are set:<br> - <br> - <small style="font-weight: bold;"><span style="font-family: - monospace;"> Current Brightness = 46.28</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;"> Target 50% - Level = 10.07, Current = 7.52, error = -5.5%</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;"> Target Near Black - = 0.46, Current = 0.46, error = -0.0%</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;"> Current white = x - 0.3439, y 0.3466, VCT 5098K DE 3.0</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;"> Target black = x - 0.3439, y 0.3466, Current = x 0.3093, y 0.2165, error = 30.30 DE</span></small><br> - <br> - and will then go back to the menu.<br> - <br> - The sixth selection <span style="font-weight: bold;">6)</span> - allows the reading of you ambient lighting conditions if your - instrument supports such a mode. Doing so will enable the <span - style="font-weight: bold;">-a</span> option to compensate for your - viewing conditions in the subsequent calibration. See <a - href="dispcal.html#a">-a</a>.<br> - <br> - Once you're happy with the display set-up, you can either - proceed on to the rest of the calibration by selecting <span - style="font-weight: bold;">7)</span>, or exit and re-start by - selecting <span style="font-weight: bold;">8)</span>. You might - want to re-start if you want to change the calibration targets.<br> - <br> - <hr style="width: 100%; height: 2px;"> - <h2>Other caveats:</h2> - NOTE that some <span style="font-weight: bold;">LCD</span> screens - behave a little strangely near their absolute white point, and may - therefore exhibit odd behavior at values just below white. It may be - advisable in such cases to set a brightness slightly less than the - maximum such a display is capable of.<br> - <br> - The program attempts to stop any screensaver or powersaver from - interfering with the measurements, but this may not be effective on - some systems, so it may be necessary to manually disable the - screensaver and/or powersaver before commencing the calibration with - a large number of patches.<br> - <br> - The calibration tables produced maintain the maximum level of - precision available on a system. If the display has VideoLUTs - available (Video Lookup Tables that the frame buffer values pass - through on their way to the display) and thier outputs are better - than 8 bits per component, then the resulting curves can reflect - this, although few current operating systems and/or display cards - actually support better than 8 bit per component output.<br> - <br> - If calibration curves are created for a display in which VideoLUTs - are not available, then the resulting calibration file will be - marked to indicate this, and a subsequent profile created with the - calibration will not have the calibration converted to the 'vcgt' - tag, since such a tag can't be loaded into the displays VideoLUTs.<br> - <br> - If communications break down with a USB connected instrument, you - may have to unplug it, and plug it in again to recover operation.<br> - <br> - Some systems (Apple OSX in particular) have a special set of user - interface controls ("Universal Access") that allows altering the - display in ways designed to assist visually impaired users, by - increasing contrast etc. This will interfere badly with any attempts - to calibrate or profile such a system, and must be turned off in - order to do so. Note that certain magic keyboard sequences can turn - this on by accident.<br> - <br> - <br> - <br> - <br> - <br> - </body> -</html> + + + + + + + + + + + +
+ colorimeters accuracy for a particular type of display.<br>
+ <br>
+ <a name="Q"></a> The <b>-Q</b> flag allows specifying a tristimulus
+ observer, and is used to compute PCS (Profile Connection Space)
+ tristimulus values from spectral readings or using a colorimeter
+ that has CCSS capability. The following choices are available:<br>
+ <b> 1931_2</b> selects the standard CIE 1931 2 degree
+ observer. The default.<br>
+ <b>1964_10</b> selects the standard CIE 1964 10 degree
+ observer.<br>
+ <b>1955_2</b> selects the Stiles and Birch 1955 2 degree
+ observer<br>
+ <b>1978_2 </b>selects the Judd and Voss 1978 2 degree
+ observer<br>
+ <b>shaw</b> selects the Shaw and Fairchild 1997 2 degree
+ observer<br>
+ <b>1964_10c</b> selects a version of the CIE 1964 10 degree
+ observer that has been adjusted using a 3x3 matrix to better agree
+ with the 1931 2 degree observer.<br>
+ <br>
+ <span style="font-weight: bold;">NOTE</span> that if you select
+ anything other than the default 1931 2 degree observer, that the Y
+ values will not be cd/m^2, due to the Y curve not being the CIE 1924
+ photopic V(λ) luminosity function.<br>
+ <br>
+ <a name="I"></a> The -<span style="font-weight: bold;">I <span
+ style="font-style: italic;">b|w</span></span> options invoke
+ instrument black level, and display white level compensation
+ (respectively). Instrument black level drift compensation attempts
+ to combat instrument black calibration drift by using a display
+ black test patch as a reference. If an instrument is not
+ acclimatised sufficiently to the measurement conditions, changes in
+ temperature can affect the black readings. Display white level drift
+ compensation attempts to combat changes in display brightness as it
+ warms up by measuring a white patch every so often, and using it to
+ normalise all the other readings. If just instrument black drift
+ compensation is needed, use <span style="font-weight: bold;">-Ib</span>.
+ If just display white level compensation is needed, use <span
+ style="font-weight: bold;">-Iw</span>. If both are needed, use <span
+ style="font-weight: bold;">-Ibw</span> or <span
+ style="font-weight: bold;">-Iwb</span>.<span style="font-weight:
+ bold;"> </span><br>
+ <br>
+ <a name="YR"></a> The -<span style="font-weight: bold;">Y R:<i>rate</i></span>
+ options overrides calibration of the instrument refresh rate. This
+ may be useful if the instrument supports this function and the
+ refresh rate cannot be accurately calibrated from the display
+ itself.<br>
+ <br>
+ <a name="YA"></a> The -<span style="font-weight: bold;">Y A</span>
+ option uses a non-adaptive integration time emission measurement
+ mode, if the instrument supports it, such as the Eye-One Pro,
+ ColorMunki, i1d3 and K10. By default an adaptive integration time
+ measurement mode will be used for emission measurements, but some
+ instruments support a fixed integration time mode that can be used
+ with display devices. This may give faster measurement times, but
+ may also give less accurate low level readings.<br>
+ <br>
+ <a name="Yp"></a> The -<span style="font-weight: bold;">Y p</span>
+ option skips asking the user to place the instrument on the display.
+ Normally a grey patch is displayed, and then the user is asked to
+ confirm that the instrument is in place, so that readings can
+ commence. This flag disables that check. This may be useful in
+ automating certain operations.<br>
+ <br>
+ <a name="C"></a> The -<span style="font-weight: bold;">C</span> <span
+ style="font-weight: bold;">"command" </span>option allows a
+ method of relaying each test value to some other display than that
+ on the system running dispcal (for instance, a photo frame, PDA
+ screen etc.), by causing the given command to be invoked to the
+ shell, with six arguments. The first three arguments are the RGB
+ test color as integers in the range 0 to 255, the second three
+ parameters are the RGB test color as floating point numbers in the
+ range 0.0 to 1.0. The script or tool should relay the given color to
+ the screen in some manner (e.g. by generating a raster file of the
+ given color and sending it to the display being profiled), before
+ returning. Note that a test window will also be created on the
+ system running dispread.<br>
+ <br>
+ <a name="M"></a> The -<span style="font-weight: bold;">M</span> <span
+ style="font-weight: bold;">"command" </span>option allows a
+ method of gathering each test value from some external source, such
+ as an instrument that is not directly supported by Argyll. The given
+ command is involked to the shell, with six arguments. The first
+ three arguments are the RGB test color as integers in the range 0 to
+ 255, the second three parameters are the RGB test color as floating
+ point numbers in the range 0.0 to 1.0. The script or tool should
+ create a file called <span style="font-weight: bold;">"command.meas</span>"
+ that contains the XYZ values for the given RGB (or measured from the
+ test window) in cd/m^2 as three numbers separated by spaces, before
+ returning. If the command returns a non-zero return value, dispcal
+ will abort. Note that a test window will also be created on the
+ system running dispcal.<br>
+ <br>
+ <a name="W"></a>The <b>-W</b> <span style="font-weight: bold;">n|h|x</span>
+ parameter overrides the default serial communications flow control
+ setting. The value <span style="font-weight: bold;">n</span> turns
+ all flow control off, <span style="font-weight: bold;">h</span>
+ sets hardware handshaking, and <span style="font-weight: bold;">x</span>
+ sets Xon/Xoff handshaking. This commend may be useful in workaround
+ serial communications issues with some systems and cables. <br>
+ <br>
+ <a name="D"></a>The <b>-D</b> flag causes communications and other
+ instrument diagnostics to be printed to stdout. A level can be set
+ between 1 .. 9, that may give progressively more verbose
+ information, depending on the instrument. This can be useful in
+ tracking down why an instrument can't connect.<br>
+ <br>
+ <a name="p1"></a><span style="font-weight: bold;">inoutfile</span>
+ The final parameter on the command line is the base filename for the
+ <a href="cal_format.html">.cal</a> file and the optional ICC
+ profile. Normally this will be created (or an existing file will be
+ overwritten). If the <span style="font-weight: bold;">-u</span>
+ flag is used, then these files will be updated. If a different ICC
+ profile name needs to be specified, do so as an argument to the <span
+ style="font-weight: bold;">-o</span> flag.<br>
+ <br>
+ <span style="font-weight: bold;">NOTE</span> that on an X11 system,
+ if the environment variable <span style="font-weight: bold;">ARGYLL_IGNORE_XRANDR1_2</span>
+ is set (ie. set it to "yes"), then the presence of the XRandR 1.2
+ extension will be ignored, and other extensions such as Xinerama and
+ XF86VidMode extension will be used. This may be a way to work around
+ buggy XRandR 1.2 implementations.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;">
+ <h2><a name="Adjustment"></a>Discussion and guide to display control
+ adjustment:</h2>
+ <br>
+ The adjustment of the display controls (brightness, contrast, R, G
+ & B channel controls etc.) is very dependent on the particular
+ monitor. Different types and brands of monitors will have different
+ controls, or controls that operate in different ways. Some displays
+ have almost no user controls, and so you may well be best skipping
+ display adjustment, and going straight to calibration.<br>
+ <br>
+ Almost all LCD displays lack a real <span style="font-weight:
+ bold;">contrast</span> control. Those that do present such a
+ control generally fake it by adjusting the video signal. For this
+ reason it is usually best to set an LCD's <span style="font-weight:
+ bold;">contrast</span> control at its neutral setting (ie. the
+ setting at which it doesn't change the video signal). Unfortunately,
+ it can be hard to know what this neutral setting is. On some
+ displays it is 50%, others 75%. If the LCD display has a "reset to
+ factory defaults" mode, then try using this first, as a way of
+ setting the <span style="font-weight: bold;">contrast</span>
+ control to neutral. The LCD <span style="font-weight: bold;">brightness</span>
+ control generally adjusts the level of backlighting the display
+ gets, which affects the maximum brightness, and also tends to raise
+ or lower the black level in proportion, without changing the
+ displays response curve shape or overall contrast ratio. If your LCD
+ display has a <span style="font-weight: bold;">backlight</span>
+ control as well as a <span style="font-weight: bold;">brightness</span>
+ control, then the brightness control is also probably being faked,
+ and you are probably better off setting it to it's neutral setting,
+ and using the <span style="font-weight: bold;">backlight</span>
+ control in place of <span style="font-weight: bold;">brightness</span>
+ in the following adjustments.<br>
+ <br>
+ Some high end displays have the ability to mimic various standard
+ colorspaces such as sRGB or AdobeRGB. You could choose to calibrate
+ and profile the display in such an emulation mode, although you
+ probably don't want to fight the emulations white point and gamma.
+ To get the best out of such a display you really want to choose it's
+ "Native Gamut" setting, whatever that is called. Note that some
+ people have reported bad experiences in trying to use "6-axis custom
+ controls" on displays such as the Dell U2410, so attempting to use
+ such a mode should be approached with caution. Ideally such a mode
+ should be used to give just the underlying native display response,
+ but the settings to achieve this may be very difficult to determine,
+ and/or it may not be possible, depending on how such a mode distorts
+ the RGB signals.<br>
+ <br>
+ On CRT based displays, the <span style="font-weight: bold;">brightness</span>
+ control generally adjusts the black level of the display (sometimes
+ called the <span style="font-weight: bold;">offset</span>), and as
+ a side effect, tends to change the maximum brightness too. A CRT <span
+ style="font-weight: bold;">contrast</span> control generally
+ adjusts the maximum brightness (sometimes called <span
+ style="font-weight: bold;">gain</span>) without affecting the
+ black level a great deal. On a CRT both the <span
+ style="font-weight: bold;">brightness</span> and <span
+ style="font-weight: bold;">contrast</span> controls will tend to
+ affect the shape or gamma of the display response curve.<br>
+ <br>
+ Many displays have some sort of color temperature adjustment. This
+ may be in the form of some pre-set color temperatures, or in the
+ form of individual Red, Green and Blue channel gain adjustments.
+ Some CRT displays also have R, G & B channel offset adjustments
+ that will affect the color temperatures near black, as well as
+ affect the individual channels curve shape. The color temperature
+ adjustment will generally affect the maximum brightness, and may
+ also affect the black level and the shape of the display response
+ curves.<br>
+ <br>
+ Some special (expensive) LCD displays may have a white point
+ adjustment that changes the color of the backlight. If you do not
+ have one of these types of LCD displays, then attempting to change
+ the white point of the display (even if it appears to have a "<span
+ style="font-weight: bold;">white point selection</span>" or <span
+ style="font-weight: bold;">R/G/B</span> "<span style="font-weight:
+ bold;">gain</span>" controls") may not be a good idea, as once
+ again these controls are probably being faked by manipulating the
+ signal levels. Even if you do manage to change the white point
+ significantly, it may do things like change the mid tone color too
+ dramatically, or create a display response that is hard to correct
+ with calibration, or results in side effects such as quantization
+ (banding) or other undesirable effects. You may have to try out
+ various controls (and your aim points for the display calibration),
+ to decide what is reasonable to attempt on an LCD display.<br>
+ <br>
+ Due to the variety of controls as well as the interaction between
+ them, it can be an iterative process to arrive at a good monitor
+ set-up, before proceeding on to calibrating and profiling a display.
+ For this reason, <span style="font-weight: bold;">dispcal</span>
+ offers a menu of adjustment modes, so that the user can
+ interactively and iteratively adjust the display controls to meet
+ the desired targets.<br>
+ <br>
+ 1) Black level (CRT: Brightness)<br>
+ 2) White point (Color temperature, R,G,B, Gain/Contrast)<br>
+ 3) White level (CRT: Gain/Contrast, LCD:
+ Brightness/Backlight)<br>
+ 4) Black point (R,G,B, Offset/Brightness)<br>
+ 5) Check all<br>
+ 6) Measure and set ambient for viewing condition adjustment<br>
+ 7) Continue on to calibration<br>
+ 8) Exit<br>
+ <br>
+ There are four basic adjustment modes. Normally one would proceed
+ through them in the order above, then perhaps repeat the first
+ adjustment, before checking the overall settings. The White point
+ and White level modes operate slightly differently, depending on
+ whether a white target point has been set using the <span
+ style="font-weight: bold;">-t -T</span> or <span
+ style="font-weight: bold;">-w</span> options, and on whether a
+ brightness target has been set using the <span style="font-weight:
+ bold;">-b</span> option.<br>
+ <br>
+ <br>
+ The first mode lets you adjust the black level of a CRT display.
+ Given the current white level, it calculates a value that should
+ produce a 1% display brightness if the black level is set correctly.
+ After doing some initial measurements, it will show the target
+ brightness value (in cd/m^2) on one line, and then underneath it
+ will show continuously updated readings from the display. The left
+ most character will switch from '\' to '/' or back again each time a
+ reading is updated. Some instruments can be quite slow in measuring
+ dark colors, and it's best to wait for a reading update before
+ changing the controls more than once. Underneath the target value is
+ displayed the current reading, and to the right of this is a '+',
+ '-' or '=' symbol, which gives a hint as to which way to adjust the
+ brightness control to improve the match to the target.<br>
+ <br>
+ <small style="font-weight: bold;"><span style="font-family:
+ monospace;"> Adjust CRT brightness to get target level.
+ Press space when done.</span><br style="font-family: monospace;">
+ <span style="font-family: monospace;"> Target
+ 0.60</span><br style="font-family: monospace;">
+ <span style="font-family: monospace;"> / Current 0.68
+ -</span></small><br>
+ <br>
+ Once happy with the adjustment, press space to go back to the menu.<br>
+ <br>
+ <br>
+ The second mode lets you adjust the color of the white point of the
+ display. If a target white point has been set, it will show the
+ target brightness value (in cd/m^2) on one line, together with the
+ target chromaticity co-ordinates for the white point, and then
+ underneath it will show continuously updated readings from the
+ display. The left most character will switch from '\' to '/' or back
+ again each time a reading is updated. Underneath the target
+ brightness value is displayed the current reading, and then the
+ current chromaticity co-ordinate values. To the right of this is the
+ current delta E of the white point from the target, and further to
+ the right are hints '+', '-' or '=' as to which direction to
+ adjust the individual Red, Green and Blue gain settings to move the
+ white point in the direction of the target, and reduce the delta E.
+ If the symbol is doubled, then this channel will have the greatest
+ effect. If you do not have individual channel gain controls, then
+ try choosing amongst color temperature pre-sets, to find one with
+ the lowest delta E. Depending on the stability of the display, the
+ coarseness of the controls, and the repeatability of the instrument,
+ you may not be able to get a perfectly zero delta E.<br>
+ <br>
+ <small style="font-weight: bold;"><span
+ style="font-family: monospace;">Adjust R,G & B gain to get
+ target x,y. Press space when done.<br>
+ Target B 60.00, x 0.3451, y 0.3516<br>
+ / Current B 60.05, x 0.3426, y 0.3506 DE
+ 1.4 R+ G+ B--</span><span style="font-family:
+ monospace;"></span></small><br>
+ <br>
+ If you did not set a white point target, then the information shown
+ is a little different - it will show the initial white point value,
+ as well as the color temperature, and the CIEDE2000 of the white
+ point to either the Daylight or Black Body locus (depending on
+ whether the <span style="font-weight: bold;">-T</span> flag was
+ set). The constantly updated values show the same thing, and the
+ Red, Green and Blue control hints show the direction to adjust the
+ controls to place the white point on the locus. The control that
+ will have the most direct effect on the color temperature will be
+ the Blue, while the Green will most directly move the white point
+ towards or away from the locus, thereby reducing the delta E of the
+ white point to the locus (but there is interaction).<br>
+ <br>
+ <small style="font-weight: bold;"><span style="font-family:
+ monospace;">Adjust R,G & B gain to desired white point.
+ Press space when done.</span><br style="font-family: monospace;">
+ <span style="font-family: monospace;"> Initial B 47.25, x
+ 0.3417, y 0.3456, CDT 5113 DE 6.9</span><br
+ style="font-family: monospace;">
+ <span style="font-family: monospace;">\ Current B 47.38, x 0.3420,
+ y 0.3460 CDT 5104 DE 6.7 R-- G+ B-</span></small><br>
+ <br>
+ The brightness value is just there as a guide to what effect
+ the adjustment is having on the overall brightness. Usually the
+ white level brightness is adjusted using the next adjustment mode.
+ Once happy with the adjustment, press space to go back to the menu.<br>
+ <br>
+ <br>
+ The third mode lets you adjust the brightness of white on the
+ display. If you set a target brightness using the <span
+ style="font-weight: bold;"><span style="font-weight: bold;">-b</span></span>
+ parameter, it will show the target brightness value (in cd/m^2) on
+ one line, and then underneath it will show continuously updated
+ readings from the display. The left most character will switch from
+ '\' to '/' or back again each time a reading is updated. Underneath
+ the target value is displayed the current reading, and to the right
+ of this is a '+', '-' or '=' symbol, which gives a hint as to which
+ way to adjust the CRT contrast or LCD brightness control to improve
+ the match to the target.<br>
+ <br>
+ <small style="font-weight: bold;"><span
+ style="font-family: monospace;">Adjust CRT Contrast or LCD
+ Brightness to get target level. Press space when done.<br>
+ Target 60.00<br>
+ / Current 59.96 +</span><span style="font-family:
+ monospace;"></span></small><br>
+ <br>
+ If you did not set a brightness target, it will show the initial
+ brightness as the target, and the current brightness, which you can
+ then set any way you want:<br>
+ <br>
+ <small style="font-weight: bold;"><span style="font-family:
+ monospace;">Adjust CRT Contrast or LCD Brightness to desired
+ level. Press space when done.</span><br style="font-family:
+ monospace;">
+ <span style="font-family: monospace;"> Initial 47.32</span><br
+ style="font-family: monospace;">
+ <span style="font-family: monospace;">/ Current 47.54</span></small><br>
+ <br>
+ Once happy with the adjustment, press space to go back to the menu.<br>
+ <br>
+ <br>
+ The fourth mode lets you adjust the color of the black point of the
+ display, if the display has Red, Green and Blue channel offset
+ controls. It will show the target 1% brightness value (in cd/m^2) on
+ one line, together with the target chromaticity co-ordinates for the
+ black point, and then underneath it will show continuously updated
+ readings from the display. The left most character will switch from
+ '\' to '/' or back again each time a reading is updated. Underneath
+ the target brightness value is displayed the current reading, and
+ then the current chromaticity co-ordinate values. To the right of
+ this is the current delta E of the black point from the target, and
+ further to the right are hints '+', '-' or '=' as to which
+ direction to adjust the individual Red, Green and Blue offset
+ settings to move the black point in the right direction. If the
+ symbol is doubled, then this channel will have the greatest effect.
+ <br>
+ <br>
+ <span style="font-family: monospace;"><span style="font-weight:
+ bold;"> Adjust R,G & B offsets to get target x,y.
+ Press space when done.<br>
+ Target B 0.60, x 0.3451, y 0.3516<br>
+ \ Current B 0.62, x 0.2782, y 0.2331 DE
+ 10.3 R+ G++ B-</span></span><small
+ style="font-weight: bold;"><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"></span></small><br>
+ <br>
+ The 1% brightness value is just there as a guide to what
+ effect the adjustment is having on the 1% brightness level. The
+ combined channel offsets may have an effect on this in combination
+ with the CRT brightness control. Press space to go back to the menu.<br>
+ <br>
+ <br>
+ The fifth selection checks on the overall settings. If targets
+ have been set, it will be like:<br>
+ <br>
+ <small style="font-weight: bold;"><span style="font-family:
+ monospace;"> Target Brightness = 50.00, Current = 47.44,
+ error = -5.1%<br>
+ Target 50% Level = 10.32, Current = 8.10,
+ error = -4.4%<br>
+ Target Near Black = 0.47, Current = 0.68,
+ error = 0.4%<br>
+ Target white = x 0.3458, y 0.3586, Current = x 0.3420, y
+ 0.3454, error = 7.55 DE<br>
+ Target black = x 0.3458, y 0.3586, Current = x 0.2908, y
+ 0.2270, error = 29.69 DE</span><span style="font-family:
+ monospace;"></span></small><br>
+ <br>
+ or if no targets are set:<br>
+ <br>
+ <small style="font-weight: bold;"><span style="font-family:
+ monospace;"> Current Brightness = 46.28</span><br
+ style="font-family: monospace;">
+ <span style="font-family: monospace;"> Target 50%
+ Level = 10.07, Current = 7.52, error = -5.5%</span><br
+ style="font-family: monospace;">
+ <span style="font-family: monospace;"> Target Near Black
+ = 0.46, Current = 0.46, error = -0.0%</span><br
+ style="font-family: monospace;">
+ <span style="font-family: monospace;"> Current white = x
+ 0.3439, y 0.3466, VCT 5098K DE 3.0</span><br
+ style="font-family: monospace;">
+ <span style="font-family: monospace;"> Target black = x
+ 0.3439, y 0.3466, Current = x 0.3093, y 0.2165, error = 30.30 DE</span></small><br>
+ <br>
+ and will then go back to the menu.<br>
+ <br>
+ The sixth selection <span style="font-weight: bold;">6)</span>
+ allows the reading of you ambient lighting conditions if your
+ instrument supports such a mode. Doing so will enable the <span
+ style="font-weight: bold;">-a</span> option to compensate for your
+ viewing conditions in the subsequent calibration. See <a
+ href="dispcal.html#a">-a</a>.<br>
+ <br>
+ Once you're happy with the display set-up, you can either
+ proceed on to the rest of the calibration by selecting <span
+ style="font-weight: bold;">7)</span>, or exit and re-start by
+ selecting <span style="font-weight: bold;">8)</span>. You might
+ want to re-start if you want to change the calibration targets.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;">
+ <h2>Other caveats:</h2>
+ NOTE that some <span style="font-weight: bold;">LCD</span> screens
+ behave a little strangely near their absolute white point, and may
+ therefore exhibit odd behavior at values just below white. It may be
+ advisable in such cases to set a brightness slightly less than the
+ maximum such a display is capable of.<br>
+ <br>
+ The program attempts to stop any screensaver or powersaver from
+ interfering with the measurements, but this may not be effective on
+ some systems, so it may be necessary to manually disable the
+ screensaver and/or powersaver before commencing the calibration with
+ a large number of patches.<br>
+ <br>
+ The calibration tables produced maintain the maximum level of
+ precision available on a system. If the display has VideoLUTs
+ available (Video Lookup Tables that the frame buffer values pass
+ through on their way to the display) and thier outputs are better
+ than 8 bits per component, then the resulting curves can reflect
+ this, although few current operating systems and/or display cards
+ actually support better than 8 bit per component output.<br>
+ <br>
+ If calibration curves are created for a display in which VideoLUTs
+ are not available, then the resulting calibration file will be
+ marked to indicate this, and a subsequent profile created with the
+ calibration will not have the calibration converted to the 'vcgt'
+ tag, since such a tag can't be loaded into the displays VideoLUTs.<br>
+ <br>
+ If communications break down with a USB connected instrument, you
+ may have to unplug it, and plug it in again to recover operation.<br>
+ <br>
+ Some systems (Apple OS X in particular) have a special set of user
+ interface controls ("Universal Access") that allows altering the
+ display in ways designed to assist visually impaired users, by
+ increasing contrast etc. This will interfere badly with any attempts
+ to calibrate or profile such a system, and must be turned off in
+ order to do so. Note that certain magic keyboard sequences can turn
+ this on by accident.<br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ </body>
+</html>
diff --git a/doc/dispread.html b/doc/dispread.html index 071fa7d..a30ab25 100644 --- a/doc/dispread.html +++ b/doc/dispread.html @@ -1,25 +1,25 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<html> - <head> - <title>dispread</title> - <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> - <meta name="author" content="Graeme Gill"> - </head> - <body> - <h2><b>spectro/dispread</b> </h2> - <h3>Summary</h3> - Display test patches on a monitor, read the colorimetric value - result with the colorimeter, and create the chart readings file. The - type of instrument is determined by the communication port selected. - Emission and display measurement instruments are supported.<br> - <br> - If you want to read a display manually rather than automatically, - see <a href="chartread.html">chartread</a> and the <a - href="chartread.html#d">-d</a> option.<br> - <h3>Usage</h3> - <small style="font-family: monospace;">dispread [-options]<i> - inoutfile</i><br> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+ <head>
+ <title>dispread</title>
+ <meta http-equiv="content-type" content="text/html;
+ charset=windows-1252">
+ <meta name="author" content="Graeme Gill">
+ </head>
+ <body>
+ <h2><b>spectro/dispread</b> </h2>
+ <h3>Summary</h3>
+ Display test patches on a monitor, read the colorimetric value
+ result with the colorimeter, and create the chart readings file. The
+ type of instrument is determined by the communication port selected.
+ Emission and display measurement instruments are supported.<br>
+ <br>
+ If you want to read a display manually rather than automatically,
+ see <a href="chartread.html">chartread</a> and the <a
+ href="chartread.html#d">-d</a> option.<br>
+ <h3>Usage</h3>
+ <small style="font-family: monospace;">dispread [-options]<i>
+ inoutfile</i><br>
<a href="#v">-v</a> @@ -43,16 +43,24 @@ - Verbose mode<br> - </small><font size="-1"><a style="font-family: monospace;" - href="#display">-display displayname</a><span - style="font-family: monospace;"> [X11 only] Choose X11 display - name<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> <a href="#dnm">-d n[,m]</a> - - [X11 only]Choose the display from the following list (default - 1),<br> + + + + + + + +
+ Verbose mode<br>
+ </small><font size="-1"><a style="font-family: monospace;"
+ href="#display">-display displayname</a><span
+ style="font-family: monospace;"> [X11 only] Choose X11 display
+ name<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> <a href="#dnm">-d n[,m]</a>
+
+ [X11 only]Choose the display from the following list (default
+ 1),<br>
and optionally @@ -83,8 +91,16 @@ m - for VideoLUT access.</span></font><br> - <font size="-1"><span style="font-family: monospace;"> <a + + + + + + + +
+ for VideoLUT access.</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> <a
href="#d">-d n</a> Choose the @@ -115,7 +131,15 @@ list - (default 1)</span></font><small style="font-family: monospace;"><br> + + + + + + + +
+ (default 1)</span></font><small style="font-family: monospace;"><br>
</small><span style="font-family: monospace;"> <a href="#dweb">-dweb[:port]</a> @@ -141,8 +165,16 @@ list - Display via a web server at port (default 8080)</span><br> - <span style="font-family: monospace;"> <a href="#dmadvr">-dmadvr</a> + + + + + + + +
+ Display via a web server at port (default 8080)</span><br>
+ <span style="font-family: monospace;"> <a href="#dmadvr">-dmadvr</a>
@@ -155,13 +187,25 @@ list - [MSWin] Display via MadVR Video Renderer</span><br> - <small style="font-family: monospace;"> <span style="font-family: - monospace;"> </span><a style="font-family: monospace;" - href="#c">-c listno</a><span style="font-family: monospace;"> - Set - communication port from the following list (default 1)<br> - </span></small><font size="-1"><span style="font-family: + + + + + + + +
+ [MSWin] Display via MadVR Video Renderer</span><br>
+ <tt> </tt><tt><a href="#dcc">-dcc[:n]</a> + +
+ </tt><tt>Display via n'th ChromeCast (default 1, ? for list)</tt><br>
+ <small style="font-family: monospace;"> <span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
+ href="#c">-c listno</a><span style="font-family: monospace;">
+ Set
+ communication port from the following list (default 1)<br>
+ </span></small><font size="-1"><span style="font-family:
monospace;"> <a href="#p">-p</a> @@ -185,9 +229,17 @@ list - Use telephoto mode (ie. for a projector) (if available)</span></font><br> - <font size="-1"><span style="font-family: monospace;"><a - href="#y">-y X</a> + + + + + + + +
+ Use telephoto mode (ie. for a projector) (if available)</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"><a
+ href="#y">-y X</a>
Display @@ -213,9 +265,17 @@ Display - type - instrument specific list to choose from.</span></font><br> - <small style="font-family: monospace;"> <span - style="text-decoration: underline;">-</span><a href="#k">k + + + + + + + +
+ type - instrument specific list to choose from.</span></font><br>
+ <small style="font-family: monospace;"> <span
+ style="text-decoration: underline;">-</span><a href="#k">k
file.cal</a> @@ -239,9 +299,17 @@ Display - Load calibration file into display while reading<br> - </small><small style="font-family: monospace;"> <span - style="text-decoration: underline;">-</span><a href="#K">K + + + + + + + +
+ Load calibration file into display while reading<br>
+ </small><small style="font-family: monospace;"> <span
+ style="text-decoration: underline;">-</span><a href="#K">K
file.cal</a> Apply @@ -266,12 +334,28 @@ Apply - calibration file to test values while reading</small><br> + + + + + + + +
+ calibration file to test values while reading</small><br>
<tt> <a href="#V">-V</a> - [MSWin] Enable MadVR color management (3dLut)</tt><br> + + + + + + + +
+ [MSWin] Enable MadVR color management (3dLut)</tt><br>
<small style="font-family: monospace;"> <a href="#s">-s</a> @@ -295,11 +379,19 @@ Apply - Save spectral information (default don't - save)<br> - </small><font style="font-family: monospace;" size="-1"> <a - href="#P">-P ho,vo,ss[,vs]</a> Position - test window and scale it<br> + + + + + + + +
+ Save spectral information (default don't
+ save)<br>
+ </small><font style="font-family: monospace;" size="-1"> <a
+ href="#P">-P ho,vo,ss[,vs]</a> Position
+ test window and scale it<br>
ho,vi: 0.0 @@ -330,7 +422,15 @@ center, - 1.0 = right/bottom etc.<br> + + + + + + + +
+ 1.0 = right/bottom etc.<br>
ss: 0.5 @@ -361,7 +461,15 @@ normal, - 2.0 = double etc.<br> + + + + + + + +
+ 2.0 = double etc.<br>
</font><font size="-1"><span style="font-family: monospace;"> @@ -378,9 +486,17 @@ normal, - ss,vs: = optional horizontal, vertical scale.</span></font><br> - <font style="font-family: monospace;" size="-1"> </font><font - size="-1"><span style="font-family: monospace;"><a href="#F">-F</a> + + + + + + + +
+ ss,vs: = optional horizontal, vertical scale.</span></font><br>
+ <font style="font-family: monospace;" size="-1"> </font><font
+ size="-1"><span style="font-family: monospace;"><a href="#F">-F</a>
@@ -404,9 +520,17 @@ normal, - Fill whole screen with black background</span></font><br> - <font size="-1"><span style="font-family: monospace;"> </span></font><font - size="-1"><span style="font-family: monospace;"><a href="#E">-E</a> + + + + + + + +
+ Fill whole screen with black background</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> </span></font><font
+ size="-1"><span style="font-family: monospace;"><a href="#E">-E</a>
@@ -415,10 +539,52 @@ normal, - </span></font><small><span style="font-family: monospace;">Video - encode output as (16-235)/255 "TV" levels</span></small><br - style="font-family: monospace;"> - <small style="font-family: monospace;"> <span + + + + + + + +
+ </span></font><small><span style="font-family: monospace;">Video
+ encode output as (16-235)/255 "TV" levels</span></small><br>
+ <font size="-1"><span style="font-family: monospace;"> </span></font><font
+ size="-1"><span style="font-family: monospace;"><a href="#Z">-Z
+ nbits</a> + + + + + + + + + + + + + + +
+ </span></font><small><span style="font-family: monospace;">Quantize +test +values +to +fit + + + + + + + + + + +
+ in nbits</span></small><br style="font-family: monospace;">
+ <small style="font-family: monospace;"> <span
style="text-decoration: underline;"></span><a href="#n">-n</a> [X11 @@ -449,8 +615,16 @@ redirect - on test window<br> - </small><small style="font-family: monospace;"> <a href="#J">-J</a> + + + + + + + +
+ on test window<br>
+ </small><small style="font-family: monospace;"> <a href="#J">-J</a>
@@ -474,8 +648,16 @@ redirect - Run calibration first</small><br> - <font size="-1"><span style="font-family: monospace;"> <a + + + + + + + +
+ Run calibration first</small><br>
+ <font size="-1"><span style="font-family: monospace;"> <a
href="#N">-N</a> @@ -499,16 +681,24 @@ redirect - Disable initial calibration of instrument if possible<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> </span><a style="font-family: monospace;" - href="#H">-H</a><span style="font-family: monospace;"> - - Use high resolution spectrum mode (if - available)</span></font><font size="-1"><span - style="font-family: monospace;"></span><span style="font-family: - monospace;"><br> - <a href="#w">-w</a> + + + + + + + +
+ Disable initial calibration of instrument if possible<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
+ href="#H">-H</a><span style="font-family: monospace;">
+
+ Use high resolution spectrum mode (if
+ available)</span></font><font size="-1"><span
+ style="font-family: monospace;"></span><span style="font-family:
+ monospace;"><br>
+ <a href="#w">-w</a>
Disable normalisation @@ -539,8 +729,16 @@ Y - 100</span></font><small><span style="font-family: monospace;"></span></small><br> - <font size="-1"><span style="font-family: monospace;"><a + + + + + + + +
+ 100</span></font><small><span style="font-family: monospace;"></span></small><br>
+ <font size="-1"><span style="font-family: monospace;"><a
href="#X1">-X file.ccmx</a> @@ -564,8 +762,16 @@ Y - Apply Colorimeter Correction Matrix</span></font><br> - <span style="font-family: monospace;"> <a href="#X2">-X + + + + + + + +
+ Apply Colorimeter Correction Matrix</span></font><br>
+ <span style="font-family: monospace;"> <a href="#X2">-X
file.ccss</a> Use Colorimeter @@ -592,13 +798,21 @@ Calibration - Spectral Samples for calibration</span><font size="-1"><span - style="font-family: monospace;"><br> - </span></font><small><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#Q">-Q <i>observ</i></a><span - style="font-family: monospace;"> - Choose CIE Observer for spectrometer or CCSS - colorimeter data:</span><br style="font-family: monospace;"> + + + + + + + +
+ Spectral Samples for calibration</span><font size="-1"><span
+ style="font-family: monospace;"><br>
+ </span></font><small><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#Q">-Q <i>observ</i></a><span
+ style="font-family: monospace;">
+ Choose CIE Observer for spectrometer or CCSS
+ colorimeter data:</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> @@ -622,11 +836,19 @@ Calibration - 1931_2 </span></small><small><span - style="font-family: monospace;">(def.)</span></small><small><span - style="font-family: monospace;">, 1964_10, S&B 1955_2, shaw, - J&V 1978_2, 1964_10c</span></small><br> - <small><span style="font-family: monospace;"> <a + + + + + + + +
+ 1931_2 </span></small><small><span
+ style="font-family: monospace;">(def.)</span></small><small><span
+ style="font-family: monospace;">, 1964_10, S&B 1955_2, shaw,
+ J&V 1978_2, 1964_10c</span></small><br>
+ <small><span style="font-family: monospace;"> <a
href="dispread.html#I">-I b|w</a> Drift compensation, @@ -657,14 +879,38 @@ Both: - -Ibw</span></small><br> + + + + + + + +
+ -Ibw</span></small><br>
<small><span style="font-family: monospace;"><tt> <a href="#YR">-Y + + + + + + + +
R:<i>rate</i></a> - Override measured refresh rate with rate Hz<br> - </tt> </span></small><font size="-1"><span - style="font-family: monospace;"></span><a style=" font-family: - monospace;" href="#YA">-<font size="-1">Y</font> A</a><span - style="font-family: monospace;"> + + + + + + + +
+ Override measured refresh rate with rate Hz<br>
+ </tt> </span></small><font size="-1"><span
+ style="font-family: monospace;"></span><a style=" font-family:
+ monospace;" href="#YA">-<font size="-1">Y</font> A</a><span
+ style="font-family: monospace;">
@@ -679,25 +925,33 @@ Both: - Use non-adaptive integration time mode (if available).</span></font><br> - <font size="-1"><span style="font-family: monospace;"> </span><a - style=" font-family: monospace;" href="#Yp">-<font size="-1">Y</font> - <font size="-1">p</font></a><span style="font-family: - monospace;"> - - Don't wait for the instrument to be placed on - the display</span></font><br> - <font size="-1"><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#C">-C "command"</a><span - style="font-family: monospace;"> - Invoke shell - "command" each time a color is set<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> </span><a style="font-family: monospace;" - href="#M">-M "command"</a><span style="font-family: monospace;"> - Invoke shell - "command" each time a color is measured</span></font><br> - <font size="-1"><span style="font-family: monospace;"> <a + + + + + + + +
+ Use non-adaptive integration time mode (if available).</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> </span><a
+ style=" font-family: monospace;" href="#Yp">-<font size="-1">Y</font>
+ <font size="-1">p</font></a><span style="font-family:
+ monospace;">
+
+ Don't wait for the instrument to be placed on
+ the display</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#C">-C "command"</a><span
+ style="font-family: monospace;">
+ Invoke shell
+ "command" each time a color is set<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
+ href="#M">-M "command"</a><span style="font-family: monospace;">
+ Invoke shell
+ "command" each time a color is measured</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> <a
href="#W">-W n|h|x</a> Override serial @@ -728,10 +982,18 @@ n - none, h = HW, x = Xon/Xoff</span></font><br> - <small style="font-family: monospace;"> <a href="#D">-D [level]</a> - Print debug - diagnostics to stderr</small><br> + + + + + + + +
+ none, h = HW, x = Xon/Xoff</span></font><br>
+ <small style="font-family: monospace;"> <a href="#D">-D [level]</a>
+ Print debug
+ diagnostics to stderr</small><br>
<small style="font-family: monospace;"> <a href="#p1"><i>inoutfile</i></a> @@ -755,72 +1017,80 @@ n - Base name for input[<a href="File_Formats.html#.ti1">.ti1</a>]/output[<a - href="File_Formats.html#.ti3">.ti3</a>] file.<br> - </small> <br> - <b>Examples</b><br> - <br> - dispread -c1 -i92 mycrt<br> - <h3>Comments<br> - </h3> - This is the tool for exercising a display, in order to measure its - color characteristics. The device test colors are defined by the - outfile.ti1 file, while the resulting device+colorimetric and - optional spectral readings are stored in the outfile.ti3 file. - Display calibration curves can be applied during the measurements, - and the curves included in the resulting .ti3 data file using the <span - style="font-weight: bold;">-k</span>flag. See <a - href="dispcal.html">dispcal</a> for information on how to - calibrate the display before profiling it. For best results, you - should run this against a neutral grey desktop background, and avoid - having any bright images or windows on the screen at the time you - run it.<br> - <br> - <a name="v"></a> The <b>-v</b> flag reports progress information.<br> - <br> - <a name="display"></a><span style="font-weight: bold;">-display</span>: - When running on a UNIX based system that used the X11 Windowing - System, <b>dispread</b> will by default use the $DISPLAY - environment variable to determine which display and screen to read - from. This can be overridden by supplying an X11 display name to the - <span style="font-weight: bold;">-display</span> option. Note that - if Xinerama is active, you can't select the screen using $DISPLAY or - -display, you have to select it using the <span style="font-weight: - bold;">-d</span> parameter.<br> - <br> - <a name="d"></a> <span style="font-weight: bold;">-d</span>: By - default the main display will be the location of the test window. If - the system has more than one display or screen, an alternate - display/screen can be selected with the <span style="font-weight: - bold;">-d</span> parameter. If you invoke <span - style="font-weight: bold;">dispread</span> so as to display the - usage information (i.e. "dispread -?" or "dispread --"), then the - discovered displays/screens will be listed. Multiple displays may - not be listed, if they appear as a single display to the operating - system (ie. the multi-display support is hidden in the video card - driver). On UNIX based system that used the X11 Windowing System, - the <span style="font-weight: bold;">-d</span> parameter will - override the screen specified by the $DISPLAY or <span - style="font-weight: bold;">-display</span> parameter.<br> - <br> - On X11 the inability to access VideoLUTs could be because you are - trying to access a remote display, and the remote display doesn't - support the XF86VidMode extension, or perhaps you are running - multiple monitors using NVidia TwinView, or MergedFB, and trying to - access anything other than the primary monitor. TwinView and - MergedFB don't properly support the XF86VidMode extension for - multiple displays. You can use <a href="dispwin.html#r">dispwin -r</a> - to test whether the VideoLUTs are accessible for a particular - display. See also below, on how to select a different display for - VideoLUT access. Also note that dispcal will fail if the Visual - depth doesn't match the VideoLUT depth. Typically the VideoLUTs have - 256 entries per color component, so the Visual generally needs to be - 24 bits, 8 bits per color component.<br> - <br> - <a name="dnm"></a>Because of the difficulty cause by TwinView and - MergedFB in X11 based systems, you can optionally specify a separate - display number after the display that is going to be used to present - test patches, for accessing the VideoLUT hardware. This must be + + + + + + + +
+ Base name for input[<a href="File_Formats.html#.ti1">.ti1</a>]/output[<a
+ href="File_Formats.html#.ti3">.ti3</a>] file.<br>
+ </small> <br>
+ <b>Examples</b><br>
+ <br>
+ dispread -c1 -i92 mycrt<br>
+ <h3>Comments<br>
+ </h3>
+ This is the tool for exercising a display, in order to measure its
+ color characteristics. The device test colors are defined by the
+ outfile.ti1 file, while the resulting device+colorimetric and
+ optional spectral readings are stored in the outfile.ti3 file.
+ Display calibration curves can be applied during the measurements,
+ and the curves included in the resulting .ti3 data file using the <span
+ style="font-weight: bold;">-k</span>flag. See <a
+ href="dispcal.html">dispcal</a> for information on how to
+ calibrate the display before profiling it. For best results, you
+ should run this against a neutral grey desktop background, and avoid
+ having any bright images or windows on the screen at the time you
+ run it.<br>
+ <br>
+ <a name="v"></a> The <b>-v</b> flag reports progress information.<br>
+ <br>
+ <a name="display"></a><span style="font-weight: bold;">-display</span>:
+ When running on a UNIX based system that used the X11 Windowing
+ System, <b>dispread</b> will by default use the $DISPLAY
+ environment variable to determine which display and screen to read
+ from. This can be overridden by supplying an X11 display name to the
+ <span style="font-weight: bold;">-display</span> option. Note that
+ if Xinerama is active, you can't select the screen using $DISPLAY or
+ -display, you have to select it using the <span style="font-weight:
+ bold;">-d</span> parameter.<br>
+ <br>
+ <a name="d"></a> <span style="font-weight: bold;">-d</span>: By
+ default the main display will be the location of the test window. If
+ the system has more than one display or screen, an alternate
+ display/screen can be selected with the <span style="font-weight:
+ bold;">-d</span> parameter. If you invoke <span
+ style="font-weight: bold;">dispread</span> so as to display the
+ usage information (i.e. "dispread -?" or "dispread --"), then the
+ discovered displays/screens will be listed. Multiple displays may
+ not be listed, if they appear as a single display to the operating
+ system (ie. the multi-display support is hidden in the video card
+ driver). On UNIX based system that used the X11 Windowing System,
+ the <span style="font-weight: bold;">-d</span> parameter will
+ override the screen specified by the $DISPLAY or <span
+ style="font-weight: bold;">-display</span> parameter.<br>
+ <br>
+ On X11 the inability to access VideoLUTs could be because you are
+ trying to access a remote display, and the remote display doesn't
+ support the XF86VidMode extension, or perhaps you are running
+ multiple monitors using NVidia TwinView, or MergedFB, and trying to
+ access anything other than the primary monitor. TwinView and
+ MergedFB don't properly support the XF86VidMode extension for
+ multiple displays. You can use <a href="dispwin.html#r">dispwin -r</a>
+ to test whether the VideoLUTs are accessible for a particular
+ display. See also below, on how to select a different display for
+ VideoLUT access. Also note that dispcal will fail if the Visual
+ depth doesn't match the VideoLUT depth. Typically the VideoLUTs have
+ 256 entries per color component, so the Visual generally needs to be
+ 24 bits, 8 bits per color component.<br>
+ <br>
+ <a name="dnm"></a>Because of the difficulty cause by TwinView and
+ MergedFB in X11 based systems, you can optionally specify a separate
+ display number after the display that is going to be used to present
+ test patches, for accessing the VideoLUT hardware. This must be
specified as a single string, e.g. <span style="font-weight: bold;">-d @@ -844,240 +1114,280 @@ n - 1,2</span> . Some experimentation may be needed using <a - href="dispwin.html">dispwin</a> on such systems, to discover what - screen has access to the VideoLUT hardware, and which screens the - test patches appear on. You may be able to calibrate one screen, and - then share the calibration with another screen. Profiling can be - done independently to calibration.<br> - <br> - <a name="dweb"></a><span style="font-weight: bold;">-dweb</span> or - <span style="font-weight: bold;">-dweb:port</span> starts a - standalone web server on your machine, which then allows a local or - remote web browser to display the the color test patches. By default - port <span style="font-weight: bold;">8080</span> is used, but this - can be overridden by appending a <span style="font-weight: bold;">:</span> - and the port number i.e. <span style="font-weight: bold;">-dweb:8001</span>. - The URL will be <span style="font-weight: bold;">http://</span> - then name of the machine or its I.P. address followed by a colon and - the port number - e.g something like <span style="font-weight: - bold;">http://192.168.0.1:8080</span>. If you use the verbose - option (<span style="font-weight: bold;">-v</span>) then a likely - URL will be printed once the server is started, or you could run <span - style="font-weight: bold;">ipconfig</span> (MSWin) or <span - style="font-weight: bold;">/sbin/ifconfig</span> (Linux or OS X) - and identify an internet address for your machine that way. <b> - JavaScript</b> needs to be enabled in your web browser for this to - work.<br> - <br> - Note that if you use this method of displaying test patches, that - there is no access to the display VideoLUTs and that the colors will - be displayed with 8 bit per component precision, and any - screen-saver or power-saver will not be disabled. You will also be - at the mercy of any color management applied by the web browser, and - may have to carefully review and configure such color management. - See the <a href="dispcal.html#o">-o</a> flag for an explanation of - the implications of having no access to the VideoLUTs.<br> - <br> - <a name="dmadvr"></a><span style="font-weight: bold;">-dmadvr</span> - [MSWin only] causes test patches to be displayed using the MadVR - video renderer. Note that you may have to start the video playback - software and load a video clip in pause for this to work. MadVR - rendering does not need or support VideoLUT access, so the <a - href="#K">-K</a> option should be used to read calibrated values. - Be aware that the state of the Graphics Card VideoLUTs may affect - the results, and therefore may have to be set appropriately using - dispwin. By default the test patch colors will <u>not</u> be - processed by the MadVR 3dLut (see the -<a href="#V">V</a> flag).<br> - <br> - <a name="c"></a> <span style="font-weight: bold;">-c</span>: The - instrument is assumed to communicate through a USB or serial - communication port, and the port can be selected with the <b>-c</b> - option, if the instrument is not connected to the first port. If you - invoke <span style="font-weight: bold;">dispread</span> so as to - display the usage information (i.e. "dispread -?" or "dispread --"), - then the discovered USB and serial ports will be listed. On - UNIX/Linux, a list of all possible serial ports are shown, but not - all of them may actually be present on your system.<br> - <br> - <a name="p"></a>The <span style="font-weight: bold;">-p</span> flag - allows measuring in telephoto mode, using instruments that support - this mode, e.g. the ColorMunki. Telephoto mode is one for taking - emissive measurements from a distance (ie. telespectometer, - tele-colorimeter) mode, and typically would be used for measuring - projector type displays. If a device does not support a specific - telephoto mode, then the normal emissive mode may be suitable for - measuring projectors.<br> - <br> - <a name="y"></a>The <span style="font-weight: bold;">-y</span> flag - allows setting the Display Type. The selection typically determines - two aspects of of the instrument operation: <span - style="font-weight: bold;">1)</span> It may set the measuring mode - to suite <a - href="http://en.wikipedia.org/wiki/Comparison_of_display_technology"><span - style="font-weight: bold;">refresh</span> or <span - style="font-weight: bold;">non-refresh</span> displays</a>. - Typically only LCD (Liquid Crystal) displays have a non-refresh - nature. <span style="font-weight: bold;">2)</span> It may select an - instrument calibration matrix suitable for a particular display - type. The selections available depends on the type and model of - instrument, and a list of the options for the discovered instruments - will be shown in the <a href="ArgyllDoc.html#CmdLine">usage</a> - information. For more details on what particular instruments support - and how this works, see <a href="instruments.html">Operation of - particular instruments</a>. <b>3)</b> Any installed CCSS files - (if applicable), or CCMX files. These files are typically created - using <a href="ccxxmake.html">ccxxmake</a>, - and installed using <a - href="oeminst.html">oeminst</a>. The - default and Base Calibration types will be indicated in the usage.<br> - <br> - <a name="s"></a><span style="font-weight: bold;">-s</span>: By - default only the colorimetric information (XYZ value) will be saved, - but for instruments that support spectral readings (such as the - Gretag Spectrolino), the <b>-s</b> option will save the spectral - readings to the .ti3 file as well.<br> - <br> - <a name="k"></a> <span style="font-weight: bold;">-k: </span>If a - display video lookup table calibration <a - href="File_Formats.html#.cal">.cal</a> file is provided, it will - be loaded into the display <span style="font-weight: bold;">VideoLUTs</span> - while the measurements are being taken, thereby being applied to the - measurement values, and the calibration will also included in the - resulting .ti3 data file, so that <a href="colprof.html">colprof</a> - can include it as a <span style="font-weight: bold;">vcgt</span> - tag in the resulting profile. This is the <span style="font-weight: - bold;">normal</span> way to profile a calibrated display. The - calibration file has usually been created using <a - href="dispcal.html">dispcal</a>. If the calibration file indicates - that the displays VideoLUTs are not accessible, or if they prove not - to be accessible, then dispread will switch to <span - style="font-weight: bold;">-K</span> mode (see below). If a - calibration file is not supplied using <b>-k</b> or <b>-K</b>, - then the display will be measured in whatever calibration state it - is in, and no calibration information is saved to the resulting .ti3 - file.<br> - If the calibration file provided created using video range encoding - (dispcal -E), then the <b>-E</b> option in dispread will be - triggered automatically.<br> - <span style="font-weight: bold;">NOTE</span> that the calibration is - loaded into the display hardware just before the instrument starts - measurement, after the test window first appears.<br> - <br> - <a name="K"></a> <span style="font-weight: bold;">-K: </span>If a - display video lookup table calibration <a - href="File_Formats.html#.cal">.cal</a> file is provided, it will - be applied to the test values for each measurement, and also - included in the resulting .ti3 data file, so that <a - href="colprof.html">colprof</a> can include it as a <span - style="font-weight: bold;">vcgt</span> tag in the resulting - profile. This is <span style="font-weight: bold;">NOT</span> - normally the best way to profile a calibrated display, since the - frame buffer may have lower precision than the VideoLUTs output - values. This is the way calibration should be applied if MadVR is - being used to display the test patches. If a calibration file is not - supplied using <b>-k</b> or <b>-K</b>, then the display will be - measured in whatever calibration state it is in, and no calibration - information is saved to the resulting .ti3 file.<br> - If the calibration file provided created using video range encoding - (dispcal -E), then the <b>-E</b> option in dispread will be - triggered automatically.<br> - <br> - <a name="V"></a><b>-V:</b> [MSWin] If using MadVR to display test - patches, then enable Color Managenent (3dLut). This would be used - for verification measurement.<br> - <br> - <a name="P"></a> The <span style="font-weight: bold;">-P</span> - parameter allows you to position and size the test patch window. By - default it is places in the center of the screen, and sized - appropriately for the type of instrument. The <span - style="font-weight: bold;">ho</span> and <span - style="font-weight: bold;">vo</span> values govern the horizontal - and vertical offset respectively. A value of 0.0 positions the - window to the far left or top of the screen, a value of 0.5 - positions it in the center of the screen (the default), and 1.0 - positions it to the far right or bottom of the screen. If three - parameters are provided, then the <span style="font-weight: bold;">ss</span> - parameter is a scale factor for the test window size. A value of 0.5 - for instance, would produce a half sized window. A value of 2.0 will - produce a double size window. If four parameters are provided, then - the last two set independent horizontal and vertical scaling - factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be - specified as a single string (no space between the numbers and the - comma). For example, to create a double sized test window at the top - right of the screen, use <span style="font-weight: bold;">-P 1,0,2</span> - . To create a window twice as wide as high: <span - style="font-weight: bold;">-P 1,0,2,1</span>.<br> - <br> - <a name="F"></a> The <span style="font-weight: bold;">-F</span> - flag causes the while screen behind the test window to be masked - with black. This can aid black accuracy when measuring CRT displays - or projectors.<br> - <br> - <a name="E"></a> The <span style="font-weight: bold;">-E</span> - flag causes the test values to be scaled to the Video RGB encoding - range of 16/255 to 235/255. If the calibration file provided using - the <b>-k</b> or <b>-K</b> flag was created using video range - encoding, then this option will be triggered automatically.<br> - <br> - <a name="n"></a><span style="font-weight: bold;">-n</span>: When - running on a UNIX based system that used the X11 Windowing System, <b>dispread</b> - normally selects the override redirect so that the test window will - appear above any other windows on the display. On some systems this - can interfere with window manager operation, and the <b>-n</b> - option turns this behaviour off.<br> - <br> - <a name="J"></a> The -<span style="font-weight: bold;">J</span> - option runs through the black and sensor relative calibration - routines for the Xrite DTP92 and DTP94 instrument, the black level - calibration for the Eye-One Display 1, and a CRT frequency - calibration for the Eye-One Display 2. For the black calibration the - instrument should be placed on an opaque, black surface, and any - stray light should be avoided by placing something opaque over the - instrument. If a Spectrolino is being used, then a white and black - calibration will always be performed before the instrument can be - placed on the display, unless the <a href="#N">-N</a> flag is used. - Generally it is not necessary to do a calibration every time an - instrument is used, just now and again. There is no point in - doing a CRT frequency calibration, as this will be done - automatically at the commencement of patch reading.<br> - <br> - <a name="N"></a> <span style="font-weight: bold;">-N</span> Any - instrument that requires regular calibration will ask for - calibration on initial start-up. Sometimes this can be awkward if - the instrument is being mounted in some sort of measuring jig, or - annoying if several sets of readings are being taken in quick - succession. The -<span style="font-weight: bold;">N</span> - suppresses this initial calibration if a valid and not timed out - previous calibration is recorded in the instrument or on the host - computer. It is advisable to only use this option on the second and - subsequent measurements in a single session.<br> - <br> - <a name="H"></a> The -<span style="font-weight: bold;">H</span> - option turns on high resolution spectral mode, if the instrument - supports it. See <a href="instruments.html">Operation of particular - instruments</a> for more details. This may give better accuracy - for display measurements.<br> - <br> - <a name="w"></a>The <b>-w</b> flag disables the normalisation of - the white patch value to 100.0, resulting in values that are in - cd/m^2. This is mainly for diagnostic purposes.<br> - <br> - <a name="X1"></a> The -<span style="font-weight: bold;">X <span - style="font-style: italic;">file.ccmx</span></span> option reads - a <a href="File_Formats.html#.ccmx">Colorimeter Correction Matrix</a> - from the given file, and applies it to the colorimeter instruments - readings. This can improve a colorimeters accuracy for a particular - type of display. A list of contributed <span style="font-weight: - bold;">ccmx</span> files is <a href="ccmxs.html">here</a>.<br> - <br> - <a name="X2"></a> The -<span style="font-weight: bold;">X <span - style="font-style: italic;">file.ccss</span></span> option reads - a <a href="File_Formats.html#.ccss">Colorimeter Calibration - Spectral Sample</a> from the given file, and uses it to set the - colorimeter instruments calibration. This will only work with - colorimeters that rely on sensor spectral sensitivity calibration - information (ie. the X-Rite <span style="font-weight: bold;">i1d3</span>, + + + + + + + +
+ 1,2</span> . Some experimentation may be needed using <a
+ href="dispwin.html">dispwin</a> on such systems, to discover what
+ screen has access to the VideoLUT hardware, and which screens the
+ test patches appear on. You may be able to calibrate one screen, and
+ then share the calibration with another screen. Profiling can be
+ done independently to calibration.<br>
+ <br>
+ <a name="dweb"></a><span style="font-weight: bold;">-dweb</span> or
+ <span style="font-weight: bold;">-dweb:port</span> starts a
+ standalone web server on your machine, which then allows a local or
+ remote web browser to display the the color test patches. By default
+ port <span style="font-weight: bold;">8080</span> is used, but this
+ can be overridden by appending a <span style="font-weight: bold;">:</span>
+ and the port number i.e. <span style="font-weight: bold;">-dweb:8001</span>.
+ The URL will be <span style="font-weight: bold;">http://</span>
+ then name of the machine or its I.P. address followed by a colon and
+ the port number - e.g something like <span style="font-weight:
+ bold;">http://192.168.0.1:8080</span>. If you use the verbose
+ option (<span style="font-weight: bold;">-v</span>) then a likely
+ URL will be printed once the server is started, or you could run <span
+ style="font-weight: bold;">ipconfig</span> (MSWin) or <span
+ style="font-weight: bold;">/sbin/ifconfig</span> (Linux or OS X)
+ and identify an internet address for your machine that way. <b>
+ JavaScript</b> needs to be enabled in your web browser for this to
+ work. You may have to modify any firewall to permit port 8080 to be
+ accessed on your machine.<br>
+ <br>
+ Note that if you use this method of displaying test patches, that
+ there is no access to the display VideoLUTs and that the colors will
+ be displayed with 8 bit per component precision, and any
+ screen-saver or power-saver will not be disabled. You will also be
+ at the mercy of any color management applied by the web browser, and
+ may have to carefully review and configure such color management.
+ See the <a href="dispcal.html#o">-o</a> flag for an explanation of
+ the implications of having no access to the VideoLUTs.<br>
+ <br>
+ <a name="dmadvr"></a><span style="font-weight: bold;">-dmadvr</span>
+ [MSWin only] causes test patches to be displayed using the MadVR
+ video renderer. Note that you may have to start the video playback
+ software and load a video clip in pause for this to work. MadVR
+ rendering does not need or support VideoLUT access, so the <a
+ href="#K">-K</a> option should be used to read calibrated values.
+ Be aware that the state of the Graphics Card VideoLUTs may affect
+ the results, and therefore may have to be set appropriately using
+ dispwin. By default the test patch colors will <u>not</u> be
+ processed by the MadVR 3dLut (see the -<a href="#V">V</a> flag).<br>
+ <br>
+ <a name="dcc"></a><span style="font-weight: bold;">-dcc</span> or <b>-dcc:<i>no</i></b>
+ causes test patches to be displayed using and available <a
+ href="http://en.wikipedia.org/wiki/Chromecast">ChromeCast</a> to
+ your TV. Use <b>-dcc:?</b> to display a list of ChromeCasts on your
+ local network. Note that the ChromeCast as a test patch source is
+ probably the<b> least accurate</b> of your choices, since it
+ up-samples the test patch and transforms from RGB to YCC and back,
+ but should be accurate within ± 1 bit. You may have to modify any
+ firewall to permit port 8081 to be accessed on your machine if it
+ falls back to the Default receiver (see <a href="Installing.html">installation
+ instructions</a> for your platform).<br>
+ <br>
+ <a name="c"></a> <span style="font-weight: bold;">-c</span>: The
+ instrument is assumed to communicate through a USB or serial
+ communication port, and the port can be selected with the <b>-c</b>
+ option, if the instrument is not connected to the first port. If you
+ invoke <span style="font-weight: bold;">dispread</span> so as to
+ display the usage information (i.e. "dispread -?" or "dispread --"),
+ then the discovered USB and serial ports will be listed. On
+ UNIX/Linux, a list of all possible serial ports are shown, but not
+ all of them may actually be present on your system.<br>
+ <br>
+ <a name="p"></a>The <span style="font-weight: bold;">-p</span> flag
+ allows measuring in telephoto mode, using instruments that support
+ this mode, e.g. the ColorMunki. Telephoto mode is one for taking
+ emissive measurements from a distance (ie. telespectometer,
+ tele-colorimeter) mode, and typically would be used for measuring
+ projector type displays. If a device does not support a specific
+ telephoto mode, then the normal emissive mode may be suitable for
+ measuring projectors.<br>
+ <br>
+ <a name="y"></a>The <span style="font-weight: bold;">-y</span> flag
+ allows setting the Display Type. The selection typically determines
+ two aspects of of the instrument operation: <span
+ style="font-weight: bold;">1)</span> It may set the measuring mode
+ to suite <a
+ href="http://en.wikipedia.org/wiki/Comparison_of_display_technology"><span
+ style="font-weight: bold;">refresh</span> or <span
+ style="font-weight: bold;">non-refresh</span> displays</a>.
+ Typically only LCD (Liquid Crystal) displays have a non-refresh
+ nature. <span style="font-weight: bold;">2)</span> It may select an
+ instrument calibration matrix suitable for a particular display
+ type. The selections available depends on the type and model of
+ instrument, and a list of the options for the discovered instruments
+ will be shown in the <a href="ArgyllDoc.html#CmdLine">usage</a>
+ information. For more details on what particular instruments support
+ and how this works, see <a href="instruments.html">Operation of
+ particular instruments</a>. <b>3)</b> Any installed CCSS files
+ (if applicable), or CCMX files. These files are typically created
+ using <a href="ccxxmake.html">ccxxmake</a>, and installed using <a
+ href="oeminst.html">oeminst</a>. The default and Base Calibration
+ types will be indicated in the usage.<br>
+ <br>
+ <a name="s"></a><span style="font-weight: bold;">-s</span>: By
+ default only the colorimetric information (XYZ value) will be saved,
+ but for instruments that support spectral readings (such as the
+ Gretag Spectrolino), the <b>-s</b> option will save the spectral
+ readings to the .ti3 file as well.<br>
+ <br>
+ <a name="k"></a> <span style="font-weight: bold;">-k: </span>If a
+ display video lookup table calibration <a
+ href="File_Formats.html#.cal">.cal</a> file is provided, it will
+ be loaded into the display <span style="font-weight: bold;">VideoLUTs</span>
+ while the measurements are being taken, thereby being applied to the
+ measurement values, and the calibration will also included in the
+ resulting .ti3 data file, so that <a href="colprof.html">colprof</a>
+ can include it as a <span style="font-weight: bold;">vcgt</span>
+ tag in the resulting profile. This is the <span style="font-weight:
+ bold;">normal</span> way to profile a calibrated display. The
+ calibration file has usually been created using <a
+ href="dispcal.html">dispcal</a>. If the calibration file indicates
+ that the displays VideoLUTs are not accessible, or if they prove not
+ to be accessible, then dispread will switch to <span
+ style="font-weight: bold;">-K</span> mode (see below). If a
+ calibration file is not supplied using <b>-k</b> or <b>-K</b>,
+ then the display will be measured in whatever calibration state it
+ is in, and no calibration information is saved to the resulting .ti3
+ file.<br>
+ If the calibration file provided created using video range encoding
+ (dispcal -E), then the <b>-E</b> option in dispread will be
+ triggered automatically.<br>
+ <span style="font-weight: bold;">NOTE</span> that the calibration is
+ loaded into the display hardware just before the instrument starts
+ measurement, after the test window first appears.<br>
+ <br>
+ <a name="K"></a> <span style="font-weight: bold;">-K: </span>If a
+ display video lookup table calibration <a
+ href="File_Formats.html#.cal">.cal</a> file is provided, it will
+ be applied to the test values for each measurement, and also
+ included in the resulting .ti3 data file, so that <a
+ href="colprof.html">colprof</a> can include it as a <span
+ style="font-weight: bold;">vcgt</span> tag in the resulting
+ profile. This is <span style="font-weight: bold;">NOT</span>
+ normally the best way to profile a calibrated display, since the
+ frame buffer may have lower precision than the VideoLUTs output
+ values. This is the way calibration should be applied if MadVR is
+ being used to display the test patches. If a calibration file is not
+ supplied using <b>-k</b> or <b>-K</b>, then the display will be
+ measured in whatever calibration state it is in, and no calibration
+ information is saved to the resulting .ti3 file.<br>
+ If the calibration file provided created using video range encoding
+ (dispcal -E), then the <b>-E</b> option in dispread will be
+ triggered automatically.<br>
+ <br>
+ <a name="V"></a><b>-V:</b> [MSWin] If using MadVR to display test
+ patches, then enable Color Managenent (3dLut). This would be used
+ for verification measurement.<br>
+ <br>
+ <a name="P"></a> The <span style="font-weight: bold;">-P</span>
+ parameter allows you to position and size the test patch window. By
+ default it is places in the center of the screen, and sized
+ appropriately for the type of instrument, or 10% of the width of the
+ display if the display size is unknown. The <span
+ style="font-weight: bold;">ho</span> and <span
+ style="font-weight: bold;">vo</span> values govern the horizontal
+ and vertical offset respectively. A value of 0.0 positions the
+ window to the far left or top of the screen, a value of 0.5
+ positions it in the center of the screen (the default), and 1.0
+ positions it to the far right or bottom of the screen. If three
+ parameters are provided, then the <span style="font-weight: bold;">ss</span>
+ parameter is a scale factor for the test window size. A value of 0.5
+ for instance, would produce a half sized window. A value of 2.0 will
+ produce a double size window. If four parameters are provided, then
+ the last two set independent horizontal and vertical scaling
+ factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be
+ specified as a single string (no space between the numbers and the
+ comma). For example, to create a double sized test window at the top
+ right of the screen, use <span style="font-weight: bold;">-P 1,0,2</span>
+ . To create a window twice as wide as high: <span
+ style="font-weight: bold;">-P 1,0,2,1</span>.<br>
+ <br>
+ <a name="F"></a> The <span style="font-weight: bold;">-F</span>
+ flag causes the while screen behind the test window to be masked
+ with black. This can aid black accuracy when measuring CRT displays
+ or projectors.<br>
+ <br>
+ <a name="E"></a> The <span style="font-weight: bold;">-E</span>
+ flag causes the test values to be scaled to the Video RGB encoding
+ range of 16/255 to 235/255. If the calibration file provided using
+ the <b>-k</b> or <b>-K</b> flag was created using video range
+ encoding, then this option will be triggered automatically. This
+ will also set quantization of 8 bits (see -Z flag below). If your
+ video connection is better than 8 bits (ie. 10 or 12 bits), then you
+ may wish to raise this default.<br>
+ <br>
+ <a name="Z"></a> <b>-Z nbits </b>Normally the target device values
+ are floating point numbers that may get rounded and quantized in the
+ process of printing them or reproducing them on the display device.
+ If some of this quantization can be accounted for, it may improve
+ the accuracy of the resulting profile, and the <span
+ style="font-weight: bold;">Q</span> parameter allows this
+ quantization to be specified. The parameter is the number of binary
+ digits (bits) that the device values should be quantized to. An idea
+ of the number of bits of precision that makes its way to your
+ display can be obtained by using <a href="dispcal.html#R">dispcal
+ -R</a> If Video encoding is selected (see -E flag above), then 8
+ bits is selected by default. On systems using an VGA connection or
+ Display Port with a graphics card with VideoLUT entries with greater
+ than 8 bits depth, or if using the MadVR rendered with dithering,
+ then a higher bit depth is typically possible.<br>
+ <br>
+ <a name="n"></a><span style="font-weight: bold;">-n</span>: When
+ running on a UNIX based system that used the X11 Windowing System, <b>dispread</b>
+ normally selects the override redirect so that the test window will
+ appear above any other windows on the display. On some systems this
+ can interfere with window manager operation, and the <b>-n</b>
+ option turns this behaviour off.<br>
+ <br>
+ <a name="J"></a> The -<span style="font-weight: bold;">J</span>
+ option runs through the black and sensor relative calibration
+ routines for the Xrite DTP92 and DTP94 instrument, the black level
+ calibration for the Eye-One Display 1, and a CRT frequency
+ calibration for the Eye-One Display 2. For the black calibration the
+ instrument should be placed on an opaque, black surface, and any
+ stray light should be avoided by placing something opaque over the
+ instrument. If a Spectrolino is being used, then a white and black
+ calibration will always be performed before the instrument can be
+ placed on the display, unless the <a href="#N">-N</a> flag is used.
+ Generally it is not necessary to do a calibration every time an
+ instrument is used, just now and again. There is no point in
+ doing a CRT frequency calibration, as this will be done
+ automatically at the commencement of patch reading.<br>
+ <br>
+ <a name="N"></a> <span style="font-weight: bold;">-N</span> Any
+ instrument that requires regular calibration will ask for
+ calibration on initial start-up. Sometimes this can be awkward if
+ the instrument is being mounted in some sort of measuring jig, or
+ annoying if several sets of readings are being taken in quick
+ succession. The -<span style="font-weight: bold;">N</span>
+ suppresses this initial calibration if a valid and not timed out
+ previous calibration is recorded in the instrument or on the host
+ computer. It is advisable to only use this option on the second and
+ subsequent measurements in a single session.<br>
+ <br>
+ <a name="H"></a> The -<span style="font-weight: bold;">H</span>
+ option turns on high resolution spectral mode, if the instrument
+ supports it. See <a href="instruments.html">Operation of particular
+ instruments</a> for more details. This may give better accuracy
+ for display measurements.<br>
+ <br>
+ <a name="w"></a>The <b>-w</b> flag disables the normalisation of
+ the white patch value to 100.0, resulting in values that are in
+ cd/m^2. This is mainly for diagnostic purposes.<br>
+ <br>
+ <a name="X1"></a> The -<span style="font-weight: bold;">X <span
+ style="font-style: italic;">file.ccmx</span></span> option reads
+ a <a href="File_Formats.html#.ccmx">Colorimeter Correction Matrix</a>
+ from the given file, and applies it to the colorimeter instruments
+ readings. This can improve a colorimeters accuracy for a particular
+ type of display. A list of contributed <span style="font-weight:
+ bold;">ccmx</span> files is <a href="ccmxs.html">here</a>.<br>
+ <br>
+ <a name="X2"></a> The -<span style="font-weight: bold;">X <span
+ style="font-style: italic;">file.ccss</span></span> option reads
+ a <a href="File_Formats.html#.ccss">Colorimeter Calibration
+ Spectral Sample</a> from the given file, and uses it to set the
+ colorimeter instruments calibration. This will only work with
+ colorimeters that rely on sensor spectral sensitivity calibration
+ information (ie. the X-Rite <span style="font-weight: bold;">i1d3</span>,
or the DataColor <span style="font-weight: bold;">Spyder4</span>).This can improve @@ -1104,144 +1414,152 @@ a - colorimeters accuracy for a particular type of display.<br> - <br> - <a name="Q"></a> The <b>-Q</b> flag allows specifying a tristimulus - observer, and is used to compute PCS (Profile Connection Space) - tristimulus values from spectral readings or using a colorimeter - that has CCSS capability. The following choices are available:<br> - <b> 1931_2</b> selects the standard CIE 1931 2 degree - observer. The default.<br> - <b>1964_10</b> selects the standard CIE 1964 10 degree - observer.<br> - <b>1955_2</b> selects the Stiles and Birch 1955 2 degree - observer<br> - <b>1978_2 </b>selects the Judd and Voss 1978 2 degree - observer<br> - <b>shaw</b> selects the Shaw and Fairchild 1997 2 degree - observer<br> - <b>1964_10c</b> selects a version of the CIE 1964 10 degree - observer that has been adjusted using a 3x3 matrix to better agree - with the 1931 2 degree observer.<br> - <br> - <span style="font-weight: bold;">NOTE</span> that if you select - anything other than the default 1931 2 degree observer, that the Y - values will not be cd/m^2, due to the Y curve not being the CIE 1924 - photopic V(λ) luminosity function.<br> - <br> - <a name="I"></a> The -<span style="font-weight: bold;">I <span - style="font-style: italic;">b|w</span></span> options invoke - instrument black level, and display white level compensation - (respectively). Instrument black level drift compensation attempts - to combat instrument black calibration drift by using a display - black test patch as a reference. If an instrument is not - acclimatised sufficiently to the measurement conditions, changes in - temperature can affect the black readings. Display white level drift - compensation attempts to combat changes in display brightness as it - warms up by measuring a white patch every so often, and using it to - normalise all the other readings. If just instrument black drift - compensation is needed, use <span style="font-weight: bold;">-Ib</span>. - If just display white level compensation is needed, use <span - style="font-weight: bold;">-Iw</span>. If both are needed, use <span - style="font-weight: bold;">-Ibw</span> or <span - style="font-weight: bold;">-Iwb</span>.<br> - <br> - <a name="YR"></a> The -<span style="font-weight: bold;">Y R:<i>rate</i></span> - options overrides calibration of the instrument refresh rate. This - may be useful if the instrument supports this function and the - refresh rate cannot be accurately calibrated from the display - itself.<br> - <span style="font-weight: bold;"> <br> - </span><a name="YA"></a> The -<span style="font-weight: bold;">Y A</span> - option uses a non-adaptive integration time emission measurement - mode, if the instrument supports it, such as the Eye-One Pro or - ColorMunki. By default an adaptive integration time measurement mode - will be used for emission measurements, but some instruments support - a fixed integration time mode that can be used with display devices. - This may give increased consistency and faster measurement times, - but may also give less accurate low level readings.<br> - <br> - <a name="Yp"></a> The -<span style="font-weight: bold;">Y p</span> - option skips asking the user to place the instrument on the display. - Normally a grey patch is displayed, and then the user is asked to - confirm that the instrument is in place, so that readings can - commence. This flag disables that check. This may be useful in - automating certain operations.<br> - <span style="font-weight: bold;"><br> - </span><a name="C"></a> The -<span style="font-weight: bold;">C</span> - <span style="font-weight: bold;">"command" </span>option allows a - method of relaying each test value to some other display than that - on the system running dispread (for instance, a photo frame, PDA - screen etc.), by causing the given command to be invoked to the - shell, with six arguments. The first three arguments are the RGB - test color as integers in the range 0 to 255, the second three - parameters are the RGB test color as floating point numbers in the - range 0.0 to 1.0. The script or tool should relay the given color to - the screen in some manner (e.g. by generating a raster file of the - given color and sending it to the display being profiled), before - returning. Note that a test window will also be created on the - system running dispread.<br> - <br> - <a name="M"></a> The -<span style="font-weight: bold;">M</span> <span - style="font-weight: bold;">"command" </span>option allows a - method of gathering each test value from some external source, such - as an instrument that is not directly supported by Argyll. The given - command is involked to the shell, with six arguments. The first - three arguments are the RGB test color as integers in the range 0 to - 255, the second three parameters are the RGB test color as floating - point numbers in the range 0.0 to 1.0. The script or tool should - create a file called <span style="font-weight: bold;">"command.meas</span>" - that contains the XYZ values for the given RGB (or measured from the - test window) in cd/m^2 as three numbers separated by spaces, before - returning. If the command returns a non-zero return value, dispread - will abort. Note that a test window will also be created on the - system running dispread.<br> - <br> - <a name="W"></a>The <b>-W</b> <span style="font-weight: bold;">n|h|x</span> - parameter overrides the default serial communications flow control - setting. The value <span style="font-weight: bold;">n</span> turns - all flow control off, <span style="font-weight: bold;">h</span> - sets hardware handshaking, and <span style="font-weight: bold;">x</span> - sets Xon/Xoff handshaking. This commend may be useful in workaround - serial communications issues with some systems and cables. <br> - <br> - <a name="D"></a>The <b>-D</b> flag causes communications and other - instrument diagnostics to be printed to stdout. A level can be set - between 1 .. 9, that may give progressively more verbose - information, depending on the instrument. This can be useful in - tracking down why an instrument can't connect.<br> - <br> - <a name="p1"></a> The final parameter on the command line is the - base filename for the <a href="File_Formats.html#.ti1">.ti1</a> - input file, and the <a href="File_Formats.html#.ti3">.ti3</a> - output file. <b>dispread</b> will add the .ti1 and .ti3 extensions - automatically.<br> - <br> - <span style="font-weight: bold;">NOTE</span> that on an X11 system, - if the environment variable <span style="font-weight: bold;">ARGYLL_IGNORE_XRANDR1_2</span> - is set (ie. set it to "yes"), then the presence of the XRandR 1.2 - extension will be ignored, and other extensions such as Xinerama and - XF86VidMode extension will be used. This may be a way to work around - buggy XRandR 1.2 implementations.<br> - <br> - <hr style="width: 100%; height: 2px;"><br> - If a large number of patches is being read, the screensaver on many - systems can interfere with the operation of dispread. It is - therefore advisable in these cases to manually turn off the - screensaver before commencing the measurements.<br> - <br> - If communications break down with a USB connected instrument, you - may have to unplug it, and plug it in again to recover.<br> - <br> - Some systems (Apple OSX in particular) have a special set of user - interface controls ("Universal Access") that allows altering the - display in ways designed to assist visually impaired users, by - increasing contrast etc. This will interfere badly with any attempts - to calibrate or profile such a system, and must be turned off in - order to do so. Note that certain magic keyboard sequences can turn - this on by accident.<br> - <br> - <br> - <br> - </body> -</html> + + + + + + + +
+ colorimeters accuracy for a particular type of display.<br>
+ <br>
+ <a name="Q"></a> The <b>-Q</b> flag allows specifying a tristimulus
+ observer, and is used to compute PCS (Profile Connection Space)
+ tristimulus values from spectral readings or using a colorimeter
+ that has CCSS capability. The following choices are available:<br>
+ <b> 1931_2</b> selects the standard CIE 1931 2 degree
+ observer. The default.<br>
+ <b>1964_10</b> selects the standard CIE 1964 10 degree
+ observer.<br>
+ <b>1955_2</b> selects the Stiles and Birch 1955 2 degree
+ observer<br>
+ <b>1978_2 </b>selects the Judd and Voss 1978 2 degree
+ observer<br>
+ <b>shaw</b> selects the Shaw and Fairchild 1997 2 degree
+ observer<br>
+ <b>1964_10c</b> selects a version of the CIE 1964 10 degree
+ observer that has been adjusted using a 3x3 matrix to better agree
+ with the 1931 2 degree observer.<br>
+ <br>
+ <span style="font-weight: bold;">NOTE</span> that if you select
+ anything other than the default 1931 2 degree observer, that the Y
+ values will not be cd/m^2, due to the Y curve not being the CIE 1924
+ photopic V(λ) luminosity function.<br>
+ <br>
+ <a name="I"></a> The -<span style="font-weight: bold;">I <span
+ style="font-style: italic;">b|w</span></span> options invoke
+ instrument black level, and display white level compensation
+ (respectively). Instrument black level drift compensation attempts
+ to combat instrument black calibration drift by using a display
+ black test patch as a reference. If an instrument is not
+ acclimatised sufficiently to the measurement conditions, changes in
+ temperature can affect the black readings. Display white level drift
+ compensation attempts to combat changes in display brightness as it
+ warms up by measuring a white patch every so often, and using it to
+ normalise all the other readings. If just instrument black drift
+ compensation is needed, use <span style="font-weight: bold;">-Ib</span>.
+ If just display white level compensation is needed, use <span
+ style="font-weight: bold;">-Iw</span>. If both are needed, use <span
+ style="font-weight: bold;">-Ibw</span> or <span
+ style="font-weight: bold;">-Iwb</span>.<br>
+ <br>
+ <a name="YR"></a> The -<span style="font-weight: bold;">Y R:<i>rate</i></span>
+ options overrides calibration of the instrument refresh rate. This
+ may be useful if the instrument supports this function and the
+ refresh rate cannot be accurately calibrated from the display
+ itself.<br>
+ <span style="font-weight: bold;"> <br>
+ </span><a name="YA"></a> The -<span style="font-weight: bold;">Y A</span>
+ option uses a non-adaptive integration time emission measurement
+ mode, if the instrument supports it, such as the Eye-One Pro,
+ ColorMunki, i1d3 and K10. By default an adaptive integration time
+ measurement mode will be used for emission measurements, but some
+ instruments support a fixed integration time mode that can be used
+ with display devices. This may give faster measurement times, but
+ may also give less accurate low level readings.<br>
+ <br>
+ <a name="Yp"></a> The -<span style="font-weight: bold;">Y p</span>
+ option skips asking the user to place the instrument on the display.
+ Normally a grey patch is displayed, and then the user is asked to
+ confirm that the instrument is in place, so that readings can
+ commence. This flag disables that check. This may be useful in
+ automating certain operations.<br>
+ <span style="font-weight: bold;"><br>
+ </span><a name="C"></a> The -<span style="font-weight: bold;">C</span>
+ <span style="font-weight: bold;">"command" </span>option allows a
+ method of relaying each test value to some other display than that
+ on the system running dispread (for instance, a photo frame, PDA
+ screen etc.), by causing the given command to be invoked to the
+ shell, with six arguments. The first three arguments are the RGB
+ test color as integers in the range 0 to 255, the second three
+ parameters are the RGB test color as floating point numbers in the
+ range 0.0 to 1.0. The script or tool should relay the given color to
+ the screen in some manner (e.g. by generating a raster file of the
+ given color and sending it to the display being profiled), before
+ returning. Note that a test window will also be created on the
+ system running dispread.<br>
+ <br>
+ <a name="M"></a> The -<span style="font-weight: bold;">M</span> <span
+ style="font-weight: bold;">"command" </span>option allows a
+ method of gathering each test value from some external source, such
+ as an instrument that is not directly supported by Argyll. The given
+ command is involked to the shell, with six arguments. The first
+ three arguments are the RGB test color as integers in the range 0 to
+ 255, the second three parameters are the RGB test color as floating
+ point numbers in the range 0.0 to 1.0. The script or tool should
+ create a file called <span style="font-weight: bold;">"command.meas</span>"
+ that contains the XYZ values for the given RGB (or measured from the
+ test window) in cd/m^2 as three numbers separated by spaces, before
+ returning. If the command returns a non-zero return value, dispread
+ will abort. Note that a test window will also be created on the
+ system running dispread.<br>
+ <br>
+ <a name="W"></a>The <b>-W</b> <span style="font-weight: bold;">n|h|x</span>
+ parameter overrides the default serial communications flow control
+ setting. The value <span style="font-weight: bold;">n</span> turns
+ all flow control off, <span style="font-weight: bold;">h</span>
+ sets hardware handshaking, and <span style="font-weight: bold;">x</span>
+ sets Xon/Xoff handshaking. This commend may be useful in workaround
+ serial communications issues with some systems and cables. <br>
+ <br>
+ <a name="D"></a>The <b>-D</b> flag causes communications and other
+ instrument diagnostics to be printed to stdout. A level can be set
+ between 1 .. 9, that may give progressively more verbose
+ information, depending on the instrument. This can be useful in
+ tracking down why an instrument can't connect.<br>
+ <br>
+ <a name="p1"></a> The final parameter on the command line is the
+ base filename for the <a href="File_Formats.html#.ti1">.ti1</a>
+ input file, and the <a href="File_Formats.html#.ti3">.ti3</a>
+ output file. <b>dispread</b> will add the .ti1 and .ti3 extensions
+ automatically.<br>
+ <br>
+ <span style="font-weight: bold;">NOTE</span> that on an X11 system,
+ if the environment variable <span style="font-weight: bold;">ARGYLL_IGNORE_XRANDR1_2</span>
+ is set (ie. set it to "yes"), then the presence of the XRandR 1.2
+ extension will be ignored, and other extensions such as Xinerama and
+ XF86VidMode extension will be used. This may be a way to work around
+ buggy XRandR 1.2 implementations.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ If a large number of patches is being read, the screensaver on many
+ systems can interfere with the operation of dispread. It is
+ therefore advisable in these cases to manually turn off the
+ screensaver before commencing the measurements.<br>
+ <br>
+ If communications break down with a USB connected instrument, you
+ may have to unplug it, and plug it in again to recover.<br>
+ <br>
+ Some systems (Apple OSX in particular) have a special set of user
+ interface controls ("Universal Access") that allows altering the
+ display in ways designed to assist visually impaired users, by
+ increasing contrast etc. This will interfere badly with any attempts
+ to calibrate or profile such a system, and must be turned off in
+ order to do so. Note that certain magic keyboard sequences can turn
+ this on by accident.<br>
+ <br>
+ <br>
+ <br>
+ </body>
+</html>
diff --git a/doc/dispwin.html b/doc/dispwin.html index f1d75f5..6036e76 100644 --- a/doc/dispwin.html +++ b/doc/dispwin.html @@ -1,38 +1,38 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<html> - <head> - <title>dispwin</title> - <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> - <meta name="author" content="Graeme Gill"> - </head> - <body> - <h2><b>spectro/dispwin</b></h2> - <h3>Summary</h3> - This tool has several different but related functions. When given as - a file argument an ICC profile containing vcgt "gamma" curves, or an - Argyll video calibration .cal file, it will load that calibration - into the chosen display. It can also install or uninstall a profile - in the system for the chosen display, or set the display calibration - to that in the currently installed system profile. By default it - displays a test window the same as that used by dispcal and - dispread, to test this functionality. It can also be used to test - the ability to load video card LUT curves to each display, and to - test how the console Bell will sound when used with some instruments - (ie. Eye-One Pro).<br> - <br> - [Note that in OS X 10.7 Lion, changes to the default system profile - permissions mean that you can't set a calibration persistently when - the default system profile is being used, unless you run as root - (ie. use sudo). Note that you do <span style="font-weight: bold;">not</span> - need to run as root to install a user profile (-Su, the default - install type.)]<br> - <h3>Usage</h3> - <font size="-1"><span style="font-family: monospace;">dispwin - [options] [<span style="font-style: italic;">calfile</span>]</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#v">-v</a><span +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+ <head>
+ <title>dispwin</title>
+ <meta http-equiv="content-type" content="text/html;
+ charset=windows-1252">
+ <meta name="author" content="Graeme Gill">
+ </head>
+ <body>
+ <h2><b>spectro/dispwin</b></h2>
+ <h3>Summary</h3>
+ This tool has several different but related functions. When given as
+ a file argument an ICC profile containing vcgt "gamma" curves, or an
+ Argyll video calibration .cal file, it will load that calibration
+ into the chosen display. It can also install or uninstall a profile
+ in the system for the chosen display, or set the display calibration
+ to that in the currently installed system profile. By default it
+ displays a test window the same as that used by dispcal and
+ dispread, to test this functionality. It can also be used to test
+ the ability to load video card LUT curves to each display, and to
+ test how the console Bell will sound when used with some instruments
+ (ie. Eye-One Pro).<br>
+ <br>
+ [Note that in OS X 10.7 Lion, changes to the default system profile
+ permissions mean that you can't set a calibration persistently when
+ the default system profile is being used, unless you run as root
+ (ie. use sudo). Note that you do <span style="font-weight: bold;">not</span>
+ need to run as root to install a user profile (-Su, the default
+ install type.)]<br>
+ <h3>Usage</h3>
+ <font size="-1"><span style="font-family: monospace;">dispwin
+ [options] [<span style="font-style: italic;">calfile</span>]</span><br
+ style="font-family: monospace;">
+ <span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#v">-v</a><span
style="font-family: monospace;"> Verbose @@ -47,17 +47,21 @@ Verbose - mode<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> </span><a style="font-family: monospace;" - href="#display">-display displayname</a><span - style="font-family: monospace;"> [<span style="font-weight: - bold;">X11 only</span>] Choose X11 display name<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> <a href="#dnm">-d n[,m]</a> - - [<span style="font-weight: bold;">X11 only</span>] Choose the - display from the following list (default 1),<br> + + + +
+ mode<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
+ href="#display">-display displayname</a><span
+ style="font-family: monospace;"> [<span style="font-weight:
+ bold;">X11 only</span>] Choose X11 display name<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> <a href="#dnm">-d n[,m]</a>
+
+ [<span style="font-weight: bold;">X11 only</span>] Choose the
+ display from the following list (default 1),<br>
and optionally @@ -72,8 +76,12 @@ optionally - choose a different display m for Video LUT access.<br> - </span></font><font size="-1"><span style="font-family: + + + +
+ choose a different display m for Video LUT access.<br>
+ </span></font><font size="-1"><span style="font-family:
monospace;"> <a href="#d">-d n</a> [Not X11] @@ -88,8 +96,12 @@ X11] - Choose the display from the following list (default 1)<br> - </span></font><span style="font-family: monospace;"> <a + + + +
+ Choose the display from the following list (default 1)<br>
+ </span></font><span style="font-family: monospace;"> <a
href="#dweb">-dweb[:port]</a> @@ -100,16 +112,24 @@ X11] - Display via a web server at port (default 8080)</span><br> - <span style="font-family: monospace;"> <a - href="dispwin.html#dmadvr">-dmadvr</a> - - [MSWin] Display via MadVR Video Renderer</span><br - style="font-family: monospace;"> - <font size="-1"><span style="font-family: monospace;"></span><span - style="font-family: monospace;"> <a href="#P">-P - ho,vo,ss[,vs]</a> Position test window - and scale it</span><br style="font-family: monospace;"> + + + +
+ Display via a web server at port (default 8080)</span><br>
+ <span style="font-family: monospace;"> <a
+ href="dispwin.html#dmadvr">-dmadvr</a>
+
+ [MSWin] Display via MadVR Video Renderer</span><br>
+ <tt> </tt><tt><a href="#dcc">-dcc[:n]</a> + +
+ </tt><tt></tt><tt>Display via n'th ChromeCast (default 1, ? for
+ list)</tt><br style="font-family: monospace;">
+ <font size="-1"><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"> <a href="#P">-P
+ ho,vo,ss[,vs]</a> Position test window
+ and scale it</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> ho,vi: 0.0 @@ -124,8 +144,12 @@ ho,vi: - = left/top, 0.5 = center, 1.0 = right/bottom etc.</span><br - style="font-family: monospace;"> + + + +
+ = left/top, 0.5 = center, 1.0 = right/bottom etc.</span><br
+ style="font-family: monospace;">
<span style="font-family: monospace;"> ss: 0.5 @@ -140,7 +164,11 @@ ss: - = half, 1.0 = normal, 2.0 = double etc.<br> + + + +
+ = half, 1.0 = normal, 2.0 = double etc.<br>
@@ -149,9 +177,13 @@ ss: - ss,vs: = optional horizontal, vertical scale.<br> - </span></font><font size="-1"><span style="font-family: - monospace;"><a href="#F">-F</a> + + + +
+ ss,vs: = optional horizontal, vertical scale.<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"><a href="#F">-F</a>
Fill whole @@ -166,30 +198,38 @@ whole - screen with black background</span></font><br> - <font size="-1"><span style="font-family: monospace;"> </span></font><font - size="-1"><span style="font-family: monospace;"><a href="#E">-E</a> + + + +
+ screen with black background</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> </span></font><font
+ size="-1"><span style="font-family: monospace;"><a href="#E">-E</a>
- </span></font><small><span style="font-family: monospace;">Video - encode output as (16-235)/255 "TV" levels</span></small><br - style="font-family: monospace;"> - <font size="-1"><span style="font-family: monospace;"></span><span - style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#i">-i</a><span - style="font-family: monospace;"> - - Run forever with random values<br> - <a href="#G">-G <span style="font-style: italic;">filename</span></a> - Display RGB - colors from CGATS file<br> - </span></font><font size="-1"><a style="font-family: - monospace;" href="#m">-m</a><span style="font-family: - monospace;"> - - Manually step through colors</span></font><br> - <font size="-1"><span style="font-family: monospace;"> <a + + + +
+ </span></font><small><span style="font-family: monospace;">Video
+ encode output as (16-235)/255 "TV" levels</span></small><br
+ style="font-family: monospace;">
+ <font size="-1"><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#i">-i</a><span
+ style="font-family: monospace;">
+
+ Run forever with random values<br>
+ <a href="#G">-G <span style="font-style: italic;">filename</span></a>
+ Display RGB
+ colors from CGATS file<br>
+ </span></font><font size="-1"><a style="font-family:
+ monospace;" href="#m">-m</a><span style="font-family:
+ monospace;">
+
+ Manually step through colors</span></font><br>
+ <font size="-1"><span style="font-family: monospace;"> <a
href="#r">-r</a> Test just @@ -204,9 +244,13 @@ just - video LUT loading & Beeps<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> <a href="#n">-n</a> + + + +
+ video LUT loading & Beeps<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> <a href="#n">-n</a>
Test native @@ -221,7 +265,11 @@ native - display values (rather than through Video LUT and C.M.)<br> + + + +
+ display values (rather than through Video LUT and C.M.)<br>
<a href="#s">-s <span style="font-style: italic;">filename.cal</span></a> Save the @@ -236,9 +284,13 @@ the - currently loaded Video LUT to 'filename'<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> <a href="#c">-c</a> + + + +
+ currently loaded Video LUT to 'filename'<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> <a href="#c">-c</a>
Load a @@ -253,10 +305,14 @@ a - linear display calibration (clear calibration)</span></font><font - size="-1"><span style="font-family: monospace;"><br> - </span></font><font size="-1"><span style="font-family: - monospace;"> <a href="#V">-V</a> + + + +
+ linear display calibration (clear calibration)</span></font><font
+ size="-1"><span style="font-family: monospace;"><br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> <a href="#V">-V</a>
Verify that @@ -271,9 +327,13 @@ that - calfile/profile cal. is currently loaded in LUT<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> <a href="#I">-I</a> + + + +
+ calfile/profile cal. is currently loaded in LUT<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> <a href="#I">-I</a>
@@ -286,10 +346,14 @@ that - </span></font><font size="-1"><span style="font-family: - monospace;">Install profile for display and use it's calibration<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> <a href="#U">-U</a> + + + +
+ </span></font><font size="-1"><span style="font-family:
+ monospace;">Install profile for display and use it's calibration<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> <a href="#U">-U</a>
@@ -302,8 +366,12 @@ that - </span></font><font size="-1"><span style="font-family: - monospace;">Un-install profile for display<br> + + + +
+ </span></font><font size="-1"><span style="font-family:
+ monospace;">Un-install profile for display<br>
<a href="#S">-S d</a> Specify the @@ -318,7 +386,11 @@ the - install/uninstall scope for OS X [nlu] or Vista [lu]<br> + + + +
+ install/uninstall scope for OS X [nlu] or Vista [lu]<br>
d is @@ -333,10 +405,14 @@ is - one of: n = network, l = local system, u = user (default)<br> - </span></font><font size="-1"><span style="font-family: - monospace;"></span></font><font size="-1"><span - style="font-family: monospace;"> <a href="#L">-L</a> + + + +
+ one of: n = network, l = local system, u = user (default)<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"></span></font><font size="-1"><span
+ style="font-family: monospace;"> <a href="#L">-L</a>
@@ -349,10 +425,14 @@ is - </span></font><font size="-1"><span style="font-family: - monospace;">Load installed profiles cal. into Video LUT<br> - </span></font><font size="-1"><span style="font-family: - monospace;"> <a href="#X">-<font size="-1">X</font></a> + + + +
+ </span></font><font size="-1"><span style="font-family:
+ monospace;">Load installed profiles cal. into Video LUT<br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> <a href="#X">-<font size="-1">X</font></a>
@@ -365,10 +445,14 @@ is - [<span style="font-weight: bold;">X11 only</span>] Run in daemon - loader mode for given X11 server <br> - </span></font><font size="-1"><span style="font-family: - monospace;"> </span><a style="font-family: monospace;" + + + +
+ [<span style="font-weight: bold;">X11 only</span>] Run in daemon
+ loader mode for given X11 server <br>
+ </span></font><font size="-1"><span style="font-family:
+ monospace;"> </span><a style="font-family: monospace;"
href="#D">-D [level]</a><span style="font-family: monospace;"> Print debug @@ -383,13 +467,17 @@ debug - diagnostics to stderr</span></font><font size="-1"><span - style="font-family: monospace;"></span></font><font size="-1"><span - style="font-family: monospace;"></span><span style="font-family: - monospace;"><br> - </span></font><a style="font-family: monospace;" - href="#p1"><font size="-1"><span style="font-family: monospace;"></span></font></a><font - size="-1"><a style="font-family: monospace;" href="#p1"><i>calfile</i></a><span + + + +
+ diagnostics to stderr</span></font><font size="-1"><span
+ style="font-family: monospace;"></span></font><font size="-1"><span
+ style="font-family: monospace;"></span><span style="font-family:
+ monospace;"><br>
+ </span></font><a style="font-family: monospace;"
+ href="#p1"><font size="-1"><span style="font-family: monospace;"></span></font></a><font
+ size="-1"><a style="font-family: monospace;" href="#p1"><i>calfile</i></a><span
style="font-family: monospace;"> Load display @@ -404,59 +492,63 @@ display - calibration (<a href="cal_format.html">.cal</a> or .icm) into - LUT, and exit.</span><span style="font-family: monospace;"></span><span - style="font-family: monospace;"></span></font><br> - <br> - <h3>Comments<br> - </h3> - <a name="v"></a> The <b>-v</b> flag makes the program more - verbose..<br> - <br> - <a name="display"></a><span style="font-weight: bold;">display</span>: - When running on a UNIX based system that used the X11 Windowing - System, <b>dispwin</b> will by default use the $DISPLAY environment - variable to determine which display and screen to read from. This - can be overridden by supplying an X11 display name to the <span - style="font-weight: bold;">-display</span> option. Note that if - Xinerama is active, you can't select the screen using $DISPLAY or - -display, you have to select it using the <span style="font-weight: - bold;">-d</span> parameter.<br> - <br> - <a name="d"></a><span style="font-weight: bold;">-d</span>: By - default the location of the test window will be the main display. If - the system has more than one display or screen, an alternate - display/screen can be selected with the <span style="font-weight: - bold;">-d</span> parameter. If you invoke <span - style="font-weight: bold;">dispwin</span> so as to display the - usage information (i.e. "dispcal -?" or "dispcal --"), then the - discovered displays/screens will be listed. Multiple displays may - not be listed if they appear as a single display to the operating - system (ie. the multi-display support is hidden in the video card - driver). On UNIX based system that used the X11 Windowing System, - the <span style="font-weight: bold;">-d</span> parameter will - override the screen specified by the $DISPLAY or <span - style="font-weight: bold;">-display</span> parameter.<br> - <span style="font-weight: bold;"></span><br> - <span style="font-weight: bold;">Note</span> that if VideoLUTs for a - display are not accessible (i.e. no hardware calibration - capability), <span style="font-weight: bold;">dispwin</span> will - will issue a warning or fail when it attempts to access them.<br> - <br> - On X11 the inability to access VideoLUTs could be because you are - trying to access a remote display, and the remote display doesn't - support the XF86VidMode extension, or perhaps you are running - multiple monitors using NVidia TwinView, or MergedFB, and trying to - access anything other than the primary monitor. TwinView and - MergedFB don't properly support the XF86VidMode extension for - multiple displays. You can use <a href="dispwin.html#r">dispwin -r</a> - to test whether the VideoLUTs are accessible for a particular - display. See also below, on how to select a different display for - VideoLUT access. Also note that dispcal will fail if the Visual - depth doesn't match the VideoLUT depth. Typically the VideoLUTs have - 256 entries per color component, so the Visual generally needs to be - 24 bits, 8 bits per color component.<br> - <br> + + + +
+ calibration (<a href="cal_format.html">.cal</a> or .icm) into
+ LUT, and exit.</span><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"></span></font><br>
+ <br>
+ <h3>Comments<br>
+ </h3>
+ <a name="v"></a> The <b>-v</b> flag makes the program more
+ verbose..<br>
+ <br>
+ <a name="display"></a><span style="font-weight: bold;">display</span>:
+ When running on a UNIX based system that used the X11 Windowing
+ System, <b>dispwin</b> will by default use the $DISPLAY environment
+ variable to determine which display and screen to read from. This
+ can be overridden by supplying an X11 display name to the <span
+ style="font-weight: bold;">-display</span> option. Note that if
+ Xinerama is active, you can't select the screen using $DISPLAY or
+ -display, you have to select it using the <span style="font-weight:
+ bold;">-d</span> parameter.<br>
+ <br>
+ <a name="d"></a><span style="font-weight: bold;">-d</span>: By
+ default the location of the test window will be the main display. If
+ the system has more than one display or screen, an alternate
+ display/screen can be selected with the <span style="font-weight:
+ bold;">-d</span> parameter. If you invoke <span
+ style="font-weight: bold;">dispwin</span> so as to display the
+ usage information (i.e. "dispcal -?" or "dispcal --"), then the
+ discovered displays/screens will be listed. Multiple displays may
+ not be listed if they appear as a single display to the operating
+ system (ie. the multi-display support is hidden in the video card
+ driver). On UNIX based system that used the X11 Windowing System,
+ the <span style="font-weight: bold;">-d</span> parameter will
+ override the screen specified by the $DISPLAY or <span
+ style="font-weight: bold;">-display</span> parameter.<br>
+ <span style="font-weight: bold;"></span><br>
+ <span style="font-weight: bold;">Note</span> that if VideoLUTs for a
+ display are not accessible (i.e. no hardware calibration
+ capability), <span style="font-weight: bold;">dispwin</span> will
+ will issue a warning or fail when it attempts to access them.<br>
+ <br>
+ On X11 the inability to access VideoLUTs could be because you are
+ trying to access a remote display, and the remote display doesn't
+ support the XF86VidMode extension, or perhaps you are running
+ multiple monitors using NVidia TwinView, or MergedFB, and trying to
+ access anything other than the primary monitor. TwinView and
+ MergedFB don't properly support the XF86VidMode extension for
+ multiple displays. You can use <a href="dispwin.html#r">dispwin -r</a>
+ to test whether the VideoLUTs are accessible for a particular
+ display. See also below, on how to select a different display for
+ VideoLUT access. Also note that dispcal will fail if the Visual
+ depth doesn't match the VideoLUT depth. Typically the VideoLUTs have
+ 256 entries per color component, so the Visual generally needs to be
+ 24 bits, 8 bits per color component.<br>
+ <br>
<a name="dnm"></a><span style="font-weight: bold;">-d n[,m]</span>Because of the @@ -471,242 +563,261 @@ the - difficulty cause by TwinView and MergedFB in X11 based systems, you - can optionally specify a separate display number after the display - that is going to be used to present test patches, for accessing the - VideoLUT hardware. This must be specified as a single string, e.g. <span - style="font-weight: bold;">-d 1,2</span> . Some experimentation - may be needed on such systems, to discover what screen has access to - the VideoLUT hardware, and which screens the test patches appear on. - You may be able to calibrate one screen, and then share the - calibration with another screen. Profiling can be done independently - to calibration.<br> - <br> - <a name="dweb"></a><span style="font-weight: bold;">-dweb</span> or - <span style="font-weight: bold;">-dweb:port</span> starts a - standalone web server on your machine, which then allows a local or - remote web browser to display the the color test patches. By default - port <span style="font-weight: bold;">8080</span> is used, but this - can be overridden by appending a <span style="font-weight: bold;">:</span> - and the port number i.e. <span style="font-weight: bold;">-dweb:8001</span>. - The URL will be <span style="font-weight: bold;">http://</span> - then name of the machine or its I.P. address followed by a colon and - the port number - e.g something like <span style="font-weight: - bold;">http://192.168.0.1:8080</span>. If you use the verbose - option (<span style="font-weight: bold;">-v</span>) then a likely - URL will be printed once the server is started, or you could run <span - style="font-weight: bold;">ipconfig</span> (MSWin) or <span - style="font-weight: bold;">/sbin/ifconfig</span> (Linux or OS X) - and identify an internet address for your machine that way. <b>JavaScript</b> - needs to be enabled in your web browser for this to work.<br> - <br> - Note that if you use this method of accessing a display, that there - is no access to the display Video Lookup tables, and that any - operation that depends on accessing the VideoLUTs will either - generate a warning or fail.<br> - <br> - <a name="dmadvr"></a><span style="font-weight: bold;">-dmadvr</span> - [MSWin only] causes test patches to be displayed using the MadVR - video renderer. Note that you may have to start the video playback - software and load a video clip in pause for this to work. MadVR - rendering does not need or support VideoLUT access, but be aware - that the state of the Graphics Card VideoLUTs may affect the results - (check this using dispwin). Test patch colors <u>will</u> be - processed by the MadVR 3dLut by default (see <a href="#n">-n</a> - flag).<br> - <br> - <a name="P"></a> The <span style="font-weight: bold;">-P</span> - parameter allows you to position and size the test patch window. By - default it is places in the center of the screen, and sized - appropriately for the type of instrument. The <span - style="font-weight: bold;">ho</span> and <span - style="font-weight: bold;">vo</span> values govern the horizontal - and vertical offset respectively. A value of 0.0 positions the - window to the far left or top of the screen, a value of 0.5 - positions it in the center of the screen (the default), and 1.0 - positions it to the far right or bottom of the screen. If three - parameters are provided, then the <span style="font-weight: bold;">ss</span> - parameter is a scale factor for the test window size. A value of 0.5 - for instance, would produce a half sized window. A value of 2.0 will - produce a double size window. If four parameters are provided, then - the last two set independent horizontal and vertical scaling - factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be - specified as a single string (no space between the numbers and the - comma). For example, to create a double sized test window at the top - right of the screen, use <span style="font-weight: bold;">-P 1,0,2</span> - . To create a window twice as wide as high: <span - style="font-weight: bold;">-P 1,0,2,1</span>.<br> - <br> - <a name="F"></a> The <span style="font-weight: bold;">-F</span> - flag causes the while screen behind the test window to be masked - with black. This can aid black accuracy when measuring CRT displays - or projectors.<br> - <br> - <a name="E"></a> The <span style="font-weight: bold;">-E</span> - flag causes the test values to be scaled to the Video RGB encoding - range of 16/255 to 235/255. Note that this is not applicable if the - MadVR render is being used to display patches, as MadVR should be - configured for Video encoding instead.<br> - <br> - By default <span style="font-weight: bold;">dispwin</span> will put - a test window on the selected display, and display some test colors, - before darkening then brightening the screen by loading video - LUT values, test the bell sounds, then restore the original values - and exit.<br> - <br> - If the <a name="i"></a><span style="font-weight: bold;">-i</span> - flag is set, then <span style="font-weight: bold;">dispwin</span> - will display the preset sequence, then random test colors forever.<br> - <br> - If the <a name="G"></a><span style="font-weight: bold;">-G</span> - parameter is set, then <span style="font-weight: bold;">dispwin</span> - will display the sequence of RGB color in the supplied CGATS file, - e.g. a .ti1 file. Typically this might the used with the <span - style="font-weight: bold;">-m</span> option to manually measure a - set of test patches.<br> - <br> - If the <a name="m"></a><span style="font-weight: bold;">-m</span> - flag is set, then <span style="font-weight: bold;">dispwin</span> - will display the preset sequence then exits, but advances manually - after each return key.<br> - <br> - If the <a name="r"></a><span style="font-weight: bold;">-r</span> - flag is set, then <span style="font-weight: bold;">dispwin</span> - will test just the loading of video LUT values by first darkening, - then lightening the screen, before exiting.<br> - <br> - If the <a name="n"></a><span style="font-weight: bold;">-n</span> - flag is set, then <span style="font-weight: bold;">dispwin</span> - will display the colors directly on the display, rather than having - the color values translated through the currently loaded Video LUTs. - In the case of using the MadVR renderer to display the patches, any - 3dLut will also be disabled.<br> - <br> - <a name="s"></a> If a <span style="font-weight: bold;">-s <span - style="font-style: italic;">filename.cal</span></span> option is - used, then rather than displaying a test window, <span - style="font-weight: bold;">dispwin</span> will save the currently - loaded calibration curves to the given calibration file. Note that - other functions such as clearing or loading a calibration can be - performed after this action.<br> - <br> - <a name="c"></a> If a <span style="font-weight: bold;">-c</span> - flag is used, then rather than displaying a test window, <span - style="font-weight: bold;">dispwin</span> will load the selected - display with a linear set of Video LUT curves, effectively clearing - the calibration, and will then exit. Note that other functions such - as loading a calibration can be performed after this action.<span - style="font-style: italic;"></span><br> - <br> - <a name="V"></a> If a <span style="font-weight: bold;">-V</span> - flag is used, then rather than loading the calibration specified as - the final argument, the currently loaded calibration will be - verified as being the same as the given calibration file. If this is - combined with the <span style="font-weight: bold;"><span - style="font-weight: bold;">-L</span></span> flag, the currently - loaded calibration will be verified as being the same as the - installed system profile for the display.<br> - <br> - <a name="I"></a><span style="font-weight: bold;">-I</span>: The ICC - profile specified as the final argument will be installed as the - default operating system profile for the chosen display, and the - display calibration will be set to the calibration tag ('vcgt' tag, - if any) in that profile.. On MSWindows and OS X this means that the - profile will be copied to the appropriate color profile directory - and registered with the operating system. For Linux X11 systems, the - profile will be installed using the <a href="ucmm.html">ucmm</a> - convention, and the X11 _ICC_PROFILE property in the root window, - and also the the XrandR 1.2 X11 _ICC_PROFILE output property on - systems that are running XrandR 1.2 or later. The latter is - following this <a - href="http://www.burtonini.com/computing/x-icc-profiles-spec-0.2.html">convention</a> - for allowing applications to locate the display profile for a - particular X11 display, and expands it to accomodate XrandR 1.2. - Note that for X11 systems, the properties are not persistent, and - will need to be loaded each time the X11 server is started (see the - <a href="#L">-L</a> flag). To make sure that the profile calbration - 'vcgt' tag gets loaded into the Graphics Card at system start, - please read the guide <a href="dispprofloc.html">here</a>.<br> - <br> - <a name="U"></a><span style="font-weight: bold;">-U</span>: The ICC - profile specified as the final argument will be un-installed as the - default operating system profile for the chosen display. The display - calibration will remain unchanged.<br> - <br> - <a name="S"></a><span style="font-weight: bold;">-S</span> d: Some - systems have more than one profile scope that an installed profile - will apply to, and this parameter allows overriding the default user - scope. On OS X, there is a choice of three scopes: <span - style="font-weight: bold;">n</span>: for network scope, if people - are sharing profiles over a network, <span style="font-weight: - bold;">l</span>: local system scope, which installs the profile - for all users of a system, and the default <span - style="font-weight: bold;">u</span>, which covers just the user - installing the profile. On Linux or Microsoft Vista, just the local - system <span style="font-weight: bold;">l</span> and user <span - style="font-weight: bold;">u</span> scope are available. Note that - you may need to run dispwin with elevated privileges(sudo) to be - able to successfully use network or local system scope. This option - also applies to uninstalling a profile. Note that to install a user - profile for the root account, you will have to login as root (sudo - will not achieve this).<br> - <br> - <a name="L"></a> <span style="font-weight: bold;">-L</span>: This - option fetches the current installed system profile for the chosen - display, and sets the display to the calibration tag ('vcgt' tag, if - any) in the profile. This is a convenient way of initializing the - display on system startup from the installed display profile, if the - system doesn't not do this automatically .<br> - <br> - <a name="X"></a> <span style="font-weight: bold;">-X</span>: Daemon - mode (experimental). When running on a UNIX based system that used - the X11 Windowing System, this option runs dispwin in a "daemon" - mode where it monitors the given X11 server, waiting for any changes - in monitors that may require loading a matching ICC profile (ie. - such as re-configuring, plugging in a different monitor etc.) - This only works if XRandR 1.2 is available on the server. By default - dispwin runs silently, and will not terminate. If the <span - style="font-weight: bold;">-v</span> option is given, it will emit - messages to stdout to show what it is doing. When it is first - invoked, it will load the installed profiles of all the screens of - the given X11 server.<br> - <br> - <a name="D"></a>The <b>-D</b> flag causes diagnostics to be printed - to stdout. A level can be set between 1 .. 9, that may give - progressively more verbose information. This can be useful in - tracking down why an operation fails.<br> - <br> - <a name="p1"></a> The final optional parameter on the command line - is the name of an ICC profile that contains a Video LUT <span - style="font-weight: bold;">vcgt</span> tag, or an Argyll <a - href="cal_format.html">.cal</a> format display calibration. If - this parameter is provided, then the selected display will be loaded - with the given calibration. If the <span style="font-weight: bold;">-V</span> - flag was given, then it is verified that this calibration is the - currently loaded one. This may be useful in initializing a - system to the current calibration on system startup, although a - better way may be to install the profile (<span style="font-weight: - bold;">-I</span> option), and then just use <span - style="font-weight: bold;">-L</span>. Note that the vcgt tag - interpretation within Argyll is consistent with that of the - originators of the tag. Other ICC profile vcgt implementations may - not be so consistent.<br> - <br> - <span style="font-weight: bold;">NOTE</span> that on an X11 system, - if the environment variable <span style="font-weight: bold;">ARGYLL_IGNORE_XRANDR1_2</span> - is set (ie. set it to "yes"), then the presence of the XRandR 1.2 - extension will be ignored, and other extensions such as Xinerama and - XF86VidMode extension will be used. This may be a way to work around - buggy XRandR 1.2 implementations.<br> - <span style="font-weight: bold;"><br> - NOTE</span> on MSWin systems that you will have to disable any - other calibration installer program if you want to be able to - control calibration using dispwin. Note also that there are other - programs that will interfere with calibration loading, such as - igfxpers.exe that gets installed with nVidia "Optimus" technology.<br> - <br> - <br> - <br> - <br> - </body> -</html> + + + +
+ difficulty cause by TwinView and MergedFB in X11 based systems, you
+ can optionally specify a separate display number after the display
+ that is going to be used to present test patches, for accessing the
+ VideoLUT hardware. This must be specified as a single string, e.g. <span
+ style="font-weight: bold;">-d 1,2</span> . Some experimentation
+ may be needed on such systems, to discover what screen has access to
+ the VideoLUT hardware, and which screens the test patches appear on.
+ You may be able to calibrate one screen, and then share the
+ calibration with another screen. Profiling can be done independently
+ to calibration.<br>
+ <br>
+ <a name="dweb"></a><span style="font-weight: bold;">-dweb</span> or
+ <span style="font-weight: bold;">-dweb:<i>port</i></span> starts a
+ standalone web server on your machine, which then allows a local or
+ remote web browser to display the the color test patches. By default
+ port <span style="font-weight: bold;">8080</span> is used, but this
+ can be overridden by appending a <span style="font-weight: bold;">:</span>
+ and the port number i.e. <span style="font-weight: bold;">-dweb:8001</span>.
+ The URL will be <span style="font-weight: bold;">http://</span>
+ then name of the machine or its I.P. address followed by a colon and
+ the port number - e.g something like <span style="font-weight:
+ bold;">http://192.168.0.1:8080</span>. If you use the verbose
+ option (<span style="font-weight: bold;">-v</span>) then a likely
+ URL will be printed once the server is started, or you could run <span
+ style="font-weight: bold;">ipconfig</span> (MSWin) or <span
+ style="font-weight: bold;">/sbin/ifconfig</span> (Linux or OS X)
+ and identify an internet address for your machine that way. <b>JavaScript</b>
+ needs to be enabled in your web browser for this to work. You may
+ have to modify any firewall to permit port 8080 to be accessed on
+ your machine.<br>
+ <br>
+ Note that if you use this method of accessing a display, that there
+ is no access to the display Video Lookup tables, and that any
+ operation that depends on accessing the VideoLUTs will either
+ generate a warning or fail.<br>
+ <br>
+ <a name="dmadvr"></a><span style="font-weight: bold;">-dmadvr</span>
+ [MSWin only] causes test patches to be displayed using the MadVR
+ video renderer. Note that you may have to start the video playback
+ software and load a video clip in pause for this to work. MadVR
+ rendering does not need or support VideoLUT access, but be aware
+ that the state of the Graphics Card VideoLUTs may affect the results
+ (check this using dispwin). Test patch colors <u>will</u> be
+ processed by the MadVR 3dLut by default (see <a href="#n">-n</a>
+ flag).<br>
+ <br>
+ <a name="dcc"></a><span style="font-weight: bold;">-dcc</span> or <b>-dcc:<i>no</i></b>
+ causes test patches to be displayed using and available <a
+ href="http://en.wikipedia.org/wiki/Chromecast">ChromeCast</a> to
+ your TV. Use <b>-dcc:?</b> to display a list of ChromeCasts on your
+ local network. Note that the ChromeCast as a test patch source is
+ probably the<b> least accurate</b> of your choices, since it
+ up-samples the test patch and transforms from RGB to YCC and back,
+ but should be accurate within ± 1 bit. You may have to modify any
+ firewall to permit port 8081 to be accessed on your machine if it
+ falls back to the Default receiver (see <a href="Installing.html">installation
+ instructions</a> for your platform).<br>
+ <br>
+ <a name="P"></a> The <span style="font-weight: bold;">-P</span>
+ parameter allows you to position and size the test patch window. By
+ default it is places in the center of the screen, and sized
+ appropriately for the type of instrument, or 10% of the width of the
+ display if the display size is unknown.. The <span
+ style="font-weight: bold;">ho</span> and <span
+ style="font-weight: bold;">vo</span> values govern the horizontal
+ and vertical offset respectively. A value of 0.0 positions the
+ window to the far left or top of the screen, a value of 0.5
+ positions it in the center of the screen (the default), and 1.0
+ positions it to the far right or bottom of the screen. If three
+ parameters are provided, then the <span style="font-weight: bold;">ss</span>
+ parameter is a scale factor for the test window size. A value of 0.5
+ for instance, would produce a half sized window. A value of 2.0 will
+ produce a double size window. If four parameters are provided, then
+ the last two set independent horizontal and vertical scaling
+ factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be
+ specified as a single string (no space between the numbers and the
+ comma). For example, to create a double sized test window at the top
+ right of the screen, use <span style="font-weight: bold;">-P 1,0,2</span>
+ . To create a window twice as wide as high: <span
+ style="font-weight: bold;">-P 1,0,2,1</span>.<br>
+ <br>
+ <a name="F"></a> The <span style="font-weight: bold;">-F</span>
+ flag causes the while screen behind the test window to be masked
+ with black. This can aid black accuracy when measuring CRT displays
+ or projectors.<br>
+ <br>
+ <a name="E"></a> The <span style="font-weight: bold;">-E</span>
+ flag causes the test values to be scaled to the Video RGB encoding
+ range of 16/255 to 235/255. Note that this is not applicable if the
+ MadVR render is being used to display patches, as MadVR should be
+ configured for Video encoding instead.<br>
+ <br>
+ By default <span style="font-weight: bold;">dispwin</span> will put
+ a test window on the selected display, and display some test colors,
+ before darkening then brightening the screen by loading video
+ LUT values, test the bell sounds, then restore the original values
+ and exit.<br>
+ <br>
+ If the <a name="i"></a><span style="font-weight: bold;">-i</span>
+ flag is set, then <span style="font-weight: bold;">dispwin</span>
+ will display the preset sequence, then random test colors forever.<br>
+ <br>
+ If the <a name="G"></a><span style="font-weight: bold;">-G</span>
+ parameter is set, then <span style="font-weight: bold;">dispwin</span>
+ will display the sequence of RGB color in the supplied CGATS file,
+ e.g. a .ti1 file. Typically this might the used with the <span
+ style="font-weight: bold;">-m</span> option to manually measure a
+ set of test patches.<br>
+ <br>
+ If the <a name="m"></a><span style="font-weight: bold;">-m</span>
+ flag is set, then <span style="font-weight: bold;">dispwin</span>
+ will display the preset sequence then exits, but advances manually
+ after each return key.<br>
+ <br>
+ If the <a name="r"></a><span style="font-weight: bold;">-r</span>
+ flag is set, then <span style="font-weight: bold;">dispwin</span>
+ will test just the loading of video LUT values by first darkening,
+ then lightening the screen, before exiting.<br>
+ <br>
+ If the <a name="n"></a><span style="font-weight: bold;">-n</span>
+ flag is set, then <span style="font-weight: bold;">dispwin</span>
+ will display the colors directly on the display, rather than having
+ the color values translated through the currently loaded Video LUTs.
+ In the case of using the MadVR renderer to display the patches, any
+ 3dLut will also be disabled.<br>
+ <br>
+ <a name="s"></a> If a <span style="font-weight: bold;">-s <span
+ style="font-style: italic;">filename.cal</span></span> option is
+ used, then rather than displaying a test window, <span
+ style="font-weight: bold;">dispwin</span> will save the currently
+ loaded calibration curves to the given calibration file. Note that
+ other functions such as clearing or loading a calibration can be
+ performed after this action.<br>
+ <br>
+ <a name="c"></a> If a <span style="font-weight: bold;">-c</span>
+ flag is used, then rather than displaying a test window, <span
+ style="font-weight: bold;">dispwin</span> will load the selected
+ display with a linear set of Video LUT curves, effectively clearing
+ the calibration, and will then exit. Note that other functions such
+ as loading a calibration can be performed after this action.<span
+ style="font-style: italic;"></span><br>
+ <br>
+ <a name="V"></a> If a <span style="font-weight: bold;">-V</span>
+ flag is used, then rather than loading the calibration specified as
+ the final argument, the currently loaded calibration will be
+ verified as being the same as the given calibration file. If this is
+ combined with the <span style="font-weight: bold;"><span
+ style="font-weight: bold;">-L</span></span> flag, the currently
+ loaded calibration will be verified as being the same as the
+ installed system profile for the display.<br>
+ <br>
+ <a name="I"></a><span style="font-weight: bold;">-I</span>: The ICC
+ profile specified as the final argument will be installed as the
+ default operating system profile for the chosen display, and the
+ display calibration will be set to the calibration tag ('vcgt' tag,
+ if any) in that profile.. On MSWindows and OS X this means that the
+ profile will be copied to the appropriate color profile directory
+ and registered with the operating system. For Linux X11 systems, the
+ profile will be installed using the <a href="ucmm.html">ucmm</a>
+ convention, and the X11 _ICC_PROFILE property in the root window,
+ and also the the XrandR 1.2 X11 _ICC_PROFILE output property on
+ systems that are running XrandR 1.2 or later. The latter is
+ following this <a
+ href="http://www.burtonini.com/computing/x-icc-profiles-spec-0.2.html">convention</a>
+ for allowing applications to locate the display profile for a
+ particular X11 display, and expands it to accomodate XrandR 1.2.
+ Note that for X11 systems, the properties are not persistent, and
+ will need to be loaded each time the X11 server is started (see the
+ <a href="#L">-L</a> flag). To make sure that the profile calbration
+ 'vcgt' tag gets loaded into the Graphics Card at system start,
+ please read the guide <a href="dispprofloc.html">here</a>.<br>
+ <br>
+ <a name="U"></a><span style="font-weight: bold;">-U</span>: The ICC
+ profile specified as the final argument will be un-installed as the
+ default operating system profile for the chosen display. The display
+ calibration will remain unchanged.<br>
+ <br>
+ <a name="S"></a><span style="font-weight: bold;">-S</span> d: Some
+ systems have more than one profile scope that an installed profile
+ will apply to, and this parameter allows overriding the default user
+ scope. On OS X, there is a choice of three scopes: <span
+ style="font-weight: bold;">n</span>: for network scope, if people
+ are sharing profiles over a network, <span style="font-weight:
+ bold;">l</span>: local system scope, which installs the profile
+ for all users of a system, and the default <span
+ style="font-weight: bold;">u</span>, which covers just the user
+ installing the profile. On Linux or Microsoft Vista, just the local
+ system <span style="font-weight: bold;">l</span> and user <span
+ style="font-weight: bold;">u</span> scope are available. Note that
+ you may need to run dispwin with elevated privileges(sudo) to be
+ able to successfully use network or local system scope. This option
+ also applies to uninstalling a profile. Note that to install a user
+ profile for the root account, you will have to login as root (sudo
+ will not achieve this).<br>
+ <br>
+ <a name="L"></a> <span style="font-weight: bold;">-L</span>: This
+ option fetches the current installed system profile for the chosen
+ display, and sets the display to the calibration tag ('vcgt' tag, if
+ any) in the profile. This is a convenient way of initializing the
+ display on system startup from the installed display profile, if the
+ system doesn't not do this automatically .<br>
+ <br>
+ <a name="X"></a> <span style="font-weight: bold;">-X</span>: Daemon
+ mode (experimental). When running on a UNIX based system that used
+ the X11 Windowing System, this option runs dispwin in a "daemon"
+ mode where it monitors the given X11 server, waiting for any changes
+ in monitors that may require loading a matching ICC profile (ie.
+ such as re-configuring, plugging in a different monitor etc.)
+ This only works if XRandR 1.2 is available on the server. By default
+ dispwin runs silently, and will not terminate. If the <span
+ style="font-weight: bold;">-v</span> option is given, it will emit
+ messages to stdout to show what it is doing. When it is first
+ invoked, it will load the installed profiles of all the screens of
+ the given X11 server.<br>
+ <br>
+ <a name="D"></a>The <b>-D</b> flag causes diagnostics to be printed
+ to stdout. A level can be set between 1 .. 9, that may give
+ progressively more verbose information. This can be useful in
+ tracking down why an operation fails.<br>
+ <br>
+ <a name="p1"></a> The final optional parameter on the command line
+ is the name of an ICC profile that contains a Video LUT <span
+ style="font-weight: bold;">vcgt</span> tag, or an Argyll <a
+ href="cal_format.html">.cal</a> format display calibration. If
+ this parameter is provided, then the selected display will be loaded
+ with the given calibration. If the <span style="font-weight: bold;">-V</span>
+ flag was given, then it is verified that this calibration is the
+ currently loaded one. This may be useful in initializing a
+ system to the current calibration on system startup, although a
+ better way may be to install the profile (<span style="font-weight:
+ bold;">-I</span> option), and then just use <span
+ style="font-weight: bold;">-L</span>. Note that the vcgt tag
+ interpretation within Argyll is consistent with that of the
+ originators of the tag. Other ICC profile vcgt implementations may
+ not be so consistent.<br>
+ <br>
+ <span style="font-weight: bold;">NOTE</span> that on an X11 system,
+ if the environment variable <span style="font-weight: bold;">ARGYLL_IGNORE_XRANDR1_2</span>
+ is set (ie. set it to "yes"), then the presence of the XRandR 1.2
+ extension will be ignored, and other extensions such as Xinerama and
+ XF86VidMode extension will be used. This may be a way to work around
+ buggy XRandR 1.2 implementations.<br>
+ <span style="font-weight: bold;"><br>
+ NOTE</span> on MSWin systems that you will have to disable any
+ other calibration installer program if you want to be able to
+ control calibration using dispwin. Note also that there are other
+ programs that will interfere with calibration loading, such as
+ igfxpers.exe that gets installed with nVidia "Optimus" technology.<br>
+ <br>
+ <br>
+ <br>
+ <br>
+ </body>
+</html>
diff --git a/doc/fakeread.html b/doc/fakeread.html index 2a7b5c0..376e971 100644 --- a/doc/fakeread.html +++ b/doc/fakeread.html @@ -3,7 +3,7 @@ <head> <title>fakeread</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> @@ -34,6 +34,9 @@ style="font-family: monospace;"></span><i style="font-family: monospace;">profile.</i><span style="font-family: monospace;">[icm|mpp|ti3] + + + </span><i style="font-family: monospace;">inoutfile</i></small><small><span style="font-family: monospace;"><br> -v @@ -44,24 +47,45 @@ Video encode device input to sepration as:<br> n + + + normal 0..1 full range RGB levels (default)<br> t + + + (16-235)/255 "TV" RGB levels<br> 6 + + + Rec601 YCbCr SD (16-235,240)/255 "TV" levels<br> 7 + + + Rec709 1125/60Hz YCbCr HD (16-235,240)/255 "TV" levels<br> 5 + + + Rec709 1250/50Hz YCbCr HD (16-235,240)/255 "TV" levels<br> 2 + + + Rec2020 YCbCr UHD (16-235,240)/255 "TV" levels<br> C + + + Rec2020 Constant Luminance YCbCr UHD (16-235,240)/255 "TV" levels<br> -p <i>separation.icm</i> Use device link separation @@ -69,7 +93,13 @@ -E flag Video decode separation device output. See -e above<br> - -k <i>file.cal</i> + -Z nbits </span></small><small><span + style="font-family: monospace;"><small><span style="font-family: + monospace;">Quantize test values to fit in nbits<br> + </span></small> -k <i>file.cal</i> + + + Apply calibration (include in .ti3 output)<br> -i <i>file.cal</i> Include calibration in .ti3 output, but don't apply it<br> @@ -82,32 +112,42 @@ -0 pow Apply power to device chanel 0-9<br> - -b <i>output.icm</i> Apply - BT.1886-like mapping with effective gamma 2.2<br> - -b g.g:<i>output.icm</i> Apply BT.1886-like mapping with - effective gamma g.g<br> - -B <i>output.icm</i> Apply - BT.1886 mapping with technical gamma 2.4<br> - -B g.g:<i>output.icm</i> Apply BT.1886 mapping with - technical gamma g.g<br> + -B + display.icm + Use BT.1886 source EOTF with technical gamma 2.4<br> + -b g.g:display.icm Use + BT.1886-like source EOTF with effective gamma g.g<br> + -b p.p:g.g:display.icm Use effective gamma g.g + source EOTF with p.p prop. output black point offset<br> + -g g.g:display.icm Use + effective gamma g.g source EOTF with all output black point + offset<br> -I intent r = relative colorimetric, a = absolute (default)<br> -A L,a,b Scale black point to target Lab value<br> -l + + + Output Lab rather than XYZ<br> -s + + + Lookup </span></small><small><span style="font-family: monospace;"><small><a style="font-family: monospace;" - href="File_Formats.html#MPP">MPP</a></small> - spectral values</span></small><br> + href="File_Formats.html#MPP">MPP</a></small> spectral values</span></small><br> <small><span style="font-family: monospace;"><small><span style="font-family: monospace;"> -R level Add average random deviation of <level>% to output PCS values<br> </span></small> -u + + + Make random deviations have uniform distributions rather than normal<br> -S @@ -130,6 +170,9 @@ + + + Base name for input[</span><a style="font-family: monospace;" href="File_Formats.html#.ti1">.ti1</a><span style="font-family: monospace;">]/output[</span><a @@ -179,12 +222,34 @@ <br> <a name="E"></a>The <b>-E</b> <i>flag</i> applies a Video decoding to the output of the separation.<small><small> </small></small>See - <a href="#e"><b>-e</b></a> for the list of decodings.<br> + + + + <a href="#e"><b>-e</b></a> for the list of decodings. Setting a + video encoding for output will also set quantization of 8 bits (see + -Z flag below). If your video connection is better than 8 bits (ie. + 10 or 12 bits), then you may wish to raise this default.<br> + <br> + <a name="Z"></a> <b>-Z nbits </b>Normally the target device values + are floating point numbers that may get rounded and quantized in the + process of printing them or reproducing them on the display device. + If some of this quantization can be accounted for, it may improve + the accuracy of the resulting profile, and the <span + style="font-weight: bold;">Q</span> parameter allows this + quantization to be specified. The parameter is the number of binary + digits (bits) that the device values should be quantized to. An idea + of the number of bits of precision that makes its way to your + display can be obtained by using <a + href="file:///D:/src/argyll/doc/dispcal.html#R">dispcal -R</a> If + Video encoding is selected (see -E flag above), then 8 bits is + selected by default. On systems using an VGA connection or Display + Port with a graphics card with VideoLUT entries with greater than 8 + bits depth, or if using the MadVR rendered with dithering, then a + higher bit depth is typically possible.<br> <br> <a name="k"></a>The <b>-k file.cal</b> parameter specifies a - calibration file created by <a - href="printcal.html">printcal</a> or <a - href="dispcal.html">dispcal</a>, and the supplied calibration + calibration file created by <a href="printcal.html">printcal</a> or + <a href="dispcal.html">dispcal</a>, and the supplied calibration curves will be applied to the chart device values after any separation and before the device profile. This allows emulating a system that uses per device channel calibration. The calibration @@ -193,26 +258,24 @@ computation of ink limits.<br> <br> <a name="i"></a> The <b>-i file.cal</b> parameter specifies a - printer calibration file created by <a - href="printcal.html">printcal</a> or <a - href="dispcal.html">dispcal</a>, and the - calibration curves will be included in the included in the resulting - .ti3 file, so that they can be passed through to the ICC profile, to - allow accurate computation of ink limits. The calibration <span + printer calibration file created by <a href="printcal.html">printcal</a> + or <a href="dispcal.html">dispcal</a>, and the calibration curves + will be included in the included in the resulting .ti3 file, so that + they can be passed through to the ICC profile, to allow accurate + computation of ink limits. The calibration <span style="font-weight: bold;">is not applied</span> to tchart values. <span style="font-weight: bold;">Note</span> that if the supplied ICC profile contains VCGT calibration curves, that these will be included in the resulting .ti3 by default.<br> <br> <a name="K"></a>The <b>-K</b> <b>file.cal</b> parameter specifies - a calibration file created by <a - href="printcal.html">printcal</a> or <a - href="dispcal.html">dispcal</a>, and the - inverse of the supplied calibration curves will be applied to the - chart device values after any separation and before the device - profile. This allows for undoing calibration curves that may be part - of a video calibration device link, so that the (calibrated device - value) device profile will work as expected.<br> + a calibration file created by <a href="printcal.html">printcal</a> + or <a href="dispcal.html">dispcal</a>, and the inverse of the + supplied calibration curves will be applied to the chart device + values after any separation and before the device profile. This + allows for undoing calibration curves that may be part of a video + calibration device link, so that the (calibrated device value) + device profile will work as expected.<br> <br> <a name="r"></a>The <span style="font-weight: bold;">-r</span> parameter is a way of simulating instability in the behaviour of the @@ -230,59 +293,18 @@ them to the power of the parameter. This applies a transfer curve to the simulated device response.<br> <br> - <a name="b"></a>The <b>-b output.icm</b> flag applies extra input - processing, applying <a - href="http://www.itu.int/rec/R-REC-BT.1886-0-201103-I">BT.1886</a>-like - - - - - - - - - - - - video gamma mapping using an effective gamma of 2.2 by default, and - overridable using <b>-b g.g:output.icm</b> where <b>g.g</b> is the - gamma. <b>output.icm</b> is the display ICC profile that provides - the black point that the BT.1886 curves will target. The gamma is an - effective gamma, meaning that its effect on 50% input is the same as - that of a pure power curve, in spite of any black offset added by - BT.1886. This has the benefit of making the overall effect of - brightness independent of the black level of the display. Setting an - effective gamma other than 2.2 is one way of making the viewing - condition adjustment for the different conditions of video encoding - and decoding, or for modelling the source colorspace as a rendering - on a video display. BT.1886 will only work with matrix type input - profiles. Typically this will be used to create a verification test + <b><a name="b"></a></b>The <b>-[b|B|g|G] [p.p:][g.g:]</b><b>display.icm</b> + series of options, substitutes an alternative EOTF (Electro-Optical + Transfer Function) for the one specified by the matrix input + profile. <b>display.icm</b> is the display ICC profile that + provides the black point that the gamma curve curves will target. + Typically these options will be used to create a verification test set for checking the operation of a device link or 3dLut created - using <a href="collink.html">collink</a>, using the same BT.1886 - parameters.<br> - <br> - <b><a name="B"></a></b>The <b>-B output.icm</b> flag applies extra - input processing, applying <a - href="http://www.itu.int/rec/R-REC-BT.1886-0-201103-I">BT.1886</a>-like - - - - - - - - - - - - video gamma mapping using a gamma of 2.4 by default, and overridable - using <b>-B g.g:output.icm</b> where <b>g.g</b> is the gamma. <b>output.icm</b> - is the display ICC profile that provides the black point that the - BT.1886 curves will target. The gamma is the technical gamma, or - power applied to the input image, and this means that its effect on - 50% input will depend on the black level of the display, making the - overall brightness somewhat unpredictable. For a more predictable - effect, use <b>-b</b>.<br> + using <a href="collink.html">collink</a>, using the same gamma + curve parameters. See <a href="collink.html#Ib">collink -I b</a> + for a full explanation of these parameters, and <a + href="Scenarios.html#TV2">Verifying Video Calibration</a> for more + detail.<br> <br> <a name="I"></a>The <span style="font-weight: bold;">-I</span> parameter allows changing the intent used in looking up the ICC diff --git a/doc/i1proHiRes.html b/doc/i1proHiRes.html index d6d8078..d6eef6a 100644 --- a/doc/i1proHiRes.html +++ b/doc/i1proHiRes.html @@ -3,7 +3,7 @@ <head> <title>The i1pro Hi Res. Mode</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta content="Graeme Gill" name="author"> </head> <body> @@ -42,6 +42,8 @@ + + width at half maximum</a>) of about 25nm. Doing a measurement at 3.3nm resolution reveals that the optical limit seems to be about 15nm, so there is some hope of improvement from that perspective.</p> @@ -56,7 +58,7 @@ which seems to have a diffraction grating/light sensor with a less smooth spectral efficiency curve than the Rev A - D models, the task of up-sampling the emissive calibration data with sufficient - accuracy is a more difficult.<br> + accuracy is more difficult.<br> </p> <h4 style="text-decoration: underline;">The verification experiment<br> </h4> @@ -77,6 +79,8 @@ href="http://www.jeti.com/cms/index.php/instruments-55/radiometer/specbos-1211"> + + specbos 1211</a> reference Tele-Spectro-Radiometer.<br> <br> 2) Using an i1pro2 in standard 10nm mode.<br> @@ -157,13 +161,17 @@ href="http://www.jeti.com/cms/index.php/instruments-55/radiometer/specbos-1211"> improve colorimetric measurement accuracy of display devices. Accuracy may conceivably be improved a little more than indicated by this experiment for i1pro rev A-D instruments which have a smoother - diffraction grating/light sensor characteristic, or it is also + diffraction grating/light sensor characteristic, but it is also conceivable that an unfortunate combination of display spectra and - the i1pro2 may result in reduced accuracy. The High Resolution mode - is primarily useful for showing more spectral detail, and should - probably not be used for colorimetric measurement when the highest - possible robustness and reliability is desired. The potential for - improved accuracy may be of benefit in other situations though. <br> + the i1pro2 may result in reduced accuracy. More extensive testing of + a range of instruments and illuminants would be needed to allay such + a concern. <br> + <br> + <b>In summary</b>: the High Resolution mode is unquestionably useful + for showing more spectral detail, and demonstrates promise of + improved accuracy, but should probably not be used used for + colorimetric measurement when the highest possible confidence is + desired.<br> <h4 style="text-decoration: underline;">Raw Data:</h4> The raw measurement data is available in this <a href="i1proHiRes.zip">.ti3 archive</a>.<br> diff --git a/doc/iccgamut.html b/doc/iccgamut.html index fe555cf..47df32c 100644 --- a/doc/iccgamut.html +++ b/doc/iccgamut.html @@ -3,18 +3,21 @@ <head> <title>iccgamut</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> <h2><b>xicc/iccgamut</b></h2> <br> - Create a gamut file or VRML file of the color gamut of an ICC + Create a gamut file or X3DOM file of the color gamut of an ICC profile.<br> <span style="font-weight: bold;"> iccgamut</span> allows creation of gamut files from the forward or backwards table of an ICC profile, in Lab or CIECAM02 Jab colorspace, and can also representing the - gamut as a VRML file.<br> + gamut as a X3DOM file.<br> + <br> + See <a href="file:///D:/src/argyll/doc/3Df.htmlormat">3D Viewing + Format</a> for switching to VRML or X3D output format.<br> <h3>Usage<br> </h3> <small><span style="font-family: monospace;">iccgamut [-options] </span><i @@ -24,6 +27,8 @@ + + Verbose</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -d sres Surface resolution @@ -31,23 +36,21 @@ <span style="font-family: monospace;"> -w emit - - - VRML .wrl file as well as CGATS .gam file</span><br + X3DOM .x3d.html file as well as CGATS .gam file</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -n Don't - add VRML axes or white/black point</span><br style="font-family: - monospace;"> - <span style="font-family: monospace;"> -k -Add + add X3DOM axes or white/black point</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> -k +Add - VRML markers for prim. & sec. "cusp" points</span><br + X3DOM markers for prim. & sec. "cusp" points</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -f function f = forward*, b = backwards</span><br @@ -61,6 +64,8 @@ s + + = saturation, a = absolute (default), d = profile default</span></small><small><span style="font-family: monospace;"></span></small><br style="font-family: monospace;"> @@ -74,6 +79,8 @@ r + + = reverse (priority: monochrome > matrix > lut)<br> </span></small><small><span style="font-family: monospace;"> </span><span style="font-family: monospace;">-p oride</span><span @@ -95,6 +102,8 @@ either + + an enumerated choice, or a series of parameters:value changes</span><br style="font-family: monospace;"> <span style="font-family: monospace;"></span></small><small><span @@ -106,12 +115,16 @@ either + + pe - Print evaluation environment (CIE 116-1995)<br> </span></small><small><span style="font-family: monospace;"> + + pc - Critical print evaluation environment (ISO-3664 P1)</span></small><small><span style="font-family: monospace;"></span><span style="font-family: monospace;"></span><br style="font-family: monospace;"> @@ -120,6 +133,8 @@ either + + mt - Monitor in typical work environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -127,6 +142,8 @@ either + + mb - Monitor in bright work environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -154,6 +171,8 @@ s:surround + + n = auto, a = average, m = dim, d = dark,</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -161,6 +180,8 @@ s:surround + + c = transparency (default average)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -168,6 +189,8 @@ w:X:Y:Z + + Adapted white point as XYZ (default media white)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -175,6 +198,8 @@ w:x:y + + Adapted white point as x, y</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -182,6 +207,8 @@ a:adaptation + + Adaptation luminance in cd.m^2 (default 50.0)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -190,6 +217,8 @@ Background + + % of image luminance (default 20)<br> l:imagewhite Image white in cd.m^2 if surround = auto (default 250)</span></small><br @@ -200,6 +229,8 @@ f:flare + + Flare light % of image luminance (default 0)<br> </span></small> </span><span style="font-family: monospace;"> @@ -208,11 +239,15 @@ f:flare <span style="font-family: monospace;"> + + g:X:Y:Z Glare color as XYZ (default media white)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> + + g:x:y Glare color as x, y<br> -s @@ -220,6 +255,8 @@ Create + + special cube surface topology plot<br style="font-family: monospace;"> </span><i style="font-family: monospace;">profile</i><span @@ -230,8 +267,9 @@ Create basename of the </span><a style="font-family: monospace;" href="File_Formats.html#.gam">gamut</a><span style="font-family: monospace;"> [.gam] and/or </span><a style="font-family: - monospace;" href="File_Formats.html#.wrl">VRML</a><span - style="font-family: monospace;"> [.wrl] file.</span></small> <br> + monospace;" href="File_Formats.html#X3DOM">X3DOM</a><span + style="font-family: monospace;"> [.x3d.html] file.</span></small> + <br> <h3>Comments</h3> The parameters are all those that control which table in the ICC profile to use, as well as what color space to convert it to. <br> @@ -246,11 +284,11 @@ Create and is a good place to start. Small values may take a lot of time to generate, and will produce big files.<br> <br> - The <b>-w</b> flag causes a VRML file to be produced, as well as a + The <b>-w</b> flag causes a X3DOM file to be produced, as well as a gamut file.<br> <br> The <b>-n</b> flag suppresses the L*a*b* axes being created in the - VRML.<br> + X3DOM.<br> <br> The <span style="font-weight: bold;">-k</span> flag adds markers for each of the primary and secondary "cusp" points (Red, Yellow, @@ -332,7 +370,7 @@ Create <br> and the resulting files will be <span style="text-decoration: underline;">profile.gam</span> and <span style="text-decoration: - underline;">profile.wrl</span>.<br> + underline;">profile.x3d.html</span>.<br> <br> To create a gamut suitable for CIECAM02 gamut mapping space in colprof or collink, something like<br> diff --git a/doc/iccgamutmapping.html b/doc/iccgamutmapping.html index d180372..8deab44 100644 --- a/doc/iccgamutmapping.html +++ b/doc/iccgamutmapping.html @@ -1,163 +1,210 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> -<head> - <title>About ICC profiles and Gamut Mapping</title> - <meta http-equiv="content-type" - content="text/html; charset=ISO-8859-1"> -</head> -<body> -<h2><u>About ICC profiles and Gamut Mapping</u></h2> -<h3>How ICC profiles support different intents</h3> -cLUT (Color Lookup Table) based ICC profiles support multiple <span - style="font-weight: bold;">intents</span> by having a table for each -intent. In a typical device cLUT profile, there are up to 6 cLUT's, -three for input (AtoB tables, that convert from device space to PCS -(Profile connection space)), and three for output (BtoA tables, that -convert from PCS to device space). The tables allow the use of -different color transforms, each transform being tailored for a -different effect:<br> -<br> -AtoB0, BtoA0: Perceptual<br> -AtoB1, BtoA1: Colorimetric<br> -AtoB2, BtoA2: Saturation<br> -<br> -The colorimetric intent is meant to convey the exact device color -behaviour, without any gamut mapping. Typically it is used to store the -devices behaviour (characterization), and is also used where exact -color reproduction is required, such as for proofing. The Colorimetric -tables double up for both relative colorimetric and -absolute colorimetric with the application of a white point restoration.<br> -<br> -The Perceptual and Saturation tables are meant to contain gamut mapping -combined with the device characterization. The allowance for this in -both the AtoB direction, as well as the BtoA direction permits a -profile to gamut map from the device gamut to some intermediate gamut, -and then from the intermediate gamut to the device gamut.<br> -<br> -[Note that Shaper/Matrix profiles are always Colorimetric intent, since -there is only a single transformation, and it does not have the -necessary flexibility to accommodate gamut mapping.]<br> -<h3>ICC Version 2 behaviour<br> -</h3> -Apart from defining the general purpose of the different tables, the -ICC Version 2 specification doesn't specify exactly how they are to -achieve this, so it is up to the profile maker to make a choice in this -regard. There is no common gamut boundary specified for the PCS, and -such an approach limits the achievable intents in any case (see ICC -Version 4 behaviour for an explanation why).<br> -<br> -What I've chosen to do with Argyll profiles, is to make all the AtoB -tables the same as colorimetric. This means that the conversion used -for the source profile is always colorimetric, and also means that the -source gamut seen by the destination profile is the source colorspace -gamut. This means that the gamut mapping is done solely in the BtoA -tables, -and that their task is to map the source colorspace gamut to the -destination colorspace gamut. So to construct the perceptual and -saturation intent mapping tables, a source profile or source gamut -needs to be specified, so that a gamut mapping can be constructed.<br> -<br> -The advantages of this approach is that the behaviour is precisely -defined, a full range of gamut mapping options is available, and -compatibility with matrix profiles (which do not have gamut mapping -transforms) and other foreign profiles can be assured, by simply using -such profiles as colorimetric sources. The main disadvantage is that -the gamut mapping will only operate exactly as intended when the -profile is linked with the source profile it was setup for. This is -really a fundamental limitation of the idea of having pre-computed -gamut mapping color transforms, that the ICC profile format was -intended to support.<br> -<br> -Some non-Argyll profile have gamut mapping transforms in their -Perceptual and Saturation A2B tables, and this means that the apparent -gamut of a source through these tables may be different to the actual -device gamut. To accommodate using these profiles with CMM's (Color -Management Modules) that do not permit the separate choice of intent -tables for the source and destination profiles, Argyll will by default -use the gamut defined by the source profile perceptual table to -create the gamut mapping of the destination perceptual table, and the -source saturation table to make the destination saturation table. Note -that this can affect the exact nature of the gamut mapping, the -distortion of the source gamut changing the apparent relationship -between it and the destination gamut - see "ICC Version 4 behavior" for -an illustration of the kind of changes this causes. [This default can -be overridden though using the colprof -nP and -nS flags.]<br> -<h3>ICC Version 4 behaviour</h3> -(Note that Argyll does not currently support ICC V4)<br> -<br> -By default, ICC Version 4 profile operate exactly the same as the ICC -V2 profile in regard to gamut mapping. A slight adjustment was made to -the permitted tag contents, to allow things like Display profiles to -contain the full range of AtoB and BtoA tables, so that they could also -be gamut mapped. But an optional part of ICCV4, is to use the <span - style="font-weight: bold;">Profile Reference Medium Gamut</span> -(PRMG) as an -intermediate gamut boundary between the source colorspace, and the -destination colorspace. If this option is used, then an additional tag -in the ICCV4 profile indicates that this is the case. This then solves -the problem of the gamut mapping having to know the source and -destination gamuts to operate. Instead, the gamut mapping is split into -two parts, the first where the source gamut to RMG is done by the AtoB -tables, and then the RMG to destination gamut is done by the BtoA -tables. Profiles can therefore be mix and matches, while retaining true -gamut mapping.<br> -<br> -This approach has a number of drawbacks though. One is that the colors -get gamut mapped twice. Gamut mapping is sometimes not very precise, -and the geometry of the transforms may not cancel out, especially since -different profile vendors may choose different algorithms in their -gamut mapping. By "cancel out", I mean that even if you were linking -the same source colorspace to the same destination colorspace, the -gamut may be expanded (say) in the process of mapping to the PRMG, and -then compressed again in mapping from the RMG to the device space, and -these expansions and compressions may not quite match. Given that the -PRMG is a relatively large gamut, larger than many real devices actual -behavior, this sort of expansion and re-compression will be the normal -thing.<br> -<br> -The chief drawback, is that only one (non colorimetric) intent can -really be supported, that of saturation. <br> -<br> -The typically expected behaviour of perceptual intent gamut mapping, is -to -compress any areas of the source gamut that lie outside the destination -gamut, but for areas that fall within the destination gamut, change -them as little as possible, consistent with keeping smooth and -proportional with respect to the compressed colors. This preserves the -source "look" as much as -possible, while ensuring that out of gamut colors are smoothly brought -within the destination gamut.<br> -<br> -Typical behavior of a saturation intent, is (at least), to not only -compress out of gamut source colors to fit within the destination, but -to expand any source boundary that falls within the destination gamut -outwards match the destination gamut. Some practical saturation gamut -mappings may go further than this, and expand a little beyond the -destination gamut to ensure fully saturated boundary colors, and also -enhance the saturation of all colors mapped through it.<br> -<br> - By mapping the source gamut to -the RMG in the A2B, all information about what areas of the source -gamut are -inside or outside of the destination gamut are lost, so the destination -gamut mapping can not known which colors may be left unchanged, and -which really need compressing. All it can do is map the RMG to match -the destination gamut, -thereby effecting a saturation style intent. <br> -<br> -Once again, this is a fundamental limitation of using pre-computed -gamut mappings. The only effective way of overcoming such limitations -is to move to a more active color management architecture, in which -gamut mappings are computed at link time, to accommodate the actual -source and destination gamuts.<br> -<br> -<br> -<img alt="Illustration of perceptual and saturation gamut mapping." - src="gamutmapping1.jpg" style="width: 665px; height: 215px;"><br> -<br> -<br> -<br> -<br> -<br> -</body> + <head> + <title>About ICC profiles and Gamut Mapping</title> + <meta http-equiv="content-type" content="text/html; + charset=windows-1252"> + </head> + <body> + <h2><u>About ICC profiles and Gamut Mapping</u></h2> + <h3>How ICC profiles support different intents</h3> + cLUT (Color Lookup Table) based ICC profiles support multiple <span + style="font-weight: bold;">intents</span> by having a table for + each + intent. In a typical device cLUT profile, there are up to 6 cLUT's, + three for input (AtoB tables, that convert from device space to PCS + (Profile connection space)), and three for output (BtoA tables, that + convert from PCS to device space). The tables allow the use of + different color transforms, each transform being tailored for a + different effect:<br> + <br> + AtoB0, BtoA0: Perceptual<br> + AtoB1, BtoA1: Colorimetric<br> + AtoB2, BtoA2: Saturation<br> + <br> + The colorimetric intent is meant to convey the exact device color + behaviour, without any gamut mapping. Typically it is used to store + the + devices behaviour (characterization), and is also used where exact + color reproduction is required, such as for proofing. The + Colorimetric + tables double up for both relative colorimetric and + absolute colorimetric with the application of a white point + restoration.<br> + <br> + The Perceptual and Saturation tables are meant to contain gamut + mapping + combined with the device characterization. The allowance for this in + both the AtoB direction, as well as the BtoA direction permits a + profile to gamut map from the device gamut to some intermediate + gamut, + and then from the intermediate gamut to the device gamut.<br> + <br> + [Note that Shaper/Matrix profiles are always Colorimetric intent, + since + there is only a single transformation, and it does not have the + necessary flexibility to accommodate gamut mapping.]<br> + <h3>ICC Version 2 behaviour<br> + </h3> + Apart from defining the general purpose of the different tables, the + ICC Version 2 specification doesn't specify exactly how they are to + achieve this, so it is up to the profile maker to make a choice in + this + regard. There is no common gamut boundary specified for the PCS, and + such an approach limits the achievable intents in any case (see ICC + Version 4 behaviour for an explanation why).<br> + <br> + What I've chosen to do with Argyll profiles, is to make all the AtoB + tables the same as colorimetric. This means that the conversion used + for the source profile is always colorimetric, and also means that + the + source gamut seen by the destination profile is the source + colorspace + gamut. This means that the gamut mapping is done solely in the BtoA + tables, + and that their task is to map the source colorspace gamut to the + destination colorspace gamut. So to construct the perceptual and + saturation intent mapping tables, a source profile or source gamut + needs to be specified, so that a gamut mapping can be constructed.<br> + <br> + The advantages of this approach is that the behaviour is precisely + defined, a full range of gamut mapping options is available, and + compatibility with matrix profiles (which do not have gamut mapping + transforms) and other foreign profiles can be assured, by simply + using + such profiles as colorimetric sources. The main disadvantage is that + the gamut mapping will only operate exactly as intended when the + profile is linked with the source profile it was setup for. This is + really a fundamental limitation of the idea of having pre-computed + gamut mapping color transforms, that the ICC profile format was + intended to support.<br> + <br> + Some non-Argyll profile have gamut mapping transforms in their + Perceptual and Saturation A2B tables, and this means that the + apparent + gamut of a source through these tables may be different to the + actual + device gamut. To accommodate using these profiles with CMM's (Color + Management Modules) that do not permit the separate choice of intent + tables for the source and destination profiles, Argyll will by + default + use the gamut defined by the source profile perceptual table to + create the gamut mapping of the destination perceptual table, and + the + source saturation table to make the destination saturation table. + Note + that this can affect the exact nature of the gamut mapping, the + distortion of the source gamut changing the apparent relationship + between it and the destination gamut - see "ICC Version 4 behavior" + for + an illustration of the kind of changes this causes. [This default + can + be overridden though using the colprof -nP and -nS flags.]<br> + <h3>ICC Version 4 behaviour</h3> + (Note that Argyll does not currently support ICC V4)<br> + <br> + By default, ICC Version 4 profile operates similarly to the ICC + V2 profile in regard to gamut mapping, with the exception that a + minimally specified reference medium and reference viewing + conditions are introduced for perceptual (and presumably saturation) + tables, allowing at least the luminance range to have a well defined + behavior when mixing and matching the perceptual A2B and B2A tables + of different profiles. A slight adjustment was made to + the permitted tag contents, to allow things like Display profiles to + contain the full range of AtoB and BtoA tables, so that they could + also + be gamut mapped. An optional part of ICCV4, introduces a more + comprehensively specified <span style="font-weight: bold;">Profile + Reference Medium Gamut</span> + (PRMG) as an + intermediate gamut boundary between the source colorspace, and the + destination colorspace. If this option is used, then an additional + tag + in the ICCV4 profile indicates that this is the case. This then + solves + the problem of the gamut mapping having to know the source and + destination gamuts to operate. Instead, the gamut mapping is split + into + two parts, the first where the source gamut to RMG is done by the + AtoB + tables, and then the RMG to destination gamut is done by the BtoA + tables. Profiles can therefore be mix and matches, while retaining + true + gamut mapping.<br> + <br> + This approach has a number of drawbacks though. One is that the + colors + get gamut mapped twice. Gamut mapping is sometimes not very precise, + and the geometry of the transforms may not cancel out, especially + since + different profile vendors may choose different algorithms in their + gamut mapping. By "cancel out", I mean that even if you were linking + the same source colorspace to the same destination colorspace, the + gamut may be expanded (say) in the process of mapping to the PRMG, + and + then compressed again in mapping from the RMG to the device space, + and + these expansions and compressions may not quite match. Given that + the + PRMG is a relatively large gamut, larger than many real devices + actual + behavior, this sort of expansion and re-compression will be the + normal + thing.<br> + <br> + The chief drawback, is that only one (non colorimetric) intent can + really be supported, that of saturation. <br> + <br> + The typically expected behavior of perceptual intent gamut mapping, + is + to + compress any areas of the source gamut that lie outside the + destination + gamut, but for areas that fall within the destination gamut, change + them as little as possible, consistent with keeping smooth and + proportional with respect to the compressed colors. This preserves + the + source "look" as much as + possible, while ensuring that out of gamut colors are smoothly + brought + within the destination gamut.<br> + <br> + Typical behavior of a saturation intent, is (at least), to not only + compress out of gamut source colors to fit within the destination, + but + to expand any source boundary that falls within the destination + gamut + outwards match the destination gamut. Some practical saturation + gamut + mappings may go further than this, and expand a little beyond the + destination gamut to ensure fully saturated boundary colors, and + also + enhance the saturation of all colors mapped through it.<br> + <br> + By mapping the source gamut to + the RMG in the A2B, all information about what areas of the source + gamut are + inside or outside of the destination gamut are lost, so the + destination + gamut mapping can not known which colors may be left unchanged, and + which really need compressing. All it can do is map the RMG to match + the destination gamut, + thereby effecting a saturation style intent. <br> + <br> + Once again, this is a fundamental limitation of using pre-computed + gamut mappings. The only effective way of overcoming such + limitations + is to move to a more active color management architecture, in which + gamut mappings are computed at link time, to accommodate the actual + source and destination gamuts.<br> + <br> + <br> + <img alt="Illustration of perceptual and saturation gamut mapping." + src="gamutmapping1.jpg" style="width: 665px; height: 215px;"><br> + <br> + <br> + <br> + <br> + <br> + </body> </html> diff --git a/doc/illumread.html b/doc/illumread.html index 0dcf5bd..9b65b2f 100644 --- a/doc/illumread.html +++ b/doc/illumread.html @@ -1,271 +1,309 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<html> - <head> - <title>illumread</title> - <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> - <meta name="author" content="Graeme Gill"> - </head> - <body> - <h2><b>spectro/illumread</b></h2> - <h3>Summary</h3> - Use an instrument or instruments to measure an illuminant spectrum, - including estimate its Ultra Violet content. A combination of direct - illumination readings and readings from a piece of paper having some - FWA content are used for this. (If the UV content is not needed, or - a suitable instrument is not available, then <a - href="spotread.html">spotread</a> should be used instead.)<br> - <h3>Usage Summary</h3> - <small><span style="font-family: monospace;">illumread [-options] - illuminant.sp</span><br style="font-family: monospace;"> - <span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#v">-v</a><span +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+ <head>
+ <title>illumread</title>
+ <meta http-equiv="content-type" content="text/html;
+ charset=windows-1252">
+ <meta name="author" content="Graeme Gill">
+ </head>
+ <body>
+ <h2><b>spectro/illumread</b></h2>
+ <h3>Summary</h3>
+ Use an instrument or instruments to measure an illuminant spectrum,
+ including estimate its Ultra Violet content. A combination of direct
+ illumination readings and readings from a piece of paper having some
+ FWA content are used for this. (If the UV content is not needed, or
+ a suitable instrument is not available, then <a
+ href="spotread.html">spotread</a> should be used instead.)<br>
+ <h3>Usage Summary</h3>
+ <small><span style="font-family: monospace;">illumread [-options]
+ illuminant.sp</span><br style="font-family: monospace;">
+ <span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#v">-v</a><span
style="font-family: monospace;"> - Verbose mode</span><span style="font-family: - monospace;"></span></small><small><span style="font-family: - monospace;"></span></small><br style="font-family: monospace;"> - <small><span style="font-family: monospace;"></span><span - style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#S">-S</a><span - style="font-family: monospace;"> - - Plot the readings in a graph window.</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#c">-c comport</a><span + + +
+ Verbose mode</span><span style="font-family:
+ monospace;"></span></small><small><span style="font-family:
+ monospace;"></span></small><br style="font-family: monospace;">
+ <small><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#S">-S</a><span
+ style="font-family: monospace;">
+
+ Plot the readings in a graph window.</span><br
+ style="font-family: monospace;">
+ <span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#c">-c comport</a><span
style="font-family: monospace;"> Set - COM port, 1..4 (default 1)</span><span style="font-family: - monospace;"></span><span style="font-family: monospace;"></span><span - style="font-family: monospace;"></span></small><small><span - style="font-family: monospace;"></span></small><font size="-1"><span - style="font-family: monospace;"></span></font><font size="-1"><span - style="font-family: monospace;"><br> - </span></font><font size="-1"><span style="font-family: + + +
+ COM port, 1..4 (default 1)</span><span style="font-family:
+ monospace;"></span><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"></span></small><small><span
+ style="font-family: monospace;"></span></small><font size="-1"><span
+ style="font-family: monospace;"></span></font><font size="-1"><span
+ style="font-family: monospace;"><br>
+ </span></font><font size="-1"><span style="font-family:
monospace;"> <a href="#N">-N</a> Disable - initial calibration of instrument</span></font> if possible<br> - <font size="-1"><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#H">-H</a><span - style="font-family: monospace;"> - - Use high resolution spectrum mode - (if available)<br> + + +
+ initial calibration of instrument</span></font> if possible<br>
+ <font size="-1"><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#H">-H</a><span
+ style="font-family: monospace;">
+
+ Use high resolution spectrum mode
+ (if available)<br>
<font size="-1"> <a href="#Yr">-Y r</a> - Set refresh measurement mode</font><br> - </span></font><font size="-1"><span style="font-family: + + +
+ Set refresh measurement mode</font><br>
+ </span></font><font size="-1"><span style="font-family:
monospace;"> <a href="#W">-W n|h|x</a> Override - serial port flow control: n = none, h = HW, x = Xon/Xoff</span></font><br> - <small><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#D">-D [level]</a><span - style="font-family: monospace;"> - - Print debug diagnostics to stderr</span></small><br> - <font size="-1"><span style="font-family: monospace;"><a + + +
+ serial port flow control: n = none, h = HW, x = Xon/Xoff</span></font><br>
+ <small><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#T">-T</a><span
+ style="font-family: monospace;">
+ + +
+ Test mode - restore & save measurements to<br>
+ +
+ *_i.sp, *_r.sp, *_p.sp, *_mpir.sp, *_cpir.sp files<br>
+ </span></small> <small><span style="font-family: monospace;"> </span><a
+ style="font-family: monospace;" href="#D">-D [level]</a><span
+ style="font-family: monospace;">
+
+ Print debug diagnostics to stderr</span></small><br>
+ <font size="-1"><span style="font-family: monospace;"><a
href="#file"><span style="font-style: italic;">illuminant.sp</span></a> File - to save measurement to<br style="font-family: monospace;"> - </span></font><small><span style="font-family: monospace;"></span><span - style="font-family: monospace;"></span></small><br> - <h3>Usage Details and Discussion</h3> - <b>illumread</b> uses a suitable instrument to read an illuminant - spectrum, and uses an indirect method to estimate the Ultra Violet - content of the illuminant, so as to provide better accuracy with <a - href="FWA.html">FWA compensation</a>. An instrument or combination - of instruments capable of spectral measurement of both emissive - measurement and reflective measurement without a U.V. filter is - required for this.<br> - <br> - <a name="v"></a>The <b>-v</b> flag causes extra information to be - printed out during chartread operation.<br> - <br> - <a name="S"></a>The <b>-S</b> flag enables the plotting of the - spectral reflectance/transmittance values. You must select the plot - window and strike a key in it to continue with another measurement.<br> - <br> - <a name="c"></a> The instrument is assumed to communicate through a - USB or serial communication port, and the initial port can be - selected with the <b>-c</b> option, if the instrument is not - connected to the first port. If you invoke <span - style="font-weight: bold;">illumread</span> so as to display the - usage information (i.e. "illumread -?" or "illumread --"), then the - discovered USB and serial ports will be listed. On UNIX/Linux, a - list of all possible serial ports are shown, but not all of them may - actually be present on your system.<br> - <br> - <a name="N"></a><span style="font-weight: bold;">-N</span> Any - instrument that requires regular calibration will ask for - calibration on initial start-up. Sometimes this can be awkward if - the instrument is being mounted in some sort of measuring jig, or - annoying if several sets of readings are being taken in quick - succession. The -<span style="font-weight: bold;">N</span> - suppresses this initial calibration if a valid and not timed out - previous calibration is recorded in the instrument or on the host - computer. It is advisable to only use this option on the second and - subsequent measurements in a single session.<br> - <br> - <a name="H"></a> The -<span style="font-weight: bold;">H</span> - option turns on high resolution spectral mode, if the instrument - supports it. See <a href="instruments.html">Operation of particular - instruments</a> for more details.<br> - <br> - <a name="Yr"></a> The -<span style="font-weight: bold;">Y r</span> - option turns on refresh mode measurement, if the instrument supports - it. This may improve the repeatability of measurements of - illuminants that have a repetitive flicker.<br> - <br> - <a name="W"></a>The <b>-W</b> <span style="font-weight: bold;">n|h|x</span> - parameter overrides the default serial communications flow control - setting. The value <span style="font-weight: bold;">n</span> turns - all flow control off, <span style="font-weight: bold;">h</span> - sets hardware handshaking, and <span style="font-weight: bold;">x</span> - sets Xon/Xoff handshaking. This commend may be useful in workaround - serial communications issues with some systems and cables. <br> - <br> - <a name="D"></a>The <b>-D</b> flag causes communications and other - instrument diagnostics to be printed to stdout. A level can be set - between 1 .. 9, that may give progressively more verbose - information, depending on the instrument. This can be useful in - tracking down why an instrument can't connect.<br> - <br> - <a name="file"></a>The <span style="font-weight: bold; font-style: - italic;">illuminant.sp</span> is the name of the file to save the - resulting illuminant spectrum to. The format used is <a - href="File_Formats.html#.sp">.sp</a>.<br> - <br> - <hr style="width: 100%; height: 2px;"><br> - Unlike the other measurement utilities, <span style="font-weight: - bold;">illumread</span> doesn't connect to the instrument until it - is about to make a measurement. This allows for the possibility of - using a different instrument for each measurement.<br> - <br> - It will display a menu:<br> - <br> - Press 1 .. 6<br> - 1) Measure direct illuminant<br> - 2) Measure illuminant reflected from paper<br> - 3) Measure paper<br> - 4) Select another instrument, Currently 1 'usb:/bus4/dev2/ - (GretagMacbeth i1 Pro)'<br> - 5) Compute illuminant spectrum, average result with 0 previous - readings & save it<br> - 6) Compute illuminant spectrum from this reading & save result<br> - 7) Exit<br> - <br> - There are three measurements to be made, after which the illuminant - can be computed and saved. Before each measurement, the instrument - may need calibrating.<br> - <br> - The first measurement needs a spectral instrument capable of reading - in an ambient or emissive mode. For instance, a Spectrolino, Eye-One - Pro or ColorMunki would be suitable instruments.<br> - <br> - The second measurement needs a spectral instrument capable of - reading in an projector or emissive mode. For instance, a - Spectrolino, Eye-One Pro or ColorMunki would be suitable - instruments.<br> - <br> - The third measurement needs a spectral instrument capable of reading - in reflective mode with UV included. For instance, a Spectrolino, - Eye-One Pro, DTP20, DTP22 or DTP41 would be suitable - instruments, as long as they are not fitted with UV filters.<br> - <br> - To be able to estimate the level of Ultra Violet (UV) light in the - illuminant, a reasonable sized piece of white paper needs to be - used. The paper should have some noticeable level of FWA - (Fluorescent Whitener Additive, or Optical Brightening Agents) in - it, so that it responds to UV light. A piece of cheap copier paper - is ideal, since cheap paper is typically whitened with large amounts - of FWA. If the paper is thin (less than 160 gsm) then two or three - sheets should be used to prevent any background showing through. [If - the intention is to use the illuminant spectrum for proofing to a - particular paper, then an alternative might be to use a piece of the - intended paper for this purpose. It's unclear which may give a - better result.]<br> - <br> - The first measurement <span style="font-weight: bold;">1)</span>, - is to use either the ambient or emissive measurement mode to measure - the illumination directly.<br> - <br> - <div style="margin-left: 40px;">If the instrument supports an - ambient measurement capability, then it will be used. If the - insrument does not have an ambient mode, then an emissive - measurement mode can be used, although typically many illuminants - are too bright to directly point the instrument at. A work-around - is to reflect the illuminant from a spectrally flat white surface. - A good candidate for this is a piece of white, fine textured - polystyrene foam. [The suitability of a reflector can be checked - using <span style="font-weight: bold;">spotread -S</span> to - check that the reflection characteristic is close to flat.]<br> - <br> - <img style="width: 228px; height: 300px;" alt="Measuring Ambient" - src="illumread_1.jpg"><img style="width: 141px; height: 282px;" - alt="Measuring Ambient" src="illumread_2.jpg"> <img - style="width: 226px; height: 282px;" alt="Measuring Ambient" - src="illumread_3.jpg"><br> - </div> - <br> - The second measurement <span style="font-weight: bold;">2)</span>, - is to measure the illuminant after it has reflected from the paper.<br> - <br> - <div style="margin-left: 40px;">This is done by placing the paper - such that it is uniformly illuminated with reasonable brightness, - and then placing the instrument so that it receives the reflected - light from the paper. This is typically achieved by placing the - instrument close to the paper at about 45º, so that it's - aperture has a clear view of the illuminated paper, but avoiding - shadowing the region that is in view. <br> - <br> - <img style="width: 219px; height: 261px;" alt="Measuring via - Paper" src="illumread_5.jpg"><img style="width: 252px; height: - 259px;" alt="Measuring via Paper" src="illumread_4.jpg"><br> - </div> - <br> - The third measurement <span style="font-weight: bold;">3)</span>, - is to measure the paper directly using the instrument reflective - mode measurement.<br> - <div style="margin-left: 40px;"><img style="width: 186px; height: - 162px;" alt="Measuring Paper" src="illumread_6.jpg"><br> - </div> - If a different instrument is needed, use <span style="font-weight: - bold;">4)</span> to select from the available instruments attached - to your computer.<br> - <br> - Once these three measurements have been made, then the illuminant - readings spectrum can be computed and save using <span - style="font-weight: bold;">6)</span>, or a series of readings can - be made with each reading being averages with the previous readings - before saving it by using <span style="font-weight: bold;">5)</span>. - Note that the averaged readings will be weighted by their absolute - intensities, and that while the direct and indirect illumination - needs measuring for each reading, the same paper measurement can be - used each time.<br> - <br> - If plotting is enabled, a plot of the measured (black) and with - estimated UV (red) is plotted. This is followed by a plot showing - measured paper reflectance (black) and the FWA calculated paper - reflectance (red).<br> - <br> - <br> - Illumread can then be terminated using <span style="font-weight: - bold;">7)</span>.<br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - </body> -</html> + + +
+ to save measurement to<br style="font-family: monospace;">
+ </span></font><small><span style="font-family: monospace;"></span><span
+ style="font-family: monospace;"></span></small><br>
+ <h3>Usage Details and Discussion</h3>
+ <b>illumread</b> uses a suitable instrument to read an illuminant
+ spectrum, and uses an indirect method to estimate the Ultra Violet
+ content of the illuminant, so as to provide better accuracy with <a
+ href="FWA.html">FWA compensation</a>. An instrument or combination
+ of instruments capable of spectral measurement of both emissive
+ measurement and reflective measurement without a U.V. filter is
+ required for this.<br>
+ <br>
+ <a name="v"></a>The <b>-v</b> flag causes extra information to be
+ printed out during chartread operation.<br>
+ <br>
+ <a name="S"></a>The <b>-S</b> flag enables the plotting of the
+ spectral reflectance/transmittance values. You must select the plot
+ window and strike a key in it to continue with another measurement.<br>
+ <br>
+ <a name="c"></a> The instrument is assumed to communicate through a
+ USB or serial communication port, and the initial port can be
+ selected with the <b>-c</b> option, if the instrument is not
+ connected to the first port. If you invoke <span
+ style="font-weight: bold;">illumread</span> so as to display the
+ usage information (i.e. "illumread -?" or "illumread --"), then the
+ discovered USB and serial ports will be listed. On UNIX/Linux, a
+ list of all possible serial ports are shown, but not all of them may
+ actually be present on your system.<br>
+ <br>
+ <a name="N"></a><span style="font-weight: bold;">-N</span> Any
+ instrument that requires regular calibration will ask for
+ calibration on initial start-up. Sometimes this can be awkward if
+ the instrument is being mounted in some sort of measuring jig, or
+ annoying if several sets of readings are being taken in quick
+ succession. The -<span style="font-weight: bold;">N</span>
+ suppresses this initial calibration if a valid and not timed out
+ previous calibration is recorded in the instrument or on the host
+ computer. It is advisable to only use this option on the second and
+ subsequent measurements in a single session.<br>
+ <br>
+ <a name="H"></a> The -<span style="font-weight: bold;">H</span>
+ option turns on high resolution spectral mode, if the instrument
+ supports it. See <a href="instruments.html">Operation of particular
+ instruments</a> for more details.<br>
+ <br>
+ <a name="Yr"></a> The -<span style="font-weight: bold;">Y r</span>
+ option turns on refresh mode measurement, if the instrument supports
+ it. This may improve the repeatability of measurements of
+ illuminants that have a repetitive flicker.<br>
+ <br>
+ <a name="W"></a>The <b>-W</b> <span style="font-weight: bold;">n|h|x</span>
+ parameter overrides the default serial communications flow control
+ setting. The value <span style="font-weight: bold;">n</span> turns
+ all flow control off, <span style="font-weight: bold;">h</span>
+ sets hardware handshaking, and <span style="font-weight: bold;">x</span>
+ sets Xon/Xoff handshaking. This commend may be useful in workaround
+ serial communications issues with some systems and cables. <br>
+ <br>
+ <a name="T"></a>The <b>-T</b> flag invokes the test mode. In test
+ mode the three measurements are saved to files <i>illuminant</i><i>_i.sp</i>
+ (Illuminant spectrum), <i>illuminant</i><i>_r.sp</i> (Illuminant
+ off paper spectrum), and <i>illuminant_p.sp (</i>Instrument
+ measured paper reflectance spectrum), and these will be loaded if
+ discovered, allowing a replay of the calculation without requiring
+ any measurement. In addition, two diagnostic files <i>illuminant</i><i>_mpir.sp</i>
+ (Measured paper under illuminant spectrum) and <i>illuminant</i><i>_cpir.sp +
+ (</i>Computed paper under illuminant spectrum) will be saved.<br>
+ <br>
+ <a name="D"></a>The <b>-D</b> flag causes communications and other
+ instrument diagnostics to be printed to stdout. A level can be set
+ between 1 .. 9, that may give progressively more verbose
+ information, depending on the instrument. This can be useful in
+ tracking down why an instrument can't connect.<br>
+ <br>
+ <a name="file"></a>The <span style="font-weight: bold; font-style:
+ italic;">illuminant.sp</span> is the name of the file to save the
+ resulting illuminant spectrum to. The format used is <a
+ href="File_Formats.html#.sp">.sp</a>.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ Unlike the other measurement utilities, <span style="font-weight:
+ bold;">illumread</span> doesn't connect to the instrument until it
+ is about to make a measurement. This allows for the possibility of
+ using a different instrument for each measurement.<br>
+ <br>
+ It will display a menu:<br>
+ <br>
+ Press 1 .. 6<br>
+ 1) Measure direct illuminant<br>
+ 2) Measure illuminant reflected from paper<br>
+ 3) Measure paper<br>
+ 4) Select another instrument, Currently 1 'usb:/bus4/dev2/
+ (GretagMacbeth i1 Pro)'<br>
+ 5) Compute illuminant spectrum, average result with 0 previous
+ readings & save it<br>
+ 6) Compute illuminant spectrum from this reading & save result<br>
+ 7) Exit<br>
+ <br>
+ There are three measurements to be made, after which the illuminant
+ can be computed and saved. Before each measurement, the instrument
+ may need calibrating.<br>
+ <br>
+ The first measurement needs a spectral instrument capable of reading
+ in an ambient or emissive mode. For instance, a Spectrolino, Eye-One
+ Pro or ColorMunki would be suitable instruments.<br>
+ <br>
+ The second measurement needs a spectral instrument capable of
+ reading in an projector or emissive mode. For instance, a
+ Spectrolino, Eye-One Pro or ColorMunki would be suitable
+ instruments.<br>
+ <br>
+ The third measurement needs a spectral instrument capable of reading
+ in reflective mode with UV included. For instance, a Spectrolino,
+ Eye-One Pro, DTP20, DTP22 or DTP41 would be suitable
+ instruments, as long as they are not fitted with UV filters.<br>
+ <br>
+ To be able to estimate the level of Ultra Violet (UV) light in the
+ illuminant, a reasonable sized piece of white paper needs to be
+ used. The paper should have some noticeable level of FWA
+ (Fluorescent Whitener Additive, or Optical Brightening Agents) in
+ it, so that it responds to UV light. A piece of cheap copier paper
+ is ideal, since cheap paper is typically whitened with large amounts
+ of FWA. If the paper is thin (less than 160 gsm) then two or three
+ sheets should be used to prevent any background showing through. If
+ the intention is to use the illuminant spectrum for proofing to a
+ particular paper, then it's best to use the intended paper for this
+ purpose.<br>
+ <br>
+ The first measurement <span style="font-weight: bold;">1)</span>,
+ is to use either the ambient or emissive measurement mode to measure
+ the illumination directly.<br>
+ <br>
+ <div style="margin-left: 40px;">If the instrument supports an
+ ambient measurement capability, then it will be used. If the
+ insrument does not have an ambient mode, then an emissive
+ measurement mode can be used, although typically many illuminants
+ are too bright to directly point the instrument at. A work-around
+ is to reflect the illuminant from a spectrally flat white surface.
+ A good candidate for this is a piece of white, fine textured
+ polystyrene foam. [The suitability of a reflector can be checked
+ using <span style="font-weight: bold;">spotread -S</span> to
+ check that the reflection characteristic is close to flat.]<br>
+ <br>
+ <img style="width: 228px; height: 300px;" alt="Measuring Ambient"
+ src="illumread_1.jpg"><img style="width: 141px; height: 282px;"
+ alt="Measuring Ambient" src="illumread_2.jpg"> <img
+ style="width: 226px; height: 282px;" alt="Measuring Ambient"
+ src="illumread_3.jpg"><br>
+ </div>
+ <br>
+ The second measurement <span style="font-weight: bold;">2)</span>,
+ is to measure the illuminant after it has reflected from the paper.<br>
+ <br>
+ <div style="margin-left: 40px;">This is done by placing the paper
+ such that it is uniformly illuminated with reasonable brightness,
+ and then placing the instrument so that it receives the reflected
+ light from the paper. This is typically achieved by placing the
+ instrument close to the paper at about 45º, so that it's aperture
+ has a clear view of the illuminated paper, but avoiding shadowing
+ the region that is in view. <br>
+ <br>
+ <img style="width: 219px; height: 261px;" alt="Measuring via
+ Paper" src="illumread_5.jpg"><img style="width: 252px; height:
+ 259px;" alt="Measuring via Paper" src="illumread_4.jpg"><br>
+ </div>
+ <br>
+ The third measurement <span style="font-weight: bold;">3)</span>,
+ is to measure the paper directly using the instrument reflective
+ mode measurement.<br>
+ <div style="margin-left: 40px;"><img style="width: 186px; height:
+ 162px;" alt="Measuring Paper" src="illumread_6.jpg"><br>
+ </div>
+ If a different instrument is needed, use <span style="font-weight:
+ bold;">4)</span> to select from the available instruments attached
+ to your computer.<br>
+ <br>
+ Once these three measurements have been made, then the illuminant
+ readings spectrum can be computed and save using <span
+ style="font-weight: bold;">6)</span>, or a series of readings can
+ be made with each reading being averages with the previous readings
+ before saving it by using <span style="font-weight: bold;">5)</span>.
+ Note that the averaged readings will be weighted by their absolute
+ intensities, and that while the direct and indirect illumination
+ needs measuring for each reading, the same paper measurement can be
+ used each time.<br>
+ <br>
+ If plotting is enabled, a plot of the measured (black) and with
+ estimated UV (red) is plotted. This is followed by a plot showing
+ measured paper reflectance (black) and the FWA calculated paper
+ reflectance (red).<br>
+ <br>
+ <br>
+ Illumread can then be terminated using <span style="font-weight:
+ bold;">7)</span>.<br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ </body>
+</html>
diff --git a/doc/instruments.html b/doc/instruments.html index 0bcc62d..f5897d5 100644 --- a/doc/instruments.html +++ b/doc/instruments.html @@ -34,9 +34,25 @@ + + + + + + + - Tele-Spectro-Radiometer<br>
<br>
+ Klein:<br>
+ <br>
+ <a href="#k10a">K10-A</a>
+
+
+
+ - Display Colorimeter. Reported also to work with
+ the K-1, K-8 and K-10<br>
+ <br>
X-Rite:<br>
<a href="#DTP20">DTP20 "Pulse"</a>
@@ -72,6 +88,13 @@ + + + + + + + - "swipe" type reflective spectrometer, that can be used untethered.<br>
<a href="#DTP22">DTP22 Digital Swatchbook</a> @@ -107,6 +130,13 @@ + + + + + + + - spot type reflective spectrometer.<br>
<a href="#DTP41">DTP41</a> @@ -142,6 +172,13 @@ + + + + + + + - spot and strip reading reflective spectrometer.<br>
<a href="#DTP41">DTP41T</a>
@@ -179,6 +216,13 @@ + + + + + + + - spot and strip reading reflective/transmissive spectrometer.<br>
<a href="#dtp51">DTP51</a> @@ -214,6 +258,13 @@ + + + + + + + - strip reading reflective colorimeter.<br>
<a href="#DTP92">DTP92</a> @@ -249,6 +300,13 @@ + + + + + + + - CRT display colorimeter.<br>
<a href="#DTP94">DTP94</a> <font size="-1">"Optix @@ -284,6 +342,13 @@ + + + + + + + XR"</font> or "Optix XR2" or "Optix Pro"- display colorimeter.<br>
<a href="#ColorMunki"><span style="text-decoration: underline;"></span></a> @@ -319,6 +384,13 @@ + + + + + + + <a href="#ColorMunki"><span style="text-decoration: underline;">ColorMunki</span></a>
Design or Photo
@@ -408,6 +480,13 @@ + + + + + + + - display colorimeter. (Treated as a Eye-One Display 2)<br>
<a href="#i1d">CalMAN X2</a>
@@ -444,6 +523,13 @@ + + + + + + + - display colorimeter. (Treated as a Eye-One Display 2)<br>
<a href="#Huey">Huey</a>
@@ -489,6 +575,13 @@ + + + + + + + [The Sequel Chroma 4 may also work.]<br>
<br>
@@ -526,6 +619,13 @@ + + + + + + + - see <a href="#i1d">Eye-One Display</a><br>
<br>
@@ -568,6 +668,13 @@ + + + + + + + [The Spyder 1 also seems to work.]<br>
<a href="#spyd3">Spyder 3</a>
@@ -580,6 +687,12 @@ - display colorimeter (Note
that the user must <a href="oeminst.html">supply</a> calibration
data)<br>
+ <a href="#spyd5">Spyder 5</a>
+
+
+ - display colorimeter (Note
+ that the user must <a href="oeminst.html">supply</a> calibration
+ data)<br>
<br>
Other:<br>
<span class="titre"><a href="#HCFR">Colorimètre
@@ -616,6 +729,13 @@ + + + + + + + - display colorimeter<br>
</span> <a href="#ColorHug">ColorHug</a> @@ -642,6 +762,13 @@ + + + + + + + - display colorimeter<span class="titre"><br>
</span><br>
@@ -948,6 +1075,13 @@ + + + + + + + type</span> selection parameter. Depending on the instrument, this
may combine two related functions: 1) Changing the measurement mode
@@ -995,8 +1129,8 @@ this measurement. A rough guide is as follows:<br>
<br>
</p>
- <table border="1" height="230" width="372" cellpadding="2"
- cellspacing="2">
+ <table cellpadding="2" cellspacing="2" border="1" height="230"
+ width="372">
<tbody>
<tr>
<td valign="top"><b>Instrument</b></td>
@@ -1009,6 +1143,12 @@ </td>
</tr>
<tr>
+ <td valign="top">Klein K10-A<br>
+ </td>
+ <td valign="top">0.05<br>
+ </td>
+ </tr>
+ <tr>
<td valign="top">DTP92<br>
</td>
<td valign="top">0.1<br>
@@ -1065,8 +1205,8 @@ style="font-weight: bold;">specbos 1211 and 1201
Tele-Spectro-Radiometer<br>
</span></span></p>
- <img alt="JETI specbos 1211" src="JETI_1211.jpg" height="210"
- width="211">
+ <img alt="JETI specbos 1211" src="JETI_1211.jpg" height="254"
+ width="257">
<p><span style="font-weight: bold;"><br>
</span><span style="font-weight: bold;">Availability:<br>
<br>
@@ -1075,9 +1215,53 @@ href="http://www.jeti.com/">JETI</a> are currently
available instruments. These are reference grade instruments
capable of emissive and ambient measurements, and are often used
- for monitor, projector and cinema calibration and
- characterization, amongst many other uses.<br>
+ for monitor, projector and cinema calibration &
+ characterization, and colorimeter calibration, amongst many other
+ uses.<br>
+ </p>
+ <p><br>
+ </p>
+ <hr size="2" width="100%">
+ <p><span style="font-weight: bold;"><a name="k10a"></a><span
+ style="font-weight: bold;">Klein K10-A Colorimeter<br>
+ </span></span></p>
+ <img alt="Klein K10-A" src="K10A.jpg" height="236" width="267"><br>
+ <p><span style="font-weight: bold;"><br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">Klein K10-A </span>from + + + + + +
+ <a href="http://www.kleininstruments.com/">Klein Instruments</a> + + + + + +
+ is a currently available instrument. It is noted for it's speed,
+ high precision, and ability to measure to very low light
+ levels.This is a high end instruments capable of contact and tele
+ - emissive, and ambient measurements, and are often used for
+ monitor, projector and cinema calibration and characterization. <br>
+ </p>
+ <p>Note that unlike the operation of other instruments, the Ambient
+ mode is purely manual - the diffuser must be fitted and then the
+ appropriate calibration setting chosen (Typically with "Lux" in
+ the name).<br>
</p>
+ <p>By default, more measurements are taken and averaged together
+ when the light level is low. This can be disabled and a single
+ measurement taken per reading, to gain maximum speed by using the
+ -Y A flag.<br>
+ </p>
+ <p>The <b>K-1</b>, <b>K-8</b> and <b>K-10</b> are also
+ reported to work. </p>
+ <p> </p>
<hr size="2" width="100%">
<p><br>
</p>
@@ -1362,6 +1546,13 @@ + + + + + + + CRT display A Cathode Ray
Tube display, that is of the Refresh type [Default, CB2].<br>
@@ -1417,6 +1608,13 @@ + + + + + + + LCD display A Liquid
Crystal Display, that is of the Non-Refresh type [default, CB1].<br>
@@ -1453,6 +1651,13 @@ + + + + + + + CRT display A Cathode Ray
Tube display, that is of the Refresh type [CB2].<br>
@@ -1505,6 +1710,13 @@ Gretag + + + + + + + MacBeth (Now X-Rite) is a discontinued instrument. It is often
available second hand. If buying it second hand, make sure it comes
@@ -1743,6 +1955,13 @@ Gretag + + + + + + + Smile</span> are:<br>
<br>
@@ -1766,6 +1985,13 @@ Gretag + + + + + + + LCD with LED back-light
A Liquid Crystal display that uses
@@ -1806,6 +2032,13 @@ Gretag + + + + + + + LCD display A Liquid
Crystal Display, that is of the Non-Refresh type. [Default, CB1]<br>
@@ -1842,6 +2075,13 @@ Gretag + + + + + + + CRT display A
Cathode Ray Tube display, that is of the Refresh type. [CB2]<br>
@@ -1897,6 +2137,13 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP + + + + + + + DreamColor</a> instruments are also reported to work. They will
appear as a be a the same as the i1Display Pro.<br>
@@ -1943,6 +2190,11 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP <b>p</b> Projector
(Marantz HP Panasonic Projectors Hybrid EDR)<br>
<br>
+ By default the integration time is adaptive, taking longer when the
+ light level is low. This can be disabled and a fixed integration
+ time used to gain maximum speed at the cost of greatly reduced low
+ light accuracy, by using the -Y A flag.<br>
+ <br>
<b>Note when measuring CRT displays:<br>
</b><br>
The small magnet in the ambient light cover used to signal what
@@ -1999,6 +2251,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + Pro</a> is still available.<br>
<span style="font-weight: bold;"></span><br>
@@ -2039,6 +2298,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + LCD display A Liquid
Crystal Display, that is of the Non-Refresh type. [Default, CB1]<br>
@@ -2075,6 +2341,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + CRT display A Cathode Ray
Tube display, that is of the Refresh type. [CB2]<br>
@@ -2136,6 +2409,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + CRT display A Cathode Ray
Tube display, that is of the Refresh type.<br>
@@ -2172,6 +2452,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + LCD display A Liquid
Crystal Display, that is of the Non-Refresh type.<br>
@@ -2241,6 +2528,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + LCD display A Liquid Crystal
Display, that is of the Non-Refresh type. [Default, CB1]<br>
@@ -2277,6 +2571,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + CRT display A Cathode Ray
Tube display, that is of the Refresh type. [CB2]<br>
@@ -2436,6 +2737,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + - normal gamut Liquid Crystal Display with standard Cold Cathode
Fluorescent Lamp backlight.<br>
@@ -2481,6 +2789,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + Wide Gamut LCD, RGB LED
Backlight - wide gamut Liquid Crystal Display with RGB LED
@@ -2521,6 +2836,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + - normal gamut Liquid Crystal Display with alternative Cold Cathode
Fluorescent Lamp backlight (Laptop ?)<br>
@@ -2529,6 +2851,222 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey style="font-weight: bold;">Spyder4Elite</span> and <span
style="font-weight: bold;">Spyder4Pro</span> instruments, but is
only capable of monochrome readings.<span style="font-weight: bold;"></span><br>
+ <br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <span style="font-weight: bold;"><a name="spyd5"></a>Spyder 5
+ colorimeter<br>
+ <br>
+ <img style="width: 262px; height: 220px;" alt="Spyder4"
+ src="Spyd5.jpg" height="350" width="449"> <br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">Spyder5Elite</span>, <span
+ style="font-weight: bold;">Spyder5Pro</span> and <span
+ style="font-weight: bold;">Spyder5Express</span> are a currently
+ available instruments. The <span style="font-weight: bold;">Spyder5Elite</span>
+ and <span style="font-weight: bold;">Spyder5Pro</span> appear to be
+ identical hardware with different software from the manufacturer.
+ The <span style="font-weight: bold;">Spyder5Express</span> lacks
+ the ambient sensor.<br>
+ <span style="font-weight: bold;"><br>
+ </span><span style="font-weight: bold;">Operation:<br>
+ </span><br>
+ These instruments are capable of using using CCSS (<a
+ href="file:///D:/src/argyll/doc/File_Formats.html#ccss">Colorimeter
+ Calibration Spectral Sample</a>) files, and this also gives the
+ instrument the capability of using a non-default standard observer.
+ CCSS files can be created using the <a
+ href="file:///D:/src/argyll/doc/ccxxmake.html">ccxxmake</a> tool
+ using a spectrometer as a reference.<br>
+ <br>
+ <span style="font-weight: bold;">Important Note </span>about the
+ DataColor Spyder 5 vendor display type/calibration support:<br>
+ <br>
+ This instrument does not have a full range of display type
+ calibration selections available without the vendor supplied
+ calibration data for it.<br>
+ This calibration data is not provided with Argyll, since it is not
+ available under a compatible license.<br>
+ You can use CCSS files as an alternative (see above), or as the
+ purchaser of a Spyder 5 instrument you should have received a copy
+ of the calibration data along with the instrument or have been
+ directed to download it from the manufacturers website, and should
+ therefore be able to enable the full range of display type
+ selections in Argyll by using the <a
+ href="file:///D:/src/argyll/doc/oeminst.html">oeminst</a> tool.<br>
+ <br>
+ The Display Selections for this instrument are:<br>
+ <br>
+ <span style="font-weight: bold;">n</span> | <span
+ style="font-weight: bold;">l</span>
+ A non-refresh type display with a generic calibration
+ [Default, CB1].<br>
+ <span style="font-weight: bold;">r | c</span> <span
+ style="font-weight: bold;"></span> A
+ refresh type display with a generic calibration.[CB2]<br>
+ <br>
+ The Display Selections for this instrument when the manufacturers
+ calibration information has been installed is:<br>
+ <br>
+ <span style="font-weight: bold;">n </span><span
+ style="font-weight: bold;"></span>
+ A non-refresh type display with a generic
+ calibration [Default, CB1].<br>
+ <span style="font-weight: bold;">r</span> <span
+ style="font-weight: bold;"></span>
+ A refresh type display with a generic
+ calibration.[CB2]<br>
+ <span style="font-weight: bold;">f
+ </span> LCD, CCFL
+ Backlight + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ - normal gamut Liquid Crystal Display with standard Cold Cathode
+ Fluorescent Lamp backlight.<br>
+ <span style="font-weight: bold;">L</span>
+ Wide Gamut LCD, CCFL
+ Backlight - wide gamut Liquid Crystal
+ Display with Cold Cathode Fluorescent Lamps backlight.<br>
+ <span style="font-weight: bold;">e</span>
+ LCD, White
+ LED Backlight
+ - normal
+ gamut Liquid Crystal Display with a White LED backlight.<br>
+ <span style="font-weight: bold;">B</span> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Wide Gamut LCD, RGB LED
+ Backlight - wide gamut Liquid Crystal Display with RGB LED
+ backlight.<br>
+ <span style="font-weight: bold;">x</span>
+ LCD, CCFL
+ Type 2
+ Backlight + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ - normal gamut Liquid Crystal Display with alternative Cold Cathode
+ Fluorescent Lamp backlight (Laptop ?)<br>
+ <br>
+ The ambient light sensor can be used with the <span
+ style="font-weight: bold;">Spyder5Elite</span> and <span
+ style="font-weight: bold;">Spyder5Pro</span> instruments, but is
+ only capable of monochrome readings.<span style="font-weight: bold;"></span><br>
<span style="font-weight: bold;"></span><br>
<hr style="width: 100%; height: 2px;"><a name="HCFR"></a><span
style="font-weight: bold;" class="titre">Colorimètre HCFR
@@ -2571,6 +3109,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + HCFR Probe</span> is a kit instrument from <span
style="font-weight: bold;"></span> <a
@@ -2625,6 +3170,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + LCD display A Liquid
Crystal Display [Default].<br>
@@ -2661,6 +3213,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + CRT display A Cathode Ray
Tube display.<br>
@@ -2694,35 +3253,77 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey <b>l</b> + + + + + + + LCD, CCFL Backlight [Default]<br>
<b>c</b> + + + + + + + CRT display<br>
<b>p</b> + + + + + + + Projector<br>
<b>e</b> + + + + + + + LCD, White LED Backlight<br>
<b>F</b> + + + + + + + Factory matrix (For Calibration) [CB1]<br>
<b> R</b> + + + + + + + Raw Reading (For Factory matrix Calibration) [CB2]<br>
<br>
diff --git a/doc/invprofcheck.html b/doc/invprofcheck.html index 9851774..bd611b3 100644 --- a/doc/invprofcheck.html +++ b/doc/invprofcheck.html @@ -39,10 +39,10 @@ Show CIE94 delta E values</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -k Show CIEDE2000 delta E values</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -w -create VRML visualisation (profile.wrl)</span><br +create X3DOM visualisation (profile.x3d.html)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -x -Use VRML axes</span><br style="font-family: monospace;"> +Use X3DOM axes</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -e Color vectors acording to delta E</span><br style="font-family: monospace;"> @@ -60,7 +60,7 @@ table. A grid of device values is created, and the transform from PCS->device, and then device->PCS is computed in L*a*b* space. The average, maximum and RMS error delta E values are computed and displayed in the chosen delta E metric. A <a - href="File_Formats.html#VRML">VRML</a> plot of the error vectors can + href="File_Formats.html#X3DOM">X3DOM</a> plot of the error vectors can be created. <span style="font-weight: bold;">invprofcheck</span> tries to only test in-gamut color values. Note that because it scans a device grid, for a CMYK device, the density of test points will be @@ -114,16 +114,16 @@ closer correspondence with perceived color differences than either CIE76 or CIE94 delta E values.<br> <br> -The <b>-w</b> creates a <a href="File_Formats.html#VRML">VRML</a> 3D +The <b>-w</b> creates a <a href="File_Formats.html#X3DOM">X3DOM</a> 3D visualization of the differences between the test points and the profiles prediction of the resulting colors.<br> <br> -The <b>-x</b> flag adds Lab axes to the VRML output.<br> +The <b>-x</b> flag adds Lab axes to the X3DOM output.<br> <br> The <span style="font-weight: bold;">-e</span> flag causes the error -vectors in the VRML output to be color coded according to their +vectors in the X3DOM output to be color coded according to their lengths, from longest to shortest: yellow, red, magenta, blue, cyan and green.<br> <br> diff --git a/doc/mpplu.html b/doc/mpplu.html index 2f0b955..8d4e755 100644 --- a/doc/mpplu.html +++ b/doc/mpplu.html @@ -11,7 +11,7 @@ <h3>Summary</h3> Lookup individual color values though an <a href="File_Formats.html#MPP">MPP</a> profile. Also -create MPP gamut files or <a href="File_Formats.html#VRML">VRML</a> +create MPP gamut files or <a href="File_Formats.html#X3DOM">X3DOM</a> views.<br> <h3>Usage</h3> <small><span style="font-family: monospace;">mpplu [-v level] [-f func] @@ -63,9 +63,9 @@ data:</span><br style="font-family: monospace;"> Create gamut output</span><br style="font-family: monospace;"> <span style="font-family: monospace;">-w - Create gamut VRML as well<br> + Create gamut X3DOM as well<br> -n -Don't add VRML axes<br> +Don't add X3DOM axes<br> -a n Gamut transparency level<br style="font-family: monospace;"> </span><span style="font-family: monospace;">-d @@ -78,7 +78,7 @@ surface detail level</span><br style="font-family: monospace;"> 1 - check partial derivative for device input</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 2 - create overlap diagnostic VRML gamut + 2 - create overlap diagnostic X3DOM gamut surface</span><br style="font-family: monospace;"> <span style="font-family: monospace;">profile.mpp Profile to be used</span><br style="font-family: monospace;"> @@ -157,15 +157,15 @@ description from the profile, creating a <a the given profile.<br> <br> The <b>-w</b> flag causes the gamut surface to be generated in <a - href="File_Formats.html#VRML">VRML</a> format + href="File_Formats.html#X3DOM">X3DOM</a> format as well as <a href="File_Formats.html#.gam">.gam</a> format.<br> <br> <small><span style="font-family: monospace;">The <span - style="font-weight: bold;">-n</span> flag suppresses the VRML axes.<br> + style="font-weight: bold;">-n</span> flag suppresses the X3DOM axes.<br> <br> The <span style="font-weight: bold;">-a</span> <span style="font-weight: bold;">n</span> parameter sets a transparency -level in the VRML surface.</span></small><br> +level in the X3DOM surface.</span></small><br> <br> The <b>-d</b> parameter controls the level of detail displayed in the gamut surface. The parameter roughly corresponds to a deltaE value, so diff --git a/doc/oeminst.html b/doc/oeminst.html index ffbc0f0..d1daccd 100644 --- a/doc/oeminst.html +++ b/doc/oeminst.html @@ -3,7 +3,7 @@ <head> <title>oeminst</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> @@ -16,7 +16,7 @@ list (<b>-y</b> option).<br> For the Spyder 2, it can install the instrument manufacturers PLD firmware pattern, which is necessary for it to operate.<br> - For the Spyder 4, it can enable the full range of manufacturers + For the Spyder 4 or 5, it can enable the full range of manufacturers colorimeter calibration selections, as well as install CCSS files.<br> For the eye-one display 3 it can locate and translate X-Rite .EDR files to CCSS files and install them to enable a full range of @@ -38,6 +38,7 @@ + Verbose</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -n @@ -49,6 +50,7 @@ + Don't install, show where files would be installed</span><br> <span style="font-family: monospace;"> -c @@ -61,6 +63,7 @@ + Don't install, save files to current directory</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -S @@ -74,6 +77,7 @@ + Specify the install scope u = user (def.), l = local system]</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> infile @@ -86,6 +90,7 @@ + setup.exe CD install file(s) or .dll(s) containing install files</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> infile.[edr|ccss|ccmx] @@ -97,6 +102,7 @@ + EDR file(s) to translate and install or CCSS or CCMX files to install</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -109,6 +115,7 @@ + </span><small><span style="font-family: monospace;">If no file is provided, oeminst will look for the install CD.</span></small> <h3></h3> @@ -151,6 +158,7 @@ + 2</span> instrument cannot function without the presence of the instrument vendors PLD firmware pattern for the device. This firmware is not provided with Argyll, since it has not been made @@ -187,6 +195,7 @@ href="http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html">XDG + Base Directory specifications</a> are used as a basis for storing the file). Programs that access instruments such as <span style="font-weight: bold;">spotread</span>, <span @@ -214,15 +223,17 @@ href="http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html">XDG - 4</span> instrument does not have the full range of vendor - instrument calibration options without the presence of the - instrument vendors calibration information for the device. This - calibration information is not provided with Argyll, since it has - not been made available under a compatible license.<br> + + 4</span> or <u><b>Spyder 5</b></u> instrument does not + have the full range of vendor instrument calibration options + without the presence of the instrument vendors calibration + information for the device. This calibration information is not + provided with Argyll, since it has not been made available under a + compatible license.<br> <br> - The purchaser of a Spyder 4 instrument should have received a copy - of this calibration information along with their instrument from - the original vendor, and <span style="font-weight: bold;">oeminst</span> + The purchaser of a Spyder 4 or 5 instrument should have received a + copy of this calibration information along with their instrument + from the original vendor, and <span style="font-weight: bold;">oeminst</span> enables the full range of calibration choice for their instrument, by locating the necessary information in the users copy of the instrument install files.</p> @@ -233,8 +244,12 @@ href="http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html">XDG drivers have not been installed, or the user does not wish to install them, or no vendors drivers are available for the users platform (i.e. Linux), then <span style="font-weight: bold;">oeminst</span> - will also attempt to locate the Spyder 4 installation CDROM, and - make use of the calibration information from there.</p> + will also attempt to locate the Spyder 4 or 5 installation CDROM, + and make use of the calibration information from there. If you + have downloaded the OEM software from the vendors website, then + you should run <b>oeminst</b> on the install package you + downloaded.<br> + </p> <br> <span style="font-weight: bold;"></span>The <span style="font-weight: bold; text-decoration: underline;">i1d3</span> @@ -279,6 +294,7 @@ href="http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html">XDG + Base Directory specifications</a> are used as a basis for storing the file). Programs that access instruments such as <span style="font-weight: bold;">spotread</span>, <span @@ -295,8 +311,7 @@ href="http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html">XDG colorimeter model that they were created for.<br> <br> If you are going to use the same CCSS or CCMX file all the time, - then you may want to set the <a - href="Environment.html">ARGYLL_COLMTER_CAL_SPEC_SET</a> + then you may want to set the <a href="Environment.html">ARGYLL_COLMTER_CAL_SPEC_SET</a> environment variable.<br> <br> <br> diff --git a/doc/profcheck.html b/doc/profcheck.html index ef0bc5b..a85e07e 100644 --- a/doc/profcheck.html +++ b/doc/profcheck.html @@ -3,7 +3,7 @@ <head> <title>profcheck</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> @@ -11,22 +11,25 @@ <h3>Summary</h3> Check an <a href="File_Formats.html#ICC">ICC</a> profile against <a href="File_Formats.html#.ti3">.ti3</a> test chart - data.<br> + data, and optionally create a pruned .ti3 file.<br> <h3>Usage Summary</h3> <small><span style="font-family: monospace;">profcheck - [-options] - data.ti3 iccprofile.icm</span><br style="font-family: + [-options] data.ti3 iccprofile.icm</span><br style="font-family: monospace;"> - - <span style="font-family: monospace;"></span></small><small><span + <span style="font-family: monospace;"></span></small><small><span style="font-family: monospace;">-v - [level] - Verbosity level (default 1), 2 to print each DE</span></small><small><span + [level] Verbosity level (default + 1), 2 to print each DE</span></small><small><span style="font-family: monospace;"></span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -c Show + + + + + CIE94 delta E values</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -k @@ -35,157 +38,204 @@ Show <span style="font-family: monospace;"> -w create - VRML visualization (iccprofile.wrl)</span><br + + + + + + X3DOM visualization (iccprofile.x3d.html)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -x Use - VRML axes<br> + + + + + + X3DOM axes<br> -m Make -VRML +X3DOM + + + + + lines a minimum of 0.5<br style="font-family: monospace;"> </span><span style="font-family: monospace;"> -e Color vectors - acording to delta E</span><br style="font-family: monospace;"> - <span style="font-family: monospace;"> -d + + + + + + acording to delta E<br> + -s + Sort output by delta E<br> + -h + + + + + Plot a histogram of delta E's<br> + -P + de + Create a pruned .ti3 with points less or equal to de delta E<br + style="font-family: monospace;"> + </span> <span style="font-family: monospace;"> -d devval1,deval2,devvalN</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> Specify - a device value to sort - against</span><br style="font-family: monospace;"> + + + + + + a device value to sort against</span><br style="font-family: + monospace;"> <span style="font-family: monospace;"> -p Sort + + + + + device value by PCS/Lab target</span><br style="font-family: monospace;"> - - <span style="font-family: monospace;">-f + <span style="font-family: monospace;">-f [illum] Use Fluorescent Whitening Agent compensation [opt. simulated inst. illum.:<br> + + + + + M0, M1, M2, A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp]<br> -i illum Choose illuminant for computation of CIE XYZ from spectral data & FWA:<br> + + + + + A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp</span><span style="font-family: monospace;"></span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -o - observ - Choose CIE - Observer - for spectral data:</span><br style="font-family: monospace;"> + observ Choose CIE Observer for + spectral data:</span><br style="font-family: monospace;"> <span style="font-family: monospace;"></span></small><small><span style="font-family: monospace;"> - 1931_2 - </span></small><small><span style="font-family: monospace;">(def.)</span></small><small><span - style="font-family: monospace;">, - 1964_10, S&B - 1955_2, shaw, J&V 1978_2</span></small><small><span - style="font-family: monospace;"><br> + + + + + + 1931_2 </span></small><small><span style="font-family: + monospace;">(def.)</span></small><small><span + style="font-family: monospace;">, 1964_10, S&B 1955_2, shaw, + J&V 1978_2</span></small><small><span style="font-family: + monospace;"><br> -I intent r = relative colorimetric, a = absolute (default)<br style="font-family: monospace;"> </span><i style="font-family: monospace;"> data.ti3</i><span style="font-family: monospace;"> - - Test - point data file</span><br style="font-family: monospace;"> + Test point data file</span><br style="font-family: + monospace;"> <i style="font-family: monospace;"> iccprofile.icm</i><span style="font-family: monospace;"> Profile to check</span></small> <br> <h3>Usage Details and Discussion</h3> <b> profcheck</b> provides a way of checking how well an <a href="File_Formats.html#ICC">ICC</a> profile conforms to the test - sample data that was used to create it (or other test samples - that are from the same device). This is the same sort of check done - within - the profile making tool (<a href="colprof.html">colprof</a>), but - having a - separate tool provides some flexibility. The absolute forward - table in the profile is used to create PCS values from the sample - points, and the profiles PCS value then compared to the PCS values - of - the measured sample points. Note the lower delta E values are not - always a better measure of how good a profile is. The aim of a - profile - is to model the underlying characteristics of a device, not to - slavishly reproduce the sampled data point values. Sampled data - point - values contain device variation and instrument reading inaccuracies, - and a good profiler will try and filter out this noise, resulting in - some deliberate differences between the profile and the sample - points - used to create it.<br> + sample data that was used to create it (or other test samples that + are from the same device). This is the same sort of check done + within the profile making tool (<a href="colprof.html">colprof</a>), + but having a separate tool provides some flexibility. The + absolute forward table in the profile is used to create PCS values + from the sample points, and the profiles PCS value then compared to + the PCS values of the measured sample points. Note the lower delta E + values are not always a better measure of how good a profile is. The + aim of a profile is to model the underlying characteristics of a + device, not to slavishly reproduce the sampled data point values. + Sampled data point values contain device variation and instrument + reading inaccuracies, and a good profiler will try and filter out + this noise, resulting in some deliberate differences between the + profile and the sample points used to create it.<br> <br> The <b>-v</b> flag prints out extra information during the - checking. A - value greater than 1 will print the color values of each test point.<br> + checking. A value greater than 1 will print the color values of each + test point.<br> <br> The <b>-c</b> option causes the differences between the test values - and - the profile prediction of the color for each device value to be - displayed - in CIE94 delta E, rather than plain L*a*b* delta E. CIE94 delta E - has a - closer - correspondence with perceived color differences than the default - CIE76 - delta E values.<br> + and the profile prediction of the color for each device value to be + displayed in CIE94 delta E, rather than plain L*a*b* delta E. CIE94 + delta E has a closer correspondence with perceived color differences + than the default CIE76 delta E values.<br> <br> The <b>-k</b> option causes the differences between the test values - and - the profile prediction of the color for each device value to be - displayed - in CIEDE2000 delta E, rather than plain L*a*b* delta E. CIEDE2000 - delta - E has a - closer - correspondence with perceived color differences than either CIE76 or - CIE94 delta E values.<br> - <br> - The <b>-w</b> creates a <a href="File_Formats.html#VRML">VRML</a> - 3D - visualization - of the differences between the test points and the profiles - prediction - of - the resulting colors.<br> - <br> - The <b>-x</b> flag adds Lab axes to the VRML output.<br> + and the profile prediction of the color for each device value to be + displayed in CIEDE2000 delta E, rather than plain L*a*b* delta E. + CIEDE2000 delta E has a closer correspondence with perceived color + differences than either CIE76 or CIE94 delta E values.<br> + <br> + The <b>-w</b> creates a <a href="File_Formats.html#X3DOM">X3DOM</a> + 3D visualization of the delta E's between the test points and the + profiles prediction of the resulting colors.<br> + <br> + The <b>-x</b> flag adds Lab axes to the X3DOM output.<br> <br> The <b>-m</b> flag makes each error line a minimum of 0.5 delta E long, so that all the points are visible. This makes it easier to - view - the distribution of test points in the reference set.<br> + view the distribution of test points in the reference set.<br> <br> The <span style="font-weight: bold;">-e</span> flag causes the - error - vectors in the VRML output to be color coded according to their - lengths, from longest to shortest: yellow, red, magenta, blue, cyan - and - green.<br> + error vectors in the X3DOM output to be color coded according to + their lengths, from longest to shortest: yellow, red, magenta, blue, + cyan and green.<br> + <br> + The <b>-s</b> flag will cause the -v2 patch by patch delta E output + to be sort from largest to smallest. This is useful in identifying + badly read patches.<br> + <br> + The <b>-h</b> flag will display a histogram plot of the fit delta + E's. The X scale is delta E, the Y scale is %<br> + <br> + The <b>-P N.NN</b> option will create a pruned .ti3 file called + data_pN.NN that contains just the measurement points that have a fit + delta E of less than or equal to the given delta E threshold. This + can be useful if you know that there are faulty or poor accuracy + readings in the data set. Use profcheck -h to examine the fit delta + E histogram to choose a threshold that cuts off the tail, and then + profcheck -P to create the pruned data set. You can check that this + is appropriate if a profcheck -h on the resulting profile no longer + has a long tail. <b>Note</b> that using this procedure will be of + no benefit if the tail is due to an inherently poor fit of the + profile to the data rather than reading innacuracy, even if it makes + the fit appear to be better.<br> + <br> + <b>NOTE</b> that the pruning does not take any special care as to + what test points are pruned - it may prune important points such as + <b>white</b> and <b>black</b> points!<br> <br> The <b>-d</b> parameters allow the specification of a particular - device value, - and the test point by test point output will be sorted by distance - from - the - given device value. This can be useful in determining how well - "supported" - the profile is in a particular area of the colorspace.<br> + device value, and the test point by test point output will be sorted + by distance from the given device value. This can be useful in + determining how well "supported" the profile is in a particular area + of the colorspace.<br> <br> If the <b>-p </b>flag is used in combination with the <b>-d</b> - parameters, - then the test point by test point output will be sorted by distance - in - PCS - (Lab) space rather than distance in device space.<br> + parameters, then the test point by test point output will be sorted + by distance in PCS (Lab) space rather than distance in device space.<br> <br> The <b>-f</b> flag enables Fluorescent Whitening Agent (FWA) compensation. This only works if spectral data is available and, the @@ -197,31 +247,27 @@ Sort illumination spectrum to be used as the similated instrument illuminant, overriding the default <b>D50</b> or CIE computation illuminant used for FWA (see <b>-i</b> below<b>). </b>See <a - href="colprof.html#f">colprof -f</a> for - a fuller explanation. The same value should be used as was used - during the creation of the + href="colprof.html#f">colprof -f</a> for a fuller explanation. The + same value should be used as was used during the creation of the profile.<br> <br> The <b>-i</b> flag allows specifying a standard or custom - illumination - spectrum, applied to the spectral test point values to compute CIE - tristimulus values. <b>A</b>, <b>D50</b>, <b>D50M2, D65</b>, <b>F5</b>, - <b>F8</b>, <b>F10</b> are a selection of standard illuminant - spectrums, with <b>D50</b> being the default. If a filename is - specified instead, it will be assumed to be an Argyll specific <a - href="File_Formats.html#.sp">.sp</a> - spectrum file. If FWA compensation is used during measurement, this + illumination spectrum, applied to the spectral test point values to + compute CIE tristimulus values. <b>A</b>, <b>D50</b>, <b>D50M2, + D65</b>, <b>F5</b>, <b>F8</b>, <b>F10</b> are a selection of + standard illuminant spectrums, with <b>D50</b> being the default. + If a filename is specified instead, it will be assumed to be an + Argyll specific <a href="File_Formats.html#.sp">.sp</a> spectrum + file. If FWA compensation is used during measurement, this illuminant will be used by default as the simulated instrument illuminant. The same value should be used as was used during the - creation of the - profile.<br> + creation of the profile.<br> <br> <a name="o"></a> The <b>-o</b> flag allows specifying a tristimulus observer, and is used to compute PCS (Profile Connection Space) tristimulus values. The following choices are available:<br> <b> 1931_2</b> selects the standard CIE 1931 2 degree - observer. - The default.<br> + observer. The default.<br> <b>1964_10</b> selects the standard CIE 1964 10 degree observer.<br> <b>1955_2</b> selects the Stiles and Birch 1955 2 degree @@ -232,16 +278,15 @@ Sort observer<br> <br> The same parameter value should be used as was used during the - creation - of the profile.<br> + creation of the profile.<br> <br> The <span style="font-weight: bold;">-I</span> parameter allows changing the intent used in looking up the ICC profile colors to relative colorimetric. This would <span style="text-decoration: - underline;">not</span> be used if you are - checking a profile against the .ti3 file that was used to create it, - since, since profiles are always made - from absolute colorimetric measurement values.<br> + underline;">not</span> be used if you are checking a profile + against the .ti3 file that was used to create it, since, since + profiles are always made from absolute colorimetric measurement + values.<br> <br> <br> <br> diff --git a/doc/scanin.html b/doc/scanin.html index ac6ccc8..96d3cc2 100644 --- a/doc/scanin.html +++ b/doc/scanin.html @@ -3,7 +3,7 @@ <head> <title>scanin</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> @@ -59,6 +59,7 @@ style="font-family: monospace;"> Generate + a chart reference (.cht) file</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -66,6 +67,7 @@ Generate style="font-family: monospace;"> Output + patch values in .val file</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -73,6 +75,7 @@ Output style="font-family: monospace;"> Use + image to measure color to convert printer pbase .ti2 to .ti3</span><span style="font-family: monospace;"></span><br style="font-family: monospace;"> @@ -81,22 +84,26 @@ Use style="font-family: monospace;"> Same + as -c, but accumulates more values to pbase .ti3</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> from + subsequent pages</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#r">-r</a><span style="font-family: monospace;"> Replace + device values in pbase .ti3</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> Default + is to create a scanner .ti3 file<br> </span></small><small><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#F">-F @@ -105,10 +112,12 @@ Default Don't + auto recognize, locate using four fiducual marks<br> <a href="#p">-p</a> Compensate + for perspective distortion<br style="font-family: monospace;"> </span></small><small><span style="font-family: monospace;"></span><span style="font-family: monospace;"> </span><a @@ -116,28 +125,31 @@ Compensate style="font-family: monospace;"> Recognize + chart in normal orientation only</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> Default + is to recognize all possible chart angles<br> <a href="#m">-m</a> Return + true mean (default is robust mean)<br> </span></small><small><span style="font-family: monospace;"> <a href="#G">-G gamma</a> - Approximate - gamma encoding of image</span></small><br style="font-family: - monospace;"> + Approximate gamma encoding of image</span></small><br + style="font-family: monospace;"> <small><span style="font-family: monospace;"></span><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#v">-v [n]</a><span style="font-family: monospace;"> Verbosity + level 0-9</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#d">-d</a><span @@ -149,6 +161,7 @@ Verbosity style="font-family: monospace;"> diag + - B&W of input image</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -156,6 +169,7 @@ diag style="font-family: monospace;"> diag + - Horizontal edge detection</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -163,6 +177,7 @@ diag style="font-family: monospace;"> diag + - Vertical edge detection</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -170,32 +185,39 @@ diag style="font-family: monospace;"> diag + - Groups detected</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#dl">l</a><span style="font-family: monospace;"> diag + - Lines detected</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#dL">L</a><span style="font-family: monospace;"> diag + - All lines detected<br> </span></small><small><span style="font-family: monospace;"> + </span><span style="font-family: monospace;"><a href="#dI">I</a> diag + - lines used to improve fit<br> </span></small><small><span style="font-family: monospace;"> + </span><a style="font-family: monospace;" href="#dc">c</a><span style="font-family: monospace;"> diag + - lines perspective corrected</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"></span><span @@ -204,36 +226,42 @@ diag style="font-family: monospace;"> diag + - lines rotated</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#ds">s</a><span style="font-family: monospace;"> diag + - sample boxes rotated</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#do">o</a><span style="font-family: monospace;"> diag + - sample box outlines</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#dn">n</a><span style="font-family: monospace;"> diag + - sample box names</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#da">a</a><span style="font-family: monospace;"> diag + - sample box areas</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#dp">p</a><span style="font-family: monospace;"> diag + - pixel areas sampled</span></small> <br> <small><span style="font-family: monospace;"> <a href="#O">-O</a> outputfile Override the @@ -250,13 +278,15 @@ diag resolutions, and will cope with some degree of noise in the scan (due to screening artefacts on the original, or film grain), but it isn't really designed to accept very high resolution input. For - anything over 600DPI, you should consider down sampling the scan - using a filtering downsample, before submitting the file to scanin. - Similarly, any file with a large level of noise (due to screening or - scanner artefacts) should consider down sampling the image or - filtering it with some average preserving filter before submitting - it to scanin. Examining the diagnostic output (ie. -dig and -dil) - may help in determining whether noise is an issue.<br> + anything over 1200 pixels on a side, you should consider down + sampling the scan using a filtering down-sample, before submitting + the file to scanin. Similarly, any file with a large level of noise + (due to screening or scanner artefacts, or a noisy surrounding + texture) should consider cropping out the noisy surrounding, or down + sampling the image or filtering it with some average preserving + filter before submitting it to scanin. Examining the diagnostic + output (ie. -dig and -dil) may help in determining whether noise is + an issue.<br> <br> There are 5 basic modes that <b>scanin</b> operates in.<br> <ul> @@ -309,12 +339,14 @@ diag create the input device profile. The file arguments in -c mode are: <a name="cp1"></a>The TIFF file that is to be processed containing the image of a print test chart, <a name="cp2"></a>the + image recognition template file for the test chart generated by the <a href="printtarg.html"> printtarg</a> tool, <a name="cp3"></a>the input device ICC or MPP profile, <a name="cp4"></a>the base name for the .ti2 file containing the test chart printer device values and their patch identifiers and the base name for the resulting .ti3 file, <a name="cp5"></a>and + finally an optional name for the image recognition diagnostic output. The resulting .ti3 file will have the same base name as the input TIFF file. If there is more than one page in the test diff --git a/doc/spec2cie.html b/doc/spec2cie.html index c928f9a..d25b0a0 100644 --- a/doc/spec2cie.html +++ b/doc/spec2cie.html @@ -3,38 +3,43 @@ <head> <title>fakeread</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> <h2><b>spectro/</b><span style="text-decoration: underline;"></span>spec2cie</h2> <h3>Summary</h3> - Convert spectral <a href="File_Formats.html#.ti3">.ti3</a> - readings into CIE XYZ or L*a*b* readings. FWA compensation may be - applied.<br> + Convert reflective spectral <a href="File_Formats.html#.ti3">.ti3</a> + readings into CIE XYZ and D50 L*a*b* readings. Apply FWA, plot + spectrums.<br> <h3>Usage</h3> <tt><small>spec2cie [options] <span style="font-style: italic;">input.ti3 + + output.ti3<br> </span></small></tt><tt><small>-v Verbose mode</small></tt><br> - <tt><small><small> <a - href="spec2cie.html#I">-I <i>illum</i></a> - Override - actual instrument illuminant - in .ti3 file:<br> + <tt><small><small> <a href="spec2cie.html#I">-I <i>illum</i></a> + + + Override actual instrument illuminant in .ti3 + file:<br> - - A, C, D50, D50M2, D65, F5, - F8, F10 or file.sp<br> + A, C, D50, D50M2, D65, F5, F8, F10 or + file.sp<br> - (only - used in conjunction with <span style="font-weight: bold;">-f</span>)<br> + + + (only used in conjunction with <span style="font-weight: + bold;">-f</span>)<br> </small></small></tt><tt><small><small> <a - href="colprof.html#f">-f [<i>illum</i>]</a> - Use Fluorescent Whitening Agent compensation - [simulated inst. illum.:<br> + href="colprof.html#f">-f [<i>illum</i>]</a> Use + Fluorescent Whitening Agent compensation [simulated inst. + illum.:<br> + + M0, M1, M2, A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp]<br> </small></small></tt><tt><small><small><small> <a @@ -42,64 +47,66 @@ Choose illuminant for computation of CIE XYZ from spectral data & FWA:<br> - - - A, C, D50 (def.), D50M2, D65, F5, + A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp<br> - </small></small><a href="#o">-o - <i>observ</i></a> - Choose CIE Observer for spectral - data:<br> + </small></small><a href="#o">-o <i>observ</i></a> + + + Choose CIE Observer for spectral data:<br> + + 1931_2 </small></tt><tt><small> (def.)</small></tt><tt><small>, - 1964_10, S&B - 1955_2, shaw, J&V 1978_2<br> + 1964_10, S&B 1955_2, shaw, J&V 1978_2<br> <a href="#p">-n</a> Don't output + + spectral values<br> </small></tt><tt><small> <a href="#p">-p</a> - Plot - each values spectrum</small></tt><tt><br> - </tt><tt> - </tt><tt><small> <span style="font-style: italic;">input.ti3</span> + Plot each values spectrum</small></tt><tt><br> + </tt><tt> </tt><tt><small> <span style="font-style: italic;">input.ti3</span> Measurement + + file<br> <span style="font-style: italic;">output.ti3</span> - Converted - measurement file</small></tt><br> + + + Converted measurement file</small></tt><br> <h3>Comments</h3> - This program takes the spectral data in a .ti3 file, converts them - to - XYZ and Lab and fills the XYZ_[XYZ] and LAB_[LAB] columns in the - output - .ti3 file with the computed XYZ and Lab values. If the columns + This program takes the (usually reflective) spectral data in a .ti3 + file, converts them to XYZ and D50 L*a*b* and fills the XYZ_[XYZ] + and LAB_[LAB] columns in the output .ti3 file. If the columns XYZ_[XYZ] and/or LAB_[LAB] are missing in the input file, they are added to the output file.<br> <br> + If FWA correction is applied, then the spectra saved will be FWA + corrected, as well as the XYZ and D50 L*a*b* values.<br> + <br> All other columns are copied from the input to the output .ti3 file.<br> <br> + Setting an actual instrument/simulated instrument/CIE illuminant + only has an effect for reflective/transmissive spectra. Emissive + spectra don't have an illuminant, and will simply be converted to + XYZ using the given observer. <br> + <br> <br> <a name="I"></a>The <b>-I</b> parameter allows specifying a an - illumination - spectrum for the actual instrument illuminant, overriding that - computed from - the type of instrument (recorded in the .ti3 file). This is rarely - used. This parameter is can - only be used in combination with the <span style="font-weight: - bold;">-f</span> - flag. If a - filename is specified instead, it will be assumed to be an Argyll - specific <a href="File_Formats.html#.sp">.sp</a> - custom spectrum file. - Illuminant details are:<br> + illumination spectrum for the actual instrument illuminant, + overriding that computed from the type of instrument (recorded in + the .ti3 file). This is rarely used. This parameter is can only be + used in combination with the <span style="font-weight: bold;">-f</span> + flag. If a filename is specified instead, it will be assumed to be + an Argyll specific <a href="File_Formats.html#.sp">.sp</a> custom + spectrum file. Illuminant details are:<br> <br> A CIE - tungsten - filament lamp 2848K<br> + tungsten filament lamp 2848K<br> D50 CIE daylight 5000K<br> D65 CIE daylight 6500K<br> F5 CIE Fluorescent @@ -107,8 +114,7 @@ Measurement F8 CIE Fluorescent 5000K, CRI 95<br> F10 CIE Fluorescent - 5000K, - CRI 81<br> + 5000K, CRI 81<br> <br> <br> <a name="f"></a> The <b>-f</b> flag enables Fluorescent Whitening @@ -121,6 +127,8 @@ Measurement standard or custom illumination spectrum to be used as the similated instrument illuminant, overriding the default <b>D50</b> or CIE computation illuminant used for FWA (see <b>-i</b> below<b>). </b>See + + <a href="colprof.html#f">colprof -f</a> for a fuller explanation. <br> <br> <a name="i"></a>The <b>-i</b> parameter allows specifying a @@ -129,8 +137,7 @@ Measurement <b>D50</b>, <b>D65</b>, <b>F5</b>, <b>F8</b>, <b>F10</b> are a selection of standard illuminant spectrums, with <b>D50</b> being the default. If a filename is specified instead, it will be assumed - to be an Argyll specific <a - href="File_Formats.html#.sp">.sp</a> + to be an Argyll specific <a href="File_Formats.html#.sp">.sp</a> custom spectrum file. This only works if spectral data is available. Illuminant details are:<br> <br> @@ -181,22 +188,18 @@ Measurement Note that if an observer other than 1931 2 degree is chosen, the resulting ICC profile will not be standard, and cannot be freely interchanged with other profiles that that us the standard 1931 2 - degree - observer. Profiles should only be linked with other profiles that - have - the same illuminant and observer.<br> - <br> + degree observer. Profiles should only be linked with other profiles + that have the same illuminant and observer.<br> <br> <br> <a name="n"></a>The <span style="font-weight: bold;">-n</span> flag - disables the output of the spectral values. If just the XYZ and - L*a*b* - values are needed, this makes for a smaller, easier to read file.<br> + disables the output of the spectral values. If just the XYZ and D50 + L*a*b* values are needed, this makes for a smaller, easier to read + file.<br> <br> <a name="p"></a>The <span style="font-weight: bold;">-p</span> flag causes each spectrum to be plotted. If FWA compensation is used, - then - the before/after compensation spectrums will be shown.<br> + then the before/after compensation spectruma will be shown.<br> <br> <br> <br> diff --git a/doc/spotread.html b/doc/spotread.html index aaac0a1..f3964f5 100644 --- a/doc/spotread.html +++ b/doc/spotread.html @@ -3,14 +3,18 @@ <head> <title>spotread</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> <h2><b>spectro/spotread</b></h2> <h3>Summary</h3> Use an instrument to read a single color value. This can be a useful - diagnostic aid. + diagnostic aid.<br> + <br> + [ A commercial tool that does much of what spotread does and more, + is the <a href="http://www.argyllpro.com.au/">ArgyllPRO ColorMeter</a>. + ]<br> <h3>Usage Summary</h3> <small><span style="font-family: monospace;">spotread [-options] [logfile]</span><br style="font-family: monospace;"> @@ -34,6 +38,14 @@ + + + + + + + + Verbose mode</span><br style="font-family: monospace;"> <span style="font-family: monospace;"></span><span @@ -58,6 +70,14 @@ + + + + + + + + Print spectrum for each reading.</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"></span><span @@ -87,6 +107,14 @@ + + + + + + + + Set COM port, 1..4 (default 1)</span><span style="font-family: monospace;"></span><span style="font-family: monospace;"><br style="font-family: monospace;"> @@ -110,6 +138,14 @@ + + + + + + + + Use transmission measurement mode</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style=" @@ -133,6 +169,14 @@ + + + + + + + + Use emissive measurement mode (absolute results)<br> </span></small><small><span style="font-family: monospace;"> </span><a style=" font-family: monospace;" href="#eb">-eb</a><span @@ -155,11 +199,27 @@ + + + + + + + + Use display white brightness relative measurement mode<br> </span></small><small><span style="font-family: monospace;"> </span><a style=" font-family: monospace;" href="#ew">-ew</a><span style="font-family: monospace;"> + + + + + + + + Use display white point relative chromatically adjusted mode<br> </span></small><small><span style="font-family: monospace;"> </span><a style=" font-family: monospace;" href="#p">-p</a><span @@ -182,6 +242,14 @@ + + + + + + + + Use telephoto measurement mode (absolute results)<br> </span></small><small><span style="font-family: monospace;"> </span><a style=" font-family: monospace;" href="#pb">-pb</a><span @@ -204,6 +272,14 @@ + + + + + + + + Use </span></small><small><span style="font-family: monospace;">projector</span></small><small><span style="font-family: monospace;"> white brightness relative measurement mode<br> @@ -228,6 +304,14 @@ + + + + + + + + Use </span></small><small><span style="font-family: monospace;">projector</span></small><small><span style="font-family: monospace;"> </span></small><small><span style="font-family: monospace;">white point relative @@ -253,6 +337,14 @@ + + + + + + + + Use ambient measurement mode (absolute results)<br> <a href="#f">-f</a> @@ -272,6 +364,14 @@ + + + + + + + + Use ambient flash measurement mode (absolute results)<br> </span></small><font size="-1"><span style="font-family: monospace;"> <a href="#y">-y X</a> @@ -293,6 +393,14 @@ + + + + + + + + Display type - instrument specific list to choose from.</span></font><br> <small><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="spotread.html#I">-I illum</a><span @@ -312,6 +420,14 @@ M0, + + + + + + + + M1, M2, A, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"></span><span @@ -319,7 +435,7 @@ M0, style="font-family: monospace;" href="#i">-i illum</a><span style="font-family: monospace;"> Choose illuminant for computation of - CIE XYZ from spectral data & FWA:</span><br + CIE XYZ from spectral reflectance & FWA:</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -348,6 +464,14 @@ D50 + + + + + + + + D50M2, D65, F5, F8, F10 or file.sp</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style=" @@ -374,6 +498,14 @@ D50 + + + + + + + + </span></small><small><span style="font-family: monospace;">1931_2 </span></small><small><span style="font-family: monospace;"> (def.)</span></small><small><span @@ -399,6 +531,14 @@ D50 + + + + + + + + Set filter configuration:<br> n @@ -419,6 +559,14 @@ D50 + + + + + + + + None<br> p @@ -439,6 +587,14 @@ D50 + + + + + + + + Polarising filter<br> 6 @@ -459,6 +615,14 @@ D50 + + + + + + + + D65<br> u @@ -479,6 +643,14 @@ D50 + + + + + + + + U.V. Cut<br> <a href="#E">-E extrafilterfile</a> Apply extra filter compensation file<br> @@ -502,6 +674,14 @@ D50 + + + + + + + + Display Yxy instead of Lab<br> </span></font><font size="-1"><span style="font-family: monospace;"> <a href="#h">-h</a> @@ -523,6 +703,14 @@ D50 + + + + + + + + Display LCh instead of Lab</span></font><br> <font size="-1"><span style="font-family: monospace;"> <a href="#V">-V</a> @@ -544,6 +732,14 @@ D50 + + + + + + + + Show running average and std. devation from ref.</span></font><br> <font size="-1"><span style="font-family: monospace;"> <a href="#T">-T</a> @@ -565,6 +761,14 @@ D50 + + + + + + + + Display correlated color temperatures and CRI<br> </span></font><font size="-1"><span style="font-family: monospace;"> <a href="#N">-N</a> @@ -585,7 +789,44 @@ D50 + + + + + + + + Disable initial calibration of instrument if possible</span></font><br> + <font size="-1"><span style="font-family: monospace;"> <a + href="spotread.html#O">-O</a> + + + + + + + + + + + + + + + + + + + + + + + + + + + Do one cal. or measure and exit</span></font><br> <font size="-1"><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#H">-H</a><span style="font-family: monospace;"> @@ -611,6 +852,14 @@ D50 + + + + + + + + Apply Colorimeter Correction Matrix</span></font><br> <span style="font-family: monospace;"> <a href="#X2">-X file.ccss</a> @@ -636,6 +885,14 @@ Samples + + + + + + + + for calibration</span><br> <font size="-1"><span style="font-family: monospace;"> </span><a style=" font-family: monospace;" href="#Yrn">-<font size="-1">Y</font> @@ -650,10 +907,26 @@ Samples + + + + + + + + Override refresh, non-refresh display mode</span></font><br> <tt> <a href="#YR">-Y R:<i>rate</i></a> + + + + + + + + Override measured refresh rate with rate Hz</tt><br> <font size="-1"><span style="font-family: monospace;"> </span><a style=" font-family: monospace;" href="#YA">-<font size="-1">Y </font>A</a><span @@ -688,6 +961,14 @@ none, + + + + + + + + h = HW, x = Xon/Xoff</span></font><br> <small><span style="font-family: monospace;"> </span><a style=" font-family: monospace;" href="#D">-D [level]</a><span @@ -713,6 +994,14 @@ none, + + + + + + + + Optional file to save reading results<br style="font-family: monospace;"> </span></font><small><span style="font-family: monospace;"></span><span @@ -736,6 +1025,64 @@ none, You must strike a key in the plot window to continue with another measurement.<br> <br> + The Graph plots light wavelength on the X axis, and either absolute + or relative level on the Y axis. <br> + <br> + <table cellpadding="0" cellspacing="0" border="1" height="153" + width="200"> + </table> + <table cellpadding="0" cellspacing="0" border="1"> + <tbody> + <tr> + <th valign="top"> Measurement Mode <br> + </th> + <th valign="top">Y Units<br> + </th> + </tr> + <tr> + <td align="center" valign="top">Emission<br> + </td> + <td align="center" valign="top">mW/(m<sup>2</sup>.sr.nm)</td> + </tr> + <tr> + <td align="center" valign="top">Ambient<br> + </td> + <td align="center" valign="top">mW/(m<sup>2</sup>.nm)<br> + </td> + </tr> + <tr> + <td align="center" valign="top">Emission Flash<br> + </td> + <td align="center" valign="top"> mW/(m<sup>2</sup>.sr.nm.s) + + + + + + <br> + </td> + </tr> + <tr> + <td align="center" valign="top">Ambient Flash<br> + </td> + <td align="center" valign="top">mW/(m<sup>2</sup>.nm.s)<br> + </td> + </tr> + <tr> + <td align="center" valign="top">Reflective<br> + </td> + <td align="center" valign="top">%/nm<br> + </td> + </tr> + <tr> + <td align="center" valign="top">Transmissive<br> + </td> + <td align="center" valign="top">%/nm<br> + </td> + </tr> + </tbody> + </table> + <br> <a name="c"></a> The instrument is assumed to communicate through a USB or serial communication port, and the port can be selected with the <b>-c</b> option, if the instrument is not connected to the @@ -833,29 +1180,33 @@ none, and how this works, see <a href="instruments.html">Operation of particular instruments</a>. <b>3)</b> Any installed CCSS files (if applicable), or CCMX files. These files are typically created - using <a href="ccxxmake.html">ccxxmake</a>, - and installed using <a - href="oeminst.html">oeminst</a>. The - default and Base Calibration types will be indicated in the usage.<br> + using <a href="ccxxmake.html">ccxxmake</a>, and installed using <a + href="oeminst.html">oeminst</a>. The default and Base Calibration + types will be indicated in the usage.<br> <br> <a name="I"></a>The <b>-I</b> parameter allows specifying a - standard or custom illumination spectrum to be used as the similated - instrument illuminant when FWA compensation is used during - measurement, overriding the default <b>D50</b> or CIE computation - illuminant used for FWA (see <b>-i</b> below<b>). </b>See <a - href="colprof.html#f">colprof -f</a> for a fuller explanation. <br> + standard or custom illumination spectrum to be used as the simulated + reflectance instrument illuminant when FWA compensation is used + during <u>measurement</u>, overriding the default <b>D50</b> or + CIE computation illuminant used for FWA (see <b>-i</b> below<b>). </b>If + + using <b>M0</b>, <b>M1</b> or <b>M2</b>, then the <b>-i</b> + option is <b>not</b> normally used. See <a href="colprof.html#f">colprof + + -f</a> for a fuller explanation. <br> <br> <a name="i"></a>The <b>-i</b> parameter allows specifying a - standard or custom illumination spectrum applied to <span + standard or custom reflectance illumination spectrum applied to <span style="text-decoration: underline;">reflective</span> or <u>transmissive</u> - spectral data to compute CIE tristimulus values. <b>A</b>, <b>D50</b>, - <b>D50M2, D65</b>, <b>F5</b>, <b>F8</b>, <b>F10</b> are a - selection of standard illuminant spectrums, with <b>D50</b> being - the default. If a filename is specified instead, it will be assumed - to be an Argyll specific <a href="File_Formats.html#.sp">.sp</a> - spectrum file. If FWA compensation is used during measurement, this - illuminant will be used by default as the simulated instrument - illuminant.<br> + spectral data to <u>compute</u> CIE tristimulus values. <b>A</b>, + <b>D50</b>, <b>D50M2, D65</b>, <b>F5</b>, <b>F8</b>, <b>F10</b> + are a selection of standard illuminant spectrums, with <b>D50</b> + being the default. If using <b>-I M0</b>, <b>M1</b> or <b>M2</b>, + then this <b>-i</b> option is <b>not</b> normally used. If a + filename is specified instead, it will be assumed to be an Argyll + specific <a href="File_Formats.html#.sp">.sp</a> spectrum file. If + FWA compensation is used during measurement, this illuminant will be + used by default as the simulated instrument illuminant.<br> <br> <a name="Q"></a> The <b>-Q</b> flag allows specifying a tristimulus observer, and is used to compute PCS (Profile Connection Space) @@ -930,6 +1281,11 @@ none, computer. It is advisable to only use this option on the second and subsequent measurements in a single session.<br> <br> + <a name="O"></a><b>-O</b> Do a calibration or a single measurement + and exit. To take a measurement with an instrument that always does + a calibration first, calibrate it and then use -O with -N. The -O + option is intended to simplify scripted use of spotread.<br> + <br> <a name="H"></a> The -<span style="font-weight: bold;">H</span> option turns on high resolution spectral mode, if the instrument supports it. See <a href="instruments.html">Operation of particular @@ -970,6 +1326,14 @@ a + + + + + + + + colorimeters accuracy for a particular type of display.<br> <br> <a name="Yrn"></a> The -<span style="font-weight: bold;">Y r </span>and @@ -982,6 +1346,14 @@ a + + + + + + + + <b>-Y n</b> options overrides the refresh display mode set by the <a href="#y">-y display type selection</a>, with <b>-Y</b><span style="font-weight: bold;"> r</span> forcing refresh display mode, @@ -997,12 +1369,12 @@ a <br> <a name="YA"></a> The -<span style="font-weight: bold;">Y A</span> option uses a non-adaptive integration time emission measurement - mode, if the instrument supports it, such as the Eye-One Pro or - ColorMunki. By default an adaptive integration time measurement mode - will be used for emission measurements, but some instruments support - a fixed integration time mode that can be used with display devices. - This may give increased consistency and faster measurement times, - but may also give less accurate low level readings.<br> + mode, if the instrument supports it, such as the Eye-One Pro, + ColorMunki, i1d3 or K10. By default an adaptive integration time + measurement mode will be used for emission measurements, but some + instruments support a fixed integration time mode that can be used + with display devices. This may give faster measurement times, but + may also give less accurate low level readings.<br> <br> <a name="W"></a>The <b>-W</b> <span style="font-weight: bold;">n|h|x</span> parameter overrides the default serial communications flow control @@ -1041,9 +1413,13 @@ a the range 0 .. 100 for reflective or transmissive readings, and absolute cd/m^2 for display, emissive and ambient readings.<br> <br> - The L*a*b* values are computed relative to a D50 100 scale white - point. (Note that using display white relative mode makes the L*a*b - relative to the display white point.)<br> + By default the L*a*b* values are computed relative to a fixed D50 + 100 scale white point, so values for emissive sources are not + particularly useful.<br> + Using the display white relative mode uses a Bradford chromatic + transform to transform from the measured white to a D50 white (the + same as ArgyllCMS ICC profile deals a display white), and then + computes the D50 L*a*b from that.<br> <br> If Fluorescent Whiter Additive (FWA) compensated readings are to be made, then this needs to be enabled with the correct command line diff --git a/doc/targen.html b/doc/targen.html index ee12f27..3aa1bb4 100644 --- a/doc/targen.html +++ b/doc/targen.html @@ -41,6 +41,8 @@ + + 0: Print grey</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -56,6 +58,8 @@ + + 1: Video grey</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -72,6 +76,8 @@ + + 2: Print RGB</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -95,6 +101,8 @@ + + 5: CMY<br style="font-family: monospace;"> </span><span style="font-family: monospace;"> @@ -115,6 +123,8 @@ + + 7: CMYK + Light CMK</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -139,6 +149,8 @@ Red + + + Blue</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -168,6 +180,8 @@ Red + + 12: CMYK + Light CM + Medium CM</span><br style="font-family: monospace;"> @@ -190,6 +204,8 @@ Red + + 0: Additive</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -218,6 +234,8 @@ Red + + 4: Black</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -234,6 +252,8 @@ Red + + 5: Orange</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -251,6 +271,8 @@ Red + + 6: Red</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -267,6 +289,8 @@ Red + + 7: Green</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -283,6 +307,8 @@ Red + + 8: Blue</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -299,6 +325,8 @@ Red + + 9: White</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -315,6 +343,8 @@ Red + + 10: Light Cyan</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -331,6 +361,8 @@ Red + + 11: Light Magenta</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -347,6 +379,8 @@ Red + + 12: Light Yellow</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -362,6 +396,8 @@ Red + + 13: Light Black</span><br style="font-family: monospace;"> @@ -380,6 +416,8 @@ Red + + 14: Medium Cyan</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -396,6 +434,8 @@ Red + + 15: Medium Magenta</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -412,6 +452,8 @@ Red + + 16: Medium Yellow</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -427,6 +469,8 @@ Red + + 17: Medium Black</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -443,6 +487,8 @@ Red + + 18: Light Light Black<br> <a href="#G">-G</a> @@ -459,6 +505,8 @@ Red + + Generate good optimzed points rather than Fast<br style="font-family: monospace;"> </span><span style="font-family: monospace;"> </span><a @@ -484,6 +532,8 @@ Red + + steps</a><span style="font-family: monospace;"> @@ -498,6 +548,8 @@ Red + + Single channel steps (default 0)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -523,6 +575,8 @@ steps + + 0)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#m">-m steps</a><span @@ -540,6 +594,8 @@ steps + + Multidimensional device space cube steps (default 0)</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"><small><span @@ -558,6 +614,8 @@ steps + + Multidimensional body centered cubic steps (default 0)<br> </span></small></span> <span style="font-family: monospace;"></span><a style="font-family: monospace;" href="#f">-f @@ -573,6 +631,8 @@ steps + + patches</a><span style="font-family: monospace;"> @@ -587,6 +647,8 @@ steps + + Add iterative & adaptive full spread patches to total (default 836)<br> @@ -603,6 +665,8 @@ steps + + Default is Optimised Farthest Point Sampling (OFPS)<br style="font-family: monospace;"> </span><span style="font-family: monospace;"> </span><a @@ -628,6 +692,8 @@ for + + full spread</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#r">-r</a><span @@ -652,6 +718,8 @@ for + + full spread</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#R">-R</a><span @@ -676,6 +744,8 @@ for + + full spread</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#q">-q</a><span @@ -700,6 +770,8 @@ for + + full spread<br> </span></small><small><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#Q">-Q</a><span @@ -731,6 +803,8 @@ centered + + cubic grid for full spread</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -756,6 +830,8 @@ centered + + cubic grid for full spread</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -781,6 +857,8 @@ for + + B.C.C. grid, default 0.333300</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -811,6 +889,8 @@ spread + + (default iterative)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#l">-l ilimit</a><span @@ -830,6 +910,8 @@ ink + + limit in %(default = none, or estimated from profile)<br> </span></small><small><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#p">-p power</a><span @@ -854,6 +936,8 @@ device + + values.</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"></span><span style="font-family: monospace;"> </span><a @@ -881,9 +965,13 @@ device - Filter out samples outside Lab sphere.</span><br - style="font-family: monospace;"> - <span style="font-family: monospace;"> </span><a + + + Filter out samples outside Lab sphere.<br> + <a href="#O">-O</a> + Don't re-order display RGB patches for minimum delay<br + style="font-family: monospace;"> + </span> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#w">-w</a><span style="font-family: monospace;"> @@ -899,12 +987,14 @@ device - Dump diagnostic outfile.wrl file (Lab locations)<br> + + + Dump diagnostic outfile.x3d.html file (Lab locations)<br> </span></small><small><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#W">-W</a><span style="font-family: monospace;"> - Dump diagnostic outfile.wrl file (Device locations)</span></small><br + Dump diagnostic outfile.x3d.html file (Device locations)</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"></span><span style="font-family: monospace;"> </span><a @@ -923,6 +1013,8 @@ device + + Base name for output(.ti1)</span></small> <br> <h3>Usage Details and Discussion<br> </h3> @@ -997,6 +1089,8 @@ device + + 5</span> will generate steps at 0.0 0.25 0.5 0.75 and 1.0, while the option <span style="font-weight: bold;">-s 5 -p 2.0</span> will generate steps at 0.0 0.0625 0.25 0.5625 and 1.0. By default, no per @@ -1057,6 +1151,8 @@ device + + <b>-b</b> flags, is not to duplicate test values already created by a previous type.<br> <br> @@ -1236,6 +1332,8 @@ device + + steps</a></small></small> patches.<br> <br> <a name="F"></a> The <b>-F</b> flag and parameters is used to @@ -1253,8 +1351,16 @@ device methods are used, then the target number of points will be achieved. For this reason, the -f N -q method is probably the easiest to use.<br> <br> + <a name="O"></a> The <b>-O</b> flag disables the normal patch + re-ordering used for display RGB sets. Displays are assumed to have + a "settling time", and the delay needed for this settling time can + be minimzed by sort the patches so that they are in an order which + minimizes the change in levels between patches. <b>-O</b> disables + this re-ordering, leaving the patches in whatever order they were + generated.<br> + <br> <a name="w"></a> The <b>-w</b> flag causes a diagnostic <a - href="File_Formats.html#VRML">VRML</a> .wrl file to be created, in + href="File_Formats.html#X3DOM">X3DOM</a> .x3d.html file to be created, in which the test points are plotted as small spheres in L*a*b* colorspace. Note that for a CMYK device, the point spacing may seem strange, since the extra K dimension is compressed into the 3 @@ -1274,6 +1380,11 @@ device number of rows, and then adjusting the total number of patches to fill the last row or paper size, in a trial and error fashion.<br> <br> + Note that some people create charts with larger numbers of patches + for the ColorMunki by altering an Eye-One Pro chart, and making + scanning jigs to guide the instrument more accurately. This may + reduce patch reading accuracy unless suitable care is taken.<br> + <br> <a name="Table"></a> Size (mm/Standard Name), No. Patches<br> <br> diff --git a/doc/tiffgamut.html b/doc/tiffgamut.html index 5b67603..6aea52d 100644 --- a/doc/tiffgamut.html +++ b/doc/tiffgamut.html @@ -3,19 +3,19 @@ <head> <title>tiffgamut</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> <h2><b>xicc/tiffgamut</b></h2> <h3>Summary</h3> - Create a gamut file or VRML file of the color gamut of the contents + Create a gamut file or X3DOM file of the color gamut of the contents of a set of TIFF or JPEG image.<br> <br> <span style="font-weight: bold;">tiffgamut</span> allows creation of gamut files from the pixel values in a set of TIFF and/or JPEG raster images, as defined by an ICC profile, in L*a*b* or CIECAM02 - Jab colorspace, and can also represent the gamut as a VRML file. + Jab colorspace, and can also represent the gamut as a X3DOM file. This can be used for visualizing and comparing the gamut of an image to the colorspace it is in, or a colorspace it might get transformed into, and can also be used to create an image source gamut for use @@ -29,7 +29,12 @@ intent for appearance space gamut mappings, and the same input viewing conditions to be used in <span style="font-weight: bold;">collink</span> or <span style="font-weight: bold;">colprof</span> using the -c - flag, i.e. "tiffgamut -pj -cmt sRGB.icm image.tif"<br> + flag, i.e. "tiffgamut -pj -cmt sRGB.icm image.tif" See <a + href="Scenarios.html#LP3">Image dependent gamut mapping using + device links</a> for an example workflow.<br> + <br> + See <a href="file:///D:/src/argyll/doc/3Df.htmlormat">3D Viewing + Format</a> for switching to VRML or X3D output format.<br> <h3>Usage Summary</h3> <small><span style="font-family: monospace;">tiffgamut [-v level] [profile.icm | embedded.tif/jpg] infile1.tif/jpg @@ -37,6 +42,8 @@ <span style="font-family: monospace;"> -v + + Verbose</span><br style="font-family: monospace;"> <span style="font-family: monospace;">-d sres Surface resolution @@ -45,18 +52,24 @@ emit - VRML .wrl file as well as CGATS .gam file</span><br + + + X3DOM .x3d.html file as well as CGATS .gam file</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -n Don't - add VRML axes or white/black point</span><br style="font-family: - monospace;"> + + + add X3DOM axes or white/black point</span><br + style="font-family: monospace;"> <span style="font-family: monospace;"> -k Add + + markers for prim. & sec. "cusp" points<br> -f perc Filter by popularity, perc = percent to use<br style="font-family: @@ -68,6 +81,8 @@ Add s + + = saturation, a = absolute (default), d = profile default</span></small><small><span style="font-family: monospace;"></span></small><br style="font-family: monospace;"> @@ -80,6 +95,8 @@ s r + + = reverse (priority: monochrome > matrix > lut)<br> </span></small><small><span style="font-family: monospace;"> </span><span style="font-family: monospace;">-p oride</span><span @@ -96,6 +113,8 @@ r either + + an enumerated choice, or a parameter:value change</span><span style="font-family: monospace;"></span><br style="font-family: monospace;"> @@ -107,11 +126,15 @@ either + + pe - Print evaluation environment (CIE 116-1995)<br> </span></small><small><span style="font-family: monospace;"> + + pc - Critical print evaluation environment (ISO-3664 P1)</span></small><small><span style="font-family: monospace;"></span><span style="font-family: monospace;"></span><br style="font-family: monospace;"> @@ -122,6 +145,8 @@ either + + mb - Monitor in bright work environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -146,36 +171,48 @@ either s:surround + + n = auto, a = average, m = dim, d = dark,</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> + + c = transparency (default average)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> w:X:Y:Z + + Adapted white point as XYZ (default media white)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> w:x:y + + Adapted white point as x, y</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> a:adaptation + + Adaptation luminance in cd.m^2 (default 50.0)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> b:background + + Background % of image luminance (default 20)<br> l:imagewhite Image white in cd.m^2 if surround = auto (default 250)</span></small><br @@ -185,6 +222,8 @@ b:background f:flare + + Flare light % of image luminance (default 1)<br> </span></small> </span><span style="font-family: monospace;"> @@ -196,6 +235,8 @@ f:flare monospace;"> <span style="font-family: monospace;"> + + g:x:y Glare color as x, y<br> -O outputfile Override the default output filename & @@ -211,11 +252,11 @@ f:flare and is a good place to start. Small values may take a lot of time to generate, and will produce big files.<br> <br> - The <b>-w</b> flag causes a VRML file to be produced, as well as a + The <b>-w</b> flag causes a X3DOM file to be produced, as well as a gamut file.<br> <br> The <b>-n</b> flag suppresses the L*a*b* axes being created in the - VRML.<br> + X3DOM.<br> <br> The <span style="font-weight: bold;">-k</span> flag adds markers for each of the primary and secondary "cusp" points (Red, Yellow, diff --git a/doc/txt2ti3.html b/doc/txt2ti3.html index 5d021fc..0fc467d 100644 --- a/doc/txt2ti3.html +++ b/doc/txt2ti3.html @@ -3,17 +3,15 @@ <head> <title>txt2ti3</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> <h2><b>profile/txt2ti3</b></h2> <h3>Summary</h3> - <small><big>Convert - Gretag/Logo/X-Rite or other CGATS format RGB or CMYK test chart - results - into</big></small> Argyll <a href="File_Formats.html#.ti3">.ti3</a> - CGATS + <small><big>Convert Gretag/Logo/X-Rite/Barbieri or other CGATS + format RGB or CMYK test chart results into</big></small> + Argyll <a href="File_Formats.html#.ti3">.ti3</a> CGATS format. <h3>Usage Summary</h3> <small><span style="font-family: monospace;">txt2ti3 [-v] [-l limit] @@ -21,91 +19,83 @@ style="font-family: monospace;"> <br style="font-family: monospace;"> <span style="font-family: monospace;">-2<span style="font-style: - italic;"> </span> - create a dummy .ti2 file as well.<br> + italic;"> </span> + create a dummy .ti2 file as well.<br> </span></small><small><span style="font-family: monospace;">-l </span><i style="font-family: monospace;">limit</i><span style="font-family: monospace;"> - set ink - limit, 0 - - - 400% (default max in file)<br> + set ink limit, 0 - 400% (default max in file)<br> -d Set + type of device as Display, not Output<br> -i Set + type of device as Input, not Output<br style="font-family: monospace;"> </span></small><small><span style="font-family: monospace;"></span><i style="font-family: monospace;">[devfile]</i><span style="font-family: monospace;"> Input - Device - CMYK - target file (typically file.txt)</span><br style="font-family: - monospace;"> + Device CMYK target file (typically file.txt)</span><br + style="font-family: monospace;"> <i style="font-family: monospace;">infile </i><span style="font-family: monospace;"> Input CIE, + Spectral or Device & Spectral file (typically file.txt)</span><br style="font-family: monospace;"> <i style="font-family: monospace;">[specfile]</i><span style="font-family: monospace;"> Input - Spectral - file (typically file.txt)</span><br style="font-family: + Spectral file (typically file.txt)</span><br style="font-family: monospace;"> <i style="font-family: monospace;">outbasefile</i><span style="font-family: monospace;"> Base name for output</span><a style="font-family: monospace;" href="File_Formats.html#.ti3">.ti3</a><span style="font-family: - monospace;"> and <a href="File_Formats.html#.ti2">.ti2</a> - file</span></small> + monospace;"> and <a href="File_Formats.html#.ti2">.ti2</a> file</span></small> <br> <h3>Usage Details and Discussion</h3> - txt2ti3 takes the Gretag/Logo/X-Rite/etc. test chart - results, and converts them - into Argyll <a href="File_Formats.html#.ti3">.ti3</a> CGATS - files.<br> + txt2ti3 takes the Gretag/Logo/X-Rite/Barbieri/etc. test chart + results, and converts them into Argyll <a + href="File_Formats.html#.ti3">.ti3</a> CGATS files.<br> It is quite common to find profile test chart data from various standards bodies and industry organizations in one of these formats, - so it is - useful to be able to convert them for use with Argyll. ICC profiles - created using Gretag Profile Maker also commonly contain the test - chart - results embedded in the profile, inside an ICC tag.<br> + so it is useful to be able to convert them for use with Argyll. ICC + profiles created using Gretag Profile Maker also commonly contain + the test chart results embedded in the profile, inside an ICC tag.<br> <br> - A variety of different packaging of Gretag/Logo data can be - accepted: <br> + A variety of different packaging of Gretag/Logo/X-Rite/Barbieri data + can be accepted: <br> <br> 1 source files, consisting of a combined device value and CIE and/or spectral values.<br> 2 source files, consisting of a file containing the device values, and a file containing the CIE and/or spectral values.<br> 2 source files, consisting of a file containing the device values - and - the CIE values, and a file containing the spectral values.<br> + and the CIE values, and a file containing the spectral values.<br> 3 source files, consisting of a file containing the device values, a file containing the CIE values, and a file containing the spectral values.<br> <br> X-Rite ColorPort seems to produce a single source file containing - combined device value and CIE - and/or spectral values.<br> + combined device value and CIE and/or spectral values.<br> <br> The Gretag/Logo test chart results format seem to change with each minor release of Profile Maker, so this tool may not work in all cases.<br> <br> + Use the Barbieri .CIE file<br> + <br> The <span style="font-style: italic;">outbasefile</span> is the - base - of the output file(s), to which txt2ti3 will automatically append a - .ti3 and .ti2 extension.<br> + base of the output file(s), to which txt2ti3 will automatically + append a .ti3 and .ti2 extension.<br> <br> The input files may have data that is scaled to one of three levels: 1.0, 100.0 or 255.0, and txt2ti3 attempts to guess what the - appropriate - range is, in order to scale to Argyll's standard range 0 .. 100.0.<br> + appropriate range is, in order to scale to Argyll's standard range 0 + .. 100.0.<br> <br> <br> </body> diff --git a/doc/viewgam.html b/doc/viewgam.html index 0bf5c04..9c3e3f0 100644 --- a/doc/viewgam.html +++ b/doc/viewgam.html @@ -1,125 +1,146 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> -<head> - <title>viewgam</title> - <meta http-equiv="content-type" - content="text/html; charset=ISO-8859-1"> - <meta name="author" content="Graeme Gill"> -</head> -<body> -<h2><b>gamut/viewgam</b></h2> -<h3>Summary</h3> -Convert one or more gamuts into a <a href="File_Formats.html#VRML">VRML</a> -3D visualization -file. This allows visual comparison of several gamut surfaces.<br> -Also allows creating the intersection (overlap) between two gamuts. -This is useful in measuring and visualizing the coverage of one gamut -of another.<br> -<h3>Usage<br> -</h3> -<small><span style="font-family: monospace;">viewgam { [-c color] [-t -trans] [-w|s] </span><span - style="font-style: italic; font-family: monospace;">infile.gam</span><span - style="font-family: monospace;"> } ... </span><span - style="font-style: italic; font-family: monospace;">outfile.wrl</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> -For each input gamut file:</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> -c </span><i - style="font-family: monospace;">color</i><span - style="font-family: monospace;"> + <head> + <title>viewgam</title> + <meta http-equiv="content-type" content="text/html; + charset=windows-1252"> + <meta name="author" content="Graeme Gill"> + </head> + <body> + <h2><b>gamut/viewgam</b></h2> + <h3>Summary</h3> + Convert one or more gamuts into a <a + href="File_Formats.html#X3DOM">X3DOM</a> 3D visualization file. + This allows visual comparison of several gamut surfaces.<br> + Also allows creating the intersection (overlap) between two gamuts. + This is useful in measuring and visualizing the coverage of one + gamut of another.<br> + <br> + See <a href="3Df.htmlormat">3D Viewing Format</a> for switching to + VRML or X3D output format.<br> + <h3>Usage<br> + </h3> + <small><span style="font-family: monospace;">viewgam { [-c color] + [-t trans] [-w|s] </span><span style="font-style: italic; + font-family: monospace;">infile.gam</span><span + style="font-family: monospace;"> } ... </span><span + style="font-style: italic; font-family: monospace;">outfile.x3d.html</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> +For + + + each input gamut file:</span><br style="font-family: monospace;"> + <span style="font-family: monospace;"> -c </span><i + style="font-family: monospace;">color</i><span + style="font-family: monospace;"> Color to -make gamut, -r = red, g = green, b = blue</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> +make + + + gamut, r = red, g = green, b = blue</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> -c = cyan, m = magenta, y = yellow, w = white</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> -n = natural color</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> -t </span><i - style="font-family: monospace;">trans</i><span - style="font-family: monospace;"> +c + + + = cyan, m = magenta, y = yellow, w = white</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> +n + + + = natural color</span><br style="font-family: monospace;"> + <span style="font-family: monospace;"> -t </span><i + style="font-family: monospace;">trans</i><span + style="font-family: monospace;"> Set transparency -from 0.0 (opaque) to 1.0 (invisible)</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> -w -Show as a wireframe</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> -s -Show as a solid surface</span><br style="font-family: monospace;"> -<i style="font-family: monospace;"> infile.gam</i><span - style="font-family: monospace;"> Name -of </span><i style="font-family: monospace;">infile</i><a - style="font-family: monospace;" href="File_Formats.html#.gam">.gam</a><span - style="font-family: monospace;"> file</span><br - style="font-family: monospace;"> -<br style="font-family: monospace;"> -<span style="font-family: monospace;"> -n -Don't add Lab axes<br> - -i Compute -and print intersecting volume of first 2 gamuts<br> - -I isect.gam Same as -i, but save intersection gamut -to isect.gam<br style="font-family: monospace;"> -</span><span style="font-family: monospace;"> </span><i - style="font-family: monospace;">outfile.wrl</i><span - style="font-family: monospace;"> Name of output -</span><i style="font-family: monospace;">outfile.wrl</i><span - style="font-family: monospace;"> file</span></small> -<br> -<h3>Usage Details and Discussion</h3> -<b>viewgam</b> creates a VRML file that allows the viewing and -comparing -of multiple gamut files by representing them as solid surfaces, -wireframes, -etc. It takes as input a list of gamut files, each file preceded by any -options that are to apply to the display of that particular -gamut. -<br> -<br> -The options that can be specified for each input gamut are:<br> -<br> -<b>-c</b> <i>color</i> allows the color of the surface or wireframe to -be -specified. Any of a number of predefined colors (red, green, blue, -cyan, -magenta, yellow, white) can be used, as well as allowing the color to -reflect -the natural color of that point in the colorspace.<br> -<br> -<b>-t</b> <i>trans</i> allows the transparency of the surface to -be -specified. A value of 0.2 might be a good place to start. Using -transparency -generally leads to a slower display than the default opaque surface -treatment, but can make it possible to see within a solid gamut surface.<br> -<br> -<b>-w</b> forces the gamut surface to be rendered as a wireframe.<br> -<br> -<b>-s</b> forces the gamut surface to be rendered as a solid surface.<br> -<br> -By default, the first gamut is treated as a solid with natural -coloring, -with the second and subsequent gamuts being wireframes with colors of -white, -red, cyan, yellow, green and blue, with decreasing visibility.<br> -<br> -The <b>-n</b> flag turns off display of the default L*a*b* axes in the -output.<br> -<br> -The <span style="font-weight: bold;">-i</span> flag computes the -intersecting volume of the first two gamuts (in cubic color units, -usually L*a*b*), as well as the volumes of the two gamuts and the -percentage the intersection is of the two gamuts. This is a useful -measure of the coverage one gamut has of another. If <span - style="font-weight: bold;">-I</span> is used, then as well as printing -the volume, the intersecting gamut will be saved to the <span - style="font-style: italic;">isect.gam</span> file.<br> -<br> -The final argument is the name of the VRML file to save the resulting -composite -3D visualization file to.<br> -<br> -</body> +from + + + 0.0 (opaque) to 1.0 (invisible)</span><br style="font-family: + monospace;"> + <span style="font-family: monospace;"> -w +Show + + + as a wireframe</span><br style="font-family: monospace;"> + <span style="font-family: monospace;"> -s +Show + + + as a solid surface</span><br style="font-family: monospace;"> + <i style="font-family: monospace;"> infile.gam</i><span + style="font-family: monospace;"> + Name of </span><i style="font-family: monospace;">infile</i><a + style="font-family: monospace;" href="File_Formats.html#.gam">.gam</a><span + style="font-family: monospace;"> file</span><br + style="font-family: monospace;"> + <br style="font-family: monospace;"> + <span style="font-family: monospace;"> -n +Don't + + + add Lab axes<br> + -i Compute and + print intersecting volume of first 2 gamuts<br> + -I isect.gam Same as -i, but save intersection + gamut to isect.gam<br style="font-family: monospace;"> + </span><span style="font-family: monospace;"> </span><i + style="font-family: monospace;">outfile </i><span + style="font-family: monospace;"><i> </i>Base + + name of output </span><i style="font-family: monospace;">outfile.x3d.html</i><span + style="font-family: monospace;"> file</span></small> <br> + <h3>Usage Details and Discussion</h3> + <b>viewgam</b> creates a X3DOM file that allows the viewing + and comparing of multiple gamut files by representing them as solid + surfaces, wireframes, etc. It takes as input a list of gamut files, + each file preceded by any options that are to apply to the display + of that particular gamut. <br> + <br> + The options that can be specified for each input gamut are:<br> + <br> + <b>-c</b> <i>color</i> allows the color of the surface or wireframe + to be specified. Any of a number of predefined colors (red, green, + blue, cyan, magenta, yellow, white) can be used, as well as allowing + the color to reflect the natural color of that point in the + colorspace.<br> + <br> + <b>-t</b> <i>trans</i> allows the transparency of the surface + to be specified. A value of 0.2 might be a good place to start. + Using transparency generally leads to a slower display than the + default opaque surface treatment, but can make it possible to see + within a solid gamut surface.<br> + <br> + <b>-w</b> forces the gamut surface to be rendered as a wireframe.<br> + <br> + <b>-s</b> forces the gamut surface to be rendered as a solid + surface.<br> + <br> + By default, the first gamut is treated as a solid with natural + coloring, with the second and subsequent gamuts being wireframes + with colors of white, red, cyan, yellow, green and blue, with + decreasing visibility.<br> + <br> + The <b>-n</b> flag turns off display of the default L*a*b* axes in + the output.<br> + <br> + The <span style="font-weight: bold;">-i</span> flag computes the + intersecting volume of the first two gamuts (in cubic color units, + usually L*a*b*), as well as the volumes of the two gamuts and the + percentage the intersection is of the two gamuts. This is a useful + measure of the coverage one gamut has of another. If <span + style="font-weight: bold;">-I</span> is used, then as well as + printing the volume, the intersecting gamut will be saved to the <span + style="font-style: italic;">isect.gam</span> file.<br> + <br> + The final argument is the base name of the X3DOM file to save the + resulting composite 3D visualization file to. If the name given + doesn't have an extension, one will be automatically added.<br> + <br> + </body> </html> |
