diff options
Diffstat (limited to 'doc')
41 files changed, 17525 insertions, 8037 deletions
diff --git a/doc/ArgyllDoc.html b/doc/ArgyllDoc.html index 498e974..98e730d 100644 --- a/doc/ArgyllDoc.html +++ b/doc/ArgyllDoc.html @@ -1,119 +1,140 @@ -<!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 name="author" content="Graeme Gill"> - <meta name="description" content="Root of Argyll CMS documentation"> - <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I) - [Netscape]"> - <title>Argyll Documentation Top</title> - </head> - <body> - <h1> Argyll CMS documentation index (V1.5.1)<br> - </h1> - Date: 8th March 2013<br> - Author: Graeme Gill - <h2><u><a name="Intro"></a>Introduction</u></h2> - ArgyllCMS is an ICC compatible color management system, available as - Open Source. It supports accurate ICC profile creation for scanners, - cameras and film recorders, and calibration and profiling of - displays and RGB & CMYK printers. Spectral sample data is - supported, allowing a selection of illuminants observer types, and - paper fluorescent whitener additive compensation. Profiles can also - incorporate source specific gamut mappings for perceptual and - saturation intents. Gamut mapping and profile linking uses the - CIECAM02 appearance model, a unique gamut mapping algorithm, and a - wide selection of rendering intents. Device Link can be created with - a wide variety of advanced options. 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.5.1, a bug fix and feature update to V1.5.0 - released on 1st March 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> - <p>The latest source code is available from <a - href="http://www.argyllcms.com/">here</a>.<br> - </p> - <h2><a href="ColorManagement.html">An Introduction to Color - Management</a></h2> - A <a href="ColorManagement.html">concise discussion</a> of what - color management is, and why we need it, together with a brief - overview of the ICC profile format.<br> - <h2 style="text-decoration: underline;">Operating Environments</h2> - <h2> </h2> - <p>Argyll is known to compile and run in at least the following - environments: </p> - 1) MSWindows XP system using Microsoft VC++ 6.0 compiler<br> - 2) MSWindows XP system using Microsoft VC++ 8.0 Express compiler + - Platform SDK Feb. 2003<br> - 3) MSWindows XP system using Microsoft VC++ 9.0 Express compiler + - Platform SDK Feb. 2003<br> - 4) MSWindows XP system using the MingW port of the GCC compiler<br> - 5) Linux on Fedora Core 8, 32 bit using gcc <br> - 6) Linux on Fedora Core 8, 64 bit using gcc<br> - 7) Apple OS X 10.3 PPC using GCC<br> - 8) Apple OS X 10.4, 10.5, 10.6 Intel using GCC<br> - 9) Apple OS X10.7 Intel using Clang<br> - 10) PCBSD 9.1 (FreeBSD) [You need to copy the libusb sub directory - from ArgyllCMS V1.4.0]<br> - <br> - Additionally it is also known to run on:<br> - <br> - MSWindows 2000, Vista & Windows 7 32 bit.<br> - MSWindows Vista 64bit, Windows 7 64bit & Windows 8 64 bit.<br> - Linux Ubuntu 7.10<br> - Linux Kubuntu 7.10<br> - Linux Mandriva 2008.0<br> - Linux OpenSuSE 10.3<br> - Linux Whitebox 4.2/2<br> - <p>but may well compile and run correctly in many more than this, - including OS X 10.8. </p> - This is a <span style="font-weight: bold;">command line terminal</span> - only environment. Those unfamiliar with command line environments - should consult an appropriate tutorial for their environment if they - are interested in using this software. See the listing of <a - href="#cltutes">tutorials</a> below.<span style="font-weight: - bold;"></span><br> - <br> - The following color measuring instruments are directly supported:<br> - <br> - X-Rite:<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 name="author" content="Graeme Gill">
+ <meta name="description" content="Root of Argyll CMS documentation">
+ <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I)
+ [Netscape]">
+ <title>Argyll Documentation Top</title>
+ </head>
+ <body>
+ <h1> Argyll CMS documentation index (V1.6.3)<br>
+ </h1>
+ Date: 26th January 2014<br>
+ Author: Graeme Gill
+ <h2><u><a name="Intro"></a>Introduction</u></h2>
+ ArgyllCMS is an ICC compatible color management system, available as
+ Open Source. It supports accurate ICC profile creation for scanners,
+ cameras and film recorders, and calibration and profiling of
+ displays and RGB & CMYK printers. Device Link can be created
+ with a wide variety of advanced options, including specialized Video
+ calibration standards and 3dLuts. Spectral sample data is
+ supported, allowing a selection of illuminants observer types, and
+ paper fluorescent whitener additive compensation. Profiles can also
+ incorporate source specific gamut mappings for perceptual and
+ saturation intents. Gamut mapping and profile linking uses the
+ CIECAM02 appearance model, a unique gamut mapping algorithm, and a
+ 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>
+ <p>The latest source code is available from <a
+ href="http://www.argyllcms.com/">here</a>.<br>
+ </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
+ href="http://www.colorwiki.com/wiki/The_Color_of_Toast">The
+ Color of Toast</a>.<br>
+ </p>
+ I present here a more technical but <a href="ColorManagement.html">concise + + + + + + + + + + + + + + +
+ discussion</a> of what color management is, and why we need it,
+ together with a brief overview of the ICC profile format.<br>
+ <br>
+ <h2 style="text-decoration: underline;">Operating Environments</h2>
+ <h2> </h2>
+ <p>Argyll is known to compile and run in at least the following
+ environments: </p>
+ 1) MSWindows XP system using Microsoft VC++ 6.0 compiler<br>
+ 2) MSWindows XP system using Microsoft VC++ 8.0 Express compiler +
+ Platform SDK Feb. 2003<br>
+ 3) MSWindows XP system using Microsoft VC++ 9.0 Express compiler +
+ Platform SDK Feb. 2003<br>
+ 4) MSWindows XP system using Microsoft VC++ 10.0 Express compiler +
+ Platform SDK Feb. 2003<br>
+ 5) MSWindows XP system using Microsoft VC++ 11.0 Express compiler<br>
+ 6) MSWindows XP system using the MingW port of the GCC compiler<br>
+ 7) Linux on Fedora Core 8, 32 bit using gcc <br>
+ 8) Linux on Fedora Core 8, 64 bit using gcc<br>
+ 9) Apple OS X 10.3 PPC using GCC<br>
+ 10) Apple OS X 10.4, 10.5, 10.6 Intel using GCC<br>
+ 11) Apple OS X10.7 Intel using Clang<br>
+ <br>
+ Additionally it is also known to run on:<br>
+ <br>
+ MSWindows 2000, Vista & Windows 7 32 bit.<br>
+ MSWindows Vista 64bit, Windows 7, 8, 8.1 64 bit.<br>
+ Linux Ubuntu 7.10<br>
+ Linux Kubuntu 7.10<br>
+ Linux Mandriva 2008.0<br>
+ Linux OpenSuSE 10.3<br>
+ Linux Whitebox 4.2/2<br>
+ <p>but may well compile and run correctly in many more than this,
+ including OS X 10.8. </p>
+ This is a <span style="font-weight: bold;">command line terminal</span>
+ only environment. Those unfamiliar with command line environments
+ should consult an appropriate tutorial for their environment if they
+ are interested in using this software. See the listing of <a
+ href="#cltutes">tutorials</a> below.<span style="font-weight:
+ bold;"></span><br>
+ <br>
+ The following color measuring instruments are directly supported:<br>
+ <br>
+ JETI:<br>
+ <br>
+ <a href="instruments.html#specbos">specbos 1211
+ & 1201</a> + + + + + + + + + + + + + + + + + + + +
+ - Tele-Spectro-Radiometer<br>
+ <br>
+ X-Rite:<br>
<a href="instruments.html#DTP20">DTP20 "Pulse"</a> @@ -156,8 +177,29 @@ - - "swipe" type reflective spectrometer, that can be used untethered.<br> - <a href="instruments.html#DTP22">DTP22 Digital + + + + + + + + + + + + + + + + + + + + +
+ - "swipe" type reflective spectrometer, that can be used untethered.<br>
+ <a href="instruments.html#DTP22">DTP22 Digital
Swatchbook</a> @@ -199,7 +241,28 @@ - - spot type reflective spectrometer.<br> + + + + + + + + + + + + + + + + + + + + +
+ - spot type reflective spectrometer.<br>
<a href="instruments.html#DTP41">DTP41</a> @@ -241,9 +304,30 @@ - - spot and strip reading reflective spectrometer.<br> - <a href="instruments.html#DTP41">DTP41T</a> - + + + + + + + + + + + + + + + + + + + + +
+ - spot and strip reading reflective spectrometer.<br>
+ <a href="instruments.html#DTP41">DTP41T</a>
+
@@ -285,7 +369,28 @@ - - spot and strip reading reflective/transmissive spectrometer.<br> + + + + + + + + + + + + + + + + + + + + +
+ - spot and strip reading reflective/transmissive spectrometer.<br>
<a href="instruments.html#dtp51">DTP51</a> @@ -327,7 +432,28 @@ - - strip reading reflective colorimeter.<br> + + + + + + + + + + + + + + + + + + + + +
+ - strip reading reflective colorimeter.<br>
<a href="instruments.html#DTP92">DTP92</a> @@ -369,68 +495,89 @@ - - CRT display colorimeter.<br> - <a href="instruments.html#DTP94">DTP94</a> <font - size="-1">"Optix XR"</font> or "Optix XR2" or "Optix Pro"- display - colorimeter.<br> - <a href="instruments.html#ColorMunki"><span - style="text-decoration: underline;">ColorMunki</span></a> Design - or Photo - - spot and "swipe" reflective/emissive spectrometer (UV cut only).<br> - <a href="instruments.html#i1d"><span - style="text-decoration: underline;">ColorMunki</span></a> Create - or Smile - - display - colorimeter. (Similar to an Eye-One Display 2)<br> - <a href="instruments.html#Huey">Lenovo W</a> - - - - built in laptop Huey display colorimeter.<br> - <a href="instruments.html#i1d3">Eye-One Display - 3</a> - - Xrite i1 DisplayPro and ColorMunki - Display <br> - - - - - [ The OEM - i1Display Pro, NEC SpectraSensor Pro and<br> - - - - Quato Silver Haze 3 OEM i1d3 are also - reported to work.]<br> - <a href="instruments.html#i1p2">Eye-One Pro2</a> - - - spot and - "swipe" reflective/emissive spectrometer.<br> - <br> - Gretag-Macbeth (now X-Rite):<br> - <a href="instruments.html#sl">Spectrolino</a> - - - spot - reflective/emissive spectrometer.<br> - <a href="instruments.html#ss">SpectroScan</a> - - - spot - reflective/emissive, XY table reflective spectrometer .<br> - <a href="instruments.html#ss">SpectroScanT</a> - - - spot - reflective/emissive/transmissive, XY table reflective spectrometer.<br> - <a href="instruments.html#i1p">Eye-One Pro</a> "EFI - ES-1000" - spot and "swipe" - reflective/emissive spectrometer.<br> - <a href="instruments.html#i1m">Eye-One Monitor</a> - - - spot and "swipe" emissive - spectrometer.<br> - <a href="instruments.html#i1d">Eye-One Display 1 - or 2 or LT</a> - - display colorimeter.<br> - <a href="instruments.html#i1d">HP DreamColor or - APS</a> + + + + + + + + + + + + + + + + + + + + +
+ - CRT display colorimeter.<br>
+ <a href="instruments.html#DTP94">DTP94</a> <font
+ size="-1">"Optix XR"</font> or "Optix XR2" or "Optix Pro"- display
+ colorimeter.<br>
+ <a href="instruments.html#ColorMunki"><span
+ style="text-decoration: underline;">ColorMunki</span></a> Design
+ or Photo -
+ spot and "swipe" reflective/emissive spectrometer (UV cut only).<br>
+ <a href="instruments.html#i1d"><span
+ style="text-decoration: underline;">ColorMunki</span></a> Create
+ or Smile
+ - display
+ colorimeter. (Similar to an Eye-One Display 2)<br>
+ <a href="instruments.html#Huey">Lenovo W</a>
+
+ -
+ built in laptop Huey display colorimeter.<br>
+ <a href="instruments.html#i1d3">Eye-One Display
+ 3</a>
+ - Xrite i1 DisplayPro and ColorMunki
+ Display <br>
+
+
+
+
+ [ The OEM
+ i1Display Pro, NEC SpectraSensor Pro,<br>
+
+
+
+ Quato Silver Haze 3 OEM and HP
+ DreamColor i1d3 are also reported to work.]<br>
+ <a href="instruments.html#i1p2">Eye-One Pro2</a>
+
+ - spot and
+ "swipe" reflective/emissive spectrometer.<br>
+ <br>
+ Gretag-Macbeth (now X-Rite):<br>
+ <a href="instruments.html#sl">Spectrolino</a>
+
+ - spot
+ reflective/emissive spectrometer.<br>
+ <a href="instruments.html#ss">SpectroScan</a>
+
+ - spot
+ reflective/emissive, XY table reflective spectrometer .<br>
+ <a href="instruments.html#ss">SpectroScanT</a>
+
+ - spot
+ reflective/emissive/transmissive, XY table reflective spectrometer.<br>
+ <a href="instruments.html#i1p">Eye-One Pro</a> "EFI
+ ES-1000" - spot and "swipe"
+ reflective/emissive spectrometer.<br>
+ <a href="instruments.html#i1m">Eye-One Monitor</a>
+
+ - spot and "swipe" emissive
+ spectrometer.<br>
+ <a href="instruments.html#i1d">Eye-One Display 1
+ or 2 or LT</a> -
+ display colorimeter.<br>
+ <a href="instruments.html#i1d">HP DreamColor or
+ APS</a>
@@ -472,8 +619,29 @@ - - display colorimeter. (Treated as a Eye-One Display 2)<br> - <a href="instruments.html#i1d">CalMAN X2</a> + + + + + + + + + + + + + + + + + + + + +
+ - display colorimeter. (Treated as a Eye-One Display 2)<br>
+ <a href="instruments.html#i1d">CalMAN X2</a>
@@ -515,17 +683,38 @@ - - display colorimeter. (Treated as a Eye-One Display 2)<br> - <a href="instruments.html#Huey">Huey</a> - - - - display colorimeter.<br> - <br> - Sequel imaging (Now X-Rite):<br> - <a href="instruments.html#mox">MonacoOPTIX</a> - - - display - colorimeter (Treated as an Eye-One Display 1)<br> + + + + + + + + + + + + + + + + + + + + +
+ - display colorimeter. (Treated as a Eye-One Display 2)<br>
+ <a href="instruments.html#Huey">Huey</a>
+
+
+ - display colorimeter.<br>
+ <br>
+ Sequel imaging (Now X-Rite):<br>
+ <a href="instruments.html#mox">MonacoOPTIX</a>
+
+ - display
+ colorimeter (Treated as an Eye-One Display 1)<br>
@@ -567,9 +756,30 @@ - [The Sequel Chroma 4 may also work.]<br> - <br> - Lacie Blue + + + + + + + + + + + + + + + + + + + + +
+ [The Sequel Chroma 4 may also work.]<br>
+ <br>
+ Lacie Blue
Eye: @@ -611,14 +821,35 @@ - - see <a href="instruments.html#i1d">Eye-One Display</a><br> - <br> - DataColor ColorVision:<br> - <a href="instruments.html#spyd2">Spyder 2</a> - - - - display colorimeter (Note - that the user must <a href="oeminst.html">supply</a> firmware)<br> + + + + + + + + + + + + + + + + + + + + +
+ - see <a href="instruments.html#i1d">Eye-One Display</a><br>
+ <br>
+ DataColor ColorVision:<br>
+ <a href="instruments.html#spyd2">Spyder 2</a>
+
+
+ - display colorimeter (Note
+ that the user must <a href="oeminst.html">supply</a> firmware)<br>
@@ -660,22 +891,53 @@ - [The Spyder 1 has also been reported as working, but this has not - been confirmed.]<br> - <a href="instruments.html#spyd3">Spyder 3</a> - - - - display colorimeter.<br> - <a href="instruments.html#spyd4">Spyder 4</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="instruments.html#HCFR">Colorimètre HCFR</a> + + + + + + + + + + + + + + + + + + + + +
+ [The Spyder 1 has also been reported as working, but this has not
+ been confirmed.]<br>
+ <a href="instruments.html#spyd3">Spyder 3</a>
+
+
+ - display colorimeter.<br>
+ <a href="instruments.html#spyd4">Spyder 4</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="instruments.html#HCFR">Colorimètre HCFR</a> + + + + + + + + + + @@ -716,8 +978,6 @@ - - display colorimeter</span><br> - <a href="http://www.hughski.com/">ColorHug</a> @@ -728,6 +988,9 @@ +
+ - display colorimeter</span><br>
+ <a href="instruments.html#ColorHug">ColorHug</a> @@ -743,104 +1006,133 @@ - - display colorimeter. Experimental only, does not work on all - platforms.<br> - <span style="font-weight: bold;"></span><span class="titre"><br> - See </span><a href="instruments.html">Operation of particular - instruments</a> for more instrument specific detail.<br> - <br> - 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 <a - href="Installing.html">installation instructions</a> 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 - supports it</span>" - thanks.<br> - </p> - <p><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> </p> - <p>There is a <a href="file:///D:/src/argyll/doc/ccmxs.html">list - of contributed</a> <span style="font-weight: bold;">ccmx</span> - (Colorimeter Correction Matrix) files for some display/colorimeter - combinations.</p> - <h2><span style="text-decoration: underline; color: rgb(51, 0, 51);"><a - name="Copyright"></a>Copyright and Licensing:</span><br> - </h2> - <p>Most of the source code and provided executable files are - copyrighted works, licensed under the <span style="font-weight: - bold;">Affero GNU Version 3 license</span>, and therefore they - (or works derived from them) can't be copied, sold or made - 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> - 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> - 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 - 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 - Documentation License, Version 1.3. The author asserts his moral - rights over this material in relationship to the attribution and - integrity of these works. In particular, if these works are - modified in a way that materially changes their functionality, - then the modified works should be renamed in a way that clearly - distinguishes them from "Argyll" or "ArgyllCMS" so that the - effects of such changes do not reflect on the original works - integrity or the original authors reputation. A subset of files - (those that are related to the color instrument drivers, and are - collected together into the instlib.zip archive by the - spectro/instlib.ksh script + xicc/ccmx.h and xicc/ccmx.c) are - licensed under the General Public License Version 2 or later, as - detailed in the <a href="License2.txt">License2.txt</a> file.<br> - </p> - <p>Portions of the ColorHug instrument library - (spectro/colorhug.[ch]) are Copyright 2011, Richard Hughes, and is - licensed under the General Public License Version 2 or later, as - detailed in the <a href="License2.txt">License2.txt</a> file.</p> - <p>The tool spectro/spec2cie.c is Copyright 2005 Gerhard Fuernkranz, - and is made available under the terms of the GNU General Public - License Version 2 or later, and is licensed here under the Version - 3 license, as detailed in the <a href="License3.txt">License3.txt</a> - file.<br> - </p> - <p>The Win32 USB library libusb-win32 kernel drivers are included in - this distribution in the usb/driver and usb/bin directories, and - are copyright Stephan Meyer and Travis Robinson, and are licensed - under the GNU Version 2 or later (the drivers, services, - installer). See usb/driver/License.txt, - libusbw/COPYING_LGPL.txt and libusbw/COPYING_GPL.txt for details. - Additional terms noted on the <a - href="http://sourceforge.net/apps/trac/libusb-win32/wiki">website</a> - are "This license combination explicitly allows the use of this - library in commercial, non-Open-Source applications."<br> - </p> - <p>The icc library in<span style="font-weight: bold;"> icc</span>/, + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ - display colorimeter<br>
+ <span style="font-weight: bold;"></span><span class="titre"><br>
+ See </span><a href="instruments.html">Operation of particular
+ instruments</a> for more instrument specific detail.<br>
+ <br>
+ 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>
+ <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
+ supports it</span>" - thanks.<br>
+ </p>
+ <p><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> </p>
+ <p>There is a <a href="ccmxs.html">list of contributed</a> <span
+ style="font-weight: bold;">ccmx</span> (Colorimeter Correction
+ Matrix) files for some display/colorimeter combinations.</p>
+ <h2><span style="text-decoration: underline; color: rgb(51, 0, 51);"><a
+ name="Copyright"></a>Copyright and Licensing:</span><br>
+ </h2>
+ <p>Most of the source code and provided executable files are
+ copyrighted works, licensed under the <span style="font-weight:
+ bold;">Affero GNU Version 3 license</span>, and therefore they
+ (or works derived from them) can't be copied, sold or made
+ 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>
+ 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>
+ 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
+ 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
+ Documentation License, Version 1.3. The author asserts his moral
+ rights over this material in relationship to the attribution and
+ integrity of these works. In particular, if these works are
+ modified in a way that materially changes their functionality,
+ then the modified works should be renamed in a way that clearly
+ distinguishes them from "Argyll" or "ArgyllCMS" so that the
+ effects of such changes do not reflect on the original works
+ integrity or the original authors reputation. A subset of files
+ (those that are related to the color instrument drivers, and are
+ collected together into the instlib.zip archive by the
+ spectro/instlib.ksh script + xicc/ccmx.h and xicc/ccmx.c) are
+ licensed under the General Public License Version 2 or later, as
+ detailed in the <a href="License2.txt">License2.txt</a> file.<br>
+ </p>
+ <p>Portions of the ColorHug instrument library
+ (spectro/colorhug.[ch]) are Copyright 2011, Richard Hughes, and is
+ licensed under the General Public License Version 2 or later, as
+ detailed in the <a href="License2.txt">License2.txt</a> file.</p>
+ <p>The tool spectro/spec2cie.c is Copyright 2005 Gerhard Fuernkranz,
+ and is made available under the terms of the GNU General Public
+ License Version 2 or later, and is licensed here under the Version
+ 3 license, as detailed in the <a href="License3.txt">License3.txt</a>
+ file.<br>
+ </p>
+ <p>The Win32 USB library libusb-win32 kernel drivers are included in
+ this distribution in the usb/driver and usb/bin directories, and
+ are copyright Stephan Meyer and Travis Robinson, and are licensed
+ under the GNU Version 2 or later (the drivers, services,
+ installer). See usb/driver/License.txt,
+ libusbw/COPYING_LGPL.txt and libusbw/COPYING_GPL.txt for details.
+ Additional terms noted on the <a
+ href="http://sourceforge.net/apps/trac/libusb-win32/wiki">website</a>
+ are "This license combination explicitly allows the use of this
+ library in commercial, non-Open-Source applications."<br>
+ </p>
+ <p>The icc library in<span style="font-weight: bold;"> icc</span>/,
the CGATS library in <span style="font-weight: bold;">cgats</span>/, @@ -882,6 +1174,27 @@ + + + + + + + + + + + + + + + + + + + + +
the jcnf library in <span style="font-weight: bold;">jcnf</span>/, @@ -922,72 +1235,93 @@ - 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 - 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> - </p> - <p> The TIFF library included in this distribution for convenience, - has its own copyright and license detailed in tiff/COPYRIGHT (an - "MIT"/"BSD" like license).<br> - </p> - <p>The Independent JPEG Group's JPEG library included in this - distribution for convenience, has its own copyright and license - detailed in jpg/README (an "MIT"/"BSD" like license). Executables - that include JPEG format support are based in part on the work of - the Independent JPEG Group. </p> - <p>xicc/iccjpeg.h and xicc/iccjpeg.c are from <a - href="http://www.littlecms.com/">lcms</a> and they are Copyright - (c) 1998-2010 Marti Maria Saguer and is licensed under an - "MIT"/"BSD" like license. See the top of the iccjpeg.c file for - 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> - <h2><span style="text-decoration: underline; color: rgb(51, 0, 51);"><a - name="ProjType"></a>What sort of project is this ? (re: - contributions)<br> - </span></h2> - This is essentially my private project, that I've made available - under GNU licensing conditions. Because I license my code under - other licenses as well, there is a limit to what I will accept in - the way of code contributions back into this project. For me to - accept contributions into the distribution, it either has to a - non-core (side) project, or has to be offered to me with copyright - conditions that are compatible with my other uses (i.e.. a "BSD" - like license, or assigning or licensing the copyright to me), or has - to be so trivial (say a one line bug fix), that it can't be the - subject of copyright. <br> - <br> - Of course there is nothing to stop someone setting up a real free - software, community project based on the GNU licensed code made - available here, that would be able to take GNU licensed - contributions from everyone and would essentially be a "fork" of - this code base.<br> - <br> - <h1><u><a href="Compiling.html">Compiling</a></u></h1> - How to <a href="Compiling.html">build the software</a> from the - source if you want to.<br> - <span style="font-weight: bold;">Note</span> that you don't need to - do this if you are using one of the binary installations.<br> - <h1 style="color: rgb(51, 204, 0);"><u><a href="Installing.html">Installing</a></u></h1> - Important notes on <a href="Installing.html">installing the binary - software</a> on various platforms.<br> - <br> - <h2 style="color: rgb(51, 0, 51);"><u><u><a name="GUIs"></a>Graphic - User Interfaces<br> - </u></u></h2> - ArgyllCMS does not directly support a graphic user interface, but - several people have written <span style="font-weight: bold;">GUI</span> + + + + + + + + + + + + + + + + + + + + +
+ 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
+ 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>
+ </p>
+ <p> The TIFF library included in this distribution for convenience,
+ has its own copyright and license detailed in tiff/COPYRIGHT (an
+ "MIT"/"BSD" like license).<br>
+ </p>
+ <p>The Independent JPEG Group's JPEG library included in this
+ distribution for convenience, has its own copyright and license
+ detailed in jpg/README (an "MIT"/"BSD" like license). Executables
+ that include JPEG format support are based in part on the work of
+ the Independent JPEG Group. </p>
+ <p>xicc/iccjpeg.h and xicc/iccjpeg.c are from <a
+ href="http://www.littlecms.com/">lcms</a> and they are Copyright
+ (c) 1998-2010 Marti Maria Saguer and is licensed under an
+ "MIT"/"BSD" like license. See the top of the iccjpeg.c file for
+ 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>
+ <h2><span style="text-decoration: underline; color: rgb(51, 0, 51);"><a
+ name="ProjType"></a>What sort of project is this ? (re:
+ contributions)<br>
+ </span></h2>
+ This is essentially my private project, that I've made available
+ under GNU licensing conditions. Because I license my code under
+ other licenses as well, there is a limit to what I will accept in
+ the way of code contributions back into this project. For me to
+ accept contributions into the distribution, it either has to a
+ non-core (side) project, or has to be offered to me with copyright
+ conditions that are compatible with my other uses (i.e.. a "BSD"
+ like license, or assigning or licensing the copyright to me), or has
+ to be so trivial (say a one line bug fix), that it can't be the
+ subject of copyright. <br>
+ <br>
+ Of course there is nothing to stop someone setting up a real free
+ software, community project based on the GNU licensed code made
+ available here, that would be able to take GNU licensed
+ contributions from everyone and would essentially be a "fork" of
+ this code base.<br>
+ <br>
+ <h1><u><a href="Compiling.html">Compiling</a></u></h1>
+ How to <a href="Compiling.html">build the software</a> from the
+ source if you want to.<br>
+ <span style="font-weight: bold;">Note</span> that you don't need to
+ do this if you are using one of the binary installations.<br>
+ <h1 style="color: rgb(51, 204, 0);"><u><a href="Installing.html">Installing</a></u></h1>
+ Important notes on <a href="Installing.html">installing the binary
+ software</a> on various platforms.<br>
+ <br>
+ <h2 style="color: rgb(51, 0, 51);"><u><u><a name="GUIs"></a>Graphic
+ User Interfaces<br>
+ </u></u></h2>
+ ArgyllCMS does not directly support a graphic user interface, but
+ several people have written <span style="font-weight: bold;">GUI</span>
based front ends for it. A popular <span style="font-weight: bold;"></span>front end that @@ -1034,17 +1368,38 @@ calibration - and profiling is <a href="http://hoech.net/dispcalGUI/">dispcalGUI</a> - by Florian Höch. Others can be found with a suitable <a -href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&aq=f&aqi=g1&aql=&oq=">search</a>.<br> - <h2 style="color: rgb(51, 0, 51);"><u><a name="CmdLine"></a>Main - Tools and the command line<br> - </u></h2> - These are all command line ("DOS" shell) tools, and each tool - require appropriate options to be set, followed by filename - arguments. Sometimes the filenames will have to include the usual - extensions, sometimes they are implicit. To get a brief listing of - the possible arguments and <span style="font-weight: bold;">usage</span> + + + + + + + + + + + + + + + + + + + + +
+ and profiling is <a href="http://hoech.net/dispcalGUI/">dispcalGUI</a>
+ by Florian Höch. Others can be found with a suitable <a
+href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&aq=f&aqi=g1&aql=&oq=">search</a>.<br>
+ <h2 style="color: rgb(51, 0, 51);"><u><a name="CmdLine"></a>Main
+ Tools and the command line<br>
+ </u></h2>
+ These are all command line ("DOS" shell) tools, and each tool
+ require appropriate options to be set, followed by filename
+ arguments. Sometimes the filenames will have to include the usual
+ extensions, sometimes they are implicit. To get a brief listing of
+ the possible arguments and <span style="font-weight: bold;">usage</span>
of any of the tools, run it with just an "-?" argument, i.e. <b>targen @@ -1084,22 +1439,43 @@ 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> - <br> - Note that in general the arguments consist of possible flags or - options followed by file name arguments. All arguments need to be - separated by whitespace. (If you need to specify a string with - embedded white space, double quote the string). A flag consists of a - dash attached to a single letter, the letter identifying the flag, - and is usually case sensitive. An option is a flag that has an - associated parameter or parameters. The parameter can be separated - from the flag by white space, or may come directly after the flag. - So if a tool has a usage that looks like this:<br> - <br> - tool -?<br> - usage: tool [options] infile outfile<br> - + + + + + + + + + + + + + + + + + + + + +
+ -? </b>(or some other unrecognized flag, if the "?" character is
+ treated specially in your shell, i.e. try "--" on OS X zsh).<br>
+ <br>
+ Note that in general the arguments consist of possible flags or
+ options followed by file name arguments. All arguments need to be
+ separated by whitespace. (If you need to specify a string with
+ embedded white space, double quote the string). A flag consists of a
+ dash attached to a single letter, the letter identifying the flag,
+ and is usually case sensitive. An option is a flag that has an
+ associated parameter or parameters. The parameter can be separated
+ from the flag by white space, or may come directly after the flag.
+ So if a tool has a usage that looks like this:<br>
+ <br>
+ tool -?<br>
+ usage: tool [options] infile outfile<br>
+
-v @@ -1141,8 +1517,29 @@ href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&a - Verbose mode<br> - -d + + + + + + + + + + + + + + + + + + + + +
+ Verbose mode<br>
+ -d
n @@ -1184,8 +1581,29 @@ href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&a - Choose a depth 0-4<br> - -r + + + + + + + + + + + + + + + + + + + + +
+ Choose a depth 0-4<br>
+ -r
@@ -1227,11 +1645,32 @@ href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&a - Use a random depth<br> - -f - [nn] - Use full range. nn optional range 0 - 100.<br> - -M + + + + + + + + + + + + + + + + + + + + +
+ Use a random depth<br>
+ -f
+ [nn]
+ Use full range. nn optional range 0 - 100.<br>
+ -M
@@ -1273,8 +1712,29 @@ href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&a - Manual<br> - infile + + + + + + + + + + + + + + + + + + + + +
+ Manual<br>
+ infile
@@ -1316,153 +1776,177 @@ href="http://www.google.com/search?hl=en&source=hp&q=argyllcms+GUI&a - Input file<br> - outfile - - Output file<br> - <br> - then there are 5 flags/options, and two filename arguments. - Notice that square braces [] denote optional items. The first - flag/option is a flag. The second is an option that has a numerical - argument in the range 0 to 4. The third is a flag. the fourth is an - option with an optional argument. The fourth is a flag. The - flags and options can generally be in any order, but must be before - the file name arguments. (For a few special tools you actually - specify a sequence of flags and files where the flags apply just to - the following file.) So example invocations may look like:<br> - <br> - tool -v testin testout<br> - tool -d3 -M testin1 testout2<br> - tool -f infile outfile<br> - tool -f 45 infile outfile<br> - tool -d 3 -f67 infile outfile<br> - <p>In order to make use of the tools, it is necessary to keep track - of where various files are, and what they are called. There are - many possible ways of doing this. One way is to put each source - profile and all its associated files (test charts, spectrometer - values etc.) in one set of directories for each source profile - type. Similarly the device profiles could be stored in a hierarchy - of directories ordered by device type, media, resolution, device - mode etc. Naturally you will want to set your $PATH so that you - can run the tools from whichever directory you are in, as well as - specify any necessary directory paths for file arguments so that - the tools are able to open them.<br> - </p> - <p>Note that there are two ways the Argyll tools deal with filename - extensions. In one you supply the extension (ie. you supply the - whole file name), so the extension is up to you. In the other - (used where one name is used for input and output files, or where - there are multiple output files), the program adds the extension. - In the documentation this should be indicated by calling it a - "base name".<br> - </p> - <p><a name="cltutes"></a>For more information on using a command - line environments, consult an appropriate tutorial:</p> - <p>MS Windows :<br> - <<a - href="http://www.bleepingcomputer.com/tutorials/tutorial76.html">http://www.bleepingcomputer.com/tutorials/tutorial76.html</a>><br> - <<a - href="http://www.pcstats.com/articleview.cfm?articleid=1723&page=1">http://www.pcstats.com/articleview.cfm?articleid=1723&page=1</a>><br> - <<a - href="http://www.voidspace.org.uk/python/articles/command_line.shtml">http://www.voidspace.org.uk/python/articles/command_line.shtml</a>><br> - <br> - To find more: <<a -href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial">http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial></a><br> - <br> - OS X:<br> - <<a - href="http://www.osxfaq.com/Tutorials/LearningCenter/">http://www.osxfaq.com/Tutorials/LearningCenter/</a>><br> - <<a - href="http://www.atomiclearning.com/macosxterminalx.shtml">http://www.atomiclearning.com/macosxterminalx.shtml</a>><br> - <<a - href="http://www.oreillynet.com/pub/a/mac/2001/12/14/terminal_one.html">http://www.oreillynet.com/pub/a/mac/2001/12/14/terminal_one.html</a>><br> - <br> - To find more: <<a - href="http://www.google.com/search?hl=en&q=OS+X+shell+tutorial">http://www.google.com/search?hl=en&q=OS+X+shell+tutorial</a>><br> - <br> - Linux:<br> - <<a - href="http://www.linuxcommand.org/index.php">http://www.linuxcommand.org/index.php</a>><br> - <<a - href="http://www.tuxfiles.org/linuxhelp/shell.html">http://www.tuxfiles.org/linuxhelp/shell.html</a>><br> - <<a - href="http://www.ee.surrey.ac.uk/Teaching/Unix/">http://www.ee.surrey.ac.uk/Teaching/Unix/</a>><br> - <br> - To find more: <<a - href="http://www.google.com/search?q=linux+command+line+shell+tutorial">http://www.google.com/search?q=linux+command+line+shell+tutorial</a>></p> - <p><br> - <span style="font-weight: bold;">Note</span> that since OS X is - based on UNIX, there is much in common between the OS X and Linux - command line environments, and many of the UNIX tutorials may be - useful:<br> - </p> - <p> <<a - href="http://www.rain.org/%7Emkummel/unix.html">http://www.rain.org/~mkummel/unix.html</a>><br> - <br> - </p> - <h2><u><a href="Scenarios.html">Tutorial: Typical usage scenarios - and examples</a></u></h2> - A <a href="Scenarios.html">guided tour</a> of the major tools, - applied to typical CMS jobs, such as calibrating displays, creating - device profiles, calibrating printers, linking profiles, and - converting color spaces of raster files. <br> - <br> - Although it is is a couple of years old now, this <a - href="http://www.argyllcms.com/doc/FCMS2010_ArgyllTute.pdf">tutorial</a> - may also be of interest.<br> - <br> - <h3 style="color: rgb(0, 0, 0);"><u><a name="Topics"></a>Topical - Discussions</u></h3> - Discussions about particular topics:<br> - <br> - <a href="FWA.html">About Fluorescent Whitening Agent compensation</a><br> - <br> - <a href="instruments.html">Operation of particular instruments</a><br> - <br> - <a href="iccgamutmapping.html">About ICC profiles and Gamut Mapping</a><br> - <br> - <a href="monitorcontrols.html">About display monitor settings and - targets</a><br> - <br> - <a href="gamma.html">About display "Gamma"</a><br> - <br> - <a href="calvschar.html">What's the difference between Calibration - and Characterization ?</a><br> - <br> - <a href="WideGamutColmters.html">Why doesn't my Colorimeter work - well on my Wide Gamut display ?</a><br> - <span style="font-family: monospace;"></span><br> - <a href="CrushedDisplyBlacks.html">My blacks get crushed on my - display - why ? How do I fix it ?</a><br> - <br> - <a href="i1proDriver.html">How can I have confidence in the i1pro - Driver ?</a><br> - <br> - <a href="evalInputTargets.html">Evaluating input targets</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> - <a - href="ArgyllFlow.jpg"><img alt="Thumbnail of Flow Diagram" - src="ArgyllFlowThumb.jpg" style="border: 2px solid ; width: - 150px; height: 202px;"></a><br> - <br> - <h2><b><u><font size="+2"><a name="CatList"></a>Main Tools by - category:</font></u></b></h2> - <h3>Calibrating devices<br> - </h3> - <small><a style="font-family: monospace;" href="dispcal.html">dispcal</a><span - style="font-family: monospace;"> - </span></small>Adjust, - calibrate and profile a display<small><big>.<br> - </big></small><small><a style="font-family: monospace;" - href="printcal.html">printcal</a><span style="font-family: - monospace;"> </span></small>Create a - printer calibration .cal file from a .ti3 data file<small><big>.</big></small><br> - <h3>Creating test targets for profiling or print calibration<br> - </h3> - <small><a style="font-family: monospace;" href="targen.html">targen</a><span + + + + + + + + + + + + + + + + + + + + +
+ Input file<br>
+ outfile
+
+ Output file<br>
+ <br>
+ then there are 5 flags/options, and two filename arguments.
+ Notice that square braces [] denote optional items. The first
+ flag/option is a flag. The second is an option that has a numerical
+ argument in the range 0 to 4. The third is a flag. the fourth is an
+ option with an optional argument. The fourth is a flag. The
+ flags and options can generally be in any order, but must be before
+ the file name arguments. (For a few special tools you actually
+ specify a sequence of flags and files where the flags apply just to
+ the following file.) So example invocations may look like:<br>
+ <br>
+ tool -v testin testout<br>
+ tool -d3 -M testin1 testout2<br>
+ tool -f infile outfile<br>
+ tool -f 45 infile outfile<br>
+ tool -d 3 -f67 infile outfile<br>
+ <p>In order to make use of the tools, it is necessary to keep track
+ of where various files are, and what they are called. There are
+ many possible ways of doing this. One way is to put each source
+ profile and all its associated files (test charts, spectrometer
+ values etc.) in one set of directories for each source profile
+ type. Similarly the device profiles could be stored in a hierarchy
+ of directories ordered by device type, media, resolution, device
+ mode etc. Naturally you will want to set your $PATH so that you
+ can run the tools from whichever directory you are in, as well as
+ specify any necessary directory paths for file arguments so that
+ the tools are able to open them.<br>
+ </p>
+ <p>Note that there are two ways the Argyll tools deal with filename
+ extensions. In one you supply the extension (ie. you supply the
+ whole file name), so the extension is up to you. In the other
+ (used where one name is used for input and output files, or where
+ there are multiple output files), the program adds the extension.
+ In the documentation this should be indicated by calling it a
+ "base name".<br>
+ </p>
+ <p><a name="cltutes"></a>For more information on using a command
+ line environments, consult an appropriate tutorial:</p>
+ <p>MS Windows :<br>
+ <<a
+ href="http://www.bleepingcomputer.com/tutorials/tutorial76.html">http://www.bleepingcomputer.com/tutorials/tutorial76.html</a>><br>
+ <<a
+ href="http://www.pcstats.com/articleview.cfm?articleid=1723&page=1">http://www.pcstats.com/articleview.cfm?articleid=1723&page=1</a>><br>
+ <<a
+ href="http://www.voidspace.org.uk/python/articles/command_line.shtml">http://www.voidspace.org.uk/python/articles/command_line.shtml</a>><br>
+ <br>
+ To find more: <<a
+href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial">http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial></a><br>
+ <br>
+ OS X:<br>
+ <<a
+ href="http://www.osxfaq.com/Tutorials/LearningCenter/">http://www.osxfaq.com/Tutorials/LearningCenter/</a>><br>
+ <<a
+ href="http://www.atomiclearning.com/macosxterminalx.shtml">http://www.atomiclearning.com/macosxterminalx.shtml</a>><br>
+ <<a
+ href="http://www.oreillynet.com/pub/a/mac/2001/12/14/terminal_one.html">http://www.oreillynet.com/pub/a/mac/2001/12/14/terminal_one.html</a>><br>
+ <br>
+ To find more: <<a
+ href="http://www.google.com/search?hl=en&q=OS+X+shell+tutorial">http://www.google.com/search?hl=en&q=OS+X+shell+tutorial</a>><br>
+ <br>
+ Linux:<br>
+ <<a
+ href="http://www.linuxcommand.org/index.php">http://www.linuxcommand.org/index.php</a>><br>
+ <<a
+ href="http://www.tuxfiles.org/linuxhelp/shell.html">http://www.tuxfiles.org/linuxhelp/shell.html</a>><br>
+ <<a
+ href="http://www.ee.surrey.ac.uk/Teaching/Unix/">http://www.ee.surrey.ac.uk/Teaching/Unix/</a>><br>
+ <br>
+ To find more: <<a
+ href="http://www.google.com/search?q=linux+command+line+shell+tutorial">http://www.google.com/search?q=linux+command+line+shell+tutorial</a>></p>
+ <p><br>
+ <span style="font-weight: bold;">Note</span> that since OS X is
+ based on UNIX, there is much in common between the OS X and Linux
+ command line environments, and many of the UNIX tutorials may be
+ useful:<br>
+ </p>
+ <p> <<a
+ href="http://www.rain.org/%7Emkummel/unix.html">http://www.rain.org/~mkummel/unix.html</a>><br>
+ <br>
+ </p>
+ <h2><u><a href="Scenarios.html">Tutorial: Typical usage scenarios
+ and examples</a></u></h2>
+ A <a href="Scenarios.html">guided tour</a> of the major tools,
+ applied to typical CMS jobs, such as calibrating displays, creating
+ device profiles, calibrating printers, linking profiles, and
+ converting color spaces of raster files. <br>
+ <br>
+ Although it is is a couple of years old now, this <a
+ href="http://www.argyllcms.com/doc/FCMS2010_ArgyllTute.pdf">tutorial</a>
+ may also be of interest.<br>
+ <br>
+ <h3 style="color: rgb(0, 0, 0);"><u><a name="Topics"></a>Topical
+ Discussions</u></h3>
+ Discussions about particular topics:<br>
+ <br>
+ <a href="FWA.html">About Fluorescent Whitening Agent compensation</a><br>
+ <br>
+ <a href="instruments.html">Operation of particular instruments</a><br>
+ <br>
+ <a href="iccgamutmapping.html">About ICC profiles and Gamut Mapping</a><br>
+ <br>
+ <a href="monitorcontrols.html">About display monitor settings and
+ targets</a><br>
+ <br>
+ <a href="gamma.html">About display "Gamma"</a><br>
+ <br>
+ <a href="calvschar.html">What's the difference between Calibration
+ and Characterization ?</a><br>
+ <br>
+ <a href="WideGamutColmters.html">Why doesn't my Colorimeter work
+ well on my Wide Gamut display ?</a><br>
+ <span style="font-family: monospace;"></span><br>
+ <a href="CrushedDisplyBlacks.html">My blacks get crushed on my
+ display - why ? How do I fix it ?</a><br>
+ <br>
+ <a href="i1proDriver.html">How can I have confidence in the i1pro
+ Driver ?</a><br>
+ <br>
+ <a href="i1proHiRes.html">Does the i1pro High Resolution mode
+ improve accuracy ?</a><br>
+ <br>
+ <a href="evalInputTargets.html">Evaluating input targets</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>
+ <a
+ href="ArgyllFlow.jpg"><img alt="Thumbnail of Flow Diagram"
+ src="ArgyllFlowThumb.jpg" style="border: 2px solid ; width:
+ 150px; height: 202px;"></a><br>
+ <br>
+ <h2><b><u><font size="+2"><a name="CatList"></a>Main Tools by
+ category:</font></u></b></h2>
+ <h3>Calibrating devices<br>
+ </h3>
+ <small><a style="font-family: monospace;" href="dispcal.html">dispcal</a><span
+ style="font-family: monospace;">
+ </span></small>Adjust,
+ calibrate and profile a display<small><big>.<br>
+ </big></small><small><a style="font-family: monospace;"
+ href="printcal.html">printcal</a><span style="font-family:
+ monospace;"> </span></small>Create a
+ printer calibration .cal file from a .ti3 data file<small><big>.</big></small><br>
+ <h3>Creating test targets for profiling or print calibration<br>
+ </h3>
+ <small><a style="font-family: monospace;" href="targen.html">targen</a><span
style="font-family: monospace;"> @@ -1504,9 +1988,30 @@ 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;"> - <a style="font-family: monospace;" href="filmtarg.html">filmtarg</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span><big>Generate a profiling test target values .ti1 file. </big><br
+ style="font-family: monospace;">
+ <a style="font-family: monospace;" href="filmtarg.html">filmtarg</a><span
style="font-family: monospace;"> </span><big>Create @@ -1548,9 +2053,30 @@ 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;"> - <a style="font-family: monospace;" href="printtarg.html">printtarg</a><span + + + + + + + + + + + + + + + + + + + + +
+ film recorder TIFF files from Argyll .ti1 file. </big><br
+ style="font-family: monospace;">
+ <a style="font-family: monospace;" href="printtarg.html">printtarg</a><span
style="font-family: monospace;"> </span><big>Create @@ -1592,11 +2118,32 @@ 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> - <h3>Obtaining test results for profiling or print calibration<br> - </h3> - <small><a style="font-family: monospace;" href="chartread.html">chartread</a><span + + + + + + + + + + + + + + + + + + + + +
+ a PS, EPS or TIFF file containing test patch values, ready for
+ printing.</big></small>
+ <h3>Obtaining test results for profiling or print calibration<br>
+ </h3>
+ <small><a style="font-family: monospace;" href="chartread.html">chartread</a><span
style="font-family: monospace;"> </span><big>Read @@ -1638,10 +2185,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: - monospace;"> - <a style="font-family: monospace;" href="dispread.html">dispread</a><span + + + + + + + + + + + + + + + + + + + + +
+ a test chart using an instrument to create a .ti3 data file.</big><span
+ style="font-family: monospace;"> </span><br style="font-family:
+ monospace;">
+ <a style="font-family: monospace;" href="dispread.html">dispread</a><span
style="font-family: monospace;"> </span><big>Test @@ -1683,9 +2251,30 @@ 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;"> - <a style="font-family: monospace;" href="filmread.html">filmread</a><span + + + + + + + + + + + + + + + + + + + + +
+ and read colorimetric values from a display </big><br
+ style="font-family: monospace;">
+ <a style="font-family: monospace;" href="filmread.html">filmread</a><span
style="font-family: monospace;"> </span><big>Read @@ -1727,9 +2316,30 @@ 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;"> - <a style="font-family: monospace;" href="scanin.html">scanin</a><span + + + + + + + + + + + + + + + + + + + + +
+ film colorimetric values using a SpectroScanT (Deprecated ?)</big><br
+ style="font-family: monospace;">
+ <a style="font-family: monospace;" href="scanin.html">scanin</a><span
style="font-family: monospace;"> @@ -1771,14 +2381,35 @@ 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> - </big></small><small><a style="font-family: monospace;" - href="illumread.html">illumread</a><span style="font-family: - monospace;"> </span></small>Use an - instrument to measure an illuminant spectrum, and estimate its UV - content.<br style="font-family: monospace;"> - <small><a style="font-family: monospace;" href="fakeread.html">fakeread</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span><big>Convert a TIFF image of a test chart into .ti3
+ device values. <br>
+ </big></small><small><a style="font-family: monospace;"
+ href="illumread.html">illumread</a><span style="font-family:
+ monospace;"> </span></small>Use an
+ instrument to measure an illuminant spectrum, and estimate its UV
+ content.<br style="font-family: monospace;">
+ <small><a style="font-family: monospace;" href="fakeread.html">fakeread</a><span
style="font-family: monospace;"> </span><big>Fake @@ -1820,13 +2451,34 @@ 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;" - href="synthread.html">synthread</a><span style="font-family: - monospace;"> </span><big>Fake the - reading of a device using a synthetic device model. </big></small><br - style="font-family: monospace;"> - <small><a style="font-family: monospace;" href="cb2ti3.html">cb2ti3</a><span + + + + + + + + + + + + + + + + + + + + +
+ the reading of a device using an ICC or MPP profile. <br>
+ </big></small><small><a style="font-family: monospace;"
+ href="synthread.html">synthread</a><span style="font-family:
+ monospace;"> </span><big>Fake the
+ reading of a device using a synthetic device model. </big></small><br
+ style="font-family: monospace;">
+ <small><a style="font-family: monospace;" href="cb2ti3.html">cb2ti3</a><span
style="font-family: monospace;"> @@ -1868,10 +2520,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: - monospace;"> - <a style="font-family: monospace;" href="kodak2ti3.html">kodak2ti3</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span><big>Convert Colorblind format CMY/RGB test chart into
+ Argyll .ti3 CGATS format. </big><br style="font-family:
+ monospace;">
+ <a style="font-family: monospace;" href="kodak2ti3.html">kodak2ti3</a><span
style="font-family: monospace;"> </span><big>Convert @@ -1913,9 +2586,30 @@ 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;"> - <a style="font-family: monospace;" href="txt2ti3.html">txt2ti3</a><span + + + + + + + + + + + + + + + + + + + + +
+ Kodak Colorflow format CMYK test chart into Argyll .ti3 CGATS
+ format. </big><br style="font-family: monospace;">
+ <a style="font-family: monospace;" href="txt2ti3.html">txt2ti3</a><span
style="font-family: monospace;"> @@ -1957,10 +2651,31 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ </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;"> @@ -2002,10 +2717,31 @@ 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: + + + + + + + + + + + + + + + + + + + + +
+ </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 @@ -2046,9 +2782,30 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - / Merge two measurement data files</big></small><br> - <h3>Creating Device Profiles</h3> - <small><a style="font-family: monospace;" href="colprof.html">colprof</a><span + + + + + + + + + + + + + + + + + + + + +
+ / Merge two measurement data files</big></small><br>
+ <h3>Creating Device Profiles</h3>
+ <small><a style="font-family: monospace;" href="colprof.html">colprof</a><span
style="font-family: monospace;"> @@ -2090,8 +2847,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Create an ICC profile from the .ti3 test data. <br>
+ <small><a style="font-family: monospace;" href="mppprof.html">mppprof</a><span
style="font-family: monospace;"> @@ -2133,9 +2911,30 @@ 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="revfix.html">revfix</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Create a Model Printer Profile (MPP) from the .ti3
+ test data. <br>
+ <small><a style="font-family: monospace;" href="revfix.html">revfix</a><span
style="font-family: monospace;"> @@ -2177,10 +2976,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. - <h3>Creating Device Link Profiles</h3> - <small><a style="font-family: monospace;" href="collink.html">collink</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Regenerate a device profiles B2A table data by
+ inverting the A2B table.
+ <h3>Creating Device Link Profiles</h3>
+ <small><a style="font-family: monospace;" href="collink.html">collink</a><span
style="font-family: monospace;"> @@ -2222,11 +3042,32 @@ 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. - <h3>Converting colors or applying print calibration<br> - </h3> - <small><a style="font-family: monospace;" href="cctiff.html">cctiff</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Link two device ICC profiles to create a device
+ link profile.
+ <h3>Converting colors or applying print calibration<br>
+ </h3>
+ <small><a style="font-family: monospace;" href="cctiff.html">cctiff</a><span
style="font-family: monospace;"> @@ -2268,10 +3109,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> - <small><a style="font-family: monospace;" href="applycal.html">applycal</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Color convert a TIFF or JPEG file using a sequence
+ of ICC device, device link, abstract profiles and calibration files.
+ <br>
+ <small><a style="font-family: monospace;" href="applycal.html">applycal</a><span
style="font-family: monospace;"> </span></small>Apply @@ -2312,8 +3174,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ calibration curves to an ICC profile.<br>
+ <small><a style="font-family: monospace;" href="icclu.html">icclu </a><span
style="font-family: monospace;"> @@ -2355,9 +3238,30 @@ 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> - <small><a style="font-family: monospace;" href="xicclu.html">xicclu</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Lookup individual color values through any ICC
+ profile table. <br>
+ <small><a style="font-family: monospace;" href="xicclu.html">xicclu</a><span
style="font-family: monospace;"> @@ -2399,9 +3303,30 @@ 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 table. <br> - <small><a style="font-family: monospace;" href="mpplu.html">mpplu</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Lookup individual color values forward or inverted
+ though an ICC profile or CAL table. <br>
+ <small><a style="font-family: monospace;" href="mpplu.html">mpplu</a><span
style="font-family: monospace;"> @@ -2443,9 +3368,30 @@ 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> - <small><a style="font-family: monospace;" href="greytiff.html">greytiff</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Lookup individual color values though an MPP
+ profile. Also create MPP gamut files/views.<br>
+ <small><a style="font-family: monospace;" href="greytiff.html">greytiff</a><span
style="font-family: monospace;"> </span></small>Convert @@ -2487,17 +3433,38 @@ 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> - </h3> - <small><a style="font-family: monospace;" href="refine.html">refine</a><span - style="font-family: monospace;"> - </span></small>Creates an - abstract profile from two chart readings, useful for refining - proofing profiles. <a href="mppprof.html"><br> - </a> - <h3>Creating gamut views</h3> - <small><a style="font-family: monospace;" href="iccgamut.html">iccgamut</a><span + + + + + + + + + + + + + + + + + + + + +
+ a TIFF file to monochrome using an ICC device profile <br>
+ <h3>Color Tweaking tools<br>
+ </h3>
+ <small><a style="font-family: monospace;" href="refine.html">refine</a><span
+ style="font-family: monospace;">
+ </span></small>Creates an
+ abstract profile from two chart readings, useful for refining
+ proofing profiles. <a href="mppprof.html"><br>
+ </a>
+ <h3>Creating gamut views</h3>
+ <small><a style="font-family: monospace;" href="iccgamut.html">iccgamut</a><span
style="font-family: monospace;"> </span></small>Create @@ -2539,8 +3506,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ 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
style="font-family: monospace;"> </span></small>Create @@ -2582,9 +3570,30 @@ 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> - <small><a style="font-family: monospace;" href="viewgam.html">viewgam</a><span + + + + + + + + + + + + + + + + + + + + +
+ a gamut file or VRML file of the color gamut of a TIFF or JPEG
+ image. <br>
+ <small><a style="font-family: monospace;" href="viewgam.html">viewgam</a><span
style="font-family: monospace;"> @@ -2626,11 +3635,32 @@ 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> - <h3>Diagnostic and test tools<br> - </h3> - <small><a style="font-family: monospace;" href="iccdump.html">iccdump</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Convert one or more gamuts into a VRML 3D
+ visualization file. Compute an intersection.<br>
+ <h3>Diagnostic and test tools<br>
+ </h3>
+ <small><a style="font-family: monospace;" href="iccdump.html">iccdump</a><span
style="font-family: monospace;"> @@ -2672,8 +3702,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Dump the contents of an ICC profile as text. <br>
+ <small><a style="font-family: monospace;" href="profcheck.html">profcheck</a><span
style="font-family: monospace;"> </span></small>Check @@ -2715,7 +3766,28 @@ 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. <br>
<small style="font-family: monospace;"><a href="invprofcheck.html">invprofcheck</a> @@ -2757,8 +3829,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ </small>Check ICC forward against inverse lookup. <br>
+ <small><a style="font-family: monospace;" href="splitti3.html">splitsti3</a><span
style="font-family: monospace;"> </span></small>Split @@ -2799,12 +3892,33 @@ 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> - <small style="font-family: monospace;"><a href="timage.html">timage</a> - </small>Create TIFF test - images. <br> - <small><a style="font-family: monospace;" href="mppcheck.html">mppcheck</a><span + + + + + + + + + + + + + + + + + + + + +
+ a CGATS file (ie. a .ti3) into two parts randomly to verify
+ profiling. <br>
+ <small style="font-family: monospace;"><a href="timage.html">timage</a>
+ </small>Create TIFF test
+ images. <br>
+ <small><a style="font-family: monospace;" href="mppcheck.html">mppcheck</a><span
style="font-family: monospace;"> </span></small>Check @@ -2846,8 +3960,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ an MPP profile against .ti3 test chart data. <br>
+ <small><a style="font-family: monospace;" href="spotread.html">spotread</a><span
style="font-family: monospace;"> </span></small>Use @@ -2888,13 +4023,37 @@ 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="verify.html">verify</a><span - style="font-family: monospace;"> - </span></small>Verify - matching of CIE in two CGATS/.ti3 files (also view differences as - VRML)<br> - <small><a style="font-family: monospace;" href="synthcal.html">synthcal</a><span + + + + + + + + + + + + + + + + + + + + +
+ an instrument to read a single spot color value. <br>
+ <small><a style="font-family: monospace;" href="colverify.html">colverify</a><span
+ style="font-family: monospace;"> </span></small>Verify + + + +
+ matching of CIE in two CGATS/.ti3 files (also view differences as
+ VRML)<br>
+ <small><a style="font-family: monospace;" href="synthcal.html">synthcal</a><span
style="font-family: monospace;"> </span></small>Create @@ -2935,10 +4094,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. - <h3>Other Tools</h3> - <small><a style="font-family: monospace;" href="ccxxmake.html">ccxxmake</a><span + + + + + + + + + + + + + + + + + + + + +
+ a synthetic input, display or output calibration (<a
+ href="File_Formats.html#.cal">.cal</a>)file.
+ <h3>Other Tools</h3>
+ <small><a style="font-family: monospace;" href="ccxxmake.html">ccxxmake</a><span
style="font-family: monospace;"> </span></small>Use @@ -2979,11 +4159,32 @@ 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) - for a particular display.<br> - <small><a style="font-family: monospace;" href="extracticc.html">extracticc</a><span - style="font-family: monospace;"></span></small><small><span + + + + + + + + + + + + + + + + + + + + +
+ a Spectrometer to create a Colorimeter Correction Matrix
+ (CCMX) or a Colorimeter Calibration Spectral Set (CCSS)
+ for a particular display.<br>
+ <small><a style="font-family: monospace;" href="extracticc.html">extracticc</a><span
+ style="font-family: monospace;"></span></small><small><span
style="font-family: monospace;"> </span>Extract @@ -3025,14 +4226,35 @@ 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;" - href="extractttag.html">extractttag</a><span style="font-family: - monospace;"></span></small><small><span style="font-family: - monospace;"> </span>Extract a text tag (ie. CGATS - .ti3 data or CAL) from an ICC profile.</small><br> - <small><a style="font-family: monospace;" href="dispwin.html">dispwin</a><span - style="font-family: monospace;"></span></small><small><span + + + + + + + + + + + + + + + + + + + + +
+ an embedded ICC profile from a TIFF or JPEG file.<br>
+ </small><small><a style="font-family: monospace;"
+ href="extractttag.html">extractttag</a><span style="font-family:
+ monospace;"></span></small><small><span style="font-family:
+ monospace;"> </span>Extract a text tag (ie. CGATS
+ .ti3 data or CAL) from an ICC profile.</small><br>
+ <small><a style="font-family: monospace;" href="dispwin.html">dispwin</a><span
+ style="font-family: monospace;"></span></small><small><span
style="font-family: monospace;"> </span></small>Install @@ -3074,15 +4296,36 @@ 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> - <small><a style="font-family: monospace;" href="specplot.html">specplot</a><span - style="font-family: monospace;"> </span><span + + + + + + + + + + + + + + + + + + + + +
+ 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>
+ <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> @@ -3124,9 +4367,30 @@ 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 - style="font-family: monospace;"> </span><span + + + + + + + + + + + + + + + + + + + + +
+ Plot a spectrum (.sp, .cmf, .ccss) and calculate CCT and VCT.<br>
+ <small><a style="font-family: monospace;" href="spec2cie.html">spec2cie</a><span
+ style="font-family: monospace;"> </span><span
style="text-decoration: underline; font-family: monospace;"></span></small>Convert @@ -3168,13 +4432,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> - - <h2><b><u><font size="+2"><a name="AlphList"></a>Main Tools - Alphabetic Listing:</font></u></b></h2> - <small><a style="font-family: monospace;" href="applycal.html">applycal</a><span + + + + + + + + + + + + + + + + + + + + +
+ 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>
+
+ <h2><b><u><font size="+2"><a name="AlphList"></a>Main Tools
+ Alphabetic Listing:</font></u></b></h2>
+ <small><a style="font-family: monospace;" href="applycal.html">applycal</a><span
style="font-family: monospace;"> </span></small>Apply @@ -3215,8 +4500,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ calibration curves to an ICC profile.<br>
+ <small><a style="font-family: monospace;" href="average.html">average</a><span
style="font-family: monospace;"> @@ -3258,8 +4564,29 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - </span><big>Average / Merge two measurement data files</big></small><br> - <small><a style="font-family: monospace;" href="cb2ti3.html">cb2ti3</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span><big>Average / Merge two measurement data files</big></small><br>
+ <small><a style="font-family: monospace;" href="cb2ti3.html">cb2ti3</a><span
style="font-family: monospace;"> @@ -3301,9 +4628,30 @@ 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> - <small><a style="font-family: monospace;" href="cctiff.html">cctiff</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Convert Colorblind format CMY/RGB test chart into
+ Argyll .ti3 CGATS format. <br>
+ <small><a style="font-family: monospace;" href="cctiff.html">cctiff</a><span
style="font-family: monospace;"> @@ -3345,9 +4693,30 @@ 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> - <small><a style="font-family: monospace;" href="ccxxmake.html">ccxxmake</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Color convert a TIFF or JPEG file using a sequence
+ of ICC device, device link, abstract profiles and calibration files.<br>
+ <small><a style="font-family: monospace;" href="ccxxmake.html">ccxxmake</a><span
style="font-family: monospace;"> </span></small>Use @@ -3388,10 +4757,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) - for a particular display.<br> - <small><a style="font-family: monospace;" href="chartread.html">chartread</a><span + + + + + + + + + + + + + + + + + + + + +
+ a Spectrometer to create a Colorimeter Correction Matrix
+ (CCMX) or a Colorimeter Calibration Spectral Set (CCSS)
+ for a particular display.<br>
+ <small><a style="font-family: monospace;" href="chartread.html">chartread</a><span
style="font-family: monospace;"> </span></small>Read @@ -3433,8 +4823,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ 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
style="font-family: monospace;"> @@ -3476,9 +4887,30 @@ 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> - <small><a style="font-family: monospace;" href="colprof.html">colprof</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Link two device ICC profiles to create a device
+ link profile. <br>
+ <small><a style="font-family: monospace;" href="colprof.html">colprof</a><span
style="font-family: monospace;"> @@ -3520,11 +4952,98 @@ 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 style="font-family: monospace;"><a href="dispcal.html">dispcal</a> - </small>Adjust, calibrate and - profile a display<small><big>.</big></small><br> - <small><a style="font-family: monospace;" href="dispread.html">dispread</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Create an ICC profile from the .ti3 test data.<br>
+ <font size="-1"><a style="font-family: monospace;"
+ href="file:///D:/src/argyll/doc/colverify.html">colverify</a><span
+ style="font-family: monospace;"> </span></font>Verify + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ matching of CIE in two CGATS/.ti3 files (also view differences as
+ VRML)<br>
+ <small style="font-family: monospace;"><a href="dispcal.html">dispcal</a>
+ </small>Adjust, calibrate and
+ profile a display<small><big>.</big></small><br>
+ <small><a style="font-family: monospace;" href="dispread.html">dispread</a><span
style="font-family: monospace;"> </span></small>Test @@ -3566,9 +5085,30 @@ 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 - style="font-family: monospace;"></span></small><small><span + + + + + + + + + + + + + + + + + + + + +
+ and read colorimetric values from a display <br>
+ <small><a style="font-family: monospace;" href="dispwin.html">dispwin</a><span
+ style="font-family: monospace;"></span></small><small><span
style="font-family: monospace;"> </span></small>Install @@ -3610,10 +5150,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> - <small><a style="font-family: monospace;" href="extracticc.html">extracticc</a><span - style="font-family: monospace;"></span></small><small><span + + + + + + + + + + + + + + + + + + + + +
+ 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="extracticc.html">extracticc</a><span
+ style="font-family: monospace;"></span></small><small><span
style="font-family: monospace;"> </span>Extract @@ -3655,13 +5216,34 @@ 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;" - href="extractttag.html">extractttag</a><span style="font-family: - monospace;"></span></small><small><span style="font-family: - monospace;"> </span>Extract a text tag (ie. CGATS - .ti3 data or CAL) from an ICC profile.</small><br> - <small><a style="font-family: monospace;" href="fakeCMY.html">fakeCMY</a><span + + + + + + + + + + + + + + + + + + + + +
+ an embedded ICC profile from a TIFF or JPEG file.<br>
+ </small><small><a style="font-family: monospace;"
+ href="extractttag.html">extractttag</a><span style="font-family:
+ monospace;"></span></small><small><span style="font-family:
+ monospace;"> </span>Extract a text tag (ie. CGATS
+ .ti3 data or CAL) from an ICC profile.</small><br>
+ <small><a style="font-family: monospace;" href="fakeCMY.html">fakeCMY</a><span
style="font-family: monospace;"> @@ -3703,9 +5285,30 @@ 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> - <small><a style="font-family: monospace;" href="fakeread.html">fakeread</a><span + + + + + + + + + + + + + + + + + + + + +
+ </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>
+ <small><a style="font-family: monospace;" href="fakeread.html">fakeread</a><span
style="font-family: monospace;"> </span></small>Fake @@ -3747,8 +5350,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ the reading of a device using an ICC or MPP profile. <br>
+ <small><a style="font-family: monospace;" href="filmread.html">filmread</a><span
style="font-family: monospace;"> </span></small>Read @@ -3790,8 +5414,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ film colorimetric values using a SpectroScanT (Deprecated ?)<br>
+ <small><a style="font-family: monospace;" href="filmtarg.html">filmtarg</a><span
style="font-family: monospace;"> </span></small>Create @@ -3833,8 +5478,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ film recorder TIFF files from Argyll .ti1 file. <br>
+ <small><a style="font-family: monospace;" href="greytiff.html">greytiff</a><span
style="font-family: monospace;"> </span></small>Convert @@ -3876,9 +5542,30 @@ 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> - <small><a style="font-family: monospace;" href="iccdump.html">iccdump</a><span + + + + + + + + + + + + + + + + + + + + +
+ a TIFF file to monochrome using an ICC device profile <small><a
+ style="font-family: monospace;" href="oeminst.html"></a></small><br>
+ <small><a style="font-family: monospace;" href="iccdump.html">iccdump</a><span
style="font-family: monospace;"> @@ -3920,8 +5607,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Dump the contents of an ICC profile as text. <br>
+ <small><a style="font-family: monospace;" href="iccgamut.html">iccgamut</a><span
style="font-family: monospace;"> </span></small>Create @@ -3963,8 +5671,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ 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
style="font-family: monospace;"> @@ -4006,9 +5735,30 @@ 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> - <small><a style="font-family: monospace;" href="illumread.html">illumread</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Lookup individual color values through any ICC
+ profile table. <br>
+ <small><a style="font-family: monospace;" href="illumread.html">illumread</a><span
style="font-family: monospace;"> </span></small>Use @@ -4049,12 +5799,33 @@ 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> - <small><a style="font-family: monospace;" href="invprofcheck.html">invprofcheck</a><span - style="font-family: monospace;"> </span></small>Check ICC - forward against inverse lookup. <br> - <small><a style="font-family: monospace;" href="kodak2ti3.html">kodak2ti3</a><span + + + + + + + + + + + + + + + + + + + + +
+ an instrument to measure an illuminant spectrum, and estimate its UV
+ content.<br>
+ <small><a style="font-family: monospace;" href="invprofcheck.html">invprofcheck</a><span
+ style="font-family: monospace;"> </span></small>Check ICC
+ forward against inverse lookup. <br>
+ <small><a style="font-family: monospace;" href="kodak2ti3.html">kodak2ti3</a><span
style="font-family: monospace;"> </span></small>Convert @@ -4096,9 +5867,30 @@ 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><a style="font-family: monospace;" href="mppcheck.html">mppcheck</a><span + + + + + + + + + + + + + + + + + + + + +
+ Kodak Colorflow format CMYK test chart into Argyll .ti3 CGATS
+ format. <br>
+ <small><a style="font-family: monospace;" href="mppcheck.html">mppcheck</a><span
style="font-family: monospace;"> </span></small>Check @@ -4140,8 +5932,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ an MPP profile against .ti3 test chart data. <br>
+ <small><a style="font-family: monospace;" href="mpplu.html">mpplu</a><span
style="font-family: monospace;"> @@ -4183,9 +5996,30 @@ 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> - <small><a style="font-family: monospace;" href="mppprof.html">mppprof</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Lookup individual color values though an MPP
+ profile. Also create MPP gamut files/views. <br>
+ <small><a style="font-family: monospace;" href="mppprof.html">mppprof</a><span
style="font-family: monospace;"> @@ -4227,15 +6061,35 @@ 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="file:///D:/src/argyll/doc/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> - <small><a style="font-family: monospace;" href="printcal.html">printcal</a><span + + + + + + + + + + + + + + + + + + + + +
+ </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>
+ <small><a style="font-family: monospace;" href="printcal.html">printcal</a><span
style="font-family: monospace;"> </span></small>Create @@ -4276,8 +6130,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ 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
style="font-family: monospace;"> </span></small><small><big>Create @@ -4319,9 +6194,30 @@ 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> - <small><a style="font-family: monospace;" href="profcheck.html">profcheck</a><span + + + + + + + + + + + + + + + + + + + + +
+ a PS, EPS or TIFF file containing test patch values, ready for
+ printing.</big></small><br>
+ <small><a style="font-family: monospace;" href="profcheck.html">profcheck</a><span
style="font-family: monospace;"> </span></small>Check @@ -4363,13 +6259,34 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - an ICC profile against .ti3 test chart data. <br> - <small><a style="font-family: monospace;" href="refine.html">refine</a><span - style="font-family: monospace;"> - </span></small>Creates an - abstract profile from two chart readings, useful for refining - proofing profiles. <br> - <small><a style="font-family: monospace;" href="revfix.html">revfix</a><span + + + + + + + + + + + + + + + + + + + + +
+ an ICC profile against .ti3 test chart data. <br>
+ <small><a style="font-family: monospace;" href="refine.html">refine</a><span
+ style="font-family: monospace;">
+ </span></small>Creates an
+ abstract profile from two chart readings, useful for refining
+ proofing profiles. <br>
+ <small><a style="font-family: monospace;" href="revfix.html">revfix</a><span
style="font-family: monospace;"> @@ -4411,9 +6328,30 @@ 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> - <small><a style="font-family: monospace;" href="scanin.html">scanin</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Regenerate a device profiles B2A table data by
+ inverting the A2B table. <br>
+ <small><a style="font-family: monospace;" href="scanin.html">scanin</a><span
style="font-family: monospace;"> @@ -4455,10 +6393,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> - <small><a style="font-family: monospace;" href="spec2cie.html">spec2cie</a><span - style="font-family: monospace;"> </span><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Convert a TIFF image of a test chart into
+ .ti3 device values. <br>
+ <small><a style="font-family: monospace;" href="spec2cie.html">spec2cie</a><span
+ style="font-family: monospace;"> </span><span
style="text-decoration: underline; font-family: monospace;"></span></small>Convert @@ -4500,10 +6459,31 @@ 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> - <small><a style="font-family: monospace;" href="specplot.html">specplot</a><span - style="font-family: monospace;"> </span><span + + + + + + + + + + + + + + + + + + + + +
+ spectral .ti3 readings into CIE XYZ or 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> @@ -4545,8 +6525,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ Plot a spectrum (.sp, .cmf, .ccss) and calculate CCT and VCT.<br>
+ <small><a style="font-family: monospace;" href="splitti3.html">splitsti3</a><span
style="font-family: monospace;"> </span></small>Split @@ -4587,9 +6588,30 @@ 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> - <small><a style="font-family: monospace;" href="spotread.html">spotread</a><span + + + + + + + + + + + + + + + + + + + + +
+ a CGATS file (ie. a .ti3) into two parts randomly to verify
+ profiling. <br>
+ <small><a style="font-family: monospace;" href="spotread.html">spotread</a><span
style="font-family: monospace;"> </span></small>Use @@ -4630,9 +6652,30 @@ 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> - <small><a style="font-family: monospace;" href="synthcal.html">synthcal</a><span + + + + + + + + + + + + + + + + + + + + +
+ an instrument to read a single spot color value. <small><a
+ style="font-family: monospace;" href="oeminst.html"></a></small><br>
+ <small><a style="font-family: monospace;" href="synthcal.html">synthcal</a><span
style="font-family: monospace;"> </span></small>Create @@ -4673,9 +6716,30 @@ 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> - <small><a style="font-family: monospace;" href="synthread.html">synthread</a><span + + + + + + + + + + + + + + + + + + + + +
+ a synthetic input, display or output calibration (<a
+ href="File_Formats.html#.cal">.cal</a>)file.<br>
+ <small><a style="font-family: monospace;" href="synthread.html">synthread</a><span
style="font-family: monospace;"> </span><big>Fake @@ -4717,8 +6781,29 @@ 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 + + + + + + + + + + + + + + + + + + + + +
+ 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
style="font-family: monospace;"> @@ -4760,9 +6845,30 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - </span></small>Generate a profiling test target values .ti1 file. - <br> - <small><a style="font-family: monospace;" href="tiffgamut.html">tiffgamut</a><span + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Generate a profiling test target values .ti1 file.
+ <br>
+ <small><a style="font-family: monospace;" href="tiffgamut.html">tiffgamut</a><span
style="font-family: monospace;"> </span></small>Create @@ -4804,14 +6910,6 @@ 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> - <small><a style="font-family: monospace;" href="timage.html">timage</a><span - style="font-family: monospace;"> - </span></small>Create TIFF - test images. <br> - <small><a style="font-family: monospace;" href="txt2ti3.html">txt2ti3</a><span - style="font-family: monospace;"> @@ -4832,6 +6930,15 @@ 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>
+ <small><a style="font-family: monospace;" href="timage.html">timage</a><span
+ style="font-family: monospace;">
+ </span></small>Create TIFF
+ test images. <br>
+ <small><a style="font-family: monospace;" href="txt2ti3.html">txt2ti3</a><span
+ style="font-family: monospace;"> @@ -4852,12 +6959,6 @@ 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> - <font size="-1"><a style="font-family: monospace;" - href="verify.html">verify</a><span style="font-family: - monospace;"> </span></font>Verify @@ -4898,10 +6999,12 @@ 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> - <font size="-1"><a style="font-family: monospace;" - href="viewgam.html">viewgam</a><span style="font-family: +
+ </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>
+ <font size="-1"><a style="font-family: monospace;"
+ href="viewgam.html">viewgam</a><span style="font-family:
monospace;"> </span></font>Convert @@ -4942,9 +7045,30 @@ 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> - <small><a style="font-family: monospace;" href="xicclu.html">xicclu</a><span + + + + + + + + + + + + + + + + + + + + +
+ one or more gamuts into a VRML 3D visualization file. Compute an
+ intersection.<br>
+ <small><a style="font-family: monospace;" href="xicclu.html">xicclu</a><span
style="font-family: monospace;"> @@ -4986,36 +7110,57 @@ 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 table. <br> - <br> - <h2><u><a href="Environment.html">Environment Variables<br> - </a></u></h2> - <span style="text-decoration: underline;"><span style="font-weight: - bold;"></span></span> Performance/memory tuning hints, plus - tweaks for scipting.<br> - <h2><u><a href="Performance.html">Performance Tuning<br> - </a></u></h2> - <span style="text-decoration: underline;"><span style="font-weight: - bold;"></span></span> Performance hints. <br> - <h2><u><a href="Overview.html">Overview</a></u></h2> - Overview of the software and its aims and functionality.<br> - <h2><u><a href="Limitations.html">Limitations</a></u></h2> - Limitations of the current functionality.<br> - <h2><u><a href="Organisation.html">Organization</a></u></h2> - How directories are organized, what they contain. - <h2><u><a href="Source.html">Source</a></u></h2> - Any detailed documentation on how the software works, or what - algorithms it is based on. (Very incomplete.) - <h2><u><a href="MinorTools.html">Minor Tools</a></u></h2> - A very brief description of minor tools and test harnesses. <br> - <br> - <br> - <h2><u><a name="FFormats"></a><a href="File_Formats.html">File - formats that Argyll uses</a></u></h2> - Argyll uses a number of file formats for its operation, some that - are external standards, and some that are unique to Argyll. <br> - <br> + + + + + + + + + + + + + + + + + + + + +
+ </span></small>Lookup individual color values forward or inverted
+ though an ICC profile or CAL table. <br>
+ <br>
+ <h2><u><a href="Environment.html">Environment Variables<br>
+ </a></u></h2>
+ <span style="text-decoration: underline;"><span style="font-weight:
+ bold;"></span></span> Performance/memory tuning hints, plus
+ tweaks for scipting.<br>
+ <h2><u><a href="Performance.html">Performance Tuning<br>
+ </a></u></h2>
+ <span style="text-decoration: underline;"><span style="font-weight:
+ bold;"></span></span> Performance hints. <br>
+ <h2><u><a href="Overview.html">Overview</a></u></h2>
+ Overview of the software and its aims and functionality.<br>
+ <h2><u><a href="Limitations.html">Limitations</a></u></h2>
+ Limitations of the current functionality.<br>
+ <h2><u><a href="Organisation.html">Organization</a></u></h2>
+ How directories are organized, what they contain.
+ <h2><u><a href="Source.html">Source</a></u></h2>
+ Any detailed documentation on how the software works, or what
+ algorithms it is based on. (Very incomplete.)
+ <h2><u><a href="MinorTools.html">Minor Tools</a></u></h2>
+ A very brief description of minor tools and test harnesses. <br>
+ <br>
+ <br>
+ <h2><u><a name="FFormats"></a><a href="File_Formats.html">File
+ formats that Argyll uses</a></u></h2>
+ Argyll uses a number of file formats for its operation, some that
+ are external standards, and some that are unique to Argyll. <br>
+ <br>
<a href="File_Formats.html#.ti1">.ti1</a> @@ -5057,7 +7202,28 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - Device test values <br> + + + + + + + + + + + + + + + + + + + + +
+ Device test values <br>
<a href="File_Formats.html#.ti2">.ti2</a> @@ -5099,7 +7265,28 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - Device test values & chart layout <br> + + + + + + + + + + + + + + + + + + + + +
+ Device test values & chart layout <br>
<a href="File_Formats.html#.ti3">.ti3</a> @@ -5141,11 +7328,32 @@ 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> - <a href="File_Formats.html#.cal">.cal</a> - Device - calibration information. <a href="cal_format.html">Format details.</a><br> + + + + + + + + + + + + + + + + + + + + +
+ Device test values & CIE tristimulus/spectral results <a
+ href="ti3_format.html">Format details.</a><br>
+ <a href="File_Formats.html#.cal">.cal</a>
+ Device
+ calibration information. <a href="cal_format.html">Format details.</a><br>
<a href="File_Formats.html#.cht">.cht</a> @@ -5187,8 +7395,29 @@ 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> + + + + + + + + + + + + + + + + + + + + +
+ Test chart recognition template. <a href="cht_format.html">Format
+ details.</a> <br>
<a href="File_Formats.html#.gam">.gam</a> @@ -5230,7 +7459,28 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - 3D gamut surface description <br> + + + + + + + + + + + + + + + + + + + + +
+ 3D gamut surface description <br>
<a href="File_Formats.html#.sp">.sp</a> @@ -5272,12 +7522,36 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - Illuminant spectral description <br> - <a href="File_Formats.html#.ccmx">.ccmx</a> - Colorimeter Correction Matrix <br> - <a href="File_Formats.html#.ccmx">.ccss</a> - Colorimeter Calibration - Spectral Set <br> + + + + + + + + + + + + + + + + + + + + +
+ Illuminant spectral description <br>
+ <a href="File_Formats.html#.cmf">.cmf</a>
+ Color Matching
+ Functions<br>
+ <a href="File_Formats.html#.ccmx">.ccmx</a>
+ Colorimeter Correction Matrix <br>
+ <a href="File_Formats.html#.ccmx">.ccss</a>
+ Colorimeter Calibration
+ Spectral Set <br>
<a href="File_Formats.html#CGATS">CGATS</a> @@ -5319,7 +7593,28 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - Standard text based data exchange format <br> + + + + + + + + + + + + + + + + + + + + +
+ Standard text based data exchange format <br>
<a href="File_Formats.html#ICC">ICC</a> @@ -5361,7 +7656,28 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - International Color Consortium profile format <br> + + + + + + + + + + + + + + + + + + + + +
+ International Color Consortium profile format <br>
<a href="File_Formats.html#MPP">MPP</a> @@ -5403,7 +7719,28 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - Model device profile format <br> + + + + + + + + + + + + + + + + + + + + +
+ Model device profile format <br>
<a href="File_Formats.html#TIFF">TIFF</a> @@ -5445,7 +7782,28 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - Tag Image File Format raster files. <br> + + + + + + + + + + + + + + + + + + + + +
+ Tag Image File Format raster files. <br>
<a href="File_Formats.html#JPEG">JPEG</a> @@ -5487,8 +7845,29 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - Joint Photographic Experts Group, JPEG File Interchange Format - raster files. <br> + + + + + + + + + + + + + + + + + + + + +
+ Joint Photographic Experts Group, JPEG File Interchange Format
+ raster files. <br>
<a href="File_Formats.html#VRML">VRML</a> @@ -5530,41 +7909,62 @@ href="http://www.google.com/search?hl=en&q=windows+command+prompt+tutorial"> - Virtual Reality Modelling Language 3D file format. <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"> -<!-- -// Comment -var v1 = ".com" -var v2 = "argyllcms" -var v3 = "Graeme" -var v4 = "@" -var v5 = "mailto:" -var v6 = v5 + v3 + v4 + v2 + v1 -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> - - </body> -</html> + + + + + + + +
+ Virtual Reality Modelling Language 3D file format. <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">
+
+<!--
+
+// Comment
+
+var v1 = ".com"
+
+var v2 = "argyllcms"
+
+var v3 = "Graeme"
+
+var v4 = "@"
+
+var v5 = "mailto:"
+
+var v6 = v5 + v3 + v4 + v2 + v1
+
+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>
+
+ </body>
+</html>
diff --git a/doc/ChangesSummary.html b/doc/ChangesSummary.html index 94e3aa3..82d083f 100644 --- a/doc/ChangesSummary.html +++ b/doc/ChangesSummary.html @@ -2,7 +2,7 @@ <html> <head> <meta http-equiv="Content-Type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> <meta name="description" content="Root of Argyll CMS documentation"> <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I) @@ -16,6 +16,187 @@ <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.2 -> V1.6.3] 26th January 2014</h1> + <ul> + <li>Added ProPhoto.icm and ProPhotoLin.icm to ref profiles.</li> + <li>Fix bug in xicclu -py conversion.</li> + <li>Added code to minimize ICC rounding error on matrix profile + white point accuracy. Re-generated all reference profiles with + this change.</li> + <li>Changed i1d3 driver to completely ignore any EEPROM checksum + errors for non "A-01" rev. instruments.</li> + <li>Made transplot handle RGB->RGB device link.</li> + <li>Removed colprof -y option. Use "profcheck -v2" instead, as it + is more developed.</li> + <li>Fixed bug in dispcal - it was not using the final measurement + pass to update the calibration curves.</li> + <li>Fixed bug in spotread, dispcal & dispread for CCSS capable + instruments where refresh display types was being ignored if a + custom observer was used, and/or the custom observer as being + ignored, and/or a CCMX was being ignored. Changed instlib + semantics for inst_opt_set_ccss_obs :- this is now set + immediately, and applied also to any subsequent set_disptype() + or col_cal_spec_set().</li> + <li>Renamed verify to colverify to avoid clash with MSWin program + of the same name. Made it print the patch location for -v2 if it + is present in the file.</li> + <li>Changed targen to ensure that -V and -p options effects are + reflected in the resulting expected CIE values of the .ti1 file.</li> + <li>Changed targen so that -V parameter also affects single + channel, grey wedge, grid & body centered grid point + distribution.</li> + <li>Changed colprof to deal with variable grid distribution in a + more neuanced way, to reduce overshoot artifacts when the -V + parameter is used.</li> + <li>Changed colprof to used a power_like function for the grid + distribution shape from the -V parameter, so as to avoid issues + with a power curve infinte slope near zero.</li> + <li>Changed colprof to used a scaled down value of the targen -V + parameter as the default for its -V parameter. Documentation now + recommends more moderate values for -V.</li> + <li>Added a special case to collink for RGB video input encoding + to (attempt) to fine tune the black point to compensate for it + (probably) not falling on a cLUT grid point. & out encoding</li> + <li>Tweaked dispcal to try and improve accuracy of black point + calibration.</li> + <li>Switch dispread to use NoClamp readings, so that average black + point value is not biased.</li> + <li>Fixed bug introduced into 1.6.2 oeminst that prevents .ccss + files being installed.<br> + </li> + </ul> + <h1>[V1.6.1 -> V1.6.2] 18th November 2013</h1> + <ul> + <li> Added "dark region emphasis" -V parameter to targen and + colprof, in an attempt to improve the accuracy of display + profiles intended for use with video. This should improve the + subsequent black point accuracy of the profile.</li> + <li>Fixed bug and tweaked dispcal black point optimization to err + on the black side. Added -v3 for even more debugging + information.</li> + <li>Changed i1d3 driver to be more forgiving of EEProm checksum + calculation, so that it works with the latest release "A-02" + rev. i1 display pro & colormunki display instruments, + as well as improving its robustness in the face of errors.</li> + <li>Fixed race condition bug in OS X HID driver. This fixes + occassional problem with i1d3, and also solves problem with the + ColorHug on OS X. </li> + <li>Fixed problem with TV encoded output and dispread -E -k/-K.</li> + <li>Fixed minor bug in DE94 in icclib.</li> + <li>Fixed major bug in illumread - result was being corrupted.</li> + <li>Fixed "edges don't match" bug in printarg when -iCM -h -s/-S + used.</li> + <li>Fix bug in -H flag in ccxxmake, chartread, dispcal, dispread, + illumread & spotread so that it works once again.</li> + <li> <br> + </li> + </ul> + <h1>[V1.6.0 -> V1.6.1] 30th September 2013</h1> + <ul> + <li>Fix bug in "average -m"<br> + </li> + <li>Fix oeminst to work with a wider range of i1d3 install files.</li> + <li>Fix ColorMunki reflective measurement accuracy, particularly + for reflective readings. This has been poor since V1.5</li> + <li>Fix bug in using DTP94 on Apple OS X introduced in V1.5</li> + <li>Fix MadVR connect code to look for appropriate 32 bit or 64 + bit .dll.</li> + <li>Improve MSWin system driver installation by creating valid + ArgyllCMS.cat file to match ArgyllCMS.inf. This eliminates the + need to "Disable Driver Signature Enforcement", as well as + allowing installation on MSWin 8.1.<br> + </li> + </ul> + <h1>[V1.5.1 -> V1.6.0] 16th August 2013</h1> + <ul> + <li>Added support for <b>JETI</b> specbos 1211 and 1201 (Thanks + to JETI for their support!)</li> + <li>Added Video profiling & 3dLut creation support for eeColor + and MadVR. See video section in tutorial for pointers to + relevant changes to tools. This includes support for MadTPG + + various Video standard ICC profiles + verification workflow.<br> + </li> + <li>Linux profile installation will use <b>colord</b> if + libcolordcompat.so is present on system.</li> + <li>Fix <b>ColorHug</b> driver so that it is backwards compatible + with FW 1.1.8</li> + <li>Made sure that MSWin test colors are not color managed. This + may affect Vista, Win7 and Win8.</li> + <li>Changed spectro/dispwin.c so that null transform color + matching is used for displaying test patches on OS X >= 10.6. + This should fix calibrating/profiling secondary displays on > + OS X 10.6. Note that the 32 bit 10.4 binary will still have + problems on > OS X 10.6.</li> + <li>Changed <b>instlib API</b> ambient XYZ and spectral units to + Lux. In previous versions of instlib they were Lux/pi.</li> + <li>For those instruments that support it, made ambient readings + honor refresh mode measurements, to improve repeatability when + measuring regularly flickering light sources. (specbos, i1d3, + i1disp).</li> + <li>Changed spotread -ew mode to be Bradford chromatic transform + rather than XYZ scaling, to better match Argyll ICC abs. vs. + rel.</li> + <li>Added support to xicclu to lookup colors though CAL files, + both forward and backwards. Will also plot CAL file contents + using -g.</li> + <li>Added -Y R:rate option to spotread, dispcal, dispread & + ccxxmake to allow setting a chosen display refresh rate. This + can be used with the Colormunki display, as well as situations + in which refresh rate measurement is not reliable.</li> + <li>By default printtarg will create PS and EPS files with a CUPS + job ticket to disable color management. Use the -U flag to + disable this.</li> + <li>Added display update delay calibration support to i1pro and + ColorMunki (just like i1disp3), to improve measurement times.</li> + <li>Changed dispcal & dispread so that they wait up to 0.5 + seconds when reading dark patches after light ones to allow for + display fall time. Added patch order optimization for + display patch sets in targen to minimize the extra time.</li> + <li>Changed dispwin daemon loader mode option from -E to -X. Added + -E option to encode test patch colors in Video 16-235 range.</li> + <li>Changed dispcal verify option from -E to -z. Added -E option + to encode test patch colors in Video 16-235 range.</li> + <li>Added -E option to to dispread to encode test patch colors in + Video 16-235 range.</li> + <li>Changed CIECAM02 Flare model to distinguish between Flare from + the image itself, and Glare from ambient light. This allows + scaling Glare with ambient automatically. Changed enumerated + viewing conditions for new Flare/Glare settings, changed all to + Flareless to improve dark image behavior, while retaining Glare + modelling. Tweaked brightness and ambient values.</li> + <li>Improved i1pro hi-res mode to improve accuracy.</li> + <li>Added Body Centered Cubic grid option to targen.</li> + <li>Added -Yn flag to dispcal and dispread, which skips asking the + user to place the instrument on the measuring spot.</li> + <li>Improve robustness of i1d3 display update measurement code.</li> + <li>Added support for applying calibration curves in collink.</li> + <li>Changed spotread so that it won't fall back to emissive spot + mode if an ambient reading is requested.</li> + <li>Turned off B2A table clip map smoothing, as it seems to + introduce reversals for some data sets, and provides little + benefit.</li> + <li>Fixed crash in ucmm/ucmm.c when loading certain profiles using + dispwin (thanks to Torok Edwin).</li> + <li>Fixed gamut mapping intent "rl" to really use relative L*a*b*</li> + <li>Fix bug in cicam02 in V1.5.0 that causes some mapping problems + in the red for collink -ir or -ila. </li> + <li>Changed cctiff so that it does lossless JPEG copy when there + is no color transformation. This makes it more useful for + embedding a profile.</li> + <li>Fix xicclu so that it works with device links.</li> + <li>Fixed bug in shaper/matrix profile curves that caused random + bumpy black behaviour (shaper curve optimization local minimum + problem).</li> + <li>Don't add colorant tag to .tiff files in cctiff unless it is a + non-standard space, as Photoshop will barf on such files.</li> + <li>Fix bug with Spyder not being able to break out of dispcal + adjustment loop.</li> + <li>Fix bug in xicc/xicclu, -K flag not being recognised.</li> + <li>Fix bug in xicc/xmatrix.c introduced in V1.5 that prevents + matrix only profiles from being created.</li> + <li>libusb 1.0 is now deprecated in favor of native USB drivers.<br> + </li> + </ul> <h1>[V1.5.0 -> V1.5.1] 8th March 2013</h1> <ul> <li>Fix spectro/instlib.ksh and standalone instlib build.</li> @@ -689,6 +870,10 @@ + + + + </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> @@ -718,6 +903,10 @@ + + + + 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/ColorHug.jpg b/doc/ColorHug.jpg Binary files differnew file mode 100644 index 0000000..6c5d16a --- /dev/null +++ b/doc/ColorHug.jpg diff --git a/doc/ColorManagement.html b/doc/ColorManagement.html index fa7b656..50505cd 100644 --- a/doc/ColorManagement.html +++ b/doc/ColorManagement.html @@ -96,11 +96,11 @@ down by the International Commission on Illumination (CIE) in 1931 with the establishment of the CIE 1931 <span style="font-weight: bold;">XYZ</span> color space. This provides a means of predicting - what light spectra will match in color for a Standard Observer, who - represents the typical response of the Human eye under given viewing - conditions. Such a color space is said to be <span - style="font-weight: bold;">Device Independent</span> since it is - not related to a particular technological capture or reproduction + what light spectra will be a color match to the Standard Observer. + The Standard Observer represents the typical response of the Human + eye under given viewing conditions. Such a color space is said to be + <span style="font-weight: bold;">Device Independent</span> since it + is not related to a particular technological capture or reproduction device. There are also closely related color-spaces which are direct transformations of the XYZ space, such as the <span style="font-weight: bold;">L* a* b*</span> space which is a more @@ -150,8 +150,8 @@ <br> A Device Link profile provides a transformation from one Device space to another. It is typically the result of - linking two device profiles, ie. Device A -> PCS -> Device B, - resulting in a direct Device A -> Device B transformation.<br> + linking two device profiles, ie. Device 1 -> PCS -> Device 2, + resulting in a direct Device 1 -> Device 2 transformation.<br> <br> <span style="font-weight: bold;">Abstract</span><br> <br> @@ -234,11 +234,11 @@ 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) can be modeled using (for example) using CIECAM02 to modify - XYZ values.<br> + flare/glare) can be modeled using (for example) using 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, + Standard Observer to convert spectral light values into XYZ values, but in practice every observer may have slightly different spectral sensitivities due to biological differences, including aging. (People with color deficient vision may have radically different @@ -252,7 +252,7 @@ of reflective prints from the light source used to view them, by characterizing a prints color by it's reflectance. This is very convenient, since a print will probably be taken into many different - lighting situations, but if the color is reduced to XYZ reflectance + lighting situations, but if the color is reduced to XYZ reflectance, the effect of the detailed interaction between the spectra of the light source and print will lead to inaccuracies.<br> <br> diff --git a/doc/Environment.html b/doc/Environment.html index a319513..66dbbe2 100644 --- a/doc/Environment.html +++ b/doc/Environment.html @@ -62,14 +62,17 @@ <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) 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 + 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> @@ -101,6 +104,7 @@ <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 style="font-weight: bold;">XDG_CACHE_HOME</span> environment variable to place per instrument calibration information (Eye-One diff --git a/doc/File_Formats.html b/doc/File_Formats.html index d6e38c5..aa0f4f4 100644 --- a/doc/File_Formats.html +++ b/doc/File_Formats.html @@ -3,7 +3,7 @@ <head> <title>Argyll File Formats</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> @@ -19,6 +19,7 @@ <a href="#.cht">.cht</a> <br> <a href="#.gam">.gam</a> <br> <a href="#.sp">.sp</a><br> + <a href="File_Formats.html#.cmf">.cmf</a><br> <a href="#CGATS">CGATS</a><br> <a href="#ICC">ICC</a><br> <a href="#MPP">MPP</a><br> @@ -89,11 +90,17 @@ <h2><a name=".sp"></a>.sp</h2> Spectral illuminant description. This is an ASCII text, <a href="File_Formats.html#CGATS">CGATS</a>, Argyll specific format, - used to hold a spectral description of an illuminant. Typically it - is used to record a custom illuminant, for use in - computing Fluorescent Whitening Agent compensation for + used to hold one or more spectral descriptions of an illuminant or + color. Typically it is used to record a custom illuminant, for use + in computing Fluorescent Whitening Agent compensation for reflective samples, as well as computing CIE tristimulus values from spectral samples.<br> + <h2><a name=".cmf"></a>.cmf</h2> + Color Matching Functions. This is an ASCII text, <a + href="file:///D:/src/argyll/doc/File_Formats.html#CGATS">CGATS</a>, + Argyll specific format, used to hold three spectral response curves + that define a tristimulus observer. The format is the same as a .sp + file.<i></i> <h2><a name=".ccmx"></a>.ccmx</h2> Colorimeter Correction Matrix. This is an ASCII text, <a href="File_Formats.html#CGATS">CGATS</a>, Argyll specific format, @@ -112,7 +119,8 @@ tuned for a particular display. The file contains a description of the display, the display technology type, the type of spectrometer used for taking the readings. See <a href="oeminst.html">oeminst</a> - and <a href="ccxxmake.html">ccxxmake</a> for more information.<br> + and <a href="ccxxmake.html">ccxxmake</a> for more information. The + format is similar to a .sp file.<br> <h3><a name="CGATS"></a>CGATS</h3> CGATS.5 Data Exchange Format, from the Annex J, of the ANSI CGATS.5-1993 standard.<br> diff --git a/doc/Installing_Linux.html b/doc/Installing_Linux.html index ad2cacc..608ff7d 100644 --- a/doc/Installing_Linux.html +++ b/doc/Installing_Linux.html @@ -44,11 +44,15 @@ + + the <span style="font-weight: bold;">/etc/rc.local</span> startup script. You may also have to run <span style="font-weight: bold;">xset + + 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> @@ -159,10 +163,19 @@ href="#serial">Serial instrument access:</a></h5> <a href="#serial">All</a><br> <br> - <span style="font-weight: bold;">NOTE:</span> That <span - style="font-weight: bold;">libmtp</span> has been known to - interfere with device access, particularly the Spyder 3. You - probably want to disable this library (look in udev).<br> + <span style="font-weight: bold;">NOTE:</span> That <b>mtp-probe</b> + / <span style="font-weight: bold;">libmtp</span> been known + to interfere with device access, particularly the Spyder 3 and + DTP94. Recent versions of the libmtp should ignore any instrument + marked as COLOR_MEASUREMENT_DEVICE by the + /etc/udev/rules.d/55-Argyll.rules file, but for older systems you + 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> <br> <span style="font-weight: bold;"></span> <hr style="width: 100%; height: 2px;"> @@ -206,6 +219,8 @@ + + <b>/sbin/udevcontrol reload_rules</b> or <span style="font-weight: bold;">/sbin/udevstart</span> or reboot to get the new file noticed.<br> @@ -387,6 +402,8 @@ instruments + + access using hotplug:<br> </span></h5> Under <span style="font-weight: bold;">much older versions of Linux</span>, @@ -542,6 +559,8 @@ instruments + + access:</span><br> </h5> If you have a serial instrument then you may find that by default diff --git a/doc/Installing_MSWindows.html b/doc/Installing_MSWindows.html index 9079db0..c08e16d 100644 --- a/doc/Installing_MSWindows.html +++ b/doc/Installing_MSWindows.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 Microsoft Windows</title> @@ -60,9 +60,9 @@ <br> So if the current value of PATH is "%SystemRoot%\system32;%SystemRoot%" and you unpacked Argyll version - 1.5.1 in <span style="font-weight: bold;">d:\bin\</span>, then you + 1.6.3 in <span style="font-weight: bold;">d:\bin\</span>, then you would modify PATH to be - "%SystemRoot%\system32;%SystemRoot%;d:\bin\Argyll_V1.5.1\bin", - + "%SystemRoot%\system32;%SystemRoot%;d:\bin\Argyll_V1.6.3\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 @@ -112,25 +112,31 @@ have to disable all of them. Reboot after changing settings.<br> <br> <hr style="width: 100%; height: 2px;"> - <h3><span style="color: rgb(51, 153, 153);">Serial Instruments:</span><br> + <h3><u><font color="#009900">Serial Instruments:</font></u><br> </h3> If you are using a serial connected instrument, then there is nothing special to do to enable this.<br> - <h3><span style="color: rgb(51, 153, 153);">USB Instruments:</span></h3> + <h3><font color="#ff6600"><u>USB Instruments:</u></font></h3> If you are using a USB connected instrument, then suitable <span - style="font-weight: bold;">USB drivers</span> may need to be - installed.<br> + style="font-weight: bold;">USB system drivers</span> may need to + be installed.<br> <span style="font-weight: bold;"><br> - </span>Note that the <span style="font-weight: bold;">Huey</span> - and <span style="font-weight: bold;">i1 Display Pro</span> and <span - style="font-weight: bold;">ColorMunki Display</span> colorimeter - appears as an HID (USB Human Interface Device Class) device, and - hence will be assigned to the default MSWindows HID driver. You - therefore <span style="font-weight: bold; text-decoration: - underline;">don't need</span> to install an Argyll <span - style="font-weight: bold;">usb</span> driver for these - instruments, although it is possible to select the libusb0.sys - driver as an alternative to the default HID driver.<br> + </span>Note that the <span style="font-weight: bold;">Huey</span>, + <span style="font-weight: bold;">i1 Display Pro</span>, <span + style="font-weight: bold;">ColorMunki Display</span> and <b>ColorHug</b> + colorimeter appears as an HID (USB Human Interface Device Class) + device, and hence will be assigned to the default MSWindows HID + driver. You therefore <span style="font-weight: bold; + text-decoration: underline;">don't need</span> to install an + Argyll <span style="font-weight: bold;">usb</span> system driver + for these instruments, although it is possible to select the + libusb0.sys driver as an alternative to the default HID driver.<br> + <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 + 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> Jump to your operating system version:<br> <br> @@ -158,13 +164,7 @@ <br> <span style="text-decoration: underline;">To install the Argyll driver for the first instrument:</span><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> + (Plug in instrument)<br> Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager -><br> Other Devices -> <instrument being @@ -191,12 +191,7 @@ <br> <span style="text-decoration: underline;">To install the Argyll Driver:</span><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> + (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 d3f9057..8a17291 100644 --- a/doc/Installing_OSX.html +++ b/doc/Installing_OSX.html @@ -1,58 +1,59 @@ -<!DOCTYPE HTML PUBLIC "-//w3c//dtd html 4.0 transitional//en"> +<!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>.<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 -executables from your command line environment, by editing your <span - style="font-weight: bold;">.profile</span> file.<br> -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 the following line to your .path file<br> -<br> - PATH=$PATH:$HOME/Argyll_V1.1.1/bin<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>>. + <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 @@ -60,224 +61,253 @@ 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> - <span style="text-decoration: underline;">Item +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> + <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 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.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 + + + + 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> -<h3><a name="HCFR"></a>HCFR Colorimeter</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> - - -<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> + + + + 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> + + + + + <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/JETI_1211.jpg b/doc/JETI_1211.jpg Binary files differnew file mode 100644 index 0000000..efbf291 --- /dev/null +++ b/doc/JETI_1211.jpg diff --git a/doc/Performance.html b/doc/Performance.html index b69f5ae..340cec0 100644 --- a/doc/Performance.html +++ b/doc/Performance.html @@ -1,106 +1,142 @@ <!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 Performance Tuning</title> -</head> -<body> -<h2> -<u>Performance Tuning</u></h2> -<br> -Some operations in Argyll can be particularly slow, so it is worth -examining ways of improving performance, or trading memory consumption -for performance.<br> -<h3>Creating Device Links and Profiles<br> -</h3> -In creating device links or the B2A tables of profiles, the execution -time is often dominated by the inversion of forward -color lookup values. An in-memory cache is employed to speed up this -operation, by keeping computed values in case they can be used more -than once. The amount of memory used for caching these values is -pre-set within the inversion code, and by default is set to use half of -the available RAM on the system, with a minimum of 50 Mbytes.<br> -<br> -The reverse cache size can be changed by setting an environment -variable -<span style="font-weight: bold;">ARGYLL_REV_CACHE_MULT</span> to a -number greater or less than than 1.0 This will multiply the size of the -cache by that number (i.e. 1.5 would increase the cache size by 50%, -0.5 would halve it).<br> -<br> -If you find that <span style="font-weight: bold;">colprof</span> -or <span style="font-weight: bold;">collink</span> -are working very slowly, but that your CPU's are nearly idle, then this -is a sign of disk swapping, and that too much memory is being -requested. This can be because other applications are also using -memory, or Argyll's default setting tries to use more memory than is -actually available. You can try shutting down other applications when -this happens, or you can <span style="font-weight: bold;">lower</span> -the amount of memory Argyll uses by setting <span - style="font-weight: bold;">ARGYLL_REV_CACHE_MULT</span> to a value -less than 1.0 (ie. try 0.5). <br> -<br> -If you have a lot of memory available, you can try increasing the -cache size to use more of the available RAM (particularly if you get a -"Warning - Reverse Cell Cache exhausted, -processing in chunks" message during processing), but if you set it to -a value too near 2.0 you risk disk swapping, which can slow progress to -a crawl.<br> -<br> -If you have a lot of memory available, then a second adjustment that -can make a great difference to the time taken -in creating B2A tables is the resolution of the inverse lookup -acceleration grid. The finer the grid, the less searching is needed to -locate the input colorspace values that -correspond to a target output color value, but the greater the memory -used in this -structure, and the greater the setup time needed to initialize the -acceleration grid. The <span style="font-weight: bold;">ARGYLL_REV_ACC_GRID_RES_MULT</span> -environment variable can alter the default resolution by a scale -factor. A value of 0.5 for instance, would halve the resolution -(typically meaning 1/8 th. the total number of grid entries and -memory), while a value of 2.0 would double it, typically resulting in 8 -times the memory usage. Increasing the resolution too much will reduce -the available memory for the reverse cache, and greatly increase setup -time.<br> -<br> -<h3>Setting an environment variable:</h3> -<br> -To set an environment variable an MSWindows DOS shell, either use set, -e.g.;<br> -<br> - set ARGYLL_REV_CACHE_MULT=1.5<br> -<br> -which will set the value for that session, or set it in<br> -<br> -Control Panel->System->Advanced->Environment Variables..<br> -<br> -in either user or system variables.<br> -<br> -For OS X or Linux, the exact procedure will depend on the shell you are -running, but<br> -is usually something like:<br> -<br> - export ARGYLL_REV_CACHE_MULT=1.5<br> -or<br> - set ARGYLL_REV_CACHE_MULT=1.5<br> -or<br> - ARGYLL_REV_CACHE_MULT=1.5<br> -<br> -and may need separately exporting, something like:<br> -<br> - export ARGYLL_REV_CACHE_MULT<br> -<br> -Generally it should be configured in the shell start-up script, -if you -want the setting to be used<br> -for every session.<br> -<br> -<br> -</body> + <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 Performance Tuning</title> + </head> + <body> + <h2> + <u>Performance Tuning</u></h2> + <br> + Some operations in Argyll can be particularly slow, so it is worth + examining ways of improving performance, or trading memory + consumption + for performance.<br> + <h3>Creating Device Links and Profiles<br> + </h3> + In creating device links or the B2A tables of profiles, the + execution + time is often dominated by the inversion of forward + color lookup values. An in-memory cache is employed to speed up this + operation, by keeping computed values in case they can be used more + than once. The amount of memory used for caching these values is + pre-set within the inversion code, and by default is set to use half + of + the available RAM on the system, with a minimum of 50 Mbytes.<br> + <br> + The reverse cache size can be changed by setting an environment + variable + <span style="font-weight: bold;">ARGYLL_REV_CACHE_MULT</span> to a + number greater or less than than 1.0 This will multiply the size of + the + cache by that number (i.e. 1.5 would increase the cache size by 50%, + 0.5 would halve it).<br> + <br> + If you find that <span style="font-weight: bold;">colprof</span> + or <span style="font-weight: bold;">collink</span> + are working very slowly, but that your CPU's are nearly idle, then + this + is a sign of disk swapping, and that too much memory is being + requested. This can be because other applications are also + using + memory, or Argyll's default setting tries to use more memory than is + actually available. You can try shutting down other applications + when + this happens, or you can <span style="font-weight: bold;">lower</span> + the amount of memory Argyll uses by setting <span + style="font-weight: bold;">ARGYLL_REV_CACHE_MULT</span> to a value + less than 1.0 (ie. try 0.5). <br> + <br> + If you have a lot of memory available, you can try increasing the + cache size to use more of the available RAM (particularly if you get + a + "Warning - Reverse Cell Cache exhausted, + processing in chunks" message during processing), but if you set it + to + a value too near 2.0 you risk disk swapping, which can slow progress + to + a crawl.<br> + <br> + If you have a lot of memory available, then a second adjustment that + can make a great difference to the time taken + in creating B2A tables is the resolution of the inverse lookup + acceleration grid. The finer the grid, the less searching is needed + to + locate the input colorspace values that + correspond to a target output color value, but the greater the + memory + used in this + structure, and the greater the setup time needed to initialize the + acceleration grid. The <span style="font-weight: bold;">ARGYLL_REV_ACC_GRID_RES_MULT</span> + environment variable can alter the default resolution by a scale + factor. A value of 0.5 for instance, would halve the resolution + (typically meaning 1/8 th. the total number of grid entries and + memory), while a value of 2.0 would double it, typically resulting + in 8 + times the memory usage. Increasing the resolution too much will + reduce + the available memory for the reverse cache, and greatly increase + setup + time.<br> + <br> + <h3>Setting an environment variable:</h3> + <br> + To set an environment variable an MSWindows DOS shell, either use + set, + e.g.;<br> + <br> + set ARGYLL_REV_CACHE_MULT=1.5<br> + <br> + which will set the value for that session, or set it in<br> + <br> + Control Panel->System->Advanced->Environment Variables..<br> + <br> + in either user or system variables.<br> + <br> + You can examine individual variables using<br> + <br> + echo %VARIABLE_NAME%<br> + <br> + or see all of them using<br> + <br> + set<br> + <br> + <br> + For OS X or Linux, the exact procedure will depend on the shell you + are + running, but<br> + is usually something like:<br> + <br> + export ARGYLL_REV_CACHE_MULT=1.5<br> + or<br> + set ARGYLL_REV_CACHE_MULT=1.5<br> + or<br> + ARGYLL_REV_CACHE_MULT=1.5<br> + <br> + and may need separately exporting, something like:<br> + <br> + export ARGYLL_REV_CACHE_MULT<br> + <br> + Generally it should be configured in the shell start-up + script, + if you + want the setting to be used<br> + for every session.<br> + <br> + You can examine individual variables using<br> + <br> + echo $VARIABLE_NAME<br> + <br> + or see all of them using<br> + <br> + set<br> + <br> + <br> + <br> + </body> </html> diff --git a/doc/Scenarios.html b/doc/Scenarios.html index 3995d21..e82a8a4 100644 --- a/doc/Scenarios.html +++ b/doc/Scenarios.html @@ -1,152 +1,190 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<html> - <head> - <title>Argyll Usage Scenarios</title> - <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> - </head> - <body> - <h2><u>Typical usage Scenarios and Examples</u></h2> - Choose a task from the list below. For more details on alternative - options, follow the links to the individual tools being used.<br> - <br> - Note that by default it is assumed that ICC profile have the file - extension <span style="font-weight: bold;">.icm</span>, but that on - Apple OS X and Unix/Linux platforms, the <span style="font-weight: - bold;">.icc</span> extension is expected and should be used.<br> - <h4><a href="#PM1">Profiling Displays</a></h4> - <h4> <a href="#PM1a">Checking you can access your - display<br> - </a></h4> - <h4> <a href="#PM1b">Adjusting and Calibrating a - displays</a></h4> - <h4> <a href="#PM1c">Adjusting, calibrating and - profiling in one step<br> - </a><span style="font-weight: bold;"></span><span - style="font-weight: bold;"></span><span style="text-decoration: - underline;"></span></h4> - <h4> <a href="#PM2">Creating display test values</a></h4> - <h4> <a href="#PM3">Taking readings from a - display</a></h4> - <h4> <a href="#PM4">Creating a display profile</a></h4> - <h4> <span style="text-decoration: underline;"></span><a - href="#PM5">Installing a display profile</a></h4> - <h4> <span style="text-decoration: underline;"></span><a - href="#PM6">Expert tips when measuring displays</a></h4> - <h4> <span style="text-decoration: underline;"></span><a - href="#PM7">Calibrating and profiling a display that doesn't - have VideoLUT access.</a></h4> - <h4><br> - <a href="#PS1">Profiling Scanners and other input devices such as - cameras<br> - </a></h4> - <h4> <a href="#PS2">Types of test charts</a></h4> - <h4> <a href="#PS3">Taking readings from a - scanner</a></h4> - <h4> <a href="#PS4">Creating a scanner profile</a></h4> - <h4><br> - <a href="#PP1">Profiling Printers</a></h4> - <h4> <a href="#PP2">Creating a print profile - test chart</a></h4> - <h4> <a href="Scenarios.html#PP2b">Printing a - print profile test chart</a></h4> - <h4> <a href="#PP3">Reading a print test chart - using an instrument</a></h4> - <h4> <a href="#PP4">Reading a print test chart - using a scanner</a></h4> - <h4> </h4> - <h4> <a href="#PP5">Creating a printer profile<br> - </a></h4> - <h4> <a href="#PP6">Choosing a black generation - curve</a></h4> - <br> - <h4><a href="Scenarios.html#PC1">Calibrating Printers</a></h4> - <h4> <a href="Scenarios.html#PC2">Calibrated - print workflows</a></h4> - <h4> <a href="Scenarios.html#PC3">Creating a - print calibration test chart</a></h4> - <h4> </h4> - <h4> <a href="Scenarios.html#PC4">Creating a - printer calibration<br> - </a></h4> - <h4> <a href="Scenarios.html#PC5">Using a printer - calibration</a></h4> - <h4> <a href="#PC6">How profile ink limits are - handled when calibration is being used<br> - </a></h4> - <h4><br> - <a href="#LP1">Linking Profiles</a></h4> - <h4><br> - <a href="#TR1">Transforming colorspaces of raster files</a></h4> - <br> - <hr style="width: 100%; height: 2px;"><br> - <h3><a name="PM1"></a>Profiling Displays</h3> - Argyll supports adjusting, calibrating and profiling of displays - using one of a number of instruments - see <a - href="instruments.html">instruments</a> for a current list. - Adjustment and calibration are prior steps to profiling, in which - the display is adjusted using it's screen controls, and then - per channel lookup tables are created to make it meet a well behaved - response of the desired type. The process following that of - creating a display profile is then similar to that of all other - output devices :- first a set of device colorspace test values needs - to be created to exercise the display, then these values need to be - displayed, while taking measurements of the resulting colors using - the instrument. Finally, the device value/measured color values need - to be converted into an ICC profile.<br> - <br> - <h3><a name="PM1a"></a>Checking you can access your display<br> - </h3> - You might first want to check that you are accessing and can - calibrate your display. You can do this using the <a - href="dispwin.html">dispwin</a><span style="font-weight: bold;"></span> - tool<span style="font-weight: bold;">.</span> If you just run <span - style="font-weight: bold;">dispwin</span> it will create a test - window and run through a series of test colors before checking that - the VideoLUT can be accessed by the display. If you invoke the usage - for <span style="font-weight: bold;">dispwin</span> (by giving it - an unrecognized option, e.g. <span style="font-weight: bold;">-?</span>) - then it will show a list of available displays next to the <span - style="font-weight: bold;"><span style="font-weight: bold;">-d</span></span> - flag. Make sure that you are accessing the display you intend to - calibrate and profile, and that the VideoLUT is effective (the <span - style="font-weight: bold;">-r</span> flag can be used to just run - the VideoLUT test). You can also try clearing the VideoLUTs using - the <span style="font-weight: bold;">-c</span> flag, and loading a - deliberately strange looking calibration <span style="font-weight: - bold;">strange.cal</span> that is provided in the Argyll <span - style="font-weight: bold;">ref</span> directory.<br> - <br> - Note that calibrating and/or profiling <span style="font-weight: - bold;">remote</span> displays is possible using X11 or a web - browser (see <span style="font-weight: bold;">-d</span> option of - dispcal and dispread), or by using some external program to send - test colors to a display (see <span style="font-weight: bold;">-C</span> - and <span style="font-weight: bold;">-M</span> options of dispcal +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+ <head>
+ <title>Argyll Usage Scenarios</title>
+ <meta http-equiv="content-type" content="text/html;
+ charset=windows-1252">
+ </head>
+ <body>
+ <h2><u>Typical usage Scenarios and Examples</u></h2>
+ Choose a task from the list below. For more details on alternative
+ options, follow the links to the individual tools being used.<br>
+ <br>
+ Note that by default it is assumed that ICC profile have the file
+ extension <span style="font-weight: bold;">.icm</span>, but that on
+ Apple OS X and Unix/Linux platforms, the <span style="font-weight:
+ bold;">.icc</span> extension is expected and should be used.<br>
+ <h4><a href="#PM1">Profiling Displays</a></h4>
+ <h4> <a href="#PM1a">Checking you can access your
+ display<br>
+ </a></h4>
+ <h4> <a href="#PM1b">Adjusting and Calibrating a
+ displays</a></h4>
+ <h4> <a href="#PM1c">Adjusting, calibrating and
+ profiling in one step<br>
+ </a><span style="font-weight: bold;"></span><span
+ style="font-weight: bold;"></span><span style="text-decoration:
+ underline;"></span></h4>
+ <h4> <a href="#PM2">Creating display test values</a></h4>
+ <h4> <a href="#PM3">Taking readings from a
+ display</a></h4>
+ <h4> <a href="#PM4">Creating a display profile</a></h4>
+ <h4> <span style="text-decoration: underline;"></span><a
+ href="#PM5">Installing a display profile</a></h4>
+ <h4> <span style="text-decoration: underline;"></span><a
+ href="#PM6">Expert tips when measuring displays</a></h4>
+ <h4> <span style="text-decoration: underline;"></span><a
+ href="#PM7">Calibrating and profiling a display that doesn't
+ have VideoLUT access.</a></h4>
+ <h4><br>
+ <a href="#PS1">Profiling Scanners and other input devices such as
+ cameras<br>
+ </a></h4>
+ <h4> <a href="#PS2">Types of test charts</a></h4>
+ <h4> <a href="#PS3">Taking readings from a
+ scanner</a></h4>
+ <h4> <a href="#PS4">Creating a scanner profile</a></h4>
+ <h4><br>
+ <a href="#PP1">Profiling Printers</a></h4>
+ <h4> <a href="#PP2">Creating a print profile
+ test chart</a></h4>
+ <h4> <a href="Scenarios.html#PP2b">Printing a
+ print profile test chart</a></h4>
+ <h4> <a href="#PP3">Reading a print test chart
+ using an instrument</a></h4>
+ <h4> <a href="#PP4">Reading a print test chart
+ using a scanner</a></h4>
+ <h4> </h4>
+ <h4> <a href="#PP5">Creating a printer profile<br>
+ </a></h4>
+ <h4> <a href="#PP6">Choosing a black generation
+ curve</a></h4>
+ <br>
+ <h4><a href="Scenarios.html#PC1">Calibrating Printers</a></h4>
+ <h4> <a href="Scenarios.html#PC2">Calibrated
+ print workflows</a></h4>
+ <h4> <a href="Scenarios.html#PC3">Creating a
+ print calibration test chart</a></h4>
+ <h4> </h4>
+ <h4> <a href="Scenarios.html#PC4">Creating a
+ printer calibration<br>
+ </a></h4>
+ <h4> <a href="Scenarios.html#PC5">Using a printer
+ calibration</a></h4>
+ <h4> <a href="#PC6">How profile ink limits are
+ handled when calibration is being used<br>
+ </a></h4>
+ <h4> <a href="#LP1">Linking Profiles</a></h4>
+ <h4> <a href="#TR1">Transforming colorspaces of raster files</a></h4>
+ <h4></h4>
+ <h4> <a href="#TV1">Creating Video Calibration 3DLuts</a></h4>
+ <h4><a href="Scenarios.html#TV2">Verifying Video Calibration 3DLuts</a></h4>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <h3><a name="PM1"></a>Profiling Displays</h3>
+ Argyll supports adjusting, calibrating and profiling of displays
+ using one of a number of instruments - see <a
+ href="instruments.html">instruments</a> for a current list.
+ Adjustment and calibration are prior steps to profiling, in which
+ the display is adjusted using it's screen controls, and then
+ per channel lookup tables are created to make it meet a well behaved
+ response of the desired type. The process following that of
+ creating a display profile is then similar to that of all other
+ output devices :- first a set of device colorspace test values needs
+ to be created to exercise the display, then these values need to be
+ displayed, while taking measurements of the resulting colors using
+ the instrument. Finally, the device value/measured color values need
+ to be converted into an ICC profile.<br>
+ <br>
+ <h3><a name="PM1a"></a>Checking you can access your display<br>
+ </h3>
+ You might first want to check that you are accessing and can
+ calibrate your display. You can do this using the <a
+ href="dispwin.html">dispwin</a><span style="font-weight: bold;"></span>
+ tool<span style="font-weight: bold;">.</span> If you just run <span
+ style="font-weight: bold;">dispwin</span> it will create a test
+ window and run through a series of test colors before checking that
+ the VideoLUT can be accessed by the display. If you invoke the usage
+ for <span style="font-weight: bold;">dispwin</span> (by giving it
+ an unrecognized option, e.g. <span style="font-weight: bold;">-?</span>)
+ then it will show a list of available displays next to the <span
+ style="font-weight: bold;"><span style="font-weight: bold;">-d</span></span>
+ flag. Make sure that you are accessing the display you intend to
+ calibrate and profile, and that the VideoLUT is effective (the <span
+ style="font-weight: bold;">-r</span> flag can be used to just run
+ the VideoLUT test). You can also try clearing the VideoLUTs using
+ the <span style="font-weight: bold;">-c</span> flag, and loading a
+ deliberately strange looking calibration <span style="font-weight:
+ bold;">strange.cal</span> that is provided in the Argyll <span
+ style="font-weight: bold;">ref</span> directory.<br>
+ <br>
+ Note that calibrating and/or profiling <span style="font-weight:
+ bold;">remote</span> displays is possible using X11 or a web
+ browser (see <span style="font-weight: bold;">-d</span> option of
+ dispcal and dispread), or by using some external program to send
+ test colors to a display (see <span style="font-weight: bold;">-C</span>
+ and <span style="font-weight: bold;">-M</span> options of dispcal
and dispread), but you may want to refer to <a href="#PM7">Calibrating - and profiling a display that doesn't have VideoLUT access</a>.<br> - <br> - <h3><a name="PM1b"></a>Adjusting and Calibrating Displays</h3> - Please read <a href="calvschar.html">What's the difference between - Calibration and Characterization ?</a> if you are unclear as to - the difference .<br> - <br> - The first step is to decide what the target should be for adjustment - and calibration. This boils down to three things: The desired - brightness, the desired white point, and the desired response curve. - The native brightness and white points of a display may be different - to the desired characteristics for some purposes. For instance, for - graphic arts use, it might be desirable to run with a warmer white - point of about 5000 degrees Kelvin, rather than the default display - white point of 6500 to 9000 Kelvin. Some LCD displays are too bright - to compare to printed material under available lighting, so it might - be desirable to reduce the maximum brightness.<br> - <br> - You can run <a href="dispcal.html#r">dispcal -r</a> to check on how - your display is currently set up. (you may have to run this as <span + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ and profiling a display that doesn't have VideoLUT access</a>.<br>
+ <br>
+ <h3><a name="PM1b"></a>Adjusting and Calibrating Displays</h3>
+ Please read <a href="calvschar.html">What's the difference between
+ Calibration and Characterization ?</a> if you are unclear as to
+ the difference .<br>
+ <br>
+ The first step is to decide what the target should be for adjustment
+ and calibration. This boils down to three things: The desired
+ brightness, the desired white point, and the desired response curve.
+ The native brightness and white points of a display may be different
+ to the desired characteristics for some purposes. For instance, for
+ graphic arts use, it might be desirable to run with a warmer white
+ point of about 5000 degrees Kelvin, rather than the default display
+ white point of 6500 to 9000 Kelvin. Some LCD displays are too bright
+ to compare to printed material under available lighting, so it might
+ be desirable to reduce the maximum brightness.<br>
+ <br>
+ You can run <a href="dispcal.html#r">dispcal -r</a> to check on how
+ your display is currently set up. (you may have to run this as <span
style="text-decoration: underline; color: rgb(204, 51, 204);">dispcal -yl @@ -157,330 +195,368 @@ - -r</span> for an LCD display, or <span style="text-decoration: - underline; color: rgb(204, 51, 204);">dispcal -yc -r</span> for a - CRT display with most of the colorimeter instruments. If so, this - will apply to all of the following examples.)<br> - <br> - Once this is done, <a href="dispcal.html">dispcal</a> can be run to - guide you through the display adjustments, and then calibrate it. By - default, the brightness and white point will be kept the same as the - devices natural brightness and white point. The default response - curve is a gamma of 2.4, except for Apple OS X systems prior to 10.6 - where a gamma of 1.8 is the default. 2.4 is close to that of - many monitors, and close to that of the sRGB colorspace. <br> - <br> - A typical calibration that leaves the brightness and white point - alone, might be:<br> - <br> - <a href="dispcal.html">dispcal</a> -v TargetA<br> - <br> - which will result in a "TargetA.cal" calibration file, that can then - be used during the profiling stage.<br> - <br> - If the absolutely native response of the display is desired during - profiling, then calibration should be skipped, and the linear.cal - file from the "ref" directory used instead as the argument to the -k - flag of <span style="font-weight: bold;">dispread</span>.<br> - <br> - <b>Dispcal</b> will display a test window in the middle of the - screen, and issue a series of instructions about placing the - instrument on the display. You may need to make sure that the - display cursor is not in the test window, and it may also be - necessary to disable any screensaver and powersavers before starting - the process, although both <span style="font-weight: bold;">dispcal</span> - and <span style="font-weight: bold;">dispread</span> will attempt - to do this for you. It's also highly desirable on CRT's, to clear - your screen of any white or bright background images or windows - (running your shell window with white text on a black background - helps a lot here.), or at least keep any bright areas away from the - test window, and be careful not to change anything on the display - while the readings are taken. Lots of bright images or windows can - affect the ability to measure the black point accurately, and - changing images on the display can cause inconsistency in the - readings, and leading to poor results.<span - style="font-weight: bold;"></span> LCD displays seem to be less - influenced by what else is on the screen.<br> - <br> - If <span style="font-weight: bold;">dispcal</span> is run without - arguments, it will provide a usage screen. The <span - style="font-weight: bold;">-c</span> parameter allows selecting a - communication port for an instrument, or selecting the instrument - you want to use, and the <a href="dispcal.html#d"><span - style="font-weight: bold;">-d</span></a> option allows selecting - a target display on a multi-display system. On some multi-monitor - systems, it may not be possible to independently calibrate and - profile each display if they appear as one single screen to the - operating system, or if it is not possible to set separate video - lookup tables for each display. You can change the position and size - of the test window using the <a href="dispcal.html#P"><span - style="font-weight: bold;">-P</span></a> parameter. You can - determine how best to arrange the test window, as well as whether - each display has separate video lookup capability, by experimenting - with the <a href="dispwin.html">dispwin</a> tool. <br> - <br> - For a more detailed discussion on interactively adjusting the - display controls using <span style="font-weight: bold;">dispcal</span>, - see <a href="dispcal.html#Adjustment">dispcal-adjustment</a>. Once - you have adjusted and calibrated your display, you can move on to - the next step.<br> - <br> - When you have calibrated and profiled your display, you can keep it - calibrated using the <a href="dispcal.html#u">dispcal -u</a> - option.<br> - <br> - <h4><a name="PM1c"></a>Adjusting, calibrating and profiling in one - step.</h4> - If a simple matrix/shaper display profile is all that is desired, <span - style="font-weight: bold;">dispcal</span> can be used to do this, - permitting display adjustment, calibration and profiling all in one - operation. This is done by using the <span style="font-weight: - bold;"><span style="font-weight: bold;">dispcal </span>-o</span> - flag:<br> - <br> - <a href="dispcal.html">dispcal</a> <a href="dispcal.html#v">-v</a> - <a href="dispcal.html#o">-o</a> <a href="dispcal.html#p1">TargetA</a><br> - <br> - This will create both a TargetA.cal file, but also a TargetA.icm - file. See <a href="dispcal.html#o">-o</a> and <a - href="dispcal.html#O">-O</a> for other variations.<br> - <br> - For more flexibility in creating a display profile, the separate - steps of creating characterization test values using <span - style="font-weight: bold;">targen</span>, reading them from the - display using <span style="font-weight: bold;">dispread</span>, and - then creating a profile using <span style="font-weight: bold;">colprof</span> - are used. The following steps illustrate this:<br> - <h4><a name="PM2"></a>Profiling in several steps: Creating display - test values</h4> - If the <span style="font-weight: bold;">dispcal</span> has not been - used to create a display profile at the same time as adjustment and - calibration, then it can be used to create a suitable set of - calibration curves as the first step, or the calibration step can be - omitted, and the display cansimply be profiled.<br> - <br> - The first step in profiling any output device, is to create a set of - device colorspace test values. The important parameters needed are: - <br> - <ul> - <li>What colorspace does the device use ?</li> - <li>How many test patches do I want to use ?</li> - <li>What information do I already have about how the device - behaves ?</li> - </ul> - For a display device, the colorspace will be RGB. The number - of test patches will depend somewhat on what quality profile you - want to make, what type of profile you want to make, and how long - you are prepared to wait when testing the display.<br> - At a minimum, a few hundred values are needed. A matrix/shaper type - of profile can get by with fewer test values, while a LUT based - profile will give better results if more test values are used. A - typical number might be 200-600 or so values, while 1000-2000 is not - an unreasonable number for a high quality characterization of a - display.<br> - <br> - To assist the choice of test patch values, it can help to have a - rough idea of how the device behaves. This could be in the form of - an ICC profile of a similar device, or a lower quality, or previous - profile for that particular device. If one were going to make a very - high quality LUT based profile, then it might be worthwhile to make - up a smaller, preliminary shaper/matrix profile using a few hundred - test points, before embarking on testing the device with several - thousand.<br> - <br> - Lets say that we ultimately want to make a profile for the device - "DisplayA", the simplest approach is to make a set of test values - that is independent of the characteristics of the particular device:<br> - <br> - <a href="targen.html">targen</a> <a href="targen.html#v">-v</a> - <a href="targen.html#d">-d3</a> <a href="targen.html#f">-f500</a> - <a href="targen.html#p1">DisplayA</a><br> - <br> - If there is a preliminary or previous profile called "OldDisplay" - available, and we want to try creating a "pre-conditioned" set of - test values that will more efficiently sample the device response, - then the following would achieve this:<br> - <u><br> - </u><a href="targen.html"> targen</a> <a href="targen.html#v">-v</a> - <a href="targen.html#d">-d3</a> <a href="targen.html#f">-f500</a> - <a href="targen.html#c">-cOldDisplay.icm</a> <a - href="targen.html#p1">DisplayA</a><br> - <br> - The output of <b>targen</b> will be the file DisplayA.ti1, - containing the device space test values, as well as expected CIE - values used for chart recognition purposes.<br> - <br> - <h4><a name="PM3"></a>Profiling in several steps: Taking readings - from a display</h4> - First it is necessary to connect your measurement instrument to your - computer, and check which communication port it is connected to. In - the following example, it is assumed that the instrument is - connected to the default port 1, which is either the first USB - instrument found, or serial port found. Invoking dispread so as to - display the usage information (by using a flag -? or --) will list - the identified serial and USB ports, and their labels.<br> - <br> - <a href="dispread.html">dispread</a> <a href="dispread.html#v">-v</a> - <a href="dispread.html#p1">DisplayA</a><br> - <br> - If we created a calibration for the display using <a - href="dispcal.html">dispcal</a>, then we will want to use this - when we take the display readings (e.g. TargetA.cal from the - calibration example)..<br> - <br> - <a href="dispread.html">dispread</a> <a href="dispread.html#v">-v</a> - <a href="dispread.html#k">-k TargetA.cal</a> <a - href="dispread.html#p1">DisplayA</a><br> - <br> - <b>dispread</b> will display a test window in the middle of the - screen, and issue a series of instructions about placing the - instrument on the display. You may need to make sure that the - display cursor is not in the test window, and it may also be - necessary to disable any screensaver before starting the process. - Exactly the same facilities are provided to select alternate - displays using the <span style="font-weight: bold;">-d</span> - parameter, and an alternate location and size for the test window - using the <span style="font-weight: bold;">-P</span> parameter as - with <span style="font-weight: bold;">dispcal</span>.<br> - <h4><a name="PM4"></a>Profiling in several steps: Creating a display - profile</h4> - There are two basic choices of profile type for a display, a - shaper/matrix profile, or a LUT based profile. They have different - tradeoffs. A shaper/matrix profile will work well on a well behaved - display, that is one that behaves in an additive color manner, will - give very smooth looking results, and needs fewer test points to - create. A LUT based profile on the other hand, will model any - display behaviour more accurately, and can accommodate gamut mapping - and different intent tables. Often it can show some unevenness and - contouring in the results though.<br> - <br> - To create a matrix/shaper profile, the following suffices:<br> - <br> - <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a> - <a href="colprof.html#E">-D"Display A"</a> <a href="colprof.html#q">-qm</a> - <a href="colprof.html#a">-as</a> <a href="colprof.html#p1">DisplayA</a><br> - <br> - For a LUT based profile, where gamut mapping is desired, then a - source profile will need to be provided to define the source gamut. - For instance, if the display profile was likely to be linked to a - CMYK printing source profile, say "swop.icm" or "fogra39l.icm", then - the following would suffice:<br> - <br> - <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a> - <a href="colprof.html#E">-D"Display A"</a> <a href="colprof.html#q">-qm</a> - <a href="colprof.html#S">-S</a><a href="colprof.html#S"> - fogra39l.icm</a> <a href="colprof.html#c">-cpp</a> <a - href="colprof.html#d">-dmt</a> <a href="colprof.html#p1">DisplayA</a><br> - <br> - Make sure you check the delta E report at the end of the profile - creation, to see if the profile is behaving reasonably.<br> - If a calibration file was used with <a href="dispread.html">dispread</a>, - then it will be converted to a vcgt tag in the profile, so that the - operating system or other system color tools load the lookup curves - into the display hardware, when the profile is used.<br> - <h4><a name="PM5"></a>Installing a display profile</h4> - <a href="dispwin.html">dispwin</a> provides a convenient way of - installing a profile as the default system profile for the chosen - display:<br> - <br> - <a href="dispwin.html">dispwin</a> <a href="dispwin.html#I">-I</a> - <a href="dispwin.html#p1">DisplayA.icm</a><br> - <br> - This also sets the display to the calibration contained in the - profile. If you want to try out a calibration before installing the - profile, using dispwin without the <span style="font-weight: bold;">-I</span> - option will load a calibration (ICC profile or .cal file) into the - current display.<br> - <br> - Some systems will automatically set the display to the calibration - contained in the installed profile (ie. OS X), while on other - systems (ie. MSWindows and Linux/X11) it is necessary to use some - tool to do this. On MSWindows XP you could install the - optional <span style="font-weight: bold;">Microsoft Color Control Panel Applet for Windows XP</span> - available for download from Microsoft to do this, but <span - style="font-weight: bold;">NOTE</span> however that it seems to - have a <span style="font-weight: bold;">bug</span>, in that it - sometimes associates the profiles with the <span - style="font-weight: bold;">wrong monitor</span> entry. Other - display calibration tools will often install a similar tool, so - beware of there being multiple, competing programs. [ Commonly these - will be in your Start->Programs->Startup folder. ]<br> - On Microsoft Vista, you need to use dispwin -L or some other tool to - load the installed profiles calibration at startup.<br> - <br> - To use dispwin to load the installed profiles calibration to the - display, use<br> - <br> - <a href="dispwin.html">dispwin</a> <a href="dispwin.html#L">-L</a><br> - <br> - As per usual, you can select the appropriate display using the <a - href="dispwin.html#d">-d</a> flag.<br> - <br> - This can be automated on MSWindows and X11/Linux by adding this - command to an appropriate startup script.<br> - More system specific details, including how to create such startup - scripts are <a href="dispprofloc.html">here</a>. <br> - <br> - If you are using Microsoft <span style="font-weight: bold;">Vista</span>, - there is a known <span style="font-weight: bold;">bug</span> in - Vista that resets the calibration every time a fade-in effect is - executed, which happens if you lock and unlock the computer, resume - from sleep or hibernate, or User Access Control is activated. Using - <a href="dispwin.html">dispwin</a> <a href="dispwin.html#L">-L</a> - may not restore the calibration, because Vista filters out setting - (what it thinks) is a calibration that is already loaded. Use <a - href="dispwin.html">dispwin</a> <a href="dispwin.html#c">-c</a> <a - href="dispwin.html#L">-L</a><span style="font-family: monospace;"></span> - as a workaround, as this will first clear the calibration, then - re-load the current calibration.<br> - <br> - On X11/Linux systems, you could try adding <a href="dispwin.html">dispwin</a> - <a href="dispwin.html#L">-L</a> to your <span style="font-weight: - bold;">~/.config/autostart</span> file, so that your window - manager automatically sets calibration when it starts. If you are - running XRandR 1.2, you might consider running the experimental <a - href="dispwin.html#D">dispwin -E</a> in the background, as in its - "daemon" mode it will update the profile and calibration in response - to any changes in the the connected display.<br> - <br> - <h4><a name="PM6"></a>Expert tips when measuring displays:<br> - </h4> - Sometimes it can be difficult to get good quality, consistent and - visually relevant readings from displays, due to various practical - considerations with regard to instruments and the displays - themselves. Argyll's tools have some extra options that may assist - in overcoming these problems.<br> - <br> - If you are using an Eye-One Pro or ColorMunki spectrometer, then you - may wish to use the <a href="dispcal.html#H">high resolution - spectral mode</a> (<span style="font-weight: bold;">-H</span>). - This may be better at capturing the often narrow wavelength peaks - that are typical of display primary colors.<br> - <br> - All instruments depend on silicon sensors, and such sensors generate - a temperature dependant level of noise ("dark noise") that is - factored out of the measurements by a dark or black instrument - calibration. The spectrometers in particular need this calibration - before commencing each set of measurements. Often an instrument will - warm up as it sits on a display, and this warming up can cause the - dark noise to increase, leading to inaccuracies in dark patch - measurements. The longer the measurement takes, the worse this - problem is likely to be. One way of addressing this is to - "acclimatise" the instrument before commencing measurements by - placing it on the screen in a powered up state, and leaving it for - some time. (Some people leave it for up to an hour to acclimatise.). - Another approach is to try and <a href="dispcal.html#I">compensate - for dark calibration changes</a> (<span style="font-weight: bold;">-Ib</span>) - by doing on the fly calibrations during the measurements, based on - the assumption that the black level of the display itself won't - change significantly. <br> - <br> - Some displays take a long time to settle down and stabilise. The is - often the case with LCD (Liquid Crystal) displays that use - fluorescent back lights, and these sorts of displays can change in - brightness significantly with changes in temperature. One way of - addressing this is to make sure that the display is given adequate - time to warm up before measurements. Another approach is to try and + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ -r</span> for an LCD display, or <span style="text-decoration:
+ underline; color: rgb(204, 51, 204);">dispcal -yc -r</span> for a
+ CRT display with most of the colorimeter instruments. If so, this
+ will apply to all of the following examples.)<br>
+ <br>
+ Once this is done, <a href="dispcal.html">dispcal</a> can be run to
+ guide you through the display adjustments, and then calibrate it. By
+ default, the brightness and white point will be kept the same as the
+ devices natural brightness and white point. The default response
+ curve is a gamma of 2.4, except for Apple OS X systems prior to 10.6
+ where a gamma of 1.8 is the default. 2.4 is close to that of
+ many monitors, and close to that of the sRGB colorspace. <br>
+ <br>
+ A typical calibration that leaves the brightness and white point
+ alone, might be:<br>
+ <br>
+ <a href="dispcal.html">dispcal</a> -v TargetA<br>
+ <br>
+ which will result in a "TargetA.cal" calibration file, that can then
+ be used during the profiling stage.<br>
+ <br>
+ If the absolutely native response of the display is desired during
+ profiling, then calibration should be skipped, and the linear.cal
+ file from the "ref" directory used instead as the argument to the -k
+ flag of <span style="font-weight: bold;">dispread</span>.<br>
+ <br>
+ <b>Dispcal</b> will display a test window in the middle of the
+ screen, and issue a series of instructions about placing the
+ instrument on the display. You may need to make sure that the
+ display cursor is not in the test window, and it may also be
+ necessary to disable any screensaver and powersavers before starting
+ the process, although both <span style="font-weight: bold;">dispcal</span>
+ and <span style="font-weight: bold;">dispread</span> will attempt
+ to do this for you. It's also highly desirable on CRT's, to clear
+ your screen of any white or bright background images or windows
+ (running your shell window with white text on a black background
+ helps a lot here.), or at least keep any bright areas away from the
+ test window, and be careful not to change anything on the display
+ while the readings are taken. Lots of bright images or windows can
+ affect the ability to measure the black point accurately, and
+ changing images on the display can cause inconsistency in the
+ readings, and leading to poor results.<span
+ style="font-weight: bold;"></span> LCD displays seem to be less
+ influenced by what else is on the screen.<br>
+ <br>
+ If <span style="font-weight: bold;">dispcal</span> is run without
+ arguments, it will provide a usage screen. The <span
+ style="font-weight: bold;">-c</span> parameter allows selecting a
+ communication port for an instrument, or selecting the instrument
+ you want to use, and the <a href="dispcal.html#d"><span
+ style="font-weight: bold;">-d</span></a> option allows selecting
+ a target display on a multi-display system. On some multi-monitor
+ systems, it may not be possible to independently calibrate and
+ profile each display if they appear as one single screen to the
+ operating system, or if it is not possible to set separate video
+ lookup tables for each display. You can change the position and size
+ of the test window using the <a href="dispcal.html#P"><span
+ style="font-weight: bold;">-P</span></a> parameter. You can
+ determine how best to arrange the test window, as well as whether
+ each display has separate video lookup capability, by experimenting
+ with the <a href="dispwin.html">dispwin</a> tool. <br>
+ <br>
+ For a more detailed discussion on interactively adjusting the
+ display controls using <span style="font-weight: bold;">dispcal</span>,
+ see <a href="dispcal.html#Adjustment">dispcal-adjustment</a>. Once
+ you have adjusted and calibrated your display, you can move on to
+ the next step.<br>
+ <br>
+ When you have calibrated and profiled your display, you can keep it
+ calibrated using the <a href="dispcal.html#u">dispcal -u</a>
+ option.<br>
+ <br>
+ <h4><a name="PM1c"></a>Adjusting, calibrating and profiling in one
+ step.</h4>
+ If a simple matrix/shaper display profile is all that is desired, <span
+ style="font-weight: bold;">dispcal</span> can be used to do this,
+ permitting display adjustment, calibration and profiling all in one
+ operation. This is done by using the <span style="font-weight:
+ bold;"><span style="font-weight: bold;">dispcal </span>-o</span>
+ flag:<br>
+ <br>
+ <a href="dispcal.html">dispcal</a> <a href="dispcal.html#v">-v</a>
+ <a href="dispcal.html#o">-o</a> <a href="dispcal.html#p1">TargetA</a><br>
+ <br>
+ This will create both a TargetA.cal file, but also a TargetA.icm
+ file. See <a href="dispcal.html#o">-o</a> and <a
+ href="dispcal.html#O">-O</a> for other variations.<br>
+ <br>
+ For more flexibility in creating a display profile, the separate
+ steps of creating characterization test values using <span
+ style="font-weight: bold;">targen</span>, reading them from the
+ display using <span style="font-weight: bold;">dispread</span>, and
+ then creating a profile using <span style="font-weight: bold;">colprof</span>
+ are used. The following steps illustrate this:<br>
+ <h4><a name="PM2"></a>Profiling in several steps: Creating display
+ test values</h4>
+ If the <span style="font-weight: bold;">dispcal</span> has not been
+ used to create a display profile at the same time as adjustment and
+ calibration, then it can be used to create a suitable set of
+ calibration curves as the first step, or the calibration step can be
+ omitted, and the display cansimply be profiled.<br>
+ <br>
+ The first step in profiling any output device, is to create a set of
+ device colorspace test values. The important parameters needed are:
+ <br>
+ <ul>
+ <li>What colorspace does the device use ?</li>
+ <li>How many test patches do I want to use ?</li>
+ <li>What information do I already have about how the device
+ behaves ?</li>
+ </ul>
+ For a display device, the colorspace will be RGB. The number
+ of test patches will depend somewhat on what quality profile you
+ want to make, what type of profile you want to make, and how long
+ you are prepared to wait when testing the display.<br>
+ At a minimum, a few hundred values are needed. A matrix/shaper type
+ of profile can get by with fewer test values, while a LUT based
+ profile will give better results if more test values are used. A
+ typical number might be 200-600 or so values, while 1000-2000 is not
+ an unreasonable number for a high quality characterization of a
+ display.<br>
+ <br>
+ To assist the choice of test patch values, it can help to have a
+ rough idea of how the device behaves. This could be in the form of
+ an ICC profile of a similar device, or a lower quality, or previous
+ profile for that particular device. If one were going to make a very
+ high quality LUT based profile, then it might be worthwhile to make
+ up a smaller, preliminary shaper/matrix profile using a few hundred
+ test points, before embarking on testing the device with several
+ thousand.<br>
+ <br>
+ Lets say that we ultimately want to make a profile for the device
+ "DisplayA", the simplest approach is to make a set of test values
+ that is independent of the characteristics of the particular device:<br>
+ <br>
+ <a href="targen.html">targen</a> <a href="targen.html#v">-v</a>
+ <a href="targen.html#d">-d3</a> <a href="targen.html#f">-f500</a>
+ <a href="targen.html#p1">DisplayA</a><br>
+ <br>
+ If there is a preliminary or previous profile called "OldDisplay"
+ available, and we want to try creating a "pre-conditioned" set of
+ test values that will more efficiently sample the device response,
+ then the following would achieve this:<br>
+ <u><br>
+ </u><a href="targen.html"> targen</a> <a href="targen.html#v">-v</a>
+ <a href="targen.html#d">-d3</a> <a href="targen.html#f">-f500</a>
+ <a href="targen.html#c">-cOldDisplay.icm</a> <a
+ href="targen.html#p1">DisplayA</a><br>
+ <br>
+ The output of <b>targen</b> will be the file DisplayA.ti1,
+ containing the device space test values, as well as expected CIE
+ values used for chart recognition purposes.<br>
+ <br>
+ <h4><a name="PM3"></a>Profiling in several steps: Taking readings
+ from a display</h4>
+ First it is necessary to connect your measurement instrument to your
+ computer, and check which communication port it is connected to. In
+ the following example, it is assumed that the instrument is
+ connected to the default port 1, which is either the first USB
+ instrument found, or serial port found. Invoking dispread so as to
+ display the usage information (by using a flag -? or --) will list
+ the identified serial and USB ports, and their labels.<br>
+ <br>
+ <a href="dispread.html">dispread</a> <a href="dispread.html#v">-v</a>
+ <a href="dispread.html#p1">DisplayA</a><br>
+ <br>
+ If we created a calibration for the display using <a
+ href="dispcal.html">dispcal</a>, then we will want to use this
+ when we take the display readings (e.g. TargetA.cal from the
+ calibration example)..<br>
+ <br>
+ <a href="dispread.html">dispread</a> <a href="dispread.html#v">-v</a>
+ <a href="dispread.html#k">-k TargetA.cal</a> <a
+ href="dispread.html#p1">DisplayA</a><br>
+ <br>
+ <b>dispread</b> will display a test window in the middle of the
+ screen, and issue a series of instructions about placing the
+ instrument on the display. You may need to make sure that the
+ display cursor is not in the test window, and it may also be
+ necessary to disable any screensaver before starting the process.
+ Exactly the same facilities are provided to select alternate
+ displays using the <span style="font-weight: bold;">-d</span>
+ parameter, and an alternate location and size for the test window
+ using the <span style="font-weight: bold;">-P</span> parameter as
+ with <span style="font-weight: bold;">dispcal</span>.<br>
+ <h4><a name="PM4"></a>Profiling in several steps: Creating a display
+ profile</h4>
+ There are two basic choices of profile type for a display, a
+ shaper/matrix profile, or a LUT based profile. They have different
+ tradeoffs. A shaper/matrix profile will work well on a well behaved
+ display, that is one that behaves in an additive color manner, will
+ give very smooth looking results, and needs fewer test points to
+ create. A LUT based profile on the other hand, will model any
+ display behaviour more accurately, and can accommodate gamut mapping
+ and different intent tables. Often it can show some unevenness and
+ contouring in the results though.<br>
+ <br>
+ To create a matrix/shaper profile, the following suffices:<br>
+ <br>
+ <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a>
+ <a href="colprof.html#E">-D"Display A"</a> <a href="colprof.html#q">-qm</a>
+ <a href="colprof.html#a">-as</a> <a href="colprof.html#p1">DisplayA</a><br>
+ <br>
+ For a LUT based profile, where gamut mapping is desired, then a
+ source profile will need to be provided to define the source gamut.
+ For instance, if the display profile was likely to be linked to a
+ CMYK printing source profile, say "swop.icm" or "fogra39l.icm", then
+ the following would suffice:<br>
+ <br>
+ <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a>
+ <a href="colprof.html#E">-D"Display A"</a> <a href="colprof.html#q">-qm</a>
+ <a href="colprof.html#S">-S</a><a href="colprof.html#S">
+ fogra39l.icm</a> <a href="colprof.html#c">-cpp</a> <a
+ href="colprof.html#d">-dmt</a> <a href="colprof.html#p1">DisplayA</a><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.<br>
+ If a calibration file was used with <a href="dispread.html">dispread</a>,
+ then it will be converted to a vcgt tag in the profile, so that the
+ operating system or other system color tools load the lookup curves
+ into the display hardware, when the profile is used.<br>
+ <h4><a name="PM5"></a>Installing a display profile</h4>
+ <a href="dispwin.html">dispwin</a> provides a convenient way of
+ installing a profile as the default system profile for the chosen
+ display:<br>
+ <br>
+ <a href="dispwin.html">dispwin</a> <a href="dispwin.html#I">-I</a>
+ <a href="dispwin.html#p1">DisplayA.icm</a><br>
+ <br>
+ This also sets the display to the calibration contained in the
+ profile. If you want to try out a calibration before installing the
+ profile, using dispwin without the <span style="font-weight: bold;">-I</span>
+ option will load a calibration (ICC profile or .cal file) into the
+ current display.<br>
+ <br>
+ Some systems will automatically set the display to the calibration
+ contained in the installed profile (ie. OS X), while on other
+ systems (ie. MSWindows and Linux/X11) it is necessary to use some
+ tool to do this. On MSWindows XP you could install the
+ optional <span style="font-weight: bold;">Microsoft Color Control Panel Applet for Windows XP</span>
+ available for download from Microsoft to do this, but <span
+ style="font-weight: bold;">NOTE</span> however that it seems to
+ have a <span style="font-weight: bold;">bug</span>, in that it
+ sometimes associates the profiles with the <span
+ style="font-weight: bold;">wrong monitor</span> entry. Other
+ display calibration tools will often install a similar tool, so
+ beware of there being multiple, competing programs. [ Commonly these
+ will be in your Start->Programs->Startup folder. ]<br>
+ On Microsoft Vista, you need to use dispwin -L or some other tool to
+ load the installed profiles calibration at startup.<br>
+ <br>
+ To use dispwin to load the installed profiles calibration to the
+ display, use<br>
+ <br>
+ <a href="dispwin.html">dispwin</a> <a href="dispwin.html#L">-L</a><br>
+ <br>
+ As per usual, you can select the appropriate display using the <a
+ href="dispwin.html#d">-d</a> flag.<br>
+ <br>
+ This can be automated on MSWindows and X11/Linux by adding this
+ command to an appropriate startup script.<br>
+ More system specific details, including how to create such startup
+ scripts are <a href="dispprofloc.html">here</a>. <br>
+ <br>
+ If you are using Microsoft <span style="font-weight: bold;">Vista</span>,
+ there is a known <span style="font-weight: bold;">bug</span> in
+ Vista that resets the calibration every time a fade-in effect is
+ executed, which happens if you lock and unlock the computer, resume
+ from sleep or hibernate, or User Access Control is activated. Using
+ <a href="dispwin.html">dispwin</a> <a href="dispwin.html#L">-L</a>
+ may not restore the calibration, because Vista filters out setting
+ (what it thinks) is a calibration that is already loaded. Use <a
+ href="dispwin.html">dispwin</a> <a href="dispwin.html#c">-c</a> <a
+ href="dispwin.html#L">-L</a><span style="font-family: monospace;"></span>
+ as a workaround, as this will first clear the calibration, then
+ re-load the current calibration.<br>
+ <br>
+ On X11/Linux systems, you could try adding <a href="dispwin.html">dispwin</a>
+ <a href="dispwin.html#L">-L</a> to your <span style="font-weight:
+ bold;">~/.config/autostart</span> file, so that your window
+ manager automatically sets calibration when it starts. If you are
+ running XRandR 1.2, you might consider running the experimental <a
+ href="dispwin.html#D">dispwin -E</a> in the background, as in its
+ "daemon" mode it will update the profile and calibration in response
+ to any changes in the the connected display.<br>
+ <br>
+ <h4><a name="PM6"></a>Expert tips when measuring displays:<br>
+ </h4>
+ Sometimes it can be difficult to get good quality, consistent and
+ visually relevant readings from displays, due to various practical
+ considerations with regard to instruments and the displays
+ themselves. Argyll's tools have some extra options that may assist
+ in overcoming these problems.<br>
+ <br>
+ If you are using an Eye-One Pro or ColorMunki spectrometer, then you
+ may wish to use the <a href="dispcal.html#H">high resolution
+ spectral mode</a> (<span style="font-weight: bold;">-H</span>).
+ This may be better at capturing the often narrow wavelength peaks
+ that are typical of display primary colors.<br>
+ <br>
+ All instruments depend on silicon sensors, and such sensors generate
+ a temperature dependant level of noise ("dark noise") that is
+ factored out of the measurements by a dark or black instrument
+ calibration. The spectrometers in particular need this calibration
+ before commencing each set of measurements. Often an instrument will
+ warm up as it sits on a display, and this warming up can cause the
+ dark noise to increase, leading to inaccuracies in dark patch
+ measurements. The longer the measurement takes, the worse this
+ problem is likely to be. One way of addressing this is to
+ "acclimatise" the instrument before commencing measurements by
+ placing it on the screen in a powered up state, and leaving it for
+ some time. (Some people leave it for up to an hour to acclimatise.).
+ Another approach is to try and <a href="dispcal.html#I">compensate
+ for dark calibration changes</a> (<span style="font-weight: bold;">-Ib</span>)
+ by doing on the fly calibrations during the measurements, based on
+ the assumption that the black level of the display itself won't
+ change significantly. <br>
+ <br>
+ Some displays take a long time to settle down and stabilise. The is
+ often the case with LCD (Liquid Crystal) displays that use
+ fluorescent back lights, and these sorts of displays can change in
+ brightness significantly with changes in temperature. One way of
+ addressing this is to make sure that the display is given adequate
+ time to warm up before measurements. Another approach is to try and
<a href="dispcal.html#I">compensate for display white level</a> @@ -490,20 +566,57 @@ - (<span style="font-weight: bold;">-Iw</span>) changes by doing on - the fly calibrations during the measurements. Instrument black level - drift and display white level drift can be combined (<span - style="font-weight: bold;">-Ibw</span>).<br> - <br> - Colorimeter instruments make use of physical color filters that - approximate the standard observer spectral sensitivity curves. - Because these filters are not perfectly accurate, the manufacturer - calibrates the instrument for typical displays, which is why you - have to make a selection between CRT (Cathode Ray Tube) and LCD - (Liquid Crystal Display) modes. If you are measuring a display that - has primary colorants that differ significantly from those typical - displays, (ie. you have a Wide Gamut Display), then you may - get disappointing results with a Colorimeter. One way of addressing + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ (<span style="font-weight: bold;">-Iw</span>) changes by doing on
+ the fly calibrations during the measurements. Instrument black level
+ drift and display white level drift can be combined (<span
+ style="font-weight: bold;">-Ibw</span>).<br>
+ <br>
+ Colorimeter instruments make use of physical color filters that
+ approximate the standard observer spectral sensitivity curves.
+ Because these filters are not perfectly accurate, the manufacturer
+ calibrates the instrument for typical displays, which is why you
+ have to make a selection between CRT (Cathode Ray Tube) and LCD
+ (Liquid Crystal Display) modes. If you are measuring a display that
+ has primary colorants that differ significantly from those typical
+ displays, (ie. you have a Wide Gamut Display), then you may
+ get disappointing results with a Colorimeter. One way of addressing
this problem is to use a <a href="File_Formats.html#.ccmx">Colorimeter @@ -512,117 +625,154 @@ - Correction Matrix</a>. These are specific to a particular - Colorimeter and Display make and model combination, although a - matrix for a different but similar type of display may give better - results than none at all. A list of contributed <span - style="font-weight: bold;">ccmx</span> files is <a - href="ccmxs.html">here</a>.<br> - <br> - <h4><a name="PM7"></a>Calibrating and profiling a display that - doesn't have VideoLUT access.</h4> - <p>In some situation there is no access to a displays VideoLUT - hardware, and this hardware is what is usually used to implement - display calibration. This could be because the display is being - accessed via a web server, or because the driver or windowing - system doesn't support VideoLUT access.<br> - </p> - <p>There are two basic options in this situation:<br> - </p> - <p> 1) Don't attempt to calibrate, just profile the display.<br> - 2) Calibrate, but incorporate the calibration in some other - way in the workflow.<br> - </p> - <p>The first case requires nothing special - just skip calibration - (see the previous section <a href="#PM7">Profiling in several - steps: Creating display test values</a>).</p> - <p> In the second case, there are three choices:<br> - </p> - <p> 2a) Use dispcal to create a calibration and a quick profile - that incorporates the calibration into the profile.<br> - 2b) Use dispcal to create the calibration, then dispread and - colprof to create a profile, and then incorporate the calibration - into the profile using applycal.<br> - 2c) Use dispcal to create the calibration, then dispread and - colprof to create a profile, and then apply the calibration after - the profile in a cctiff workflow.<br> - </p> - <p>The first case requires nothing special, use dispcal in a normal - fashioned with the <span style="font-weight: bold;">-o</span> - option to generate a quick profile.The profile created will <span - style="text-decoration: underline;">not</span> 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 device R=G=B=1.0. Some systems may not - cope properly with this type of profile, and a general shift in - white point through such a profile can create an odd looking - display if it is applied to images but not to other elements on - the display say as GUI decoration elements or other application - windows.<br> - </p> - <p>In the second case, the calibration file created using dispcal - should be provided to dispread using the <span - style="font-weight: bold;">-K</span> flag:<br> - </p> - <p><a href="dispread.html">dispread</a> <a href="dispread.html#v">-v</a> - <a href="dispread.html#K">-K TargetA.cal</a> <a - href="dispread.html#p1">DisplayA</a></p> - <p><span style="font-weight: bold;"></span>Create the profile as - usual using colprof. but note that colprof will ignore the - calibration, and that no 'vcgt' tag will be added to the profile.<br> - You can then use <a href="applycal.html">applycal </a>to combine - the calibration into the profile. Note that the resulting profile - will be slightly unusual, since the profile is not made completely - consistent with the effects of the calibration, and the device - R=G=B=1.0 probably not longer corresponds with the PCS white or - the white point.<br> - </p> - In the third case, the same procedure as above is used to create a - profile, but the calibration is applied in a raster transformation - workflow explicitly, e.g.:<br> - <br> - <a href="cctiff.html">cctiff</a> <a - href="cctiff.html#p1">SourceProfile.icm</a> <a - href="cctiff.html#p1">DisplayA.icm</a> <a href="cctiff.html#p2">DisplayA.cal</a> - <a href="cctiff.html#p3">infile.tif</a> <a href="cctiff.html#p4">outfile.tif</a><br> - or<br> - <a href="cctiff.html">cctiff</a> <a - href="cctiff.html#p1">SourceProfile.icm</a> <a - href="cctiff.html#p1">DisplayA.icm</a> <a href="cctiff.html#p2">DisplayA.cal</a> - <a href="cctiff.html#p3">infile.jpg</a> <a href="cctiff.html#p4">outfile.jpg</a><br> - <span style="font-weight: bold;"></span><br> - <hr size="2" width="100%"> - <h3><a name="PS1"></a>Profiling Scanners and other input devices - such as cameras<br> - </h3> - Because a scanner or camera is an input device, it is necessary to - go about profiling it in quite a different way to an output device. - To profile it, a test chart is needed to exercise the input device - response, to which the CIE values for each test patch is known. - Generally standard reflection or transparency test charts are used - for this purpose.<br> - <h4><a name="PS2"></a>Types of test charts</h4> - The most common and popular test chart for scanner profiling is the - IT8.7/2 chart. This is a standard format chart generally reproduced - on photographic film, containing about 264 test patches.<br> - An accessible and affordable source of such targets is Wolf Faust a - <a href="http://www.targets.coloraid.de/">www.coloraid.de</a>.<br> - Another source is LaserSoft <a - href="http://www.silverfast.com/show/it8/en.html">www.silverfast.com.</a><br> - The Kodak Q-60 Color Input Target is also a typical example:<br> - <br> - <img src="Q60.jpg" alt="Kodak Q60 chart image" height="141" - width="200"> <br> - <br> - A very simple chart that is widely available is the Macbeth - ColorChecker chart, although it contains only 24 patches and - therefore is probably not ideal for creating profiles:<br> - <img alt="ColorChecker 24 patch" src="colorchecker.jpg" - style="width: 112px; height: 78px;"><br> - <br> - Other popular charts are the X-Rite/GretagMacbeth ColorChecker DC + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Correction Matrix</a>. These are specific to a particular
+ Colorimeter and Display make and model combination, although a
+ matrix for a different but similar type of display may give better
+ results than none at all. A list of contributed <span
+ style="font-weight: bold;">ccmx</span> files is <a
+ href="ccmxs.html">here</a>.<br>
+ <br>
+ <h4><a name="PM7"></a>Calibrating and profiling a display that
+ doesn't have VideoLUT access.</h4>
+ <p>In some situation there is no access to a displays VideoLUT
+ hardware, and this hardware is what is usually used to implement
+ display calibration. This could be because the display is being
+ accessed via a web server, or because the driver or windowing
+ system doesn't support VideoLUT access.<br>
+ </p>
+ <p>There are two basic options in this situation:<br>
+ </p>
+ <p> 1) Don't attempt to calibrate, just profile the display.<br>
+ 2) Calibrate, but incorporate the calibration in some other
+ way in the workflow.<br>
+ </p>
+ <p>The first case requires nothing special - just skip calibration
+ (see the previous section <a href="#PM7">Profiling in several
+ steps: Creating display test values</a>).</p>
+ <p> In the second case, there are three choices:<br>
+ </p>
+ <p> 2a) Use dispcal to create a calibration and a quick profile
+ that incorporates the calibration into the profile.<br>
+ 2b) Use dispcal to create the calibration, then dispread and
+ colprof to create a profile, and then incorporate the calibration
+ into the profile using applycal.<br>
+ 2c) Use dispcal to create the calibration, then dispread and
+ colprof to create a profile, and then apply the calibration after
+ the profile in a cctiff workflow.<br>
+ </p>
+ <p>The first case requires nothing special, use dispcal in a normal
+ fashioned with the <span style="font-weight: bold;">-o</span>
+ option to generate a quick profile.The profile created will <span
+ style="text-decoration: underline;">not</span> 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 device R=G=B=1.0. Some systems may not
+ cope properly with this type of profile, and a general shift in
+ white point through such a profile can create an odd looking
+ display if it is applied to images but not to other elements on
+ the display say as GUI decoration elements or other application
+ windows.<br>
+ </p>
+ <p>In the second case, the calibration file created using dispcal
+ should be provided to dispread using the <span
+ style="font-weight: bold;">-K</span> flag:<br>
+ </p>
+ <p><a href="dispread.html">dispread</a> <a href="dispread.html#v">-v</a>
+ <a href="dispread.html#K">-K TargetA.cal</a> <a
+ href="dispread.html#p1">DisplayA</a></p>
+ <p><span style="font-weight: bold;"></span>Create the profile as
+ usual using colprof. but note that colprof will ignore the
+ calibration, and that no 'vcgt' tag will be added to the profile.<br>
+ You can then use <a href="applycal.html">applycal </a>to combine
+ the calibration into the profile. Note that the resulting profile
+ will be slightly unusual, since the profile is not made completely
+ consistent with the effects of the calibration, and the device
+ R=G=B=1.0 probably not longer corresponds with the PCS white or
+ the white point.<br>
+ </p>
+ In the third case, the same procedure as above is used to create a
+ profile, but the calibration is applied in a raster transformation
+ workflow explicitly, e.g.:<br>
+ <br>
+ <a href="cctiff.html">cctiff</a> <a
+ href="cctiff.html#p1">SourceProfile.icm</a> <a
+ href="cctiff.html#p1">DisplayA.icm</a> <a href="cctiff.html#p2">DisplayA.cal</a>
+ <a href="cctiff.html#p3">infile.tif</a> <a href="cctiff.html#p4">outfile.tif</a><br>
+ or<br>
+ <a href="cctiff.html">cctiff</a> <a
+ href="cctiff.html#p1">SourceProfile.icm</a> <a
+ href="cctiff.html#p1">DisplayA.icm</a> <a href="cctiff.html#p2">DisplayA.cal</a>
+ <a href="cctiff.html#p3">infile.jpg</a> <a href="cctiff.html#p4">outfile.jpg</a><br>
+ <span style="font-weight: bold;"></span><br>
+ <hr size="2" width="100%">
+ <h3><a name="PS1"></a>Profiling Scanners and other input devices
+ such as cameras<br>
+ </h3>
+ Because a scanner or camera is an input device, it is necessary to
+ go about profiling it in quite a different way to an output device.
+ To profile it, a test chart is needed to exercise the input device
+ response, to which the CIE values for each test patch is known.
+ Generally standard reflection or transparency test charts are used
+ for this purpose.<br>
+ <h4><a name="PS2"></a>Types of test charts</h4>
+ The most common and popular test chart for scanner profiling is the
+ IT8.7/2 chart. This is a standard format chart generally reproduced
+ on photographic film, containing about 264 test patches.<br>
+ An accessible and affordable source of such targets is Wolf Faust a
+ <a href="http://www.targets.coloraid.de/">www.coloraid.de</a>.<br>
+ Another source is LaserSoft <a
+ href="http://www.silverfast.com/show/it8/en.html">www.silverfast.com.</a><br>
+ The Kodak Q-60 Color Input Target is also a typical example:<br>
+ <br>
+ <img src="Q60.jpg" alt="Kodak Q60 chart image" height="141"
+ width="200"> <br>
+ <br>
+ A very simple chart that is widely available is the Macbeth
+ ColorChecker chart, although it contains only 24 patches and
+ therefore is probably not ideal for creating profiles:<br>
+ <img alt="ColorChecker 24 patch" src="colorchecker.jpg"
+ style="width: 112px; height: 78px;"><br>
+ <br>
+ Other popular charts are the X-Rite/GretagMacbeth ColorChecker DC
and <a href="http://www.xrite.com/product_overview.aspx?ID=938">ColorChecker @@ -632,17 +782,54 @@ - SG</a> charts:<br> - <br> - <img src="DC.jpg" alt="GretagMacbeth ColorChecker DC chart" - height="122" width="200"> <img alt="ColorChecker SG" src="SG.jpg" - style="width: 174px; height: 122px;"><br> - <br> - The GretagMacbeth Eye-One Pro Scan Target 1.4 can also be used:<br> - <br> - <img alt="Eye-One Scan Target 1.4" src="i1scan14.jpg" style="border: - 2px solid ; width: 200px; height: 140px;"><br> - <br> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ SG</a> charts:<br>
+ <br>
+ <img src="DC.jpg" alt="GretagMacbeth ColorChecker DC chart"
+ height="122" width="200"> <img alt="ColorChecker SG" src="SG.jpg"
+ style="width: 174px; height: 122px;"><br>
+ <br>
+ The GretagMacbeth Eye-One Pro Scan Target 1.4 can also be used:<br>
+ <br>
+ <img alt="Eye-One Scan Target 1.4" src="i1scan14.jpg" style="border:
+ 2px solid ; width: 200px; height: 140px;"><br>
+ <br>
Also supported is the <a href="http://www.hutchcolor.com/hct.htm">HutchColor @@ -652,13 +839,50 @@ - HCT</a> :<br> - <br> - <img alt="HutchColor HCT" src="HCT.jpg" style="width: 182px; height: - 140px;"><br> - <br> - <br> - and <a + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 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 @@ -668,7 +892,44 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm - Métairie's Digital TargeT 003</a> and <a + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Métairie's Digital TargeT 003</a> and <a
href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.html">Christophe @@ -678,12 +939,49 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm - Métairie's Digital Target - 3</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> - <br> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Métairie's Digital Target - 3</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>
+ <br>
and the <a href="http://www.silverfast.com/show/dc-targets/en.html">LaserSoft @@ -693,106 +991,217 @@ 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 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 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 - 201</a>: <a + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 201</a>: <a
href="http://www.qpcard.com/en_b2c/color-reference-cards/instant-camera-raw-profiling-with-qpcard-202.html">QPcard - 202</a>:<br> - <br> - <img style=" width: 41px; height: 141px;" alt="QPCard201" - src="QPcard201.jpg"> - <img - style=" width: 97px; height: 141px;" alt="QPcard202" - src="QPcard202.jpg"><br> - <br> - <h4><a name="PS3"></a>Taking readings from a scanner or camera<br> - </h4> - The test chart you are using needs to be placed on the scanner, and - the scanner needs to be configured to a suitable state, and restored - to that same state when used subsequently with the resulting - profile. For a camera, the chart needs to be lit in a controlled and - even manner using the light source that will be used for subsequent - photographs, and should be shot so as to minimise any geometric - distortion, although the <a href="scanin.html#p">scanin -p</a> flag - may be used to compensate for some degree of distortion. As with any - color profiling task, it is important to setup a known and - repeatable image processing flow, to ensure that the resulting - profile will be usable.<br> - <br> - The chart should be captured and saved to a TIFF format file. I will - assume the resulting file is called scanner.tif. The raster file - need only be roughly cropped so as to contain the test chart - (including the charts edges).<br> - <br> - The second step is to extract the RGB values from the scanner.tif - file, and match then to the reference CIE values. To locate the - patch values in the scan, the <b>scanin</b> tool needs to be given - a template <a href="File_Formats.html#.cht">.cht</a> file that - describes the features of the chart, and how the test patches are - labeled. Also needed is a file containing the CIE values for each of - the patches in the chart, which is typically supplied with the - chart, available from the manufacturers web site, or has been - measured using a spectrometer.<br> - <br> - <div style="margin-left: 40px;">For an IT8.7/2 chart, this is the <span - style="font-weight: bold;">ref/</span><b>it8.cht</b> file - supplied with Argyll, and the manufacturer will will supply - an individual or batch average file along with the chart - containing this information, or downloadable from their web site. - For instance, Kodak Q60 target reference files are <a - href="ftp://ftp.kodak.com/gastds/Q60DATA/">here</a>.<br> - NOTE that the reference file for the IT8.7/2 chart supplied with <span - style="font-weight: bold;">Monaco EZcolor</span> can be - obtained by unzipping the .mrf file. (You may have to make a copy - of the file with a .zip extension to do this.)<br> - <br> - For the ColorChecker 24 patch chart, the <span - style="font-weight: bold;">ref/ColorChecker.cht</span> file - should be used, and there is also a <span style="font-weight: - bold;">ref/ColorChecker.cie</span> file provided that is based - on the manufacturers reference values for the chart. You can also - create your own reference file using an instrument and chartread, - making use of the chart reference file <span style="font-weight: - bold;">ref/ColorChecker.ti2</span>:<br> - <a href="chartread.html">chartread</a> -n -a - ColorChecker.ti2<br> - Note that due to the small number of patches, a profile created - from such a chart is not likely to be very detailed.<br> - <br> - For the ColorChecker DC chart, the <span style="font-weight: - bold;">ref/ColorCheckerDC.cht</span> file should be used, and - there will be a ColorCheckerDC reference file supplied by - X-Rite/GretagMacbeth with the chart.<br> - <br> - The ColorChecker SG is relatively expensive, but is preferred by - many people because (like the ColorChecker and ColorCheckerDC) its - colors are composed of multiple different pigments, giving it - reflective spectra that are more representative of the real world, - unlike many other charts that are created out of combination of 3 - or 4 colorants.<br> - A limited CIE reference file is available from X-Rite <a -href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.txt">here</a>, - but it is not in the usual CGATS format. To convert it to a CIE - reference file useful for <span style="font-weight: bold;">scanin</span>, - you will need to edit the X-Rite file using a <span - style="text-decoration: underline;">plain text</span> editor, - first deleting everything before the line starting with "A1" and + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 202</a>:<br>
+ <br>
+ <img style=" width: 41px; height: 141px;" alt="QPCard201"
+ src="QPcard201.jpg">
+ <img
+ style=" width: 97px; height: 141px;" alt="QPcard202"
+ src="QPcard202.jpg"><br>
+ <br>
+ <h4><a name="PS3"></a>Taking readings from a scanner or camera<br>
+ </h4>
+ The test chart you are using needs to be placed on the scanner, and
+ the scanner needs to be configured to a suitable state, and restored
+ to that same state when used subsequently with the resulting
+ profile. For a camera, the chart needs to be lit in a controlled and
+ even manner using the light source that will be used for subsequent
+ photographs, and should be shot so as to minimise any geometric
+ distortion, although the <a href="scanin.html#p">scanin -p</a> flag
+ may be used to compensate for some degree of distortion. As with any
+ color profiling task, it is important to setup a known and
+ repeatable image processing flow, to ensure that the resulting
+ profile will be usable.<br>
+ <br>
+ The chart should be captured and saved to a TIFF format file. I will
+ assume the resulting file is called scanner.tif. The raster file
+ need only be roughly cropped so as to contain the test chart
+ (including the charts edges).<br>
+ <br>
+ The second step is to extract the RGB values from the scanner.tif
+ file, and match then to the reference CIE values. To locate the
+ patch values in the scan, the <b>scanin</b> tool needs to be given
+ a template <a href="File_Formats.html#.cht">.cht</a> file that
+ describes the features of the chart, and how the test patches are
+ labeled. Also needed is a file containing the CIE values for each of
+ the patches in the chart, which is typically supplied with the
+ chart, available from the manufacturers web site, or has been
+ measured using a spectrometer.<br>
+ <br>
+ <div style="margin-left: 40px;">For an IT8.7/2 chart, this is the <span
+ style="font-weight: bold;">ref/</span><b>it8.cht</b> file
+ supplied with Argyll, and the manufacturer will will supply
+ an individual or batch average file along with the chart
+ containing this information, or downloadable from their web site.
+ For instance, Kodak Q60 target reference files are <a
+ href="ftp://ftp.kodak.com/gastds/Q60DATA/">here</a>.<br>
+ NOTE that the reference file for the IT8.7/2 chart supplied with <span
+ style="font-weight: bold;">Monaco EZcolor</span> can be
+ obtained by unzipping the .mrf file. (You may have to make a copy
+ of the file with a .zip extension to do this.)<br>
+ <br>
+ For the ColorChecker 24 patch chart, the <span
+ style="font-weight: bold;">ref/ColorChecker.cht</span> file
+ should be used, and there is also a <span style="font-weight:
+ bold;">ref/ColorChecker.cie</span> file provided that is based
+ on the manufacturers reference values for the chart. You can also
+ create your own reference file using an instrument and chartread,
+ making use of the chart reference file <span style="font-weight:
+ bold;">ref/ColorChecker.ti2</span>:<br>
+ <a href="chartread.html">chartread</a> -n -a
+ ColorChecker.ti2<br>
+ Note that due to the small number of patches, a profile created
+ from such a chart is not likely to be very detailed.<br>
+ <br>
+ For the ColorChecker DC chart, the <span style="font-weight:
+ bold;">ref/ColorCheckerDC.cht</span> file should be used, and
+ there will be a ColorCheckerDC reference file supplied by
+ X-Rite/GretagMacbeth with the chart.<br>
+ <br>
+ The ColorChecker SG is relatively expensive, but is preferred by
+ many people because (like the ColorChecker and ColorCheckerDC) its
+ colors are composed of multiple different pigments, giving it
+ reflective spectra that are more representative of the real world,
+ unlike many other charts that are created out of combination of 3
+ or 4 colorants.<br>
+ A limited CIE reference file is available from X-Rite <a
+href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.txt">here</a>,
+ but it is not in the usual CGATS format. To convert it to a CIE
+ reference file useful for <span style="font-weight: bold;">scanin</span>,
+ you will need to edit the X-Rite file using a <span
+ style="text-decoration: underline;">plain text</span> editor,
+ first deleting everything before the line starting with "A1" and
everything after "N10", then prepending <a href="SG_header.txt">this @@ -801,78 +1210,119 @@ 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.<br> - If you do happen to have access to a more comprehensive instrument - measurement of the ColorChecker SG, or you have measured it - yourself using a color instrument,<br> - then you <span style="text-decoration: underline;">may</span> - need to convert the reference information from spectral <span - style="font-weight: bold;">ColorCheckerSG.txt</span> file to CIE - value <span style="font-weight: bold;">ColorCheckerSG.cie</span> - reference file, follow the following steps:<br> - <a href="txt2ti3.html">txt2ti3</a> - ColorCheckerSG.txt ColorCheckerSG<br> - <a href="spec2cie.html">spec2cie</a> - ColorCheckerSG.ti3 ColorCheckerSG.cie<br> - <br> - For the Eye-One Pro Scan Target 1.4 chart, the <span - style="font-weight: bold;"><span style="font-weight: bold;">ref/</span>i1_RGB_Scan_1.4.cht</span> - file should be used, and as there is no reference file - accompanying this chart, the chart needs to be read with an - instrument (usually the Eye-One Pro). This can be done using - chartread, making use of the chart reference file <span - style="font-weight: bold;">ref/i1_RGB_Scan_1.4.ti2</span>:<br> - <a href="chartread.html">chartread</a> -n -a - i1_RGB_Scan_1.4<br> - and then rename the resulting <span style="font-weight: bold;">i1_RGB_Scan_1.4.ti3</span> - file to <span style="font-weight: bold;">i1_RGB_Scan_1.4.cie</span><br> - <span style="font-weight: bold;"></span><br> - For the HutchColor HCT chart, the <span style="font-weight: - bold;"><span style="font-weight: bold;">ref/</span>Hutchcolor.cht</span> - file should be used, and the reference <span style="font-weight: - bold;">.txt</span> file downloaded from the HutchColor website.<br> - <br> - For the Christophe Métairie's Digital TargeT 003 chart with - 285 patches, the <span style="font-weight: bold;"><span - style="font-weight: bold;">ref/</span>CMP_DT_003.cht</span> - 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> - file should be used, and the cie reference <span - style="font-weight: bold;"></span>files come with the chart.<br> - <br> - For the LaserSoft DCPro chart, the <span style="font-weight: - bold;">ref/LaserSoftDCPro.cht</span> file should be used, and - reference <span style="font-weight: bold;">.txt</span> file - downloaded from the <a - href="http://www.silverfast.com/it8calibration/">Silverfast - website</a>.<br> - <br> - For the Datacolor SpyderCheckr, the <span style="font-weight: - bold;">ref/SpyderChecker.cht</span> file should be used, and a - reference <span style="font-weight: bold;">ref/SpyderChecker.cie - </span>file made from measuring a sample chart is also available. - Alternately you could create your own reference file by - transcribing the <a - href="http://spyder.datacolor.com/images/photo_checkr_colordatainfo.jpg">values</a> - on the Datacolor website. <br> - <br> - For the QPCard 201, the <span style="font-weight: bold;">ref/QPcard_201.cht</span> - file should be used, and a reference <span style="font-weight: - bold;">ref/QPcard_201.cie</span> file made from measuring a - sample chart is also available. <br> - <br> - For the QPCard 202, the <span style="font-weight: bold;">ref/QPcard_202.cht</span> - file should be used, and a reference <span style="font-weight: - bold;">ref/QPcard_202.cie</span> file made from measuring a - sample chart is also available. <br> - </div> - <br> - For any other type of chart, a chart recognition template file will - need to be created (this is beyond the scope of the current + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ header</a>, and appending <a href="SG_footer.txt">this footer</a>,
+ making sure there are no blank lines inserted in the process.
+ There are reports that X-Rite have experimented with different ink
+ formulations for certain patches, so the above reference may not
+ be as accurate as desired, and it is preferable to measure your
+ own chart using a spectrometer, if you have the capability.<br>
+ If you do happen to have access to a more comprehensive instrument
+ measurement of the ColorChecker SG, or you have measured it
+ yourself using a color instrument,<br>
+ then you <span style="text-decoration: underline;">may</span>
+ need to convert the reference information from spectral <span
+ style="font-weight: bold;">ColorCheckerSG.txt</span> file to CIE
+ value <span style="font-weight: bold;">ColorCheckerSG.cie</span>
+ reference file, follow the following steps:<br>
+ <a href="txt2ti3.html">txt2ti3</a>
+ ColorCheckerSG.txt ColorCheckerSG<br>
+ <a href="spec2cie.html">spec2cie</a>
+ ColorCheckerSG.ti3 ColorCheckerSG.cie<br>
+ <br>
+ For the Eye-One Pro Scan Target 1.4 chart, the <span
+ style="font-weight: bold;"><span style="font-weight: bold;">ref/</span>i1_RGB_Scan_1.4.cht</span>
+ file should be used, and as there is no reference file
+ accompanying this chart, the chart needs to be read with an
+ instrument (usually the Eye-One Pro). This can be done using
+ chartread, making use of the chart reference file <span
+ style="font-weight: bold;">ref/i1_RGB_Scan_1.4.ti2</span>:<br>
+ <a href="chartread.html">chartread</a> -n -a
+ i1_RGB_Scan_1.4<br>
+ and then rename the resulting <span style="font-weight: bold;">i1_RGB_Scan_1.4.ti3</span>
+ file to <span style="font-weight: bold;">i1_RGB_Scan_1.4.cie</span><br>
+ <span style="font-weight: bold;"></span><br>
+ For the HutchColor HCT chart, the <span style="font-weight:
+ bold;"><span style="font-weight: bold;">ref/</span>Hutchcolor.cht</span>
+ file should be used, and the reference <span style="font-weight:
+ bold;">.txt</span> file downloaded from the HutchColor website.<br>
+ <br>
+ For the Christophe Métairie's Digital TargeT 003 chart with 285
+ patches, the <span style="font-weight: bold;"><span
+ style="font-weight: bold;">ref/</span>CMP_DT_003.cht</span>
+ 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>
+ file should be used, and the cie reference <span
+ style="font-weight: bold;"></span>files come with the chart.<br>
+ <br>
+ For the LaserSoft DCPro chart, the <span style="font-weight:
+ bold;">ref/LaserSoftDCPro.cht</span> file should be used, and
+ reference <span style="font-weight: bold;">.txt</span> file
+ downloaded from the <a
+ href="http://www.silverfast.com/it8calibration/">Silverfast
+ website</a>.<br>
+ <br>
+ For the Datacolor SpyderCheckr, the <span style="font-weight:
+ bold;">ref/SpyderChecker.cht</span> file should be used, and a
+ reference <span style="font-weight: bold;">ref/SpyderChecker.cie
+ </span>file made from measuring a sample chart is also available.
+ Alternately you could create your own reference file by
+ transcribing the <a
+ href="http://spyder.datacolor.com/images/photo_checkr_colordatainfo.jpg">values</a>
+ on the Datacolor website. <br>
+ <br>
+ For the QPCard 201, the <span style="font-weight: bold;">ref/QPcard_201.cht</span>
+ file should be used, and a reference <span style="font-weight:
+ bold;">ref/QPcard_201.cie</span> file made from measuring a
+ sample chart is also available. <br>
+ <br>
+ For the QPCard 202, the <span style="font-weight: bold;">ref/QPcard_202.cht</span>
+ file should be used, and a reference <span style="font-weight:
+ bold;">ref/QPcard_202.cie</span> file made from measuring a
+ sample chart is also available. <br>
+ </div>
+ <br>
+ For any other type of chart, a chart recognition template file will
+ need to be created (this is beyond the scope of the current
documentation, although see the <a href="cht_format.html">.cht_format @@ -881,398 +1331,439 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t - documentation</a>).<br> - <br> - To create the scanner .ti3 file, run the <b>scanin</b> tool as - follows (assuming an IT8 chart is being used):<br> - <br> - <a href="scanin.html"> scanin</a> -v scanner.tif It8.cht It8ref.txt<br> - <br> - "It8ref.txt" or "It8ref.cie" is assumed to be the name of the CIE - reference file supplied by the chart manufacturer. The resulting - file will be named "<b>scanner.ti3</b>".<br> - <br> - <span style="font-weight: bold;">scanin</span> will process 16 bit - per component .tiff files, which (if the scanner is capable of - creating such files), may improve the quality of the profile. - <br> - <br> - If you have any doubts about the correctness of the chart - recognition, or the subsequent profile's delta E report is unusual, - then use the scanin diagnostic flags <a href="scanin.html#d">-dipn</a> - and examine the <span style="font-weight: bold;">diag.tif</span> - diagnostic file, to make sure that the patches are identified and - aligned correctly. If you have problems getting good automatic - alignment, then consider doing a manual alignment by locating the - fiducial marks on your scan, and feeding them into scanin <a - href="scanin.html#F">-F</a> parameters. The fiducial marks should - be listed in a clockwise direction starting at the top left.<br> - <h4><a name="PS4"></a>Creating a scanner or camera input profile</h4> - Similar to a display profile, an input profile can be either a - shaper/matrix or LUT based profile. Well behaved input devices will - probably give the best results with a shaper/matrix profile, and - this may also be the best choice if your test chart has a small or - unevenly distributed set of test patchs (ie. the IT8.7.2). If a - shaper/matrix profile is a poor fit, consider using a LUT type - profile.<br> - <br> - When creating a LUT type profile, there is the choice of XYZ or - L*a*b* PCS (Device independent, Profile Connection Space). Often for - input devices, it is better to choose the XYZ PCS, as this may be a - better fit given that input devices are usually close to being - linearly additive in behaviour.<br> - <br> - If the purpose of the input profile is to use it as a substitute for - a colorimeter, then the <b>-u</b> flag should be used to avoid - clipping values above the white point. Unless the shaper/matrix type - profile is a very good fit, it is probably advisable to use a LUT - type profile in this situation.<br> - <br> - To create a matrix/shaper profile, the following suffices:<br> - <br> - <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a> - <a href="colprof.html#E">-D"Scanner</a> <a href="colprof.html#E">A"</a> - <a href="colprof.html#q">-qm</a> <a href="colprof.html#a">-as</a> <a - href="colprof.html#p1">scanner</a><br> - <br> - For an XYZ PCS LUT based profile then the following would be used:<br> - <br> - <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a> - <a href="colprof.html#E">-D"Scanner A"</a> <a href="colprof.html#q">-qm</a> - <a href="colprof.html#a">-ax</a> <a href="colprof.html#p1">scanner</a><br> - <br> - For the purposes of a poor mans colorimeter, the following would - generally be used:<br> - <br> - <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a> - <a href="colprof.html#E">-D"Scanner A"</a> <a href="colprof.html#q">-qm</a> - <a href="colprof.html#a">-ax</a> <a href="colprof.html#u">-u</a> <a - href="colprof.html#p1">scanner</a><br> - <br> - Make sure you check the delta E report at the end of the profile - creation, to see if the profile is behaving reasonably.<br> - <br> - <br> - If profiling a <span style="font-weight: bold;">camera</span> in <span - style="font-weight: bold;">RAW</span> mode, then there may be some - advantage in creating a pure matrix only profile, in which it is - assumed that the camera response is completely linear. This may - reduce extrapolation artefacts. If setting the white point will be - done in some application, then it may also be an advantage to use - the <span style="font-weight: bold;">-u</span> flag and avoid - setting the white point to that of the profile chart:<br> - <br> - <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a> - <a href="colprof.html#E">-D"Camera"</a> <a href="colprof.html#q">-qm</a> - <a href="colprof.html#a">-am</a> <a href="colprof.html#u">-u</a> <a - href="colprof.html#p1">scanner</a><br> - <br> - <br> - <hr size="2" width="100%"> - <h3><a name="PP1"></a>Profiling Printers<br> - </h3> - The overall process is to create a set of device measurement target - values, print them out, measure them, and then create an ICC profile - from the measurements. If the printer is an RGB based printer, then - the process is only slightly more complicated than profiling a - display. If the printer is CMYK based, then some additional - parameters are required to set the total ink limit (TAC) and - black generation curve.<br> - <h4><a name="PP2"></a>Creating a print profile test chart</h4> - The first step in profiling any output device, is to create a set of - device colorspace test values. The important parameters needed are:<br> - <ul> - <li>What colorspace does the device use ?</li> - <li>How many test patches do I want to use/what paper size do I - want to use ?</li> - <li>What instrument am I going to use to read the patches ?<br> - </li> - <li>If it is a CMYK device, what is the total ink limit ?<br> - </li> - <li>What information do I already have about how the device - behaves ?</li> - </ul> - Most printers running through simple drivers will appear as if they - are RGB devices. In fact there is no such thing as a real RGB - printer, since printers use white media and the colorant must - subtract from the light reflected on it to create color, but the - printer itself turns the incoming RGB into the native print - colorspace, so for this reason we will tell targen to use the "Print - RGB" colorspace, so that it knows that it's really a subtractive - media. Other drivers will drive a printer more directly, and will - expect a CMYK profile. [Currently Argyll is not capable of creating - an ICC profile for devices with more colorants than CMYK. When this - capability is introduced, it will by creating an additional - separation profile which then allows the printer to be treated as a - CMY or CMYK printer.] One way of telling what sort of profile is - expected for your device is to examine an existing profile for that - device using <a href="http://www.argyllcms.com/doc/iccdump.html">iccdump</a>.<br> - <br> - The number of test patches will depend somewhat on what quality - profile you want to make, how well behaved the printer is, as well - as the effort needed to read the number of test values. Generally it - is convenient to fill a certain paper size with the maximum number - of test values that will fit.<br> - <br> - At a minimum, for an "RGB" device, a few hundred values are needed - (400-1000). For high quality CMYK profiles, 1000-3000 is not an - unreasonable number of patches.<br> - <br> - To assist the determination of test patch values, it can help to - have a rough idea of how the device behaves, so that the device test - point locations can be pre-conditioned. This could be in the form of - an ICC profile of a similar device, or a lower quality, or previous - profile for that particular device. If one were going to make a very - high quality Lut based profile, then it might be worthwhile to make - up a smaller, preliminary shaper/matrix profile using a few hundred - test points, before embarking on testing the device with several - thousand.<br> - <br> - The documentation for the <a - href="http://www.argyllcms.com/doc/targen.html">targen</a> tool - lists a <a href="http://www.argyllcms.com/doc/targen.html#Table">table</a> - of paper sizes and number of patches for typical situations.<br> - <br> - For a CMYK device, a total ink limit usually needs to be specified. - Sometimes a device will have a maximum total ink limit set by its - manufacturer or operator, and some CMYK systems (such as chemical - proofing systems) don't have any limit. Typical printing devices - such as Xerographic printers, inkjet printers and printing presses - will have a limit. The exact procedure for determining an ink limit - is outside the scope of this document, but one way of going about - this might be to generate some small (say a few hundred patches) - with targen & pritntarg with different total ink limits, and - printing them out, making the ink limit as large as possible without - striking problems that are caused by too much ink.<br> - <br> - Generally one wants to use the maximum possible amount of ink to - maximize the gamut available on the device. For most CMYK devices, - an ink limit between 200 and 400 is usual, but and ink limit of 250% - or over is generally desirable for reasonably dense blacks and dark - saturated colors. And ink limit of less than 200% will begin to - compromise the fully saturated gamut, as secondary colors (ie - combinations of any two primary colorants) will not be able to reach - full strength.<br> - <br> - Once an ink limit is used in printing the characterization test - chart for a device, it becomes a critical parameter in knowing what - the characterized gamut of the device is. If after printing the test - chart, a greater ink limit were to be used, the the software would - effectively be extrapolating the device behaviour at total ink - levels beyond that used in the test chart, leading to inaccuracies.<br> - <br> - Generally in Argyll, the ink limit is established when creating the - test chart values, and then carried through the profile making - process automatically. Once the profile has been made however, the - ink limit is no longer recorded, and you, the user, will have to - keep track of it if the ICC profile is used in any program than - needs to know the usable gamut of the device.<br> - <br> - <br> - Lets consider two devices in our examples, "PrinterA" which is an - "RGB" device, and "PrinterB" which is CMYK, and has a target ink - limit of 250%. <br> - <br> - The simplest approach is to make a set of test values that is - independent of the characteristics of the particular device:<br> - <br> - <a href="targen.html">targen</a> <a href="targen.html#v">-v</a> - <a href="targen.html#d">-d2</a> <a href="targen.html#f">-f1053</a> - <a href="targen.html#p1">PrinterA</a><br> - <br> - <a href="targen.html">targen</a> <a href="targen.html#v">-v</a> - <a href="targen.html#d">-d4</a> <a href="targen.html#l">-l260</a> - <a href="targen.html#f">-f1053</a> <a href="targen.html#p1">PrinterB</a><br> - <br> - The number of patches chosen here happens to be right for an A4 - paper size being read using a Spectroscan instrument. See the <a - href="targen.html#Table">table</a> in the <a - href="targen.html">targen</a> documentation for some other - suggested numbers.<br> - <br> - If there is a preliminary or previous profile called "OldPrinterA" - available, and we want to try creating a "pre-conditioned" set of - test values that will more efficiently sample the device response, - then the following would achieve this:<u><br> - </u><br> - <a href="targen.html">targen</a> <a href="targen.html#v">-v</a> - <a href="targen.html#d">-d2</a> <a href="targen.html#f">-f1053</a> - <a href="targen.html#c">-c OldPrinterA</a> <a - href="targen.html#p1">PrinterA</a><br> - <br> - <a href="targen.html">targen</a> <a href="targen.html#v">-v</a> - <a href="targen.html#d">-d4</a> <a href="targen.html#l">-l260</a> - <a href="targen.html#f">-f1053</a> <a href="targen.html#c">-c - OldPrinterB</a> <a href="targen.html#p1">PrinterB</a><br> - <a href="targen.html#p1"></a><br> - <br> - The output of <b>targen</b> will be the file PrinterA.ti1 and - PrinterB.ti1 respectively, containing the device space test values, - as well as expected CIE values used for chart recognition purposes.<br> - <br> - <h4><a name="PP2b"></a>Printing a print profile test chart<br> - <br> - </h4> - The next step is turn the test values in to a PostScript or TIFF - raster test file that can printed on the device. The basic - information that needs to be supplied is the type of instrument that - will be used to read the patches, as well as the paper size it is to - be formatted for.<br> - <br> - For an X-Rite DTP41, the following would be typical:<br> - <br> - <a href="printtarg.html">printtarg</a> <a href="printtarg.html#v">-v</a> - <a href="printtarg.html#i">-i41</a> <a href="printtarg.html#p">-pA4</a> - <a href="printtarg.html#p1">PrinterA</a><br> - <br> - For a Gretag Eye-One Pro, the following would be typical:<br> - <br> - <a href="printtarg.html">printtarg</a> <a href="printtarg.html#v">-v</a> - <a href="printtarg.html#i">-ii1</a> <a href="printtarg.html#p">-pA4</a> - <a href="printtarg.html#p1">PrinterA</a><br> - <br> - For using with a scanner as a colorimeter, the Gretag Spectroscan - layout is suitable, but the <a href="printtarg.html#s">-s</a> flag - should be used so as to generate a layout suitable for scan - recognition, as well as generating the scan recognition template - files. (You probably want to use less patches with <span - style="font-weight: bold;">targen</span>, when using the <span - style="font-weight: bold;">printtarg -s</span> flag, e.g. 1026 - patches for an A4R page, etc.) The following would be typical:<br> - <br> - <a href="printtarg.html">printtarg</a> <a href="printtarg.html#v">-v</a> - <a href="printtarg.html#s">-s</a> <a href="printtarg.html#i">-iSS</a> - <a href="printtarg.html#p">-pA4R</a> <a href="printtarg.html#p1">PrinterA</a><br> - <span style="font-weight: bold;"><br> - printtarg</span> reads the PrinterA.ti1 file, creates a - PrinterA.ti2 file containing the layout information as well as the - device values and expected CIE values, as well as a PrinterA.ps file - containing the test chart. If the <span style="font-weight: bold;">-s</span> - flag is used, one or more PrinterA.cht files is created to allow the - <a href="scanin.html">scanin</a> program to recognize the chart.<br> - <br> - To create TIFF raster files rather than PostScript, use the <a - href="printtarg.html#t"><span style="font-weight: bold;">-t</span></a> - flag.<br> - <br> - <span style="font-weight: bold;">GSview</span> is a good program to - use to check what the PostScript file will look like, without - actually printing it out. You could also use <span - style="font-weight: bold;">Photoshop</span> or <span - style="font-weight: bold;">ImageMagick</span> for this purpose.<br> - <br> - The last step is to print the chart out.<br> - <br> - Using a suitable PostScript or raster file printing program, - downloader, print the chart. If you are not using a TIFF test chart, - and you do not have a PostScript capable printer, then an - interpreter like GhostScript or even Photoshop could be used to - rasterize the file into something that can be printed. Note that it - is important that the PostScript interpreter or TIFF printing - application and printer configuration is setup for a device - profiling run, and that any sort of color conversion of color - correction be turned off so that the device values in the PostScript - or TIFF file are sent directly to the device. If the device has a - calibration system, then it would be usual to have setup and - calibrated the device before starting the profiling run, and to - apply calibration to the chart values. If Photoshop was to be used, - then either the chart needs to be a single page, or separate .eps or - .tiff files for each page should be used, so that they can be - converted and printed one at a time (see the <a - href="printtarg.html#e">-e</a> and <a href="printtarg.html#t">-t</a> - flags).<br> - <br> - <h4><a name="PP3"></a>Reading a print test chart using an instrument</h4> - Once the test chart has been printed, the color of the patches needs - to be read using a suitable instrument.<br> - <br> - Several different instruments are currently supported, some that - need to be used patch by patch, some read a strip at a time, and - some read a sheet at a time. See <a href="instruments.html">instruments</a> - for a current list.<br> - <br> - The instrument needs to be connected to your computer before running - the <a href="chartread.html">chartread</a> command. Both serial - port and USB connected Instruments are supported. A serial port to - USB adapter might have to be used if your computer doesn't have any - serial ports, and you have a serial interface connected instrument.<br> - <br> - If you run <a href="chartread.html">chartread</a> so as to print - out its usage message (ie. by using a <span style="font-weight: - bold;">-?</span> or <span style="font-weight: bold;">--</span> - flags), then it will list any identified serial ports or USB - connected instruments, and their corresponding number for the <a - href="chartread.html#c">-c</a> option. By default, <a - href="chartread.html">chartread</a> will try to connect to the - first available USB instrument, or an instrument on the first serial - port.<br> - <br> - The only arguments required is to specify the basename of the .ti2 - file. If a non-default serial port is to be used, then the <span - style="font-weight: bold;">-c</span> option would also be - specified.<br> - <br> - e.g. for a Spectroscan on the second port:<br> - <br> - <a href="chartread.html">chartread</a> <a href="chartread.html#c">-c2</a> - <a href="chartread.html#p1">PrinterA</a><br> - <br> - For a DTP41 to the default serial port:<br> - <br> - <a href="chartread.html">chartread</a><a href="chartread.html#i"></a> - <a href="chartread.html#p1">PrinterA</a><br> - <br> - <span style="font-weight: bold;">chartread</span> will interactively - prompt you through the process of reading each sheet or strip. See <a - href="chartread.html">chartread</a> for more details on the - responses for each type of instrument. Continue with <a - href="Scenarios.html#PP5">Creating a printer profile</a>.<br> - <br> - <h4><a name="PP4"></a>Reading a print test chart using a scanner or - camera<br> - </h4> - <br> - Argyll supports using a scanner or even a camera as a substitute for - a colorimeter. While a scanner or camera is no replacement for a - color measurement instrument, it may give acceptable results in some - situations, and may give better results than a generic profile for a - printing device.<br> - <br> - The main limitation of the scanner-as-colorimeter approach are:<br> - <br> - * The scanner dynamic range and/or precision may not match the - printers or what is required for a good profile.<br> - * The spectral interaction of the scanner test chart and printer - test chart with the scanner spectral response can cause color - errors.<br> - * Spectral differences caused by different black amounts in the - print test chart can cause color errors. <br> - * The scanner reference chart gamut may be much smaller than the - printers gamut, making the scanner profile too inaccurate to be - useful. <br> - <br> - As well as some of the above, a camera may not be suitable if it - automatically adjusts exposure or white point when taking a picture, - and this behavior cannot be disabled.<br> - <br> - The end result is often a profile that has a noticeable color cast, - compared to a profile created using a colorimeter or spectrometer.<br> - <br> - <br> - It is assumed that you have created a scanner or camera profile - following the <a - href="http://www.argyllcms.com/doc/Scenarios.html#PS1">procedure</a> - outline above. For best possible results it is advisable to both - profile the scanner or camera, and use it in scanning the printed - test chart, in as "raw" mode as possible (i.e. using 16 bits per - component images, if the scanner or camera is capable of doing so; - not setting white or black points, using a fixed exposure etc.). It - is generally advisable to create a LUT type input profile, and use - the <a href="http://www.argyllcms.com/doc/colprof.html#u">-u</a> - flag to avoid clipping scanned value whiter than the input - calibration chart.<br> - <br> - Scan or photograph your printer chart (or charts) on the scanner or + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ documentation</a>).<br>
+ <br>
+ To create the scanner .ti3 file, run the <b>scanin</b> tool as
+ follows (assuming an IT8 chart is being used):<br>
+ <br>
+ <a href="scanin.html"> scanin</a> -v scanner.tif It8.cht It8ref.txt<br>
+ <br>
+ "It8ref.txt" or "It8ref.cie" is assumed to be the name of the CIE
+ reference file supplied by the chart manufacturer. The resulting
+ file will be named "<b>scanner.ti3</b>".<br>
+ <br>
+ <span style="font-weight: bold;">scanin</span> will process 16 bit
+ per component .tiff files, which (if the scanner is capable of
+ creating such files), may improve the quality of the profile.
+ <br>
+ <br>
+ If you have any doubts about the correctness of the chart
+ recognition, or the subsequent profile's delta E report is unusual,
+ then use the scanin diagnostic flags <a href="scanin.html#d">-dipn</a>
+ and examine the <span style="font-weight: bold;">diag.tif</span>
+ diagnostic file, to make sure that the patches are identified and
+ aligned correctly. If you have problems getting good automatic
+ alignment, then consider doing a manual alignment by locating the
+ fiducial marks on your scan, and feeding them into scanin <a
+ href="scanin.html#F">-F</a> parameters. The fiducial marks should
+ be listed in a clockwise direction starting at the top left.<br>
+ <h4><a name="PS4"></a>Creating a scanner or camera input profile</h4>
+ Similar to a display profile, an input profile can be either a
+ shaper/matrix or LUT based profile. Well behaved input devices will
+ probably give the best results with a shaper/matrix profile, and
+ this may also be the best choice if your test chart has a small or
+ unevenly distributed set of test patchs (ie. the IT8.7.2). If a
+ shaper/matrix profile is a poor fit, consider using a LUT type
+ profile.<br>
+ <br>
+ When creating a LUT type profile, there is the choice of XYZ or
+ L*a*b* PCS (Device independent, Profile Connection Space). Often for
+ input devices, it is better to choose the XYZ PCS, as this may be a
+ better fit given that input devices are usually close to being
+ linearly additive in behaviour.<br>
+ <br>
+ If the purpose of the input profile is to use it as a substitute for
+ a colorimeter, then the <b>-u</b> flag should be used to avoid
+ clipping values above the white point. Unless the shaper/matrix type
+ profile is a very good fit, it is probably advisable to use a LUT
+ type profile in this situation.<br>
+ <br>
+ To create a matrix/shaper profile, the following suffices:<br>
+ <br>
+ <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a>
+ <a href="colprof.html#E">-D"Scanner</a> <a href="colprof.html#E">A"</a>
+ <a href="colprof.html#q">-qm</a> <a href="colprof.html#a">-as</a> <a
+ href="colprof.html#p1">scanner</a><br>
+ <br>
+ For an XYZ PCS LUT based profile then the following would be used:<br>
+ <br>
+ <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a>
+ <a href="colprof.html#E">-D"Scanner A"</a> <a href="colprof.html#q">-qm</a>
+ <a href="colprof.html#a">-ax</a> <a href="colprof.html#p1">scanner</a><br>
+ <br>
+ For the purposes of a poor mans colorimeter, the following would
+ generally be used:<br>
+ <br>
+ <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a>
+ <a href="colprof.html#E">-D"Scanner A"</a> <a href="colprof.html#q">-qm</a>
+ <a href="colprof.html#a">-ax</a> <a href="colprof.html#u">-u</a> <a
+ href="colprof.html#p1">scanner</a><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
+ the readings, average errors of 5 or less, and maximum errors of 15
+ or less would normally be expected. If errors are grossly higher
+ than this, then this is an indication that something is seriously
+ wrong with the device measurement, or profile creation.<br>
+ <br>
+ If profiling a <span style="font-weight: bold;">camera</span> in <span
+ style="font-weight: bold;">RAW</span> mode, then there may be some
+ advantage in creating a pure matrix only profile, in which it is
+ assumed that the camera response is completely linear. This may
+ reduce extrapolation artefacts. If setting the white point will be
+ done in some application, then it may also be an advantage to use
+ the <span style="font-weight: bold;">-u</span> flag and avoid
+ setting the white point to that of the profile chart:<br>
+ <br>
+ <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a>
+ <a href="colprof.html#E">-D"Camera"</a> <a href="colprof.html#q">-qm</a>
+ <a href="colprof.html#a">-am</a> <a href="colprof.html#u">-u</a> <a
+ href="colprof.html#p1">scanner</a><br>
+ <br>
+ <br>
+ <hr size="2" width="100%">
+ <h3><a name="PP1"></a>Profiling Printers<br>
+ </h3>
+ The overall process is to create a set of device measurement target
+ values, print them out, measure them, and then create an ICC profile
+ from the measurements. If the printer is an RGB based printer, then
+ the process is only slightly more complicated than profiling a
+ display. If the printer is CMYK based, then some additional
+ parameters are required to set the total ink limit (TAC) and
+ black generation curve.<br>
+ <h4><a name="PP2"></a>Creating a print profile test chart</h4>
+ The first step in profiling any output device, is to create a set of
+ device colorspace test values. The important parameters needed are:<br>
+ <ul>
+ <li>What colorspace does the device use ?</li>
+ <li>How many test patches do I want to use/what paper size do I
+ want to use ?</li>
+ <li>What instrument am I going to use to read the patches ?<br>
+ </li>
+ <li>If it is a CMYK device, what is the total ink limit ?<br>
+ </li>
+ <li>What information do I already have about how the device
+ behaves ?</li>
+ </ul>
+ Most printers running through simple drivers will appear as if they
+ are RGB devices. In fact there is no such thing as a real RGB
+ printer, since printers use white media and the colorant must
+ subtract from the light reflected on it to create color, but the
+ printer itself turns the incoming RGB into the native print
+ colorspace, so for this reason we will tell targen to use the "Print
+ RGB" colorspace, so that it knows that it's really a subtractive
+ media. Other drivers will drive a printer more directly, and will
+ expect a CMYK profile. [Currently Argyll is not capable of creating
+ an ICC profile for devices with more colorants than CMYK. When this
+ capability is introduced, it will by creating an additional
+ separation profile which then allows the printer to be treated as a
+ CMY or CMYK printer.] One way of telling what sort of profile is
+ expected for your device is to examine an existing profile for that
+ device using <a href="http://www.argyllcms.com/doc/iccdump.html">iccdump</a>.<br>
+ <br>
+ The number of test patches will depend somewhat on what quality
+ profile you want to make, how well behaved the printer is, as well
+ as the effort needed to read the number of test values. Generally it
+ is convenient to fill a certain paper size with the maximum number
+ of test values that will fit.<br>
+ <br>
+ At a minimum, for an "RGB" device, a few hundred values are needed
+ (400-1000). For high quality CMYK profiles, 1000-3000 is not an
+ unreasonable number of patches.<br>
+ <br>
+ To assist the determination of test patch values, it can help to
+ have a rough idea of how the device behaves, so that the device test
+ point locations can be pre-conditioned. This could be in the form of
+ an ICC profile of a similar device, or a lower quality, or previous
+ profile for that particular device. If one were going to make a very
+ high quality Lut based profile, then it might be worthwhile to make
+ up a smaller, preliminary shaper/matrix profile using a few hundred
+ test points, before embarking on testing the device with several
+ thousand.<br>
+ <br>
+ The documentation for the <a
+ href="http://www.argyllcms.com/doc/targen.html">targen</a> tool
+ lists a <a href="http://www.argyllcms.com/doc/targen.html#Table">table</a>
+ of paper sizes and number of patches for typical situations.<br>
+ <br>
+ For a CMYK device, a total ink limit usually needs to be specified.
+ Sometimes a device will have a maximum total ink limit set by its
+ manufacturer or operator, and some CMYK systems (such as chemical
+ proofing systems) don't have any limit. Typical printing devices
+ such as Xerographic printers, inkjet printers and printing presses
+ will have a limit. The exact procedure for determining an ink limit
+ is outside the scope of this document, but one way of going about
+ this might be to generate some small (say a few hundred patches)
+ with targen & pritntarg with different total ink limits, and
+ printing them out, making the ink limit as large as possible without
+ striking problems that are caused by too much ink.<br>
+ <br>
+ Generally one wants to use the maximum possible amount of ink to
+ maximize the gamut available on the device. For most CMYK devices,
+ an ink limit between 200 and 400 is usual, but and ink limit of 250%
+ or over is generally desirable for reasonably dense blacks and dark
+ saturated colors. And ink limit of less than 200% will begin to
+ compromise the fully saturated gamut, as secondary colors (ie
+ combinations of any two primary colorants) will not be able to reach
+ full strength.<br>
+ <br>
+ Once an ink limit is used in printing the characterization test
+ chart for a device, it becomes a critical parameter in knowing what
+ the characterized gamut of the device is. If after printing the test
+ chart, a greater ink limit were to be used, the the software would
+ effectively be extrapolating the device behaviour at total ink
+ levels beyond that used in the test chart, leading to inaccuracies.<br>
+ <br>
+ Generally in Argyll, the ink limit is established when creating the
+ test chart values, and then carried through the profile making
+ process automatically. Once the profile has been made however, the
+ ink limit is no longer recorded, and you, the user, will have to
+ keep track of it if the ICC profile is used in any program than
+ needs to know the usable gamut of the device.<br>
+ <br>
+ <br>
+ Lets consider two devices in our examples, "PrinterA" which is an
+ "RGB" device, and "PrinterB" which is CMYK, and has a target ink
+ limit of 250%. <br>
+ <br>
+ The simplest approach is to make a set of test values that is
+ independent of the characteristics of the particular device:<br>
+ <br>
+ <a href="targen.html">targen</a> <a href="targen.html#v">-v</a>
+ <a href="targen.html#d">-d2</a> <a href="targen.html#f">-f1053</a>
+ <a href="targen.html#p1">PrinterA</a><br>
+ <br>
+ <a href="targen.html">targen</a> <a href="targen.html#v">-v</a>
+ <a href="targen.html#d">-d4</a> <a href="targen.html#l">-l260</a>
+ <a href="targen.html#f">-f1053</a> <a href="targen.html#p1">PrinterB</a><br>
+ <br>
+ The number of patches chosen here happens to be right for an A4
+ paper size being read using a Spectroscan instrument. See the <a
+ href="targen.html#Table">table</a> in the <a
+ href="targen.html">targen</a> documentation for some other
+ suggested numbers.<br>
+ <br>
+ If there is a preliminary or previous profile called "OldPrinterA"
+ available, and we want to try creating a "pre-conditioned" set of
+ test values that will more efficiently sample the device response,
+ then the following would achieve this:<u><br>
+ </u><br>
+ <a href="targen.html">targen</a> <a href="targen.html#v">-v</a>
+ <a href="targen.html#d">-d2</a> <a href="targen.html#f">-f1053</a>
+ <a href="targen.html#c">-c OldPrinterA</a> <a
+ href="targen.html#p1">PrinterA</a><br>
+ <br>
+ <a href="targen.html">targen</a> <a href="targen.html#v">-v</a>
+ <a href="targen.html#d">-d4</a> <a href="targen.html#l">-l260</a>
+ <a href="targen.html#f">-f1053</a> <a href="targen.html#c">-c
+ OldPrinterB</a> <a href="targen.html#p1">PrinterB</a><br>
+ <a href="targen.html#p1"></a><br>
+ <br>
+ The output of <b>targen</b> will be the file PrinterA.ti1 and
+ PrinterB.ti1 respectively, containing the device space test values,
+ as well as expected CIE values used for chart recognition purposes.<br>
+ <br>
+ <h4><a name="PP2b"></a>Printing a print profile test chart<br>
+ <br>
+ </h4>
+ The next step is turn the test values in to a PostScript or TIFF
+ raster test file that can printed on the device. The basic
+ information that needs to be supplied is the type of instrument that
+ will be used to read the patches, as well as the paper size it is to
+ be formatted for.<br>
+ <br>
+ For an X-Rite DTP41, the following would be typical:<br>
+ <br>
+ <a href="printtarg.html">printtarg</a> <a href="printtarg.html#v">-v</a>
+ <a href="printtarg.html#i">-i41</a> <a href="printtarg.html#p">-pA4</a>
+ <a href="printtarg.html#p1">PrinterA</a><br>
+ <br>
+ For a Gretag Eye-One Pro, the following would be typical:<br>
+ <br>
+ <a href="printtarg.html">printtarg</a> <a href="printtarg.html#v">-v</a>
+ <a href="printtarg.html#i">-ii1</a> <a href="printtarg.html#p">-pA4</a>
+ <a href="printtarg.html#p1">PrinterA</a><br>
+ <br>
+ For using with a scanner as a colorimeter, the Gretag Spectroscan
+ layout is suitable, but the <a href="printtarg.html#s">-s</a> flag
+ should be used so as to generate a layout suitable for scan
+ recognition, as well as generating the scan recognition template
+ files. (You probably want to use less patches with <span
+ style="font-weight: bold;">targen</span>, when using the <span
+ style="font-weight: bold;">printtarg -s</span> flag, e.g. 1026
+ patches for an A4R page, etc.) The following would be typical:<br>
+ <br>
+ <a href="printtarg.html">printtarg</a> <a href="printtarg.html#v">-v</a>
+ <a href="printtarg.html#s">-s</a> <a href="printtarg.html#i">-iSS</a>
+ <a href="printtarg.html#p">-pA4R</a> <a href="printtarg.html#p1">PrinterA</a><br>
+ <span style="font-weight: bold;"><br>
+ printtarg</span> reads the PrinterA.ti1 file, creates a
+ PrinterA.ti2 file containing the layout information as well as the
+ device values and expected CIE values, as well as a PrinterA.ps file
+ containing the test chart. If the <span style="font-weight: bold;">-s</span>
+ flag is used, one or more PrinterA.cht files is created to allow the
+ <a href="scanin.html">scanin</a> program to recognize the chart.<br>
+ <br>
+ To create TIFF raster files rather than PostScript, use the <a
+ href="printtarg.html#t"><span style="font-weight: bold;">-t</span></a>
+ flag.<br>
+ <br>
+ <span style="font-weight: bold;">GSview</span> is a good program to
+ use to check what the PostScript file will look like, without
+ actually printing it out. You could also use <span
+ style="font-weight: bold;">Photoshop</span> or <span
+ style="font-weight: bold;">ImageMagick</span> for this purpose.<br>
+ <br>
+ The last step is to print the chart out.<br>
+ <br>
+ Using a suitable PostScript or raster file printing program,
+ downloader, print the chart. If you are not using a TIFF test chart,
+ and you do not have a PostScript capable printer, then an
+ interpreter like GhostScript or even Photoshop could be used to
+ rasterize the file into something that can be printed. Note that it
+ is important that the PostScript interpreter or TIFF printing
+ application and printer configuration is setup for a device
+ profiling run, and that any sort of color conversion of color
+ correction be turned off so that the device values in the PostScript
+ or TIFF file are sent directly to the device. If the device has a
+ calibration system, then it would be usual to have setup and
+ calibrated the device before starting the profiling run, and to
+ apply calibration to the chart values. If Photoshop was to be used,
+ then either the chart needs to be a single page, or separate .eps or
+ .tiff files for each page should be used, so that they can be
+ converted and printed one at a time (see the <a
+ href="printtarg.html#e">-e</a> and <a href="printtarg.html#t">-t</a>
+ flags).<br>
+ <br>
+ <h4><a name="PP3"></a>Reading a print test chart using an instrument</h4>
+ Once the test chart has been printed, the color of the patches needs
+ to be read using a suitable instrument.<br>
+ <br>
+ Several different instruments are currently supported, some that
+ need to be used patch by patch, some read a strip at a time, and
+ some read a sheet at a time. See <a href="instruments.html">instruments</a>
+ for a current list.<br>
+ <br>
+ The instrument needs to be connected to your computer before running
+ the <a href="chartread.html">chartread</a> command. Both serial
+ port and USB connected Instruments are supported. A serial port to
+ USB adapter might have to be used if your computer doesn't have any
+ serial ports, and you have a serial interface connected instrument.<br>
+ <br>
+ If you run <a href="chartread.html">chartread</a> so as to print
+ out its usage message (ie. by using a <span style="font-weight:
+ bold;">-?</span> or <span style="font-weight: bold;">--</span>
+ flags), then it will list any identified serial ports or USB
+ connected instruments, and their corresponding number for the <a
+ href="chartread.html#c">-c</a> option. By default, <a
+ href="chartread.html">chartread</a> will try to connect to the
+ first available USB instrument, or an instrument on the first serial
+ port.<br>
+ <br>
+ The only arguments required is to specify the basename of the .ti2
+ file. If a non-default serial port is to be used, then the <span
+ style="font-weight: bold;">-c</span> option would also be
+ specified.<br>
+ <br>
+ e.g. for a Spectroscan on the second port:<br>
+ <br>
+ <a href="chartread.html">chartread</a> <a href="chartread.html#c">-c2</a>
+ <a href="chartread.html#p1">PrinterA</a><br>
+ <br>
+ For a DTP41 to the default serial port:<br>
+ <br>
+ <a href="chartread.html">chartread</a><a href="chartread.html#i"></a>
+ <a href="chartread.html#p1">PrinterA</a><br>
+ <br>
+ <span style="font-weight: bold;">chartread</span> will interactively
+ prompt you through the process of reading each sheet or strip. See <a
+ href="chartread.html">chartread</a> for more details on the
+ responses for each type of instrument. Continue with <a
+ href="Scenarios.html#PP5">Creating a printer profile</a>.<br>
+ <br>
+ <h4><a name="PP4"></a>Reading a print test chart using a scanner or
+ camera<br>
+ </h4>
+ <br>
+ Argyll supports using a scanner or even a camera as a substitute for
+ a colorimeter. While a scanner or camera is no replacement for a
+ color measurement instrument, it may give acceptable results in some
+ situations, and may give better results than a generic profile for a
+ printing device.<br>
+ <br>
+ The main limitation of the scanner-as-colorimeter approach are:<br>
+ <br>
+ * The scanner dynamic range and/or precision may not match the
+ printers or what is required for a good profile.<br>
+ * The spectral interaction of the scanner test chart and printer
+ test chart with the scanner spectral response can cause color
+ errors.<br>
+ * Spectral differences caused by different black amounts in the
+ print test chart can cause color errors. <br>
+ * The scanner reference chart gamut may be much smaller than the
+ printers gamut, making the scanner profile too inaccurate to be
+ useful. <br>
+ <br>
+ As well as some of the above, a camera may not be suitable if it
+ automatically adjusts exposure or white point when taking a picture,
+ and this behavior cannot be disabled.<br>
+ <br>
+ The end result is often a profile that has a noticeable color cast,
+ compared to a profile created using a colorimeter or spectrometer.<br>
+ <br>
+ <br>
+ It is assumed that you have created a scanner or camera profile
+ following the <a
+ href="http://www.argyllcms.com/doc/Scenarios.html#PS1">procedure</a>
+ outline above. For best possible results it is advisable to both
+ profile the scanner or camera, and use it in scanning the printed
+ test chart, in as "raw" mode as possible (i.e. using 16 bits per
+ component images, if the scanner or camera is capable of doing so;
+ not setting white or black points, using a fixed exposure etc.). It
+ is generally advisable to create a LUT type input profile, and use
+ the <a href="http://www.argyllcms.com/doc/colprof.html#u">-u</a>
+ flag to avoid clipping scanned value whiter than the input
+ calibration chart.<br>
+ <br>
+ Scan or photograph your printer chart (or charts) on the scanner or
camera previously profiled. <big><span style="font-weight: bold;">The @@ -1282,97 +1773,134 @@ 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> - <br> - I will assume the resulting scan/photo input file is called <span - style="font-weight: bold;">PrinterB.tif</span> (or <span - style="font-weight: bold;">PrinterB1.tif</span>, <span - style="font-weight: bold;">PrinterB2.tif</span> etc. in the case - of multiple charts). As with profiling the scanner or camera, the - raster file need only be roughly cropped so as to contain the test - chart.<br> - <br> - The scanner recognition files created when <span - style="font-weight: bold;">printtarg</span> was run is assumed to - be called <span style="font-weight: bold;">PrinterB.cht</span>. - Using the scanner profile created previously (assumed to be called <span - style="font-weight: bold;">scanner.icm</span>), the printer test - chart scan patches are converted to CIE values using the <span - style="font-weight: bold;">scanin</span> tool:<br> - <br> - <a href="scanin.html">scanin</a> <a href="scanin.html#v">-v</a> <a - href="scanin.html#c">-c</a> <a href="scanin.html#cp1">PrinterB.tif</a> - <a href="scanin.html#cp2">PrinterB.cht</a> <a - href="scanin.html#cp3">scanner.icm</a> <a href="scanin.html#cp4">PrinterB</a><br> - <br> - If there were multiple test chart pages, the results would be - accumulated page by page using the <a href="scanin.html#ca">-ca</a> - option, ie., if there were 3 pages:<br> - <br> - <a href="scanin.html">scanin</a> <a href="scanin.html#v">-v</a> <a - href="scanin.html#c">-c</a> <a href="scanin.html#cp1">PrinterB1.tif</a> - <a href="scanin.html#cp2">PrinterB1.cht</a> <a - href="scanin.html#cp3">scanner.icm</a> <a href="scanin.html#cp4">PrinterB</a><br> - <a href="scanin.html">scanin</a> <a href="scanin.html#v">-v</a> <a - href="scanin.html#ca">-ca</a> <a href="scanin.html#cp1">PrinterB2.tif</a> - <a href="scanin.html#cp2">PrinterB2.cht</a> <a - href="scanin.html#cp3">scanner.icm</a> <a href="scanin.html#cp4">PrinterB</a><br> - <a href="scanin.html">scanin</a> <a href="scanin.html#v">-v</a> <a - href="scanin.html#ca">-ca</a> <a href="scanin.html#cp1">PrinterB3.tif</a> - <a href="scanin.html#cp2">PrinterB3.cht</a> <a - href="scanin.html#cp3">scanner.icm</a> <a href="scanin.html#cp4">PrinterB</a><br> - <br> - Now that the <span style="font-weight: bold;">PrinterB.ti3</span> - data has been obtained, the profile continue in the next section - with <span style="font-weight: bold;">Creating a printer profile</span>.<br> - <br> - If you have any doubts about the correctness of the chart - recognition, or the subsequent profile's delta E report is unusual, - then use the scanin diagnostic flags <a href="scanin.html#d">-dipn</a> - and examine the <span style="font-weight: bold;">diag.tif</span> - diagnostic file.<br> - <h4><a name="PP5"></a>Creating a printer profile<br> - </h4> - Creating an RGB based printing profile is very similar to creating a - display device profile. For a CMYK printer, some additional - information is needed to set the black generation.<br> - <br> - Where the resulting profile will be used conventionally (ie. using <a - href="collink.html">collink</a> <a href="collink.html#s">-s</a>, - or <a href="cctiff.html">cctiff</a> or most other "dumb" CMMs) it - is important to specify that gamut mapping should be computed for - the output (B2A) perceptual and saturation tables. This is done by - specifying a device profile as the parameter to the <a - href="colprof.html">colprof</a> <a href="colprof.html#S">-S</a> - flag. When you intend to create a "general use" profile, it can be a - good technique to specify the source gamut as the opposite type of - profile to that being created, i.e. if a printer profile is being - created, specify a display profile (e.g. sRGB) as the source gamut. - If a display profile is being created, then specify a printer - profile as the source (e.g. Figra, SWOP etc.). When linking to - the profile you have created this way as the output profile, then - use perceptual intent if the source is the opposite type, and - relative colorimetric if it is the same type.<br> - <br> - "Opposite type of profile" refers to the native gamut of the device, - and what its fundamental nature is, additive or subtractive. An - emissive display will have additive primaries (R, G & B), while - a reflective print, will have subtractive primaries (C, M, Y & - possibly others), irrespective of what colorspace the printer is - driven in (a printer might present an RGB interface, but internally - this will be converted to CMY, and it will have a CMY type of - gamut). Because of the complimentary nature of additive and - subtractive device primary colorants, these types of devices have - the most different gamuts, and hence need the most gamut mapping to - convert from one colorspace to the other.<br> - <br> - If you are creating a profile for a specific purpose, intending to - link it to a specific input profile, then you will get the best - results by specifying that source profile as the source gamut.<br> - <br> - If a profile is only going to be used as an input profile, or is - going to be used with a "smart" CMM (e.g. <a href="collink.html">collink</a> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ scanner or camera must be configured and used exactly the same
+ as it was when it was profiled.</span></big><br>
+ <br>
+ I will assume the resulting scan/photo input file is called <span
+ style="font-weight: bold;">PrinterB.tif</span> (or <span
+ style="font-weight: bold;">PrinterB1.tif</span>, <span
+ style="font-weight: bold;">PrinterB2.tif</span> etc. in the case
+ of multiple charts). As with profiling the scanner or camera, the
+ raster file need only be roughly cropped so as to contain the test
+ chart.<br>
+ <br>
+ The scanner recognition files created when <span
+ style="font-weight: bold;">printtarg</span> was run is assumed to
+ be called <span style="font-weight: bold;">PrinterB.cht</span>.
+ Using the scanner profile created previously (assumed to be called <span
+ style="font-weight: bold;">scanner.icm</span>), the printer test
+ chart scan patches are converted to CIE values using the <span
+ style="font-weight: bold;">scanin</span> tool:<br>
+ <br>
+ <a href="scanin.html">scanin</a> <a href="scanin.html#v">-v</a> <a
+ href="scanin.html#c">-c</a> <a href="scanin.html#cp1">PrinterB.tif</a>
+ <a href="scanin.html#cp2">PrinterB.cht</a> <a
+ href="scanin.html#cp3">scanner.icm</a> <a href="scanin.html#cp4">PrinterB</a><br>
+ <br>
+ If there were multiple test chart pages, the results would be
+ accumulated page by page using the <a href="scanin.html#ca">-ca</a>
+ option, ie., if there were 3 pages:<br>
+ <br>
+ <a href="scanin.html">scanin</a> <a href="scanin.html#v">-v</a> <a
+ href="scanin.html#c">-c</a> <a href="scanin.html#cp1">PrinterB1.tif</a>
+ <a href="scanin.html#cp2">PrinterB1.cht</a> <a
+ href="scanin.html#cp3">scanner.icm</a> <a href="scanin.html#cp4">PrinterB</a><br>
+ <a href="scanin.html">scanin</a> <a href="scanin.html#v">-v</a> <a
+ href="scanin.html#ca">-ca</a> <a href="scanin.html#cp1">PrinterB2.tif</a>
+ <a href="scanin.html#cp2">PrinterB2.cht</a> <a
+ href="scanin.html#cp3">scanner.icm</a> <a href="scanin.html#cp4">PrinterB</a><br>
+ <a href="scanin.html">scanin</a> <a href="scanin.html#v">-v</a> <a
+ href="scanin.html#ca">-ca</a> <a href="scanin.html#cp1">PrinterB3.tif</a>
+ <a href="scanin.html#cp2">PrinterB3.cht</a> <a
+ href="scanin.html#cp3">scanner.icm</a> <a href="scanin.html#cp4">PrinterB</a><br>
+ <br>
+ Now that the <span style="font-weight: bold;">PrinterB.ti3</span>
+ data has been obtained, the profile continue in the next section
+ with <span style="font-weight: bold;">Creating a printer profile</span>.<br>
+ <br>
+ If you have any doubts about the correctness of the chart
+ recognition, or the subsequent profile's delta E report is unusual,
+ then use the scanin diagnostic flags <a href="scanin.html#d">-dipn</a>
+ and examine the <span style="font-weight: bold;">diag.tif</span>
+ diagnostic file.<br>
+ <h4><a name="PP5"></a>Creating a printer profile<br>
+ </h4>
+ Creating an RGB based printing profile is very similar to creating a
+ display device profile. For a CMYK printer, some additional
+ information is needed to set the black generation.<br>
+ <br>
+ Where the resulting profile will be used conventionally (ie. using <a
+ href="collink.html">collink</a> <a href="collink.html#s">-s</a>,
+ or <a href="cctiff.html">cctiff</a> or most other "dumb" CMMs) it
+ is important to specify that gamut mapping should be computed for
+ the output (B2A) perceptual and saturation tables. This is done by
+ specifying a device profile as the parameter to the <a
+ href="colprof.html">colprof</a> <a href="colprof.html#S">-S</a>
+ flag. When you intend to create a "general use" profile, it can be a
+ good technique to specify the source gamut as the opposite type of
+ profile to that being created, i.e. if a printer profile is being
+ created, specify a display profile (e.g. sRGB) as the source gamut.
+ If a display profile is being created, then specify a printer
+ profile as the source (e.g. Figra, SWOP etc.). When linking to
+ the profile you have created this way as the output profile, then
+ use perceptual intent if the source is the opposite type, and
+ relative colorimetric if it is the same type.<br>
+ <br>
+ "Opposite type of profile" refers to the native gamut of the device,
+ and what its fundamental nature is, additive or subtractive. An
+ emissive display will have additive primaries (R, G & B), while
+ a reflective print, will have subtractive primaries (C, M, Y &
+ possibly others), irrespective of what colorspace the printer is
+ driven in (a printer might present an RGB interface, but internally
+ this will be converted to CMY, and it will have a CMY type of
+ gamut). Because of the complimentary nature of additive and
+ subtractive device primary colorants, these types of devices have
+ the most different gamuts, and hence need the most gamut mapping to
+ convert from one colorspace to the other.<br>
+ <br>
+ If you are creating a profile for a specific purpose, intending to
+ link it to a specific input profile, then you will get the best
+ results by specifying that source profile as the source gamut.<br>
+ <br>
+ If a profile is only going to be used as an input profile, or is
+ going to be used with a "smart" CMM (e.g. <a href="collink.html">collink</a>
<a href="collink.html#g">-g</a> or <a href="collink.html#G">-G</a>), then @@ -1383,69 +1911,113 @@ then - it can save considerable processing time and space if the -b flag is - used, and the -S flag not used.<br> - <br> - For an RGB printer intended to print RGB originals, the following - might be a typical profile usage:<br> - <br> - <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a> - <a href="colprof.html#E">-D"Printer A"</a> <a href="colprof.html#q">-qm</a> - <a href="colprof.html#S">-S</a><a href="colprof.html#S"> sRGB.icm</a> - <a href="colprof.html#c">-cmt</a> <a href="colprof.html#d">-dpp</a> - <a href="colprof.html#p1">PrinterA</a><br> - <br> - or if you intent to print from Fogra, SWOP or other standard CMYK - style originals:<br> - <br> - <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a> - <a href="colprof.html#E">-D"Printer A"</a> <a href="colprof.html#q">-qm</a> - <a href="colprof.html#S">-S</a><a href="colprof.html#S"> - fogra39l.icm</a> <a href="colprof.html#c">-cmt</a> <a - href="colprof.html#d">-dpp</a> <a href="colprof.html#p1">PrinterA</a><br> - <br> - If you know what colorspace your originals are in, use that as the - argument to <span style="font-weight: bold;">-S</span>.<br> - <br> - <h4><a name="PP6"></a>Choosing a black generation curve (and other - CMYK printer options)<br> - </h4> - For a CMYK printer, it would be normal to specify the type of black - generation, either as something simple, or as a specific curve. The - documentation in <a href="colprof.html#k">colprof</a> for the - details of the options.<span style="font-weight: bold;"><br> - <br> - Note</span> that making a good choice of black generation curve - can affect things such as: how robust neutrals are given printer - drift or changes in viewing lighting, how visible screening is, and - how smooth looking the B2A conversion is.<br> - <br> - For instance, maximizing the level of K will mean that the neutral - colors are composed of greater amounts of Black ink, and black ink - retains its neutral appearance irrespective of printer behavior or - the spectrum of the illuminant used to view the print. On the other - hand, output which is dominantly from one of the color channels will - tend to emphasize the screening pattern and any unevenness (banding - etc.) of that channel, and the black channel in particular has the - highest visibility. So in practice, some balance between the levels - of the four channels is probably best, with more K if the screening - is fine and a robust neutral balance is important, or less K if the - screening is more visible and neutral balance is less critical. The - levels of K at the edges of the gamut of the device will be fixed by - the nature of the ink combinations that maximize the gamut (ie. - typically zero ink for light chromatic colors, some combination for - dark colors, and a high level of black for very dark near neutrals), - and it is also usually important to set a curve that smoothly - transitions to the K values at the gamut edges. Dramatic changes in - K imply equally dramatic changes in CMY, and these abrupt - transitions will reveal the limited precision and detail that can be - captured in a lookup table based profile, often resulting in a - "bumpy" looking output.<br> - <br> - If you want to experiment with the various black generation - parameters, then it might be a good idea to create a preliminary - profile (using <a href="colprof.html#q">-ql</a> <a - href="colprof.html#b">-b</a> <a href="colprof.html#ni">-no</a>, <a + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ it can save considerable processing time and space if the -b flag is
+ used, and the -S flag not used.<br>
+ <br>
+ For an RGB printer intended to print RGB originals, the following
+ might be a typical profile usage:<br>
+ <br>
+ <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a>
+ <a href="colprof.html#E">-D"Printer A"</a> <a href="colprof.html#q">-qm</a>
+ <a href="colprof.html#S">-S</a><a href="colprof.html#S"> sRGB.icm</a>
+ <a href="colprof.html#c">-cmt</a> <a href="colprof.html#d">-dpp</a>
+ <a href="colprof.html#p1">PrinterA</a><br>
+ <br>
+ or if you intent to print from Fogra, SWOP or other standard CMYK
+ style originals:<br>
+ <br>
+ <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a>
+ <a href="colprof.html#E">-D"Printer A"</a> <a href="colprof.html#q">-qm</a>
+ <a href="colprof.html#S">-S</a><a href="colprof.html#S">
+ fogra39l.icm</a> <a href="colprof.html#c">-cmt</a> <a
+ href="colprof.html#d">-dpp</a> <a href="colprof.html#p1">PrinterA</a><br>
+ <br>
+ If you know what colorspace your originals are in, use that as the
+ argument to <span style="font-weight: bold;">-S</span>.<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
+ the readings, average errors of 5 or less, and maximum errors of 15
+ or less would normally be expected. If errors are grossly higher
+ than this, then this is an indication that something is seriously
+ wrong with the device measurement, or profile creation.
+ <h4><a name="PP6"></a>Choosing a black generation curve (and other
+ CMYK printer options)<br>
+ </h4>
+ For a CMYK printer, it would be normal to specify the type of black
+ generation, either as something simple, or as a specific curve. The
+ documentation in <a href="colprof.html#k">colprof</a> for the
+ details of the options.<span style="font-weight: bold;"><br>
+ <br>
+ Note</span> that making a good choice of black generation curve
+ can affect things such as: how robust neutrals are given printer
+ drift or changes in viewing lighting, how visible screening is, and
+ how smooth looking the B2A conversion is.<br>
+ <br>
+ For instance, maximizing the level of K will mean that the neutral
+ colors are composed of greater amounts of Black ink, and black ink
+ retains its neutral appearance irrespective of printer behavior or
+ the spectrum of the illuminant used to view the print. On the other
+ hand, output which is dominantly from one of the color channels will
+ tend to emphasize the screening pattern and any unevenness (banding
+ etc.) of that channel, and the black channel in particular has the
+ highest visibility. So in practice, some balance between the levels
+ of the four channels is probably best, with more K if the screening
+ is fine and a robust neutral balance is important, or less K if the
+ screening is more visible and neutral balance is less critical. The
+ levels of K at the edges of the gamut of the device will be fixed by
+ the nature of the ink combinations that maximize the gamut (ie.
+ typically zero ink for light chromatic colors, some combination for
+ dark colors, and a high level of black for very dark near neutrals),
+ and it is also usually important to set a curve that smoothly
+ transitions to the K values at the gamut edges. Dramatic changes in
+ K imply equally dramatic changes in CMY, and these abrupt
+ transitions will reveal the limited precision and detail that can be
+ captured in a lookup table based profile, often resulting in a
+ "bumpy" looking output.<br>
+ <br>
+ If you want to experiment with the various black generation
+ parameters, then it might be a good idea to create a preliminary
+ profile (using <a href="colprof.html#q">-ql</a> <a
+ href="colprof.html#b">-b</a> <a href="colprof.html#ni">-no</a>, <a
href="colprof.html#no">-ni</a> and no <a href="colprof.html#S">-S</a>), @@ -1454,406 +2026,443 @@ then - and then used <a href="xicclu.html#g">xicclu</a> to explore the - effect of the parameters.<br> - <br> - For instance, say we have our CMYK .ti3 file <span - style="font-weight: bold;">PrinterB.ti3</span>. First we make a - preliminary profile called <span style="font-weight: bold;">PrinterBt</span>:<br> - <br> - copy PrinterB.ti3 PrinterBt.ti3 (Use - "cp" on Linux or OSX of course.)<br> - <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a> - <a href="colprof.html#q">-qm</a> <a href="colprof.html#b">-b</a> <a - href="colprof.html#c">-cmt</a> <a href="colprof.html#d">-dpp</a> - <a href="colprof.html#p1">PrinterBt</a><br> - <br> - Then see what the minimum black level down the neutral axis can be. - Note that we need to also set any ink limits we've decided on as - well (coloprof defaulting to 10% less than the value recorded in the - .ti3 file). In this example the test chart has a 300% total ink - limit, and we've decided to use 290%:<br> - <br> - <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a - href="xicclu.html#k">-kz</a> <a href="xicclu.html#l">-l290</a> <a - href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a - href="xicclu.html#p1">PrinterBt.icm</a><br> - <br> - Which might be a graph something like this:<br> - <br> - <img alt="Graph of CMYK neutral axis with minimum K" - src="Kgraph1.jpg" style="width: 250px; height: 250px;"><br> - <br> - Note how the minimum black is zero up to 93% of the - white->black L* curve, and then jumps up to 87%. This is because - we've reached the total ink limit, and K then has to be substituted - for CMY, to keep the total under the total ink limit.<br> - <br> - Then let's see what the maximum black level down the neutral axis - can be:<br> - <br> - <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a - href="xicclu.html#k">-kx</a> <a href="xicclu.html#l">-l290</a> <a - href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a - href="xicclu.html#p1">PrinterBt.icm</a><br> - <br> - Which might be a graph something like this:<br> - <br> - <img alt="Graph of CMYK neutral axis with maximum K" - src="Kgraph2.jpg" style="width: 250px; height: 250px;"><br> - <br> - Note how the CMY values are fairly low up to 93% of the - white->black L* curve (the low levels of CMY are helping set the - neutral color), and then they jump up. This is because we've reach - the point where black on it's own, isn't as dark as the color that - can be achieved using CMY and K. Because the K has a dominant effect - on the hue of the black, the levels of CMY are often fairly volatile - in this region.<br> - <br> - Any K curve we specify must lie between the black curves of the - above two graphs.<br> - <br> - Let's say we'd like to chose a moderate black curve, one that aims - for about equal levels of CMY and K. We should also aim for it to be - fairly smooth, since this will minimize visual artefacts caused by - the limited fidelity that profile LUT tables are able to represent - inside the profile.<br> - <br> - <img style="width: 340px; height: 258px;" alt="-k parameters" - src="Kparams.jpg"><br> - <br> - <br> - For minimum discontinuities we should aim for the curve to finish at - the point it has to reach to satisfy the total ink limit at 87% - curve and 93% black. For a first try we can simply set a straight - line to that point: <br> - <br> - <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a - href="xicclu.html#k">-kp 0 0 .93 .87 1.0</a> <a - href="xicclu.html#l">-l290</a> <a href="xicclu.html#f">-fif</a> <a - href="xicclu.html#i">-ir</a> <a href="xicclu.html#p1">PrinterBt.icm</a><br> - <br> - <img alt="Graph of CMYK neutral axis with kp 0 0 1.0 1.0 1.0 -l290" - src="Kgraph3.jpg" style="width: 250px; height: 250px;"><br> - <br> - The black "curve" hits the 93%/87% mark well, but is a bit too far - above CMY, so we'll try making the black curve concave:<br> - <br> - <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a - href="xicclu.html#k">-kp </a><a href="xicclu.html#k">0 0 .93 .87 - 0.65</a> <a href="xicclu.html#l">-l290</a> <a - href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a - href="xicclu.html#p1">PrinterBt.icm</a><br> - <br> - <img alt="Graph of CMYK neutral axis with -kp 0 .05 1 .9 1 -l290" - src="Kgraph4.jpg" style="width: 250px; height: 249px;"><br> - <br> - This looks just about perfect, so the the curve parameters can now - be used to generate our real profile:<br> - <br> - <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a> - <a href="colprof.html#E">-D"Printer B"</a> <a href="colprof.html#q">-qm</a> - <a href="colprof.html#k">-kp </a><a href="xicclu.html#k">0 0 .93 - .87 0.65</a> <a href="colprof.html#S">-S</a><a - href="colprof.html#S"> sRGB.icm</a> <a href="colprof.html#c">-cmt</a> - <a href="colprof.html#d">-dpp</a> <a href="colprof.html#p1">PrinterB</a><br> - <br> - and the resulting B2A table black curve can be checked using xicclu:<br> - <br> - <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a - href="xicclu.html#f">-fb</a> <a href="xicclu.html#i">-ir</a> <a - href="xicclu.html#p1">PrinterB.icm</a><br> - <br> - <img style="width: 250px; height: 250px;" alt="sadsadas" - src="Kgraph5.jpg"><br> - <br> - <br> - <hr style="margin-left: 0px; margin-right: auto; width: 20%; height: - 2px;"><br> - <span style="font-weight: bold;">Examples of other inkings:<br> - <br> - </span>A smoothed zero black inking:<br> - <br> - <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a - href="xicclu.html#k">-kp </a><a href="xicclu.html#k">0 .7 .93 .87 - 1.0</a> <a href="xicclu.html#l">-l290</a> <a - href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a - href="xicclu.html#p1">PrinterBt.icm</a><br> - <br> - <img style="width: 250px; height: 250px;" alt="sadsadas" - src="Kgraph6.jpg"><br> - <br> - A low black inking:<br> - <br> - <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a - href="xicclu.html#k">-kp </a><a href="xicclu.html#k">0 0 .93 .87 - 0.15</a> <a href="xicclu.html#l">-l290</a> <a - href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a - href="xicclu.html#p1">PrinterBt.icm</a><br> - <br> - <img style="width: 250px; height: 250px;" alt="sadsadas" - src="Kgraph7.jpg"><br> - <br> - <br> - A high black inking:<br> - <br> - <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a - href="xicclu.html#k">-kp </a><a href="xicclu.html#k">0 0 .93 .87 - 1.2</a> <a href="xicclu.html#l">-l290</a> <a - href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a - href="xicclu.html#p1">PrinterBt.icm</a><br> - <br> - <img style="width: 250px; height: 250px;" alt="sadsadas" - src="Kgraph8.jpg"><br> - <br> - <span style="font-weight: bold;"></span> - <h4>Overriding the ink limit<br> - </h4> - Normally the total ink limit will be read from the <span - style="font-weight: bold;">PrinterB.ti3</span> file, and will be - set at a level 10% lower than the number used in creating the test - chart values using <a href="targen.html#l">targen -l</a>. If you - want to override this with a lower limit, then use the <a - href="colprof.html#l">-l flag</a>.<br> - <br> - <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a> - <a href="colprof.html#E">-D"Printer B"</a> <a href="colprof.html#q">-qm</a> - <a href="colprof.html#S">-S</a><a href="colprof.html#S"> sRGB.icm</a> - <a href="colprof.html#c">-cmt</a> <a href="colprof.html#d">-dpp</a> - <a href="colprof.html#k">-kr</a> <a href="xicclu.html#l">-l290</a> - <a href="colprof.html#p1">PrinterB</a><br> - <br> - Make sure you check the delta E report at the end of the profile - creation, to see if the profile is behaving reasonably.<br> - <br> - One way of checking that your ink limit is not too high, is to use "<span - style="font-weight: bold;">xicc -fif -ia</span>" to check, by - setting different ink limits using the <span style="font-weight: - bold;">-l</span> option, feeding Lab = 0 0 0 into it, and checking - the resulting black point. Starting with the ink limit used - with <span style="font-weight: bold;">targen</span> for the test - chart, reduce it until the black point starts to be affected. If it - is immediately affected by any reduction in the ink limit, then the - black point may be improved by increasing the ink limit used to - generate the test chart and then re-print and re-measuring it, - assuming other aspects such as wetness, smudging, spreading or - drying time are not an issue.<br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <h3><a name="PC1"></a>Calibrating Printers<br> - </h3> - <span style="font-weight: bold;">Profiling</span> creates a - description of how a device behaves, while <span - style="font-weight: bold;">calibration</span> on the other hand is - intended to <span style="text-decoration: underline;">change</span> - how a device behaves. Argyll has the ability to create per-channel - device space calibration curves for print devices, that can then be - used to improve the behavior of of the device, making a subsequent - profile fit the device more easily and also allow day to day - correction of device drift without resorting to a full re-profile.<br> - <br> - <span style="font-weight: bold;">NOTE:</span> Because calibration - adds yet another layer to the way color is processed, it is - recommended that it not be attempted until the normal profiling - workflow is established, understood and verified.<br> - <h4><a name="PC2"></a>Calibrated print workflows</h4> - There are two main workflows that printer calibration curves can be - applied to:<br> - <br> - <span style="text-decoration: underline;">Workflow <span - style="font-weight: bold;">with</span> native calibration - capability</span>:<br> - <br> - Firstly the printer itself may have the capability of using per - channel calibration curves. In this situation, the calibration - process will be largely independent of profiling. Firstly the - printer is configured to have both its color management and - calibration disabled (the latter perhaps achieved by loading linear - calibration curves), and a print calibration test chart that - consists of per channel color wedges is printed. The calibration - chart is read and the resulting .ti3 file converted into calibration - curves by processing it using <span style="font-weight: bold;">printcal</span>. - The calibration is then installed into the printer. Subsequent - profiling will be performed on the <span style="text-decoration: - underline;">calibrated</span> printer (ie. the profile test chart - will have the calibration curves applied to it by the printer, and - the resulting ICC profile will represent the behavior of the - calibrated printer.)<br> - <br> - <span style="text-decoration: underline;">Workflow <span - style="font-weight: bold;">without</span> native calibration - capability</span>:<br> - <br> - The second workflow is one in which the printer has no calibration - capability itself. In this situation, the calibration process will - have to be applied using the ICC color management tools, so careful - coordination with profiling is needed. Firstly the printer is - configured to have its color management disabled, and a print - calibration test chart that consists of per channel color wedges is - printed. The calibration chart is converted into calibration curves - by reading it and then processing the resultant .ti3 using <span - style="font-weight: bold;">printcal</span>,. During the subsequent - <span style="text-decoration: underline;">profiling</span>, the - calibration curves will need to be applied to the profile test chart - in the process of using <span style="font-weight: bold;">printtarg</span>. - Once the the profile has been created, then in subsequent printing - the calibration curves will need to be applied to an image being - printed either explicitly when using <span style="font-weight: - bold;">cctiff</span> to apply color profiles <span - style="text-decoration: underline;">and</span> calibration, <span - style="font-weight: bold;">OR</span> by creating a version of the - profile that has had the calibration curves incorporated into it - using the <span style="font-weight: bold;">applycal</span> tool. - The latter is useful when some CMM (color management module) other - than <span style="font-weight: bold;">cctiff </span>is being used.<br> - <br> - Once calibration aim targets for a particular device and mode - (screening, paper etc.) have been established, then the printer can - be re-calibrated at any time to bring its per channel behavior back - into line if it drifts, and the new calibration curves can be - installed into the printer, or re-incorporated into the profile. - - <h4><a name="PC3"></a>Creating a print calibration test chart</h4> - The first step is to create a print calibration test chart. Since - calibration only creates per-channel curves, only single channel - step wedges are required for the chart. The main choice is the - number of steps in each wedge. For simple fast calibrations perhaps - as few as 20 steps per channel may be enough, but for a better - quality of calibration something like 50 or more steps would be a - better choice.<br> - <br> - Let's consider two devices in our examples, "PrinterA" which is an - "RGB" printer device, and "PrinterB" which is CMYK. In fact there is - no such thing as a real RGB printer, since printers use white media - and the colorant must subtract from the light reflected on it to - create color, but the printer itself turns the incoming RGB into the - native print colorspace, so for this reason we are careful to tell - targen to use the "Print RGB" colorspace, so that it knows to create - step wedges from media white to full colorant values.<br> - <br> - For instance, to create a 50 steps per channel calibration test - chart for our RGB and CMYK devices, the following would be - sufficient:<br> - <br> - <a href="targen.html">targen</a> <a href="targen.html#v">-v</a> - <a href="targen.html#d">-d2</a> <a href="targen.html#s">-s50</a> - <a href="targen.html#e">-e3</a> <a href="targen.html#f">-f0</a> <a - href="targen.html#p1">PrinterA_c</a><br> - <br> - <a href="targen.html">targen</a> <a href="targen.html#v">-v</a> - <a href="targen.html#d">-d4</a> <a href="targen.html#s">-s50</a> - <a href="targen.html#e">-e4</a> <a href="targen.html#f">-f0</a> <a - href="targen.html#p1">PrinterB_c</a><br> - <a href="targen.html#p1"></a><br> - For an outline of how to then print and read the resulting test - chart, see <a href="Scenarios.html#PP2b">Printing a print - profile test chart</a>, and <a href="Scenarios.html#PP3">Reading - a print test chart using an instrument</a>. Note that the printer - must be in an un-profiled and un-calibrated mode when doing this - print. Having done this, there will be a PrinterA.ti3 or - PrinterB.ti3 file containing the step wedge calibration chart - readings.<br> - <br> - <span style="font-weight: bold;">NOTE</span> that if you are - calibrating a raw printer driver, and there is considerable dot - gain, then you may want to use the <a href="targen.html#p">-p</a> - parameter to adjust the test chart point distribution to spread them - more evenly in perceptual space, giving more accurate control over - the calibration. Typically this will be a value greater than one for - a device that has dot gain, e.g. values of 1.5, 2.0 or 2.5 might be - good places to start. You can do a preliminary calibration and use - the verbose output of printcal to recommend a suitable value for <span - style="font-weight: bold;">-p</span>.<br> - <h4><a name="PC4"></a>Creating a printer calibration<br> - </h4> - The <a href="printcal.html">printcal</a> tool turns a calibration - chart <a href="File_Formats.html#.ti3">.ti3</a> file into a <a - href="File_Formats.html#.cal">.cal</a> file. It has three main - operating modes:- Initial calibration, Re-Calibration, and - Verification. (A fourth mode, "Imitation" is very like Initial - Calibration, but is used for establishing a calibration target that - a similar printer can attempt to imitate.)<br> - <br> - The distinction between Initial Calibration and Re-Calibration is - that in the initial calibration we establish the "aim points" or - response we want out of the printer after calibration. There are - three basic parameters to set this for each channel: Maximum level, - minimum level, and curve shape.<br> - <br> - By default the maximum level will be set using a heuristic which - attempts to pick the point when there is diminishing returns for - applying more colorant. This can be overridden using the <span - style="font-weight: bold;">-x# percent</span> option, where <span - style="font-weight: bold;">#</span> represents the choice of - channel this will be applied to. The parameter is the percentage of - device maximum. <br> - <br> - The minimum level defaults to 0, but can be overridden using the <span - style="font-weight: bold;">-n# deltaE</span> option. A minimum of - 0 means that zero colorant will correspond to the natural media - color, but it may be desirable to set a non-pure media color using - calibration for the purposes of emulating some other media. The - parameter is in Delta E units.<br> - <br> - The curve shape defaults to being perceptually uniform, which means - that even steps of calibrated device value result in perceptually - even color steps. In some situations it may be desirable to alter - this curve (for instance when non color managed output needs to be - sent to the calibrated printer), and a simple curve shape target can - be set using the <span style="font-weight: bold;">-t# percent</span> - parameter. This affects the output value at 50% input value, and - represents the percentage of perceptual output. By default it is 50% - perceptual output for 50% device input.<br> - <br> - Once a device has been calibrated, it can be re-calibrated to the - same aim target.<br> - <br> - Verification uses a calibration test chart printed through the - calibration, and compares the achieved response to the aim target.<br> - <br> - The simplest possible way of creating the <span style="font-weight: - bold;">PrinterA.cal</span> file is:<br> - <br> - <a href="printcal.html">printcal</a> <a - href="printcal.html#i">-i</a> <a href="colprof.html#p2">PrinterA_c</a><br> - <br> - For more detailed information, you can add the <span - style="font-weight: bold;">-v</span> and <span - style="font-weight: bold;">-p</span> flags:<br> - <br> - <a href="printcal.html">printcal</a> <a - href="printcal.html#v">-v</a> <a href="printcal.html#p">-p</a> <a - href="printcal.html#i">-i</a> <a href="colprof.html#p2">PrinterB_c</a><br> - <br> - (You will need to select the plot window and hit a key to advance - past each plot).<br> - <br> - For re-calibration, the name of the previous calibration file will - need to be supplied, and a new calibration<br> - file will be created:<br> - <br> - <a href="printcal.html">printcal</a> <a - href="printcal.html#v">-v</a> <a href="printcal.html#p">-p</a> <a - href="printcal.html#r">-r</a> <a href="colprof.html#p1">PrinterB_c_old</a> - <a href="colprof.html#p2">PrinterB_c_new</a><br> - <br> - Various aim points are normally set automatically by <span - style="font-weight: bold;">printcal</span>, but these can be - overridden using the <a href="colprof.html#x">-x</a>, <a - href="colprof.html#n">-n</a> and <a href="colprof.html#t">-t</a> - options. e.g. say we wanted to set the maximum ink for Cyan to 80% - and Black to 95%, we might use:<br> - <br> - <a href="printcal.html">printcal</a> <a - href="printcal.html#v">-v</a> <a href="printcal.html#p">-p</a> <a - href="printcal.html#i">-i</a> <a href="colprof.html#x">-xc 80</a> - <a href="colprof.html#x">-xk 95</a> <a href="colprof.html#p2">PrinterB_c</a><br> - <br> - <a href="colprof.html#p2"></a> - <h4><a name="PC5"></a>Using a printer calibration</h4> - The resulting calibration curves can be used with the following - other Argyll tools:<br> - <br> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ and then used <a href="xicclu.html#g">xicclu</a> to explore the
+ effect of the parameters.<br>
+ <br>
+ For instance, say we have our CMYK .ti3 file <span
+ style="font-weight: bold;">PrinterB.ti3</span>. First we make a
+ preliminary profile called <span style="font-weight: bold;">PrinterBt</span>:<br>
+ <br>
+ copy PrinterB.ti3 PrinterBt.ti3 (Use
+ "cp" on Linux or OSX of course.)<br>
+ <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a>
+ <a href="colprof.html#q">-qm</a> <a href="colprof.html#b">-b</a> <a
+ href="colprof.html#c">-cmt</a> <a href="colprof.html#d">-dpp</a>
+ <a href="colprof.html#p1">PrinterBt</a><br>
+ <br>
+ Then see what the minimum black level down the neutral axis can be.
+ Note that we need to also set any ink limits we've decided on as
+ well (coloprof defaulting to 10% less than the value recorded in the
+ .ti3 file). In this example the test chart has a 300% total ink
+ limit, and we've decided to use 290%:<br>
+ <br>
+ <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a
+ href="xicclu.html#k">-kz</a> <a href="xicclu.html#l">-l290</a> <a
+ href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a
+ href="xicclu.html#p1">PrinterBt.icm</a><br>
+ <br>
+ Which might be a graph something like this:<br>
+ <br>
+ <img alt="Graph of CMYK neutral axis with minimum K"
+ src="Kgraph1.jpg" style="width: 250px; height: 250px;"><br>
+ <br>
+ Note how the minimum black is zero up to 93% of the
+ white->black L* curve, and then jumps up to 87%. This is because
+ we've reached the total ink limit, and K then has to be substituted
+ for CMY, to keep the total under the total ink limit.<br>
+ <br>
+ Then let's see what the maximum black level down the neutral axis
+ can be:<br>
+ <br>
+ <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a
+ href="xicclu.html#k">-kx</a> <a href="xicclu.html#l">-l290</a> <a
+ href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a
+ href="xicclu.html#p1">PrinterBt.icm</a><br>
+ <br>
+ Which might be a graph something like this:<br>
+ <br>
+ <img alt="Graph of CMYK neutral axis with maximum K"
+ src="Kgraph2.jpg" style="width: 250px; height: 250px;"><br>
+ <br>
+ Note how the CMY values are fairly low up to 93% of the
+ white->black L* curve (the low levels of CMY are helping set the
+ neutral color), and then they jump up. This is because we've reach
+ the point where black on it's own, isn't as dark as the color that
+ can be achieved using CMY and K. Because the K has a dominant effect
+ on the hue of the black, the levels of CMY are often fairly volatile
+ in this region.<br>
+ <br>
+ Any K curve we specify must lie between the black curves of the
+ above two graphs.<br>
+ <br>
+ Let's say we'd like to chose a moderate black curve, one that aims
+ for about equal levels of CMY and K. We should also aim for it to be
+ fairly smooth, since this will minimize visual artefacts caused by
+ the limited fidelity that profile LUT tables are able to represent
+ inside the profile.<br>
+ <br>
+ <img style="width: 340px; height: 258px;" alt="-k parameters"
+ src="Kparams.jpg"><br>
+ <br>
+ <br>
+ For minimum discontinuities we should aim for the curve to finish at
+ the point it has to reach to satisfy the total ink limit at 87%
+ curve and 93% black. For a first try we can simply set a straight
+ line to that point: <br>
+ <br>
+ <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a
+ href="xicclu.html#k">-kp 0 0 .93 .87 1.0</a> <a
+ href="xicclu.html#l">-l290</a> <a href="xicclu.html#f">-fif</a> <a
+ href="xicclu.html#i">-ir</a> <a href="xicclu.html#p1">PrinterBt.icm</a><br>
+ <br>
+ <img alt="Graph of CMYK neutral axis with kp 0 0 1.0 1.0 1.0 -l290"
+ src="Kgraph3.jpg" style="width: 250px; height: 250px;"><br>
+ <br>
+ The black "curve" hits the 93%/87% mark well, but is a bit too far
+ above CMY, so we'll try making the black curve concave:<br>
+ <br>
+ <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a
+ href="xicclu.html#k">-kp </a><a href="xicclu.html#k">0 0 .93 .87
+ 0.65</a> <a href="xicclu.html#l">-l290</a> <a
+ href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a
+ href="xicclu.html#p1">PrinterBt.icm</a><br>
+ <br>
+ <img alt="Graph of CMYK neutral axis with -kp 0 .05 1 .9 1 -l290"
+ src="Kgraph4.jpg" style="width: 250px; height: 249px;"><br>
+ <br>
+ This looks just about perfect, so the the curve parameters can now
+ be used to generate our real profile:<br>
+ <br>
+ <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a>
+ <a href="colprof.html#E">-D"Printer B"</a> <a href="colprof.html#q">-qm</a>
+ <a href="colprof.html#k">-kp </a><a href="xicclu.html#k">0 0 .93
+ .87 0.65</a> <a href="colprof.html#S">-S</a><a
+ href="colprof.html#S"> sRGB.icm</a> <a href="colprof.html#c">-cmt</a>
+ <a href="colprof.html#d">-dpp</a> <a href="colprof.html#p1">PrinterB</a><br>
+ <br>
+ and the resulting B2A table black curve can be checked using xicclu:<br>
+ <br>
+ <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a
+ href="xicclu.html#f">-fb</a> <a href="xicclu.html#i">-ir</a> <a
+ href="xicclu.html#p1">PrinterB.icm</a><br>
+ <br>
+ <img style="width: 250px; height: 250px;" alt="sadsadas"
+ src="Kgraph5.jpg"><br>
+ <br>
+ <br>
+ <hr style="margin-left: 0px; margin-right: auto; width: 20%; height:
+ 2px;"><br>
+ <span style="font-weight: bold;">Examples of other inkings:<br>
+ <br>
+ </span>A smoothed zero black inking:<br>
+ <br>
+ <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a
+ href="xicclu.html#k">-kp </a><a href="xicclu.html#k">0 .7 .93 .87
+ 1.0</a> <a href="xicclu.html#l">-l290</a> <a
+ href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a
+ href="xicclu.html#p1">PrinterBt.icm</a><br>
+ <br>
+ <img style="width: 250px; height: 250px;" alt="sadsadas"
+ src="Kgraph6.jpg"><br>
+ <br>
+ A low black inking:<br>
+ <br>
+ <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a
+ href="xicclu.html#k">-kp </a><a href="xicclu.html#k">0 0 .93 .87
+ 0.15</a> <a href="xicclu.html#l">-l290</a> <a
+ href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a
+ href="xicclu.html#p1">PrinterBt.icm</a><br>
+ <br>
+ <img style="width: 250px; height: 250px;" alt="sadsadas"
+ src="Kgraph7.jpg"><br>
+ <br>
+ <br>
+ A high black inking:<br>
+ <br>
+ <a href="xicclu.html">xicclu</a> <a href="xicclu.html#g">-g</a> <a
+ href="xicclu.html#k">-kp </a><a href="xicclu.html#k">0 0 .93 .87
+ 1.2</a> <a href="xicclu.html#l">-l290</a> <a
+ href="xicclu.html#f">-fif</a> <a href="xicclu.html#i">-ir</a> <a
+ href="xicclu.html#p1">PrinterBt.icm</a><br>
+ <br>
+ <img style="width: 250px; height: 250px;" alt="sadsadas"
+ src="Kgraph8.jpg"><br>
+ <br>
+ <span style="font-weight: bold;"></span>
+ <h4>Overriding the ink limit<br>
+ </h4>
+ Normally the total ink limit will be read from the <span
+ style="font-weight: bold;">PrinterB.ti3</span> file, and will be
+ set at a level 10% lower than the number used in creating the test
+ chart values using <a href="targen.html#l">targen -l</a>. If you
+ want to override this with a lower limit, then use the <a
+ href="colprof.html#l">-l flag</a>.<br>
+ <br>
+ <a href="colprof.html">colprof</a> <a href="colprof.html#v">-v</a>
+ <a href="colprof.html#E">-D"Printer B"</a> <a href="colprof.html#q">-qm</a>
+ <a href="colprof.html#S">-S</a><a href="colprof.html#S"> sRGB.icm</a>
+ <a href="colprof.html#c">-cmt</a> <a href="colprof.html#d">-dpp</a>
+ <a href="colprof.html#k">-kr</a> <a href="xicclu.html#l">-l290</a>
+ <a href="colprof.html#p1">PrinterB</a><br>
+ <br>
+ Make sure you check the delta E report at the end of the profile
+ creation, to see if the profile is behaving reasonably.<br>
+ <br>
+ One way of checking that your ink limit is not too high, is to use "<span
+ style="font-weight: bold;">xicc -fif -ia</span>" to check, by
+ setting different ink limits using the <span style="font-weight:
+ bold;">-l</span> option, feeding Lab = 0 0 0 into it, and checking
+ the resulting black point. Starting with the ink limit used
+ with <span style="font-weight: bold;">targen</span> for the test
+ chart, reduce it until the black point starts to be affected. If it
+ is immediately affected by any reduction in the ink limit, then the
+ black point may be improved by increasing the ink limit used to
+ generate the test chart and then re-print and re-measuring it,
+ assuming other aspects such as wetness, smudging, spreading or
+ drying time are not an issue.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <h3><a name="PC1"></a>Calibrating Printers<br>
+ </h3>
+ <span style="font-weight: bold;">Profiling</span> creates a
+ description of how a device behaves, while <span
+ style="font-weight: bold;">calibration</span> on the other hand is
+ intended to <span style="text-decoration: underline;">change</span>
+ how a device behaves. Argyll has the ability to create per-channel
+ device space calibration curves for print devices, that can then be
+ used to improve the behavior of of the device, making a subsequent
+ profile fit the device more easily and also allow day to day
+ correction of device drift without resorting to a full re-profile.<br>
+ <br>
+ <span style="font-weight: bold;">NOTE:</span> Because calibration
+ adds yet another layer to the way color is processed, it is
+ recommended that it not be attempted until the normal profiling
+ workflow is established, understood and verified.<br>
+ <h4><a name="PC2"></a>Calibrated print workflows</h4>
+ There are two main workflows that printer calibration curves can be
+ applied to:<br>
+ <br>
+ <span style="text-decoration: underline;">Workflow <span
+ style="font-weight: bold;">with</span> native calibration
+ capability</span>:<br>
+ <br>
+ Firstly the printer itself may have the capability of using per
+ channel calibration curves. In this situation, the calibration
+ process will be largely independent of profiling. Firstly the
+ printer is configured to have both its color management and
+ calibration disabled (the latter perhaps achieved by loading linear
+ calibration curves), and a print calibration test chart that
+ consists of per channel color wedges is printed. The calibration
+ chart is read and the resulting .ti3 file converted into calibration
+ curves by processing it using <span style="font-weight: bold;">printcal</span>.
+ The calibration is then installed into the printer. Subsequent
+ profiling will be performed on the <span style="text-decoration:
+ underline;">calibrated</span> printer (ie. the profile test chart
+ will have the calibration curves applied to it by the printer, and
+ the resulting ICC profile will represent the behavior of the
+ calibrated printer.)<br>
+ <br>
+ <span style="text-decoration: underline;">Workflow <span
+ style="font-weight: bold;">without</span> native calibration
+ capability</span>:<br>
+ <br>
+ The second workflow is one in which the printer has no calibration
+ capability itself. In this situation, the calibration process will
+ have to be applied using the ICC color management tools, so careful
+ coordination with profiling is needed. Firstly the printer is
+ configured to have its color management disabled, and a print
+ calibration test chart that consists of per channel color wedges is
+ printed. The calibration chart is converted into calibration curves
+ by reading it and then processing the resultant .ti3 using <span
+ style="font-weight: bold;">printcal</span>,. During the subsequent
+ <span style="text-decoration: underline;">profiling</span>, the
+ calibration curves will need to be applied to the profile test chart
+ in the process of using <span style="font-weight: bold;">printtarg</span>.
+ Once the the profile has been created, then in subsequent printing
+ the calibration curves will need to be applied to an image being
+ printed either explicitly when using <span style="font-weight:
+ bold;">cctiff</span> to apply color profiles <span
+ style="text-decoration: underline;">and</span> calibration, <span
+ style="font-weight: bold;">OR</span> by creating a version of the
+ profile that has had the calibration curves incorporated into it
+ using the <span style="font-weight: bold;">applycal</span> tool.
+ The latter is useful when some CMM (color management module) other
+ than <span style="font-weight: bold;">cctiff </span>is being used.<br>
+ <br>
+ Once calibration aim targets for a particular device and mode
+ (screening, paper etc.) have been established, then the printer can
+ be re-calibrated at any time to bring its per channel behavior back
+ into line if it drifts, and the new calibration curves can be
+ installed into the printer, or re-incorporated into the profile.
+
+ <h4><a name="PC3"></a>Creating a print calibration test chart</h4>
+ The first step is to create a print calibration test chart. Since
+ calibration only creates per-channel curves, only single channel
+ step wedges are required for the chart. The main choice is the
+ number of steps in each wedge. For simple fast calibrations perhaps
+ as few as 20 steps per channel may be enough, but for a better
+ quality of calibration something like 50 or more steps would be a
+ better choice.<br>
+ <br>
+ Let's consider two devices in our examples, "PrinterA" which is an
+ "RGB" printer device, and "PrinterB" which is CMYK. In fact there is
+ no such thing as a real RGB printer, since printers use white media
+ and the colorant must subtract from the light reflected on it to
+ create color, but the printer itself turns the incoming RGB into the
+ native print colorspace, so for this reason we are careful to tell
+ targen to use the "Print RGB" colorspace, so that it knows to create
+ step wedges from media white to full colorant values.<br>
+ <br>
+ For instance, to create a 50 steps per channel calibration test
+ chart for our RGB and CMYK devices, the following would be
+ sufficient:<br>
+ <br>
+ <a href="targen.html">targen</a> <a href="targen.html#v">-v</a>
+ <a href="targen.html#d">-d2</a> <a href="targen.html#s">-s50</a>
+ <a href="targen.html#e">-e3</a> <a href="targen.html#f">-f0</a> <a
+ href="targen.html#p1">PrinterA_c</a><br>
+ <br>
+ <a href="targen.html">targen</a> <a href="targen.html#v">-v</a>
+ <a href="targen.html#d">-d4</a> <a href="targen.html#s">-s50</a>
+ <a href="targen.html#e">-e4</a> <a href="targen.html#f">-f0</a> <a
+ href="targen.html#p1">PrinterB_c</a><br>
+ <a href="targen.html#p1"></a><br>
+ For an outline of how to then print and read the resulting test
+ chart, see <a href="Scenarios.html#PP2b">Printing a print
+ profile test chart</a>, and <a href="Scenarios.html#PP3">Reading
+ a print test chart using an instrument</a>. Note that the printer
+ must be in an un-profiled and un-calibrated mode when doing this
+ print. Having done this, there will be a PrinterA.ti3 or
+ PrinterB.ti3 file containing the step wedge calibration chart
+ readings.<br>
+ <br>
+ <span style="font-weight: bold;">NOTE</span> that if you are
+ calibrating a raw printer driver, and there is considerable dot
+ gain, then you may want to use the <a href="targen.html#p">-p</a>
+ parameter to adjust the test chart point distribution to spread them
+ more evenly in perceptual space, giving more accurate control over
+ the calibration. Typically this will be a value greater than one for
+ a device that has dot gain, e.g. values of 1.5, 2.0 or 2.5 might be
+ good places to start. You can do a preliminary calibration and use
+ the verbose output of printcal to recommend a suitable value for <span
+ style="font-weight: bold;">-p</span>.<br>
+ <h4><a name="PC4"></a>Creating a printer calibration<br>
+ </h4>
+ The <a href="printcal.html">printcal</a> tool turns a calibration
+ chart <a href="File_Formats.html#.ti3">.ti3</a> file into a <a
+ href="File_Formats.html#.cal">.cal</a> file. It has three main
+ operating modes:- Initial calibration, Re-Calibration, and
+ Verification. (A fourth mode, "Imitation" is very like Initial
+ Calibration, but is used for establishing a calibration target that
+ a similar printer can attempt to imitate.)<br>
+ <br>
+ The distinction between Initial Calibration and Re-Calibration is
+ that in the initial calibration we establish the "aim points" or
+ response we want out of the printer after calibration. There are
+ three basic parameters to set this for each channel: Maximum level,
+ minimum level, and curve shape.<br>
+ <br>
+ By default the maximum level will be set using a heuristic which
+ attempts to pick the point when there is diminishing returns for
+ applying more colorant. This can be overridden using the <span
+ style="font-weight: bold;">-x# percent</span> option, where <span
+ style="font-weight: bold;">#</span> represents the choice of
+ channel this will be applied to. The parameter is the percentage of
+ device maximum. <br>
+ <br>
+ The minimum level defaults to 0, but can be overridden using the <span
+ style="font-weight: bold;">-n# deltaE</span> option. A minimum of
+ 0 means that zero colorant will correspond to the natural media
+ color, but it may be desirable to set a non-pure media color using
+ calibration for the purposes of emulating some other media. The
+ parameter is in Delta E units.<br>
+ <br>
+ The curve shape defaults to being perceptually uniform, which means
+ that even steps of calibrated device value result in perceptually
+ even color steps. In some situations it may be desirable to alter
+ this curve (for instance when non color managed output needs to be
+ sent to the calibrated printer), and a simple curve shape target can
+ be set using the <span style="font-weight: bold;">-t# percent</span>
+ parameter. This affects the output value at 50% input value, and
+ represents the percentage of perceptual output. By default it is 50%
+ perceptual output for 50% device input.<br>
+ <br>
+ Once a device has been calibrated, it can be re-calibrated to the
+ same aim target.<br>
+ <br>
+ Verification uses a calibration test chart printed through the
+ calibration, and compares the achieved response to the aim target.<br>
+ <br>
+ The simplest possible way of creating the <span style="font-weight:
+ bold;">PrinterA.cal</span> file is:<br>
+ <br>
+ <a href="printcal.html">printcal</a> <a
+ href="printcal.html#i">-i</a> <a href="colprof.html#p2">PrinterA_c</a><br>
+ <br>
+ For more detailed information, you can add the <span
+ style="font-weight: bold;">-v</span> and <span
+ style="font-weight: bold;">-p</span> flags:<br>
+ <br>
+ <a href="printcal.html">printcal</a> <a
+ href="printcal.html#v">-v</a> <a href="printcal.html#p">-p</a> <a
+ href="printcal.html#i">-i</a> <a href="colprof.html#p2">PrinterB_c</a><br>
+ <br>
+ (You will need to select the plot window and hit a key to advance
+ past each plot).<br>
+ <br>
+ For re-calibration, the name of the previous calibration file will
+ need to be supplied, and a new calibration<br>
+ file will be created:<br>
+ <br>
+ <a href="printcal.html">printcal</a> <a
+ href="printcal.html#v">-v</a> <a href="printcal.html#p">-p</a> <a
+ href="printcal.html#r">-r</a> <a href="colprof.html#p1">PrinterB_c_old</a>
+ <a href="colprof.html#p2">PrinterB_c_new</a><br>
+ <br>
+ Various aim points are normally set automatically by <span
+ style="font-weight: bold;">printcal</span>, but these can be
+ overridden using the <a href="colprof.html#x">-x</a>, <a
+ href="colprof.html#n">-n</a> and <a href="colprof.html#t">-t</a>
+ options. e.g. say we wanted to set the maximum ink for Cyan to 80%
+ and Black to 95%, we might use:<br>
+ <br>
+ <a href="printcal.html">printcal</a> <a
+ href="printcal.html#v">-v</a> <a href="printcal.html#p">-p</a> <a
+ href="printcal.html#i">-i</a> <a href="colprof.html#x">-xc 80</a>
+ <a href="colprof.html#x">-xk 95</a> <a href="colprof.html#p2">PrinterB_c</a><br>
+ <br>
+ <a href="colprof.html#p2"></a>
+ <h4><a name="PC5"></a>Using a printer calibration</h4>
+ The resulting calibration curves can be used with the following
+ other Argyll tools:<br>
+ <br>
<a href="printtarg.html#K">printtarg</a> To apply @@ -1871,7 +2480,44 @@ chart, - and/or to have it included in .ti3 file.<br> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ and/or to have it included in .ti3 file.<br>
<a href="cctiff.html#p2">cctiff</a> To apply @@ -1889,7 +2535,44 @@ an - image file.<br> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ image file.<br>
<a href="applycal.html#p1">applycal</a> @@ -1899,7 +2582,44 @@ an - To incorporate calibration into an ICC profile.<br> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ To incorporate calibration into an ICC profile.<br>
<a href="chartread.html#I">chartread</a> To override @@ -1917,261 +2637,1046 @@ a - profile chart.<br> - <br> - <br> - In a workflow <span style="font-weight: bold;">with</span> native - calibration capability, the calibration curves would be used with - printarg during subsequent <span style="font-weight: bold;">profiling</span> - so that any ink limit calculations will reflect final device values, - while not otherwise using the calibration within the ICC workflow:<br> - <br> - <a href="printtarg.html">printtarg</a> <a - href="printtarg.html#v">-v</a> <a href="printtarg.html#i">-ii1</a> - <a href="printtarg.html#p">-pA4</a> <a href="printtarg.html#I">-I - PrinterA_c.cal</a> <a href="printtarg.html#p1">PrinterA</a><br> - <br> - This will cause the .ti2 and resulting .ti3 and ICC profiles to - contain the calibration curves, allowing all the tools to be able to - compute final device value ink limits. The calibration curves must - also of course be installed into the printer. The means to do this - is currently outside the scope of Argyll (ie. either the print - system needs to be able to understand Argyll CAL format files, or - some tool will be needed to convert Argyll CAL files into the - printer calibration format).<br> - <br> - <br> - In a workflow <span style="font-weight: bold;">without</span> - native calibration capability, the calibration curves would be used - with printarg to <span style="text-decoration: underline;">apply</span> - the calibration to the test patch samples during subsequent <span - style="font-weight: bold;">profiling</span>, as well as embedding - it in the resulting .ti3 to allow all the tools to be able to - compute final device value ink limits:<br> - <br> - <a href="printtarg.html">printtarg</a> <a - href="printtarg.html#v">-v</a> <a href="printtarg.html#i">-ii1</a> - <a href="printtarg.html#p">-pA4</a> <a href="printtarg.html#K">-K - PrinterA_c.cal</a> <a href="printtarg.html#p1">PrinterA</a><br> - <a href="cctiff.html#p4"></a><br> - To apply calibration to an ICC profile, so that a calibration - unaware CMM can be used:<br> - <br> - <a href="applycal.html">applycal</a> <a - href="applycal.html#p1">PrinterA.cal</a> <a - href="applycal.html#p2">PrinterA.icm</a> <a - href="applycal.html#p3">PrinterA_cal.icm</a><br> - <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> - 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> - <br> - Another useful tool is <a href="synthcal.html">synthcal</a>, that - allows creating linear or synthetic calibration files for disabling - calibration or testing.<br> - Similarly, <a href="fakeread.html">fakeread</a> also supports - applying calibration curves and embedding them in the resulting .ti3 - file<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 - linearized device, and the profiling is generally unaware of the - underlying non-linearized device values, an exception is made in the - calculation of ink limits during profiling. This is made possible by - including the calibration curves in the profile charts .ti2 and - subsequent .ti3 file and resulting ICC profile <span - style="font-weight: bold;">'targ'</span> text tag, by way of the <span - style="font-weight: bold;">printtarg</span> <span - style="font-weight: bold;">-I</span> or <span style="font-weight: - bold;">-K</span> options. This is done on the assumption that the - physical quantity of ink is what's important in setting the ink - limit, and that the underlying non-linearized device values - represent such a physical quantity.<br> - <br> - <br> - <hr size="2" width="100%"> - <h3><a name="LP1"></a>Linking Profiles</h3> - Two device profiles can be linked together to create a device link - profile, than encapsulates a particular device to device transform. - Often this step is not necessary, as many systems and tools will - link two device profiles "on the fly", but creating a device link - profile gives you the option of using "smart CMM" techniques, such - as true gamut mapping, improved inverse transform accuracy, tailored - black generation and ink limiting.<br> - <br> - The overall process is to link the input space and output space - profiles using <a href="collink.html">collink</a>, creating a - device to device link profile. The device to device link profile can - then be used by cctiff (or other ICC device profile capable tools), - to color correct a raster files.<br> - <br> - Three examples will be given here, showing the three different modes - than <span style="font-weight: bold;">collink</span> supports.<br> - <br> - In <a href="collink.html#s">simple mode</a>, the two profiles are - linked together in a similar fashion to other <span - style="font-weight: bold;">CMMs</span> simply using the forward - and backwards color transforms defined by the profiles. Any gamut - mapping is determined by the content of the tables within the two - profiles, together with the particular intent chosen. Typically the - same intent will be used for both the source and destination - profile:<br> - <br> - <a href="collink.html">collink</a> <a href="collink.html#v">-v</a> - <a href="collink.html#q">-qm</a> <a href="collink.html#s">-s</a> <a - href="collink.html#si">-ip</a> <a href="collink.html#so">-op</a> - <a href="collink.html#p1">SouceProfile.icm</a> <a - href="collink.html#p2">DestinationProfile.icm</a> <a - href="collink.html#p3">Source2Destination.icm</a><br> - <br> - <br> - In <a href="collink.html#g">gamut mapping mode</a>, the - pre-computed intent mappings inside the profiles are not used, but - instead the gamut mapping between source and destination is tailored - to the specific gamuts of the two profiles, and the intent parameter - supplied to <span style="font-weight: bold;">collink</span>. - Additionally, source and destination viewing conditions should be - provided, to allow the color appearance space conversion to work as - intended. The colorimetric B2A table in the destination profile is - used, and this will determine any black generation and ink limiting:<br> - <br> - <a href="collink.html">collink</a> <a href="collink.html#v">-v</a> - <a href="collink.html#q">-qm</a> <a href="collink.html#g">-g</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">MonitorSouceProfile.icm</a> - <a href="collink.html#p2">DestinationProfile.icm</a> <a - href="collink.html#p3">Source2Destination.icm</a><br> - <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, - but instead the gamut mapping between source and destination is - tailored to the specific gamuts of the two profiles, and the intent - parameter supplied to <span style="font-weight: bold;">collink</span>. - In addition, the B2A table is <span style="font-weight: bold;">not</span> - used in the destination profile, but the A2B table is instead - inverted, leading to improved transform accuracy, and in CMYK - devices, allowing the ink limiting and black generation parameters - to be set:<br> - <br> - For a CLUT table based RGB printer destination profile, the - following would be appropriate:<br> - <br> - <a href="collink.html">collink</a> <a href="collink.html#v">-v</a> - <a href="collink.html#q">-qm</a> <a href="collink.html#G">-G</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">MonitorSouceProfile.icm</a> - <a href="collink.html#p2">RGBDestinationProfile.icm</a> <a - href="collink.html#p3">Source2Destination.icm</a><br> - <br> - For a CMYK profile, the total ink limit needs to be specified (a - typical value being 10% less than the value used in creating the - device test chart), and the type of black generation also needs to - be specified:<br> - <br> - <a href="collink.html">collink</a> <a href="collink.html#v">-v</a> - <a href="collink.html#q">-qm</a> <a href="collink.html#G">-G</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#l">-l250</a> - <a href="collink.html#k">-kr</a> <a href="collink.html#p1">MonitorSouceProfile.icm</a> - <a href="collink.html#p2">CMYKDestinationProfile.icm</a> <a - href="collink.html#p3">Source2Destination.icm</a><br> - <br> - Note that you should set the source (<a href="collink.html#c">-c</a>) - and destination (<a href="collink.html#d">-d</a>) viewing conditions - for the type of device the profile represents, and the conditions - under which it will be viewed.<br> - <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 - be trying to evaluate print output using a display. Often it is - sufficient to use an absolute or relative colorimetric transform - from the print device space to the display space, but while these - provide a colorimetric preview of the result, they do not take into - account the subjective appearance differences due to the different - device conditions. It can therefore be useful to create a soft proof - appearance transform using collink:<br> - <br> - <a href="collink.html">collink</a> <a href="collink.html#v">-v</a> - <a href="collink.html#q">-qm</a> <a href="collink.html#G">-G</a> <a - href="collink.html#si">-ila</a> <a href="collink.html#c">-cpp</a> - <a href="collink.html#d">-dmt</a> <a href="collink.html#l">-t250</a> <a - href="collink.html#k"></a><a href="collink.html#p1">CMYKDestinationProfile.icm</a> - <a href="collink.html#p2">MonitorProfile.icm</a> <a - href="collink.html#p3">SoftProof.icm</a><br> - <br> - We use the Luminance matched appearance intent, to preserve the - subjective apperance of the target device, which takes into account - the viewing conditions and assumes adaptation to the differences in - the luminence range, but otherwise not attempting to compress or - change the gamut.<br> - - <hr size="2" width="100%"><br> - <h3><a name="TR1"></a>Transforming colorspaces of raster files</h3> - Although a device profile or device link profile may be useful with - other programs and systems, Argyll provides the tool <a - href="cctiff.html">cctiff</a> for directly applying a device to - device transform to a <a href="File_Formats.html#TIFF">TIFF</a> or - <a href="File_Formats.html#JPEG">JPEG</a> raster file. The cctiff - tool is capable of linking an arbitrary sequence of device profiles, - device links, abstract profiles and calibration curves. Each device - profile can be preceded by the <span style="font-weight: bold;">-i</span> - option to indicate the intent that should be used. Both 8 and 16 bit - per component files can be handled, and up to 8 color channels. The - color transform is optimized to perform the overall transformation - rapidly.<br> - <br> - If a device link is to be used, the following is a typical example:<br> - <br> - <a href="cctiff.html">cctiff</a> <a href="cctiff.html#p1">Source2Destination.icm</a> - <a href="cctiff.html#p3">infile.tif</a> <a href="cctiff.html#p4">outfile.tif</a><br> - or<br> - <a href="cctiff.html">cctiff</a> <a href="cctiff.html#p1">Source2Destination.icm</a> - <a href="cctiff.html#p3">infile.jpg</a> <a href="cctiff.html#p4">outfile.jpg</a><br> - <br> - <i><br> - </i>If a source and destination profile are to be used, the - following would be a typical example:<br> - <br> - <a href="cctiff.html"> cctiff</a> <a href="cctiff.html#i">-ip</a> - <a href="cctiff.html#p1i">SourceProfile.icm</a> <a - href="cctiff.html#i">-ip</a> <a href="cctiff.html#p1o">DestinationProfile.icm</a> - <a href="cctiff.html#p3">infile.tif</a> <a href="cctiff.html#p4">outfile.tif</a><br> - or<br> - <a href="cctiff.html"> cctiff</a> <a href="cctiff.html#i">-ip</a> - <a href="cctiff.html#p1i">SourceProfile.icm</a> <a - href="cctiff.html#i">-ip</a> <a href="cctiff.html#p1o">DestinationProfile.icm</a> - <a href="cctiff.html#p3">infile.jpg</a> <a href="cctiff.html#p4">outfile.jpg</a><br> - <br> - <br> - <hr size="2" width="100%"><br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - <br> - </body> -</html> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ profile chart.<br>
+ <br>
+ <br>
+ In a workflow <span style="font-weight: bold;">with</span> native
+ calibration capability, the calibration curves would be used with
+ printarg during subsequent <span style="font-weight: bold;">profiling</span>
+ so that any ink limit calculations will reflect final device values,
+ while not otherwise using the calibration within the ICC workflow:<br>
+ <br>
+ <a href="printtarg.html">printtarg</a> <a
+ href="printtarg.html#v">-v</a> <a href="printtarg.html#i">-ii1</a>
+ <a href="printtarg.html#p">-pA4</a> <a href="printtarg.html#I">-I
+ PrinterA_c.cal</a> <a href="printtarg.html#p1">PrinterA</a><br>
+ <br>
+ This will cause the .ti2 and resulting .ti3 and ICC profiles to
+ contain the calibration curves, allowing all the tools to be able to
+ compute final device value ink limits. The calibration curves must
+ also of course be installed into the printer. The means to do this
+ is currently outside the scope of Argyll (ie. either the print
+ system needs to be able to understand Argyll CAL format files, or
+ some tool will be needed to convert Argyll CAL files into the
+ printer calibration format).<br>
+ <br>
+ <br>
+ In a workflow <span style="font-weight: bold;">without</span>
+ native calibration capability, the calibration curves would be used
+ with printarg to <span style="text-decoration: underline;">apply</span>
+ the calibration to the test patch samples during subsequent <span
+ style="font-weight: bold;">profiling</span>, as well as embedding
+ it in the resulting .ti3 to allow all the tools to be able to
+ compute final device value ink limits:<br>
+ <br>
+ <a href="printtarg.html">printtarg</a> <a
+ href="printtarg.html#v">-v</a> <a href="printtarg.html#i">-ii1</a>
+ <a href="printtarg.html#p">-pA4</a> <a href="printtarg.html#K">-K
+ PrinterA_c.cal</a> <a href="printtarg.html#p1">PrinterA</a><br>
+ <a href="cctiff.html#p4"></a><br>
+ To apply calibration to an ICC profile, so that a calibration
+ unaware CMM can be used:<br>
+ <br>
+ <a href="applycal.html">applycal</a> <a
+ href="applycal.html#p1">PrinterA.cal</a> <a
+ href="applycal.html#p2">PrinterA.icm</a> <a
+ href="applycal.html#p3">PrinterA_cal.icm</a><br>
+ <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>
+ 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>
+ <br>
+ Another useful tool is <a href="synthcal.html">synthcal</a>, that
+ allows creating linear or synthetic calibration files for disabling
+ calibration or testing.<br>
+ Similarly, <a href="fakeread.html">fakeread</a> also supports
+ applying calibration curves and embedding them in the resulting .ti3
+ file<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
+ linearized device, and the profiling is generally unaware of the
+ underlying non-linearized device values, an exception is made in the
+ calculation of ink limits during profiling. This is made possible by
+ including the calibration curves in the profile charts .ti2 and
+ subsequent .ti3 file and resulting ICC profile <span
+ style="font-weight: bold;">'targ'</span> text tag, by way of the <span
+ style="font-weight: bold;">printtarg</span> <span
+ style="font-weight: bold;">-I</span> or <span style="font-weight:
+ bold;">-K</span> options. This is done on the assumption that the
+ physical quantity of ink is what's important in setting the ink
+ limit, and that the underlying non-linearized device values
+ represent such a physical quantity.<br>
+ <br>
+ <br>
+ <hr size="2" width="100%">
+ <h3><a name="LP1"></a>Linking Profiles</h3>
+ Two device profiles can be linked together to create a device link
+ profile, than encapsulates a particular device to device transform.
+ Often this step is not necessary, as many systems and tools will
+ link two device profiles "on the fly", but creating a device link
+ profile gives you the option of using "smart CMM" techniques, such
+ as true gamut mapping, improved inverse transform accuracy, tailored
+ black generation and ink limiting.<br>
+ <br>
+ The overall process is to link the input space and output space
+ profiles using <a href="collink.html">collink</a>, creating a
+ device to device link profile. The device to device link profile can
+ then be used by cctiff (or other ICC device profile capable tools),
+ to color correct a raster files.<br>
+ <br>
+ Three examples will be given here, showing the three different modes
+ than <span style="font-weight: bold;">collink</span> supports.<br>
+ <br>
+ In <a href="collink.html#s">simple mode</a>, the two profiles are
+ linked together in a similar fashion to other <span
+ style="font-weight: bold;">CMMs</span> simply using the forward
+ and backwards color transforms defined by the profiles. Any gamut
+ mapping is determined by the content of the tables within the two
+ profiles, together with the particular intent chosen. Typically the
+ same intent will be used for both the source and destination
+ profile:<br>
+ <br>
+ <a href="collink.html">collink</a> <a href="collink.html#v">-v</a>
+ <a href="collink.html#q">-qm</a> <a href="collink.html#s">-s</a> <a
+ href="collink.html#si">-ip</a> <a href="collink.html#so">-op</a>
+ <a href="collink.html#p1">SouceProfile.icm</a> <a
+ href="collink.html#p2">DestinationProfile.icm</a> <a
+ href="collink.html#p3">Source2Destination.icm</a><br>
+ <br>
+ <br>
+ In <a href="collink.html#g">gamut mapping mode</a>, the
+ pre-computed intent mappings inside the profiles are not used, but
+ instead the gamut mapping between source and destination is tailored
+ to the specific gamuts of the two profiles, and the intent parameter
+ supplied to <span style="font-weight: bold;">collink</span>.
+ Additionally, source and destination viewing conditions should be
+ provided, to allow the color appearance space conversion to work as
+ intended. The colorimetric B2A table in the destination profile is
+ used, and this will determine any black generation and ink limiting:<br>
+ <br>
+ <a href="collink.html">collink</a> <a href="collink.html#v">-v</a>
+ <a href="collink.html#q">-qm</a> <a href="collink.html#g">-g</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">MonitorSouceProfile.icm</a>
+ <a href="collink.html#p2">DestinationProfile.icm</a> <a
+ href="collink.html#p3">Source2Destination.icm</a><br>
+ <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,
+ but instead the gamut mapping between source and destination is
+ tailored to the specific gamuts of the two profiles, and the intent
+ parameter supplied to <span style="font-weight: bold;">collink</span>.
+ In addition, the B2A table is <span style="font-weight: bold;">not</span>
+ used in the destination profile, but the A2B table is instead
+ inverted, leading to improved transform accuracy, and in CMYK
+ devices, allowing the ink limiting and black generation parameters
+ to be set:<br>
+ <br>
+ For a CLUT table based RGB printer destination profile, the
+ following would be appropriate:<br>
+ <br>
+ <a href="collink.html">collink</a> <a href="collink.html#v">-v</a>
+ <a href="collink.html#q">-qm</a> <a href="collink.html#G">-G</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">MonitorSouceProfile.icm</a>
+ <a href="collink.html#p2">RGBDestinationProfile.icm</a> <a
+ href="collink.html#p3">Source2Destination.icm</a><br>
+ <br>
+ For a CMYK profile, the total ink limit needs to be specified (a
+ typical value being 10% less than the value used in creating the
+ device test chart), and the type of black generation also needs to
+ be specified:<br>
+ <br>
+ <a href="collink.html">collink</a> <a href="collink.html#v">-v</a>
+ <a href="collink.html#q">-qm</a> <a href="collink.html#G">-G</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#l">-l250</a>
+ <a href="collink.html#k">-kr</a> <a href="collink.html#p1">MonitorSouceProfile.icm</a>
+ <a href="collink.html#p2">CMYKDestinationProfile.icm</a> <a
+ href="collink.html#p3">Source2Destination.icm</a><br>
+ <br>
+ Note that you should set the source (<a href="collink.html#c">-c</a>)
+ and destination (<a href="collink.html#d">-d</a>) viewing conditions
+ for the type of device the profile represents, and the conditions
+ under which it will be viewed.<br>
+ <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
+ be trying to evaluate print output using a display. Often it is
+ sufficient to use an absolute or relative colorimetric transform
+ from the print device space to the display space, but while these
+ provide a colorimetric preview of the result, they do not take into
+ account the subjective appearance differences due to the different
+ device conditions. It can therefore be useful to create a soft proof
+ appearance transform using collink:<br>
+ <br>
+ <a href="collink.html">collink</a> <a href="collink.html#v">-v</a>
+ <a href="collink.html#q">-qm</a> <a href="collink.html#G">-G</a> <a
+ href="collink.html#si">-ila</a> <a href="collink.html#c">-cpp</a>
+ <a href="collink.html#d">-dmt</a> <a href="collink.html#l">-t250</a> <a
+ href="collink.html#k"></a><a href="collink.html#p1">CMYKDestinationProfile.icm</a>
+ <a href="collink.html#p2">MonitorProfile.icm</a> <a
+ href="collink.html#p3">SoftProof.icm</a><br>
+ <br>
+ We use the Luminance matched appearance intent, to preserve the
+ subjective apperance of the target device, which takes into account
+ the viewing conditions and assumes adaptation to the differences in
+ the luminence range, but otherwise not attempting to compress or
+ change the gamut.<br>
+
+ <hr size="2" width="100%"><br>
+ <h3><a name="TR1"></a>Transforming colorspaces of raster files</h3>
+ Although a device profile or device link profile may be useful with
+ other programs and systems, Argyll provides the tool <a
+ href="cctiff.html">cctiff</a> for directly applying a device to
+ device transform to a <a href="File_Formats.html#TIFF">TIFF</a> or
+ <a href="File_Formats.html#JPEG">JPEG</a> raster file. The cctiff
+ tool is capable of linking an arbitrary sequence of device profiles,
+ device links, abstract profiles and calibration curves. Each device
+ profile can be preceded by the <span style="font-weight: bold;">-i</span>
+ option to indicate the intent that should be used. Both 8 and 16 bit
+ per component files can be handled, and up to 8 color channels. The
+ color transform is optimized to perform the overall transformation
+ rapidly.<br>
+ <br>
+ If a device link is to be used, the following is a typical example:<br>
+ <br>
+ <a href="cctiff.html">cctiff</a> <a href="cctiff.html#p1">Source2Destination.icm</a>
+ <a href="cctiff.html#p3">infile.tif</a> <a href="cctiff.html#p4">outfile.tif</a><br>
+ or<br>
+ <a href="cctiff.html">cctiff</a> <a href="cctiff.html#p1">Source2Destination.icm</a>
+ <a href="cctiff.html#p3">infile.jpg</a> <a href="cctiff.html#p4">outfile.jpg</a><br>
+ <br>
+ <i><br>
+ </i>If a source and destination profile are to be used, the
+ following would be a typical example:<br>
+ <br>
+ <a href="cctiff.html"> cctiff</a> <a href="cctiff.html#i">-ip</a>
+ <a href="cctiff.html#p1i">SourceProfile.icm</a> <a
+ href="cctiff.html#i">-ip</a> <a href="cctiff.html#p1o">DestinationProfile.icm</a>
+ <a href="cctiff.html#p3">infile.tif</a> <a href="cctiff.html#p4">outfile.tif</a><br>
+ or<br>
+ <a href="cctiff.html"> cctiff</a> <a href="cctiff.html#i">-ip</a>
+ <a href="cctiff.html#p1i">SourceProfile.icm</a> <a
+ href="cctiff.html#i">-ip</a> <a href="cctiff.html#p1o">DestinationProfile.icm</a>
+ <a href="cctiff.html#p3">infile.jpg</a> <a href="cctiff.html#p4">outfile.jpg</a><br>
+ <br>
+ <br>
+ <hr size="2" width="100%"><br>
+ <h3><a name="TV1"></a>Creating Video Calibration 3DLuts</h3>
+ Video calibration typically involves trying to make your actual
+ display device emulate an ideal video display, one which matches
+ what your Video media was intended to be displayed on. An ICC device
+ link embodies the machinery to do exactly this, to take device
+ values in the target source colorspace and transform them into an
+ actual output device colorspace. In the Video and Film industries a
+ very similar, but less sophisticated means of doing this is to use
+ 3DLuts, which come in a multitude of different format. ICC device
+ links have the advantage of being a superset of 3dLuts, encapsulated
+ in a standard file format.<br>
+ <br>
+ To facilitate Video calibration of certain Video systems, ArgyllCMS
+ supports some 3DLut output options as part of <a
+ href="collink.html">collink</a>.<br>
+ <br>
+ What follows here is an outline of how to create Video calibration
+ 3DLuts using ArgyllCMS. First comes a general discussion of various
+ aspects of video device links/3dLuts, and followed with some
+ specific advice regarding the systems that ArgyllCMS supports. Last
+ is some recommended scenarios for verifying the quality of Video
+ calibration achieved.<br>
+ <h5>1) How to display test patches.<br>
+ </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>
+ <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
+ behavior of the output device, but making such a Link just from two
+ ICC profile requires the use of Absolute Colorimetric intent during
+ linking, and this reduces flexibility. In addition, a typical ICC
+ device profile may not capture the neutral axis behavior quite as
+ well as an explicit calibration, since it doesn't sample the
+ displays neutral axis behaviour in quite as much detail. It is often
+ desirable therefore, to calibrate the display device so as to have
+ the specific white point desired so that one of the white point
+ relative linking intents can be used, and to improve the displays
+ general neutral axis behavior so that subsequent profiling works to
+ best advantage. In summary, there are basically 4 options in
+ handling white point & neutral axis calibration:<br>
+ <ul>
+ <li>Don't bother correcting the white point. Most displays are
+ close to the typical D65 target, and our eyes adapt to the white
+ automatically unless it is very far from the daylight locus or
+ we have something else to refer to. If this approach is taken,
+ then display profiling and linking can ignore calibration, and
+ one of the non Absolute Colorimetric intents (such as Relative
+ Colorimetric) is chosen during profile linking. It is wise to
+ make sure that the video card VideoLUTs are set to some known
+ state (ie. linear using "dispwin -c" , or set by a an installed
+ ICC display profile) though.<br>
+ </li>
+ <li>Calibrate the white point and linearise the neutral axis using
+ the display controls. Many TV's have internal calibration
+ controls that allow setting the white point, and possibly the
+ neutral axis response. Either a dedicated Video calibration
+ 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
+ help, the Device Link will override the transfer curve
+ characteristic of the calibrated display, so aiming for a
+ transfer curve approximately the same as the target and
+ reasonably perceptually linear is all that is required. If this
+ approach is taken, then display profiling and linking can ignore
+ calibration, and one of the non Absolute Colorimetric intents is
+ chosen during profile linking. It is wise to make sure that the
+ video card VideoLUTs are set to some known state though.</li>
+ <li>[<b>Recommended</b>] Calibrate the white point and neutral
+ axis using ArgyllCMS <a href="dispcal.html">dispcal</a>. Since
+ the Device Link will override the calibrated transfer curve
+ characteristic of the display, there there may be no point in
+ doing much more than a medium calibration, and choosing a
+ standard that has a straight segment from black, such as L*a*b*,
+ sRGB, Rec709 or SMPTE240 curve. The exact shape of the
+ calibration curve is not critically important, as the profiling
+ 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
+ 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
+ quite as accurate as an explicit calibration.</li>
+ </ul>
+ If an explicit calibration is used, then it is a good idea to add
+ some test points down the neutral axis when profiling (targen <a
+ href="targen.html#g">-g parameter</a>). <br>
+ <br>
+ <b>3) Choice of where to apply display per channel calibration
+ curves</b><br>
+ <br>
+ If calibration curves are going to be used, then it needs to be
+ decided where they will be applied in the video processing chain.
+ There are two options:<br>
+ <br>
+ <b>a)</b> Install the calibration curves in the playback system. On
+ a PC the display, this can be done by loading the calibration curves
+ into the Video Card temporarily using "dispwin calibration.cal", or
+ installing the ICC profile into the system persistently using
+ something like "<a href="dispwin.html#I">dispwin -I profile.icm</a>",<br>
+ or when using MadVR 0.86.9 or latter by creating a 3dLut with
+ appended calibration curves using <a href="collink#H">-H
+ display.cal</a>.<br>
+ <br>
+ <b>b)</b> The calibration can be incorporated into the Device
+ Link/3dLUT by providing it to collink as the <a
+ href="collink.html#a">-a display.cal</a>. This is the only option
+ if the video display path does not have some separate facility to
+ handle calibration curves. Note that if the playback system has
+ graphic card VideoLUTs then they will have to be set to a defined
+ consistent state such as linear. When using MadVR 0.86.9 or latter
+ this will be done automatically since the -a option will append a
+ linear set of calibration curves to the 3dLut.<br>
+ <br>
+ The choice is dictated by a number of considerations:<br>
+ <ul>
+ <li>Does the video playback path have a facility for installing
+ the calibration curves ? If playing back system is a PC, then
+ typically the Graphics Card supports 1D VideoLUTs, thereby
+ making a) a possible choice.<br>
+ </li>
+ <li>Does the video playback <u>always</u> play back through the
+ Video Card VideoLUTs ? Some systems do not apply VIdeoLUTs to
+ things like overlay plane rendering. If not, then you need to
+ choose b), but also make sure that if it does use the Video Card
+ VideoLUTs in some situations, that they are set to linear (ie.
+ dispcal -c). One way of determining when the VideoLUTs get used
+ or not is to load a distinct calibration such as "strange.cal"
+ provided in the <b>ref</b> folder, and check visually if it is
+ affecting the video or not, ie. "dispcal strange.cal". Note that
+ using MadVR 0.86.9 or latter in combination with a 3dLut with
+ appended calibration curves will apply the calibration even with
+ overlay plane rendering.<br>
+ </li>
+ <li>Do you want/need other applications to share the calibration
+ curves or profile or not ? If you do, then it is desirable to
+ choose a).</li>
+ <li>Quality considerations. VideoLUTs may or may not be of greater
+ depth than the standard 8 bit per color component frame buffer.
+ If they are, and the video path passes that extra depth through
+ to the display, and the display is capable of using that extra
+ depth, then a) may be a desirable choice from a quality point of
+ view. You can get some idea whether this is the case by running
+ "dispcal -R". If the VideoLUT depth is not better than 8 bits,
+ then it may be more desirable to choose b), since renders like
+ MadVR can use dithering to give better than 8 bits precision in
+ the video playback.<br>
+ </li>
+ </ul>
+ <h5>4) Output device calibration and profiling.</h5>
+ Output device profiling should basically follow the guide above in <a
+ href="#PM1b">Adjusting and Calibrating a displays</a> and <a
+ href="#PM1">Profiling Displays</a>. The assumption is that either
+ you are calibrating/profiling your computer display for video, or
+ your TV is connected to the computer you are creating
+ calibrations/profiles on, and that the connection between the PC and
+ TV display is such that full range RGB signals are being used, or
+ that the Video card has automatically or manually been configured to
+ 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>
+ <br>
+ Once the profile has been created, it is possible to then use the
+ resulting Device Link/3DLut with signal encoding other than full
+ range or Video level RGB. <br>
+ <h5>5) Target colorspace<br>
+ </h5>
+ In practical terms, there are five common Video and Digital Cinema
+ encoding colorspaces. <br>
+ <br>
+ For Standard Definition:<br>
+ <br>
+ EBU 3213 or "PAL 576i" primaries.<br>
+ <br>
+ SMPTE RP 145 or "NTSC 480i" primaries.<br>
+ <br>
+ For High Definition:<br>
+ <br>
+ Rec 709 primaries.<br>
+ <br>
+ For Ultra High Defintion<br>
+ <br>
+ Rec 2020 primaries.<br>
+ <br>
+ For Digital Cinema<br>
+ <br>
+ SMPTE-431-2 or "DCI-P3"<br>
+ <br>
+ PAL and NTSC have historically had poorly specified transfer curve
+ encodings, and the Rec 709 HDTV encoding curve is the modern <a
+ href="http://www.poynton.com/notes/DVAI/DVAI_TOC_full.html#23">recommendation</a>,
+ but the overall interpretation of Video sources may in fact be
+ partly determined by the expected standard Video display device
+ characteristics (see <b>Viewing conditions adjustment and gamut
+ mapping</b> below for more details).<br>
+ <br>
+ To enable targeting these colorspaces, ArgyllCMS provides 5 ICC
+ profiles in the ref directory to use as source
+ colorspaces: <br>
+ <br>
+ EBU3213_PAL.icm<br>
+ <br>
+ SMPTE_RP145_NTSC.icm<br>
+ <br>
+ Rec709.icm<br>
+ <br>
+ Rec2020.icm<br>
+ <br>
+ SMPTE431_P3.icm<br>
+ <h5>6) Signal encoding</h5>
+ Typical PC display output uses full range RGB signals (0 .. 255 in 8
+ bit parlance), while typical Video encoding allows some head &
+ footroom for overshoot and sync of digitized analog signals, and
+ typically uses a 16..235 range in 8 bits. In many cases Video is
+ encoded as luma and color difference signals YCbCr (loosely known as
+ YUV as well), and this also uses a restricted range 16..235 for Y,
+ and 16..240 for Cb and Cr in 8 bit encoding. The extended gamut
+ xvYCC encoding uses 16..235 for Y, and 1..254 for Cb and Cr.<br>
+ <br>
+ The signal encoding comes into play in two situations: 1)
+ Calibrating and profiling the display, and 2) Using the resulting
+ Device Link/3DLut.<br>
+ The encoding may need to be different in these two situations,
+ either because different video source devices are being used for
+ calibration/profiling and for video playback, or because the video
+ playback system uses the Device Link/3DLut at a point in its
+ processing pipeline that requires a specific encoding.<br>
+ <br>
+ For calibration & profiling, the display will be driven by a
+ computer system so that dispcal and dispread can be used. By default
+ these programs expect to output full range RGB signals, and it is
+ assumed that either the display accepts full range signals, or that
+ the graphics card or connection path has been setup to convert the
+ full range values into Video range signals automatically or
+ manually. If this is not the case, then both dispcal and dispread
+ have a -E option that will modify them to output Video range RGB
+ values.<br>
+ <br>
+ If MadVR is the target of the calibration and profiling, then there
+ is an option to use it to display the calibration and profiling test
+ patches (<b>-d madvr</b>). In this case, MadVR should be configured
+ appropriately for full range or Video range encoding, and the -E
+ flag should <u>not</u> be used with dispcal or dispread, since
+ MadVR will be taking care of such conversions.<br>
+ <br>
+ If a calibration file was created using dispcal -E, then using it in
+ dispread will automatically trigger Video level RGB signals during
+ profiling. Any time such a Video level calibration is loaded into
+ the Graphics card VideoLUTs using dispwin, or the calibration curve
+ is converted to a 'vcgt' tag in a profile, the curve will also
+ convert full range RGB to Video range RGB. This should be kept in
+ mind so that if video playback is being performed with the
+ calibration curves installed in the Graphics card VideoLUTs, that
+ full range is converted only once to Video range (ie. In this
+ situation MadVR output should be set to full range if being played
+ back through the calibration curves in hardware, but only if dispcal
+ -E has been used). On the other hand, if the calibration curves are
+ incorporated into the DeviceLink/3dLUT, then the conversion to Video
+ levels has to be done somewhere else in the pipeline, such as using
+ MadVR video level output, or by the graphics card, etc.<br>
+ <br>
+ When creating the Device Link/3dLut, it is often necessary to
+ specify one of the video encodings so that it fits in to the
+ processing pipeline correctly. For instance the eeColor needs to
+ have input and output encoding that suits the HDMI signals passing
+ through it, typically Video Range RGB. MadVR needs Video Level RGB
+ to match the values being passed through the 3dLut at that point.<br>
+ <br>
+ There are several version of YCbCr encoding supported as well, even
+ though neither the eeColor nor the current version of MadVR need or
+ can use them at present.<br>
+ <h5>7) Black point mapping</h5>
+ <p>Video encoding assumes that the black displayed on a device is a
+ perfect black (zero light). No real device has a perfect black,
+ and if a colorimetric intent is used then certain image values
+ 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>
+ </p>
+ <h5>8) Viewing conditions adjustment and gamut mapping</h5>
+ <p> </p>
+ <p>In historical TV systems, there is a viewing conditions
+ adjustment being made between the bright studio conditions that TV
+ is filmed in, and the typical dim viewing environment that people
+ view it in. This is created by the difference between the encoding
+ response curve gamma of about 2.0, and a typical CRT response
+ curve gamma of 2.4. <br>
+ </p>
+ <p>In theory Rec709 defines the video encoding, but it seems in
+ 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
+ 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>
+ </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>
+ <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>
+ <br>
+ <tt>dispcal -v -o -qm -k0 -w 0.3127,0.3290 -gs -o TVmtx.icm
+ TV</tt><br>
+ <br>
+ We are targeting a D65 white point (<tt>-w 0.3127,0.3290)</tt> and
+ an sRGB response curve.<br>
+ <br>
+ If you are using the madTPG you would use:<br>
+ <br>
+ <tt>dispcal -v -d madvr -o -qm -k0 -w 0.3127,0.3290 -gs -o
+ TVmtx.icm TV</tt><br>
+ <br>
+ Then we need to create a display patch test set. We can use the
+ simple matrix to pre-condition the test patches, as this helps
+ distribute them where they will be of most benefit. If have
+ previously profiled your display, you should use that previous
+ profile, or if you decided not to do a dispcal, then the Rec709.icm
+ should be used as a substitute. Some per channel and a moderate
+ number of full spread patches is used here - more will increase
+ profiling accuracy, a smaller number will speed it up. Since the
+ video or film material is typically viewed in a darkened viewing
+ environment, and often uses a range of maximum brightnesses in
+ different scenes, the device behavior in the dark regions of its
+ response are often of great importance, and using the <a
+ href="targen.html#V">targen -V</a> parameter can help improve the
+ accuracy in this region at the expense of slightly lower accuracy in
+ lighter regions.<br>
+ <br>
+ <tt>targen -v -d3 -s30 -g100 -f1000 -cTVmtx.icm -V1.8 TV</tt><br>
+ <br>
+ The display can then be measured:<br>
+ <br>
+ <tt>dispread -v -k TV.cal TV</tt><br>
+ <br>
+ or using madTPG:<br>
+ <br>
+ dispread -v -d madvr -K TV.cal TV<br>
+ <br>
+ and then a cLUT type ICC profile created. Since we will be using
+ collink smart linking, we minimize the B2A table size. We use the
+ default colprof -V parameter carried through from targen:<br>
+ <br>
+ <tt>colprof -v -qh -bl TV</tt><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
+ the readings, average errors of 5 or less, and maximum errors of 15
+ or less would normally be expected. If errors are grossly higher
+ than this, then this is an indication that something is seriously
+ wrong with the device measurement, or profile creation.<br>
+ <br>
+ If you would like to use the display ICC profile for general color
+ managed applications, then you would compute a more complete
+ profile:<br>
+ <br>
+ <tt>colprof -v -qh TV</tt><br>
+ <br>
+ The recommended approach then is to create a Device Link that uses 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
+ HD.icm # dark conditions</tt><tt><br>
+ </tt><tt> collink -v -Ib -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
+ HD.icm # mid to dim conditions</tt><tt><br>
+ </tt><tt> collink -v -Ib:2.0 -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
+ mapping:<br>
+ <br>
+ <tt> collink -v -ctv -dmd -da:1 -G -ila Rec709.icm TV.icm
+ HD.icm # very dark conditions</tt><tt><br>
+ </tt><tt> collink -v -ctv -dmd -da:3 -G -ila Rec709.icm
+ TV.icm HD.icm # dim conditions</tt><tt><br>
+ </tt><tt> collink -v -ctv -dmd -da:7 -G -ila Rec709.icm
+ TV.icm HD.icm # mid to dim conditions - good default</tt><tt><br>
+ </tt><tt> collink -v -ctv -dmd -da:15 -G -ila Rec709.icm
+ TV.icm HD.icm # mid conditions</tt><br>
+ <br>
+ or using both to model a reference video display system that is
+ adapted to your viewing conditions:<br>
+ <tt><br>
+ </tt><tt> collink -v -Ib -c md -dmd -da:5 -G -ila
+ Rec709.icm TV.icm HD.icm # very dark conditions</tt><tt><br>
+ </tt><tt> collink -v -Ib -c md -dmd -da:10 -G -ila Rec709.icm
+ TV.icm HD.icm # dim conditions</tt><tt><br>
+ </tt><tt> collink -v -Ib -c md -dmd -da:18 -G -ila Rec709.icm
+ TV.icm HD.icm # mid to dark conditions</tt><tt><br>
+ </tt><tt> collink -v -Ib -c md -dmd -da:30 -G -ila Rec709.icm
+ TV.icm HD.icm # mid to dark conditions</tt><br>
+ <br>
+ None of the above examples incorporate the calibration curves, so it
+ is assumed that the calibration curves would be installed so that
+ the Video Card applies calibration, ie:<br>
+ <br>
+ <tt>dispwin TV.cal</tt><br>
+ <br>
+ or the simple matrix profile installed:<br>
+ <br>
+ <tt>dispwin -I TVmtx.icm</tt><br>
+ <br>
+ or a the more complete display profile could be installed:<br>
+ <br>
+ dispwin -I TV.icm<br>
+ <br>
+ See also <a href="dispprofloc.html">here</a> for information on how
+ to make sure the calibration is loaded on each system start. If not,
+ then you will want to incorporate the calibration in the Device
+ Link/3dlut by using collink "-a TV.cal".<br>
+ <br>
+ If the video path needs Video Level RGB encoding but does not
+ provide a means to do this, then you will want to include the <b>-E</b>
+ flag in the dispcal and dispread command lines above.<br>
+ <br>
+ Below are specific recommendation for the eeColor and MadVR that
+ include the flags to create the .3dlut and encode the input and
+ output values appropriately, but only illustrate using the
+ recommended BT.1886 black point and viewing conditions adjustments,
+ rather than illustrating CIECAM02 etc. use.<br>
+ <br>
+ For faster exploration of different collink option, you could omit
+ the "colprof -bl" option, and use collink "-g" instead of "-G",
+ since this<br>
+ will greatly speed up collink. Once you are happy with the link
+ details, you can then generate a higher quality link/3dLut using
+ "collink -G ..".<br>
+ <br>
+ You can also increase the precision of the device profile by
+ increasing the number of test patches measured (ie. up to a few
+ thousand, depending on how long you are prepared to wait for the
+ measurement to complete, and how stable your display and instrument
+ are).<br>
+ <br>
+ Alternatives to relative colorimetric rendering ("-i r") or
+ luminance matched appearance ("-i la") used in the examples above
+ and below, are, perceptual ("-i p") which will ensure that the
+ source gamut is compressed rather than clipped by the display, or
+ even a saturation rendering ("-i ms"), which will expand the gamut
+ of the source to the full range of the output.<br>
+ <br>
+ <br>
+ <b>eeColor</b><br>
+ <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
+ HD.icm </tt><br>
+ <br>
+ For correct operation both the 3DLut HD.txt and the per channel
+ input curves HD-first1dred.txt, HD-first1dgreen.txt and
+ HD-first1dblue.txt. the latter by copying them over the default
+ input curve files uploaded by the TruVue application.<br>
+ <br>
+ See <a
+ href="http://www.avsforum.com/t/1464890/eecolor-processor-argyllcms"><http://www.avsforum.com/t/1464890/eecolor-processor-argyllcms></a>
+ for some more details.<br>
+ <br>
+ Where the eeColor is connected from a Video source using HDMI, it
+ 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>
+ <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
+ re-installed, or install the ones generated by collink, which will
+ be linear for -e t mode.<br>
+ <br>
+ <b>MadVR</b><br>
+ <br>
+ MadVR 0.86.9 or latter has a number of features to support accurate
+ profiling and calibration, and is the recommended version to
+ use. It converts from the media colorspace to the 3dLut input
+ space automatically with the type of source being played, but has
+ configuration for to 5 3dLuts, each one optimized for a particular
+ source color space. The advantage of building and installing several
+ 3dLuts is that unnecessary gamut clipping can be avoided.<br>
+ <br>
+ If you are just building one 3dLut then Rec709 source is a good one
+ to pick.<br>
+ <br>
+ If you want to share the VideoLUT calibration curves between your
+ 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><tt> </tt><tt><br>
+ </tt><tt> collink -v -3m -et -Et -Ib -G -ir </tt><tt><tt>-H + + + + + + + + + + +
+ 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 + + + + + + + + + + +
+ TV.cal </tt>SMPTE_RP145_NTSC.icm TV.icm SD_NTSC.icm</tt><br>
+ <br>
+ For best quality it is better to let MadVR apply the calibration
+ 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><tt> </tt><tt><br>
+ </tt><tt> collink -v -3m -et -Et -Ib -G -ir </tt><tt><tt>-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 + + + + + + + + + + +
+ TV.cal </tt>SMPTE_RP145_NTSC.icm TV.icm SD_NTSC.icm</tt><br>
+ <br>
+ the consequence though is that the appearance of other application
+ will shift when MadVR is using the 3dLut and loading the calibration
+ curves.<br>
+ <br>
+ The 3dLut can be used by opening the MadVR settings dialog,
+ selecting "calibration" and then selecting "calibrate this display
+ by using an external 3DLUT file", and then using the file dialog to
+ use it.<br>
+ <br>
+ If neither the -a no -H options are used, then no calibration curves
+ will be appended to the 3dLut, and MadVR will not change the
+ VideoLUTs when that 3dLut is in use. It is then up to you to manage
+ the graphics card VideoLUTs in some other fashion.<tt><br>
+ <br>
+ </tt>
+ <hr size="2" width="100%"><br>
+ <h3><a name="TV2"></a>Verifying Video Calibration</h3>
+ <p>Often it is desirable to verify the results of a video
+ calibration and profile, and the following gives an outline of how
+ to use ArgyllCMS tools to do this. It is only possible to expect
+ perfect verification if a colorimetric intent was used during
+ linking - currently it's not possible to exactly verify a
+ perceptual or CIECAM02 viewing condition adjusted link.<br>
+ <br>
+ </p>
+ <p>The first step is to create a set of test points. This is
+ essentially the same as creating a set of test points for the
+ purposes of profiling, although it is best not to create exactly
+ the same set, so as to explore the colorspace at different
+ locatioins. For the purposes here, we'll actually create a regular
+ grid test set, since this makes it easier to visualize the
+ results, although a less regular set would probably be better for
+ numerical evaluation:<br>
+ </p>
+ <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>
+ </p>
+ <p>Next we create a reference file by simulating the expected
+ response of the perfect video display system. Assuming the collink
+ options were "-et -Et -Ib -G -ir Rec709.icm TV.icm HD.icm" then we
+ 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>
+ </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>
+ </p>
+ <hr size="2" width="20%">
+ <p>A sanity check we can make at this point is to see what the
+ expected result of the profiling & calibration will be, by
+ 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>
+ </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>and then you can verify:<br>
+ </tt></p>
+ <p><tt> colverify -v -n -w -x ref.ti3 checkA.ti3<br>
+ </tt></p>
+ <p>If you have targeted some other white point rather than video D65
+ for the display, then use the -N flag instead of -n to align the
+ white points. [ Note that there can be some small discrepancies in
+ this case in some parts of the color space if a CIECAM02 linking
+ intent was used, due to the slightly different chromatic
+ adaptation algorithm it uses compared to the one used by verify to
+ match the white points.]<tt><br>
+ </tt></p>
+ <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
+ 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
+ is likely to be doing the right thing in making the display
+ emulate the video colorspace with a BT.1886 like black point
+ adjustment. You could also check just the in gamut test points
+ using:<br>
+ </p>
+ <p><tt> v</tt><tt>erify -v -N -w -x -L TV.icm ref.ti3
+ checkA.ti3<br>
+ <br>
+ </tt></p>
+ <hr size="2" width="20%">
+ <p>You can explicitly compare the gamuts of your video space and
+ your display using the gamut tools:<br>
+ </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>
+ </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
+ 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>
+ <p><tt> copy verify.ti1 checkB.ti1</tt><tt><br>
+ </tt><tt> dispread -v 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
+ configure madVR to use the 3dLut you want to measure as the
+ default, and also use the dispread -V flag to make sure that the
+ 3dLut is being used for the measurements: [<b>Note</b> that if the
+ version of MadVR you are using does not have radio buttons in its
+ calibration setup to indicate a default 3dLut, then the 3dLut
+ under test should be the only one set - all others should be
+ blank. ]<br>
+ </p>
+ <p><tt> dispread -v -d madvr -V checkB</tt><br>
+ </p>
+ <p>Verify the same way as above:<br>
+ </p>
+ <p><tt> v</tt><tt>erify -v -n -w -x ref.ti3 checkB.ti3<br>
+ </tt></p>
+ <p>If your display does not cover the full gamut of your video
+ source, the errors are probably dominated by out of gamut colors.
+ You can verify just the in gamut test values by asking verify to
+ skip them, and this will give a better notion of the actual device
+ link and calibration accuracy:<tt><br>
+ </tt></p>
+ <p><tt> v</tt><tt>erify -v -n -w -x -L TV.icm ref.ti3
+ checkB.ti3</tt></p>
+ <p><br>
+ </p>
+ <p> <br>
+ </p>
+ <p><br>
+ <br>
+ </p>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ </body>
+</html>
@@ -45,6 +45,8 @@ i1m.jpg i1p.jpg sl.jpg ss.jpg +JETI_1211.jpg +ColorHug.jpg mox.jpg moxxr.jpg Chroma4.jpg @@ -60,6 +62,9 @@ WideGamutColmters.html CrushedDisplyBlacks.html i1proDriver.html i1proDriver.xls +i1proHiRes.html +i1proHiRes.jpg +i1proHiRes.zip evalInputTargets.html YellowGreen.jpg srgbplot.gif @@ -118,7 +123,7 @@ timage.html cube.jpg surface.jpg LabSteps.jpg -verify.html +colverify.html viewgam.html xicclu.html oeminst.html diff --git a/doc/cal_format.html b/doc/cal_format.html index 3e40205..361a329 100644 --- a/doc/cal_format.html +++ b/doc/cal_format.html @@ -10,31 +10,24 @@ <h2>Description of the .cal format</h2> Device calibration information. This is ASCII text, <a href="File_Formats.html#CGATS">CGATS</a>, Argyll specific format, - used - to hold a description of device setup information that brings it to - a - desired calibration state. Calibration files are created by <a - href="synthcal.html">synthcal</a>, <a href="dispcal.html">dispcal</a> + used to hold a description of device setup information that brings + it to a desired calibration state. Calibration files are created by + <a href="synthcal.html">synthcal</a>, <a href="dispcal.html">dispcal</a> and <a href="printcal.html">printcal</a>.<br> <br> While fully compatible with the CGATS.5 Data Exchange Format, the particular required keywords and fields are unique to Argyll, hence - an - Argyll specific file identifier <span style="font-weight: bold;">CAL</span> + an Argyll specific file identifier <span style="font-weight: bold;">CAL</span> is used to avoid confusion with standard ANSI or CGATS files.<br> <br> The <span style="font-weight: bold;">.cal</span> format changes - from - time to time with new releases, to add new functionality, but - generally - retains backwards compatibility. Note that in the description below, - the word "may" indicates an optional component, while the word - "shall" - indicates a necessary component.<br> + from time to time with new releases, to add new functionality, but + generally retains backwards compatibility. Note that in the + description below, the word "may" indicates an optional component, + while the word "shall" indicates a necessary component.<br> <br> Generally a .cal file contains only one table, the table containing - the - setup information. <br> + the setup information. <br> <br> <br> The table contains the following:<br> @@ -50,11 +43,12 @@ style="font-weight: bold;">DESCRIPTOR</span>, <span style="font-weight: bold;">ORIGINATOR</span>, or <span style="font-weight: bold;">CREATED</span> keywords and values (as - per - CGATS).<br> + per CGATS).<br> <br> There shall be a <span style="font-weight: bold;">DEVICE_CLASS</span> keyword that has a value of <span style="font-weight: bold;">"OUTPUT</span>", + + "<span style="font-weight: bold;">DISPLAY</span>" or <span style="font-weight: bold;">"INPUT"</span>.<br> This indicates what type of device the calibration information is @@ -62,65 +56,100 @@ <br> A <span style="font-weight: bold;">"DISPLAY"</span> type device may have a <span style="font-weight: bold;">VIDEO_LUT_CALIBRATION_POSSIBLE - </span>keyword that - must have a value of "<span style="font-weight: bold;">NO</span>" or - "<span style="font-weight: bold;">YES</span>", to indicate whether - the display has the ability to be calibrated by loading VideoLUT - values.<br> + + + </span>keyword that must have a value of "<span style="font-weight: + bold;">NO</span>" or "<span style="font-weight: bold;">YES</span>", + + to indicate whether the display has the ability to be calibrated by + loading VideoLUT values.<br> + <br> + A <span style="font-weight: bold;">"DISPLAY"</span> type device may + have a <span style="font-weight: bold;">TV_OUTPUT_ENCODING </span>keyword + + that must have a value of "<span style="font-weight: bold;">NO</span>" + or "<span style="font-weight: bold;">YES</span>", to indicate + whether the calibration was created withing the video (16-235)/255 + compressed range of device value. This is used to signal to a + VideoLUT loader whether calibration values should be converted to + video encoded range when loaded into hardware. The calibration + values stored in the .cal file are never video encoded themselves, + i.e. 0.0 is always device minimum, and 1.0 is always device maximum.<br> <br> There shall be a keyword <span style="font-weight: bold;">COLOR_REP</span> that has a value that indicates what colorspaces of the device - values. - The colorspaces shall be encoded with one or two letters - per - component. The device spaces shall use the - following letter encoding:<br> + values. The colorspaces shall be encoded with one or two + letters per component. The device spaces shall use the following + letter encoding:<br> <br> <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span> Cyan + + - + + + C<br> Magenta M<br> Yellow - + + + Y<br> Black - + + + K<br> Orange - + + + O<br> Red - + + + R<br> Green - + + + G<br> Blue - + + + B<br> White W<br> Light Cyan - + + + c<br> Light -Magenta + Magenta + + m<br> Light -Yellow + Yellow + + y<br> Light -Black + Black + + k<br> Medium Cyan 2c<br> Medium Magenta - - 2m<br> + 2m<br> Medium Yellow 2y<br> Medium Black @@ -130,53 +159,47 @@ Black &nb There may be an a prefix <span style="font-weight: bold;">i</span> preceding the device space letter encoding, indicating that although the space appears to be an additive space, it is in fact a - subtractive - device.<br> + subtractive device.<br> <br> Typical values might be: "<span style="font-weight: bold;">RGB</span><span style="font-weight: bold;"></span>" for an RGB display, "<span style="font-weight: bold;">iRGB</span><span style="font-weight: - bold;"></span>" - for an RGB printer, "<span style="font-weight: bold;">CMYK</span>" - for - a - printer, "<span style="font-weight: bold;">RGB"</span> for an RGB - scanner.<br> + bold;"></span>" for an RGB printer, "<span style="font-weight: + bold;">CMYK</span>" for a printer, "<span style="font-weight: + bold;">RGB"</span> for an RGB scanner.<br> <br> The <span style="font-weight: bold;">NUMBER_OF_FIELDS</span> - keyword - shall have a value that indicates the number of fields in each data - set, e.g. <span style="font-weight: bold;">4</span> (as per CGATS).<br> + keyword shall have a value that indicates the number of fields in + each data set, e.g. <span style="font-weight: bold;">4</span> (as + per CGATS).<br> <br> The start of the declaration of the fields shall be marked by the <span style="font-weight: bold;">BEGIN_DATA_FORMAT</span> keyword (as - per - CGATS).<br> + per CGATS).<br> <br> The fields shall use the standard CGATS pattern of the full - colorspace - identified followed by the individual colorant identifier. There - shall - be an initial input index value identified by the letter <span - style="font-weight: bold;">I</span>.<br> + colorspace identified followed by the individual colorant + identifier. There shall be an initial input index value identified + by the letter <span style="font-weight: bold;">I</span>.<br> <br> - For an RGB device, the - following fields would be used:<br> + For an RGB device, the following fields would be used:<br> <br> <span style="font-weight: bold;">RGB_I</span> + + The device value input value between 0.0 and 1.0.<br> <span style="font-weight: bold;">RGB_R</span> + + The Red device value input value between 0.0 and 1.0.<br> <span style="font-weight: bold;">RGB_G</span> The Green device value input value between 0.0 - and - 1.0.<br> + and 1.0.<br> <span style="font-weight: bold;">RGB_B</span> The Blue device value input value between 0.0 - and - 1.0.<br> + and 1.0.<br> <br> The corresponding field names for a CMYK device would be <span style="font-weight: bold;">CMYK_I</span>, <span @@ -198,16 +221,15 @@ Black &nb CGATS).<br> <br> Each set of data shall be on one line, and shall be separated by - white - space. All values shall be normalized to lie between 0.0 and 1.0.<br> + white space. All values shall be normalized to lie between 0.0 and + 1.0.<br> <br> The end of the values of the data sets shall be marked by the <span style="font-weight: bold;">END_DATA</span> keyword (as per CGATS).<br> <br> There may then be device type specific extra tables that hold target - or - device behavior information. These will be specific to the tool that - creates that particular type of calibration.<br> + or device behavior information. These will be specific to the tool + that creates that particular type of calibration.<br> <br> Generally any other keywords and values will be ignored.<br> <br> diff --git a/doc/ccxxmake.html b/doc/ccxxmake.html index c4d8059..8ef31b7 100644 --- a/doc/ccxxmake.html +++ b/doc/ccxxmake.html @@ -42,7 +42,7 @@ 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="file:///D:/src/argyll/doc/oeminst.html">installed</a>, and + href="oeminst.html">installed</a>, and will then appear in the available display type selection (<b>-y</b> option).<br> <br> @@ -69,6 +69,8 @@ + + Verbose mode</small><br> <a href="#S">-S</a> Create @@ -87,6 +89,8 @@ rather + + than CCMX<br> <a href="#f">-f file1.ti3[,file2.ti3]</a> @@ -108,6 +112,8 @@ 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 @@ -124,6 +130,8 @@ two + + displayname</a> [X11 only] Choose X11 display name</font><br style="font-family: monospace;"> <font style="font-family: monospace;" size="-1"></font><font @@ -153,6 +161,8 @@ m + + for VideoLUT access.</font><br style="font-family: monospace;"> <font style="font-family: monospace;" size="-1"> <a href="#d">-d @@ -168,6 +178,8 @@ m + + n</a> Choose the @@ -189,6 +201,8 @@ list + + (default 1)</font><br> <span style="font-family: monospace;"> <a href="#dweb">-dweb[:port]</a> @@ -208,7 +222,21 @@ list - Display via a web server at port (default 8080)</span><br + + + Display via a web server at port (default 8080)</span><br> + <span style="font-family: monospace;"> <a href="#dmadvr">-dmadvr</a> + + + + + + + + + + + [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> @@ -225,6 +253,8 @@ list + + Use telephoto mode (ie. for a projector) (if available)</font><br style="font-family: monospace;"> <font size="-1"><span style="font-family: monospace;"><a @@ -244,6 +274,8 @@ list + + Display type - instrument specific list to choose from.</span></font><font style="font-family: monospace;" size="-1"> (CCMX)</font><br style="font-family: monospace;"> @@ -261,6 +293,8 @@ list + + ho,vo,ss[,vs]</a> Position test window and scale it</font><br style="font-family: monospace;"> <font style="font-family: monospace;" size="-1"> @@ -284,6 +318,8 @@ center, + + 1.0 = right/bottom etc.</font><br style="font-family: monospace;"> <font style="font-family: monospace;" size="-1"> ss: @@ -306,6 +342,8 @@ normal, + + 2.0 = double etc.</font><br> <font size="-1"><span style="font-family: monospace;"> @@ -315,6 +353,8 @@ normal, + + ss,vs: = optional horizontal, vertical scale.</span></font><br style="font-family: monospace;"> <font style="font-family: monospace;" size="-1"> </font><font @@ -333,6 +373,8 @@ normal, + + Fill whole screen with black background</font><br style="font-family: monospace;"> <small style="font-family: monospace;"> <span @@ -358,6 +400,8 @@ on + + test window<br> </small><font style="font-family: monospace;" size="-1"> <a href="#N">-N</a> @@ -374,6 +418,8 @@ on + + Disable initial calibration of instrument</font><small style="font-family: monospace;"> if possible<br> </small><span style="font-family: monospace;"> </span><font @@ -392,6 +438,8 @@ on + + Use high resolution spectrum mode (if available)</font><font style="font-family: monospace;" size="-1"></font><br style="font-family: monospace;"> @@ -409,6 +457,8 @@ on + + "command"</a> Invoke shell "command" each time a color is set<br> </font><small style="font-family: monospace;"> <a href="#o">-o @@ -439,6 +489,8 @@ sequence + + combination steps (default 3)</font><br style="font-family: monospace;"> <font style="font-family: monospace;" size="-1"> <a href="#W">-W @@ -455,6 +507,8 @@ sequence + + n|h|x</a> Override serial @@ -476,6 +530,8 @@ n + + none, h = HW, x = Xon/Xoff</font><br style="font-family: monospace;"> <small style="font-family: monospace;"> <a href="#D">-D [level]</a> @@ -500,6 +556,8 @@ overall + + escription</small><br> <small style="font-family: monospace;"> <a href="#I">-I "displayname"</a> </small><span @@ -519,11 +577,15 @@ overall + + "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> + + Set UI selection character(s)</tt><br> <font size="-1"><span style="font-family: monospace;"> </span><a style=" font-family: monospace;" href="#Yrn">-<font size="-1">Y</font> @@ -537,8 +599,12 @@ 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 style="font-family: monospace;"> @@ -638,6 +704,8 @@ 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 @@ -660,6 +728,13 @@ overall style="font-weight: bold;">/sbin/ifconfig</span> (Linux or OS X) and identify an internet address for your machine that way.<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. Test patch + colors <u>will</u> be processed by the MadVR 3dLut.<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 @@ -752,6 +827,8 @@ overall + + of particular instruments</a> for more details. This may give better accuracy for display measurements.<br> <br> @@ -860,14 +937,22 @@ overall + + <b>-Y n</b> options overrides the refresh display mode set by the <a - href="file:///D:/src/argyll/doc/spotread.html#y">-y display type + 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 + 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 diff --git a/doc/cht_format.html b/doc/cht_format.html index 1e02db1..80a3e9e 100644 --- a/doc/cht_format.html +++ b/doc/cht_format.html @@ -1,576 +1,622 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> -<head> - <title>Scan Recognition Format File (.cht)</title> - <meta http-equiv="content-type" - content="text/html; charset=ISO-8859-1"> - <meta name="author" content="Graeme Gill"> -</head> -<body> -<h2>Description of the .cht format</h2> -[This is a rather inflexible format, that should really be replaced -with a CGATS style file.]<br> -<br> -The <span style="font-weight: bold;">.cht</span> format file is used -to hold the image recognition information that allows the <a - href="scanin.html">scanin</a> program to align the input image with -the specified sample boxes.<br> -<br> -A raw <span style="font-weight: bold;">.cht</span> file can be -produced by running <a href="scanin.html">scanin</a> -with the <a href="scanin.html#g">-g</a> option, although this will -then need -cleaning up manually, using a text editor. The cleanup consists of -deleting -any unwanted reference lines from the XLIST and YLISTs, adding the the -sample -box references, and possibly adding the expected sample values.<br> -<br> -The <span style="font-weight: bold;">.cht</span> image recognition -file is usually set up to recognized a scanned test chart that includes -the edges of the chart itself, <span style="font-weight: bold;">not</span> -a cropped version of the chart that excludes the edges of the chart -itself. This is to allow <span style="font-weight: bold;">scanin</span> -to be used with scans that have just be roughly cropped, without -requiring that a scan be treated in detail with an application such as -Adobe Photoshop.<br> -<br> -The keywords and associated data must be used in the following order: <b>BOXES</b>, -<b>BOX_SHRINK</b>, <b>REF_ROTATION</b>, <b>XLIST</b>, <b>YLIST</b> -and <b>EXPECTED</b>.<br> -<br> -The physical units used for boxes and edge lists are arbitrary units -(i.e. -pixels as generated by scanin -g, but could be mm, inches etc. if -created - some other way), the only requirement is that the sample box -definitions need to agree with the X/YLIST definitions. Typically if a -scanned chart is used to build the reference, the units will be pixels -of the scanned chart.<br> -<br> -The <b>BOXES</b> keyword introduces the list of diagnostic and sample -boxes. -The integer following this keyword must be the total number of -diagnostic -and sample boxes, but <span style="font-weight: bold;">not</span> -including any fiducual marks. The lines following the BOXES keyword must -then -contain -the fiducial mark, diagnostic or sample box definitions. Each box -definition line -consists -of 11 space separated parameters, and can generate a grid of sample or -diagnostic -boxes:<br> -<br> - <b>kl lxs lxe lys lye w h xo yo xi yi</b><br> -<br> -with the following usage:<br> -<br> - <b>kl</b> is a key letter.<br> -<br> - <span style="font-weight: bold;">F</span> -is used to define four fiducial mZarks that may be used for manual -alignment of an image to the target. The four marks are nominally a -top left mark, a top right mark, bottom right mark and a bottom left -mark. The parameters are labeled as follows:<br> - <b><br> - </b><b>F _ _ x0 y0 x1 y1 x2 y2 -x3 y3<br> -<br> - </b>Where the first two -parameters are not used, and a '_' character should be used as -a place holder, and the follows the X and Y coordinates for the four -fiducial marks.<span style="font-weight: bold;"></span><span - style="font-weight: bold;"></span> Typically fiducial marks are chosen -to be at the corners of the overall bounding box, or at corner cross -marks on the chart etc. Fiducial marks may be omitted, but in this case -manual alignment cannot be used.<br> -<br> - <b>D</b> is used for a diagnostic -box which will show up in the diagnostic raster output, but is not used -as -a sample box. The label information can be arbitrary.<br> - <br> - <b>X</b> is used for a sequence -of boxes in which the X label comes first in the concatenated sample -box label.<br> - <br> - <b>Y</b> is used for a sequence -of boxes in which the Y label comes first in the concatenated sample -box label.<br> -<br> - Boxes are created incrementing in -the X direction fastest, and the Y direction slowest.<br> -<br> - <b>lxs</b> is the X axis starting label. This is -generally a letter or number, and it will be incremented appropriately -to reach <b>lxe</b><br> -<br> - <b>lxe</b> is the X axis ending label. When the X -label reaches this this value (inclusively), the iteration in the X -direction will reset.<br> -<br> - <b>lys</b> is the Y axis starting label. This is -generally a letter or number, and it will be incremented appropriately -to reach <b>lye</b><br> -<br> - <b>lye</b> is the Y axis ending label. When the Y -label reaches this this value (inclusively), the iteration through the -boxes will end.<br> -<br> - The X & Y labels will be concatenated to form -the sample box label.<br> -<br> - A sample label that consists of the character '_' is -treated as a null label (useful for an array that only iterates in one -direction).<br> -<br> - <b>w</b>,<b> h</b> are the width and height of each -box in the array.<br> -<br> - <b>xo</b>, <b>yo</b> are the origin of the top -left -of the array.<br> -<br> - <b>xi</b>, <b>yi</b> are the increments between -each -box in the array.<br> -<br> -A blank line should follow the last box definition line.<br> -<br> -The keyword <b>BOX_SHRINK</b> marks the definition of how much each -sample -box should be shrunk on each edge before sampling the pixel values. -This -allows the sample boxes to be defined at their edges, while allowing a -safety -margin for the pixels actually sampled. The units are the same -arbitrary units -used for the sample box definitions.<br> -<br> -A blank line should follow this keyword.<br> -<br> -The optional <b>REF_ROTATION</b> keyword indicates the rotation in -radians -clockwise of the reference image when the edge lists were generated. -This -amount of rotation is undone to the image before applying the sample -box -location information. The rotation is about the origin -(the -origin is assumed to be upper left corner). If omitted, the reference -rotation -is assumed to be 0.0<br> -<br> -A blank line should follow this keyword.<br> -<br> -The <b>XLIST</b> is a list of vertical edge reference "ticks", along -the -X axis. Ticks are just edge transitions, typically being each edge of -the sample boxes, but should include edges of any features that have -significant width and a length that is at least 50% of the available -space. It is these edge ticks that are used to locate the reference -cells position within the input raster. The integer after the keyword -"XLIST" is the number of entries -in -the list. The first number in the column is the offset of the tick from -the -origin, the second number is used to improve the correlation by -representing -the strength of that "tick" relative to the strongest tick which will -have -a value 1.0. Strength is measured by the relative length of the edge.<br> -<br> -The third number represents the relative number of times this "tick" is -crossed by lines in the other direction. A line is regarded as crossing -if part of it is closer to the "tick" line that half the distance to -the next tick line. The number is normalized so that the largest -crossing count has a weight of -1.0. This may be set to 1.0 if it is not known or easily computed.<br> -<br> -A blank line should follow the last <b>XLIST</b> edge definition.<br> -<br> -The <b>YLIST</b> is same format and details as the <b>XLIST</b>, used -for -horizontal edges.<br> -<br> -The <b>EXPECTED</b> keyword introduces an optional list of <span - style="text-decoration: underline;">approximate</span> -expected -sample -box color values, allowing better identification of the possible -rotation -of a chart, particularly if it has no asymmetric patch shapes or -locations -in the chart. Following the keyword should either be <b>XYZ</b> or <b>LAB</b>, -depending on the color space used to describe the reference values, -then -an integer indicating the number of entries in the list.<br> -<br> -Each following expected color entry consists of four values. The first -is -the sample box label, which should correspond to one of those defined -by -the <b>BOXES</b> entry above. It is an error if no corresponding box -has -been defined. The remaining three values are the <span - style="text-decoration: underline;">approximate</span> XYZ or -L*a*b* -color value expected for that sample box. The XYZ values are assumed to -be -scaled to a maximum Y value of 100. An expected color value doesn't -have -to be provided for every defined sample box, nor is it expected to be -accurate - it just has to represent the approximate expected color. -(Actual chart reference values are provided as a separate CGATS file to -<a href="scanin.html"><span style="font-weight: bold;">scanin</span></a>).<br> -<br> -A blank line should follow the last <b>EXPECTED</b> box value.<br> -<br> -<br> -<hr size="2" width="100%"><br> -The following is an example .cht file, suitable for a typical Q60 IT8 -scan target.<br> -<tt><br> -<font size="-1"> BOXES 290<br> - F _ _ _ _ 1 1 615.5 1.5 615 409<br> - D ALL ALL _ _ 615 409 1 1 0 0<br> - D MARK MARK _ _ 14 14 1 1 0 0<br> - Y 01 22 A L 25.625 25.625 26.625 26.625 25.625 25.625<br> - X GS00 GS23 _ _ 25.625 51.25 0.0 358.75 25.625 0.0<br> -<br> -BOX_SHRINK 3.0<br> -<br> -REF_ROTATION -0.002006<br> -<br> -XLIST 32<br> - 1.799625 1.000000 0.312500<br> - 27.064987 0.874039 0.750000<br> - 52.592403 0.133439 0.687500<br> - 78.196610 0.264191 0.687500<br> - 104.117756 0.165427 0.937500<br> - 129.377994 0.844432 0.937500<br> - 155.144274 0.501218 0.875000<br> - 180.839181 0.491428 0.937500<br> - 206.359758 0.212384 0.937500<br> - 232.038808 0.851851 0.937500<br> - 257.854725 0.162956 0.625000<br> - 283.552463 0.101243 0.812500<br> - 300.534000 0.024750 0.812500<br> - 309.507688 0.093829 1.000000<br> - 334.711314 0.856821 1.000000<br> - 360.428194 0.787677 1.000000<br> - 385.849730 0.748130 0.937500<br> - 386.650071 0.039487 0.687500<br> - 394.630372 0.024725 0.687500<br> - 411.835654 0.802501 0.750000<br> - 414.017731 0.041974 0.937500<br> - 437.133504 0.674062 0.937500<br> - 437.975355 0.103714 1.000000<br> - 462.938460 0.671643 1.000000<br> - 463.880560 0.093836 0.937500<br> - 488.517995 0.679022 1.000000<br> - 514.338544 0.760511 1.000000<br> - 540.037492 0.111108 0.625000<br> - 565.856396 0.133330 0.562500<br> - 591.114717 0.565475 0.562500<br> - 603.447516 0.032097 0.312500<br> - 615.984915 0.829608 0.250000<br> -<br> -YLIST 22<br> - 2.477956 0.993407 0.142857<br> - 12.988903 0.016393 0.190476<br> - 14.739109 0.036082 0.190476<br> - 26.746171 0.911487 0.428571<br> - 52.537114 0.303282 0.904762<br> - 78.060317 0.585303 0.857143<br> - 103.498271 0.606862 0.761905<br> - 128.994535 0.567266 0.761905<br> - 154.483041 0.550814 0.714286<br> - 179.935985 0.623055 0.666667<br> - 205.552940 0.350826 0.714286<br> - 212.051372 0.016393 0.714286<br> - 231.153547 0.824618 0.857143<br> - 256.697418 0.744268 0.952381<br> - 282.145841 0.736126 0.904762<br> - 307.899015 0.536075 0.952381<br> - 333.262903 0.903282 0.809524<br> - 340.217754 0.019722 0.190476<br> - 344.988867 0.019671 0.095238<br> - 346.988885 0.018032 0.095238<br> - 358.840278 0.999967 1.000000<br> - 409.201393 1.000000 0.000000<br> -<br> -EXPECTED XYZ 264<br> - A1 3.85 3.22 1.9<br> - A2 4.89 3.27 1.6<br> - A3 5.87 3.31 1.33<br> - A4 6.3 3.38 1.19<br> - A5 13.01 11.44 7.64<br> - A6 16.14 11.99 6.81<br> - A7 19.35 12.41 6.06<br> - A8 20.41 11.97 5.3<br> - A9 43.5 42.81 32.65<br> - A10 45.58 42.37 30.95<br> - A11 48.99 43.2 29.9<br> - A12 50.73 44.02 29.96<br> - A13 74.46 78.76 66.06<br> - A14 75.66 76.42 64.08<br> - A15 78.36 81.34 65.41<br> - A16 70.52 73.3 59.16<br> - A17 74.98 75.98 60.69<br> - A18 72.85 77.3 60.25<br> - A19 73.09 75.52 64.54<br> - B1 3.47 3.08 1.41<br> - B2 4.41 3.25 0.9<br> - B3 5.04 3.23 0.58<br> - B4 5.19 3.11 0.47<br> - B5 13.36 11.59 5.56<br> - B6 15.97 12.03 3.69<br> - B7 19.2 12.49 2.2<br> - B8 19.73 11.52 1.17<br> - B9 42.19 41.84 29.34<br> - B10 44.83 42.17 25.93<br> - B11 48.06 42.9 23.01<br> - B12 49.63 43.08 21.34<br> - B13 66.21 72.54 64.61<br> - B14 70.16 67.1 60.33<br> - B15 75.46 78.69 51.58<br> - B16 57.47 59.58 47.66<br> - B17 68.33 66.45 49.05<br> - B18 63.89 70.29 51.3<br> - B19 61.12 62.16 59.79<br> - C1 4.97 4.75 1.98<br> - C2 5.18 4.65 1.23<br> - C3 5.51 4.58 0.71<br> - C4 5.77 4.61 0.67<br> - C5 24.57 23.44 10.14<br> - C6 28.1 24.64 5.22<br> - C7 31.15 25.28 2.2<br> - C8 30.85 23.68 1.35<br> - C9 49.16 49.36 32.37<br> - C10 51.72 50.72 26.53<br> - C11 55.24 53.14 21.93<br> - C12 56.87 53.62 18.46<br> - C13 57.68 65.65 62.7<br> - C14 63.46 56.66 55.49<br> - C15 73 76.11 40.78<br> - C16 44.73 46.38 36.8<br> - C17 60.64 55.73 38.1<br> - C18 52.15 60.27 41.5<br> - C19 48.13 49.18 54.38<br> - D1 4.19 4.41 1.93<br> - D2 4.48 4.72 1.24<br> - D3 4.55 4.78 0.8<br> - D4 4.32 4.53 0.78<br> - D5 27.33 28.55 12.95<br> - D6 28.68 30.04 7.25<br> - D7 29.51 31.01 3.41<br> - D8 27.55 28.44 1.83<br> - D9 56.06 58.19 38.21<br> - D10 56.03 58.46 30.02<br> - D11 56.2 59.33 24.44<br> - D12 56.19 59.41 19.14<br> - D13 48.21 57.42 59.53<br> - D14 58.18 49.14 51.36<br> - D15 70.98 73.73 33.63<br> - D16 34.31 35.73 28.22<br> - D17 54.27 47.53 29.58<br> - D18 41.67 50.64 32.28<br> - D19 36.95 37.82 48.09<br> - E1 4.15 4.75 2.03<br> - E2 4 4.98 1.37<br> - E3 3.3 4.49 0.86<br> - E4 3.11 4.3 0.86<br> - E5 13.11 14.9 7.06<br> - E6 12.26 15.23 4.18<br> - E7 11.53 15.57 2.27<br> - E8 9.69 13.74 1.51<br> - E9 39.15 42.08 27.33<br> - E10 37.43 41.51 22.23<br> - E11 36.99 42.5 18.85<br> - E12 36.4 42.58 16.27<br> - E13 39.97 49.81 56.15<br> - E14 52.08 41.07 46.36<br> - E15 68.71 70.76 26.45<br> - E16 25.7 26.97 21.28<br> - E17 48.53 40.6 22<br> - E18 31.62 40.82 23.35<br> - E19 31.19 31.19 43.4<br> - F1 1.51 1.91 1.06<br> - F2 1.29 2.04 0.98<br> - F3 1.16 2.09 0.82<br> - F4 1.14 2.04 0.8<br> - F5 6.53 8.25 5.13<br> - F6 5.61 8.66 4.38<br> - F7 4.6 8.77 3.7<br> - F8 3.45 7.63 2.78<br> - F9 37.8 41.07 30.91<br> - F10 35.92 40.76 29.03<br> - F11 35.42 41.99 29.07<br> - F12 34 41.8 28<br> - F13 32.13 42.12 51.99<br> - F14 45.72 33.34 40.77<br> - F15 66.26 67.29 19.65<br> - F16 17.02 18.07 14.4<br> - F17 41.59 32.53 15.16<br> - F18 26.26 35.26 18.81<br> - F19 24.3 23.6 37.48<br> - G1 2.31 3 2.27<br> - G2 2 3.21 2.58<br> - G3 1.66 3.21 2.75<br> - G4 1.58 3.03 2.6<br> - G5 8.99 11.08 8.79<br> - G6 7.68 11.3 9.56<br> - G7 6.52 11.5 10.2<br> - G8 5.5 10.85 10.55<br> - G9 38.29 41.75 33.45<br> - G10 35.83 41.16 34.11<br> - G11 34.56 41.83 35.63<br> - G12 33.69 42.14 36.7<br> - G13 25.95 35.68 48<br> - G14 40.6 27.62 36.14<br> - G15 63.72 63.63 14.35<br> - G16 10.85 11.82 9.58<br> - G17 37.23 27.64 11.62<br> - G18 20.28 28.97 14.15<br> - G19 17.7 16.74 31.7<br> - H1 2.56 3.04 2.92<br> - H2 2.34 3.2 4.12<br> - H3 2.12 3.28 5.43<br> - H4 2.06 3.18 5.29<br> - H5 10.07 11.6 11.24<br> - H6 9.01 11.68 14.81<br> - H7 8.22 12 19.42<br> - H8 7.25 11.55 21.45<br> - H9 39.25 42.31 36.81<br> - H10 37.58 41.85 40.37<br> - H11 37.16 43.07 45.79<br> - H12 36.27 43.78 49.47<br> - H13 21.47 30.78 44.22<br> - H14 36.49 23.35 32.38<br> - H15 61.58 60.55 10.95<br> - H16 8.21 8.71 6.91<br> - H17 33.04 23.26 8.38<br> - H18 16.22 24.35 10.41<br> - H19 12.86 11.84 26.82<br> - I1 4.22 4.44 5.28<br> - I2 4.35 4.48 8.36<br> - I3 4.4 4.44 11.94<br> - I4 4.48 4.58 12.17<br> - I5 15.15 15.78 15.23<br> - I6 14.56 15.12 19.52<br> - I7 14.37 14.81 24.48<br> - I8 14.11 14.76 30.03<br> - I9 41.03 42.58 36.94<br> - I10 40.85 42.23 40.73<br> - I11 40.86 42.33 45.05<br> - I12 41.31 42.73 47.77<br> - I13 17.26 25.93 40.23<br> - I14 32.66 19.63 28.81<br> - I15 59.37 57.18 7.79<br> - I16 4.97 5.32 4.32<br> - I17 28.62 18.88 5.48<br> - I18 11.58 18.98 7.25<br> - I19 9.58 8.34 22.87<br> - I20 0.45 0.4 0.33<br> - I21 2.28 1.78 0.98<br> - I22 2.37 1.95 0.85<br> - J1 2.15 1.9 2.6<br> - J2 2.57 2 4.72<br> - J3 2.93 1.95 8.1<br> - J4 3.15 1.92 10.76<br> - J5 11.73 11.6 11.81<br> - J6 12.98 11.93 16.19<br> - J7 13.91 12.07 20.95<br> - J8 14.01 11.59 24.35<br> - J9 40.75 41.22 36.34<br> - J10 41.26 41.07 39.74<br> - J11 42.63 41.68 44.51<br> - J12 44.02 41.78 49.25<br> - J13 13.82 21.69 35.98<br> - J14 28.87 16.33 25.08<br> - J15 56.04 52.29 4.97<br> - J16 2.46 2.63 2.29<br> - J17 24.04 14.75 3.15<br> - J18 8.12 14.49 4.55<br> - J19 5.98 4.79 17.76<br> - J20 8.26 5.37 1.04<br> - J21 11.52 7.81 1.62<br> - J22 14.67 10.72 2.6<br> - K1 5.63 4.7 4.86<br> - K2 6.74 4.58 7.23<br> - K3 8.04 4.48 9.73<br> - K4 9.39 4.76 11.79<br> - K5 16.66 15.39 14.44<br> - K6 18.72 15.18 18.23<br> - K7 21.56 15.5 22.97<br> - K8 23 15.02 25.37<br> - K9 42.5 42.02 36.05<br> - K10 44.55 41.63 39.71<br> - K11 47.19 41.96 44.03<br> - K12 49.9 43.14 47.21<br> - K13 10.61 17.44 31.24<br> - K14 24.84 13.19 21<br> - K15 53.12 48.05 3.19<br> - K16 1.05 1.14 1.13<br> - K17 19.93 11.34 1.67<br> - K18 5.3 10.47 2.73<br> - K19 3.95 2.76 13.94<br> - K20 30.61 26.43 11.04<br> - K21 34.91 29.6 11.78<br> - K22 38.95 34.57 18.4<br> - L1 3.88 3.12 2.32<br> - L2 4.93 3.2 2.69<br> - L3 5.75 3.14 3.02<br> - L4 7.31 3.79 3.4<br> - L5 13.29 11.54 9.39<br> - L6 16.22 11.73 10.32<br> - L7 19.95 12.08 12.06<br> - L8 20.79 11.31 12.01<br> - L9 43.22 42.09 33.78<br> - L10 45.52 41.88 34.65<br> - L11 49.04 42.87 35.98<br> - L12 51.03 43.83 37.78<br> - L13 7.45 12.77 25.59<br> - L14 21.26 10.76 17.73<br> - L15 49.45 43.12 2.14<br> - L16 0.47 0.49 0.5<br> - L17 16.04 8.49 0.78<br> - L18 2.91 6.5 1.39<br> - L19 2.5 1.45 10.28<br> - L20 38.7 33.98 20.86<br> - L21 39.36 35.23 21.23<br> - L22 41.36 38.77 23.51<br> - GS0 79.47 82.51 69.04<br> - GS1 72.62 74.94 59.17<br> - GS2 63.15 65.11 51.57<br> - GS3 54.72 56.51 45.03<br> - GS4 48.1 49.81 39.24<br> - GS5 42.22 43.64 34.45<br> - GS6 37.33 38.7 30.5<br> - GS7 32.38 33.61 26.11<br> - GS8 27.56 28.7 22.11<br> - GS9 22.5 23.4 17.99<br> - GS10 18.77 19.55 14.83<br> - GS11 15.48 16.08 12.04<br> - GS12 12.69 13.29 9.98<br> - GS13 10.35 10.81 7.97<br> - GS14 8.39 8.77 6.37<br> - GS15 6.45 6.79 4.97<br> - GS16 4.95 5.18 3.7<br> - GS17 3.58 3.82 2.76<br> - GS18 2.76 2.89 2.06<br> - GS19 1.97 2.08 1.45<br> - GS20 1.22 1.31 0.98<br> - GS21 1 1.05 0.74<br> - GS22 0.87 0.89 0.65<br> - GS23 0.34 0.32 0.32<br> -<br> -</font> </tt><br> -<tt> <br> -</tt><br> -<br> -</body> + <head> + <title>Scan Recognition Format File (.cht)</title> + <meta http-equiv="content-type" content="text/html; + charset=windows-1252"> + <meta name="author" content="Graeme Gill"> + </head> + <body> + <h2>Description of the .cht format</h2> + [This is a rather inflexible format, that should really be replaced + with a CGATS style file.]<br> + <br> + The <span style="font-weight: bold;">.cht</span> format file is + used + to hold the image recognition information that allows the <a + href="scanin.html">scanin</a> program to align the input image + with + the specified sample boxes.<br> + <br> + A raw <span style="font-weight: bold;">.cht</span> file can be + produced by running <a href="scanin.html">scanin</a> + with the <a href="scanin.html#g">-g</a> option, although this will + then need + cleaning up manually, using a text editor. The cleanup consists of + deleting + any unwanted reference lines from the XLIST and YLISTs, adding the + the + sample + box references, and possibly adding the expected sample values.<br> + <br> + The <span style="font-weight: bold;">.cht</span> image recognition + file is usually set up to recognized a scanned test chart that + includes + the edges of the chart itself, <span style="font-weight: bold;">not</span> + a cropped version of the chart that excludes the edges of the chart + itself. This is to allow <span style="font-weight: bold;">scanin</span> + to be used with scans that have just be roughly cropped, without + requiring that a scan be treated in detail with an application such + as + Adobe Photoshop.<br> + <br> + The keywords and associated data must be used in the following + order: <b>BOXES</b>, + <b>BOX_SHRINK</b>, <b>REF_ROTATION</b>, <b>XLIST</b>, <b>YLIST</b> + and <b>EXPECTED</b>.<br> + <br> + The physical units used for boxes and edge lists are arbitrary units + (i.e. + pixels as generated by scanin -g, but could be mm, inches etc. if + created + some other way), the only requirement is that the sample box + definitions need to agree with the X/YLIST definitions. Typically if + a + scanned chart is used to build the reference, the units will be + pixels + of the scanned chart.<br> + <br> + The <b>BOXES</b> keyword introduces the list of diagnostic and + sample + boxes. + The integer following this keyword must be the total number of + diagnostic + and sample boxes, but <span style="font-weight: bold;">not</span> + including any fiducual marks. The lines following the BOXES keyword + must + then + contain + the fiducial mark, diagnostic or sample box definitions. Each box + definition line + consists + of 11 space separated parameters, and can generate a grid of sample + or + diagnostic + boxes:<br> + <br> + <b>kl lxs lxe lys lye w h xo yo xi yi</b><br> + <br> + with the following usage:<br> + <br> + <b>kl</b> is a key letter.<br> + <br> + <span style="font-weight: + bold;">F</span> + is used to define four fiducial marks that may be used for manual + alignment of an image to the target. The four marks are nominally a + top left mark, a top right mark, bottom right mark and a bottom left + mark (ie. clockwise order from top left). The parameters are labeled + as follows:<br> + <b><br> + </b><b>F _ _ x0 y0 x1 y1 x2 + y2 + x3 y3<br> + <br> + </b>Where the first two + parameters are not used, and a '_' character should be used as + a place holder, and the follows the X and Y coordinates for the four + fiducial marks.<span style="font-weight: bold;"></span><span + style="font-weight: bold;"></span> Typically fiducial marks are + chosen + to be at the corners of the overall bounding box, or at corner cross + marks on the chart etc. Fiducial marks may be omitted, but in this + case + manual alignment cannot be used.<br> + <br> + <b>D</b> is used for a + diagnostic + box which will show up in the diagnostic raster output, but is not + used + as + a sample box. The label information can be arbitrary.<br> + <br> + <b>X</b> is used for a + sequence + of boxes in which the X label comes first in the concatenated sample + box label.<br> + <br> + <b>Y</b> is used for a + sequence + of boxes in which the Y label comes first in the concatenated sample + box label.<br> + <br> + Boxes are created incrementing + in + the X direction fastest, and the Y direction slowest.<br> + <br> + <b>lxs</b> is the X axis starting label. This is + generally a letter or number, and it will be incremented + appropriately + to reach <b>lxe</b><br> + <br> + <b>lxe</b> is the X axis ending label. When the X + label reaches this this value (inclusively), the iteration in the X + direction will reset.<br> + <br> + <b>lys</b> is the Y axis starting label. This is + generally a letter or number, and it will be incremented + appropriately + to reach <b>lye</b><br> + <br> + <b>lye</b> is the Y axis ending label. When the Y + label reaches this this value (inclusively), the iteration through + the + boxes will end.<br> + <br> + The X & Y labels will be concatenated to form + the sample box label.<br> + <br> + A sample label that consists of the character '_' + is + treated as a null label (useful for an array that only iterates in + one + direction).<br> + <br> + <b>w</b>,<b> h</b> are the width and height of + each + box in the array.<br> + <br> + <b>xo</b>, <b>yo</b> are the origin of the top + left + of the array.<br> + <br> + <b>xi</b>, <b>yi</b> are the increments between + each + box in the array.<br> + <br> + A blank line should follow the last box definition line.<br> + <br> + The keyword <b>BOX_SHRINK</b> marks the definition of how much each + sample + box should be shrunk on each edge before sampling the pixel values. + This + allows the sample boxes to be defined at their edges, while allowing + a + safety + margin for the pixels actually sampled. The units are the same + arbitrary units + used for the sample box definitions.<br> + <br> + A blank line should follow this keyword.<br> + <br> + The optional <b>REF_ROTATION</b> keyword indicates the rotation in + radians + clockwise of the reference image when the edge lists were generated. + This + amount of rotation is undone to the image before applying the sample + box + location information. The rotation is about the origin + (the + origin is assumed to be upper left corner). If omitted, the + reference + rotation + is assumed to be 0.0<br> + <br> + A blank line should follow this keyword.<br> + <br> + The <b>XLIST</b> is a list of vertical edge reference "ticks", + along + the + X axis. Ticks are just edge transitions, typically being each edge + of + the sample boxes, but should include edges of any features that have + significant width and a length that is at least 50% of the available + space. It is these edge ticks that are used to locate the reference + cells position within the input raster. The integer after the + keyword + "XLIST" is the number of entries + in + the list. The first number in the column is the offset of the tick + from + the + origin, the second number is used to improve the correlation by + representing + the strength of that "tick" relative to the strongest tick which + will + have + a value 1.0. Strength is measured by the relative length of the + edge.<br> + <br> + The third number represents the relative number of times this "tick" + is + crossed by lines in the other direction. A line is regarded as + crossing + if part of it is closer to the "tick" line that half the distance to + the next tick line. The number is normalized so that the largest + crossing count has a weight of + 1.0. This may be set to 1.0 if it is not known or easily computed.<br> + <br> + A blank line should follow the last <b>XLIST</b> edge definition.<br> + <br> + The <b>YLIST</b> is same format and details as the <b>XLIST</b>, + used + for + horizontal edges.<br> + <br> + The <b>EXPECTED</b> keyword introduces an optional list of <span + style="text-decoration: underline;">approximate</span> + expected + sample + box color values, allowing better identification of the possible + rotation + of a chart, particularly if it has no asymmetric patch shapes or + locations + in the chart. Following the keyword should either be <b>XYZ</b> or + <b>LAB</b>, + depending on the color space used to describe the reference values, + then + an integer indicating the number of entries in the list.<br> + <br> + Each following expected color entry consists of four values. The + first + is + the sample box label, which should correspond to one of those + defined + by + the <b>BOXES</b> entry above. It is an error if no corresponding + box + has + been defined. The remaining three values are the <span + style="text-decoration: underline;">approximate</span> XYZ or + L*a*b* + color value expected for that sample box. The XYZ values are assumed + to + be + scaled to a maximum Y value of 100. An expected color value doesn't + have + to be provided for every defined sample box, nor is it expected to + be + accurate - it just has to represent the approximate expected color. + (Actual chart reference values are provided as a separate CGATS file + to + <a href="scanin.html"><span style="font-weight: bold;">scanin</span></a>).<br> + <br> + A blank line should follow the last <b>EXPECTED</b> box value.<br> + <br> + <br> + <hr size="2" width="100%"><br> + The following is an example .cht file, suitable for a typical Q60 + IT8 + scan target.<br> + <tt><br> + <font size="-1"> BOXES 290<br> + F _ _ _ _ 1 1 615.5 1.5 615 409<br> + D ALL ALL _ _ 615 409 1 1 0 0<br> + D MARK MARK _ _ 14 14 1 1 0 0<br> + Y 01 22 A L 25.625 25.625 26.625 26.625 25.625 25.625<br> + X GS00 GS23 _ _ 25.625 51.25 0.0 358.75 25.625 0.0<br> + <br> + BOX_SHRINK 3.0<br> + <br> + REF_ROTATION -0.002006<br> + <br> + XLIST 32<br> + 1.799625 1.000000 0.312500<br> + 27.064987 0.874039 0.750000<br> + 52.592403 0.133439 0.687500<br> + 78.196610 0.264191 0.687500<br> + 104.117756 0.165427 0.937500<br> + 129.377994 0.844432 0.937500<br> + 155.144274 0.501218 0.875000<br> + 180.839181 0.491428 0.937500<br> + 206.359758 0.212384 0.937500<br> + 232.038808 0.851851 0.937500<br> + 257.854725 0.162956 0.625000<br> + 283.552463 0.101243 0.812500<br> + 300.534000 0.024750 0.812500<br> + 309.507688 0.093829 1.000000<br> + 334.711314 0.856821 1.000000<br> + 360.428194 0.787677 1.000000<br> + 385.849730 0.748130 0.937500<br> + 386.650071 0.039487 0.687500<br> + 394.630372 0.024725 0.687500<br> + 411.835654 0.802501 0.750000<br> + 414.017731 0.041974 0.937500<br> + 437.133504 0.674062 0.937500<br> + 437.975355 0.103714 1.000000<br> + 462.938460 0.671643 1.000000<br> + 463.880560 0.093836 0.937500<br> + 488.517995 0.679022 1.000000<br> + 514.338544 0.760511 1.000000<br> + 540.037492 0.111108 0.625000<br> + 565.856396 0.133330 0.562500<br> + 591.114717 0.565475 0.562500<br> + 603.447516 0.032097 0.312500<br> + 615.984915 0.829608 0.250000<br> + <br> + YLIST 22<br> + 2.477956 0.993407 0.142857<br> + 12.988903 0.016393 0.190476<br> + 14.739109 0.036082 0.190476<br> + 26.746171 0.911487 0.428571<br> + 52.537114 0.303282 0.904762<br> + 78.060317 0.585303 0.857143<br> + 103.498271 0.606862 0.761905<br> + 128.994535 0.567266 0.761905<br> + 154.483041 0.550814 0.714286<br> + 179.935985 0.623055 0.666667<br> + 205.552940 0.350826 0.714286<br> + 212.051372 0.016393 0.714286<br> + 231.153547 0.824618 0.857143<br> + 256.697418 0.744268 0.952381<br> + 282.145841 0.736126 0.904762<br> + 307.899015 0.536075 0.952381<br> + 333.262903 0.903282 0.809524<br> + 340.217754 0.019722 0.190476<br> + 344.988867 0.019671 0.095238<br> + 346.988885 0.018032 0.095238<br> + 358.840278 0.999967 1.000000<br> + 409.201393 1.000000 0.000000<br> + <br> + EXPECTED XYZ 264<br> + A1 3.85 3.22 1.9<br> + A2 4.89 3.27 1.6<br> + A3 5.87 3.31 1.33<br> + A4 6.3 3.38 1.19<br> + A5 13.01 11.44 7.64<br> + A6 16.14 11.99 6.81<br> + A7 19.35 12.41 6.06<br> + A8 20.41 11.97 5.3<br> + A9 43.5 42.81 32.65<br> + A10 45.58 42.37 30.95<br> + A11 48.99 43.2 29.9<br> + A12 50.73 44.02 29.96<br> + A13 74.46 78.76 66.06<br> + A14 75.66 76.42 64.08<br> + A15 78.36 81.34 65.41<br> + A16 70.52 73.3 59.16<br> + A17 74.98 75.98 60.69<br> + A18 72.85 77.3 60.25<br> + A19 73.09 75.52 64.54<br> + B1 3.47 3.08 1.41<br> + B2 4.41 3.25 0.9<br> + B3 5.04 3.23 0.58<br> + B4 5.19 3.11 0.47<br> + B5 13.36 11.59 5.56<br> + B6 15.97 12.03 3.69<br> + B7 19.2 12.49 2.2<br> + B8 19.73 11.52 1.17<br> + B9 42.19 41.84 29.34<br> + B10 44.83 42.17 25.93<br> + B11 48.06 42.9 23.01<br> + B12 49.63 43.08 21.34<br> + B13 66.21 72.54 64.61<br> + B14 70.16 67.1 60.33<br> + B15 75.46 78.69 51.58<br> + B16 57.47 59.58 47.66<br> + B17 68.33 66.45 49.05<br> + B18 63.89 70.29 51.3<br> + B19 61.12 62.16 59.79<br> + C1 4.97 4.75 1.98<br> + C2 5.18 4.65 1.23<br> + C3 5.51 4.58 0.71<br> + C4 5.77 4.61 0.67<br> + C5 24.57 23.44 10.14<br> + C6 28.1 24.64 5.22<br> + C7 31.15 25.28 2.2<br> + C8 30.85 23.68 1.35<br> + C9 49.16 49.36 32.37<br> + C10 51.72 50.72 26.53<br> + C11 55.24 53.14 21.93<br> + C12 56.87 53.62 18.46<br> + C13 57.68 65.65 62.7<br> + C14 63.46 56.66 55.49<br> + C15 73 76.11 40.78<br> + C16 44.73 46.38 36.8<br> + C17 60.64 55.73 38.1<br> + C18 52.15 60.27 41.5<br> + C19 48.13 49.18 54.38<br> + D1 4.19 4.41 1.93<br> + D2 4.48 4.72 1.24<br> + D3 4.55 4.78 0.8<br> + D4 4.32 4.53 0.78<br> + D5 27.33 28.55 12.95<br> + D6 28.68 30.04 7.25<br> + D7 29.51 31.01 3.41<br> + D8 27.55 28.44 1.83<br> + D9 56.06 58.19 38.21<br> + D10 56.03 58.46 30.02<br> + D11 56.2 59.33 24.44<br> + D12 56.19 59.41 19.14<br> + D13 48.21 57.42 59.53<br> + D14 58.18 49.14 51.36<br> + D15 70.98 73.73 33.63<br> + D16 34.31 35.73 28.22<br> + D17 54.27 47.53 29.58<br> + D18 41.67 50.64 32.28<br> + D19 36.95 37.82 48.09<br> + E1 4.15 4.75 2.03<br> + E2 4 4.98 1.37<br> + E3 3.3 4.49 0.86<br> + E4 3.11 4.3 0.86<br> + E5 13.11 14.9 7.06<br> + E6 12.26 15.23 4.18<br> + E7 11.53 15.57 2.27<br> + E8 9.69 13.74 1.51<br> + E9 39.15 42.08 27.33<br> + E10 37.43 41.51 22.23<br> + E11 36.99 42.5 18.85<br> + E12 36.4 42.58 16.27<br> + E13 39.97 49.81 56.15<br> + E14 52.08 41.07 46.36<br> + E15 68.71 70.76 26.45<br> + E16 25.7 26.97 21.28<br> + E17 48.53 40.6 22<br> + E18 31.62 40.82 23.35<br> + E19 31.19 31.19 43.4<br> + F1 1.51 1.91 1.06<br> + F2 1.29 2.04 0.98<br> + F3 1.16 2.09 0.82<br> + F4 1.14 2.04 0.8<br> + F5 6.53 8.25 5.13<br> + F6 5.61 8.66 4.38<br> + F7 4.6 8.77 3.7<br> + F8 3.45 7.63 2.78<br> + F9 37.8 41.07 30.91<br> + F10 35.92 40.76 29.03<br> + F11 35.42 41.99 29.07<br> + F12 34 41.8 28<br> + F13 32.13 42.12 51.99<br> + F14 45.72 33.34 40.77<br> + F15 66.26 67.29 19.65<br> + F16 17.02 18.07 14.4<br> + F17 41.59 32.53 15.16<br> + F18 26.26 35.26 18.81<br> + F19 24.3 23.6 37.48<br> + G1 2.31 3 2.27<br> + G2 2 3.21 2.58<br> + G3 1.66 3.21 2.75<br> + G4 1.58 3.03 2.6<br> + G5 8.99 11.08 8.79<br> + G6 7.68 11.3 9.56<br> + G7 6.52 11.5 10.2<br> + G8 5.5 10.85 10.55<br> + G9 38.29 41.75 33.45<br> + G10 35.83 41.16 34.11<br> + G11 34.56 41.83 35.63<br> + G12 33.69 42.14 36.7<br> + G13 25.95 35.68 48<br> + G14 40.6 27.62 36.14<br> + G15 63.72 63.63 14.35<br> + G16 10.85 11.82 9.58<br> + G17 37.23 27.64 11.62<br> + G18 20.28 28.97 14.15<br> + G19 17.7 16.74 31.7<br> + H1 2.56 3.04 2.92<br> + H2 2.34 3.2 4.12<br> + H3 2.12 3.28 5.43<br> + H4 2.06 3.18 5.29<br> + H5 10.07 11.6 11.24<br> + H6 9.01 11.68 14.81<br> + H7 8.22 12 19.42<br> + H8 7.25 11.55 21.45<br> + H9 39.25 42.31 36.81<br> + H10 37.58 41.85 40.37<br> + H11 37.16 43.07 45.79<br> + H12 36.27 43.78 49.47<br> + H13 21.47 30.78 44.22<br> + H14 36.49 23.35 32.38<br> + H15 61.58 60.55 10.95<br> + H16 8.21 8.71 6.91<br> + H17 33.04 23.26 8.38<br> + H18 16.22 24.35 10.41<br> + H19 12.86 11.84 26.82<br> + I1 4.22 4.44 5.28<br> + I2 4.35 4.48 8.36<br> + I3 4.4 4.44 11.94<br> + I4 4.48 4.58 12.17<br> + I5 15.15 15.78 15.23<br> + I6 14.56 15.12 19.52<br> + I7 14.37 14.81 24.48<br> + I8 14.11 14.76 30.03<br> + I9 41.03 42.58 36.94<br> + I10 40.85 42.23 40.73<br> + I11 40.86 42.33 45.05<br> + I12 41.31 42.73 47.77<br> + I13 17.26 25.93 40.23<br> + I14 32.66 19.63 28.81<br> + I15 59.37 57.18 7.79<br> + I16 4.97 5.32 4.32<br> + I17 28.62 18.88 5.48<br> + I18 11.58 18.98 7.25<br> + I19 9.58 8.34 22.87<br> + I20 0.45 0.4 0.33<br> + I21 2.28 1.78 0.98<br> + I22 2.37 1.95 0.85<br> + J1 2.15 1.9 2.6<br> + J2 2.57 2 4.72<br> + J3 2.93 1.95 8.1<br> + J4 3.15 1.92 10.76<br> + J5 11.73 11.6 11.81<br> + J6 12.98 11.93 16.19<br> + J7 13.91 12.07 20.95<br> + J8 14.01 11.59 24.35<br> + J9 40.75 41.22 36.34<br> + J10 41.26 41.07 39.74<br> + J11 42.63 41.68 44.51<br> + J12 44.02 41.78 49.25<br> + J13 13.82 21.69 35.98<br> + J14 28.87 16.33 25.08<br> + J15 56.04 52.29 4.97<br> + J16 2.46 2.63 2.29<br> + J17 24.04 14.75 3.15<br> + J18 8.12 14.49 4.55<br> + J19 5.98 4.79 17.76<br> + J20 8.26 5.37 1.04<br> + J21 11.52 7.81 1.62<br> + J22 14.67 10.72 2.6<br> + K1 5.63 4.7 4.86<br> + K2 6.74 4.58 7.23<br> + K3 8.04 4.48 9.73<br> + K4 9.39 4.76 11.79<br> + K5 16.66 15.39 14.44<br> + K6 18.72 15.18 18.23<br> + K7 21.56 15.5 22.97<br> + K8 23 15.02 25.37<br> + K9 42.5 42.02 36.05<br> + K10 44.55 41.63 39.71<br> + K11 47.19 41.96 44.03<br> + K12 49.9 43.14 47.21<br> + K13 10.61 17.44 31.24<br> + K14 24.84 13.19 21<br> + K15 53.12 48.05 3.19<br> + K16 1.05 1.14 1.13<br> + K17 19.93 11.34 1.67<br> + K18 5.3 10.47 2.73<br> + K19 3.95 2.76 13.94<br> + K20 30.61 26.43 11.04<br> + K21 34.91 29.6 11.78<br> + K22 38.95 34.57 18.4<br> + L1 3.88 3.12 2.32<br> + L2 4.93 3.2 2.69<br> + L3 5.75 3.14 3.02<br> + L4 7.31 3.79 3.4<br> + L5 13.29 11.54 9.39<br> + L6 16.22 11.73 10.32<br> + L7 19.95 12.08 12.06<br> + L8 20.79 11.31 12.01<br> + L9 43.22 42.09 33.78<br> + L10 45.52 41.88 34.65<br> + L11 49.04 42.87 35.98<br> + L12 51.03 43.83 37.78<br> + L13 7.45 12.77 25.59<br> + L14 21.26 10.76 17.73<br> + L15 49.45 43.12 2.14<br> + L16 0.47 0.49 0.5<br> + L17 16.04 8.49 0.78<br> + L18 2.91 6.5 1.39<br> + L19 2.5 1.45 10.28<br> + L20 38.7 33.98 20.86<br> + L21 39.36 35.23 21.23<br> + L22 41.36 38.77 23.51<br> + GS0 79.47 82.51 69.04<br> + GS1 72.62 74.94 59.17<br> + GS2 63.15 65.11 51.57<br> + GS3 54.72 56.51 45.03<br> + GS4 48.1 49.81 39.24<br> + GS5 42.22 43.64 34.45<br> + GS6 37.33 38.7 30.5<br> + GS7 32.38 33.61 26.11<br> + GS8 27.56 28.7 22.11<br> + GS9 22.5 23.4 17.99<br> + GS10 18.77 19.55 14.83<br> + GS11 15.48 16.08 12.04<br> + GS12 12.69 13.29 9.98<br> + GS13 10.35 10.81 7.97<br> + GS14 8.39 8.77 6.37<br> + GS15 6.45 6.79 4.97<br> + GS16 4.95 5.18 3.7<br> + GS17 3.58 3.82 2.76<br> + GS18 2.76 2.89 2.06<br> + GS19 1.97 2.08 1.45<br> + GS20 1.22 1.31 0.98<br> + GS21 1 1.05 0.74<br> + GS22 0.87 0.89 0.65<br> + GS23 0.34 0.32 0.32<br> + <br> + </font> </tt><br> + <tt> <br> + </tt><br> + <br> + </body> </html> diff --git a/doc/collink.html b/doc/collink.html index 0b94bc7..778b682 100644 --- a/doc/collink.html +++ b/doc/collink.html @@ -27,6 +27,30 @@ style="font-family: monospace;"> + + + + + + + + + + + + + + + + + + + + + + + + Verbose<br> </span></small><small><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#A">-A "manufacturer"</a><span @@ -57,6 +81,30 @@ Verify existing + + + + + + + + + + + + + + + + + + + + + + + + profile, rather than link (Debug option)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -71,6 +119,30 @@ Override 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 @@ -79,6 +151,30 @@ Don't preserve + + + + + + + + + + + + + + + + + + + + + + + + device curves in result</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -112,15 +208,73 @@ preserve Include - abstract profile in link</span><br style="font-family: - monospace;"> - <span style="font-family: monospace;"> </span><a + + + + + + + + + + + + + + + + + + + + + + + + + abstract profile in link</span></small><br> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#a">-a file.cal</a><span + style="font-family: monospace;"> + Apply calibration + curves</span></small> to link output and append linear<br> + <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 style="font-family: monospace;" href="#s">-s</a><span style="font-family: monospace;"> Simple 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 @@ -133,6 +287,30 @@ Mode Gamut + + + + + + + + + + + + + + + + + + + + + + + + Mapping Mode using inverse outprofile A2B [optional source gamut]</span><br style="font-family: monospace;"> <br style="font-family: monospace;"> @@ -149,6 +327,30 @@ Gamut s + + + + + + + + + + + + + + + + + + + + + + + + = saturation, a = absolute colorimetric</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -162,6 +364,30 @@ s s + + + + + + + + + + + + + + + + + + + + + + + + = saturation, a = absolute colorimetric</span><br style="font-family: monospace;"> <br style="font-family: monospace;"> @@ -178,12 +404,60 @@ a - + + + + + + + + + + + + + + + + + + + + + + + + Absolute Colorimetric (in Jab) [ICC Absolute Colorimetric]<br> aw - + + + + + + + + + + + + + + + + + + + + + + + + Absolute Colorimetric (in Jab) with scaling to fit white point<br style="font-family: monospace;"> </span><span style="font-family: monospace;"> @@ -191,12 +465,60 @@ aa - + + + + + + + + + + + + + + + + + + + + + + + + Absolute Appearance</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> r - + + + + + + + + + + + + + + + + + + + + + + + + White Point Matched Appearance [ICC Relative Colorimetric]</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -204,6 +526,30 @@ la - + + + + + + + + + + + + + + + + + + + + + + + + Luminance matched Appearance</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -211,11 +557,59 @@ p - + + + + + + + + + + + + + + + + + + + + + + + + Perceptual (Preferred) [ICC Perceptual]<br> </span></small><small><span style="font-family: monospace;"> pa + + + + + + + + + + + + + + + + + + + + + + + + - Perceptual Appearance</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"></span><span @@ -224,12 +618,60 @@ ms - + + + + + + + + + + + + + + + + + + + + + + + + Saturation</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> s - + + + + + + + + + + + + + + + + + + + + + + + + Enhanced Saturation [ICC Saturation]</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -237,8 +679,56 @@ al - - Absolute Colorimetric (Lab)</span><span style="font-family: - monospace;"></span><br style="font-family: monospace;"> + + + + + + + + + + + + + + + + + + + + + + + + + Absolute Colorimetric (Lab)<br> + + + + + + + + + + + + + + + + + + + + + + + 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 @@ -254,6 +744,30 @@ al either + + + + + + + + + + + + + + + + + + + + + + + + an enumerated choice, or a parameter</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -266,6 +780,30 @@ either either + + + + + + + + + + + + + + + + + + + + + + + + an enumerated choice, or a parameter:value change<br> </span></small><small><span style="font-family: monospace;"> pp - Practical @@ -276,12 +814,60 @@ 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><span style="font-family: monospace;"></span><span @@ -296,6 +882,30 @@ either + + + + + + + + + + + + + + + + + + + + + + + + mb - Monitor in bright work environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -321,6 +931,30 @@ s:surround n + + + + + + + + + + + + + + + + + + + + + + + + = auto, a = average, m = dim, d = dark,</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -328,6 +962,30 @@ n + + + + + + + + + + + + + + + + + + + + + + + + c = transparency (default average)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -335,6 +993,30 @@ w:X:Y:Z Adapted + + + + + + + + + + + + + + + + + + + + + + + + white point as XYZ (default media white)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -342,12 +1024,60 @@ w:x:y Adapted + + + + + + + + + + + + + + + + + + + + + + + + white point as x, y</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> a:adaptation Adaptatation + + + + + + + + + + + + + + + + + + + + + + + + luminance in cd.m^2 (default 50.0)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -356,30 +1086,105 @@ Background % + + + + + + + + + + + + + + + + + + + + + + + + of image luminance (default 20)<br> - l:scenewhite - Scene white in cd.m^2 if surround = auto (default 250)<br - style="font-family: monospace;"> - </span><span style="font-family: monospace;"> + l:imagewhite + Image white in cd.m^2 if surround = auto (default 250)</span></small><br + style="font-family: monospace;"> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> f:flare Flare light - % of image luminance (default 1)</span><br style="font-family: - monospace;"> + + + + + + + + + + + + + + + + + + + + + + + + + % of image luminance (default 0)<br> + </span></small> </span><span style="font-family: + monospace;"> + g:glare Glare light % of + ambient (default 1)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -f:X:Y:Z -Flare - color as XYZ (default media white)</span><br 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;"> -f:x:y -Flare + + + + + + + + + + + + + + g:x:y Glare color as x, y</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#t">-t <i>tlimit</i></a><span @@ -388,6 +1193,30 @@ set source + + + + + + + + + + + + + + + + + + + + + + + + total ink limit, 0 - 400% (estimate by default)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -397,6 +1226,30 @@ set source + + + + + + + + + + + + + + + + + + + + + + + + total ink limit, 0 - 100% (estimate by default)</span><br style="font-family: monospace;"> <br style="font-family: monospace;"> @@ -413,6 +1266,30 @@ source 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;"> @@ -420,6 +1297,30 @@ t 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 @@ -430,6 +1331,30 @@ z p + + + + + + + + + + + + + + + + + + + + + + + + = black level generation curve parameters</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -441,6 +1366,30 @@ p q + + + + + + + + + + + + + + + + + + + + + + + + = transfer source K to dual curve limits</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -455,6 +1404,30 @@ set destination + + + + + + + + + + + + + + + + + + + + + + + + total ink limit, 0 - 400% (estimate by default)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -464,16 +1437,349 @@ set destination + + + + + + + + + + + + + + + + + + + + + + + + total ink limit, 0 - 100% (estimate by default)<br> - </span></small> <small><span style="font-family: - monospace;"><a href="#P">-P</a> + <a href="#3">-3 flag</a> + + + + + + + + + + + + + + + + + + + + + Create "3DLut" output file as well as devlink<br> + + e + + + + + + + + + + + + + + + + + + + + + eeColor .txt file</span></small><br> + <tt> + m + + + + + + + + + MadVR .3dlut file</tt><br> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> <a href="#Ib">-I b</a> + + + + + + + + + + + + + + + + + + + + + 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> + + + + + + + + + + + + + + Apply BT.1886-like mapping with effective gamma g.g to + input<br> + </span></small></span></small> <a href="#IB">-I B</a> + + + + + + + + + + + + + + + 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> + + + + + + + + + + + + + + Apply BT.1886-like mapping with technical gamma g.g to input<br> + </span></small> <a href="#e">-e flag</a> + + + + + + + + + + + + + + + + + + + + + Video encode input as:<br> + <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 + + + + + + + + + + normal RGB 0..1 levels (default)<br> + + t + + + + + + + + + + RGB (16-235)/255 "TV" 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> + + x + + + + + + + + + + xvYCC Rec601 YCbCr Rec709 Prims. SD (16-235,240)/255 "TV" + levels<br> + + X + + + + + + + + + + xvYCC Rec709 YCbCr Rec709 Prims. HD (16-235,240)/255 "TV" + levels<br> + </span></small> </span></small> <small><span + style="font-family: monospace;"><a href="#P">-P</a> Create gamut + + + + + + + + + + + + + + + + + + + + + + + + gammap_p.wrl and gammap_s.wrl diagostics</span></small><small><br> - <br> <span style="font-family: monospace;"></span></small><span style="font-family: monospace;"> <span style="text-decoration: underline;"><span style="font-style: @@ -484,9 +1790,57 @@ source ICC + + + + + + + + + + + + + + + + + + + + + + + + profile. 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: monospace;"> <span style="font-family: monospace;"><span @@ -498,6 +1852,30 @@ destination 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: @@ -570,6 +1948,30 @@ ICC + + + + + + + + + + + + + + + + + + + + + + + + Override clut res. set by <b>-q</b><br> <br> This sets the basic quality of the resulting link, by choosing the @@ -644,13 +2046,28 @@ ICC conflict with achieving a smooth mapping, warnings messages will be emitted.<br> <br> - <a name="p"></a> The <b>-p</b> option alows specifying an abstract - profile be applied between the source and destination profiles. An - abstract profile is a way of specifying a color adjustment in a - device independent way. The abstract profile might have been created - using one of the <span style="font-weight: bold;">tweak</span> + <a name="p"></a> The <b>-p</b> parameter allows specifying an + abstract profile be applied between the source and destination + profiles. An abstract profile is a way of specifying a color + adjustment in a device independent way. The abstract profile might + have been created using one of the <span style="font-weight: bold;">tweak</span> tools, such as <a href="refine.html">refine</a>.<br> <br> + <a name="a"></a> The <b>-a</b> parameter causes calibration curves + in the supplied file to be applied after the link of the profiles. + This is used as an alternative to calibration curves being loaded + into the graphics card VideoLut. For MadVR 3dlut output, a linear + set of calibration curves will also be appended to the 3dlut, + ensuring that the correct VideoLUT curves get loaded at the time the + 3dLut is used by MadVR v0.86.9 or latter. By default no calibration + curves are appended to a MadVR 3dLut.<br> + <br> + <a name="H"></a> The <b>-H</b> parameter causes calibration curves + in the supplied file to be appended to a MadVR 3dlut output, + ensuring that the correct VideoLUT curves get loaded at the time the + 3dLut is used by MadVR v0.86.9 or latter. By default no calibration + curves are appended to a MadVR 3dLut.<br> + <br> The basic linking style is chosen by using the <b>-s</b> (default), <b>-g</b> or <b>-G</b> flags. The three behaviors are:<br> <br> @@ -698,6 +2115,30 @@ ICC 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 @@ -710,6 +2151,30 @@ ICC + + + + + + + + + + + + + + + + + + + + + + + + <b>p</b> = perceptual, <b>r</b> = relative colorimetric,<br> <b>s</b> @@ -778,10 +2243,10 @@ ICC <br> <a name="ila"></a>The <span style="font-weight: bold;">la</span> intent, Luminance matched appearance, linearly compresses or - expands the the luminance axis to match the source to the - destination space, while not otherwise altering the gamut, - clipping any out of gamut colors to the closest match. This is - often useful for appearance based soft proofing.<br> + expands the the luminance axis from white to black to match the + source to the destination space, while not otherwise altering the + gamut, clipping any out of gamut colors to the closest match. This + is often useful for appearance based soft proofing.<br> <br> <a name="ip"></a>The <span style="font-weight: bold;">p</span> intent, Perceptual, uses "knee" type 3 Dimensional compression to @@ -816,11 +2281,18 @@ ICC The white point is mapped precisely from source to destination.<br> <br> <a name="ial"></a>The <span style="font-weight: bold;">al</span> - intent, Absolute Appearance (Lab), is similar to intent <span - style="font-weight: bold;">a</span>, but L*a*b* colorspace is - used rather than CIECAM02 Jab appearance space. This often leads - to poor reproduction of blue and red hues, but can be useful as a - reference mapping.<br> + intent, Absolute Colorimetric (Lab), is similar to intent <span + style="font-weight: bold;">a</span>, but <b>L*a*b*</b> + colorspace is used rather than CIECAM02 Jab appearance space. This + often leads to poor reproduction of blue and red hues, but can be + useful as a reference mapping.<br> + <br> + <a name="iar"></a>The <span style="font-weight: bold;">ar</span> + intent, White Point Matched Colorimetric (Lab), is similar to + intent <span style="font-weight: bold;">r</span>, but L*a*b* + colorspace is used rather than CIECAM02 Jab appearance space. This + often leads to poor reproduction of blue and red hues, but can be + useful as a reference mapping.<br> </div> <br> <a name="w"></a> The <b>-w</b> flag forces the white points to be @@ -919,30 +2391,150 @@ ICC + + + + + + + + + + + + + + + + + + + + + + + + _______ enle<br> | + + + + + + + + + + + + + + + + + + + + + + + + /<br> | + + + + + + + + + + + + + + + + + + + + + + + + /<br> | + + + + + + + + + + + + + + + + + + + + + + + + /<br> | + + + + + + + + + + + + + + + + + + + + + + + + /<br> stle | ------/<br> @@ -955,6 +2547,30 @@ ICC White + + + + + + + + + + + + + + + + + + + + + + + + Black<br> <br> </tt>For minimum sensitivity of printed output to the lighting @@ -1023,6 +2639,243 @@ White &nb in final calibrated device values if the profile includes calibration information.<br> <br> + <a name="3"></a>The <b>-3</b> <i>flag</i> triggers creation of a + "3dLut" of one of the following formats:<br> + <b>e</b> <a + href="http://www.eecolor.com/">eeColor </a>format ".txt" files. + This includes 3 input curve files, the cLut file and 3 output curve + files.<br> + <b>m</b> <a + href="http://forum.doom9.org/showthread.php?t=146228&page=22">MadVR</a> + format ".3dlut" file.<br> + <br> + Some hardware devices and other software make use of cLUT type + tables that are analogous to ICC device links, but are typically + less sophisticated and flexible. The <b>-3</b> flag allows creation + of some of these file formats as well as the normal ICC device link. + Choosing one of these formats will typically also configure various + other parameters to default values suitable for that format, such as + the table resolution (<b>-r</b>), and the use of 1D input and + output curves (<b>-n</b>). Other parameters (such as <b>-I</b>, <b>-e</b> + and <b>-E</b>) may have to be set to get a table suitable for the + particular target and situation.<br> + <br> + The <b>-3 e</b> eeColor format is basically a 65^3 cLUT, but the + hardware is unable to map a 1.0 input value to anything other than + 1.0 output. If one of the video input encodings is being used (<b>-e + t</b> or <b>-e 7</b> etc.), then this is not an issued, since a + 1.0 input is not used for image data. For normal (full) input range + (ie. if the eeColor is being used to process the output of a + computer Video card, and the video card is not encoding using TV + values), then this is a problem, and collink will compensate for + this by creating a set of per channel input curve files that can be + loaded into the eeColor. The xvYCC encoding (<b>-e x</b> and <b>-e + X</b>) uses almost the full range of values for the Cb & Cr + values, and also needs per channel input curves to allow a full + range of mapping.<br> + <br> + For this reason collink generates the following 7 files:<br> + <br> + basename-first1dred.txt<br> + basename-first1dgreen.txt<br> + basename-first1dblue.txt<br> + test.txt <br> + basename-second1dred.txt<br> + basename-second1dgreen.txt<br> + basename-second1dblue.txt<br> + <br> + even though the 1d files will be linear for all cases except the + normal and xvYCC input range.<br> + <br> + The MadVR format is an 8 bit input, 16 bit output cLUT of 100 Mbytes + size, and will written to the file <b>basename.3dlut</b>. If the -a + or -H options are used, then the MadVR 3dLut will have a set of + appropriate per channel calibration curves appended to the 3dLut, to + ensure that the hardware is correctly set for it if used with MadVR + V0.86.9 or latter. This functionality is analogous to a 'VCGT' tag + in a normal ICC display profile.<br> + <br> + 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 + + + + + + + + + + + + + + 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> + <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><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> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> + x + + + + + + + + + + xvYCC Rec601 YCbCr Rec709 Prims. SD (16-235,240)/255 "TV" + levels<br> + + X + + + + + + + + + + xvYCC Rec709 YCbCr Rec709 Prims. HD (16-235,240)/255 "TV" + levels</span></small></span></small><br> + <br> + When xvYCC is chosen, the encoding is either a Rec601 YCbCr or + Rec709 YCbCr with extended range Cb and Cr values, and a hard coded + Rec709 source colorspace, corresponding to the xvYCC specifications. + The <a href="#p1">source profile</a> provided to collink is used to + define the source gamut for gamut mapping, and also the space that + any <a href="#Ib">BT.1886</a> processing will be performed in. For + instance, if the xvYCC is being used to encode a larger gamut such + as UHD Rec2020, or Digital Cinema SMPTE431 P3, then the + corresponding ICC profile should be provided as the source profile.<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> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> + n + + + + + + + + + + normal RGB 0..1 full range levels (default)<br> + + t + + + + + + + + + + RGB (16-235)/255 "TV" 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> + </span></small></span></small><br> + <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 illustrate the gamut mapping generated.<br> @@ -1044,6 +2897,30 @@ White &nb For information on typical usage, see the <a href="Scenarios.html">Typical + + + + + + + + + + + + + + + + + + + + + + + + Usage Scenarios</a> page.<br> <br> <br> diff --git a/doc/colprof.html b/doc/colprof.html index de9d5c2..022f984 100644 --- a/doc/colprof.html +++ b/doc/colprof.html @@ -3,7 +3,7 @@ <head> <title>colprof</title> <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> + charset=windows-1252"> <meta name="author" content="Graeme Gill"> </head> <body> @@ -26,6 +26,18 @@ + + + + + + + + + + + + Verbose mode<br> <a href="#A">-A "manufacturer"</a> Set the manufacturer description string<br> @@ -42,6 +54,18 @@ Transparency, Matte, Negative, BlackAndWhite<br> </small></tt><tt><small> <a href="colprof.html#Zi">-Z prsa</a> + + + + + + + + + + + + Default intent: Perceptual, Rel. Colorimetric, Saturation, Abs. Colorimetric</small></tt><tt><br> @@ -51,7 +75,8 @@ <a href="#b">-b [lmhun]</a> Low quality B2A table - or specific B2A quality or none for input device<br> - <a href="#y">-y</a> + <a href="#ni">-ni</a> + @@ -63,8 +88,6 @@ - Verify A2B profile<br> - <a href="#ni">-ni</a> @@ -93,6 +116,18 @@ + + + + + + + + + + + + Don't create output (PCS) shaper curves<br> </small></tt><tt><small> <a href="#nc">-nc</a> @@ -123,6 +158,18 @@ x + + + + + + + + + + + + max K, r = ramp K<br> <a href="#kp">-k p stle stpo enpo enle shape</a><br> @@ -147,6 +194,18 @@ White + + + + + + + + + + + + - 1.0<br> @@ -171,6 +230,18 @@ Wh + + + + + + + + + + + + 0.0 - Bk 1.0<br> @@ -195,6 +266,18 @@ Wh + + + + + + + + + + + + 0.0 - Bk 1.0<br> @@ -218,6 +301,18 @@ Black + + + + + + + + + + + + 0.0 - 1.0<br> @@ -242,10 +337,34 @@ concave, + + + + + + + + + + + + 1.0-2.0 convex<br> <a href="#K">-K parameters</a> + + + + + + + + + + + + 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% @@ -277,6 +396,18 @@ cLUT + + + + + + + + + + + + x = XYZ cLUT, X = display XYZ cLUT + matrix<br> @@ -300,6 +431,18 @@ s + + + + + + + + + + + + shaper+matrix, m = matrix only,<br> @@ -324,6 +467,18 @@ S + + + + + + + + + + + + single shaper+matrix<br> <a href="#u">-u</a> @@ -333,6 +488,18 @@ 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> @@ -359,17 +526,58 @@ and + + + + + + + + + + + + primaries to be +ve</tt><tt><br> - </tt><tt> </tt><tt><small><small><a - href="file:///D:/src/argyll/doc/colprof.html#f">-f [<i>illum</i>]</a> + <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> Use Fluorescent Whitening Agent compensation [opt. simulated inst. illum.:<br> + + + + + + + + + + + + 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="file:///D:/src/argyll/doc/colprof.html#i">-i <i>illum</i></a> + </tt><tt><small><small><small><small> <a href="#i">-i <i>illum</i></a> + + + + + + + + + + + + Choose illuminant for computation of CIE XYZ from spectral data & FWA:<br> @@ -385,6 +593,18 @@ D50 (def.), 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> @@ -400,6 +620,18 @@ 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> @@ -427,6 +659,18 @@ for + + + + + + + + + + + + given source<br> <a href="#S">-S src.icc</a> @@ -440,6 +684,18 @@ for + + + + + + + + + + + + Apply gamut mapping to output profile perceptual and saturation B2A table<br> <a href="#nP">-nP</a> @@ -454,6 +710,18 @@ for + + + + + + + + + + + + Use colormetric source gamut to make output profile perceptual table<br> <a href="#nS">-nS</a> @@ -468,6 +736,18 @@ for + + + + + + + + + + + + Use colormetric source gamut to make output profile saturation table<br> <a href="#g">-g src.gam</a> @@ -490,6 +770,18 @@ for + + + + + + + + + + + + Override gamut mapping intent for output profile saturation table:<br> </small></tt><tt><small> @@ -520,6 +812,18 @@ for + + + + + + + + + + + + pa - Perceptual Appearance</small></tt><tt><br> </tt><tt> </tt><tt><small> @@ -533,12 +837,37 @@ for + + + + + + + + + + + + ms - Saturation<br> s - Enhanced Saturation [ICC Saturation]<br> al - Absolute Colorimetric (Lab)</small></tt><tt><small><br> + + + + + + + + + + + + + rl - White Point Matched Colorimetric (Lab)<br> <a href="#c">-c viewcond</a> @@ -551,6 +880,18 @@ for + + + + + + + + + + + + set input viewing conditions for output profile CIECAM02 gamut mapping,<br> @@ -565,6 +906,18 @@ for + + + + + + + + + + + + either an enumerated choice, or a parameter<br> <a href="#d">-d viewcond</a> @@ -578,6 +931,18 @@ for + + + + + + + + + + + + set output viewing conditions for output profile CIECAM02, gamut mapping<br> @@ -592,6 +957,18 @@ for + + + + + + + + + + + + either an enumerated choice, or a parameter:value change<br> @@ -605,6 +982,18 @@ for + + + + + + + + + + + + Also sets out of gamut clipping CAM space.<br> @@ -618,6 +1007,18 @@ for + + + + + + + + + + + + Enumerated Viewing Conditions:<br> </small></tt><tt><small> pp - Practical Reflection Print (ISO-3664 @@ -660,6 +1061,18 @@ for + + + + + + + + + + + + c = transparency (default average)<br> @@ -677,20 +1090,41 @@ for b:background Background % of image luminance (default 20)<br> - l:scenewhite - Scene white in cd.m^2 if surround = auto (default 250)<br> - - - f:flare Flare light % of - image luminance (default 1)<br> - - - f:X:Y:Z Flare color as XYZ - (default media white)<br> - - - f:x:y Flare - color as x, y<br> + + l:imageewhite Image white in cd.m^2 if surround = auto + (default 250)</small></tt><br> + <tt><small><small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> + + + f:flare Flare light + % of image luminance (default 0)<br> + </span></small> + </span><span style="font-family: monospace;"> + + + + + + + + + + + g:glare Glare light % of + ambient (default 1)</span><br style="font-family: + monospace;"> + <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</span></small> <br> <a href="#P">-P</a> @@ -704,6 +1138,18 @@ for + + + + + + + + + + + + Create gamut gammap_p.wrl and gammap_s.wrl diagostics<br> </small></tt><tt><small> <a href="#O">-O outputfile</a> Override @@ -718,6 +1164,18 @@ 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 @@ -824,13 +1282,6 @@ Override profiles and matrix profiles will only contain a colorimetric intent table or matrix.<br> <br> - <a name="y"></a> The <b>-y</b> flag does a verification check on - the AtoB profile. This is done by comparing what CIE colors the - profile predicts for the test chart test patches, and comparing them - to the actual values. A summary of the average and maximum Lab delta - E's will be printed out if this flag is set. If the <b>-v</b> flag - is also set, then information for each patch will also be printed.<br> - <br> <a name="ni"></a><a name="np"></a><a name="no"></a>Normally cLUT base profiles are generated with three major elements:- per device channel (shaper) input curves, the multi-dimensional lut table, and @@ -859,6 +1310,18 @@ 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 @@ -873,6 +1336,18 @@ 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 @@ -922,6 +1397,18 @@ the + + + + + + + + + + + + | _______ enle<br> @@ -936,6 +1423,18 @@ the + + + + + + + + + + + + | /<br> @@ -949,6 +1448,18 @@ the + + + + + + + + + + + + | /<br> @@ -962,6 +1473,18 @@ the + + + + + + + + + + + + | /<br> @@ -975,6 +1498,18 @@ the + + + + + + + + + + + + | /<br> stle | ------/<br> @@ -996,6 +1531,18 @@ White &nb + + + + + + + + + + + + Black<br> </tt> <br> For minimum sensitivity of printed output to the lighting spectrum, @@ -1063,8 +1610,8 @@ White &nb By default (equivalent to <b>-al</b>) profile creates a <span style="font-weight: bold;">cLUT</span> based table profile with a PCS (Profile Connection Space) of L*a*b*, which generally gives the - most accurate results, and allows for the four different rendering - intents that ICC profiles can support.<br> + most robust and accurate results, and allows for the four different + rendering intents that ICC profiles can support.<br> <br> A cLUT base table profile using a PCS of XYZ can be created if <b>-ax</b> is used, and this may have the advantage of better accuracy for @@ -1072,14 +1619,16 @@ White &nb clipping for displays with a colorant chromaticity that can't be encoded in L*a*b* PCS space, and may give a more accurate white point for input devices by avoiding clipping of values above the - white point that can occur in L*a*b* based cLUT input profiles. By - default cLUT XYZ PCS Display profiles will also have a set of dummy - matrix tags included in them, for better compatibility with other - systems. The dummy matrix deliberately interchanges Red, Green and - Blue channels, so that it is obvious if the cLUT tables are not - being used. If it is important for both the cLUT and matrix be - accurate, use <span style="font-weight: bold;">-aX</span>, which - will create shaper/matrix tags.<br> + white point that can occur in L*a*b* based cLUT input profiles. A <b>disadvantage</b> + of this type of profile is that it can be a lot less robust if given + a test patch set that is sparse, or too evenly spaced. By default + cLUT XYZ PCS Display profiles will also have a set of dummy matrix + tags included in them, for better compatibility with other systems. + The dummy matrix deliberately interchanges Red, Green and Blue + channels, so that it is obvious if the cLUT tables are not being + used. If it is important for both the cLUT and matrix be accurate, + use <span style="font-weight: bold;">-aX</span>, which will create + shaper/matrix tags.<br> <br> For RGB input or display profiles, a simpler type of profile using either a gamma curves or a general shaper curves, combined with a @@ -1159,6 +1708,25 @@ White &nb black and primary values, so as to work with these programs, but this will reduce the accuracy of the profile.<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 + lighter regions. By default this value will be a scaled down version + of the one set using the <a href="targen.html#V">targen -V</a> + parameter, and values in the range <b>1.3 - 1.6</b> are a good + place to start. Display devices used for video or film reproduction + are typically viewed in dark viewing environments with no strong + white reference, and typically employ a range of brightness levels + in different scenes. This often means that the devices dark region + response is of particular importance, so increasing the density of + cLUT grid points in the dark region may improved the balance of + accuracy of the resulting profile for video or film reproduction. + This is most valuable when used in concert with a set of test points + that more densely sample the dark regions, by use of the + corresponding targen -V parameter. Emphasizing the dark region + characterization will reduce the accuracy of modelling the + lighter regions given a certain quality/grid resolution.<br> + <br> <a name="f"></a> The <b>-f</b> flag enables Fluorescent Whitening Agent (FWA) compensation. This only works if spectral data is available and, the instrument is not UV filtered. FWA @@ -1192,6 +1760,18 @@ 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 @@ -1500,7 +2080,7 @@ White &nb profile (.icm extension on the MSWindows platform, .icc on Apple or Unix platforms). The <span style="font-weight: bold;">-O</span> parameter will override this default. - <h3>Discussion</h3> + <h3><a name="Di"></a>Discussion</h3> Note that monochrome profiling isn't currently supported. It may be supported sometime in the future.<br> <br> @@ -1512,7 +2092,7 @@ White &nb readings, average errors of 5 or less, and maximum errors of 15 or less would normally be expected. If errors are grossly higher than this, then this is an indication that something is seriously wrong - with the device testing, or profile creation.<br> + with the device measurement, or profile creation.<br> <br> Given a .ti3 file from a display device that contains calibration curves (generated by <a href="dispcal.html">dispcal</a>, passed diff --git a/doc/verify.html b/doc/colverify.html index bd4a953..3f8bc72 100644 --- a/doc/verify.html +++ b/doc/colverify.html @@ -1,13 +1,13 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> - <title>verify</title> + <title>colverify</title> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <meta name="author" content="Graeme Gill"> </head> <body> - <h2><b>profile/verify</b></h2> + <h2><b>profile/colverify</b></h2> <h3>Summary</h3> Verify a color transform by comparing CIE measurement values from two test charts. The charts can be any suitably formatted CGATS or <a @@ -16,26 +16,29 @@ worst case delta E will be reported, as well as the worst 10% and best 90% of values.<br> <h3>Usage Summary</h3> - <tt><small>verify [-options] target.ti3 measured.ti3<br> - -v - - - Verbose - print each patch value<br> + <tt><small>colverify [-options] target.ti3 measured.ti3<br> + -v + [n] + Verbose mode, n >= 2 print each value<br> -n Normalise + each files reading to white Y<br> -N Normalise + each files reading to 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> @@ -44,20 +47,23 @@ Use -w + create VRML vector visualisation (measured.wrl)<br> </small></tt><tt><small> -W - - create VRML marker & vector visualisation + + create VRML marker & vector visualisation (measured.wrl)</small></tt><tt><br> </tt><tt> </tt><tt><small> -x + Use VRML 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 @@ -65,19 +71,25 @@ Use data & FWA:<br> + 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</small><br> - <i>target.ti3</i> Target or - reference patch data file<br> + 1955_2, shaw, J&V 1978_2<br> + -L profile.icm Skip any first file out of + profile gamut patches<br> + -X file.ccmx Apply Colorimeter + Correction Matrix to second file<br> + </small> <i>target.ti3</i> + Target or reference patch data file<br> <i>measured.ti3</i> Measured or actual patch data file</small></tt><br> <h3>Usage Details and Discussion</h3> - <b> verify</b> provides a way of verifying how well a color + <b> colverify</b> provides a way of verifying how well a color transformation (such a proofing) performs.<br> <br> The <b>-v</b> flag prints out extra information during the @@ -168,6 +180,17 @@ 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> + <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 + any verification. This can be useful in evaluating the effects of a + calibration matrix on raw colorimeter values, against reference + values measured using a spectrometer.<br> + <br> If both CIE and spectral values are present in the input files, the CIE values will be used by default. Using the <span style="font-weight: bold;">-i</span>, <span style="font-weight: diff --git a/doc/dispcal.html b/doc/dispcal.html index 7327c8f..e23a8d0 100644 --- a/doc/dispcal.html +++ b/doc/dispcal.html @@ -43,6 +43,20 @@ + + + + + + + + + + + + + + Verbose mode<br> </span></font><font size="-1"><span style="font-family: monospace;"> </span><a style="font-family: monospace;" @@ -82,6 +96,20 @@ for + + + + + + + + + + + + + + VideoLUT access.</span></font><br> <font size="-1"><span style="font-family: monospace;"> <a href="#d">-d n</a> @@ -112,6 +140,20 @@ list + + + + + + + + + + + + + + 1)</span></font><br> <span style="font-family: monospace;"> <a href="#dweb">-dweb[:port]</a> @@ -132,7 +174,40 @@ list - Display via a web server at port (default 8080)</span><br + + + + + + + + + + + + + + + Display via a web server at port (default 8080)</span><br> + <span style="font-family: monospace;"> <a href="#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;"></span><span style="font-family: @@ -158,6 +233,20 @@ list + + + + + + + + + + + + + + listno</a><span style="font-family: monospace;"> Set communication port from the following list (default 1)<br> @@ -208,6 +297,20 @@ list + + + + + + + + + + + + + + Fast ICC Profile Description string (Default "outfile")<br> <a href="#u">-u</a> Update @@ -237,6 +340,20 @@ ICC + + + + + + + + + + + + + + profile VideoLUTs</span><span style="font-family: monospace;"></span><span style="font-family: monospace;"></span><br style="font-family: monospace;"> @@ -262,6 +379,20 @@ ICC + + + + + + + + + + + + + + Quality - Low, Medium (def), High<br> <a href="#p">-p</a> @@ -272,6 +403,20 @@ 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> @@ -295,6 +440,20 @@ ICC + + + + + + + + + + + + + + Display type - instrument specific list to choose from.</span></font><font size="-1"><span style="font-family: monospace;"><br style="font-family: monospace;"> @@ -328,6 +487,20 @@ in + + + + + + + + + + + + + + deg. K (deflt.)<br> </span></font><font size="-1"><span style="font-family: monospace;"> </span><a style="font-family: monospace;" @@ -359,6 +532,20 @@ 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 @@ -383,6 +570,20 @@ temperaturee + + + + + + + + + + + + + + Set the target white point as chromaticity coordinates</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -407,6 +608,20 @@ temperaturee + + + + + + + + + + + + + + Set the target white brightness in cd/m^2</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -431,6 +646,20 @@ temperaturee + + + + + + + + + + + + + + Set the target response curve gamma (Def. 2.4)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -453,6 +682,20 @@ temperaturee + + + + + + + + + + + + + + Use "-gl" for L*a*b* curve</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -475,6 +718,20 @@ temperaturee + + + + + + + + + + + + + + Use "-gs" for sRGB curve<br> Use @@ -504,6 +761,20 @@ use + + + + + + + + + + + + + + -a as well!)<br> @@ -525,6 +796,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> <font size="-1"><span style="font-family: monospace;"> @@ -547,6 +832,20 @@ use + + + + + + + + + + + + + + Use "-G2.4 -f0" for BT.1886</span></font> @@ -560,6 +859,20 @@ use + + + + + + + + + + + + + + <br> <font size="-1"><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#G">-G gamma</a><span @@ -594,6 +907,20 @@ output + + + + + + + + + + + + + + offset (default all output offset)<br> <a href="#a">-a ambient</a> @@ -615,6 +942,20 @@ 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> @@ -647,6 +988,20 @@ 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 @@ -672,10 +1027,25 @@ 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="#E">-E</a><span style="font-family: monospace;"> + href="#z">-<font size="-1">z</font></a><span style="font-family: + monospace;"> @@ -696,6 +1066,20 @@ 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 @@ -730,6 +1114,20 @@ center, + + + + + + + + + + + + + + = right/bottom etc.</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> ss: @@ -759,6 +1157,20 @@ normal, + + + + + + + + + + + + + + = double etc.<br> </span></font><font size="-1"><span style="font-family: monospace;"> @@ -768,6 +1180,20 @@ normal, + + + + + + + + + + + + + + ss,vs: = optional horizontal, vertical scale.</span></font><br> <font size="-1"><span style="font-family: monospace;"> <a href="#F">-F</a> @@ -791,8 +1217,39 @@ normal, + + + + + + + + + + + + + + Fill whole screen with black background</span></font><font - size="-1"><span style="font-family: monospace;"></span></font><br + 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> + + + + + + + + + + + + + + </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 @@ -825,6 +1282,20 @@ on + + + + + + + + + + + + + + test window<br> </span></font><font size="-1"><span style="font-family: monospace;"> </span><a style="font-family: monospace;" @@ -852,6 +1323,20 @@ 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 @@ -883,6 +1368,20 @@ on + + + + + + + + + + + + + + Apply Colorimeter Correction Matrix</span></font><br> <span style="font-family: monospace;"> <a href="#X2">-X file.ccss</a> @@ -908,6 +1407,20 @@ 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 @@ -935,6 +1448,20 @@ 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, @@ -959,14 +1486,42 @@ Calibration - Drift compensation, Black: -Ib, White: -Iw, Both: -Ibw<br> - </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 + + + + + + + + + + + + + + + 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 @@ -1009,6 +1564,20 @@ 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 @@ -1034,6 +1603,20 @@ none, + + + + + + + + + + + + + + Print debug diagnostics to stderr</span></font><br style="font-family: monospace;"> <font size="-1"><span style="font-family: monospace;"></span><span @@ -1059,6 +1642,20 @@ 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 @@ -1079,7 +1676,9 @@ none, <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.<br> + 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 @@ -1149,6 +1748,20 @@ 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 @@ -1183,6 +1796,16 @@ none, 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> @@ -1198,9 +1821,11 @@ none, 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. If <span style="font-weight: bold;">-R</span> - is use, then the uncalibrated ("raw" or "native") behaviour is - measured. Reported are: <br> + 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> @@ -1339,10 +1964,9 @@ 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="file:///D:/src/argyll/doc/ccxxmake.html">ccxxmake</a>, - and installed using <a - href="file:///D:/src/argyll/doc/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="t"></a><span style="text-decoration: underline;"></span> <span style="font-weight: bold;">-t</span> Set the target white point @@ -1410,6 +2034,20 @@ 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 @@ -1438,6 +2076,20 @@ 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>) @@ -1517,6 +2169,20 @@ 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 @@ -1606,7 +2272,8 @@ As 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).<br> + 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 @@ -1629,6 +2296,20 @@ 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 @@ -1668,7 +2349,7 @@ If ascertained. The verification uses a fixed number of semi-random test values to test the calibration.<br> <br> - <a name="E"></a><span style="font-weight: bold;">-E</span> Run + <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 @@ -1677,7 +2358,7 @@ If 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;">-E</span>. + 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 @@ -1710,6 +2391,16 @@ If 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 @@ -1789,6 +2480,20 @@ a + + + + + + + + + + + + + + colorimeters accuracy for a particular type of display.<br> <br> <a name="Q"></a> The <b>-Q</b> flag allows specifying a tristimulus @@ -1832,6 +2537,12 @@ a 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 @@ -1841,6 +2552,13 @@ a 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 diff --git a/doc/dispprofloc.html b/doc/dispprofloc.html index b583914..668ed16 100644 --- a/doc/dispprofloc.html +++ b/doc/dispprofloc.html @@ -11,195 +11,143 @@ </h2> <br> Installing a display profile for your monitor is very operating - system - dependent, which is why <a href="dispwin.html#I">dispin -I</a> is a - good way of taking care of all these details. On some systems it is - not - the operating system itself that - supports display profiles, but individual applications, or helper - programs.<br> + system dependent, which is why <a href="dispwin.html#I">dispin -I</a> + is a good way of taking care of all these details. On some systems + it is not the operating system itself that supports display + profiles, but individual applications, or helper programs.<br> <br> Please choose from the detailed instructions below that suite your system:<br> <br> - <span style="font-weight: bold;"><a href="#MSW">Microsoft - Windows</a><br> + <span style="font-weight: bold;"><a href="#MSW">Microsoft Windows</a><br> <a href="#OSX">Apple OS X</a><br> <a href="#Linux">Linux/UNIX X11</a></span><br> <br> <hr style="width: 100%; height: 2px;"><a name="MSW"></a>On <span style="font-weight: bold;">Microsoft Windows</span>, display - profiles are typically in one of the - following directories:<br> + profiles are typically in one of the following directories:<br> <p> MS Windows Me and 98: C:\Windows\System\Color<br> </p> <p> MS Windows NT: - C:\Winnt\system32\spool\drivers\color - </p> + C:\Winnt\system32\spool\drivers\color </p> <p> MS Window 2000, XP, Vista and 7: C:\Windows\system32\spool\drivers\color</p> <p>An alternative to using <span style="font-weight: bold;">dispwin - -I</span> - to install your display profiles, - is to use the Display - Property dialog, advanced settings, Color management tab, and - locate - the profile and install it there. This in - itself does not cause the profile to be made use of anywhere in - your - system.<br> + -I</span> to install your display profiles, is to use the + Display Property dialog, advanced settings, Color management tab, + and locate the profile and install it there. This in itself does + not cause the profile to be made use of anywhere in your system.<br> </p> <p>If you are using Adobe Photoshop on your system, then you can - tell - it to use your monitor profile by editing the appropriate registry - key, - typically "My + tell it to use your monitor profile by editing the appropriate + registry key, typically "My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Color\Monitor\Monitor0", - to - contain the name of the display profile, and then restart - Photoshop - This is the simplest way of ensuring that the Adobe calibration - loader - tool Adobe Gamma loads the video hardware lookup tables from the - vcgt tag, and - uses the profile as its display profile.<br> + to contain the name of the display profile, and then restart + Photoshop This is the simplest way of ensuring that the Adobe + calibration loader tool Adobe Gamma loads the video hardware + lookup tables from the vcgt tag, and uses the profile as its + display profile.<br> </p> <p>The adobe gamma tool can be told to use your profile, but the procedure is slightly tricky: Open adobe gamma from photoshop (in - the - Help->Color Management... menu item), select "Open Adobe - Gamma", and - select the "Load.." button. Select your profile and "Open". Select - "OK" - in the Adobe Gamma, it will then ask you to save it's modified - version - of your profile under a different name. Chose a name for the - modified - profile, and save it. Exit from Photoshop. Copy the profile you - want to - use, over the modified profile that you saved in Adobe Gamma. (If - you - don't do the last step, the profile Photoshop will be using will - have - been modified in strange ways from what you intended.)<br> + the Help->Color Management... menu item), select "Open Adobe + Gamma", and select the "Load.." button. Select your profile and + "Open". Select "OK" in the Adobe Gamma, it will then ask you to + save it's modified version of your profile under a different name. + Chose a name for the modified profile, and save it. Exit from + Photoshop. Copy the profile you want to use, over the modified + profile that you saved in Adobe Gamma. (If you don't do the last + step, the profile Photoshop will be using will have been modified + in strange ways from what you intended.)<br> </p> <p>Installing a profile on Microsoft Windows generally doesn't mean that the profiles calibration will be automatically loaded into a - display on startup. A separated tool is usually needed to achiev + display on startup. A separated tool is usually needed to achieve this.<br> </p> <p>Some Microsoft Windows applications may come with - "Gamma/VCGT/RAMDAC/Video LUT" - loader tools, consult their documentation and check your Start - Menu - Startup folders. If you don't want to use any of these 3rd party - tools, you can also use the <a - href="file:///D:/src/argyll/doc/dispwin.html">dispwin</a> + "Gamma/VCGT/RAMDAC/Video LUT" loader tools, so consult their + documentation and check your Start Menu Startup folders. If you + don't want to use any of these 3rd party tools, you can also use + the <a href="dispwin.html">dispwin</a> tool to do this for you, as it takes either a <a - href="file:///D:/src/argyll/doc/cal_format.html">.cal</a> or ICC - file - as an argument. The <a - href="http://freshmeat.net/projects/xcalib/">xcalib</a> - tool could also be used.<br> + href="cal_format.html">.cal</a> or ICC + file as an argument. The <a + href="http://freshmeat.net/projects/xcalib/">xcalib</a> tool + could also be used.<br> </p> <p>To add a startup item that will load a profiles calibration into - the - display using <span style="font-weight: bold;">dispwin</span>, - use the - following - instructions:<br> + the display using <span style="font-weight: bold;">dispwin</span>, + use the following instructions:<br> </p> <p style="margin-left: 40px;">On the task bar, right click and - select - "Properties", then select the "Advanced" tab, then click "Add..". - then - browse till you locate dispwin.exe. In the box containing the path - to - <span style="font-weight: bold;">dispwin.exe</span>, add a space - then - the option <span style="font-weight: bold;">-L</span>, eg:<br> + select "Properties", then select the "Advanced" tab, then click + "Add..". then browse till you locate dispwin.exe. In the box + containing the path to <span style="font-weight: bold;">dispwin.exe</span>, + add a space then the option <span style="font-weight: bold;">-L</span>, + eg:<br> </p> <p style="margin-left: 40px;"> <span style="font-weight: bold;">c:\bin\argyll\dispwin -L</span></p> <p style="margin-left: 40px;">If you don't want to use the default installed profile, you could explicitly set the calibration file - to use - as an argument:</p> + to use as an argument:</p> <p style="margin-left: 40px;"> <span style="font-weight: bold;">c:\bin\argyll\dispwin c:\myprofiles\mydisplay.icm<br> </span></p> <p style="margin-left: 40px;">Click "Next >", select the - "Startup" - folder, then name the item (ie. - "Argyll Calibration Loader"), then press "Finish".<br> + "Startup" folder, then name the item (ie. "Argyll Calibration + Loader"), then press "Finish".<br> <br> You can test it out by simply navigating the "Start" menu to the "Startup" folder and selecting the item you've just created. If - you - want to alter any of the details, navigate to the item again and - right - click it, and select "Properties". More than one startup item can - be - created to set the calibration for more than one display. You may - want - to cut and paste the "Target" line to a normal Command Prompt - shell to - check that it works as expected, as it is impossible to catch - error - messages in the startup.<br> + you want to alter any of the details, navigate to the item again + and right click it, and select "Properties". More than one startup + item can be created to set the calibration for more than one + display. You may want to cut and paste the "Target" line to a + normal Command Prompt shell to check that it works as expected, as + it is impossible to catch error messages in the startup.<br> </p> Microsoft Windows <span style="font-weight: bold;">XP</span> has an optional <span style="font-weight: bold;">Microsoft Color Control Panel Applet for Windows XP</span> - available for - download from - Microsoft, which handles installation and registering of the a - display - profile, and will also automatically set the display calibration on - system startup. The applet is started from the control panel, and - first - you have to "Install..." the profile in the <span - style="font-weight: bold;">Profiles</span> tab, then associate it - with - the display in the <span style="font-weight: bold;">Devices</span> - tab, but <span style="font-weight: bold;">NOTE</span> that it seems - to - have a <span style="font-weight: bold;">bug</span>, in that it - sometimes associates the profiles with the <span - style="font-weight: bold;">wrong monitor</span> entry!<br> - <br> - On - Microsoft <span style="font-weight: bold;">Vista</span> you can set - the display profile in + available for download from Microsoft, which handles installation + and registering of the a display profile, and will also + automatically set the display calibration on system startup. The + applet is started from the control panel, and first you have to + "Install..." the profile in the <span style="font-weight: bold;">Profiles</span> + tab, then associate it with the display in the <span + style="font-weight: bold;">Devices</span> tab, but <span + style="font-weight: bold;">NOTE</span> that it seems to have a <span + style="font-weight: bold;">bug</span>, in that it sometimes + associates the profiles with the <span style="font-weight: bold;">wrong + monitor</span> entry!<br> + <br> + On Microsoft <span style="font-weight: bold;">Vista</span> you can + set the display profile in Control Panel -> Hardware and Sound -> Color Management, as an alternative to <span style="font-weight: bold;">dispwin -I</span>. In Devices you select "Use my settings for this device", and then add the profile you've created. Unfortunately - though, it doesn't use the 'vcgt' - calibration curves on system startup, so a tool such as <span - style="font-weight: bold;">dispwin</span> will still have to be - used - to do this. Note that currently Vista also has a <span - style="font-weight: bold;">bug</span> that causes the calibration - curves to be reset whenever the User Account Dialog (and similar) is - displayed. This problem can only be worked around manually, by - re-running the startup item whenever this happens. Note that due to - the - details of this bug it is necessary to actually reset the - calibration - to something else before re-setting it. This can be done quite - conveniently in dispwin by adding the <span style="font-weight: - bold;">-c</span> - flag: e.g.: <span style="font-weight: bold;">c:\bin\argyll\dispwin - -c - -L</span><br> - <br> - On - Microsoft <span style="font-weight: bold;">Windows 7</span> you can - set - the display profile by opening the <span class="phrase">Color + + though, it doesn't use the 'vcgt' calibration curves on system + startup, so a tool such as <span style="font-weight: bold;">dispwin</span> + will still have to be used to do this. Note that currently Vista + also has a <span style="font-weight: bold;">bug</span> that causes + the calibration curves to be reset whenever the User Account Dialog + (and similar) is displayed. This problem can only be worked around + manually, by re-running the startup item whenever this happens. Note + that due to the details of this bug it is necessary to actually + reset the calibration to something else before re-setting it. This + can be done quite conveniently in dispwin by adding the <span + style="font-weight: bold;">-c</span> flag: e.g.: <span + style="font-weight: bold;">c:\bin\argyll\dispwin -c -L</span><br> + <br> + On Microsoft <span style="font-weight: bold;">Windows 7 & 8</span> + you can set the display profile by opening the <span class="phrase">Color + Management control by clicking the <span class="ui">Start</span> button and then clicking <span class="ui">Control Panel</span>. In the search box, type <span class="userInput">color management</span>, @@ -213,25 +161,25 @@ Unfortunately profile has been marked "(default)" if you want it to be automatically used for your display.<br> <br> - By default Windows 7 seems to automatically load the default display - profiles calibration on startup, but needs to be told to do this at - all other times by changing the system defaults, or if some 3rd - party tool to load display calibration has been installed. This can - be done by logging on with a user account that has administrative - privileges, then opening the <span class="phrase">Color Management - (see above), and then select the "</span><span class="ui">Advanced</span>" - tab, and then "<span class="ui">Change system defaults...", then - select the </span><span class="phrase">"</span><span class="ui">Advanced</span>" - tab, and select/un-select the "<span class="ui">Use <span - class="notLocalizable">Windows</span> display calibration</span>" - check box. (You could use <span style="font-weight: bold;">dispwin - -I</span> as an alternative to this if you really wanted.)<br> + By default Windows 7 & 8 seems to automatically load the default + display profiles calibration on startup, but needs to be told to do + this at all other times by changing the system defaults, or if some + 3rd party tool to load display calibration has been installed. This + can be done by logging on with a user account that has + administrative privileges, then opening the <span class="phrase">Color + Management (see above), and then select the "</span><span + class="ui">Advanced</span>" tab, and then "<span class="ui">Change + system defaults...", then select the </span><span class="phrase">"</span><span + class="ui">Advanced</span>" tab, and select/un-select the "<span + class="ui">Use <span class="notLocalizable">Windows</span> + display calibration</span>" check box. (You could use <span + style="font-weight: bold;">dispwin -I</span> as an alternative to + this if you really wanted.)<br> <br> <br> <hr style="width: 100%; height: 2px;"><a name="OSX"></a>On <span - style="font-weight: bold;">Apple OSX</span>, the display - profile are in one of the following - locations:<br> + style="font-weight: bold;">Apple OSX</span>, the display profile + are in one of the following locations:<br> <br> /Network/Library/ColorSync/Profiles<br> /System/Library/Colorsync/Profiles<br> @@ -239,25 +187,22 @@ Unfortunately ~/Library/ColorSync/Profiles<br> <br> Note though that /System/Library/Colorsync/Profiles is only - for - profiles supplied by Apple. You can use <a href="dispwin.html#S">dispwin - -S</a> to select the appropriate scope when installing a - profile - using <a href="dispwin.html#I">dispwin -I</a>. You can use the - "System + for profiles supplied by Apple. You can use <a + href="dispwin.html#S">dispwin -S</a> to select the + appropriate scope when installing a profile using <a + href="dispwin.html#I">dispwin -I</a>. You can use the "System Preferences->Displays->Color" tool to check that the profile - has been installed correctly. Note that the contents of - the description tag (the argument to the <span style="font-weight: - bold;"><span style="font-weight: bold;">-D</span></span> - flag used with the <span style="font-weight: bold;">colprof</span> - tool) will be used to identify the profile.<br> + has been installed correctly. Note that the contents of the + description tag (the argument to the <span style="font-weight: + bold;"><span style="font-weight: bold;">-D</span></span> flag used + with the <span style="font-weight: bold;">colprof</span> tool) will + be used to identify the profile.<br> <br> <hr style="width: 100%; height: 2px;"><a name="Linux"></a>On <span style="font-weight: bold;">Linux</span> and other <span style="font-weight: bold;">Unix</span> style systems, there is no - universally agreed location for ICC profiles yet, - although the following locations have been suggested at various - times:<br> + universally agreed location for ICC profiles yet, although the + following locations have been suggested at various times:<br> <br> /usr/share/color/icc<br> /usr/local/share/color/icc<br> @@ -270,18 +215,16 @@ Unfortunately <br> Argyll <a href="dispwin.html">dispwin</a> follows uses the <a href="ucmm.html">ucmm</a> scheme for storing user and system - display - profiles, and when a display is set to use a profile correctly, it - will - follow <a + display profiles, and when a display is set to use a profile + correctly, it will follow <a href="http://www.burtonini.com/computing/x-icc-profiles-spec-0.2.html">this + convention</a> to make it available to applications.<br> <br> If you want the display calibration to be loaded, you should - consider - installing a tool to do so at startup, such as <a - href="file:///D:/src/argyll/doc/dispwin.html">dispwin</a> - or <a href="http://freshmeat.net/projects/xcalib/">xcalib</a>.<br> + consider installing a tool to do so at startup, such as <a + href="dispwin.html">dispwin</a> or <a + href="http://freshmeat.net/projects/xcalib/">xcalib</a>.<br> <br> Using <a href="dispwin.html">dispwin</a> the currently installed profile for a particular display can be loaded using the <a @@ -292,21 +235,17 @@ Unfortunately <br> </span>which will both upload the installed profile <span style="font-style: italic;"></span>into the <span - style="font-weight: bold;"></span>root - window _ICC_PROFILE property, and also load it into the display - VideoLUTs. <br> + style="font-weight: bold;"></span>root window _ICC_PROFILE + property, and also load it into the display VideoLUTs. <br> <br> You can use the <span style="font-weight: bold;">dispwin</span> <a - href="file:///D:/src/argyll/doc/dispwin.html#d">-d</a> parameter - in - the usual way to select other - displays to store or load the calibration using the _ICC_PROFILE - property.<br> + href="dispwin.html#d">-d</a> parameter + in the usual way to select other displays to store or load the + calibration using the _ICC_PROFILE property.<br> <br> To do this when you start your X11 server, you could put the above command in your <span style="font-weight: bold;">.xinitrc</span> - file - in your home directory for each screen.<br> + file in your home directory for each screen.<br> <br> <br> </body> diff --git a/doc/dispread.html b/doc/dispread.html index e1ce861..071fa7d 100644 --- a/doc/dispread.html +++ b/doc/dispread.html @@ -34,6 +34,15 @@ + + + + + + + + + Verbose mode<br> </small><font size="-1"><a style="font-family: monospace;" href="#display">-display displayname</a><span @@ -65,6 +74,15 @@ m + + + + + + + + + for VideoLUT access.</span></font><br> <font size="-1"><span style="font-family: monospace;"> <a href="#d">-d n</a> @@ -88,6 +106,15 @@ list + + + + + + + + + (default 1)</span></font><small style="font-family: monospace;"><br> </small><span style="font-family: monospace;"> <a href="#dweb">-dweb[:port]</a> @@ -105,7 +132,30 @@ list + + + + + + + + + Display via a web server at port (default 8080)</span><br> + <span style="font-family: monospace;"> <a href="#dmadvr">-dmadvr</a> + + + + + + + + + + + + + [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;"> @@ -126,6 +176,15 @@ 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> @@ -145,6 +204,15 @@ 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 @@ -162,6 +230,15 @@ 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 @@ -180,7 +257,21 @@ Apply + + + + + + + + + calibration file to test values while reading</small><br> + <tt> <a href="#V">-V</a> + + + + [MSWin] Enable MadVR color management (3dLut)</tt><br> <small style="font-family: monospace;"> <a href="#s">-s</a> @@ -195,6 +286,15 @@ Apply + + + + + + + + + Save spectral information (default don't save)<br> </small><font style="font-family: monospace;" size="-1"> <a @@ -221,6 +321,15 @@ center, + + + + + + + + + 1.0 = right/bottom etc.<br> ss: @@ -243,6 +352,15 @@ normal, + + + + + + + + + 2.0 = double etc.<br> </font><font size="-1"><span style="font-family: monospace;"> @@ -251,6 +369,15 @@ 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> @@ -268,7 +395,28 @@ normal, - Fill whole screen with black background</span></font><br + + + + + + + + + + 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> + + + + + + + + + </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 style="text-decoration: underline;"></span><a href="#n">-n</a> @@ -292,6 +440,15 @@ redirect + + + + + + + + + on test window<br> </small><small style="font-family: monospace;"> <a href="#J">-J</a> @@ -308,6 +465,15 @@ redirect + + + + + + + + + Run calibration first</small><br> <font size="-1"><span style="font-family: monospace;"> <a href="#N">-N</a> @@ -324,6 +490,15 @@ 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;" @@ -355,6 +530,15 @@ Y + + + + + + + + + 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> @@ -371,6 +555,15 @@ Y + + + + + + + + + Apply Colorimeter Correction Matrix</span></font><br> <span style="font-family: monospace;"> <a href="#X2">-X file.ccss</a> @@ -390,6 +583,15 @@ 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 @@ -411,6 +613,15 @@ 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, @@ -437,18 +648,46 @@ Both: - -Ibw<br> - </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 + + + + + + + + + + -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> + <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 @@ -480,6 +719,15 @@ n + + + + + + + + + none, h = HW, x = Xon/Xoff</span></font><br> <small style="font-family: monospace;"> <a href="#D">-D [level]</a> Print debug @@ -498,6 +746,15 @@ 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> @@ -578,6 +835,15 @@ 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 @@ -600,9 +866,9 @@ n 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> + 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 @@ -613,6 +879,17 @@ n 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> @@ -650,9 +927,9 @@ n 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="file:///D:/src/argyll/doc/ccxxmake.html">ccxxmake</a>, + using <a href="ccxxmake.html">ccxxmake</a>, and installed using <a - href="file:///D:/src/argyll/doc/oeminst.html">oeminst</a>. The + 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 @@ -664,7 +941,7 @@ n <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;">ViedoLUTs</span> + 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> @@ -672,14 +949,20 @@ n 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 a calibration file is not - created, then the display will be read in whatever calibration state - it is in. 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). <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> + 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 @@ -691,7 +974,18 @@ n 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.<br> + 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 @@ -720,6 +1014,12 @@ n 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 @@ -795,6 +1095,15 @@ a + + + + + + + + + colorimeters accuracy for a particular type of display.<br> <br> <a name="Q"></a> The <b>-Q</b> flag allows specifying a tristimulus @@ -835,9 +1144,14 @@ a 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;"> <br> - <br> + 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 @@ -846,7 +1160,14 @@ a 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> - <span style="font-weight: bold;"> <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 diff --git a/doc/dispwin.html b/doc/dispwin.html index a07d50f..f1d75f5 100644 --- a/doc/dispwin.html +++ b/doc/dispwin.html @@ -43,6 +43,10 @@ Verbose + + + + mode<br> </span></font><font size="-1"><span style="font-family: monospace;"> </span><a style="font-family: monospace;" @@ -64,6 +68,10 @@ optionally + + + + 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> @@ -76,6 +84,10 @@ X11] + + + + Choose the display from the following list (default 1)<br> </span></font><span style="font-family: monospace;"> <a href="#dweb">-dweb[:port]</a> @@ -84,7 +96,15 @@ X11] - Display via a web server at port (default 8080)</span><br + + + + + 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 @@ -100,6 +120,10 @@ ho,vi: + + + + = left/top, 0.5 = center, 1.0 = right/bottom etc.</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -112,11 +136,19 @@ ss: + + + + = half, 1.0 = normal, 2.0 = double etc.<br> + + + + ss,vs: = optional horizontal, vertical scale.<br> </span></font><font size="-1"><span style="font-family: monospace;"><a href="#F">-F</a> @@ -130,7 +162,18 @@ whole - screen with black background</span></font><br + + + + + 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 @@ -157,6 +200,10 @@ just + + + + video LUT loading & Beeps<br> </span></font><font size="-1"><span style="font-family: monospace;"> <a href="#n">-n</a> @@ -170,7 +217,11 @@ native - display values (rather than through Video LUT)<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 @@ -181,6 +232,10 @@ the + + + + currently loaded Video LUT to 'filename'<br> </span></font><font size="-1"><span style="font-family: monospace;"> <a href="#c">-c</a> @@ -194,6 +249,10 @@ 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: @@ -208,6 +267,10 @@ 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> @@ -219,6 +282,10 @@ 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: @@ -231,6 +298,10 @@ that + + + + </span></font><font size="-1"><span style="font-family: monospace;">Un-install profile for display<br> <a href="#S">-S d</a> @@ -243,6 +314,10 @@ the + + + + install/uninstall scope for OS X [nlu] or Vista [lu]<br> d @@ -254,6 +329,10 @@ 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 @@ -266,10 +345,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="#E">-E</a> + monospace;"> <a href="#X">-<font size="-1">X</font></a> @@ -278,6 +361,10 @@ 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: @@ -292,6 +379,10 @@ 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: @@ -309,6 +400,10 @@ 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> @@ -372,6 +467,10 @@ 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 @@ -406,6 +505,16 @@ the 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 @@ -433,6 +542,12 @@ the 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 @@ -463,7 +578,9 @@ the 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.<br> + 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 @@ -507,7 +624,9 @@ the 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).<br> + <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 @@ -539,7 +658,7 @@ the display on system startup from the installed display profile, if the system doesn't not do this automatically .<br> <br> - <a name="E"></a> <span style="font-weight: bold;">-E</span>: Daemon + <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 diff --git a/doc/fakeread.html b/doc/fakeread.html index aa2847c..2a7b5c0 100644 --- a/doc/fakeread.html +++ b/doc/fakeread.html @@ -1,248 +1,372 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> -<head> - <title>fakeread</title> - <meta http-equiv="content-type" - content="text/html; charset=ISO-8859-1"> - <meta name="author" content="Graeme Gill"> -</head> -<body> -<h2><b>spectro/fakeread</b></h2> -<h3>Summary</h3> -Simulate the measurement of a devices response, using an existing -device profile, or measured test point data set. The device profile can -be either -an <a href="File_Formats.html#ICC">ICC</a> or <a - href="File_Formats.html#MPP">MPP</a> profile, or the data set can be a -<a href="File_Formats.html#.ti3">.ti3</a> file. A device link -separation or color space conversion can be applied before the -print/measure simulation.<br> -<h3>Usage</h3> -<small><span style="font-family: monospace;">fakeread [-v] [-s] </span></small><small><span - style="font-family: monospace;">[<span style="font-style: italic;">separation.ic<span - style="font-family: monospace;">m</span></span>] </span></small><small><span - 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><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> -v + <head> + <title>fakeread</title> + <meta http-equiv="content-type" content="text/html; + charset=ISO-8859-1"> + <meta name="author" content="Graeme Gill"> + </head> + <body> + <h2><b>spectro/fakeread</b></h2> + <h3>Summary</h3> + Simulate the measurement of a devices response, using an existing + device profile, or measured test point data set. The device profile + can be either an <a href="File_Formats.html#ICC">ICC</a> or <a + href="File_Formats.html#MPP">MPP</a> profile, or the data set can + be a <a href="File_Formats.html#.ti3">.ti3</a> file. A device link + separation or color space conversion can be applied before the + print/measure simulation, as well as device calibration or + inverse calibration curves.<br> + <br> + <b>fakeread</b> can be useful for creating a data set from an + existing profile to re-create a different style of profile (i.e. + create a cLUT profile from a matrix profile), for creating synthetic + data sets with known amounts of randomness for testing profile + creation against a perfectly known ideal, or for creating + verification test sets for checking colorimetric colorspace + emulation against.<br> + <br> + The options below are in the order of color processing that fakeread + performs.<br> + <h3>Usage</h3> + <small><span style="font-family: monospace;">fakeread [-options] </span></small><small><span + style="font-family: monospace;"></span></small><small><span + 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 + [n] + Verbose mode [level]<br> + -e + flag + 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 + profile on input<br> + -E + flag + Video decode separation device output. See -e above<br> + -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> + -K <i>file.cal</i> + Apply inverse calibration<br> + -r + level Add + average random deviation of <level>% to device values + (after sep. & cal.)<br> + -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> + -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> + <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 + seed + Set random seed<br> + </span><span style="font-family: monospace;"> </span><i + style="font-family: monospace;">profile.</i><span + style="font-family: monospace;">[icm|mpp|ti3] </span><a + style="font-family: monospace;" href="File_Formats.html#ICC">ICC</a><span + style="font-family: monospace;">, </span><a style="font-family: + monospace;" href="File_Formats.html#MPP">MPP</a><span + style="font-family: monospace;"> or </span><a + style="font-family: monospace;" href="File_Formats.html#.ti3">.ti3</a><span + style="font-family: monospace;"> profile/file to use</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"></span><i + style="font-family: monospace;">inoutfile</i><span + style="font-family: monospace;"> - Verbose mode</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> -s - Lookup </span><a style="font-family: monospace;" - href="File_Formats.html#MPP">MPP</a><span - style="font-family: monospace;"> spectral values</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> -p -Use -separation profile</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> -l -Output -Lab rather than XYZ<br> - -k -file.cal -Apply -calibration (after sep.) and include in .ti3<br> - -i -file.cal -Include -calibration in .ti3 (but don't apply it)<br> -</span></small><small><span style="font-family: monospace;"> -r -level -Add -average random deviation of <level>% to input device values -(after sep. & cal.)</span></small><br - style="font-family: monospace;"> -<small><span style="font-family: monospace;"></span><span - style="font-family: monospace;"> -0 -pow -Apply -power to input device chanel 0-9 (after sep. cal. & rand.)</span><br - style="font-family: monospace;"> - -<span style="font-family: monospace;">-R -level -Add -average random deviation of <level>% to output PCS values<br> -</span></small><small><span style="font-family: monospace;"> -u - - -Make -random deviations have uniform distributions rather than normal<br> - -S -seed -Set -random seed<br style="font-family: monospace;"> -</span></small><small><span style="font-family: monospace;"></span><span - style="font-family: monospace;"> -b -L,a,b -Scale -black point to target Lab value<br> - -I -intent -r = relative colorimetric, a = absolute (default)<br - style="font-family: monospace;"> -</span><span style="font-family: monospace;"> [<span - style="font-style: italic;">separation.ic<span - style="font-family: monospace;">m</span></span>] -Device -link separation profile</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><i - style="font-family: monospace;">profile.</i><span - style="font-family: monospace;">[icm|mpp|ti3] </span><a - style="font-family: monospace;" href="File_Formats.html#ICC">ICC</a><span - style="font-family: monospace;">, </span><a - style="font-family: monospace;" href="File_Formats.html#MPP">MPP</a><span - style="font-family: monospace;"> -or </span><a style="font-family: monospace;" - href="File_Formats.html#.ti3">.ti3</a><span - style="font-family: monospace;"> -profile/file to use</span><br style="font-family: monospace;"> - -<span style="font-family: monospace;"></span><i - style="font-family: monospace;">inoutfile</i><span - style="font-family: monospace;"> - - 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 - style="font-family: monospace;" href="File_Formats.html#.ti3">.ti3</a><span - style="font-family: monospace;">] file</span></small><br> -<b><br> -Examples</b><br> -<br> -fakeread profile.icm testvalues<br> -fakeread -p separation.icm profile.icm testvalues<br> -<h3>Comments<br> -</h3> -The <span style="font-weight: bold;">-v</span> flag does nothing at -the moment.<br> -The <span style="font-weight: bold;">-s</span> flag works only with -MPP profiles that contain spectral model -information.<br> -The <span style="font-weight: bold;">-p</span> flag enables a device -to device value conversion before -converting to expected PCS values.<br> -The <span style="font-weight: bold;">-l</span> flag causes the CIE -output values to be L*a*b* rather than the -default XYZ values.<br> -<br> -The <b>-k file.cal</b> parameter specifies a printer -calibration file created by <a href="printcal.html">printcal</a>, and -the supplied calibration curves will be applied to the chart device -values after any separation. This allows emulating a system that uses -per device channel calibration. The calibration curves will also be -included in -the resulting .ti3 file, so that they can be passed through to the ICC -profile allowing accurate 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>, -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 calibration curves, that these will -be included in the resulting .ti3 by default.<br> -<span style="font-weight: bold;"></span><br> -The <span style="font-weight: bold;">-r</span> parameter is a way of -simulating instability in the behaviour of -the simulated -printing system. The parameter supplied to the flag will be used to -scale a random offset added to the device values (after any separation -and calibration is applied). The offset will be a normally distributed -error with an -average deviation of level%. A typically value supplied -might be 1.0 to simulate 1% randomness.<br> -<br> -The <span style="font-weight: bold;">-0, -1, -2 .. -9</span> -parameters are a way of simulating changes in the -behaviour of the simulated printing system. The parameter supplied to -the flag will be used to modify the device values (after any -separation, calibration and device randomness -is applied) by raising them to the power of the parameter. This applies -a transfer curve to the simulated device response.<br> -<br> -The <span style="font-weight: bold;">-R</span> parameter is a way of -simulating instability in the behaviour of -the simulated -measuring system. The parameter supplied to the flag will be used to -scale a random offset added to the PCS values. The offset will be a -normally distributed error with an average deviation of level%. A -typically value supplied -might be 1.0 to simulate 1% randomness. <br> -<br> -The <span style="font-weight: bold;">-u</span> flag changes the -distribution of the random offsets applied using the <span - style="font-weight: bold;">-r</span> or <span - style="font-weight: bold;">-R</span> flags, from the default standard -deviation, to a uniform deviation distribution. The level is still -specified as an average deviation.<br> -<br> -The <span style="font-weight: bold;">-S</span> parameter lets a -particular random seed be used when generating random offsets, so that -the randomness can be made repeatable. Normally a different seed will -be used for each run. <br> -<br> -The <span style="font-weight: bold;">-b</span> parameter is a way of -simulating devices that have a different black point to the profile -used. This only works if an ICC profile is used, and scales the black -point to the parameter value. This will be done in XYZ space by -default, and in L*a*b* space if the <span style="font-weight: bold;">-l</span> -flag is used.<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 intend -to make a profile from the resulting .ti3 file, since profiles are -always made from absolute colorimetric measurement values. Note that -this flag does nothing if the profile is an MPP or .ti3 file.<br> -<br> -Fakeread is useful in creating artificial test value for testing <a - href="colprof.html">colprof</a>, as well as providing one path for -turning an MPP profile into an ICC profile. If a <a - href="File_Formats.html#.ti3">.ti3</a> file is -specified instead of an <a href="File_Formats.html#ICC">ICC</a> or <a - href="File_Formats.html#MPP">MPP</a> profile, -then the closest matching measured points in the .<a - href="File_Formats.html#.ti3">.ti3</a> are substituted -for the test values in the <a href="File_Formats.html#.ti1">.ti1</a> -file on -output. If the <a href="File_Formats.html#.ti1">.ti1</a> -file is a monochrome test file with a White device value, then an RGB <a - href="File_Formats.html#ICC">ICC</a> profile, <a - href="File_Formats.html#MPP">MPP</a> or <a - href="File_Formats.html#.ti3">.ti3</a> may be used, and the White -values will be translated to equal RGB values. If the <a - href="File_Formats.html#.ti1">.ti1</a> -file is a monochrome test file with a Black device value, then a CMYK <a - href="File_Formats.html#ICC">ICC</a> profile, <a - href="File_Formats.html#MPP">MPP</a> or <a - href="File_Formats.html#.ti3">.ti3</a> may be used, and the Black -values will be translated to equal CMY = 0, K = grey values. <span - style="font-weight: bold;">Note</span> that -any calibration within a supplied ICC profile is <span - style="text-decoration: underline;">not</span> applied during the -conversion, although it will be included in the .ti3 output (see <span - style="font-weight: bold;">-k</span> and <span - style="font-weight: bold;">-i</span> flags for how apply calibration -curves during the conversion and/or include -a specific calibration curves in the output).<br> -<br> -If a separation device profile is provided (e.g. from CMY -> CMYK, -or perhaps CMYK->CMYK, to simulate a color correction step before -"printing"), then this will be applied to the .ti1 device values, -before converting the the device values into .ti3 PCS values.<br> -<br> -<br> -<br> -</body> + + + 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 + style="font-family: monospace;" href="File_Formats.html#.ti3">.ti3</a><span + style="font-family: monospace;">] file</span></small><br> + <b><br> + Examples</b><br> + <br> + fakeread profile.icm testvalues<br> + fakeread -p separation.icm profile.icm testvalues<br> + <h3>Comments<br> + </h3> + <a name="v"></a>The <span style="font-weight: bold;">-v</span> flag + reports extra information, e.g. on what BT.1886 option is doing. A + level > 1 will be more verbose.<br> + <br> + <a name="e"></a>The <b>-e</b> <i>flag</i> applies a Video encoding + to the input of the separation.<small><small><br> + <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" lev</small></small><br> + <br> + <a name="p"></a>The <span style="font-weight: bold;">-p</span> <b><i>separation.icm</i></b> + option enables a device to device value conversion before converting + to expected PCS values. This might be an ink separation of a video + calibration device link. The argument is the name of the ICC device + link that defines the separation.<br> + <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> + <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 + 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 + curves will also be included in the resulting .ti3 file, so that + they can be passed through to the ICC profile allowing accurate + 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 + 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> + <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 + simulated printing system. The parameter supplied to the flag will + be used to scale a random offset added to the device values (after + any separation and calibration is applied). The offset will be a + normally distributed error with an average deviation of level%. A + typically value supplied might be 1.0 to simulate 1% randomness.<br> + <br> + <a name="0"></a>The <span style="font-weight: bold;">-0, -1, -2 .. + -9</span> parameters are a way of simulating changes in the + behavior of the simulated printing system. The parameter supplied to + the flag will be used to modify the device values (after any + separation, calibration and device randomness is applied) by raising + 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 + 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> + <br> + <a name="I"></a>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 + intend to make a profile from the resulting .ti3 file, since + profiles are always made from absolute colorimetric measurement + values. Note that this flag does nothing if the profile is an MPP or + .ti3 file.<br> + <span style="font-weight: bold;"></span><br> + <a name="A"></a>The <span style="font-weight: bold;">-A</span> + parameter is a way of simulating devices that have a different black + point to the profile used. This only works if an ICC profile is + used, and scales the black point to the parameter value. This will + be done in XYZ space by default, and in L*a*b* space if the <a + href="#l"><span style="font-weight: bold;">-l</span></a> flag is + used.<br> + <br> + <a name="l"></a>The <span style="font-weight: bold;">-l</span> flag + causes the CIE output values to be L*a*b* rather than the default + XYZ values.<br> + <br> + <a name="s"></a>The <span style="font-weight: bold;">-s</span> flag + works if a spectral MPP file is being used as a device profile, and + causes the output to include spectral values.<br> + <br> + <a name="R"></a>The <span style="font-weight: bold;">-R</span> + parameter is a way of simulating instability in the behavior of the + simulated measuring system. The parameter supplied to the flag will + be used to scale a random offset added to the PCS values. The offset + will be a normally distributed error with an average deviation of + level%. A typically value supplied might be 1.0 to simulate 1% + randomness. <br> + <br> + <a name="u"></a>The <span style="font-weight: bold;">-u</span> flag + changes the distribution of the random offsets applied using the <span + style="font-weight: bold;">-r</span> or <span style="font-weight: + bold;">-R</span> flags, from the default standard deviation, to a + uniform deviation distribution. The level is still specified as an + average deviation.<br> + <br> + <a name="S"></a>The <span style="font-weight: bold;">-S</span> + parameter lets a particular random seed be used when generating + random offsets, so that the randomness can be made repeatable. + Normally a different seed will be used for each run. <br> + <br> + Fakeread is useful in creating artificial test value for testing <a + href="colprof.html">colprof</a>, as well as providing one path for + turning an MPP profile into an ICC profile. It can also be used to + create a reference file for verifying against. If a <a + href="File_Formats.html#.ti3">.ti3</a> file is specified instead + of an <a href="File_Formats.html#ICC">ICC</a> or <a + href="File_Formats.html#MPP">MPP</a> profile, then the closest + matching measured points in the .<a href="File_Formats.html#.ti3">.ti3</a> + are substituted for the test values in the <a + href="File_Formats.html#.ti1">.ti1</a> file on output. If the <a + href="File_Formats.html#.ti1">.ti1</a> file is a monochrome test + file with a White device value, then an RGB <a + href="File_Formats.html#ICC">ICC</a> profile, <a + href="File_Formats.html#MPP">MPP</a> or <a + href="File_Formats.html#.ti3">.ti3</a> may be used, and the White + values will be translated to equal RGB values. If the <a + href="File_Formats.html#.ti1">.ti1</a> file is a monochrome test + file with a Black device value, then a CMYK <a + href="File_Formats.html#ICC">ICC</a> profile, <a + href="File_Formats.html#MPP">MPP</a> or <a + href="File_Formats.html#.ti3">.ti3</a> may be used, and the Black + values will be translated to equal CMY = 0, K = grey values. <span + style="font-weight: bold;">Note</span> that any calibration within + a supplied ICC profile is <span style="text-decoration: underline;">not</span> + applied during the conversion, although it will be included in the + .ti3 output (see <span style="font-weight: bold;">-k</span> and <span + style="font-weight: bold;">-i</span> flags for how apply + calibration curves during the conversion and/or include a specific + calibration curves in the output).<br> + <br> + If a separation device profile is provided (e.g. from CMY -> + CMYK, or perhaps CMYK->CMYK, to simulate a color correction step + before "printing", or perhaps a Video RGB->RGB calibration link) + then this will be applied to the .ti1 device values, before + converting the the device values into .ti3 PCS values.<br> + <br> + <br> + <br> + <br> + </body> </html> diff --git a/doc/i1proHiRes.html b/doc/i1proHiRes.html new file mode 100644 index 0000000..d6d8078 --- /dev/null +++ b/doc/i1proHiRes.html @@ -0,0 +1,177 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> + <head> + <title>The i1pro Hi Res. Mode</title> + <meta http-equiv="content-type" content="text/html; + charset=ISO-8859-1"> + <meta content="Graeme Gill" name="author"> + </head> + <body> + <h2 style="text-decoration: underline; font-weight: bold;">Does the + i1pro High Resolution mode improve accuracy ?<br> + </h2> + A question that has been asked is : "<span style="font-weight: + bold;">You've extended the Eye-One Pro with a high resolution + spectral mode, giving readings at 3.3nm spacing rather than the + default 10nm. Does this mode improve accuracy ?</span>"<br> + <br> + This is a quite reasonable question. The following attempts to + answer it.<br> + <h4 style="text-decoration: underline;">Why would a higher + resolution spectral mode improve accuracy ?<br> + </h4> + A spectrometer computes CIE tri-stimulus values by measuring + spectral values and then weighing those values by the observer + curves before summing the weigted values. The accuracy depends on + the correct weighting being applied at each wavelength. If the color + is composed of very narrow spectra peaks, as is sometimes the case + for certain light sources and many display devices, then the exact + positioning of one of the peaks on the observer curves may be + influencial in the final color value, and too coarse a quanization + of the spectral readings may lead to tri-stimulus errors. So in + theory increasing the spectral reading resolution to 3.3 nm should + lead to improved color accuracy with narrow spectra color sources. <br> + <h4 style="text-decoration: underline;">Why may this not work in + practice ?</h4> + <p>The instrument spectral resolving power is set by a number of + factors, and a critical one is the entrance slit width. By + measuring a very narrow band source such a as a laser, using the + default 10nm resolution indicates a FWHM (<a + href="http://en.wikipedia.org/wiki/Full_width_at_half_maximum">Full + + + + + 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> + <p>Another factor is that the calibration data for the instrument is + only given at 10nm intervals. So to produce calibrated readings at + 3.3nm intervals, it is necessary to up-sample the calibration data + with sufficient accuracy. If the calibration data is sufficiently + smooth (indicating that the underlying device characteristics are + also smooth), or any slight inaccuracy will get calibrated out + (which is typically the case for reflective measurements) then + this may not be a limitation either. In the case of the i1pro2, + 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> + </p> + <h4 style="text-decoration: underline;">The verification experiment<br> + </h4> + To give some indication of whether ArgyllCMS's high resolution + spectral mode is capable of improving color measurement accuracy, or + at least to indicate that it doesn't noticeably worsen it, the + following fairly simple, real world experiment was performed:<br> + <br> + A measurement target consisting of white + primary + secondary + colors (White, Red, Green, Blue, Cyan, Magenta, Yellow) repeated 10 + times was used. This target was displayed on a conventional LCD + screen with a CCFL backlight (MacBook display), and measured using + using ArgyllCMS V1.6.0 <a href="dispread.html">dispread</a>:<br> + <br> + 1) Using a <a +href="http://www.jeti.com/cms/index.php/instruments-55/radiometer/specbos-1211">JETI + + + + + specbos 1211</a> reference Tele-Spectro-Radiometer.<br> + <br> + 2) Using an i1pro2 in standard 10nm mode.<br> + <br> + 3) Using an i1pro2 in ArgyllCMS 3.3nm mode.<br> + <br> + The resulting readings were then analyzed using <a + href="colverify.html">colverify</a>.<br> + <br> + The results were analyzed two ways, first in absolute value error + terms, and secondly in brightness (Y) normalized terms, the latter + corresponding to the typical way such readings are used for display + calibration and profiling. <br> + <br> + A second, similar experiment was run on a CRT type display.<br> + <h4 style="text-decoration: underline;">Results:</h4> + <p><br> + LCD display:<br> + </p> + <p>Absolute errors of i1pro2 10nm mode to specbos 1211:<br> + </p> + Total errors (CIEDE2000): peak = + 3.070420, avg = 2.204137<br> + <br> + Absolute errors of i1pro2 3.3nm mode to specbos 1211:<br> + <br> + Total errors (CIEDE2000): peak = + 2.108411, avg = 1.568577<br> + <br> + <br> + White Y normalised errors of i1pro2 10nm mode to specbos 1211:<br> + <br> + Total errors (CIEDE2000): peak = + 2.419800, avg = 0.747926<br> + <br> + White Y normalised errors of i1pro2 3.3nm mode to specbos 1211:<br> + <br> + Total errors (CIEDE2000): peak = + 1.595033, avg = 0.578270<br> + <br> + <br> + So in this particular situation, hi-res mode improves accuracy by + somewhere between 0.2 and 0.6 DeltaE 2K.<br> + <br> + <br> + Example of white spectrum for the three measurements (red: 10nm + i1pro2, green: 3.3nm i1pro2, black: specbos):<br> + <img alt="specbos 1211 (Black), i1pro2 10nm (Red), i1pro2 3.3nm + (Green)" src="i1proHiRes.jpg" height="335" width="667"><br> + <br> + <p><br> + CRT display:<br> + </p> + <p>Absolute errors of i1pro2 10nm mode to specbos 1211:<br> + </p> + Total errors (CIEDE2000): peak = + 1.516886, avg = 0.965740<br> + <br> + Absolute errors of i1pro2 3.3nm mode to specbos 1211:<br> + <br> + Total errors (CIEDE2000): peak = + 1.751776, avg = 0.887878<br> + <br> + <br> + White Y normalised errors of i1pro2 10nm mode to specbos 1211:<br> + <br> + Total errors (CIEDE2000): peak = + 1.509129, avg = 0.654752<br> + <br> + White Y normalised errors of i1pro2 3.3nm mode to specbos 1211:<br> + <br> + Total errors (CIEDE2000): peak = + 1.284044, avg = 0.622501<br> + <br> + <h4 style="text-decoration: underline;">Conclusions:</h4> + The results for the conditions of this particular experiment + indicate that ArgyllCMS High Resolution mode can very slightly + 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 + 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> + <h4 style="text-decoration: underline;">Raw Data:</h4> + The raw measurement data is available in this <a + href="i1proHiRes.zip">.ti3 archive</a>.<br> + <br> + <br> + <br> + <br> + <br> + <br> + </body> +</html> diff --git a/doc/i1proHiRes.jpg b/doc/i1proHiRes.jpg Binary files differnew file mode 100644 index 0000000..c07b37c --- /dev/null +++ b/doc/i1proHiRes.jpg diff --git a/doc/i1proHiRes.zip b/doc/i1proHiRes.zip Binary files differnew file mode 100644 index 0000000..49721f9 --- /dev/null +++ b/doc/i1proHiRes.zip diff --git a/doc/iccgamut.html b/doc/iccgamut.html index 6d2f5ba..fe555cf 100644 --- a/doc/iccgamut.html +++ b/doc/iccgamut.html @@ -12,186 +12,226 @@ Create a gamut file or VRML 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 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> <h3>Usage<br> </h3> <small><span style="font-family: monospace;">iccgamut [-options] </span><i style="font-family: monospace;">profile</i><br style="font-family: monospace;"> <span style="font-family: monospace;"> -v + + + Verbose</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -d - sres Surface - resolution details 1.0 - 50.0</span><br style="font-family: - monospace;"> + sres Surface resolution + details 1.0 - 50.0</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -w emit + + + VRML .wrl 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 + + + VRML 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 style="font-family: - monospace;"> - - <span style="font-family: monospace;"></span></small><small><span - style="font-family: monospace;">-i - intent p = - perceptual, r = relative colorimetric,</span><br + function f = forward*, b = backwards</span><br style="font-family: monospace;"> + <span style="font-family: monospace;"></span></small><small><span + style="font-family: monospace;">-i + intent p = perceptual, r = relative + colorimetric,</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> s + + + = saturation, a = absolute (default), d = profile default</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;"> -o - order n = normal - (priority: lut > matrix > monochrome)</span><br - style="font-family: monospace;"> + order n = normal (priority: lut + > matrix > monochrome)</span><br style="font-family: + monospace;"> <span style="font-family: monospace;"> r - = reverse (priority: monochrome > - matrix > lut)<br> + + + + = reverse (priority: monochrome > matrix > lut)<br> </span></small><small><span style="font-family: monospace;"> </span><span style="font-family: monospace;">-p oride</span><span style="font-family: monospace;"> l - = - Lab_PCS (default), j = CIECAM02 Appearance Jab</span></small><small><span + = Lab_PCS (default), j = CIECAM02 Appearance Jab</span></small><small><span style="font-family: monospace;"></span><span style="font-family: monospace;"></span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -l - tlimit set total - ink limit, 0 - 400% (estimate by default)</span><br - style="font-family: monospace;"> + tlimit set total ink limit, 0 - 400% + (estimate by default)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -L - klimit set black ink - limit, 0 - 100% (estimate by default)</span><br - style="font-family: monospace;"> + klimit set black ink limit, 0 - 100% + (estimate by default)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -c - viewcond set - viewing conditions for CIECAM02,</span><br style="font-family: - monospace;"> + viewcond set viewing conditions for CIECAM02,</span><br + style="font-family: monospace;"> <span style="font-family: monospace;"> either - an enumerated choice, or a series of - parameters:value changes</span><br style="font-family: - monospace;"> + + + + 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 - style="font-family: monospace;"> - pp - Practical Reflection - Print - (ISO-3664 P2)</span><br style="font-family: monospace;"> + style="font-family: monospace;"> + pp - Practical Reflection Print (ISO-3664 P2)</span><br + style="font-family: monospace;"> <span style="font-family: monospace;"> + + + 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;"> <span style="font-family: monospace;"> + + + mt - Monitor in typical work environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> + + + mb - Monitor in bright work environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - md - Monitor in darkened work + md - Monitor in darkened work environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - jm - Projector in dim environment</span><br + jm - Projector in dim environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - jd - Projector in dark environment</span><br + jd - Projector in dark environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - pcd - Photo CD - original scene + pcd - Photo CD - original scene outdoors</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - ob - Original scene - Bright Outdoors</span><br + ob - Original scene - Bright Outdoors</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - cx - Cut Sheet Transparencies on a viewing - box</span></small><small><span style="font-family: monospace;"></span><span - style="font-family: monospace;"></span><br style="font-family: - monospace;"> + cx - Cut Sheet Transparencies on a + viewing box</span></small><small><span style="font-family: + monospace;"></span><span style="font-family: monospace;"></span><br + style="font-family: monospace;"> <span style="font-family: monospace;"> 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;"> + + + + 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;"> + + + + 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:scenewhite Scene - white in - cd.m^2 if surround = auto (default 250)<br style="font-family: - monospace;"> - </span><span style="font-family: monospace;"> + l:imagewhite Image + white in cd.m^2 if surround = auto (default 250)</span></small><br + style="font-family: monospace;"> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> f:flare - Flare - light % of image luminance (default 1)</span><br - style="font-family: monospace;"> + + + + Flare light % of image luminance (default 0)<br> + </span></small> </span><span style="font-family: + monospace;"> + g:glare Glare light % of ambient + (default 1)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -f:X:Y:Z - Flare color as - XYZ (default media white)</span><br 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;"> -f:x:y - Flare color as x, y<br> + + + g:x:y Glare color as + x, y<br> -s Create + + + special cube surface topology plot<br style="font-family: monospace;"> </span><i style="font-family: monospace;">profile</i><span style="font-family: monospace;"> - The - name of the </span><a style="font-family: monospace;" - href="File_Formats.html#ICC">ICC</a><span style="font-family: - monospace;"> - profile, as well as the 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> + The name of the </span><a style="font-family: + monospace;" href="File_Formats.html#ICC">ICC</a><span + style="font-family: monospace;"> profile, as well as the + 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> <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> @@ -201,127 +241,106 @@ Create cubic L*a*b* units.<br> <br> The <b>-d</b> parameter controls the level of detail displayed in - the - surface. The parameter roughly corresponds to a deltaE value, so - smaller - values give greater detail. The default value is around 10, and is a - good - place to start. Small values may take a lot of time to generate, and - will - produce big files.<br> + the surface. The parameter roughly corresponds to a deltaE value, so + smaller values give greater detail. The default value is around 10, + 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 gamut file.<br> <br> - The <b>-n</b> flag suppresses the L*a*b* axes being created in - the VRML.<br> + The <b>-n</b> flag suppresses the L*a*b* axes being created in the + VRML.<br> <br> The <span style="font-weight: bold;">-k</span> flag adds markers - for - each of the primary and secondary "cusp" points (Red, Yellow, Green, - Cyan, Blue & Magenta). No markers will be displayed if the cusps - cannot be determined.<br> + for each of the primary and secondary "cusp" points (Red, Yellow, + Green, Cyan, Blue & Magenta). No markers will be displayed if + the cusps cannot be determined.<br> <br> The <b>-f </b>parameter allows choosing the ICC table to be used - in - plotting the gamut. The backwards tables generally incorporate gamut - compression, and therefore don't reflect the native capabilities of - the - device.<br> + in plotting the gamut. The backwards tables generally incorporate + gamut compression, and therefore don't reflect the native + capabilities of the device.<br> <br> The <b>-i</b> flag selects the intent transform used for a lut - based - profile. It also selects between relative and absolute colorimetric - for - non-lut base profiles. Note that anything other than colorimetric - may - not represent the - native capabilities of the device. The default intent will be - absolute - colorimetic for L*a*b* output, and CIECAM02 appearance for Jab - output.<br> + based profile. It also selects between relative and absolute + colorimetric for non-lut base profiles. Note that anything other + than colorimetric may not represent the native capabilities of the + device. The default intent will be absolute colorimetic for L*a*b* + output, and CIECAM02 appearance for Jab output.<br> <br> An ICC profile is allowed to contain more than the minimum number of elements or table needed to describe a certain transform, and may contain redundant descriptions. By default, lut based table information will be used first if present, followed by matrix/shaper - information, and only using - monochrome information if it is all that is present. The <b>-o</b> - flag, - reverses this order. <br> + information, and only using monochrome information if it is all that + is present. The <b>-o</b> flag, reverses this + order. <br> <br> <span style="font-weight: bold;">-p</span>: By default the gamut - will - be created in L*a*b* colorspace. If <span style="font-weight: - bold;">-pj</span> is selected, then CIECAM02 + will be created in L*a*b* colorspace. If <span + style="font-weight: bold;">-pj</span> is selected, then CIECAM02 appearance space Jab will be used for the output, and the viewing conditions will be taken into account. Jab space is what is normally needed to be compatible with the default intents used in <a href="colprof.html">colprof</a>. <span style="font-weight: bold;"><br> </span>Note that the CIECAM02 output space selection by default uses the colorimetric transform of the profile resulting in the - appearance - of the native device, but that the perceptual or + appearance of the native device, but that the perceptual or saturation transforms may be used by selecting them using the <span style="font-weight: bold;">-i</span> parameter, which may give a different result with some profiles. This may be desirable if an - image - is to be transformed through the perceptual or saturation tables of - a - profile as part of a link with an Argyll generated output profile, - since it will then represent the apparent gamut of the image when - subject to these tables. If the absolute colorimetric intent is - chosen - using <span style="font-weight: bold;">-ia</span> in combinations - with - <span style="font-weight: bold;">-pj</span>, then Jab with - a fixed white reference is used, which emulates an absolute CIECAM02 - Jab - appearance space. <br> + image is to be transformed through the perceptual or saturation + tables of a profile as part of a link with an Argyll generated + output profile, since it will then represent the apparent gamut of + the image when subject to these tables. If the absolute colorimetric + intent is chosen using <span style="font-weight: bold;">-ia</span> + in combinations with <span style="font-weight: bold;">-pj</span>, + then Jab with a fixed white reference is used, which emulates + an absolute CIECAM02 Jab appearance space. <br> <br> The <b>-l</b> parameter allows setting a total ink limit (TAC) for - printing - devices. If a device has a total ink limit, and hasn't been + printing devices. If a device has a total ink limit, and hasn't been characterised with device values above this limit, then plotting the gamut in these areas will almost certainly be misleading. tables. By - default, a total ink limit will - be estimated from the profile tables. The ink limit - will be in final calibrated device values if the profile includes - calibration information.<br> + default, a total ink limit will be estimated from the profile + tables. The ink limit will be in final calibrated device values if + the profile includes calibration information.<br> <br> The <b>-L</b> parameter allows setting a black ink limit for - printing - devices. If a device is to be used with a black ink limit, then it - is - useful to evaluate - the gamut with the limit in place. By default, a black ink limit - will - be estimated from the profile tables. The ink limit - will be in final calibrated device values if the profile includes - calibration information.<br> + printing devices. If a device is to be used with a black ink limit, + then it is useful to evaluate the gamut with the limit in place. By + default, a black ink limit will be estimated from the profile + tables. The ink limit will be in final calibrated device values if + the profile includes calibration information.<br> <br> The <b>-c</b> parameter allows setting the CIECAM02 viewing - conditions, - either by choosing a typical viewing environment, or controlling - particular viewing condition parameters.<br> + conditions, either by choosing a typical viewing environment, or + controlling particular viewing condition parameters.<br> <br> The <span style="font-weight: bold;">-s</span> flag creates a - special - hyper-cube surface plot that is artificially colored. This can be - useful for identifying the topology of the black ink color response.<br> + special hyper-cube surface plot that is artificially colored. This + can be useful for identifying the topology of the black ink color + response.<br> <h3>Example<br> </h3> To create a view in L*a*b* of the absolute gamut of a CMYK file with - an - ink limit of 260%, one might use:<br> + an ink limit of 260%, one might use:<br> <br> <span style="font-style: italic;">iccgamut -w - -ff - -ia -l260 profile.icm</span><br> + -ff -ia -l260 profile.icm</span><br> <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> + <br> + To create a gamut suitable for CIECAM02 gamut mapping space in + colprof or collink, something like<br> + <br> + iccgamut -ir -pj -cmt profile.icm<br> + <br> + where the viewing conditions "mt" should the same as the source + conditions in colprof or collink.<br> <br style="font-weight: bold;"> <span style="font-weight: bold;"></span><br> <br> diff --git a/doc/illumread.html b/doc/illumread.html index 03b5648..0dcf5bd 100644 --- a/doc/illumread.html +++ b/doc/illumread.html @@ -10,15 +10,11 @@ <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> + 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;"> @@ -26,6 +22,7 @@ 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;"> @@ -34,46 +31,46 @@ 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;"> + 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 + + 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> + 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: 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 + 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> @@ -81,40 +78,26 @@ File <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> + 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> + 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> + 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 + 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 @@ -129,40 +112,39 @@ File 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> + 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> + 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 + <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> + 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> + 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> + 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> @@ -173,74 +155,55 @@ File 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> + 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> + 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> + 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> + 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> + 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> + 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> + 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> + 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;" @@ -250,22 +213,15 @@ File </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> + 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> + 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: @@ -273,33 +229,29 @@ File </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> + 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> + 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> + 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: diff --git a/doc/instruments.html b/doc/instruments.html index 896c0e5..0bcc62d 100644 --- a/doc/instruments.html +++ b/doc/instruments.html @@ -1,28 +1,44 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<html> - <head> - <title>Operation of particular instruments</title> - <meta http-equiv="content-type" content="text/html; - charset=ISO-8859-1"> - </head> - <body> - <h2><u>Operation of particular instruments</u></h2> - <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><span - style="font-weight: bold;"></span><br> - <br> - The following instruments are directly supported:<br> - (Please <span style="font-weight: bold;">note</span> the <a - href="Installing.html">installation instructions</a> for each - platform - they contain important information for getting your - instruments working.)<br> - <br> - X-Rite:<br> - <a href="#DTP20">DTP20 "Pulse"</a> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+ <head>
+ <title>Operation of particular instruments</title>
+ <meta http-equiv="content-type" content="text/html;
+ charset=windows-1252">
+ </head>
+ <body>
+ <h2><u>Operation of particular instruments</u></h2>
+ <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><span
+ style="font-weight: bold;"></span><br>
+ <br>
+ The following instruments are directly supported:<br>
+ (Please <span style="font-weight: bold;">note</span> the <a
+ href="Installing.html">installation instructions</a> for each
+ platform - they contain important information for getting your
+ instruments working.)<br>
+ <br>
+ JETI:<br>
+ <br>
+ <a href="#specbos">specbos 1211 & 1201</a> + + + + + + + + + + +
+ - Tele-Spectro-Radiometer<br>
+ <br>
+ X-Rite:<br>
+ <a href="#DTP20">DTP20 "Pulse"</a>
@@ -45,7 +61,19 @@ - - "swipe" type reflective spectrometer, that can be used untethered.<br> + + + + + + + + + + + +
+ - "swipe" type reflective spectrometer, that can be used untethered.<br>
<a href="#DTP22">DTP22 Digital Swatchbook</a> @@ -68,7 +96,19 @@ - - spot type reflective spectrometer.<br> + + + + + + + + + + + +
+ - spot type reflective spectrometer.<br>
<a href="#DTP41">DTP41</a> @@ -91,9 +131,21 @@ - - spot and strip reading reflective spectrometer.<br> - <a href="#DTP41">DTP41T</a> - + + + + + + + + + + + +
+ - spot and strip reading reflective spectrometer.<br>
+ <a href="#DTP41">DTP41T</a>
+
@@ -116,7 +168,19 @@ - - spot and strip reading reflective/transmissive spectrometer.<br> + + + + + + + + + + + +
+ - spot and strip reading reflective/transmissive spectrometer.<br>
<a href="#dtp51">DTP51</a> @@ -139,7 +203,19 @@ - - strip reading reflective colorimeter.<br> + + + + + + + + + + + +
+ - strip reading reflective colorimeter.<br>
<a href="#DTP92">DTP92</a> @@ -162,7 +238,19 @@ - - CRT display colorimeter.<br> + + + + + + + + + + + +
+ - CRT display colorimeter.<br>
<a href="#DTP94">DTP94</a> <font size="-1">"Optix @@ -185,7 +273,19 @@ - XR"</font> or "Optix XR2" or "Optix Pro"- display colorimeter.<br> + + + + + + + + + + + +
+ XR"</font> or "Optix XR2" or "Optix Pro"- display colorimeter.<br>
<a href="#ColorMunki"><span style="text-decoration: underline;"></span></a> @@ -208,62 +308,73 @@ - <a href="#ColorMunki"><span style="text-decoration: underline;">ColorMunki</span></a> - Design or Photo - - spot and "swipe" - reflective/emissive spectrometer (UV cut only).<br> - <a href="#i1d"><span style="text-decoration: - underline;">ColorMunki</span></a> Create or Smile - - display - colorimeter. (Similar to an Eye-One Display 2)<br> - <a href="#Huey">Lenovo W</a> - - - built in laptop - Huey display colorimeter.<br> - <a href="#i1d3">Eye-One Display 3</a> - - - i1 DisplayPro and ColorMunki Display<br> - - - - - [ The OEM - i1Display Pro and<br> - - - - - - NEC SpectraSensor Pro are also reported to work.]<br> - <a href="instruments.html#i1p2">Eye-One Pro2</a> - - - spot and - "swipe" reflective/emissive spectrometer.<br> - <br> - Gretag-Macbeth (now X-Rite):<br> - <a href="#sl">Spectrolino</a> - - - spot reflective/emissive - spectrometer<br> - <a href="#ss">SpectroScan</a> - - - spot reflective/emissive, XY table - reflective spectrometer <br> - <a href="#ss">SpectroScanT</a> - - - spot reflective/emissive/transmissive, XY - table reflective spectrometer<br> - <a href="#i1p">Eye-One Pro</a> "EFI ES-1000" - - spot and "swipe" reflective/emissive - spectrometer<br> - <a href="instruments.html#i1m">Eye-One Monitor</a> - - - spot and "swipe" emissive spectrometer<br> - <a href="#i1d">Eye-One Display 1 or 2 or - LT</a> - display - colorimeter<br> - <a href="instruments.html#i1d">HP DreamColor or - APS</a> + + + + + + + + + + + +
+ <a href="#ColorMunki"><span style="text-decoration: underline;">ColorMunki</span></a>
+ Design or Photo
+ - spot and "swipe"
+ reflective/emissive spectrometer (UV cut only).<br>
+ <a href="#i1d"><span style="text-decoration:
+ underline;">ColorMunki</span></a> Create or Smile
+ - display
+ colorimeter. (Similar to an Eye-One Display 2)<br>
+ <a href="#Huey">Lenovo W</a>
+
+ - built in laptop
+ Huey display colorimeter.<br>
+ <a href="#i1d3">Eye-One Display 3</a>
+
+ - i1 DisplayPro and ColorMunki Display<br>
+
+
+
+
+ [ The OEM
+ i1Display Pro, NEC SpectraSensor Pro,<br>
+
+
+
+ Quato Silver Haze 3 OEM and HP
+ DreamColor i1d3 are also reported to work.]<br>
+ <a href="instruments.html#i1p2">Eye-One Pro2</a>
+
+ - spot and
+ "swipe" reflective/emissive spectrometer.<br>
+ <br>
+ Gretag-Macbeth (now X-Rite):<br>
+ <a href="#sl">Spectrolino</a>
+
+ - spot reflective/emissive
+ spectrometer<br>
+ <a href="#ss">SpectroScan</a>
+
+ - spot reflective/emissive, XY table
+ reflective spectrometer <br>
+ <a href="#ss">SpectroScanT</a>
+
+ - spot reflective/emissive/transmissive, XY
+ table reflective spectrometer<br>
+ <a href="#i1p">Eye-One Pro</a> "EFI ES-1000"
+ - spot and "swipe" reflective/emissive
+ spectrometer<br>
+ <a href="instruments.html#i1m">Eye-One Monitor</a>
+
+ - spot and "swipe" emissive spectrometer<br>
+ <a href="#i1d">Eye-One Display 1 or 2 or
+ LT</a> - display
+ colorimeter<br>
+ <a href="instruments.html#i1d">HP DreamColor or
+ APS</a>
@@ -286,8 +397,20 @@ - - display colorimeter. (Treated as a Eye-One Display 2)<br> - <a href="#i1d">CalMAN X2</a> + + + + + + + + + + + +
+ - display colorimeter. (Treated as a Eye-One Display 2)<br>
+ <a href="#i1d">CalMAN X2</a>
@@ -310,17 +433,29 @@ - - display colorimeter. (Treated as a Eye-One Display 2)<br> - <a href="#Huey">Huey</a> - - - - display colorimeter<br> - <br> - Sequel imaging (Now X-Rite):<br> - <a href="#mox">MonacoOPTIX</a> - - - display colorimeter (Treated - as an Eye-One Display 1)<br> + + + + + + + + + + + +
+ - display colorimeter. (Treated as a Eye-One Display 2)<br>
+ <a href="#Huey">Huey</a>
+
+
+ - display colorimeter<br>
+ <br>
+ Sequel imaging (Now X-Rite):<br>
+ <a href="#mox">MonacoOPTIX</a>
+
+ - display colorimeter (Treated
+ as an Eye-One Display 1)<br>
@@ -343,9 +478,21 @@ - [The Sequel Chroma 4 may also work.]<br> - <br> - Lacie Blue + + + + + + + + + + + +
+ [The Sequel Chroma 4 may also work.]<br>
+ <br>
+ Lacie Blue
Eye: @@ -368,15 +515,6 @@ - - see <a href="#i1d">Eye-One Display</a><br> - <br> - DataColor ColorVision:<br> - <a href="#spyd2">Spyder 2</a> - - - - display colorimeter (Note - that the user must <a href="oeminst.html">supply</a> firmware)<br> - @@ -388,6 +526,17 @@ +
+ - see <a href="#i1d">Eye-One Display</a><br>
+ <br>
+ DataColor ColorVision:<br>
+ <a href="#spyd2">Spyder 2</a>
+
+
+ - display colorimeter (Note
+ that the user must <a href="oeminst.html">supply</a> firmware)<br>
+ + @@ -398,20 +547,6 @@ - [The Spyder 1 also seems to work.]<br> - <a href="#spyd3">Spyder 3</a> - - - - display colorimeter.<br> - <a href="#spyd4">Spyder 4</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 @@ -433,6 +568,21 @@ +
+ [The Spyder 1 also seems to work.]<br>
+ <a href="#spyd3">Spyder 3</a>
+
+
+ - display colorimeter.<br>
+ <a href="#spyd4">Spyder 4</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
HCFR</a> @@ -455,9 +605,6 @@ - - display colorimeter<br> - </span> - ColorHug @@ -469,10 +616,15 @@ +
+ - display colorimeter<br>
+ </span> <a href="#ColorHug">ColorHug</a> + + + + + - - display colorimeter. Experimental only, does not work on all - platforms.<br> - @@ -485,284 +637,289 @@ - Set environmental variable ENABLE_COLORHUG=true to test it.<span - class="titre"><br> - </span><br> - Other instruments can be supported indirectly, since patch result - files created by other packages can be imported into Argyll.<br> - <span class="titre"><br> - General information about:<br> - <br> - <a href="#strip">Strip reading instruments</a><br> - </span> <a href="#xy">X-Y Table instruments</a><br> - <a href="#spot">Spot reading instruments</a><br> - <span style="font-weight: bold;"></span><br> - <br> - There is a <a href="ccmxs.html">list of contributed</a> <span - style="font-weight: bold;">ccmx</span> (Colorimeter Correction - Matrix) files.<br> - <br> - <hr style="width: 100%; height: 2px;"> - <h3><a name="strip"></a>Strip reading instruments</h3> - When used with a <span style="font-weight: bold;">DT20</span>, <span - style="font-weight: bold;">DTP41</span>, <span - style="font-weight: bold;">DTP51</span>, <span - style="font-weight: bold;">Eye-One Pro<span style="font-weight: - bold;"> </span></span>or <span style="font-weight: bold;">ColorMunki</span> - strip reading instrument, chartread will first establish - communications with the instrument, and then set it up ready to read - the strips. The strips are labeled A to ZZ, and for each strip it - will prompt:<br> - <br> - About to read strip XX :<br> - <br> - where XX is the strip label, and this is followed by the available - options to navigate, read the strip, or finish. Note that the normal - (forward) direction of strip reading is one that starts at the strip - label.<br> - <br> - For the <span style="font-weight: bold;">DTP51</span> you should - feed the strip into the instrument, and the microswitch will trigger - the read.<br> - <br> - For the <span style="font-weight: bold;">DTP41</span> you should - line the appropriate strip up in the machine, and press its button.<br> - <br> - For the <span style="font-weight: bold;">Eye-One Pro</span> you - should set the guide to the appropriate strip, place the instrument - <span style="text-decoration: underline;">ahead</span> of the first - patch on blank paper, and then press and hold the instruments - button. When you hear a beep from the computer, you can then move - the instrument steadily over the patches, releasing the button after - the instrument is past the last patch. Moving the instrument too - fast or changing speeds may cause a mis-read, or a scan with few - samples read per patch.<br> - <br> - For the <span style="font-weight: bold;">ColorMunki</span> with the - default chart, the patches are the same width as the silver portion - of body (white version), or the textured portion of the body (black - version). Place aperture of the the instrument (located at its - center) in the white space ahead of the first patch, and then press - and hold the instruments button. When you hear a beep from the - computer, you can then move the instrument steadily over the - patches, releasing the button after the instrument is past the last - patch. Moving the instrument too fast or changing speeds may cause a - mis-read, or a scan with few samples read per patch. For the <span - style="font-weight: bold;">high density</span> ColorMunki chart (<a - href="printtarg.html#h">printtarg -h</a>), the patches are - arranged so that three rows are exactly the width of the body - of the instrument. If you are careful you can use this to guide the - center of the instrument over each row, or you may prefer to use - something like a plastic ruler to help guide the instrument.<br> - <br> - Using the <span style="font-weight: bold;">DTP20</span> or the <span - style="font-weight: bold;">Eye-One Pro</span> or <span - style="font-weight: bold;">ColorMunki</span> with a randomized - chart layout, the strip may be scanned from either direction. If a - randomized chart layout has not been used for the <span - style="font-weight: bold;">Eye-One Pro</span> or <span - style="font-weight: bold;">ColorMunki</span>, then the chart - should only be read in the one direction (use <a - href="chartread.html#B">chartread -B</a>).<br> - <br> - Note that you may have to check that system alert sounds are enabled - and at a suitable volume to in order to hear the beep prompt. For - the Eye-One Pro and ColorMunki, a second beep will sound after a - successfully read strip, or a double beep will sound, - indicating a failure or warning that needs attention. See also the - note on Linux in <a href="Installing_Linux.html">installation</a>.<br> - <br> - If the strip is read successfully there will be a single "success" - beep, and the line will be followed with:<br> - <br> - Ready to read strip XX : <br> - Strip read OK<br> - <br> - If there is an error of some sort there will be a double "fail" - beep, and a message will be issued, and you will be asked whether to - abort the chart reading, or retry the<br> - failed strip:<br> - <br> - Ready to read strip XX : <br> - Strip read failed due to misread (Not enough - patches)<br> - <br> - Hit Esc to give up, any other key to retry:<br> - <br> - If you are unable to successfully read a strip after several - retries, you can skip that strip using the <span - style="font-weight: bold;">'n'</span> key, and save<br> - the chart readings without that strip.<br> - <br> - If the strip is read successfully, but the patches values don't seem - to be what is expected, you will get a double "fail" beep and - the following type of warning:<br> - <br> - Ready to read strip XX :<br> - (Warning) Seem to have read strip YY - rather than XX !<br> - Hit Return to use it anyway, any other key to - retry, Esc, ^C or Q to give up:<br> - <br> - This could be because you have accidentally read the wrong strip (a - common mistake), or it could be that the device response is so - different from what is expected that warning is erroneous, or you - may get a lot of these sorts of warnings if you are accidentally - reading the wrong chart. You may also get this sort of warning if - you are not using bi-direction reading (chartread -B), and read the - strip from the wrong end.<br> - If you are absolutely sure you lined up the correct strip, then hit - return, otherwise line the appropriate strip up again, and hit some - other key (ie. space).<br> - Erroneous warnings are less likely if a previous profile for a - device was given to <span style="font-weight: bold;">targen</span> - to set more accurate expectations.<br> - <br> - You may also see the following type of warning:<br> - <br> - Ready to read strip XX :<br> - (Warning) Patch error YY.YYY (>35 not good, - >95 bad)<br> - There is at least one patch with an very unexpected - response!<br> - Hit Return to use it anyway, any other key to - retry, Esc, ^C or Q to give up:<br> - <br> - Similar to the previous warning, this indicates that while the right - strip appears to have been read, one of the patch readings is quite - different to what is expected. This may indicate an error of some - sort (ie. damaged test chart, or bad instrument positioning), or may - be erroneous if the actual device response is quite different to the - expectation. Erroneous warnings are less likely if a previous - profile for a device was given to <span style="font-weight: bold;">targen</span> - to set more accurate expectations.<br> - <br> - You can also navigate the next strip to be read using the <span - style="font-weight: bold;">'f'</span> key to move forward and the - <span style="font-weight: bold;">'b'</span> keys<span - style="font-weight: bold;"></span><span style="font-weight: bold;"></span> - to move backwards. The prompt will indicate whether this strip has - already been read or not, or whether all strips have been read. You - can also use <span style="font-weight: bold;">'n'</span> to move - forward to the next unread strip. After each successful reading it - will move forward to the next unread strip. When you are finished, - use the <span style="font-weight: bold;">'d'</span> to indicate - that you are done. You can choose to finish before all the strips - are read, and the patches that have been read will be saved to the - .ti3 file. This is useful if you are unable to read a particular - strip successfully, or if you are unable to finish the chart in one - session, and you can later <span style="text-decoration: - underline;">resume</span> reading the chart by using the <span - style="font-weight: bold;">chartread -r</span> flag. [You could - resume reading the chart patch by patch using the <span - style="font-weight: bold;">chartread -r -p</span> if you are - unable to read a strip successfully.]<br> - <br> - When reading in patch by patch mode, there are a few additional - navigation options, such as <span style="font-weight: bold;"><span - style="font-weight: bold;">F</span></span> to move forward 10 - patches, <span style="font-weight: bold;">B</span> to move - backwards 10 patches, and <span style="font-weight: bold;">g</span> - to go to a specific patch.<br> - <br> - You can abort the whole process at any time by hitting Escape, and - the readings will not be saved.<br> - <br> - <hr style="width: 100%; height: 2px;"> - <h3><a name="xy"></a>X-Y Table instruments</h3> - When you are using an XY table type instrument, such as a Gretag <span - style="font-weight: bold;">SpectroScan</span>, chartread - will first establish communications with the instrument, and then - set it up ready to read the chart. You will be prompted for each - sheet with a message such as:<br> - <br> - Please make sure that the white reference is in - slot 1, then<br> - place sheet 1 of 4 on table, then<br> - hit return to continue, Esc to give up<br> - <br> - After hitting return you will be prompted to line up three squares - on the sheet, one at a time:<br> - <br> - Using the XY table controls, locate patch A1 with - the sight,<br> - then hit return to continue, Esc to give up<br> - <br> - On completing this, the instrument will commence reading each sheet.<br> - <br> - <hr style="width: 100%; height: 2px;"> - <h3><a name="spot"></a>Spot reading instruments</h3> - When used with a <span style="font-weight: bold;">DT22</span> or <span - style="font-weight: bold;">SpectroLino</span> or use the patch by - patch reading mode (<span style="font-weight: bold;">chartread -p</span>) - with the <span style="font-weight: bold;"></span> <span - style="font-weight: bold;">Eye-One Pro<span style="font-weight: - bold;"> </span></span>or <span style="font-weight: bold;">ColorMunki</span> - instrument, or use the external values mode (<span - style="font-weight: bold;">chartread -x</span>), chartread will - first establish communications with the instrument, and then set it - up ready to read the patches. The patches are typically labeled by - column A to ZZ, and row 1-999. Each patch will prompt:<br> - <br> - Ready to read patch 'XX' :<br> - <br> - where XX is the patch label, and this is followed by the available - options to navigate, read the strip, or finish.<br> - <br> - Place the instrument on the indicated patch, and trigger a reading - using one of the available methods (typically using the instrument - switch of pressing a key).<br> - <br> - There should be an audible prompt on a successful or failed reading. - <br> - <br> - Note that you may have to check that system alert sounds are enabled - and at a suitable volume to in order to hear the beep prompt. For - the Eye-One Pro and ColorMunki, a second beep will sound after a - successfully read strip, or a double beep will sound, - indicating a failure or warning that needs attention. See also the - note on Linux in <a href="Installing_Linux.html">installation</a>.<br> - <br> - If the patch is read successfully, the line will be completed with:<br> - <br> - Ready to read patch XX :<br> - Patch read OK<br> - <br> - If there is an error of some sort, a message will be issued, and you - will be asked whether to abort the chart reading, or retry the<br> - failed patch:<br> - <br> - Ready to read patch XX : read_strip - returned 'Strip misread' (Bad reading)<br> - <br> - Strip read failed due to misread<br> - Hit Esc to give up, any other key to retry:<br> - <br> - You can navigate the next patch to be read using the <span - style="font-weight: bold;">'f'</span> key to move forward and the - <span style="font-weight: bold;">'b'</span> keys<span - style="font-weight: bold;"></span><span style="font-weight: bold;"></span> - to move backwards, while <span style="font-weight: bold;">'F'</span> - and <span style="font-weight: bold;">'B'</span> will move forward - and backwards by 10 patches. The prompt will indicate whether this - patch has already been read or not, or whether all patches have been - read. You can also use <span style="font-weight: bold;">'n'</span> - to move forward to the next unread patch. When you are finished, use - the <span style="font-weight: bold;">'d'</span> to indicate that - you are done. You can choose to finish before all the patches are - read, and they will be saved to the .ti3 file. This is useful if you - are unable to finish the chart in one session, and you can later <span - style="text-decoration: underline;">resume</span> reading the - chart by using the <span style="font-weight: bold;">chartread -r</span> - flag.<br> - <br> - You can abort the whole process at any time by hitting Escape, and - the readings will not be saved.<br> - <br> - <span style="font-weight: bold;"></span> - <hr style="width: 100%; height: 2px;"> - <h3><a name="displaytype"></a>Display Type<br> - </h3> + + + + + +
+ - display colorimeter<span class="titre"><br>
+ </span><br>
+ Other instruments can be supported indirectly, since patch result
+ files created by other packages can be imported into Argyll.<br>
+ <span class="titre"><br>
+ General information about:<br>
+ <br>
+ <a href="#strip">Strip reading instruments</a><br>
+ </span> <a href="#xy">X-Y Table instruments</a><br>
+ <a href="#spot">Spot reading instruments</a><br>
+ <span style="font-weight: bold;"></span><br>
+ <br>
+ There is a <a href="ccmxs.html">list of contributed</a> <span
+ style="font-weight: bold;">ccmx</span> (Colorimeter Correction
+ Matrix) files.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;">
+ <h3><a name="strip"></a>Strip reading instruments</h3>
+ When used with a <span style="font-weight: bold;">DT20</span>, <span
+ style="font-weight: bold;">DTP41</span>, <span
+ style="font-weight: bold;">DTP51</span>, <span
+ style="font-weight: bold;">Eye-One Pro<span style="font-weight:
+ bold;"> </span></span>or <span style="font-weight: bold;">ColorMunki</span>
+ strip reading instrument, chartread will first establish
+ communications with the instrument, and then set it up ready to read
+ the strips. The strips are labeled A to ZZ, and for each strip it
+ will prompt:<br>
+ <br>
+ About to read strip XX :<br>
+ <br>
+ where XX is the strip label, and this is followed by the available
+ options to navigate, read the strip, or finish. Note that the normal
+ (forward) direction of strip reading is one that starts at the strip
+ label.<br>
+ <br>
+ For the <span style="font-weight: bold;">DTP51</span> you should
+ feed the strip into the instrument, and the microswitch will trigger
+ the read.<br>
+ <br>
+ For the <span style="font-weight: bold;">DTP41</span> you should
+ line the appropriate strip up in the machine, and press its button.<br>
+ <br>
+ For the <span style="font-weight: bold;">Eye-One Pro</span> you
+ should set the guide to the appropriate strip, place the instrument
+ <span style="text-decoration: underline;">ahead</span> of the first
+ patch on blank paper, and then press and hold the instruments
+ button. When you hear a beep from the computer, you can then move
+ the instrument steadily over the patches, releasing the button after
+ the instrument is past the last patch. Moving the instrument too
+ fast or changing speeds may cause a mis-read, or a scan with few
+ samples read per patch.<br>
+ <br>
+ For the <span style="font-weight: bold;">ColorMunki</span> with the
+ default chart, the patches are the same width as the silver portion
+ of body (white version), or the textured portion of the body (black
+ version). Place aperture of the the instrument (located at its
+ center) in the white space ahead of the first patch, and then press
+ and hold the instruments button. When you hear a beep from the
+ computer, you can then move the instrument steadily over the
+ patches, releasing the button after the instrument is past the last
+ patch. Moving the instrument too fast or changing speeds may cause a
+ mis-read, or a scan with few samples read per patch. For the <span
+ style="font-weight: bold;">high density</span> ColorMunki chart (<a
+ href="printtarg.html#h">printtarg -h</a>), the patches are
+ arranged so that three rows are exactly the width of the body
+ of the instrument. If you are careful you can use this to guide the
+ center of the instrument over each row, or you may prefer to use
+ something like a plastic ruler to help guide the instrument.<br>
+ <br>
+ Using the <span style="font-weight: bold;">DTP20</span> or the <span
+ style="font-weight: bold;">Eye-One Pro</span> or <span
+ style="font-weight: bold;">ColorMunki</span> with a randomized
+ chart layout, the strip may be scanned from either direction. If a
+ randomized chart layout has not been used for the <span
+ style="font-weight: bold;">Eye-One Pro</span> or <span
+ style="font-weight: bold;">ColorMunki</span>, then the chart
+ should only be read in the one direction (use <a
+ href="chartread.html#B">chartread -B</a>).<br>
+ <br>
+ Note that you may have to check that system alert sounds are enabled
+ and at a suitable volume to in order to hear the beep prompt. For
+ the Eye-One Pro and ColorMunki, a second beep will sound after a
+ successfully read strip, or a double beep will sound,
+ indicating a failure or warning that needs attention. See also the
+ note on Linux in <a href="Installing_Linux.html">installation</a>.<br>
+ <br>
+ If the strip is read successfully there will be a single "success"
+ beep, and the line will be followed with:<br>
+ <br>
+ Ready to read strip XX : <br>
+ Strip read OK<br>
+ <br>
+ If there is an error of some sort there will be a double "fail"
+ beep, and a message will be issued, and you will be asked whether to
+ abort the chart reading, or retry the<br>
+ failed strip:<br>
+ <br>
+ Ready to read strip XX : <br>
+ Strip read failed due to misread (Not enough
+ patches)<br>
+ <br>
+ Hit Esc to give up, any other key to retry:<br>
+ <br>
+ If you are unable to successfully read a strip after several
+ retries, you can skip that strip using the <span
+ style="font-weight: bold;">'n'</span> key, and save<br>
+ the chart readings without that strip.<br>
+ <br>
+ If the strip is read successfully, but the patches values don't seem
+ to be what is expected, you will get a double "fail" beep and
+ the following type of warning:<br>
+ <br>
+ Ready to read strip XX :<br>
+ (Warning) Seem to have read strip YY
+ rather than XX !<br>
+ Hit Return to use it anyway, any other key to
+ retry, Esc, ^C or Q to give up:<br>
+ <br>
+ This could be because you have accidentally read the wrong strip (a
+ common mistake), or it could be that the device response is so
+ different from what is expected that warning is erroneous, or you
+ may get a lot of these sorts of warnings if you are accidentally
+ reading the wrong chart. You may also get this sort of warning if
+ you are not using bi-direction reading (chartread -B), and read the
+ strip from the wrong end.<br>
+ If you are absolutely sure you lined up the correct strip, then hit
+ return, otherwise line the appropriate strip up again, and hit some
+ other key (ie. space).<br>
+ Erroneous warnings are less likely if a previous profile for a
+ device was given to <span style="font-weight: bold;">targen</span>
+ to set more accurate expectations.<br>
+ <br>
+ You may also see the following type of warning:<br>
+ <br>
+ Ready to read strip XX :<br>
+ (Warning) Patch error YY.YYY (>35 not good,
+ >95 bad)<br>
+ There is at least one patch with an very unexpected
+ response!<br>
+ Hit Return to use it anyway, any other key to
+ retry, Esc, ^C or Q to give up:<br>
+ <br>
+ Similar to the previous warning, this indicates that while the right
+ strip appears to have been read, one of the patch readings is quite
+ different to what is expected. This may indicate an error of some
+ sort (ie. damaged test chart, or bad instrument positioning), or may
+ be erroneous if the actual device response is quite different to the
+ expectation. Erroneous warnings are less likely if a previous
+ profile for a device was given to <span style="font-weight: bold;">targen</span>
+ to set more accurate expectations.<br>
+ <br>
+ You can also navigate the next strip to be read using the <span
+ style="font-weight: bold;">'f'</span> key to move forward and the
+ <span style="font-weight: bold;">'b'</span> keys<span
+ style="font-weight: bold;"></span><span style="font-weight: bold;"></span>
+ to move backwards. The prompt will indicate whether this strip has
+ already been read or not, or whether all strips have been read. You
+ can also use <span style="font-weight: bold;">'n'</span> to move
+ forward to the next unread strip. After each successful reading it
+ will move forward to the next unread strip. When you are finished,
+ use the <span style="font-weight: bold;">'d'</span> to indicate
+ that you are done. You can choose to finish before all the strips
+ are read, and the patches that have been read will be saved to the
+ .ti3 file. This is useful if you are unable to read a particular
+ strip successfully, or if you are unable to finish the chart in one
+ session, and you can later <span style="text-decoration:
+ underline;">resume</span> reading the chart by using the <span
+ style="font-weight: bold;">chartread -r</span> flag. [You could
+ resume reading the chart patch by patch using the <span
+ style="font-weight: bold;">chartread -r -p</span> if you are
+ unable to read a strip successfully.]<br>
+ <br>
+ When reading in patch by patch mode, there are a few additional
+ navigation options, such as <span style="font-weight: bold;"><span
+ style="font-weight: bold;">F</span></span> to move forward 10
+ patches, <span style="font-weight: bold;">B</span> to move
+ backwards 10 patches, and <span style="font-weight: bold;">g</span>
+ to go to a specific patch.<br>
+ <br>
+ You can abort the whole process at any time by hitting Escape, and
+ the readings will not be saved.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;">
+ <h3><a name="xy"></a>X-Y Table instruments</h3>
+ When you are using an XY table type instrument, such as a Gretag <span
+ style="font-weight: bold;">SpectroScan</span>, chartread
+ will first establish communications with the instrument, and then
+ set it up ready to read the chart. You will be prompted for each
+ sheet with a message such as:<br>
+ <br>
+ Please make sure that the white reference is in
+ slot 1, then<br>
+ place sheet 1 of 4 on table, then<br>
+ hit return to continue, Esc to give up<br>
+ <br>
+ After hitting return you will be prompted to line up three squares
+ on the sheet, one at a time:<br>
+ <br>
+ Using the XY table controls, locate patch A1 with
+ the sight,<br>
+ then hit return to continue, Esc to give up<br>
+ <br>
+ On completing this, the instrument will commence reading each sheet.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;">
+ <h3><a name="spot"></a>Spot reading instruments</h3>
+ When used with a <span style="font-weight: bold;">DT22</span> or <span
+ style="font-weight: bold;">SpectroLino</span> or use the patch by
+ patch reading mode (<span style="font-weight: bold;">chartread -p</span>)
+ with the <span style="font-weight: bold;"></span> <span
+ style="font-weight: bold;">Eye-One Pro<span style="font-weight:
+ bold;"> </span></span>or <span style="font-weight: bold;">ColorMunki</span>
+ instrument, or use the external values mode (<span
+ style="font-weight: bold;">chartread -x</span>), chartread will
+ first establish communications with the instrument, and then set it
+ up ready to read the patches. The patches are typically labeled by
+ column A to ZZ, and row 1-999. Each patch will prompt:<br>
+ <br>
+ Ready to read patch 'XX' :<br>
+ <br>
+ where XX is the patch label, and this is followed by the available
+ options to navigate, read the strip, or finish.<br>
+ <br>
+ Place the instrument on the indicated patch, and trigger a reading
+ using one of the available methods (typically using the instrument
+ switch of pressing a key).<br>
+ <br>
+ There should be an audible prompt on a successful or failed reading.
+ <br>
+ <br>
+ Note that you may have to check that system alert sounds are enabled
+ and at a suitable volume to in order to hear the beep prompt. For
+ the Eye-One Pro and ColorMunki, a second beep will sound after a
+ successfully read strip, or a double beep will sound,
+ indicating a failure or warning that needs attention. See also the
+ note on Linux in <a href="Installing_Linux.html">installation</a>.<br>
+ <br>
+ If the patch is read successfully, the line will be completed with:<br>
+ <br>
+ Ready to read patch XX :<br>
+ Patch read OK<br>
+ <br>
+ If there is an error of some sort, a message will be issued, and you
+ will be asked whether to abort the chart reading, or retry the<br>
+ failed patch:<br>
+ <br>
+ Ready to read patch XX : read_strip
+ returned 'Strip misread' (Bad reading)<br>
+ <br>
+ Strip read failed due to misread<br>
+ Hit Esc to give up, any other key to retry:<br>
+ <br>
+ You can navigate the next patch to be read using the <span
+ style="font-weight: bold;">'f'</span> key to move forward and the
+ <span style="font-weight: bold;">'b'</span> keys<span
+ style="font-weight: bold;"></span><span style="font-weight: bold;"></span>
+ to move backwards, while <span style="font-weight: bold;">'F'</span>
+ and <span style="font-weight: bold;">'B'</span> will move forward
+ and backwards by 10 patches. The prompt will indicate whether this
+ patch has already been read or not, or whether all patches have been
+ read. You can also use <span style="font-weight: bold;">'n'</span>
+ to move forward to the next unread patch. When you are finished, use
+ the <span style="font-weight: bold;">'d'</span> to indicate that
+ you are done. You can choose to finish before all the patches are
+ read, and they will be saved to the .ti3 file. This is useful if you
+ are unable to finish the chart in one session, and you can later <span
+ style="text-decoration: underline;">resume</span> reading the
+ chart by using the <span style="font-weight: bold;">chartread -r</span>
+ flag.<br>
+ <br>
+ You can abort the whole process at any time by hitting Escape, and
+ the readings will not be saved.<br>
+ <br>
+ <span style="font-weight: bold;"></span>
+ <hr style="width: 100%; height: 2px;">
+ <h3><a name="displaytype"></a>Display Type<br>
+ </h3>
Many of the colorimeters have a <span style="font-weight: bold;">display @@ -780,360 +937,398 @@ - type</span> selection parameter. Depending on the instrument, this - may combine two related functions: 1) Changing the measurement mode - to suite either refresh-type, or non-refresh displays, and 2) - Changing the calibration to suite a particular displays spectral - characteristics.<br> - <br> - A refresh type display uses a technology that presents different - portions of the image at different times, doing so at a high enough - rate that this is normally imperceptible. This time varying - characteristic can interfere with measuring a display color unless - the instrument makes allowances for it, typically by making its - measurement period a multiple of the display refresh period. Display - types that <span style="font-weight: bold;">refresh</span> are CRT - (Cathode Ray Tube), Single chip DLP (Digital Light Processing) and - Plasma displays. An example of a <span style="font-weight: bold;">non-refresh</span> - display technology is LCD (Liquid Crystal Display), although is a - few cases the back-light illumination may have a low enough - frequency flicker to benefit from the refresh mode.<br> - <br> - Instruments in which the display type selection only changes the - measurement mode (i.e. i1d3), will typically have some other - independent option to set the calibration type. Simpler instruments - combine the measurement mode with a calibration selections, - typically refresh+CRT and non-refresh+LCD. Some instruments are a - hybrid of both (Spyder4), where the display type can select between - generic refresh/non-refresh that can then use a .CCSS to set the - calibration type, or a combined selection of non-refresh and a - particular display type.<br> - <br> - See <a - href="http://en.wikipedia.org/wiki/Comparison_of_display_technology">Comparison_of_display_technology</a> - for some background on different display technologies.<br> - <br> - <hr size="2" width="100%"><br> - <h3><a name="refreshmeasurement"></a>Refresh Rate Measurement</h3> - <p>Most of the colorimeters that have a refresh display type - selection, also have an ability to measure the refresh rate of a - display. Some of the spectrometers also have a display refresh - rate measurement capability when in an emissive measurement mode, - even though they don't use this to support a refresh display mode. - You can do a display refresh rate measurement in <a - href="spotread.html">spotread</a> using the <b>'F' </b>key. - The particular instruments have a range of accuracy when making - this measurement. A rough guide is as follows:<br> - <br> - </p> - <table border="1" cellpadding="2" cellspacing="2" height="230" - width="372"> - <tbody> - <tr> - <td valign="top"><b>Instrument</b></td> - <td valign="top"><b>Typical error in Hz.</b></td> - </tr> - <tr> - <td valign="top">DTP92<br> - </td> - <td valign="top">0.1<br> - </td> - </tr> - <tr> - <td valign="top">i1 Display 2<br> - </td> - <td valign="top">0.5<br> - </td> - </tr> - <tr> - <td valign="top">Spyder 2<br> - </td> - <td valign="top">0.7<br> - </td> - </tr> - <tr> - <td valign="top">Spyder 3<br> - </td> - <td valign="top">3<br> - </td> - </tr> - <tr> - <td valign="top">Spyder 4<br> - </td> - <td valign="top">3<br> - </td> - </tr> - <tr> - <td valign="top">i1 Display Pro<br> - </td> - <td valign="top">0.05<br> - </td> - </tr> - <tr> - <td valign="top">i1 Pro Spectro.<br> - </td> - <td valign="top">0.05<br> - </td> - </tr> - <tr> - <td valign="top">ColorMunki Spectro.<br> - </td> - <td valign="top">0.05<br> - </td> - </tr> - </tbody> - </table> - <p><br> - </p> - <hr style="width: 100%; height: 8px;"><br> - <span style="font-weight: bold;"></span><br> - <span style="font-weight: bold;"><a name="ColorMunki"></a><span - style="font-weight: bold;">ColorMunki </span>Design or Photo <span - style="font-weight: bold;">reflective/emissive spectrometer</span><br> - <br> - <img style="width: 272px; height: 243px;" alt="" title="ColorMunki - (White)" src="ColorMunki.jpg"> <br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">ColorMunki</span> <span - style="font-weight: bold;">Design or Photo </span>from <a - href="http://www.xrite.com/">X-Rite</a> is currently - available in two different packages from the manufacturer. These - packages differ in what features the manufacturers software - provides, as well as cosmetic differences between the instrument - (white and black). This comparison <a - href="http://www.colormunki.com/product/show?page=2">chart</a> - illustrates the differences. Used with Argyll, there are no - differences in operation of a ColorMunki instrument, irrespective of - which package it came with. The ColorMunki Design has the lowest - RRP, but the Photo package may be cheaper with discounting .<br> - <br> - <span style="font-weight: bold;">Limitations & Features:</span><br> - <br> - Unlike the Eye-One Pro, the ColorMunki is only available in a U.V. - Cut (ie. "Ultra Violet filtered") model. This means that it is not - suitable for use with the Fluorescent Whitener Additive - Compensation option in Argyll (see <a href="FWA.html">here</a> for - a discussion about what FWA compensation is).<br> - <br> - Like the Eye-One Pro, this instrument does support the <a - href="spotread.html#H">high resolution</a> spectral mode.<br> - <br> - <span style="font-weight: bold;">OS X and X-Rite drivers</span><br> - <br> - Please note the installation <a - href="Installing_OSX.html#ColorMunki">instructions</a>.<br> - <br> - <span style="font-weight: bold;">Tips & Tricks:<br> - <br> - </span>In handling the instrument when about to make a reading, be - very careful not to accidentally press the switch - it is large and - easily pressed by accident. A guide of some sort (ie. a plastic - ruler) can help a lot in keeping the instrument over a line - of patches. <br> - <br> - <span style="font-weight: bold;">Patch recognition:</span><br> - <br> - For the best chances of good patch recognition, the instrument - should be drawn smoothly and not too rapidly over the strip. (This - can be a little tricky due to the two small rubber feet on the - bottom of the device that aid its spot reading guide.) If there is a - misread, try slowing down slightly. Generally a higher quality set - of readings will result if slower scans are used, since there will - then be more samples averaged for each patch. <br> - <br> - In <a href="chartread.html">chartread</a>, the -<span - style="font-weight: bold;">T ratio</span> argument modifies the - patch consistency tolerance threshold for the ColorMunki. In - recognizing patches in a strip, the instrument takes multiple - readings as the strip is read, and then divide the readings up into - each patch. It then check the consistency of the multiple readings - corresponding to each patch, and reject the measurement if they are - too inconsistent. For some media (ie. a coarser screens, fabric - etc.) the default tolerance may be unreasonably tight, so the <span - style="font-weight: bold;">-T ratio</span> argument can be used to - modify this criteria. To loosen the tolerance, use a number greater - than 1.0 (ie. 1.5, 2.0). <br> - <br> - Note that <a href="printtarg.html">printtarg</a> provides the <a - href="printtarg.html#h">-h</a> option that allows the choice of - two different patch row widths with ColorMunki test charts. [Some - people have successfully used the i1Pro patch layout with the - ColorMunki, by making a guide to keep it over the much narrower - patchs.]<br> - <br> - <span style="font-weight: bold;"></span><br> - <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span><span - style="font-weight: bold;"></span><br> - <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span> - <hr style="width: 100%; height: 2px;"><span style="font-weight: - bold;"><br> - <a name="DTP20"></a></span><span style="font-weight: bold;">DTP20 - "Pulse" reflective spectrometer<br> - <br> - </span><span style="font-weight: bold;"><img title="DTP20" alt="" - src="DTP20.jpg" style="width: 304px; height: 210px;"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">DTP20</span> from <a - href="http://www.xrite.com/">X-Rite</a> was discontinued during - 2007, but may still be available from old stock or second hand. <br> - <br> - <span style="font-weight: bold;">Special features:</span><br> - <br> - The <span style="font-weight: bold;">DTP20</span> has a couple of - unique features that Argyll can take advantage of. One is that it - can operate un-tethered (off line). A whole chart can be read - un-tethered by first clearing any previous readings in the - instrument, then reading the chart TID strip, before reading all the - other strips. The instrument can then be connected up to <span - style="font-weight: bold;">chartread</span>, which will recognize - the chart, and download all the measurements.<br> - If there is no chart in the instrument when chartread connects to - it, then it will use the strip by strip tethered mode, just like the - other strip instruments. If the right number of spot readings are - present in the instrument, these will be used by <span - style="font-weight: bold;">chartread</span> too.<br> - <br> - Un-tethered spot measurements can also be read in using <span - style="font-weight: bold;">spotread</span>, which will notice the - stored readings, and offer to print them out, or they can be - ignored, and tethered readings taken. This will clear any saved spot - readings.<br> - <br> - <span style="font-weight: bold;">Note</span> that tethered (on-line) - strip reading will only work if the firmware in the device is - version 1.03 or greater. You can check the firmware version by - running with the verbose option: <span style="font-weight: bold;">-v<br> - <br> - Chart printing:<br> - <span style="font-weight: bold;"><br> - </span></span>Because the DTP20 measures exact distances using the - markings on its ruler, it's critical that the chart be printed out - exactly the right size. If the chart gets re-sized at all in the - process of printing it, the DTP20 is likely to fail in reading it. - If you have a problem with this, you might want to increase the page - margins using the <span style="font-weight: bold;">printtarg -m</span> - parameter, or find a printing path that preserves the test chart - size correctly.<br> - <br> - <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span><span - style="font-weight: bold;">Operation:<br> - <br> - </span>When reading in tethered (on-line) mode, that the instrument - takes <span style="font-weight: bold;">several seconds</span> to - download the measurements after each strip, and that the indicator - will be in "rainbow" mode while this occurs. <span - style="text-decoration: underline;">Wait</span> until the - indicator turns solid green again before starting to measure the - next strip.<br> - <br> - To <span style="font-weight: bold;">reset</span> the instrument and - clear any stored readings: press the button three times in quick - succession. The indicator will turn solid blue. Then hold the button - down until the instrument beeps and the indicator goes out. Release - the button and the indicator should flash then return to solid green - (ready).<br> - <br> - To <span style="font-weight: bold;">calibrate</span> the - instrument, place it on its calibration tile, then press the button - three times in quick succession.The indicator will turn solid blue. - Click the button another three times in quick succession, and the - indicator should turn yellow. Then hold the button down until the - instrument beeps and the indicator goes out. Release the button and - the instrument should flash and then turn solid green.<br> - <br> - If the chart is particularly <span style="font-weight: bold;">small</span>, - the patches may end up printed very close to the edge of the chart, - and therefore it may be difficult to confine your scan to the chart, - and passing<br> - the instrument over the edge of the chart may prevent it reading - successfully. One way of working around this is to place the chart - on a larger piece of paper of the same type.<br> - <br> - The <span style="font-weight: bold;">speed</span> of scan can be - quite critical with this instrument. In particular, it doesn't work - very well if the scan is too <span style="font-weight: bold;">slow</span>. - You don't want to go too fast either, as this reduces the number of - samples per patch.<br> - <br> - <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span><span - style="font-weight: bold;"></span><br> - <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span> - <hr style="width: 100%; height: 2px;"><span style="font-weight: - bold;"><br> - <a name="DTP22"></a></span><span style="font-weight: bold;">DTP22 - Digital Swatchbook reflective spectrometer</span><br> - <span style="font-weight: bold;"><br> - <img alt="" src="DTP22.jpg" style="width: 222px; height: 193px;"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">DTP22</span> from <a - href="http://www.xrite.com/">X-Rite</a> is a discontinued - instrument. It may still be available second hand. It is - capable of reading colored patches one at a time.<br> - <br> - <br> - <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span> - <hr style="width: 100%; height: 2px;"><span style="font-weight: - bold;"><br> - <a name="DTP41"></a>DTP41 reflective, DTP41T - reflective/transmissive spectrometers<br> - <br> - <img alt="" src="DTP41.jpg" style="width: 263px; height: 298px;"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">DTP41</span> and <span - style="font-weight: bold;">DTP41T</span> from <a - href="http://www.xrite.com/">X-Rite</a> is a discontinued - instrument. It may still be available second hand. <br> - <br> - The series II instruments (<span style="font-weight: bold;">DTP41B</span> - and <span style="font-weight: bold;">DTP41TB</span>) offer both - serial and USB connection. Note that currently only serial operation - using Argyll is possible with these instruments.<br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <a name="dtp51"></a><span style="font-weight: bold;">DTP51 - reflective colorimeter<br> - <br> - <img alt="" src="DTP51.jpg" style="width: 263px; height: 223px;"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">DTP51</span> from <a - href="http://www.xrite.com/">X-Rite</a> is a discontinued - instrument. It may still be available second hand. <br> - <br> - <span style="font-weight: bold;">Operation:</span><br> - <span style="font-weight: bold;"><span style="font-weight: bold;"><br> - </span></span>The DTP51's switch is triggered by inserting a strip - into the slot.<br> - <br> - <br> - <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span> - <hr style="width: 100%; height: 2px;"><span style="font-weight: - bold;"><br> - <a name="DTP92"></a>DTP92 CRT display colorimeter<br> - <br> - <img alt="" src="DTP92.jpg" style="width: 223px; height: 180px;"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">DTP92</span><span - style="font-weight: bold;"></span> from <a - href="http://www.xrite.com/">X-Rite</a> is a discontinued - instrument. It may still be available second hand. It will - only read CRT technology displays.<br> - <br> - <span style="font-weight: bold;">Operation:</span><br> - <br> - The Display Selections for this instrument are:<br> - <br> + + + + + + + + + + + +
+ type</span> selection parameter. Depending on the instrument, this
+ may combine two related functions: 1) Changing the measurement mode
+ to suite either refresh-type, or non-refresh displays, and 2)
+ Changing the calibration to suite a particular displays spectral
+ characteristics.<br>
+ <br>
+ A refresh type display uses a technology that presents different
+ portions of the image at different times, doing so at a high enough
+ rate that this is normally imperceptible. This time varying
+ characteristic can interfere with measuring a display color unless
+ the instrument makes allowances for it, typically by making its
+ measurement period a multiple of the display refresh period. Display
+ types that <span style="font-weight: bold;">refresh</span> are CRT
+ (Cathode Ray Tube), Single chip DLP (Digital Light Processing) and
+ Plasma displays. An example of a <span style="font-weight: bold;">non-refresh</span>
+ display technology is LCD (Liquid Crystal Display), although is a
+ few cases the back-light illumination may have a low enough
+ frequency flicker to benefit from the refresh mode.<br>
+ <br>
+ Instruments in which the display type selection only changes the
+ measurement mode (i.e. i1d3), will typically have some other
+ independent option to set the calibration type. Simpler instruments
+ combine the measurement mode with a calibration selections,
+ typically refresh+CRT and non-refresh+LCD. Some instruments are a
+ hybrid of both (Spyder4), where the display type can select between
+ generic refresh/non-refresh that can then use a .CCSS to set the
+ calibration type, or a combined selection of non-refresh and a
+ particular display type.<br>
+ <br>
+ See <a
+ href="http://en.wikipedia.org/wiki/Comparison_of_display_technology">Comparison_of_display_technology</a>
+ for some background on different display technologies.<br>
+ <br>
+ <hr size="2" width="100%"><br>
+ <h3><a name="refreshmeasurement"></a>Refresh Rate Measurement</h3>
+ <p>Most of the colorimeters that have a refresh display type
+ selection, also have an ability to measure the refresh rate of a
+ display. Some of the spectrometers also have a display refresh
+ rate measurement capability when in an emissive measurement mode,
+ even though they don't use this to support a refresh display mode.
+ You can do a display refresh rate measurement in <a
+ href="spotread.html">spotread</a> using the <b>'F' </b>key.
+ The particular instruments have a range of accuracy when making
+ this measurement. A rough guide is as follows:<br>
+ <br>
+ </p>
+ <table border="1" height="230" width="372" cellpadding="2"
+ cellspacing="2">
+ <tbody>
+ <tr>
+ <td valign="top"><b>Instrument</b></td>
+ <td valign="top"><b>Typical error in Hz.</b></td>
+ </tr>
+ <tr>
+ <td valign="top">spectrobos 1211/1201<br>
+ </td>
+ <td valign="top">0.05<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">DTP92<br>
+ </td>
+ <td valign="top">0.1<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">i1 Display 2<br>
+ </td>
+ <td valign="top">0.5<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">Spyder 2<br>
+ </td>
+ <td valign="top">0.7<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">Spyder 3<br>
+ </td>
+ <td valign="top">3<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">Spyder 4<br>
+ </td>
+ <td valign="top">3<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">i1 Display Pro<br>
+ </td>
+ <td valign="top">0.05<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">i1 Pro Spectro.<br>
+ </td>
+ <td valign="top">0.05<br>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">ColorMunki Spectro.<br>
+ </td>
+ <td valign="top">0.05<br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p><br>
+ </p>
+ <hr size="2" width="100%">
+ <p><span style="font-weight: bold;"><a name="specbos"></a><span
+ 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">
+ <p><span style="font-weight: bold;"><br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">specbos 1211</span><span
+ style="font-weight: bold;"> </span>and <b>1201</b>from <a
+ 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>
+ </p>
+ <hr size="2" width="100%">
+ <p><br>
+ </p>
+ <span style="font-weight: bold;"></span><br>
+ <span style="font-weight: bold;"><a name="ColorMunki"></a><span
+ style="font-weight: bold;">ColorMunki </span>Design or Photo <span
+ style="font-weight: bold;">reflective/emissive spectrometer</span><br>
+ <br>
+ <img style="width: 272px; height: 243px;" alt="" title="ColorMunki
+ (White)" src="ColorMunki.jpg"> <br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">ColorMunki</span> <span
+ style="font-weight: bold;">Design or Photo </span>from <a
+ href="http://www.xrite.com/">X-Rite</a> is currently
+ available in two different packages from the manufacturer. These
+ packages differ in what features the manufacturers software
+ provides, as well as cosmetic differences between the instrument
+ (white and black). This comparison <a
+ href="http://www.colormunki.com/product/show?page=2">chart</a>
+ illustrates the differences. Used with Argyll, there are no
+ differences in operation of a ColorMunki instrument, irrespective of
+ which package it came with. The ColorMunki Design has the lowest
+ RRP, but the Photo package may be cheaper with discounting .<br>
+ <br>
+ <span style="font-weight: bold;">Limitations & Features:</span><br>
+ <br>
+ Unlike the Eye-One Pro, the ColorMunki is only available in a U.V.
+ Cut (ie. "Ultra Violet filtered") model. This means that it is not
+ suitable for use with the Fluorescent Whitener Additive
+ Compensation option in Argyll (see <a href="FWA.html">here</a> for
+ a discussion about what FWA compensation is).<br>
+ <br>
+ Like the Eye-One Pro, this instrument does support the <a
+ href="spotread.html#H">high resolution</a> spectral mode.<br>
+ <br>
+ <span style="font-weight: bold;">OS X and X-Rite drivers</span><br>
+ <br>
+ Please note the installation <a
+ href="Installing_OSX.html#ColorMunki">instructions</a>.<br>
+ <br>
+ <span style="font-weight: bold;">Tips & Tricks:<br>
+ <br>
+ </span>In handling the instrument when about to make a reading, be
+ very careful not to accidentally press the switch - it is large and
+ easily pressed by accident. A guide of some sort (ie. a plastic
+ ruler) can help a lot in keeping the instrument over a line
+ of patches. <br>
+ <br>
+ <span style="font-weight: bold;">Patch recognition:</span><br>
+ <br>
+ For the best chances of good patch recognition, the instrument
+ should be drawn smoothly and not too rapidly over the strip. (This
+ can be a little tricky due to the two small rubber feet on the
+ bottom of the device that aid its spot reading guide.) If there is a
+ misread, try slowing down slightly. Generally a higher quality set
+ of readings will result if slower scans are used, since there will
+ then be more samples averaged for each patch. <br>
+ <br>
+ In <a href="chartread.html">chartread</a>, the -<span
+ style="font-weight: bold;">T ratio</span> argument modifies the
+ patch consistency tolerance threshold for the ColorMunki. In
+ recognizing patches in a strip, the instrument takes multiple
+ readings as the strip is read, and then divide the readings up into
+ each patch. It then check the consistency of the multiple readings
+ corresponding to each patch, and reject the measurement if they are
+ too inconsistent. For some media (ie. a coarser screens, fabric
+ etc.) the default tolerance may be unreasonably tight, so the <span
+ style="font-weight: bold;">-T ratio</span> argument can be used to
+ modify this criteria. To loosen the tolerance, use a number greater
+ than 1.0 (ie. 1.5, 2.0). <br>
+ <br>
+ Note that <a href="printtarg.html">printtarg</a> provides the <a
+ href="printtarg.html#h">-h</a> option that allows the choice of
+ two different patch row widths with ColorMunki test charts. [Some
+ people have successfully used the i1Pro patch layout with the
+ ColorMunki, by making a guide to keep it over the much narrower
+ patchs.]<br>
+ <br>
+ <span style="font-weight: bold;"></span><br>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span><span
+ style="font-weight: bold;"></span><br>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span>
+ <hr style="width: 100%; height: 2px;"><span style="font-weight:
+ bold;"><br>
+ <a name="DTP20"></a></span><span style="font-weight: bold;">DTP20
+ "Pulse" reflective spectrometer<br>
+ <br>
+ </span><span style="font-weight: bold;"><img title="DTP20" alt=""
+ src="DTP20.jpg" style="width: 304px; height: 210px;"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">DTP20</span> from <a
+ href="http://www.xrite.com/">X-Rite</a> was discontinued during
+ 2007, but may still be available from old stock or second hand. <br>
+ <br>
+ <span style="font-weight: bold;">Special features:</span><br>
+ <br>
+ The <span style="font-weight: bold;">DTP20</span> has a couple of
+ unique features that Argyll can take advantage of. One is that it
+ can operate un-tethered (off line). A whole chart can be read
+ un-tethered by first clearing any previous readings in the
+ instrument, then reading the chart TID strip, before reading all the
+ other strips. The instrument can then be connected up to <span
+ style="font-weight: bold;">chartread</span>, which will recognize
+ the chart, and download all the measurements.<br>
+ If there is no chart in the instrument when chartread connects to
+ it, then it will use the strip by strip tethered mode, just like the
+ other strip instruments. If the right number of spot readings are
+ present in the instrument, these will be used by <span
+ style="font-weight: bold;">chartread</span> too.<br>
+ <br>
+ Un-tethered spot measurements can also be read in using <span
+ style="font-weight: bold;">spotread</span>, which will notice the
+ stored readings, and offer to print them out, or they can be
+ ignored, and tethered readings taken. This will clear any saved spot
+ readings.<br>
+ <br>
+ <span style="font-weight: bold;">Note</span> that tethered (on-line)
+ strip reading will only work if the firmware in the device is
+ version 1.03 or greater. You can check the firmware version by
+ running with the verbose option: <span style="font-weight: bold;">-v<br>
+ <br>
+ Chart printing:<br>
+ <span style="font-weight: bold;"><br>
+ </span></span>Because the DTP20 measures exact distances using the
+ markings on its ruler, it's critical that the chart be printed out
+ exactly the right size. If the chart gets re-sized at all in the
+ process of printing it, the DTP20 is likely to fail in reading it.
+ If you have a problem with this, you might want to increase the page
+ margins using the <span style="font-weight: bold;">printtarg -m</span>
+ parameter, or find a printing path that preserves the test chart
+ size correctly.<br>
+ <br>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span><span
+ style="font-weight: bold;">Operation:<br>
+ <br>
+ </span>When reading in tethered (on-line) mode, that the instrument
+ takes <span style="font-weight: bold;">several seconds</span> to
+ download the measurements after each strip, and that the indicator
+ will be in "rainbow" mode while this occurs. <span
+ style="text-decoration: underline;">Wait</span> until the
+ indicator turns solid green again before starting to measure the
+ next strip.<br>
+ <br>
+ To <span style="font-weight: bold;">reset</span> the instrument and
+ clear any stored readings: press the button three times in quick
+ succession. The indicator will turn solid blue. Then hold the button
+ down until the instrument beeps and the indicator goes out. Release
+ the button and the indicator should flash then return to solid green
+ (ready).<br>
+ <br>
+ To <span style="font-weight: bold;">calibrate</span> the
+ instrument, place it on its calibration tile, then press the button
+ three times in quick succession.The indicator will turn solid blue.
+ Click the button another three times in quick succession, and the
+ indicator should turn yellow. Then hold the button down until the
+ instrument beeps and the indicator goes out. Release the button and
+ the instrument should flash and then turn solid green.<br>
+ <br>
+ If the chart is particularly <span style="font-weight: bold;">small</span>,
+ the patches may end up printed very close to the edge of the chart,
+ and therefore it may be difficult to confine your scan to the chart,
+ and passing<br>
+ the instrument over the edge of the chart may prevent it reading
+ successfully. One way of working around this is to place the chart
+ on a larger piece of paper of the same type.<br>
+ <br>
+ The <span style="font-weight: bold;">speed</span> of scan can be
+ quite critical with this instrument. In particular, it doesn't work
+ very well if the scan is too <span style="font-weight: bold;">slow</span>.
+ You don't want to go too fast either, as this reduces the number of
+ samples per patch.<br>
+ <br>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span><span
+ style="font-weight: bold;"></span><br>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span>
+ <hr style="width: 100%; height: 2px;"><span style="font-weight:
+ bold;"><br>
+ <a name="DTP22"></a></span><span style="font-weight: bold;">DTP22
+ Digital Swatchbook reflective spectrometer</span><br>
+ <span style="font-weight: bold;"><br>
+ <img alt="" src="DTP22.jpg" style="width: 222px; height: 193px;"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">DTP22</span> from <a
+ href="http://www.xrite.com/">X-Rite</a> is a discontinued
+ instrument. It may still be available second hand. It is
+ capable of reading colored patches one at a time.<br>
+ <br>
+ <br>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span>
+ <hr style="width: 100%; height: 2px;"><span style="font-weight:
+ bold;"><br>
+ <a name="DTP41"></a>DTP41 reflective, DTP41T
+ reflective/transmissive spectrometers<br>
+ <br>
+ <img alt="" src="DTP41.jpg" style="width: 263px; height: 298px;"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">DTP41</span> and <span
+ style="font-weight: bold;">DTP41T</span> from <a
+ href="http://www.xrite.com/">X-Rite</a> is a discontinued
+ instrument. It may still be available second hand. <br>
+ <br>
+ The series II instruments (<span style="font-weight: bold;">DTP41B</span>
+ and <span style="font-weight: bold;">DTP41TB</span>) offer both
+ serial and USB connection. Note that currently only serial operation
+ using Argyll is possible with these instruments.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <a name="dtp51"></a><span style="font-weight: bold;">DTP51
+ reflective colorimeter<br>
+ <br>
+ <img alt="" src="DTP51.jpg" style="width: 263px; height: 223px;"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">DTP51</span> from <a
+ href="http://www.xrite.com/">X-Rite</a> is a discontinued
+ instrument. It may still be available second hand. <br>
+ <br>
+ <span style="font-weight: bold;">Operation:</span><br>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"><br>
+ </span></span>The DTP51's switch is triggered by inserting a strip
+ into the slot.<br>
+ <br>
+ <br>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span>
+ <hr style="width: 100%; height: 2px;"><span style="font-weight:
+ bold;"><br>
+ <a name="DTP92"></a>DTP92 CRT display colorimeter<br>
+ <br>
+ <img alt="" src="DTP92.jpg" style="width: 223px; height: 180px;"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">DTP92</span><span
+ style="font-weight: bold;"></span> from <a
+ href="http://www.xrite.com/">X-Rite</a> is a discontinued
+ instrument. It may still be available second hand. It will
+ only read CRT technology displays.<br>
+ <br>
+ <span style="font-weight: bold;">Operation:</span><br>
+ <br>
+ The Display Selections for this instrument are:<br>
+ <br>
<span style="font-weight: bold;">c</span> @@ -1156,32 +1351,44 @@ - CRT display A Cathode Ray - Tube display, that is of the Refresh type [Default, CB2].<br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <span style="font-weight: bold;"><a name="DTP94"></a>DTP94, </span><font - size="-1">"Optix XR"</font> or "Optix XR2" or "Optix Pro" <span - style="font-weight: bold;">display colorimetrers</span><br> - <span style="font-weight: bold;"><br> - <img title="DTP94" alt="" src="DTP94.jpg" style="width: 138px; - height: 171px;"> - <img alt="" title="Optix XR/Pro" src="moxxr.jpg" - style="width: 155px; height: 190px;"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">DTP94 </span>from <a - href="http://www.xrite.com/">X-Rite</a> is a discontinued - instrument, although it is still being supplied to OEMs. It - may still be available as old stock, or second hand. It was sold as - an instrument without software as the DTP94, and packaged with - software from the manufacturer as the "Optix XR" range.<br> - <br> - <span style="font-weight: bold;">Operation:</span><br> - <br> - The Display Selections for this instrument are:<br> - <br> + + + + + + + + + + + +
+ CRT display A Cathode Ray
+ Tube display, that is of the Refresh type [Default, CB2].<br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <span style="font-weight: bold;"><a name="DTP94"></a>DTP94, </span><font
+ size="-1">"Optix XR"</font> or "Optix XR2" or "Optix Pro" <span
+ style="font-weight: bold;">display colorimetrers</span><br>
+ <span style="font-weight: bold;"><br>
+ <img title="DTP94" alt="" src="DTP94.jpg" style="width: 138px;
+ height: 171px;">
+ <img alt="" title="Optix XR/Pro" src="moxxr.jpg"
+ style="width: 155px; height: 190px;"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">DTP94 </span>from <a
+ href="http://www.xrite.com/">X-Rite</a> is a discontinued
+ instrument, although it is still being supplied to OEMs. It
+ may still be available as old stock, or second hand. It was sold as
+ an instrument without software as the DTP94, and packaged with
+ software from the manufacturer as the "Optix XR" range.<br>
+ <br>
+ <span style="font-weight: bold;">Operation:</span><br>
+ <br>
+ The Display Selections for this instrument are:<br>
+ <br>
<span style="font-weight: bold;">l</span> @@ -1199,8 +1406,20 @@ - LCD display A Liquid - Crystal Display, that is of the Non-Refresh type [default, CB1].<br> + + + + + + + + + + + +
+ LCD display A Liquid
+ Crystal Display, that is of the Non-Refresh type [default, CB1].<br>
<span style="font-weight: bold;">c</span> @@ -1223,23 +1442,35 @@ - CRT display A Cathode Ray - Tube display, that is of the Refresh type [CB2].<br> - <b>g</b> - Generic - Generic - display [CB3]<br> - <br> - <br> - <span style="font-weight: bold;"></span> - <hr style="width: 100%; height: 2px;"><span style="font-weight: - bold;"><br> - <a name="sl"></a>Spectrolino reflective/emissive spectrometer<br> - <br> - <img alt="" src="sl.jpg" style="width: 239px; height: 200px;"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> + + + + + + + + + + + +
+ CRT display A Cathode Ray
+ Tube display, that is of the Refresh type [CB2].<br>
+ <b>g</b>
+ Generic
+ Generic
+ display [CB3]<br>
+ <br>
+ <br>
+ <span style="font-weight: bold;"></span>
+ <hr style="width: 100%; height: 2px;"><span style="font-weight:
+ bold;"><br>
+ <a name="sl"></a>Spectrolino reflective/emissive spectrometer<br>
+ <br>
+ <img alt="" src="sl.jpg" style="width: 239px; height: 200px;"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
</span>The <span style="font-weight: bold;">Spectrolino </span>from Gretag @@ -1263,220 +1494,237 @@ Gretag - MacBeth (Now X-Rite) is a discontinued instrument. It is often - available second hand. If buying it second hand, make sure it comes - with all it's accessories, including white reference, spot reading - adapter, display reading adapters, filters (UV, polarizing, D65), - serial cable adapter and power supply.<br> - <span style="font-weight: bold;"><br> - </span> - <hr style="width: 100%; height: 2px;"><span style="font-weight: - bold;"><br> - <a name="ss"></a>SpectroScan reflective/emissive and SpectroScanT - reflective/emissive/transmissive spectrometers<br> - <br> - <img style="width: 336px; height: 294px;" alt="" src="ss.jpg"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">SpectroScan</span> and - <span style="font-weight: bold;">SpectroScanT</span> from Gretag - MacBeth (Now X-Rite) is a discontinued instrument. It is the - combination of an X-Y table and the <span style="font-weight: - bold;">Spectrolino</span> instrument. The <span - style="font-weight: bold;">SpectroScanT</span> is capable of - measuring transparency. It is often available second hand. If buying - it second hand, make sure it comes with all it's accessories, - including white reference, spot reading adapter, display reading - adapters, filters (UV, polarizing, D65) and power supply.<br> - <br> - If measuring transparencies using a SpectroScanT, the <b>Enter</b> - key on the instrument may be used to trigger each reading. It will - be recognized after each previous reading has been completed.<br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <br> - <span style="font-weight: bold;"><a name="i1p2"></a>Eye-One Pro2:</span><br> - <img style=" width: 357px; height: 234px;" alt="Eye-One Pro 2" - src="i1pro2.jpg"><br> - <br> - There is support for some of the new features of the Eye-One Pro2 - (also known as the Eye-One Pro Rev E), in particular the Rev E - measurement mode, spectrometer stray light reduction, wavelength - calibration, and improved black level tracking. This new support can - be disabled and an Eye-One Pro2 operated in legacy mode by setting - the environment variable ARGYLL_DISABLE_I1PRO2_DRIVER. See <a - href="file:///D:/src/argyll/doc/instruments.html#i1p">Eye-One Pro - reflective/emissive spectrometer</a><span style="font-weight: - bold;"> </span>below for details on the operation of this type of - instrument.<br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <span style="font-weight: bold;"><a name="i1p"></a>Eye-One Pro and - Eye-One Pro2 reflective/emissive spectrometer<br> - <br> - <img alt="" src="i1p.jpg" style="width: 347px; height: 234px;"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">Eye-One Pro</span> from - <a href="http://www.xrite.com/">X-Rite</a> (was Gretag MacBeth) is - available in two packages from the manufacturer. These packages - differ partly in what accessories come with the instrument, but - primarily in what features the manufacturers software provides. This - comparison <a - href="http://www.xrite.com/product_overview.aspx?ID=812">chart</a> - illustrates the differences. Used with Argyll, there are no - differences in operation of an Eye-One Pro instrument, irrespective - of which package it came with. The lowest cost package is the <a - href="http://www.xrite.com/product_overview.aspx?ID=1461">i1 Basic - Pro</a>.<br> - <br> - The EFI ES-1000 (which is a re-badged Eye-One Pro) is also reported - to work with Argyll.<br> - <br> - Unless you know what you're doing, and have a very specific reason - to buy an instrument fitted with a UV (Ultra Violet) filter, make - sure that you buy an instrument without the filter. A UV filtered - instrument can't deal intelligently with FWA (Fluorescent Whitener - Additive) effects in paper. (Look <a href="FWA.html">here</a> for - more information about FWA compensation.) Using FWA compensation you - can make measurements using ISO 13655:2009 M0, M1 and M2 conditions. - The M2 condition emulates a UV cut instrument.<br> - <br> - There have been four revisions of the Eye-One Pro, Rev. A, B, D and - E (AKA Eye-One Pro2). The rev B, D and E are capable of sampling - twice as fast as the Rev. A version of the instrument, and are also - available with an ambient light reading capability.<br> - <br> - <span style="font-weight: bold;">NOTE</span> for those running on - older versions of Linux with a Rev. D, there was a problem with the - Linux USB stack that causes the instrument to stop working once it - has been used. The only workaround is to unplug and replug the - instrument in again, whereupon it can be used one time again. A fix - for this problem was in the Linux 2.6.26 kernel release.<br> - <br> - See also <a href="i1proDriver.html">How can I have confidence in - the i1pro Driver ?</a><br> - <br> - <span style="font-weight: bold;">Patch recognition:</span><br> - <br> - For the best chances of good patch recognition, the instrument - should be drawn smoothly and not too rapidly over the strip. If - there is a misread, try slowing down slightly. The Rev A and B. - instruments have a slower sampling rate than the latter revision - instruments, and hence must be used a bit more slowly. Generally a - higher quality set of readings will result if slower scans are used, - since there will then be more samples averaged for each patch.<br> - <br> - In <a href="chartread.html">chartread</a>, the -<span - style="font-weight: bold;">T ratio</span> argument modifies the - patch consistency tolerance threshold for the Eye-One Pro. In - recognizing patches in a strip, the instrument takes multiple - readings as the strip is read, and then divide the readings up into - each patch. It then check the consistency of the multiple readings - corresponding to each patch, and reject the measurement if they are - too inconsistent. For some media (ie. a coarser screens, fabric - etc.) the default tolerance may be unreasonably tight, so the <span - style="font-weight: bold;">-T ratio</span> argument can be used to - modify this criteria. To loosen the tolerance, use a number greater - than 1.0 (ie. 1.5, 2.0). <span style="font-weight: bold;"></span><br> - <br> - <span style="font-weight: bold;">Special features:</span><br> - <br> - A feature unique to Argyll when used with the Eye-One Pro, is the - high resolution spectral mode. This returns spectral measurements at - 3.333 nm spacing, rather than the default 10nm spacing, and also - extends the range of wavelengths very slightly. This high resolution - may assist in giving better accuracy for "peaky" emissive sources - such as illuminants and displays. The high resolution mode is - selected by using the <span style="font-weight: bold;">-H</span> - flag on the command line to <span style="font-weight: bold;">dispcal</span>, - <span style="font-weight: bold;">dispread</span>, <span - style="font-weight: bold;">chartread</span>, and <span - style="font-weight: bold;">spotread</span>. It can also be toggled - on and off within <span style="font-weight: bold;">spotread</span> - using the <span style="font-weight: bold;">h</span> key. The - extended range down to 350nm may give some information about an - illuminants ultra violet content, although the accuracy of the - readings between 350-380, and 730-740nm should not be relied upon.<br> - <br> - <img alt="High res. and standard res. spectrum." - src="Fluorescent.jpg" style="width: 750px; height: 375px;"><br> - <br> - <img alt="C.R.T high res. and standard res. spectrum." - src="CRTspectrum.jpg" style="width: 750px; height: 375px;"><br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <span style="font-weight: bold;"><a name="i1m"></a>Eye-One Monitor - emissive spectrometer<br> - <br> - <img alt="" src="i1m.jpg" style="width: 347px; height: 234px;"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">Eye-One Monitor</span> - from <a href="http://www.xrite.com/">X-Rite</a> (was Gretag - MacBeth) is a discontinued instrument. It was a lower cost version - of the <span style="font-weight: bold;">Eye-One Pro</span> without - reflective measurement capability. See <a href="#i1p">Eye-One Pro - reflective/emissive spectrometer</a><span style="font-weight: - bold;"> </span>for details on the operation of this instrument.<br> - <br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <span style="font-weight: bold;"><a name="i1d"></a>Eye-One Display - 1, Eye-One Display 2, Eye-One Display LT, ColorMunki Create, - ColorMunki Smile colorimeters,<br> - <br> - <img style=" width: 124px; height: 168px;" alt="ColorMunki Smile" - src="Smile.jpg"><img alt="Eye-One Display 2" src="i1d.jpg" - style="width: 145px; height: 168px;"> <img style="width: 133px; - height: 168px;" alt="ColorMunki Create" - src="ColorMunkiCreate.jpg"><br> - <br> - Instrument Availability:<br> - <br> - </span>The <span style="font-weight: bold;">ColorMunki Smile</span> - colorimeter is a currently available instrument.<br> - The <span style="font-weight: bold;">Eye-One Display LT</span> and - <span style="font-weight: bold;">Eye-One Display 2</span> are - discontinued products, although they may still be available from - some retailers, second hand, and may still be shipped with some - displays as part of their calibration capability.<br> - The <span style="font-weight: bold;">ColorMunki Create</span> - colorimeter is a discontinued product, although they may still be - available from some retailers or second hand,can also be used. They - will appear as an i1Display2 colorimeter.<br> - The <span style="font-weight: bold;">HP DreamColor</span> - colorimeter can also be used, and will appear as an i1Display2 - colorimeter [note that it is calibrated for the DreamColor display].<br> - The <span style="font-weight: bold;">HP APS</span> (Advanced - Profiling Solution) colorimeter is also reported to work, and will - appear as an i1Display2.<br> - The <span style="font-weight: bold;">CalMAN X2</span> colorimeter - is also reported to work, and will appear as an i1Display2 - colorimeter.<br> - The <span style="font-weight: bold;">Lacie Blue Eye</span> <span - style="font-weight: bold;"></span> colorimeter is also reported to - work, and will appear as an i1Display2 colorimeter.<br> - <br> - <span style="font-weight: bold;"></span>The <span - style="font-weight: bold;">Eye-One Display 1</span> is a - discontinued instrument. <br> - <br> - The Eye-One Display LT came with a less expensive<span - style="text-decoration: underline;"></span> package with more - limited software from the manufacture.<br> - The Eye-One Display 2 package came with more software - features, but the instruments are virtually identical, and - will operate identically using Argyll.<br> - The ColorMunki Create<span style="text-decoration: underline;"></span> - package is another alternative, and will operate identically using - Argyll.<br> - <br> - <span style="font-weight: bold;">Operation:</span><br> - <br> + + + + + + + + + + + +
+ MacBeth (Now X-Rite) is a discontinued instrument. It is often
+ available second hand. If buying it second hand, make sure it comes
+ with all it's accessories, including white reference, spot reading
+ adapter, display reading adapters, filters (UV, polarizing, D65),
+ serial cable adapter and power supply.<br>
+ <span style="font-weight: bold;"><br>
+ </span>
+ <hr style="width: 100%; height: 2px;"><span style="font-weight:
+ bold;"><br>
+ <a name="ss"></a>SpectroScan reflective/emissive and SpectroScanT
+ reflective/emissive/transmissive spectrometers<br>
+ <br>
+ <img style="width: 336px; height: 294px;" alt="" src="ss.jpg"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">SpectroScan</span> and
+ <span style="font-weight: bold;">SpectroScanT</span> from Gretag
+ MacBeth (Now X-Rite) is a discontinued instrument. It is the
+ combination of an X-Y table and the <span style="font-weight:
+ bold;">Spectrolino</span> instrument. The <span
+ style="font-weight: bold;">SpectroScanT</span> is capable of
+ measuring transparency. It is often available second hand. If buying
+ it second hand, make sure it comes with all it's accessories,
+ including white reference, spot reading adapter, display reading
+ adapters, filters (UV, polarizing, D65) and power supply.<br>
+ <br>
+ If measuring transparencies using a SpectroScanT, the <b>Enter</b>
+ key on the instrument may be used to trigger each reading. It will
+ be recognized after each previous reading has been completed.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <br>
+ <span style="font-weight: bold;"><a name="i1p2"></a>Eye-One Pro2:</span><br>
+ <img style=" width: 357px; height: 234px;" alt="Eye-One Pro 2"
+ src="i1pro2.jpg"><br>
+ <br>
+ There is support for some of the new features of the Eye-One Pro2
+ (also known as the Eye-One Pro Rev E), in particular the Rev E
+ measurement mode, spectrometer stray light reduction, wavelength
+ calibration, and improved black level tracking. This new support can
+ be disabled and an Eye-One Pro2 operated in legacy mode by setting
+ the environment variable ARGYLL_DISABLE_I1PRO2_DRIVER. See <a
+ href="instruments.html#i1p">Eye-One Pro reflective/emissive
+ spectrometer</a><span style="font-weight: bold;"> </span>below
+ for details on the operation of this type of instrument.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <span style="font-weight: bold;"><a name="i1p"></a>Eye-One Pro and
+ Eye-One Pro2 reflective/emissive spectrometer<br>
+ <br>
+ <img alt="" src="i1p.jpg" style="width: 347px; height: 234px;"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">Eye-One Pro</span> from
+ <a href="http://www.xrite.com/">X-Rite</a> (was Gretag MacBeth) is
+ available in two packages from the manufacturer. These packages
+ differ partly in what accessories come with the instrument, but
+ primarily in what features the manufacturers software provides. This
+ comparison <a
+ href="http://www.xrite.com/product_overview.aspx?ID=812">chart</a>
+ illustrates the differences. Used with Argyll, there are no
+ differences in operation of an Eye-One Pro instrument, irrespective
+ of which package it came with. The lowest cost package is the <a
+ href="http://www.xrite.com/product_overview.aspx?ID=1461">i1 Basic
+ Pro</a>.<br>
+ <br>
+ The EFI ES-1000 (which is a re-badged Eye-One Pro) is also reported
+ to work with Argyll.<br>
+ <br>
+ Unless you know what you're doing, and have a very specific reason
+ to buy an instrument fitted with a UV (Ultra Violet) filter, make
+ sure that you buy an instrument without the filter. A UV filtered
+ instrument can't deal intelligently with FWA (Fluorescent Whitener
+ Additive) effects in paper. (Look <a href="FWA.html">here</a> for
+ more information about FWA compensation.) Using FWA compensation you
+ can make measurements using ISO 13655:2009 M0, M1 and M2 conditions.
+ The M2 condition emulates a UV cut instrument.<br>
+ <br>
+ There have been four revisions of the Eye-One Pro, Rev. A, B, D and
+ E (AKA Eye-One Pro2). The rev B, D and E are capable of sampling
+ twice as fast as the Rev. A version of the instrument, and are also
+ available with an ambient light reading capability.<br>
+ <br>
+ <span style="font-weight: bold;">NOTE</span> for those running on
+ older versions of Linux with a Rev. D, there was a problem with the
+ Linux USB stack that causes the instrument to stop working once it
+ has been used. The only workaround is to unplug and replug the
+ instrument in again, whereupon it can be used one time again. A fix
+ for this problem was in the Linux 2.6.26 kernel release.<br>
+ <br>
+ See also <a href="i1proDriver.html">How can I have confidence in
+ the i1pro Driver ?</a><br>
+ <br>
+ <span style="font-weight: bold;">Patch recognition:</span><br>
+ <br>
+ For the best chances of good patch recognition, the instrument
+ should be drawn smoothly and not too rapidly over the strip. If
+ there is a misread, try slowing down slightly. The Rev A and B.
+ instruments have a slower sampling rate than the latter revision
+ instruments, and hence must be used a bit more slowly. Generally a
+ higher quality set of readings will result if slower scans are used,
+ since there will then be more samples averaged for each patch.<br>
+ <br>
+ In <a href="chartread.html">chartread</a>, the -<span
+ style="font-weight: bold;">T ratio</span> argument modifies the
+ patch consistency tolerance threshold for the Eye-One Pro. In
+ recognizing patches in a strip, the instrument takes multiple
+ readings as the strip is read, and then divide the readings up into
+ each patch. It then check the consistency of the multiple readings
+ corresponding to each patch, and reject the measurement if they are
+ too inconsistent. For some media (ie. a coarser screens, fabric
+ etc.) the default tolerance may be unreasonably tight, so the <span
+ style="font-weight: bold;">-T ratio</span> argument can be used to
+ modify this criteria. To loosen the tolerance, use a number greater
+ than 1.0 (ie. 1.5, 2.0). <span style="font-weight: bold;"></span><br>
+ <br>
+ <span style="font-weight: bold;">Special features:</span><br>
+ <br>
+ A feature unique to Argyll when used with the Eye-One Pro, is the
+ high resolution spectral mode. This returns spectral measurements at
+ 3.333 nm spacing, rather than the default 10nm spacing, and also
+ extends the range of wavelengths very slightly. This high resolution
+ may assist in giving better accuracy for "peaky" emissive sources
+ such as illuminants and displays. The high resolution mode is
+ selected by using the <span style="font-weight: bold;">-H</span>
+ flag on the command line to <span style="font-weight: bold;">dispcal</span>,
+ <span style="font-weight: bold;">dispread</span>, <span
+ style="font-weight: bold;">chartread</span>, and <span
+ style="font-weight: bold;">spotread</span>. It can also be toggled
+ on and off within <span style="font-weight: bold;">spotread</span>
+ using the <span style="font-weight: bold;">h</span> key.<br>
+ <br>
+ Note that while finer spectral resolution will worsen the signal to
+ noise ratio of the individual spectral values, the signal to noise
+ ratio of the resulting tri-stimulus color values will be identical
+ to normal resolution mode, since the same overall integration is
+ performed. <br>
+ <br>
+ See <a href="i1proHiRes.html">Does the i1pro High Resolution mode
+ improve accuracy ?</a><br>
+ <br>
+ <img alt="High res. and standard res. spectrum."
+ src="Fluorescent.jpg" style="width: 750px; height: 375px;"><br>
+ <br>
+ <img alt="C.R.T high res. and standard res. spectrum."
+ src="CRTspectrum.jpg" style="width: 750px; height: 375px;"><br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <span style="font-weight: bold;"><a name="i1m"></a>Eye-One Monitor
+ emissive spectrometer<br>
+ <br>
+ <img alt="" src="i1m.jpg" style="width: 347px; height: 234px;"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">Eye-One Monitor</span>
+ from <a href="http://www.xrite.com/">X-Rite</a> (was Gretag
+ MacBeth) is a discontinued instrument. It was a lower cost version
+ of the <span style="font-weight: bold;">Eye-One Pro</span> without
+ reflective measurement capability. See <a href="#i1p">Eye-One Pro
+ reflective/emissive spectrometer</a><span style="font-weight:
+ bold;"> </span>for details on the operation of this instrument.<br>
+ <br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <span style="font-weight: bold;"><a name="i1d"></a>Eye-One Display
+ 1, Eye-One Display 2, Eye-One Display LT, ColorMunki Create,
+ ColorMunki Smile colorimeters,<br>
+ <br>
+ <img style=" width: 124px; height: 168px;" alt="ColorMunki Smile"
+ src="Smile.jpg"><img alt="Eye-One Display 2" src="i1d.jpg"
+ style="width: 145px; height: 168px;"> <img style="width: 133px;
+ height: 168px;" alt="ColorMunki Create"
+ src="ColorMunkiCreate.jpg"><br>
+ <br>
+ Instrument Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">ColorMunki Smile</span>
+ colorimeter is a currently available instrument.<br>
+ The <span style="font-weight: bold;">Eye-One Display LT</span> and
+ <span style="font-weight: bold;">Eye-One Display 2</span> are
+ discontinued products, although they may still be available from
+ some retailers, second hand, and may still be shipped with some
+ displays as part of their calibration capability.<br>
+ The <span style="font-weight: bold;">ColorMunki Create</span>
+ colorimeter is a discontinued product, although they may still be
+ available from some retailers or second hand,can also be used. They
+ will appear as an i1Display2 colorimeter.<br>
+ The <span style="font-weight: bold;">HP DreamColor</span>
+ colorimeter can also be used, and will appear as an i1Display2
+ colorimeter [note that it is calibrated for the DreamColor display].<br>
+ The <span style="font-weight: bold;">HP APS</span> (Advanced
+ Profiling Solution) colorimeter is also reported to work, and will
+ appear as an i1Display2.<br>
+ The <span style="font-weight: bold;">CalMAN X2</span> colorimeter
+ is also reported to work, and will appear as an i1Display2
+ colorimeter.<br>
+ The <span style="font-weight: bold;">Lacie Blue Eye</span> <span
+ style="font-weight: bold;"></span> colorimeter is also reported to
+ work, and will appear as an i1Display2 colorimeter.<br>
+ <br>
+ <span style="font-weight: bold;"></span>The <span
+ style="font-weight: bold;">Eye-One Display 1</span> is a
+ discontinued instrument. <br>
+ <br>
+ The Eye-One Display LT came with a less expensive<span
+ style="text-decoration: underline;"></span> package with more
+ limited software from the manufacture.<br>
+ The Eye-One Display 2 package came with more software
+ features, but the instruments are virtually identical, and
+ will operate identically using Argyll.<br>
+ The ColorMunki Create<span style="text-decoration: underline;"></span>
+ package is another alternative, and will operate identically using
+ Argyll.<br>
+ <br>
+ <span style="font-weight: bold;">Operation:</span><br>
+ <br>
The Display Selections for the <span style="font-weight: bold;">ColorMunki @@ -1484,23 +1732,47 @@ Gretag - Smile</span> are:<br> - <br> - <span style="font-weight: bold;">f</span> - LCD with CCFL back-light - A Liquid Crystal display that uses a Cold - Cathode Fluorescent back lighting. [Default, CB1]<br> + + + + + + + + + + + +
+ Smile</span> are:<br>
+ <br>
+ <span style="font-weight: bold;">f</span>
+ LCD with CCFL back-light
+ A Liquid Crystal display that uses a Cold
+ Cathode Fluorescent back lighting. [Default, CB1]<br>
<span style="font-weight: bold;">e</span> - LCD with LED back-light - A Liquid Crystal display that uses - Light Emitting Diode back lighting.<br> - <br> - other instruments will offer:<br> - <br> + + + + + + + + + + + +
+ LCD with LED back-light
+ A Liquid Crystal display that uses
+ Light Emitting Diode back lighting.<br>
+ <br>
+ other instruments will offer:<br>
+ <br>
<span style="font-weight: bold;">l</span> @@ -1523,8 +1795,20 @@ Gretag - LCD display A Liquid - Crystal Display, that is of the Non-Refresh type. [Default, CB1]<br> + + + + + + + + + + + +
+ LCD display A Liquid
+ Crystal Display, that is of the Non-Refresh type. [Default, CB1]<br>
<span style="font-weight: bold;">c</span> @@ -1547,121 +1831,141 @@ Gretag - CRT display A - Cathode Ray Tube display, that is of the Refresh type. [CB2]<br> - <br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <span style="font-weight: bold;"><a name="i1d3"></a></span> <span - style="font-weight: bold;">i1 DisplayPro and ColorMunki Display<span - style="font-weight: bold;"> colorimeters (i1 Display 3)</span><br> - <br> - <img alt="i1 Display Pro" src="i1d3_1.jpg" style="width: 194px; - height: 223px;"> <img style="width: 176px; height: 222px;" - alt="ColorMunki Display" src="i1d3_2.jpg"><br> - <br> - Instrument Availability:<br> - <br> - </span>Both instruments are currently available..<br> - <br> - The ColorMunki Display is a less expensive <a -href="http://xritephoto.com/ph_product_overview.aspx?id=1513&catid=149">package</a> - with more limited software from the manufacture, and takes a - noticeably longer time to make most measurements (a minimum of 1 - second), but both instruments will take longer for very dark - samples, and under these conditions the speed difference is less - significant.<br> - <br> - The i1Display Pro <a -href="http://xritephoto.com/ph_product_overview.aspx?id=1454&catid=109">package</a> - comes with i1Profiler, and the instrument is generally faster than - the ColorMunki Display, but other than this and the software - package, the instruments appear to be virtually identical. (Note - though that the ColorMunki Display is <u>unable</u> to measure the - refresh period, so is less repeatable in this mode than the - i1Display Pro).<br> - <br> - Both instruments are capable of using CCSS (<a - href="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="ccxxmake.html">ccxxmake</a> tool, and - installed or translated from the .EDR files that are provided with - the instrument CD using the <a href="oeminst.html">oeminst</a> - utility using a spectrometer as a reference.<br> - <br> - There are some OEM versions of this instrument around too, and the <a - href="http://www.spectracal.com/">SpectraCal OEM i1Display</a>, <a - href="http://www.chromapure.com/">ChromaPure</a> and <a - href="http://www.necdisplay.com/p/sensors/mdsvsensor3">NEC - SpectraSensor Pro</a> instruments are also reported to work. They - will appear as a be a the same as the i1Display Pro.<br> - <span style="font-weight: bold;">[Note</span> that if you have an - OEM version of this instrument, it's worth checking if they come - with any extra .edr files, that can then be translated for use with - ArgyllCMS using <a href="oeminst.html">oeminst</a>.]<br> - <br> - On MSWindows, if you have installed the Manufacturers applications, - you may have to shut the i1Profiler tray application down before - Argyll can open the instrument.<br> - <br> - <span style="font-weight: bold;">Operation:</span><br> - <br> - The Display Selections for this instrument are:<br> - <br> - <span style="font-weight: bold;">n</span><span - style="font-weight: bold;"></span> A - non-refresh type display [Default, CB1].<br> - <span style="font-weight: bold;">r</span> - A refresh type display - The refresh period - is measured, and the integration time adjusted appropriately. [CB2]<br> - <br> - With the manufacturers .edr files & reference Argyll .ccss files - installed, the following selections are:<br> - <br> - <span style="font-weight: bold;">n</span><span - style="font-weight: bold;"></span> A - non-refresh type display [Default, CB1].<br> - <span style="font-weight: bold;">r</span> - A refresh type display - The refresh - period is measured, and the integration time adjusted appropriately. - [CB2]<br> - <b>c</b> CRT - (Hitachi CM2112MET, Diamond View 1772ie)<br> - <b>l</b> LCD CCFL - IPS (CCFL AC EIZO HP with CORRECTION)<br> - <b>L</b> LCD CCFL - Wide Gamut IPS (WG CCFL NEC241 271)<br> - <b>b </b> LCD RGB - LED IPS (RGBLED HP SOYO)<br> - <b>e</b> LCD White - LED IPS (WLED AC LG Samsung)<br> - <b>p</b> Projector - (Marantz HP Panasonic Projectors Hybrid EDR)<br> - <br> - <b>Note when measuring CRT displays:<br> - </b><br> - The small magnet in the ambient light cover used to signal what - position it is in, can interfere in the operation of the CRT - display, particularly if the ambient cover is in it's natural - position at 180 degrees away from the measuring lens. One way of - minimizing this is to swing the cover down so that it touches the - display adjacent to the lens, thereby moving the magnet away from - the display surface. A more thorough but inconvenient way of - avoiding this problem is to unclip the ambient light cover and slide - it down the cable.<br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <span style="font-weight: bold;"><a name="Huey"></a>Huey colorimeter<br> - <br> - <img alt="" src="Huey.jpg" style="width: 128px; height: 202px;"><br> - <br> - Availability:<br> - <br> - </span>The <span style="font-weight: bold;">Huey </span>is widely - available under the <a href="http://www.pantone.com/">Pantone</a> - name as well as the manufacturer, <a href="http://www.xrite.com/">X-Rite</a>. - There lower cost Huey is now discontinued, while the <a + + + + + + + + + + + +
+ CRT display A
+ Cathode Ray Tube display, that is of the Refresh type. [CB2]<br>
+ <br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <span style="font-weight: bold;"><a name="i1d3"></a></span> <span
+ style="font-weight: bold;">i1 DisplayPro and ColorMunki Display<span
+ style="font-weight: bold;"> colorimeters (i1 Display 3)</span><br>
+ <br>
+ <img alt="i1 Display Pro" src="i1d3_1.jpg" style="width: 194px;
+ height: 223px;"> <img style="width: 176px; height: 222px;"
+ alt="ColorMunki Display" src="i1d3_2.jpg"><br>
+ <br>
+ Instrument Availability:<br>
+ <br>
+ </span>Both instruments are currently available..<br>
+ <br>
+ The ColorMunki Display is a less expensive <a
+href="http://xritephoto.com/ph_product_overview.aspx?id=1513&catid=149">package</a>
+ with more limited software from the manufacture, and takes a
+ noticeably longer time to make most measurements (a minimum of 1
+ second), but both instruments will take longer for very dark
+ samples, and under these conditions the speed difference is less
+ significant.<br>
+ <br>
+ The i1Display Pro <a
+href="http://xritephoto.com/ph_product_overview.aspx?id=1454&catid=109">package</a>
+ comes with i1Profiler, and the instrument is generally faster than
+ the ColorMunki Display, but other than this and the software
+ package, the instruments appear to be virtually identical. (Note
+ though that the ColorMunki Display is <u>unable</u> to measure the
+ refresh period, so is less repeatable in this mode than the
+ i1Display Pro).<br>
+ <br>
+ Both instruments are capable of using CCSS (<a
+ href="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="ccxxmake.html">ccxxmake</a> tool, and
+ installed or translated from the .EDR files that are provided with
+ the instrument CD using the <a href="oeminst.html">oeminst</a>
+ utility using a spectrometer as a reference.<br>
+ <br>
+ There are some OEM versions of this instrument around too, and the <a
+ href="http://www.spectracal.com/">SpectraCal OEM i1Display</a>, <a
+ href="http://www.chromapure.com/">ChromaPure</a>, <a
+ href="http://www.necdisplay.com/p/sensors/mdsvsensor3">NEC
+ SpectraSensor Pro</a> and <a
+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>
+ <span style="font-weight: bold;">[Note</span> that if you have an
+ OEM version of this instrument, it's worth checking if they come
+ with any extra .edr files, that can then be translated for use with
+ ArgyllCMS using <a href="oeminst.html">oeminst</a>.]<br>
+ <br>
+ On MSWindows, if you have installed the Manufacturers applications,
+ you may have to shut the i1Profiler tray application down before
+ Argyll can open the instrument.<br>
+ <br>
+ <span style="font-weight: bold;">Operation:</span><br>
+ <br>
+ The Display Selections for this instrument are:<br>
+ <br>
+ <span style="font-weight: bold;">n</span><span
+ style="font-weight: bold;"></span> A
+ non-refresh type display [Default, CB1].<br>
+ <span style="font-weight: bold;">r</span>
+ A refresh type display - The refresh period
+ is measured, and the integration time adjusted appropriately. [CB2]<br>
+ <br>
+ With the manufacturers .edr files & reference Argyll .ccss files
+ installed, the following selections are:<br>
+ <br>
+ <span style="font-weight: bold;">n</span><span
+ style="font-weight: bold;"></span> A
+ non-refresh type display [Default, CB1].<br>
+ <span style="font-weight: bold;">r</span>
+ A refresh type display - The refresh
+ period is measured, and the integration time adjusted appropriately.
+ [CB2]<br>
+ <b>c</b> CRT
+ (Hitachi CM2112MET, Diamond View 1772ie)<br>
+ <b>l</b> LCD CCFL
+ IPS (CCFL AC EIZO HP with CORRECTION)<br>
+ <b>L</b> LCD CCFL
+ Wide Gamut IPS (WG CCFL NEC241 271)<br>
+ <b>b </b> LCD RGB
+ LED IPS (RGBLED HP SOYO)<br>
+ <b>e</b> LCD White
+ LED IPS (WLED AC LG Samsung)<br>
+ <b>p</b> Projector
+ (Marantz HP Panasonic Projectors Hybrid EDR)<br>
+ <br>
+ <b>Note when measuring CRT displays:<br>
+ </b><br>
+ The small magnet in the ambient light cover used to signal what
+ position it is in, can interfere in the operation of the CRT
+ display, particularly if the ambient cover is in it's natural
+ position at 180 degrees away from the measuring lens. One way of
+ minimizing this is to swing the cover down so that it touches the
+ display adjacent to the lens, thereby moving the magnet away from
+ the display surface. A more thorough but inconvenient way of
+ avoiding this problem is to unclip the ambient light cover and slide
+ it down the cable.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <span style="font-weight: bold;"><a name="Huey"></a>Huey colorimeter<br>
+ <br>
+ <img alt="" src="Huey.jpg" style="width: 128px; height: 202px;"><br>
+ <br>
+ Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">Huey </span>is widely
+ available under the <a href="http://www.pantone.com/">Pantone</a>
+ name as well as the manufacturer, <a href="http://www.xrite.com/">X-Rite</a>.
+ There lower cost Huey is now discontinued, while the <a
href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey @@ -1684,12 +1988,24 @@ 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> - <span style="font-weight: bold;">Operation:</span><br> - <br> - The Display Selections for this instrument are:<br> - <br> + + + + + + + + + + + +
+ Pro</a> is still available.<br>
+ <span style="font-weight: bold;"></span><br>
+ <span style="font-weight: bold;">Operation:</span><br>
+ <br>
+ The Display Selections for this instrument are:<br>
+ <br>
<span style="font-weight: bold;">l</span> @@ -1712,8 +2028,20 @@ 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> + + + + + + + + + + + +
+ LCD display A Liquid
+ Crystal Display, that is of the Non-Refresh type. [Default, CB1]<br>
<span style="font-weight: bold;">c</span> @@ -1736,33 +2064,45 @@ 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> - <br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <span style="font-weight: bold;"><a name="mox"></a>MonacoOPTIX - colorimeters<br> - <br> - <img alt="" src="mox.jpg" style="width: 115px; height: 147px;"> - <img alt="" src="Chroma4.jpg" - style="width: 135px; height: 146px;"><br> - <br> - Instrument Availability:<br> - </span><br> - <span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">MonacoOPTIX</span> from - Monaco Soft is a discontinued instrument. It may still be - available as old stock, or second hand. It was sold packaged with - software from the manufacturer. The Sequel Chroma 4 appears to be a - similar instrument, and both seem to operate as if they were an - Eye-One Display 1 using Argyll.<br> - <br> - <span style="font-weight: bold;">Operation:</span><br> - <br> - The Display Selections for this instrument are:<br> - <br> + + + + + + + + + + + +
+ CRT display A Cathode Ray
+ Tube display, that is of the Refresh type. [CB2]<br>
+ <br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <span style="font-weight: bold;"><a name="mox"></a>MonacoOPTIX
+ colorimeters<br>
+ <br>
+ <img alt="" src="mox.jpg" style="width: 115px; height: 147px;">
+ <img alt="" src="Chroma4.jpg"
+ style="width: 135px; height: 146px;"><br>
+ <br>
+ Instrument Availability:<br>
+ </span><br>
+ <span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">MonacoOPTIX</span> from
+ Monaco Soft is a discontinued instrument. It may still be
+ available as old stock, or second hand. It was sold packaged with
+ software from the manufacturer. The Sequel Chroma 4 appears to be a
+ similar instrument, and both seem to operate as if they were an
+ Eye-One Display 1 using Argyll.<br>
+ <br>
+ <span style="font-weight: bold;">Operation:</span><br>
+ <br>
+ The Display Selections for this instrument are:<br>
+ <br>
<span style="font-weight: bold;">c</span> @@ -1785,8 +2125,20 @@ 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> + + + + + + + + + + + +
+ CRT display A Cathode Ray
+ Tube display, that is of the Refresh type.<br>
<span style="font-weight: bold;">l</span> @@ -1809,41 +2161,53 @@ 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> - <br> - <hr style="width: 100%; height: 2px;"><br> - <span style="font-weight: bold;"><a name="spyd2"></a>Spyder 2 - colorimeter<br> - <br> - <img alt="" src="Spyd2.jpg" style="width: 218px; height: 232px;"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">Spyder 2 </span><span - style="font-weight: bold;"></span>has been superseded by the - Spyder 3 & 4, but may be available second hand.<br> - [The Spyder 1 has also been reported as working, but this has not - been confirmed.]<br> - <span style="font-weight: bold;"><br> - </span><span style="font-weight: bold;">Operation:<br> - </span><br> - <span style="font-weight: bold;">Important Note </span>about the - ColorVision Spyder 2 instrument support:<br> - <br> - This instrument cannot function without the driver software having - access to the vendor supplied PLD firmware pattern for it.<br> - This firmware is not provided with Argyll, since it is not available - under a compatible license.<br> - <br> - The purchaser of a Spyder 2 instrument should have received a copy - of this firmware along with their instrument, and should therefore - be able to enable the Argyll driver for this instrument by using the - <a href="oeminst.html">oeminst</a> tool.<span style="font-weight: - bold;"></span><br> - <br> - The Display Selections for this instrument are:<br> - <br> + + + + + + + + + + + +
+ LCD display A Liquid
+ Crystal Display, that is of the Non-Refresh type.<br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <span style="font-weight: bold;"><a name="spyd2"></a>Spyder 2
+ colorimeter<br>
+ <br>
+ <img alt="" src="Spyd2.jpg" style="width: 218px; height: 232px;"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">Spyder 2 </span><span
+ style="font-weight: bold;"></span>has been superseded by the
+ Spyder 3 & 4, but may be available second hand.<br>
+ [The Spyder 1 has also been reported as working, but this has not
+ been confirmed.]<br>
+ <span style="font-weight: bold;"><br>
+ </span><span style="font-weight: bold;">Operation:<br>
+ </span><br>
+ <span style="font-weight: bold;">Important Note </span>about the
+ ColorVision Spyder 2 instrument support:<br>
+ <br>
+ This instrument cannot function without the driver software having
+ access to the vendor supplied PLD firmware pattern for it.<br>
+ This firmware is not provided with Argyll, since it is not available
+ under a compatible license.<br>
+ <br>
+ The purchaser of a Spyder 2 instrument should have received a copy
+ of this firmware along with their instrument, and should therefore
+ be able to enable the Argyll driver for this instrument by using the
+ <a href="oeminst.html">oeminst</a> tool.<span style="font-weight:
+ bold;"></span><br>
+ <br>
+ The Display Selections for this instrument are:<br>
+ <br>
<span style="font-weight: bold;">l</span> @@ -1866,8 +2230,20 @@ 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> + + + + + + + + + + + +
+ LCD display A Liquid Crystal
+ Display, that is of the Non-Refresh type. [Default, CB1]<br>
<span style="font-weight: bold;">c</span> @@ -1890,131 +2266,143 @@ 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> - <br> - <br> - <span style="font-weight: bold;">Linux USB hub problems:<br> - <br> - </span>Note that the Spyder doesn't appear to operate at all well on - Linux if attached to a secondary USB hub. You may have such a - secondary hub built into your motherboard. If Argyll has difficulty - in reliably talking to the Spyder, try connecting it directly to the - computer rather than via a usb hub, or try using a USB port on your - computer that connects directly to a root hub. This is probably due - to a bug in the Linux EHCI driver, and a fix is due to appear in the - Linux kernel sometime after July 2011. The name of the fix is "EHCI: - fix direction handling for interrupt data toggles".<br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <span style="font-weight: bold;"><a name="spyd3"></a>Spyder 3 - colorimeter<br> - <br> - <img style="width: 262px; height: 220px;" alt="Spyder3" - src="Spyd3.jpg"> <img style="width: 193px; height: 220px;" - alt="Spyder3Express" src="Spyd3x.jpg"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">Spyder3Elite</span>, <span - style="font-weight: bold;">Spyder3Pro</span> and <span - style="font-weight: bold;">Spyder3Express</span> are being - superseded by the Spyder4, but may still stocked by some dealers, - and may be available second hand. The <span style="font-weight: - bold;">Spyder3Elite</span> and <span style="font-weight: bold;">Spyder3Pro</span> - appear to be identical hardware with different software from the - manufacturer. The <span style="font-weight: bold;">Spyder3Express</span> - lacks the ambient sensor.<br> - <br> - [Note that this instrument doesn't seem particularly suited to - measuring CRT displays, since it no longer seems to synchronise its - readings to a CRT refresh, and you can no longer remove the LCD - filter, reducing its sensitivity compared to the Spyder 2 in CRT - mode. The Spyder 2 or one of the other instruments may be a better - choice if you particularly need to measure CRTs or Refresh - displays.]<br> - <span style="font-weight: bold;"><br> - </span><span style="font-weight: bold;">Operation:<br> - </span><br> - The ambient light sensor can be used with the <span - style="font-weight: bold;">Spyder3Elite</span> and <span - style="font-weight: bold;">Spyder3Pro</span> instruments, but is - only capable of monochrome readings.<span style="font-weight: bold;"><br> - </span><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 [Default, CB1]<br> - <span style="font-weight: bold;">r | c</span> - A refresh type display. [CB2]<br> - <br> - <br> - <hr style="width: 100%; height: 2px;"><br> - <span style="font-weight: bold;"><a name="spyd4"></a>Spyder 4 - colorimeter<br> - <br> - <img style=" width: 262px; height: 220px;" alt="Spyder4" - src="Spyd4.jpg"> <br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;">Spyder4Elite</span>, <span - style="font-weight: bold;">Spyder4Pro</span> and <span - style="font-weight: bold;">Spyder4Express</span> are a currently - available instruments. The <span style="font-weight: bold;">Spyder4Elite</span> - and <span style="font-weight: bold;">Spyder4Pro</span> appear to be - identical hardware with different software from the manufacturer. - The <span style="font-weight: bold;">Spyder4Express</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_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="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 4 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 4 instrument you should have received a copy - of the calibration data along with their instrument, and should - therefore be able to enable the full range of display type - selections in Argyll by using the <a href="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 + + + + + + + + + + + +
+ CRT display A Cathode Ray
+ Tube display, that is of the Refresh type. [CB2]<br>
+ <br>
+ <br>
+ <span style="font-weight: bold;">Linux USB hub problems:<br>
+ <br>
+ </span>Note that the Spyder doesn't appear to operate at all well on
+ Linux if attached to a secondary USB hub. You may have such a
+ secondary hub built into your motherboard. If Argyll has difficulty
+ in reliably talking to the Spyder, try connecting it directly to the
+ computer rather than via a usb hub, or try using a USB port on your
+ computer that connects directly to a root hub. This is probably due
+ to a bug in the Linux EHCI driver, and a fix is due to appear in the
+ Linux kernel sometime after July 2011. The name of the fix is "EHCI:
+ fix direction handling for interrupt data toggles".<br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <span style="font-weight: bold;"><a name="spyd3"></a>Spyder 3
+ colorimeter<br>
+ <br>
+ <img style="width: 262px; height: 220px;" alt="Spyder3"
+ src="Spyd3.jpg"> <img style="width: 193px; height: 220px;"
+ alt="Spyder3Express" src="Spyd3x.jpg"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">Spyder3Elite</span>, <span
+ style="font-weight: bold;">Spyder3Pro</span> and <span
+ style="font-weight: bold;">Spyder3Express</span> are being
+ superseded by the Spyder4, but may still stocked by some dealers,
+ and may be available second hand. The <span style="font-weight:
+ bold;">Spyder3Elite</span> and <span style="font-weight: bold;">Spyder3Pro</span>
+ appear to be identical hardware with different software from the
+ manufacturer. The <span style="font-weight: bold;">Spyder3Express</span>
+ lacks the ambient sensor.<br>
+ <br>
+ [Note that this instrument doesn't seem particularly suited to
+ measuring CRT displays, since it no longer seems to synchronise its
+ readings to a CRT refresh, and you can no longer remove the LCD
+ filter, reducing its sensitivity compared to the Spyder 2 in CRT
+ mode. The Spyder 2 or one of the other instruments may be a better
+ choice if you particularly need to measure CRTs or Refresh
+ displays.]<br>
+ <span style="font-weight: bold;"><br>
+ </span><span style="font-weight: bold;">Operation:<br>
+ </span><br>
+ The ambient light sensor can be used with the <span
+ style="font-weight: bold;">Spyder3Elite</span> and <span
+ style="font-weight: bold;">Spyder3Pro</span> instruments, but is
+ only capable of monochrome readings.<span style="font-weight: bold;"><br>
+ </span><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 [Default, CB1]<br>
+ <span style="font-weight: bold;">r | c</span>
+ A refresh type display. [CB2]<br>
+ <br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><br>
+ <span style="font-weight: bold;"><a name="spyd4"></a>Spyder 4
+ colorimeter<br>
+ <br>
+ <img style=" width: 262px; height: 220px;" alt="Spyder4"
+ src="Spyd4.jpg"> <br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;">Spyder4Elite</span>, <span
+ style="font-weight: bold;">Spyder4Pro</span> and <span
+ style="font-weight: bold;">Spyder4Express</span> are a currently
+ available instruments. The <span style="font-weight: bold;">Spyder4Elite</span>
+ and <span style="font-weight: bold;">Spyder4Pro</span> appear to be
+ identical hardware with different software from the manufacturer.
+ The <span style="font-weight: bold;">Spyder4Express</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_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="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 4 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 4 instrument you should have received a copy
+ of the calibration data along with the instrument, and should
+ therefore be able to enable the full range of display type
+ selections in Argyll by using the <a href="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 @@ -2037,17 +2425,29 @@ 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> - <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> + + + + + + + + + + + +
+ - 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> @@ -2070,12 +2470,24 @@ 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 - backlight.<br> - <span style="font-weight: bold;">x</span> - LCD, CCFL - Type 2 + + + + + + + + + + + +
+ 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 @@ -2098,23 +2510,6 @@ 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> - <br> - The ambient light sensor can be used with the <span - 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> - <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 - colorimeter<br> - <br> - <img alt="" src="HCFR.jpg" style="width: 203px; height: 194px;"><br> - <br> - </span><span style="font-weight: bold;">Availability:<br> - <br> - </span>The <span style="font-weight: bold;" class="titre">Colorimètre @@ -2126,6 +2521,34 @@ 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>
+ <br>
+ The ambient light sensor can be used with the <span
+ 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>
+ <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
+ colorimeter<br>
+ <br>
+ <img alt="" src="HCFR.jpg" style="width: 203px; height: 194px;"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;" class="titre">Colorimètre + + + + + + + + + + @@ -2136,26 +2559,39 @@ 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 - href="http://www.homecinema-fr.com/colorimetre/index_en.php">HCFR</a>. - <br> - <br> - <span style="font-weight: bold;">OS X</span><br> - <br> - Please note the installation <a href="Installing_OSX.html#HCFR">instructions</a>.<br> - <br> - <span style="font-weight: bold;">Operation:</span><br> - <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span><br> - The accuracy of this instrument does not seem to be comparable to - the commercial instruments when used for measuring displays, - particularly in the area of measuring dark colors, and I've seen the - best results when used with a CRT display. It may well give good - results in calibrating projectors, since this was what it was - designed to do.<br> - <br> - The Display Selections for this instrument are:<br> - <br> + + + + + + + + + + + + +
+ HCFR Probe</span> is a kit instrument from <span
+ style="font-weight: bold;"></span> <a
+ href="http://www.homecinema-fr.com/colorimetre/index_en.php">HCFR</a>.
+ <br>
+ <br>
+ <span style="font-weight: bold;">OS X</span><br>
+ <br>
+ Please note the installation <a href="Installing_OSX.html#HCFR">instructions</a>.<br>
+ <br>
+ <span style="font-weight: bold;">Operation:</span><br>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span><br>
+ The accuracy of this instrument does not seem to be comparable to
+ the commercial instruments when used for measuring displays,
+ particularly in the area of measuring dark colors, and I've seen the
+ best results when used with a CRT display. It may well give good
+ results in calibrating projectors, since this was what it was
+ designed to do.<br>
+ <br>
+ The Display Selections for this instrument are:<br>
+ <br>
<span style="font-weight: bold;">l</span> @@ -2178,8 +2614,20 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey - LCD display A Liquid - Crystal Display [Default].<br> + + + + + + + + + + + +
+ LCD display A Liquid
+ Crystal Display [Default].<br>
<span style="font-weight: bold;">c</span> @@ -2202,13 +2650,86 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey - CRT display A Cathode Ray - Tube display.<br> - <b>R</b> Raw - Reading Raw sensor readings, - used for calibration [CB1]<br> - <br> - <br> - <br> - </body> -</html> + + + + + + + + + + + +
+ CRT display A Cathode Ray
+ Tube display.<br>
+ <b>R</b> Raw
+ Reading Raw sensor readings,
+ used for calibration [CB1]<br>
+ <br>
+ <hr style="width: 100%; height: 2px;"><a name="ColorHug"></a><span
+ style="font-weight: bold;" class="titre">ColorHug<br>
+ <br>
+ <img alt="" src="ColorHug.jpg" style="width: 203px; height:
+ 194px;" height="623" width="552"><br>
+ <br>
+ </span><span style="font-weight: bold;">Availability:<br>
+ <br>
+ </span>The <span style="font-weight: bold;" class="titre">ColorHug</span>
+ is a low cost display colorimeter instrument from <span
+ style="font-weight: bold;"></span> <a
+ href="http://www.hughski.com/">Hughski</a>. <br>
+ <br>
+ <span style="font-weight: bold;">Operation:</span><br>
+ <span style="font-weight: bold;"><span style="font-weight: bold;"></span></span><br>
+ Due to the nature of its sensor, the ColorHug accuracy is quite
+ dependent on the instrument calibration matrix. A custom .CCMX will
+ greatly assist it's accuracy, although a workaround is to calibrate
+ your display using its native white point, rather than aiming for
+ some absolute white point such as D65.<br>
+ <br>
+ The Display Selections for this instrument are:<br>
+ <br>
+ <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>
+ <br>
+ <br>
+ <br>
+ <br>
+ <br>
+ </body>
+</html>
diff --git a/doc/oeminst.html b/doc/oeminst.html index 7334d8d..ffbc0f0 100644 --- a/doc/oeminst.html +++ b/doc/oeminst.html @@ -296,7 +296,7 @@ href="http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html">XDG <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="file:///D:/src/argyll/doc/Environment.html">ARGYLL_COLMTER_CAL_SPEC_SET</a> + href="Environment.html">ARGYLL_COLMTER_CAL_SPEC_SET</a> environment variable.<br> <br> <br> diff --git a/doc/printtarg.html b/doc/printtarg.html index 5faab76..0d86cac 100644 --- a/doc/printtarg.html +++ b/doc/printtarg.html @@ -20,6 +20,7 @@ style="font-family: monospace;"> + Verbose mode</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#i">-i 20 | 22 | 41 | 51 | @@ -34,10 +35,12 @@ DTP20, = + DTP22, 41 = DTP41, 51 = DTP51, SS = SpectroScan,<br> + i1 = i1Pro, CM = ColorMunki</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -50,6 +53,7 @@ spacer size + by factor (e.g. 0.857 or 1.5 etc.)<br> </span></small><small><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#A">-A scale</a><span @@ -61,6 +65,7 @@ by additional + factor (e.g. 0.857 or 1.5 etc.)</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"></span><span @@ -75,6 +80,7 @@ additional style="font-family: monospace;"> + Don't randomize patch location</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -87,6 +93,7 @@ image recognition + (.cht) file</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#S">-S</a><span @@ -98,6 +105,7 @@ but don't + generate wide orientation strip.</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -105,6 +113,7 @@ don't style="font-family: monospace;"> + Force colored spacers</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#b">-b</a><span @@ -116,12 +125,14 @@ don't style="font-family: monospace;"> + Force no spacers</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#f">-f</a><span style="font-family: monospace;"> + Create PostScript DeviceN Color fallback</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -135,6 +146,7 @@ don't Black colorspace encoding DeviceGray (def), DeviceCMYK, Separation or DeviceN<br> <a href="#o">-o k|n</a> + CMY colorspace encoding DefiveCMYK (def), inverted DeviceRGB or DeviceN<br style="font-family: monospace;"> </span> <span style="font-family: monospace;"> </span><a @@ -142,6 +154,7 @@ don't style="font-family: monospace;"> + Output EPS compatible file<br> <a href="#t">-t [res]</a> Output @@ -151,6 +164,7 @@ TIFF raster + file, optional res DPI (default 200)<br> <a href="#T">-T [res]</a> Output @@ -160,11 +174,13 @@ TIFF raster + file, optional res DPI (default 200)<br> </span></small><small><span style="font-family: monospace;"> <a href="#C">-C</a> + Don't use TIFF compression</span></small><br> <small><span style="font-family: monospace;"> <a href="#N">-N</a> Use @@ -174,10 +190,12 @@ N channels + more than 4<br> <a href="#D">-D</a> + Dither 8 bit TIFF values down from 16 bit<br> <a href="#Q">-Q nbits</a> Quantize @@ -187,6 +205,7 @@ to fit + in nbits<br> </span></small><small style="font-family: monospace;"> <span style="text-decoration: underline;">-</span><a href="#K">K @@ -201,6 +220,7 @@ fit style="font-family: monospace;"> + Use given random start number</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -219,12 +239,14 @@ fit Set + a page margin in mm (default 6.0 mm)<br> </span></small><small><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#M">-M margin</a><span style="font-family: monospace;"> + </span></small><small><span style="font-family: monospace;">Set a page margin in mm and include it in TIFF</span><span style="font-family: monospace;"></span></small><br> @@ -232,6 +254,7 @@ Set + Don't limit strip length</span></small><br> <small><span style="font-family: monospace;"> <a href="#L">-L</a> Suppress @@ -241,12 +264,19 @@ paper clip - border<br style="font-family: monospace;"> + + border</span></small><br> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> <a href="#U">-U</a> + + Suppress CUPS cupsJobTicket: cups-disable-cmm in PS & + EPS files</span></small><br style="font-family: monospace;"> </span><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#p">-p size</a><span style="font-family: monospace;"> + Select page size from:</span><br style="font-family: monospace;"> <span style="font-family: monospace;"></span></small><small><span style="font-family: monospace;"> @@ -254,17 +284,20 @@ clip A4 + [210.0 x 297.0 mm]<br> A4R + [297.0 x 210.0 mm]<br> A3 + [297.0 x 420.0 mm] (default)<br> @@ -279,18 +312,21 @@ A3 + Legal [215.9 x 355.6 mm]<br> + 4x6 [101.6 x 152.4 mm]<br> 11x17 + [279.4 x 431.8 mm]<br style="font-family: monospace;"> </span><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#pp">-p WWWxHHH</a><span @@ -304,6 +340,7 @@ A3 style="font-family: monospace;"> + 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 style="font-family: monospace;" @@ -333,6 +370,7 @@ A3 -A: + </span>Normally, <b>printtarg</b> prints test patches that are the minimum size that can be reliably and accurately read by the instrument. For some media, it might be desirable to use test @@ -385,6 +423,7 @@ A3 turn this off you probably want to <a href="chartread.html#B">disable + bi-directional</a> strip reading in instruments such as the i1pro.<br> <br> <a name="s"></a> The <b>-s</b> flag does two things. One is that it @@ -408,6 +447,7 @@ A3 then contrasting neutral colored spacers will be used, but these generally work less reliably than colored spacers. <a name="n"></a>The + <b>-n</b> flag will cause spacers to be omitted, which may still work with smaller numbers of test values when the patch selection is randomized, but won't work successfully when a large number of test @@ -573,9 +613,11 @@ A3 represented in the Postscript or TIFF output. The default is to use the DeviceGray representation (<span style="font-weight: bold;">-wg</span>), + but Device RGB can also be used, where the R, G &B values are all set to the same value (<span style="font-weight: bold;">-wr</span>), + a <span style="font-weight: bold;">White</span> separation color can be specified (<span style="font-weight: bold;">-ws</span>), or a DeviceN <span style="font-weight: bold;">White</span> color can be @@ -592,6 +634,7 @@ can also + be used, where the CMY values are zero, and just the K channel is used (<span style="font-weight: bold;">-kc</span>), a <span style="font-weight: bold;">Black</span> separation color can be @@ -604,6 +647,7 @@ also output. The default is to use the DeviceCMYK representation (<span style="font-weight: bold;">-ok</span>) where the K value is always zero, or inverted Device RGB (<span style="font-weight: bold;">-or</span>), + or as a 3 channel DeviceN colorsoace can be used (<span style="font-weight: bold;">-on</span>).<br> <br> @@ -641,10 +685,19 @@ also hold the chart in place, while it is being read. (Currently this is only the Eye-One Pro).<br> <br> + <a name="U"></a> The <b>-U</b> flag suppresses the CUPS + %cupsJobTicket: cups-disable-cmm in PS and EPS files. By default + this ensures that the resulting files doesn't have color management + applied to it. If you are creating a test chart that should be color + managed (perhaps because you want to use it to verify the overall + operation of the printing system), then you can use the <b>-U</b> + flag to disable this.<br> + <br> <a name="p"></a> The <b>-p</b> parameter specifies the paper size. The size can either be one of the default sizes, <a name="pp"></a>or + can be specified in millimeters. Limitations of the instrument may limit the maximum number of patches in a strip. For SpectroScan, a size of A4 or Letter (or smaller) should be used. Useful diff --git a/doc/profcheck.html b/doc/profcheck.html index ebb719b..ef0bc5b 100644 --- a/doc/profcheck.html +++ b/doc/profcheck.html @@ -197,7 +197,7 @@ 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="file:///D:/src/argyll/doc/colprof.html#f">colprof -f</a> for + 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> @@ -209,7 +209,7 @@ Sort <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:///D:/src/argyll/doc/File_Formats.html#.sp">.sp</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 diff --git a/doc/refine.html b/doc/refine.html index cfe18b9..36a0ae4 100644 --- a/doc/refine.html +++ b/doc/refine.html @@ -15,15 +15,16 @@ format, but only XYZ, Lab or spectral values will be used (ie. all device space values are ignored). Typically the charts would be printed on a target system (the one being emulated, say a printing - press), and the proofing system (the one that is being profiled). - The abstract profile that <span style="font-weight: bold;">refine</span> + press, or created using an ideal target profile such as Rec709), and + the proofing system (the device that is being profiled). The + abstract profile that <span style="font-weight: bold;">refine</span> produces will be a correction that makes the proofing system behave more like the target. This can then be used to recreate the proofing systems ICC profile, or device link. By feeding a previous abstract correction profile in as well, iterative improvement can be made to the proofing reproduction.<br> <br> - <a href="verify.html">verify</a> is a useful tool to use on the two + <a href="colverify.html">colverify</a> is a useful tool to use on the two test charts, to check how well the refinement is proceeding. If a white point relative match is being created (refine -R), then use veryify -N.<br> @@ -32,14 +33,17 @@ [inabs] outabs<br> -v + Verbose<br> -c Create + initial abstract correction profile<br> -g Don't + impose output device gamut limit<br> -r res Set abstract profile clut resolution (default 33)<br> @@ -48,6 +52,7 @@ Don't -R Aim + for white point relative match rather than absolute<br> </small></tt><tt><small><small></small><small><small>-f [illum] Use Fluorescent Whitening Agent @@ -55,6 +60,7 @@ Aim + M0, M1, M2, A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp]<br> -i illum Choose @@ -63,26 +69,33 @@ Aim + A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp</small></small><br> -o observ Choose CIE Observer for spectral data:<br> 1931_2, + 1964_10, S&B 1955_2, J&V 1978_2 (def.)<br> <span style="font-style: italic;">cietarget </span> + Target CIE or spectral values, CGATS file (e.g. .ti3)<br> <span style="font-style: italic;">ciecurrent</span> + Actual CIE or spectral values, CGATS file (e.g. .ti3)<br> [<span style="font-style: italic;">outdevicc</span>] + Output device ICC profile to set gamut limit (not used if -g)<br> [<span style="font-style: italic;">inabs</span>] Previous + abstract correction ICC profile (not used if -c)<br> <span style="font-style: italic;">outabs</span> Created/refined + abstract correction ICC profile</small></tt><br> <h3>Usage Details</h3> <b>refine</b> provides a way of improving the profile accuracy of a @@ -135,7 +148,7 @@ Created/refined 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="file:///D:/src/argyll/doc/colprof.html#f">colprof -f</a> for + 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> @@ -146,7 +159,7 @@ Created/refined 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:///D:/src/argyll/doc/File_Formats.html#.sp">.sp</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 @@ -178,6 +191,7 @@ Created/refined <span style="font-style: italic; font-weight: bold;">cietarget</span> Is + the filename of the target CIE or spectral values. This is a <a href="File_Formats.html#CGATS">CGATS</a> file (e.g. a <a href="File_Formats.html#.ti3">.ti3</a> made using <a @@ -198,6 +212,7 @@ Is [<span style="font-style: italic; font-weight: bold;">outdevicc</span>] If + the <span style="font-weight: bold;">-g</span> flag is not used, then the output device ICC profile should be supplied here, to allow <span style="font-weight: bold;">refine</span> to limit its @@ -206,6 +221,7 @@ If [<span style="font-weight: bold; font-style: italic;">inabs</span>] After + the first correction has been created, subsequent corrections need to improve upon previous ones, so the previous correction profile should be provided here. For the first correction, the <span @@ -215,6 +231,7 @@ After <span style="font-weight: bold; font-style: italic;">outabs</span> The + name of the created or refined abstract correction ICC profile<br> <br> <h3> Discussion</h3> @@ -249,9 +266,9 @@ The file.<br> <br> Lets check how well the proofing system current matches using - verify:<br> + colverify:<br> <br> - verify reference.ti3 chart1.ti3<br> + colverify reference.ti3 chart1.ti3<br> <br> We then create our initial abstract correction fix profile <span style="font-weight: bold;">fix1.icm</span> using refine:<br> @@ -282,6 +299,7 @@ The the same options as you used to create your initial <span style="font-weight: bold;"><span style="font-weight: bold;"></span>proofer.icm + </span>or <span style="font-weight: bold;">target_proofer.icm</span>, with the addition of the "-p fix1.icm" option to specify the abstract correction profile be applied.<br> @@ -292,9 +310,9 @@ The style="font-weight: bold;">chart2.ti3</span> file.<br> <br> Lets check how well the proofing system matches after this first - round of refinement using verify:<br> + round of refinement using colverify:<br> <br> - verify reference.ti3 chart2.ti3<br> + colverify reference.ti3 chart2.ti3<br> <br> <br> <span style="font-weight: bold;"><span style="font-weight: bold;">>>></span></span><br> @@ -302,6 +320,7 @@ The <span style="font-weight: bold;"><span style="font-weight: bold;"> </span></span>We can + then start another round of improvement:<br> <br> We refine our previous abstract correction fix profile using @@ -328,14 +347,15 @@ can style="font-weight: bold;">chart3.ti3</span> file.<br> <br> Check again how well the proofing system matches after this first - round of refinement using verify:<br> + round of refinement using colverify:<br> <br> - verify reference.ti3 chart3.ti3<br> + colverify reference.ti3 chart3.ti3<br> <br> Rounds of improvements can be continues by looping back to <span style="font-weight: bold;">>>></span>, being careful to increment the names of the <span style="font-weight: bold;">fixN.icm</span>, + <span style="font-weight: bold;">proofer_fixN.icm</span> or <span style="font-weight: bold;">target_proofer_fixN.icm</span> and <span style="font-weight: bold;">chartN.ti3</span>files. Stop when diff --git a/doc/scanin.html b/doc/scanin.html index db5091f..ac6ccc8 100644 --- a/doc/scanin.html +++ b/doc/scanin.html @@ -10,11 +10,8 @@ <h2><b>scanin/scanin</b></h2> <h3>Summary</h3> Convert an 8 or 16 bit per component <a - href="File_Formats.html#TIFF">TIFF</a> - image of a - test chart into <a href="File_Formats.html#.ti3">.ti3</a> - device - values + href="File_Formats.html#TIFF">TIFF</a> image of a test chart + into <a href="File_Formats.html#.ti3">.ti3</a> device values using automatic pattern recognition, or manual chart alignment.<br> Performs other tasks associated with turning a TIFF raster of test patches into numeric values. <br> @@ -22,40 +19,37 @@ </h3> <small><a style="font-family: monospace;" href="#_"> usage</a><span style="font-family: monospace;">: scanin [options] input.tif - recogin.cht - valin.cie [diag.tif]</span><br style="font-family: monospace;"> + recogin.cht valin.cie [diag.tif]</span><br style="font-family: + monospace;"> <span style="font-family: monospace;"> :- inputs - 'input.tif', and outputs scanner - 'input.ti3', or</span><br style="font-family: monospace;"> + 'input.tif', and outputs scanner 'input.ti3', or</span><br + style="font-family: monospace;"> <br style="font-family: monospace;"> <a style="font-family: monospace;" href="#g"> usage</a><span style="font-family: monospace;">: scanin -g [options] input.tif - recogout.cht - [diag.tif]</span><br style="font-family: monospace;"> + recogout.cht [diag.tif]</span><br style="font-family: + monospace;"> <span style="font-family: monospace;"> :- outputs file 'recogout.cht', or</span><br style="font-family: monospace;"> <br style="font-family: monospace;"> <a style="font-family: monospace;" href="#o"> usage</a><span style="font-family: monospace;">: scanin -o [options] input.tif - recogin.cht - [diag.tif]</span><br style="font-family: monospace;"> + recogin.cht [diag.tif]</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> :- outputs file 'input.val', or</span><br style="font-family: monospace;"> <br style="font-family: monospace;"> <a style="font-family: monospace;" href="#c"> usage</a><span style="font-family: monospace;">: scanin -c [options] input.tif - recogin.cht - scanprofile.[icm|mpp] pbase [diag.tif]</span><br + recogin.cht scanprofile.[icm|mpp] pbase [diag.tif]</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> :- inputs - pbase.ti2 - and outputs printer pbase.ti3, or</span><br style="font-family: - monospace;"> + pbase.ti2 and outputs printer pbase.ti3, or</span><br + style="font-family: monospace;"> <br style="font-family: monospace;"> <a style="font-family: monospace;" href="#r"> usage</a><span style="font-family: monospace;">: scanin -r [options] input.tif - recogin.cht - pbase [diag.tif]</span><br style="font-family: monospace;"> + recogin.cht pbase [diag.tif]</span><br style="font-family: + monospace;"> <span style="font-family: monospace;"> :- inputs pbase.ti2+.ti3 and outputs pbase.ti3</span><br style="font-family: monospace;"> @@ -64,18 +58,21 @@ style="font-family: monospace;" href="#g">-g</a><span style="font-family: monospace;"> Generate + a chart reference (.cht) file</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#o">-o</a><span style="font-family: monospace;"> Output + patch values in .val file</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#c">-c</a><span 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;"> @@ -83,19 +80,23 @@ Use style="font-family: monospace;" href="#ca">-ca</a><span 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 @@ -103,84 +104,98 @@ Default <br> 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 style="font-family: monospace;" href="#a">-a</a><span 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: + 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 style="font-family: monospace;"> [ihvglLIcrsonap] - generate - diagnostic output (try -dipn)</span><br style="font-family: - monospace;"> + generate diagnostic output (try -dipn)</span><br + style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#di">i</a><span style="font-family: monospace;"> diag + - B&W of input image</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#dh">h</a><span style="font-family: monospace;"> diag + - Horizontal edge detection</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#dv">v</a><span style="font-family: monospace;"> diag + - Vertical edge detection</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#dg">g</a><span 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 @@ -188,365 +203,251 @@ diag style="font-family: monospace;" href="#dr">r</a><span 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 default output filename - & extension.</span></small><br> + + - pixel areas sampled</span></small> <br> + <small><span style="font-family: monospace;"> <a href="#O">-O</a> + outputfile Override the + default output filename & extension.</span></small><br> <h3>Usage Details and Discussion</h3> <span style="font-weight: bold;">scanin</span> is setup to deal with - a - raster file that has been roughly cropped to a size that contains - the - test chart. It's exact orientation is not important [ie. there is - usually no need to rotate or crop the image any more finely.] The + a raster file that has been roughly cropped to a size that contains + the test chart. It's exact orientation is not important [ie. there + is usually no need to rotate or crop the image any more finely.] The reference files are normally set up with the assumption that the - edges - of the chart are visible within the image, and if the image is - cropped - to exclude the chart edges, it may well not recognize the chart - properly. It is designed to cope with a variety of 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> + edges of the chart are visible within the image, and if the image is + cropped to exclude the chart edges, it may well not recognize the + chart properly. It is designed to cope with a variety of + 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> <br> There are 5 basic modes that <b>scanin</b> operates in.<br> <ul> <li><a name="_"></a>When no special argument is given scanin is assumed to be parsing an input device characterization chart - (ie. an - IT8.7/2 chart), for the purpose of creating a <a + (ie. an IT8.7/2 chart), for the purpose of creating a <a href="File_Formats.html#.ti3">.ti3</a> data file containing the CIE test values and the corresponding RGB scanner values. The <a href="File_Formats.html#.ti3">.ti3</a> file can then be - used for - creating - an input profile using <a href="colprof.html">colprof</a>. The - file - arguments are: <a name="_p1"></a>The TIFF file that is to be - processed, <a name="_p2"></a>the image recognition template - file, <a name="_p3"></a>the CIE reference value definitions for - the test chart - (sometimes labeled a ".q60" file), <a name="_p4"></a>and an - optional - name for the image recognition - diagnostic output. The resulting .ti3 file will have the same - base name - as the input TIFF file.</li> + used for creating an input profile using <a href="colprof.html">colprof</a>. + The file arguments are: <a name="_p1"></a>The TIFF file that is + to be processed, <a name="_p2"></a>the image recognition + template file, <a name="_p3"></a>the CIE reference value + definitions for the test chart (sometimes labeled a ".q60" + file), <a name="_p4"></a>and an optional name for the image + recognition diagnostic output. The resulting .ti3 file will have + the same base name as the input TIFF file.</li> <li><a name="g"></a>If the<b> -g</b> flag is specified, then - scanin - is operating in a mode designed to create the necessary image - recognition template file (<a href="File_Formats.html#.cht">.cht</a>) - boilerplate information. Patch - location and labeling information would need to be added - manually to - such - a generated file, to make a complete and useable recognition - template - file. <a href="cht_format.html">CHT file format.</a> The input - TIFF - file in - this situation, should be a good quality image, perhaps - synthetically - generated - (rather than being scanned), and perfectly oriented, to make - specification - of the patch locations easier. The file arguments are: <a - name="gp1"></a>The - TIFF file that - is to be processed, <a name="gp2"></a>the image recognition - template - file to be created, <a name="gp3"></a>and + scanin is operating in a mode designed to create the necessary + image recognition template file (<a + href="File_Formats.html#.cht">.cht</a>) boilerplate + information. Patch location and labeling information would need + to be added manually to such a generated file, to make a + complete and useable recognition template file. <a + href="cht_format.html">CHT file format.</a> The input TIFF + file in this situation, should be a good quality image, perhaps + synthetically generated (rather than being scanned), and + perfectly oriented, to make specification of the patch locations + easier. The file arguments are: <a name="gp1"></a>The TIFF file + that is to be processed, <a name="gp2"></a>the image + recognition template file to be created, <a name="gp3"></a>and an optional name for the image recognition diagnostic output.</li> <li><a name="o"></a>If the <b>-o</b> flag is used, then scanin - will - process the input TIFF file and produce a generic <a - href="File_Formats.html#CGATS">CGATS</a> - style file containing just the patch values (a <span - style="font-weight: bold;">.val</span> file). The file - arguments - are: <a name="op1"></a>The TIFF file that is to be processed, <a - name="op2"></a>the image recognition template file - to be created, <a name="op3"></a>and an optional name for the - image - recognition diagnostic - output.</li> + will process the input TIFF file and produce a generic <a + href="File_Formats.html#CGATS">CGATS</a> style file + containing just the patch values (a <span style="font-weight: + bold;">.val</span> file). The file arguments are: <a + name="op1"></a>The TIFF file that is to be processed, <a + name="op2"></a>the image recognition template file to be + created, <a name="op3"></a>and an optional name for the image + recognition diagnostic output.</li> <li><a name="c"></a>If the <b>-c</b> flag is used, then an input - image - of a print test chart can be used - in combination with a device profile, to estimate the CIE - tristimulus - values of the patches. This allows RGB - input devices to be used as a crude replacement for a color - measuring - instrument. The icc or mpp profile has - (presumably) been - created by scanning an IT8.7/2 chart (or similar) through the - RGB input - device, - and - then using scanin to create the .ti3 file needed to feed to - colprof to - 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 chart, then scanin - will need - to be run multiple times, once for each scan file made from each - test - chart. <a name="ca"></a>The <b>-ca</b> flag combination should - be - used - for all pages after the first, - as this then adds that pages test values to the .ti3 file, - rather than - creating - a .ti3 file that contains only that pages test values. If the - incoming - .ti2 file contains per-channel calibration - curves, these will be passed through to the .ti3 so that - accurate ink - limits can be computed during profiling. </li> + image of a print test chart can be used in combination with a + device profile, to estimate the CIE tristimulus values of the + patches. This allows RGB input devices to be used as a crude + replacement for a color measuring instrument. The icc or mpp + profile has (presumably) been created by scanning an IT8.7/2 + chart (or similar) through the RGB input device, and then using + scanin to create the .ti3 file needed to feed to colprof to + 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 + chart, then scanin will need to be run multiple times, once for + each scan file made from each test chart. <a name="ca"></a>The + <b>-ca</b> flag combination should be used for all pages after + the first, as this then adds that pages test values to the .ti3 + file, rather than creating a .ti3 file that contains only that + pages test values. If the incoming .ti2 file contains + per-channel calibration curves, these will be passed through to + the .ti3 so that accurate ink limits can be computed during + profiling. </li> <li><a name="r"></a>If the <span style="font-weight: bold;">-r</span> - flag is used, then the input TIFF value - is used as a source of device values to replace any existing - device - values in the given .ti3 - file. This is intended for use in the situation in which the - device - values - being fed into an output device are altered in some way that is - difficult - to predict (ie. such as being screened and then de-screened), - and this - alteration - to the device values needs to be taken into account in creating - a - profile - for such a device. The file arguments in -r mode are: <a - name="rp1"></a>The - TIFF file that - is to be processed containing a rasterized image of an output - test - chart, <a name="rp2"></a>the image recognition template file - for the - test - chart generated by the <a href="printtarg.html"> printtarg</a> - tool, <a name="rp3"></a>the base name for - the .ti2 file containing the output test chart device values and - their - patch + flag is used, then the input TIFF value is used as a source of + device values to replace any existing device values in the given + .ti3 file. This is intended for use in the situation in which + the device values being fed into an output device are altered in + some way that is difficult to predict (ie. such as being + screened and then de-screened), and this alteration to the + device values needs to be taken into account in creating a + profile for such a device. The file arguments in -r mode are: <a + name="rp1"></a>The TIFF file that is to be processed + containing a rasterized image of an output test chart, <a + name="rp2"></a>the image recognition template file for the + test chart generated by the <a href="printtarg.html"> printtarg</a> + tool, <a name="rp3"></a>the base name for the .ti2 file + containing the output test chart device values and their patch identifiers and the base name for the .ti3 file that is to have - its - device - values replaced, <a name="rp4"></a>and finally an optional name - for - the - image recognition diagnostic - output.<br> + its device values replaced, <a name="rp4"></a>and finally an + optional name for the image recognition diagnostic output.<br> </li> </ul> A number of flags and options are available, that are independent of - the - mode that scanin is in.<br> + the mode that scanin is in.<br> <br> Normally scanin will try and recognize a chart, irrespective of its orientation. For charts that have some asymmetric patch size or arrangement (such as an IT8.7/2, or a chart generated by <a - href="printtarg.html"> printtarg</a> - with the <b>-s</b> option), this is both flexible and reliable. - Other - charts - may be symmetrical, and therefore having scanin figure out the - orientation - automatically is a problem if the recognition template does not - contain - expected patch values, since it will have an equal chance of - orienting - it incorrectly as correctly. To solve this, the <a name="a"></a><b>-a</b> - flag can be - used, - and care taken to provide a raster file that is within 45 degrees of - "no - rotation".<br> + href="printtarg.html"> printtarg</a> with the <b>-s</b> option), + this is both flexible and reliable. Other charts may be symmetrical, + and therefore having scanin figure out the orientation automatically + is a problem if the recognition template does not contain expected + patch values, since it will have an equal chance of orienting it + incorrectly as correctly. To solve this, the <a name="a"></a><b>-a</b> + flag can be used, and care taken to provide a raster file that is + within 45 degrees of "no rotation".<br> <br> <a name="F"></a>Normally scanin will use automatic chart recognition - to - identify the location of the test patches and extract their values. - If - the chart <a href="cht_format.html">CHT file</a> + to identify the location of the test patches and extract their + values. If the chart <a href="cht_format.html">CHT file</a> has four fiducial marks defined, then the chart can be manually aligned by specifying the pixel location of the four marks as arguments to the <span style="font-weight: bold;"><span style="font-weight: bold;">-F</span></span> flag. The top left, - top - right, bottom right and bottom left fiducial marks X and Y - co-ordinates - should be - specified as a single concatenated argument, separated by comma's, - e.g: - -F 10,20,435,22,432,239,10,239 The coodinates may be - fractional using a decimal point. - Four fiducial marks allows for compensation for perspective - distortion.<br> + top right, bottom right and bottom left fiducial marks X and Y + co-ordinates should be specified as a single concatenated argument, + separated by comma's, e.g: -F 10,20,435,22,432,239,10,239 The + coodinates may be fractional using a decimal point. Four fiducial + marks allows for compensation for perspective distortion.<br> <br> <a name="p"></a>By default the automatic chart recognition copes - with - rotation, scale and stretch in the chart image, making it suitable - for - charts that have been scanned, or shot squarely with a camera. If a - chart has been shot not exactly facing the camera (perhaps to avoid - reflection, or to get more even lighting), then it will suffer from - perspective distortion as well. The <span style="font-weight: - bold;"><span style="font-weight: bold;">-p</span></span> flag - enables automatic - compensation for perspective distortion.<br> + with rotation, scale and stretch in the chart image, making it + suitable for charts that have been scanned, or shot squarely with a + camera. If a chart has been shot not exactly facing the camera + (perhaps to avoid reflection, or to get more even lighting), then it + will suffer from perspective distortion as well. The <span + style="font-weight: bold;"><span style="font-weight: bold;">-p</span></span> + flag enables automatic compensation for perspective distortion.<br> <br> <a name="m"></a>Normally scanin computes an average of the pixel - values - within a sample square, using a "robust" mean, that discards pixel - values that are too far from the average ("outlier" pixel values). - This - is done in an attempt to discard value that are due to scanning - artefacts such as dust, scratches etc. You can force scanin to - return - the true mean values for the sample squares that includes all the - pixel - values, by using the <span style="font-weight: bold;">-m</span> + values within a sample square, using a "robust" mean, that discards + pixel values that are too far from the average ("outlier" pixel + values). This is done in an attempt to discard value that are due to + scanning artefacts such as dust, scratches etc. You can force scanin + to return the true mean values for the sample squares that includes + all the pixel values, by using the <span style="font-weight: bold;">-m</span> flag.<br> <br> <a name="G"></a>Normally scanin has reasonably robust feature recognition, but the default assumption is that the input chart has - an - approximately even visual distribution of patch values, and has been - scanned and converted to a typical gamma 2.2 corrected image, - meaning - that the average patch pixel value is expected to be about 50%. If - this - is not the case (for instance if the input chart has been scanned - with - linear light or "raw" encoding), then it may enhance the image - recognition to provide the approximate gamma encoding of the image. - For - instance, if linear light encoding ("Raw") is used, a <span - style="font-weight: bold;">-G</span> value of 1.0 would be - appropriate. Values less than 2.2 should be tried if the chart is - particularly dark, or greater than 2.2 if the chart is particularly - light. Generally it is only necessary to provide this is there are - problems in recognizing the chart.<br> + an approximately even visual distribution of patch values, and has + been scanned and converted to a typical gamma 2.2 corrected image, + meaning that the average patch pixel value is expected to be about + 50%. If this is not the case (for instance if the input chart has + been scanned with linear light or "raw" encoding), then it may + enhance the image recognition to provide the approximate gamma + encoding of the image. For instance, if linear light encoding + ("Raw") is used, a <span style="font-weight: bold;">-G</span> value + of 1.0 would be appropriate. Values less than 2.2 should be tried if + the chart is particularly dark, or greater than 2.2 if the chart is + particularly light. Generally it is only necessary to provide this + is there are problems in recognizing the chart.<br> <br> <a name="v"></a> The <b>-v</b> flag enables extra verbosity in processing. This can aid debugging, if a chart fails to be recognized.<br> <br> <a name="d"></a> The <b>-d</b> flag enables the generation of an - image - recognition diagnostic raster. The name of diagnostic raster can be - specified as the last in the - command line, or if not, will default to <span style="font-weight: - bold;">diag.tif</span>. Various flags control what - is written to the diagnostic - raster. - Note that at least one flag must be specified for a diagnostic - raster - to be produced.<br> + image recognition diagnostic raster. The name of diagnostic raster + can be specified as the last in the command line, or if not, will + default to <span style="font-weight: bold;">diag.tif</span>. + Various flags control what is written to the diagnostic raster. Note + that at least one flag must be specified for a diagnostic raster to + be produced.<br> <b><a name="di"></a>i</b> creates a black and - white - version of the input raster in the diagnostic output, to be able to - compare with the feature extraction.<br> + white version of the input raster in the diagnostic output, to be + able to compare with the feature extraction.<br> <b><a name="dh"></a>h</b> will show pixels in the input image classified as being on horizontal edges, in red.<br> <b><a name="dv"></a>v</b> will show pixels in the input image classified as being vertical edges, in green.<br> <b><a name="dg"></a>g</b> will show groups of - pixels - that will be used - to estimate edge lines, each group in a different color.<br> + pixels that will be used to estimate edge lines, each group in a + different color.<br> <b><a name="dl"></a>l</b> will show valid lines estimated from the vertical and horizontal pixel groups, in white.<br> <b><a name="dL"></a>L</b> will show all lines - (valid - and invalid) estimated from the vertical and horizontal pixel - groups, - in white.<br> + (valid and invalid) estimated from the vertical and horizontal pixel + groups, in white.<br> <b><a name="dI"></a>I</b> will show valid lines lines - used - to improve the final fit, - in blue.<br> + used to improve the final fit, in blue.<br> <b><a name="dc"></a>c</b> will show the lines with perspective correction applied in cyan.<br> <b><a name="dr"></a>r</b> will show the lines - rotated - to the reference - chart orientation, in yellow.<br> + rotated to the reference chart orientation, in yellow.<br> <b><a name="ds"></a>s</b> will show the diagnostic sampling box edge outlines, rotated to the reference chart - orientation, - in orange.<br> + orientation, in orange.<br> <b><a name="do"></a>o</b> will show all the - sampling - box edge outlines, in orange.<br> + sampling box edge outlines, in orange.<br> <b><a name="dn"></a>n</b> will show the ID names - of - the sampling boxes, plus the diagnostic sample boxes, using a simple - stroke font, in orange.<br> + of the sampling boxes, plus the diagnostic sample boxes, using a + simple stroke font, in orange.<br> <b><a name="da"></a>a</b> will show the sampling areas as crossed boxes, plus the diagnostic sample boxes, in orange.<br> <b><a name="dp"></a>p</b> will show the sampling @@ -555,26 +456,21 @@ diag The combination of <b>-dipn</b> is usually a good place to start.<br> <br> The <a href="File_Formats.html#TIFF">TIFF</a> file can be either 8 - or - 16 bits per color component, with 16 bit files being slower to - process, - but yielding more precise results.<br> + or 16 bits per color component, with 16 bit files being slower to + process, but yielding more precise results.<br> <br> If at all in doubt that the file has been recognized correctly, use - the - <span style="font-weight: bold;">-dipn</span> diagnostic flag + the <span style="font-weight: bold;">-dipn</span> diagnostic flag combination, and check the resulting diagnostic raster file.<br> [ A badly recognised image will typically result in high self fit delta E's when used with colprof. ]<br> <br> <a name="O"></a>The <span style="font-weight: bold;">-O</span> - parameter allows the - output file name & extension to be specified independently of - the - last tiff - filename. Note that the full filename must be specified, including - the - extension.<br> + parameter allows the output file name & extension to be + specified independently of the last tiff filename. This works for + the default, -g and -o modes. It is ignored for the -r, -c and -ca + modes that use a basename for .ti2 in and .ti3 output. Note that the + full filename must be specified, including the extension. <br> <br> <br> <br> diff --git a/doc/spec2cie.html b/doc/spec2cie.html index 192ee64..c928f9a 100644 --- a/doc/spec2cie.html +++ b/doc/spec2cie.html @@ -19,7 +19,7 @@ Verbose mode</small></tt><br> <tt><small><small> <a - href="file:///D:/src/argyll/doc/spec2cie.html#I">-I <i>illum</i></a> + href="spec2cie.html#I">-I <i>illum</i></a> Override actual instrument illuminant in .ti3 file:<br> @@ -31,14 +31,14 @@ (only used in conjunction with <span style="font-weight: bold;">-f</span>)<br> </small></small></tt><tt><small><small> <a - href="file:///D:/src/argyll/doc/colprof.html#f">-f [<i>illum</i>]</a> + 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 - href="file:///D:/src/argyll/doc/spec2cie.html#i">-i <i>illum</i></a> + href="spec2cie.html#i">-i <i>illum</i></a> Choose illuminant for computation of CIE XYZ from spectral data & FWA:<br> @@ -93,7 +93,7 @@ Measurement bold;">-f</span> flag. If a filename is specified instead, it will be assumed to be an Argyll - specific <a href="file:///D:/src/argyll/doc/File_Formats.html#.sp">.sp</a> + specific <a href="File_Formats.html#.sp">.sp</a> custom spectrum file. Illuminant details are:<br> <br> @@ -130,7 +130,7 @@ Measurement 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:///D:/src/argyll/doc/File_Formats.html#.sp">.sp</a> + href="File_Formats.html#.sp">.sp</a> custom spectrum file. This only works if spectral data is available. Illuminant details are:<br> <br> diff --git a/doc/spotread.html b/doc/spotread.html index 0259530..aaac0a1 100644 --- a/doc/spotread.html +++ b/doc/spotread.html @@ -31,6 +31,9 @@ + + + Verbose mode</span><br style="font-family: monospace;"> <span style="font-family: monospace;"></span><span @@ -52,6 +55,9 @@ + + + Print spectrum for each reading.</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"></span><span @@ -78,6 +84,9 @@ + + + Set COM port, 1..4 (default 1)</span><span style="font-family: monospace;"></span><span style="font-family: monospace;"><br style="font-family: monospace;"> @@ -98,6 +107,9 @@ + + + Use transmission measurement mode</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style=" @@ -118,6 +130,9 @@ + + + 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 @@ -137,26 +152,15 @@ + + + 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 relative measurement mode<br> + 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 style="font-family: monospace;"> @@ -175,6 +179,9 @@ + + + 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 @@ -194,6 +201,9 @@ + + + Use </span></small><small><span style="font-family: monospace;">projector</span></small><small><span style="font-family: monospace;"> white brightness relative measurement mode<br> @@ -215,9 +225,13 @@ + + + Use </span></small><small><span style="font-family: monospace;">projector</span></small><small><span - style="font-family: monospace;"> white relative measurement mode</span></small><small><span - style="font-family: monospace;"></span></small><br> + style="font-family: monospace;"> </span></small><small><span + style="font-family: monospace;">white point relative + chromatically adjusted mode</span></small><br> <small><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#a">-a</a><span style="font-family: monospace;"> @@ -236,6 +250,9 @@ + + + Use ambient measurement mode (absolute results)<br> <a href="#f">-f</a> @@ -252,6 +269,9 @@ + + + Use ambient flash measurement mode (absolute results)<br> </span></small><font size="-1"><span style="font-family: monospace;"> <a href="#y">-y X</a> @@ -270,6 +290,9 @@ + + + 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 @@ -286,6 +309,9 @@ 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,6 +345,9 @@ D50 + + + D50M2, D65, F5, F8, F10 or file.sp</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style=" @@ -342,6 +371,9 @@ D50 + + + </span></small><small><span style="font-family: monospace;">1931_2 </span></small><small><span style="font-family: monospace;"> (def.)</span></small><small><span @@ -364,6 +396,9 @@ D50 + + + Set filter configuration:<br> n @@ -381,6 +416,9 @@ D50 + + + None<br> p @@ -398,6 +436,9 @@ D50 + + + Polarising filter<br> 6 @@ -415,6 +456,9 @@ D50 + + + D65<br> u @@ -432,6 +476,9 @@ D50 + + + U.V. Cut<br> <a href="#E">-E extrafilterfile</a> Apply extra filter compensation file<br> @@ -452,6 +499,9 @@ D50 + + + Display Yxy instead of Lab<br> </span></font><font size="-1"><span style="font-family: monospace;"> <a href="#h">-h</a> @@ -470,6 +520,9 @@ D50 + + + Display LCh instead of Lab</span></font><br> <font size="-1"><span style="font-family: monospace;"> <a href="#V">-V</a> @@ -488,6 +541,9 @@ 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> @@ -506,6 +562,9 @@ D50 + + + Display correlated color temperatures and CRI<br> </span></font><font size="-1"><span style="font-family: monospace;"> <a href="#N">-N</a> @@ -523,6 +582,9 @@ D50 + + + 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 @@ -546,6 +608,9 @@ D50 + + + Apply Colorimeter Correction Matrix</span></font><br> <span style="font-family: monospace;"> <a href="#X2">-X file.ccss</a> @@ -568,6 +633,9 @@ 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> @@ -579,14 +647,20 @@ 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 + 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> + Use non-adaptive integration time mode (if + available).</span></font><br> <font size="-1"><span style="font-family: monospace;"> <a href="#W">-W n|h|x</a> Override @@ -611,6 +685,9 @@ 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 @@ -633,6 +710,9 @@ none, + + + Optional file to save reading results<br style="font-family: monospace;"> </span></font><small><span style="font-family: monospace;"></span><span @@ -695,7 +775,9 @@ none, <a name="ew"></a>The <span style="font-weight: bold;">-ew</span> flag allows measuring in emissive mode using instruments that support this mode, with the reading being relative to the white - value read as the first reading.<br> + value read as the first reading using a Bradford chromatic adaption. + This matches the absolute <-> relative intent transformation + of Argyll ICC profiles.<br> <br> <a name="p"></a>The <span style="font-weight: bold;">-p</span> flag allows measuring in telephoto mode, using instruments that support @@ -714,7 +796,9 @@ none, <a name="pw"></a>The <span style="font-weight: bold;">-pw</span> flag allows measuring in telephoto mode using instruments that support this mode, with the reading being relative to the white - value read as the first reading.<br> + value read as the first reading using a Bradford chromatic adaption. + This matches the absolute <-> relative intent transformation + of Argyll ICC profiles.<br> <br> <a name="a"></a>The <span style="font-weight: bold;">-a</span> flag allows measuring in ambient illumination mode using instruments that @@ -749,9 +833,9 @@ 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="file:///D:/src/argyll/doc/ccxxmake.html">ccxxmake</a>, + using <a href="ccxxmake.html">ccxxmake</a>, and installed using <a - href="file:///D:/src/argyll/doc/oeminst.html">oeminst</a>. The + 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 @@ -883,6 +967,9 @@ 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 @@ -892,6 +979,9 @@ 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, @@ -899,6 +989,12 @@ a 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><b></b> + 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 @@ -975,6 +1071,10 @@ a can be toggled on and off using the <span style="font-weight: bold;">h</span> key.<br> <br> + If the instrument supports a laser target (such as the JETI + specbos), then this can be toggled on & off using the <b>t</b> + key. It will automatically be turned off at each measurement.<br> + <br> If the instrument supports stored readings (ie. DTP20), then these can be ignored using the <span style="font-weight: bold;">n</span> key.<br> diff --git a/doc/targen.html b/doc/targen.html index d03416f..ee12f27 100644 --- a/doc/targen.html +++ b/doc/targen.html @@ -3,7 +3,7 @@ <head> <title>targen</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,65 +11,112 @@ <h3>Summary</h3> Generate a profiling test target values <a href="File_Formats.html#.ti1">.ti1</a> file. <b>targen</b> - is - used to generate the device channel test point values for grayscale, - RGB, CMY, CMYK or N-color output or display devices. + is used to generate the device channel test point values for + grayscale, RGB, CMY, CMYK or N-color output or display + devices. <h3>Usage Summary</h3> <small><span style="font-family: monospace;">targen [options] outfile</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#v">-v [level]</a><span + style="font-family: monospace;"> + Verbose mode [optional verbose level, 1..n]</span><br style="font-family: monospace;"> - Verbose mode [optional - verbose level, 1..n]</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#d">-d col_comb</a><span style="font-family: monospace;"> choose colorant combination from the following:</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 0: - Print - grey</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 0: Print grey</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - - - 1: - Video - grey</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 1: Video grey</span><br + style="font-family: monospace;"> <span style="font-family: monospace;"> - - - - - 2: - Print - RGB</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 2: Print RGB</span><br + style="font-family: monospace;"> <span style="font-family: monospace;"> - - - 3: - Video RGB</span><br style="font-family: monospace;"> + + 3: Video RGB</span><br + style="font-family: monospace;"> <span style="font-family: monospace;"> - - - - 4: CMYK<br> - - 5: - CMY<br style="font-family: monospace;"> + + 4: CMYK<br> + + + + + + + + + + + + + + + 5: CMY<br style="font-family: monospace;"> </span><span style="font-family: monospace;"> - - - - 6: - CMYK + Light CM</span><br style="font-family: monospace;"> + + 6: CMYK + + Light CM</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - 7: CMYK + Light CMK</span><br - style="font-family: monospace;"> + + + + + + + + + + + + + + 7: + CMYK + Light CMK</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> @@ -79,150 +126,381 @@ CMYK + Red + + + + + + + + + + + + + + Blue</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - + 9: CMYK + Orange + Green</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - - 10: CMYK + - Light CMK + Light Light K</span><br style="font-family: - monospace;"> + + 10: CMYK + Light CMK + + Light Light K</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - + 11: CMYK + Orange + Green + Light CM</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - 12: CMYK + Light - CM + Medium CM</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 12: + CMYK + Light CM + Medium CM</span><br style="font-family: + monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#D">-D colorant</a><span style="font-family: monospace;"> Add or delete colorant from combination:</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - - - 0: - Additive</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + + 0: Additive</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 1: - Cyan</span><br style="font-family: monospace;"> + 1: Cyan</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - + 2: Magenta</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - + 3: Yellow</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - 4: - Black</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 4: Black</span><br + style="font-family: monospace;"> <span style="font-family: monospace;"> - - 5: + + + + + + + + + + + + + + 5: Orange</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 6: - Red</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 6: Red</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 7: - Green</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 7: Green</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 8: - Blue</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 8: Blue</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 9: - White</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 9: White</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 10: - Light - Cyan</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 10: Light Cyan</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 11: - Light - Magenta</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 11: Light Magenta</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 12: - Light - Yellow</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 12: Light Yellow</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> + + + + + + + + + + + + + - - 13: - Light - Black</span><br style="font-family: monospace;"> + 13: Light Black</span><br style="font-family: + monospace;"> <span style="font-family: monospace;"> - 14: - Medium - Cyan</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 14: Medium Cyan</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 15: - Medium - Magenta</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 15: Medium Magenta</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - 16: - Medium - Yellow</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 16: Medium Yellow</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - - - 17: - Medium - Black</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + 17: + Medium Black</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - 18: - Light - Light - Black<br> + + + + + + + + + + + + + + 18: Light + Light Black<br> <a href="#G">-G</a> - Generate - good - optimzed - points - rather - than - Fast<br style="font-family: monospace;"> + + + + + + + + + + + + + + Generate good optimzed points rather than Fast<br + style="font-family: monospace;"> </span><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#e">-e patches</a><span style="font-family: monospace;"> White - color test patches (default 4)</span><br style="font-family: + color test patches (default 4)</span></small><br + style="font-family: monospace;"> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#B">-B patches</a><span + style="font-family: monospace;"> + Black test patches (default 4 Grey/RGB, else 0)<br> + </span></small></span> <span style="font-family: + monospace;"></span><a style="font-family: monospace;" href="#s">-s + + + + + + + + + + + + steps</a><span style="font-family: monospace;"> + + + + + + + + + + + + + + Single channel steps (default 0)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#s">-s steps</a><span - style="font-family: monospace;"> - Single - channel - steps - (default - 0)</span><br style="font-family: monospace;"> - <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#g">-g steps</a><span style="font-family: monospace;"> Gray @@ -232,31 +510,101 @@ or CMY steps (default + + + + + + + + + + + + + 0)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#m">-m steps</a><span style="font-family: monospace;"> - Multidimensional - device - space - cube - steps - (default - 2)</span><br style="font-family: monospace;"> - <span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#f">-f patches</a><span - style="font-family: monospace;"> - Add - iterative & adaptive full spread patches to total (default - 836)<br> - - Default - is - Optimised - Farthest - Point - Sampling - (OFPS)<br style="font-family: monospace;"> + + + + + + + + + + + + + + Multidimensional device space cube steps (default 0)</span></small><br + style="font-family: monospace;"> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#b">-b steps</a><span + style="font-family: monospace;"> + + + + + + + + + + + + + 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 + + + + + + + + + + + + + patches</a><span style="font-family: monospace;"> + + + + + + + + + + + + + + Add iterative & adaptive full spread patches to total + (default 836)<br> + + + + + + + + + + + + + + + Default is Optimised Farthest Point Sampling (OFPS)<br + style="font-family: monospace;"> </span><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#t">-t</a><span style="font-family: monospace;"> @@ -267,6 +615,19 @@ incremental far point 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 @@ -278,6 +639,19 @@ device space random 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 @@ -289,6 +663,19 @@ perceptual space random 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 @@ -300,14 +687,26 @@ device space-filling quasi-random for + + + + + + + + + + + + + full spread<br> </span></small><small><span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#Q">-Q</a><span style="font-family: monospace;"> - - Use perceptual space-filling quasi-random for full spread</span></small><br - style="font-family: monospace;"> + Use perceptual space-filling quasi-random for full + spread</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="#i">-i</a><span @@ -319,6 +718,19 @@ device space body centered + + + + + + + + + + + + + cubic grid for full spread</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a @@ -331,8 +743,21 @@ perceptual space body centered - cubic grid for full - spread</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + cubic grid for full spread</span><br style="font-family: + monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#a">-a angle</a><span style="font-family: monospace;"> @@ -343,14 +768,26 @@ angle - 0.5 for - B.C.C. grid, default -2047840407</span><br style="font-family: + + + + + + + + + + + + + + B.C.C. grid, default 0.333300</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#A">-A adaptation</a><span style="font-family: monospace;"> - Degree - of adaptation of OFPS 0.0 - 1.0 (default 0.1, 1.0 if -c profile - provided)</span><br style="font-family: monospace;"> + Degree of adaptation of OFPS 0.0 - 1.0 (default 0.1, 1.0 if -c + profile provided)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> </span><a style="font-family: monospace;" href="#t">-t</a><span style="font-family: monospace;"> @@ -361,13 +798,38 @@ point for full spread - (default - iterative)</span><br style="font-family: monospace;"> + + + + + + + + + + + + + + (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 style="font-family: monospace;"> Total 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 @@ -379,104 +841,127 @@ applied to all device + + + + + + + + + + + + + values.</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="#c">-c profile</a><span style="font-family: monospace;"> Optional device ICC or MPP pre-conditioning profile filename<br> - <a href="#N">-N emphasis</a> - Degree of - neutral axis patch concentration 0-1. (default 0.50)<br + <a href="#N">-N nemphasis</a> Degree of + neutral axis patch concentration 0-1. (default 0.50)</span></small><br> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> <a href="#V">-V + demphasis</a> dark region patch + concentration 1.0-4.0 (default 1.0 = none)</span></small><br style="font-family: monospace;"> - </span> - <a style="font-family: monospace;" href="#F">-F L,a,b,rad</a><span - style="font-family: monospace;"> Filter out - samples - outside Lab sphere.</span><br style="font-family: monospace;"> + </span> <a style="font-family: monospace;" href="#F">-F + L,a,b,rad</a><span style="font-family: monospace;"> + + + + + + + + + + + + + Filter out samples outside Lab sphere.</span><br + style="font-family: monospace;"> <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 - (Lab - locations)<br> + + + + + + + + + + + + + + Dump diagnostic outfile.wrl 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 style="font-family: monospace;"> + + Dump diagnostic outfile.wrl file (Device locations)</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="#p1">outfile</a><span style="font-family: monospace;"> - Base - name - for - output(.ti1)</span></small> - <br> + + + + + + + + + + + + + + Base name for output(.ti1)</span></small> <br> <h3>Usage Details and Discussion<br> </h3> The number of target patches needs to be chosen, depending on the - media - size, the type of device, and the quality of profile required. For - an - inkjet device, something like 3000 test points or more is desirable - for high quality profiles, while 500-1000 will probably suffice for - a - medium quality profile. A few hundred may be sufficient for a - preliminary profile. Well behaved printing devices (such as a - chemical - proof, or a high quality printing press) may produce good profiles - with - 1000 to 2000 test points. Well behaved RGB devices such as CRT - monitors - may need only a few - hundred points, if a shaper/matrix type profile is to be produced, - while pseudo RGB printers, or other RGB devices that a CLUT type - profile may be used + media size, the type of device, and the quality of profile required. + For an inkjet device, something like 3000 test points or more is + desirable for high quality profiles, while 500-1000 will probably + suffice for a medium quality profile. A few hundred may be + sufficient for a preliminary profile. Well behaved printing devices + (such as a chemical proof, or a high quality printing press) may + produce good profiles with 1000 to 2000 test points. Well behaved + RGB devices such as CRT monitors may need only a few hundred points, + if a shaper/matrix type profile is to be produced, while pseudo RGB + printers, or other RGB devices that a CLUT type profile may be used with, should probably choose somewhere between 500 and 3000 patches. - For 'N' color profile creation, - 3000 or more test points should probably be used.<br> + For 'N' color profile creation, 3000 or more test points should + probably be used.<br> <br> <a name="v"></a> The <b>-v</b> flag turns on extra verbosity when generating patch values. Extra diagnostics and verbosity may be available if a parameter is provided with a value greater than 1.<br> <br> <a name="d"></a> The <b>-d</b> parameter sets the colorspace the - test - values will be generated in. Video gray space is assumed to be an - additive space, where a zero device value will be black, and a - maximum - device value will be white. A print gray space is assumed to be a - subtractive space, - in which a zero device value will be white, and a maximum device - value - will - be black. If no colorspace is specified, subtractive CMYK is assumed - as - a default.<br> + test values will be generated in. Video gray space is assumed to be + an additive space, where a zero device value will be black, and a + maximum device value will be white. A print gray space is assumed to + be a subtractive space, in which a zero device value will be white, + and a maximum device value will be black. If no colorspace is + specified, subtractive CMYK is assumed as a default.<br> <br> <a name="D"></a> The <b>-D</b> parameter modifies the colorspace - set - by <span style="font-weight: bold;">-d</span> by allowing - individual - colorants to be added or subtracted from the colorspace.<br> + set by <span style="font-weight: bold;">-d</span> by allowing + individual colorants to be added or subtracted from the colorspace.<br> <br> <a name="G"></a> The <b>-G</b> flag changes the Incremental Far - Point - Distribution - algorithm from fast to good mode. Fast mode uses a limited number of - iterations to optimize the patch locations, while good mode strives - for - a more even patch distribution by using more iterations.<br> + Point Distribution algorithm from fast to good mode. Fast mode uses + a limited number of iterations to optimize the patch locations, + while good mode strives for a more even patch distribution by using + more iterations.<br> <br> The composition of the test patches is controlled by the following flags and parameters:<br> @@ -485,309 +970,286 @@ device colored test patches, defaulting to 4 if the -e flag isn't used. The white patches are usually very important in establishing white point that the ICC data is made relative to, so it improves robustness to - use - more than a - single point.<br> + use more than a single point.<br> + <br> + <a name="B"></a> The <b>-B</b> parameter sets the number of black + colored test patches, defaulting to 4 if the -B flag isn't used and + the colorspace is grey or RGB. The black point can be very important + for characterizing additive color spaces, so measuring more than one + black patch improves robustness over measuring just a single point.<br> <br> <a name="s"></a> The <b>-s</b> parameter sets the number of patches in a set of per colorant wedges. The steps are evenly spaced in - device - space by default, and the total number of test patches will be the - number of - colorants - times the value specified with the -s flag. If the <span - style="font-weight: bold;">-p</span> parameter is provided, then, - then the steps will be distributed according to the power value. - e.g. - the option <span style="font-weight: bold;">-s 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 colorant - test wedge values are generated. When creating a test chart for a - device - that will be used as a source colorspace, it is often useful to - generated - some per colorant wedge values.<br> + device space by default, and the total number of test patches will + be the number of colorants times the value specified with the -s + flag. If the <span style="font-weight: bold;">-p</span> parameter + is provided, then, then the steps will be distributed according to + the power value. e.g. the option <span style="font-weight: bold;">-s + + + + + + + + + + + + + 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 + colorant test wedge values are generated. When creating a test chart + for a device that will be used as a source colorspace, it is often + useful to generated some per colorant wedge values.<br> <br> <a name="g"></a> The <b>-g</b> parameter sets the number of patches in a set of combined (nominally gray) wedges. This will typically be equal RGB or CMY values, and by default will be equally spaced steps - in - device - space. If the <span style="font-weight: bold;">-p</span> parameter - is - provided, then, - then the steps will be distributed according to the power value. - e.g. - the option <span style="font-weight: bold;">-g 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;">-g 5 -p 2.0</span> will generate steps - at - 0.0 - 0.0625 0.25 0.5625 and 1.0. By - default, no gray combination values are generated. When creating a - test - chart for a device that will be used as a source colorspace, it is - often - useful to generated some per colorant wedge values.<br> + in device space. If the <span style="font-weight: bold;">-p</span> + parameter is provided, then, then the steps will be distributed + according to the power value. e.g. the option <span + style="font-weight: bold;">-g 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;">-g 5 -p 2.0</span> will generate steps at 0.0 0.0625 0.25 + 0.5625 and 1.0. By default, no gray combination values are + generated. When creating a test chart for a device that will be used + as a source colorspace, it is often useful to generated some per + colorant wedge values.<br> <br> <a name="m"></a> The <b>-m</b> parameter sets the edge size of the multidimensional grid of test values. The total number of patches of this type will be the -m parameter value to the power of the number - of - colorants. The grid steps are evenly spaced in device space by - default, - but if the <span style="font-weight: bold;">-p</span> parameter is - provided, then, - then the steps will be distributed according to the power value. - e.g. - the option <span style="font-weight: bold;">-m 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;">-m 5 -p 2.0</span> will generate steps - at - 0.0 - 0.0625 0.25 0.5625 and 1.0. By - default, all the device primary color combinations that fall within - the - ink limit are generated..<br> - <br> - The behavior of the <b>-e</b>, <b>-s</b>, <b>-g</b> and <b>-m</b> - flags, is not to duplicate test values already created by a previous - type.<br> + of colorants. The grid steps are evenly spaced in device space by + default, but if the <span style="font-weight: bold;">-p</span> + parameter is provided, then, then the steps will be distributed + according to the power value. e.g. the option <span + style="font-weight: bold;">-m 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;">-m 5 -p 2.0</span> will generate steps at 0.0 0.0625 0.25 + 0.5625 and 1.0. By default, all the device primary color + combinations that fall within the ink limit are generated..<br> + <br> + <a name="m"></a> The <b>-b</b> parameter sets the outer edge size + of the multidimensional body centered grid of test values. The total + number of patches of this type will be the -b parameter value to the + power of the number of colorants plus the (number-1) to the power of + the number of colorants. The grid steps are evenly spaced in device + space by default, but if the <span style="font-weight: bold;">-p</span> + parameter is provided, then, then the steps will be distributed + according to the power value. A body centered grid is a regular grid + (see <b>-m</b>) with another smaller regular grid within it, at the + centers of the outer grid. This grid arrangement is more space + efficient than a regular grid (ie. for a given number of test + points, it fills the space better.)<br> + <br> + The behavior of the <b>-e</b>, <b>-s</b>, <b>-g</b> <b>-m </b>and + + + + + + + + + + + + + <b>-b</b> flags, is not to duplicate test values already created by + a previous type.<br> <br> <a name="f"></a> The <b>-f</b> parameter sets the number of full spread test patches. Full spread patches are distributed according - to - the default or chosen algorithm. The default algorithm will optimize - the point locations to minimize the distance from any point in - device - space, to the nearest - sample point. This is called Optimized Farthest Point Sampling - (OFPS) . - This can be overridden by specifying the <b>-t. -r, -R, - -q, - -i or -I</b> flags. If the default OFPS algorithm is used, then - adaptive - test - point distribution can be fully enabled by supplying a previous or - typical profile with the <span style="font-weight: bold;">-c</span> - option. The total number patches specified will - include any - patches - generated using the <b>-e</b>, <b>-s</b>, <b>-g</b> and <b>-m</b> - flags (i.e. - full spread patches will be added to bring the total number of - patches - including - those generated using the <b>-e</b>, <b>-s</b>, <b>-g</b> and <b>-m</b> - flags - up to the specified number). When there are more than four device - channels, - the full spread distribution algorithm can't deal with so many - dimensions, - and <b>targen</b> falls back on an incremental far point - distribution - algorithm - by default, that doesn't generate such evenly spread points. This - behaviour - can be forced using the <b>-t</b> flag. A <a href="#Table">table</a> - of useful total patch counts for different paper sizes is shown - below. + to the default or chosen algorithm. The default algorithm will + optimize the point locations to minimize the distance from any point + in device space, to the nearest sample point. This is called + Optimized Farthest Point Sampling (OFPS) . This can be overridden by + specifying the <b>-t. -r, -R, -q, -i or -I</b> flags. If the + default OFPS algorithm is used, then adaptive test point + distribution can be fully enabled by supplying a previous or typical + profile with the <span style="font-weight: bold;">-c</span> option. + The total number patches specified will include any patches + generated using the <b>-e</b>, <b>-s</b>, <b>-g</b> <b>-m</b> + and <b>-b</b> flags (i.e. full spread patches will be added to + bring the total number of patches including those generated using + the <b>-e</b>, <b>-s</b>, <b>-g</b> <b>-m </b>and <b>-b</b> + flags up to the specified number). When there are more than four + device channels, the full spread distribution algorithm can't deal + with so many dimensions, and <b>targen</b> falls back on an + incremental far point distribution algorithm by default, that + doesn't generate such evenly spread points. This behaviour can be + forced using the <b>-t</b> flag. A <a href="#Table">table</a> of + useful total patch counts for different paper sizes is shown below. Note that it's occasionally the case that the OFPS algorithm will - fail - to complete, or make very slow progress if the <span + fail to complete, or make very slow progress if the <span style="font-weight: bold;">-c</span> profile is poor, non-smooth, - or - has unusual behaviour. In these cases a different algorithm should - be - chosen (ie. <span style="font-weight: bold;">-Q</span> or <span - style="font-weight: bold;">-I</span>), or perhaps a smoother or - lower - resolution ("quality") previous profile may overcome the problem. <br> + or has unusual behaviour. In these cases a different algorithm + should be chosen (ie. <span style="font-weight: bold;">-Q</span> or + <span style="font-weight: bold;">-I</span>), or perhaps a smoother + or lower resolution ("quality") previous profile may overcome the + problem. <br> <br> <a name="t"></a> The <b>-t</b> flag overrides the default full - spread - test patch algorithm, and makes use of the Incremental Far Point - Distribution - algorithm, which incrementally searches for test points that are as - far - away - as possible from any existing points. This is used as the default - for - dimensions - higher than 4.<br> + spread test patch algorithm, and makes use of the Incremental Far + Point Distribution algorithm, which incrementally searches for test + points that are as far away as possible from any existing points. + This is used as the default for dimensions higher than 4.<br> <br> <a name="r"></a> The <b>-r</b> flag overrides the default full - spread - test patch algorithm, and chooses test points with an even random - distribution in device space.<br> + spread test patch algorithm, and chooses test points with an even + random distribution in device space.<br> <br> <a name="R"></a> The <b>-R</b> flag overrides the default full - spread - test patch algorithm, and chooses test points with an even random - distribution in perceptual space.<br> + spread test patch algorithm, and chooses test points with an even + random distribution in perceptual space.<br> <br> <a name="q"></a> The <b>-q</b> flag overrides the default full - spread - test patch algorithm, and chooses test points with a quasi-random, - space filling distribution in device space.<br> + spread test patch algorithm, and chooses test points with a + quasi-random, space filling distribution in device space.<br> <br> <a name="Q"></a> The <b>-Q</b> flag overrides the default full - spread - test patch algorithm, and chooses test points with a quasi-random, - space filling distribution in perceptual space.<br> + spread test patch algorithm, and chooses test points with a + quasi-random, space filling distribution in perceptual space.<br> <br> <a name="i"></a> The <b>-i</b> flag overrides the default full - spread - test patch algorithm, and chooses test points with body centered - cubic - distribution in device space.<br> + spread test patch algorithm, and chooses test points with body + centered cubic distribution in device space.<br> <br> <a name="I"></a> The <b>-I</b> flag overrides the default full - spread - test patch algorithm, and chooses test points with body centered - cubic - distribution in perceptual space.<br> + spread test patch algorithm, and chooses test points with body + centered cubic distribution in perceptual space.<br> <br> <a name="a"></a> The <b>-a <i>angle</i></b> parameter sets the - overall - angle that the body centered grid distribution has.<br> + overall angle that the body centered grid distribution has.<br> <br> <a name="A"></a> The <b>-A <i>adaptation</i></b> parameter sets - the - degree of adaptation to the known device characteristics, used by - the - default full spread OFPS algorithm. A profile - should be provided using the <span style="font-weight: bold;">-c</span> + the degree of adaptation to the known device characteristics, used + by the default full spread OFPS algorithm. A profile should be + provided using the <span style="font-weight: bold;">-c</span> parameter if <span style="font-weight: bold; font-style: italic;">adaptation</span> - is set above a low level. By - default the adaptation is 0.1 (low), and 1.0 (maximum) if <span - style="font-weight: bold;">-c profile</span> is provided, but - these - defaults can be overridden using this option. For instance, if the <span - style="font-weight: bold;">-c profile</span> doesn't represent the - device behavior very well, a lower adaption than 1.0 might be - appropriate.<br> + is set above a low level. By default the adaptation is 0.1 (low), + and 1.0 (maximum) if <span style="font-weight: bold;">-c profile</span> + is provided, but these defaults can be overridden using this option. + For instance, if the <span style="font-weight: bold;">-c profile</span> + doesn't represent the device behavior very well, a lower adaption + than 1.0 might be appropriate.<br> <br> <a name="l"></a> The <b>-l</b> flag and parameter sets a total ink - limit (Total - Area Coverage or TAC), which is adhered to for all the generated - points. It is generally good practice to set a test chart ink limit - at - least 10% higher than the ink limit that will be applied when making - the resulting profile. In the case of device cube points, this can - generate extra test - values that lie at the ink limit boundary. For gray wedge values, - any - that exceed the ink limit are omitted. Full spread test values are - all - generated to lie - within the ink limit. Although it doesn't make much sense, this - parameter has an affect on additive device spaces (such as RGB), but - should not normally be used with such devices. The total ink limit - value will be written to the - .ti1 file, and carried through automatically to the .ti3 file, so - that - it - can be used during profile creation. If a profile is provided using - the - <span style="font-weight: bold;">-c</span> flag, then this will be - used - to estimate an ink limit, if none is provided with the <span - style="font-weight: bold;">-l</span> flag. Ink limits are, as far - as - possible, always in final calibrated device values, and the - calibration - curves from the profile provided to the <span style="font-weight: - bold;">-c</span> flag will be used to estimate the - equivalent limit in the underlying pre-calibration device space - values - that targen creates.<br> + limit (Total Area Coverage or TAC), which is adhered to for all the + generated points. It is generally good practice to set a test chart + ink limit at least 10% higher than the ink limit that will be + applied when making the resulting profile. In the case of device + cube points, this can generate extra test values that lie at the ink + limit boundary. For gray wedge values, any that exceed the ink limit + are omitted. Full spread test values are all generated to lie within + the ink limit. Although it doesn't make much sense, this parameter + has an affect on additive device spaces (such as RGB), but should + not normally be used with such devices. The total ink limit value + will be written to the .ti1 file, and carried through automatically + to the .ti3 file, so that it can be used during profile creation. If + a profile is provided using the <span style="font-weight: bold;">-c</span> + flag, then this will be used to estimate an ink limit, if none is + provided with the <span style="font-weight: bold;">-l</span> flag. + Ink limits are, as far as possible, always in final calibrated + device values, and the calibration curves from the profile provided + to the <span style="font-weight: bold;">-c</span> flag will be used + to estimate the equivalent limit in the underlying pre-calibration + device space values that targen creates.<br> <br> <a name="p"></a> The <b>-p</b> flag and parameter sets a power-like - value - applied to all of the device values after they are generated, <span - style="font-weight: bold;"></span><span style="font-weight: bold;"></span>the -spacer -colors. -This -can -be -useful -in - creating calibration charts for - very non-linearly behaved devices. A value greater than 1.0 will - cause - a tighter spacing of test values near device value 0.0, while a - value - less than 1.0 will cause a tighter spacing near device value 1.0. <span - style="font-weight: bold;">printcal</span> will recommend a - power-like - value if the verbose option is used. [ <span style="font-weight: - bold;">Note</span> - that for Print RGB space this - is reversed, since internally a Print RGB space is treated as a CMY - space. ]. <span style="font-weight: bold;">Note</span> that the - device - model used to create the expected patch values will not take into - account the applied power, nor will the more complex full spread - algorithms correctly take into account the power in generating - values - up to the ink limits. (A power-like function is used, to avoid the - excessive compression that a real power function would apply).<br> + value applied to all of the device values after they are generated, + <span style="font-weight: bold;"></span><span style="font-weight: + bold;"></span>the spacer colors. This can be useful in creating + calibration charts for very non-linearly behaved devices. A value + greater than 1.0 will cause a tighter spacing of test values near + device value 0.0, while a value less than 1.0 will cause a tighter + spacing near device value 1.0. <span style="font-weight: bold;">printcal</span> + will recommend a power-like value if the verbose option is used. [ <span + style="font-weight: bold;">Note</span> that for Print RGB space + this is reversed, since internally a Print RGB space is treated as a + CMY space. ]. <span style="font-weight: bold;">Note</span> that the + device model used to create the expected patch values will not take + into account the applied power, nor will the more complex full + spread algorithms correctly take into account the power in + generating values up to the ink limits. (A power-like function is + used, to avoid the excessive compression that a real power function + would apply).<br> <br> <a name="c"></a> The <b>-c</b> flag and parameter is used to - specify - an <a href="File_Formats.html#ICC">ICC</a> or <a + specify an <a href="File_Formats.html#ICC">ICC</a> or <a href="File_Formats.html#MPP">MPP</a> pre-conditioning profile, for estimating perceptual distances and colorspace curvature, used in optimizing the full spread test point placement,or in creating - perceptualy spaced distributions. Normally a previous - profile for this or a similar device will be used, or a simpler, - preliminary profile will be created and used. If no such profile is - specified, a default device space model is used. Note that this - will only have an effect if an algorithm that uses perceptual - placement (such as <span style="font-weight: bold;">-R, -Q, -I</span> - or the default OFPS with an - <span style="font-weight: bold;">-A</span> value > 0.0) is being - used.<br> - <br> - <a name="N"></a> The <b>-N emphasis</b> parameter allows changing - the - degree to which the patch distribution should emphasise the neutral - axis. Since the neutral axis is regarded as the most visually - critical - are of the color space, it can help maximize the quality of the - resulting profile to place more measurement patches in this region. - This emphasis is only effective for perceptual patch distributions, - and - for the default OFPS distribution if the <a href="#A">adaptation</a> - parameter is set to a high value. It is also most effective when a <a - href="#c">pre-conditioning</a> profile is provided, since this is - the - only way that neutral can be determined. The default value of 0.5 - provides an affect about twice the emphasis of the CIE94 Delta E - formula.<br> + perceptualy spaced distributions. Normally a previous profile for + this or a similar device will be used, or a simpler, preliminary + profile will be created and used. If no such profile is specified, a + default device space model is used. Note that this will only have an + effect if an algorithm that uses perceptual placement (such as <span + style="font-weight: bold;">-R, -Q, -I</span> or the default OFPS + with an <span style="font-weight: bold;">-A</span> value > 0.0) + is being used.<br> + <br> + <a name="N"></a> The <b>-N nemphasis</b> parameter allows changing + the degree to which the patch distribution should emphasise the + neutral axis. Since the neutral axis is regarded as the most + visually critical are of the color space, it can help maximize the + quality of the resulting profile to place more measurement patches + in this region. This emphasis is only effective for perceptual patch + distributions, and for the default OFPS distribution if the <a + href="#A">adaptation</a> parameter is set to a high value. It is + also most effective when a <a href="#c">pre-conditioning</a> + profile is provided, since this is the only way that neutral can be + determined. The default value of 0.5 provides an affect about twice + the emphasis of the CIE94 Delta E formula.<br> + <br> + <a name="V"></a> The <b>-V demphasis</b> parameter allows changing + the degree to which the patch distribution should emphasis dark + region of the device response. Display devices used for video or + film reproduction are typically viewed in dark viewing environments + with no strong white reference, and typically employ a range of + brightness levels in different scenes. This often means that the + devices dark region response is of particular importance, so + increasing the relative number of sample points in the dark region + may improved the balance of accuracy of the resulting profile for + video or film reproduction. This emphasis is only effective for + perceptual patch distributions where a <a href="targen.html#c">pre-conditioning</a> + profile is provided. The default value of 1.0 provides no emphasis + of the dark regions. A value somewhere around <b>1.5 - 2.0</b> is a + good place to start for video profile use. A scaled down version of + the -V parameter will be passed on through the .ti3 file to colprof + where it will set a default value for the corresponding <a + href="colprof.html#V">colprof -V</a> parameter. Note that + increasing the proportion of dark patches will typically lengthen + the time that an instrument takes to read the whole chart. + Emphasizing the dark region characterization will reduce the + accuracy of measuring and modelling the lighter regions, given a + fixed number of test points and profile quality/grid resolution. The + parameter will also be used in an analogous way to the <small><a + href="file:///D:/src/argyll/doc/targen.html#p">-p power</a> + value in changing the distribution of </small><small><a + href="file:///D:/src/argyll/doc/targen.html#s">-s steps</a>, </small><small><a + href="file:///D:/src/argyll/doc/targen.html#g">-g steps</a>, </small><small><a + href="file:///D:/src/argyll/doc/targen.html#m">-m steps</a></small> + and <small><small><a href="file:///D:/src/argyll/doc/targen.html#b">-b + + + + steps</a></small></small> patches.<br> <br> <a name="F"></a> The <b>-F</b> flag and parameters is used to - define - an L*a*b* sphere to filter the test points through. Only test points - within the sphere (defined by it's center and radius) will be - written - to the .ti1 file. This can be good for targeting supplemental test - points at a troublesome area of a device. The accuracy of the L*a*b* - target will be best when the <span style="font-weight: bold;">-c</span> - option is used to specify a reasonably accurate profile for the - device. - Note that the actual number of points generated can be hard to - predict, - and will depend on the type of generation used. All means of - generating - points except the -f N & -r, -R and -q will generate a smaller - number of test points than expected. If the -f N & -r, -R and -q + define an L*a*b* sphere to filter the test points through. Only test + points within the sphere (defined by it's center and radius) will be + written to the .ti1 file. This can be good for targeting + supplemental test points at a troublesome area of a device. The + accuracy of the L*a*b* target will be best when the <span + style="font-weight: bold;">-c</span> option is used to specify a + reasonably accurate profile for the device. Note that the actual + number of points generated can be hard to predict, and will depend + on the type of generation used. All means of generating points + except the -f N & -r, -R and -q will generate a smaller number + of test points than expected. If the -f N & -r, -R and -q 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> @@ -798,35 +1260,29 @@ in strange, since the extra K dimension is compressed into the 3 dimensional L*a*b* space. <a name="W"></a>If the <span style="font-weight: bold;">-W</span> flag is given, the plot will - be - in device space, with only the first 3 dimensions of each point - being - plotted.<br> + be in device space, with only the first 3 dimensions of each point + being plotted.<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> output - file. <b>targen</b> will add the .ti1 extension automatically.<br> + base filename for the <a href="File_Formats.html#.ti1">.ti1</a> + output file. <b>targen</b> will add the .ti1 extension + automatically.<br> <br> Some typical total patch number/paper size combinations are shown below. These "magic" numbers are found by using <a href="printtarg.html">printtarg</a> to compute the row length and number of rows, and then adjusting the total number of patches to - fill - the last row or paper size, in an iterative fashion.<br> + fill the last row or paper size, in a trial and error fashion.<br> <br> <a name="Table"></a> Size (mm/Standard Name), - - No. Patches<br> + No. Patches<br> <br> DTP20:<br> <br> 1 x A4 540<br> 2 x A4 1080<br> - 3 x A4 - 1620<br> - 4 x A4 - 2160<br> + 3 x A4 1620<br> + 4 x A4 2160<br> <br> 1 x Letter 570<br> 2 x Letter 1140<br> @@ -844,41 +1300,27 @@ in DTP41:<br> <br> 1 x A4 - - - 375<br> + 375<br> 2 x A4 - - - 750<br> + 750<br> 3 x A4 - - - 1125<br> + 1125<br> 4 x A4 - - - 1500<br> + 1500<br> <br> 1 x Letter - - 345<br> + 345<br> 2 x Letter - - 690<br> + 690<br> 3 x Letter - - 1035<br> + 1035<br> 4 x Letter - - 1380<br> + 1380<br> <br> 1 x A3 - - 836<br> + 836<br> 2 x A3 - - 1672<br> + 1672<br> <br> 1 x 11x17 780<br> @@ -889,55 +1331,41 @@ in DTP51:<br> <br> 1 x A4 - - - 266<br> + 266<br> 2 x A4 - - - 532<br> + 532<br> 3 x A4 - - - 798<br> + 798<br> 4 x A4 - - - 1064<br> + 1064<br> <br> 1 x Letter - - 252<br> + 252<br> 2 x Letter - - 504<br> + 504<br> 3 x Letter - - 756<br> + 756<br> 4 x Letter 1008<br> <br> 1 x A3 - - 580<br> + 580<br> 2 x A3 - - 1160<br> + 1160<br> <br> 1 x 11x17 570<br> 2 x 11x17 - - 1140<br> + 1140<br> <br> SpectroScan with square patches:<br> <br> 1 x A4R 1014<br> 2 x A4R 2028<br> - 3 x A4R - 3042<br> - 4 x A4R - 4056<br> + 3 x A4R + 3042<br> + 4 x A4R + 4056<br> <br> 1 x LetterR 999<br> 2 x LetterR 1998<br> @@ -948,10 +1376,10 @@ in <br> 1 x A4R 1170<br> 2 x A4R 2340<br> - 3 x A4R - 3510<br> - 4 x A4R - 4680<br> + 3 x A4R + 3510<br> + 4 x A4R + 4680<br> <br> 1 x LetterR 1092<br> 2 x LetterR 2184<br> @@ -962,10 +1390,8 @@ in <br> 1 x A4 441<br> 2 x A4 882<br> - 3 x A4 - 1323<br> - 4 x A4 - 1764<br> + 3 x A4 1323<br> + 4 x A4 1764<br> <br> 1 x Letter 462<br> 2 x Letter 924<br> diff --git a/doc/tiffgamut.html b/doc/tiffgamut.html index bc63ce7..5b67603 100644 --- a/doc/tiffgamut.html +++ b/doc/tiffgamut.html @@ -9,182 +9,195 @@ <body> <h2><b>xicc/tiffgamut</b></h2> <h3>Summary</h3> - Create a gamut file or VRML file of the color gamut of the - contents of a set of TIFF or JPEG image.<br> + Create a gamut file or VRML 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. 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 with <a href="collink.html"> - collink</a>.<br> + 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. + 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 + with <a href="collink.html"> collink</a>.<br> <br> <span style="font-weight: bold;">NOTE</span> that if you are - creating - an image gamut suitable for use with the <a href="collink.html">collink</a> - <a href="collink.html#g">-g</a> or <a href="collink.html#G">-G</a> - flags, or <a href="colprof.html#g">colprof - -g</a>, use the Jab appearance space 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> + creating an image gamut suitable for use with the <a + href="collink.html">collink</a> <a href="collink.html#g">-g</a> + or <a href="collink.html#G">-G</a> flags, or <a + href="colprof.html#g">colprof -g</a>, use the Jab appearance space + 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> <h3>Usage Summary</h3> <small><span style="font-family: monospace;">tiffgamut [-v level] [profile.icm | embedded.tif/jpg] infile1.tif/jpg [infile2.tif/jpg ...]</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -v + + Verbose</span><br style="font-family: monospace;"> - - <span style="font-family: monospace;">-d - sres Surface - resolution details 1.0 - 50.0</span><br style="font-family: - monospace;"> + <span style="font-family: monospace;">-d + sres Surface resolution + details 1.0 - 50.0</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -w emit + + VRML .wrl 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 + + markers for prim. & sec. "cusp" points<br> -f perc Filter by - popularity, - perc = percent to use<br style="font-family: monospace;"> + popularity, perc = percent to use<br style="font-family: + monospace;"> </span><span style="font-family: monospace;"> -i - intent p = - perceptual, r = relative colorimetric,</span><br - style="font-family: monospace;"> + intent p = perceptual, r = relative + colorimetric,</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> s + + = saturation, a = absolute (default), d = profile default</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;"> -o - order n = normal - (priority: lut > matrix > monochrome)</span><br - style="font-family: monospace;"> + order n = normal (priority: lut + > matrix > monochrome)</span><br style="font-family: + monospace;"> <span style="font-family: monospace;"> r - = reverse (priority: monochrome > - matrix > lut)<br> + + + = reverse (priority: monochrome > matrix > lut)<br> </span></small><small><span style="font-family: monospace;"> </span><span style="font-family: monospace;">-p oride</span><span style="font-family: monospace;"> l - = - Lab_PCS (default), j = CIECAM02 Appearance Jab</span></small><br + = Lab_PCS (default), j = CIECAM02 Appearance Jab</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"></span><span style="font-family: monospace;"> -c viewcond - set - appearance mode and viewing conditions for CIECAM02,</span><br + set appearance mode and viewing conditions for CIECAM02,</span><br style="font-family: monospace;"> <span style="font-family: monospace;"></span><span style="font-family: monospace;"></span></small><small><span style="font-family: monospace;"> either + + an enumerated choice, or a parameter:value change</span><span style="font-family: monospace;"></span><br style="font-family: monospace;"> <span style="font-family: monospace;"></span></small><small><span - style="font-family: monospace;"> - pp - Practical Reflection - Print - (ISO-3664 P2)</span><br style="font-family: monospace;"> + style="font-family: monospace;"> + pp - Practical Reflection Print (ISO-3664 P2)</span><br + style="font-family: monospace;"> <span style="font-family: monospace;"> + + 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;"> - <span style="font-family: monospace;"> - mt - Monitor in typical work environment</span><br + <span style="font-family: monospace;"> + mt - Monitor in typical work environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> + + mb - Monitor in bright work environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - md - Monitor in darkened work + md - Monitor in darkened work environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - jm - Projector in dim environment</span><br + jm - Projector in dim environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - jd - Projector in dark environment</span><br + jd - Projector in dark environment</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - pcd - Photo CD - original scene - outdoors</span><br style="font-family: monospace;"> + pcd - Photo CD - original scene outdoors</span><br + style="font-family: monospace;"> <span style="font-family: monospace;"> - - ob - Original scene - Bright Outdoors</span><br + ob - Original scene - Bright Outdoors</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - cx - Cut Sheet Transparencies on a viewing - box</span></small><br style="font-family: monospace;"> + cx - Cut Sheet Transparencies on a + viewing box</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"> 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;"> + + + 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;"> + + + 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;"> + + + 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:scenewhite Scene - white in - cd.m^2 if surround = auto (default 250)<br style="font-family: - monospace;"> - </span><span style="font-family: monospace;"> + l:imagewhite Image + white in cd.m^2 if surround = auto (default 250)</span></small><br + style="font-family: monospace;"> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> f:flare - Flare - light % of image luminance (default 1)</span><br - style="font-family: monospace;"> + + + Flare light % of image luminance (default 1)<br> + </span></small> </span><span style="font-family: + monospace;"> + g:glare Glare light % of ambient + (default 1)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> - - f:X:Y:Z Flare color as - XYZ (default media white)</span><br style="font-family: + g:X:Y:Z Glare color + as XYZ (default media white)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -f:x:y - Flare color as x, y<br> + + g:x:y Glare color as + x, y<br> -O outputfile Override the default output filename & extension.<br style="font-family: monospace;"> </span></small><br> @@ -193,148 +206,116 @@ f:x:y The<b> -v</b> flag dumps out the ICC profile header information.<br> <br> The <b>-d</b> parameter controls the level of detail displayed in - the - surface. The parameter roughly corresponds to a deltaE value, so - smaller - values - give greater detail. The default value is around 10, and is a good - place - to start. Small values may take a lot of time to generate, and will - produce - big files.<br> + the surface. The parameter roughly corresponds to a deltaE value, so + smaller values give greater detail. The default value is around 10, + 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 gamut file.<br> <br> - The <b>-n</b> flag suppresses the L*a*b* axes being created in - the + The <b>-n</b> flag suppresses the L*a*b* axes being created in the VRML.<br> <br> The <span style="font-weight: bold;">-k</span> flag adds markers - for - each of the primary and secondary "cusp" points (Red, Yellow, Green, - Cyan, Blue & Magenta). No markers will be displayed if the cusps - cannot be determined.<br> + for each of the primary and secondary "cusp" points (Red, Yellow, + Green, Cyan, Blue & Magenta). No markers will be displayed if + the cusps cannot be determined.<br> <br> The <span style="font-weight: bold;">-f</span> <span style="font-weight: bold;">perc</span> parameter turns on - filtering of - the raster colors. The colors from the image are clustered, and then - sorted according to popularity, and then the <span + filtering of the raster colors. The colors from the image are + clustered, and then sorted according to popularity, and then the <span style="font-weight: bold;">perc</span> most common percentage of colors are used to create the gamut surface. This may be useful in creating a source gamut mapping surface that favors the important colors within an image, and doesn't attempt to compress the color reproduction in order to reproduce the little used colors. A value of <span style="font-weight: bold;">perc</span> of 90 or 80 may be - a good place - to start. Note that the filtering is performed independently on each - raster image processed, with the final gamut being the union of all - the - filtered image gamuts.<br> + a good place to start. Note that the filtering is performed + independently on each raster image processed, with the final gamut + being the union of all the filtered image gamuts.<br> <br> The <b>-i</b> flag selects the intent transform used for a lut - based - profile. It also selects between relative and absolute colorimetric - for - non-lut base profiles. Note that anything other than colorimetric - may - not represent the - native capabilities of the device. The default intent will be - absolute - colorimetic for L*a*b* output, and CIECAM02 appearance for Jab - output.<br> + based profile. It also selects between relative and absolute + colorimetric for non-lut base profiles. Note that anything other + than colorimetric may not represent the native capabilities of the + device. The default intent will be absolute colorimetic for L*a*b* + output, and CIECAM02 appearance for Jab output.<br> <br> An ICC profile is allowed to contain more than the minimum number of elements or table needed to describe a certain transform, and may contain redundant descriptions. By default, LUT based table information will be used first if present, followed by matrix/shaper - information, and only using monochrome - information if it is all that is present. The <b>-o</b> flag, - reverses - this + information, and only using monochrome information if it is all that + is present. The <b>-o</b> flag, reverses this order. <br> <br> <span style="font-weight: bold;">-p</span>: By default the gamut - will - be created in L*a*b* colorspace. If <span style="font-weight: - bold;">-pj</span> is selected, then CIECAM02 + will be created in L*a*b* colorspace. If <span + style="font-weight: bold;">-pj</span> is selected, then CIECAM02 appearance space Jab will be used for the output, and the viewing conditions will be taken into account. Jab space is what is normally needed to be compatible with the default intents used in <a href="colprof.html">colprof</a>. <span style="font-weight: bold;"><br> </span>Note that the CIECAM02 output space selection by default uses the colorimetric transform of the profile resulting in the - appearance - of the native device, but that the perceptual or + appearance of the native device, but that the perceptual or saturation transforms may be used by selecting them using the <span style="font-weight: bold;">-i</span> parameter, which may give a different result with some profiles. This may be desirable if an - image - is to be transformed through the perceptual or saturation tables of - a - profile as part of a link with an Argyll generated output profile, - since it will then represent the apparent gamut of the image when - subject to these tables. If the absolute colorimetric intent is - chosen - using <span style="font-weight: bold;">-ia</span> in combinations - with - <span style="font-weight: bold;">-pj</span>, then Jab with - a fixed white reference is used, which emulates an absolute CIECAM02 - Jab - appearance space. <br> + image is to be transformed through the perceptual or saturation + tables of a profile as part of a link with an Argyll generated + output profile, since it will then represent the apparent gamut of + the image when subject to these tables. If the absolute colorimetric + intent is chosen using <span style="font-weight: bold;">-ia</span> + in combinations with <span style="font-weight: bold;">-pj</span>, + then Jab with a fixed white reference is used, which emulates + an absolute CIECAM02 Jab appearance space. <br> <br> The <span style="font-weight: bold;">-c</span> parameter sets the output space to CIECAM02 appearance Jab values, and also allows - choosing - a set of viewing conditions, either by choosing a typical viewing - environment, or controlling - particular viewing condition parameters. This is only functional if - an - ICC profile is provided.<br> + choosing a set of viewing conditions, either by choosing a typical + viewing environment, or controlling particular viewing condition + parameters. This is only functional if an ICC profile is provided.<br> <br> The <span style="font-weight: bold;">-O</span> parameter allows the output file name & extension to be specified independently of - the - last tiff/jpeg - filename. Note that the full filename must be specified, including - the - extension.<br> + the last tiff/jpeg filename. Note that the full filename must be + specified, including the extension.<br> <br> If the TIFF or JPEG files are in a device space (ie. RGB, CMYK - etc.), then it - is - necessary to supply an ICC profile to translate the device space - values - to a CIE space value such as L*a*b* or CIECAM02 Jab space for - creating - a gamut surface. For the ICC profile provided it is then possible to - select exactly what type of conversion is used. A TIFF or JPEGfile - with an - embedded ICC profile may be supplied as the profile argument - e.g. - to - get the gamut of a tiff file that contains an embedded profile use - something like:<br> + etc.), then it is necessary to supply an ICC profile to translate + the device space values to a CIE space value such as L*a*b* or + CIECAM02 Jab space for creating a gamut surface. For the ICC profile + provided it is then possible to select exactly what type of + conversion is used. A TIFF or JPEGfile with an embedded ICC profile + may be supplied as the profile argument - e.g. to get the gamut of a + tiff file that contains an embedded profile use something like:<br> <br> tiffgamut image.tif image.tif<br> <br> - If a TIFF file is - already in a CIE space such as CIELab or ICCLab, then it is not - necessary to select an ICC profile, although a PCS to PCS - colorspace profile may be chosen. All the TIFF and JPEG files - must be in the same colorspace.<br> + To create a gamut suitable for CIECAM02 gamut mapping space in + colprof or collink, something like<br> + <br> + tiffgamut -ir -pj -cmt image.icm image.tif<br> + <br> + where the viewing conditions "mt" should the same as the source + conditions in colprof or collink.<br> + <br> + If a TIFF file is already in a CIE space such as CIELab or ICCLab, + then it is not necessary to select an ICC profile, although a + PCS to PCS colorspace profile may be chosen. All the TIFF and JPEG + files must be in the same colorspace.<br> <br> One or more TIFF and/or JPEG files may be specified, and the gamut - is the union of - the gamuts of each file. This is useful for creating an image - specific - gamut mapping that can be applied to a set of images with consistent - results between the images. Note that the output gamut file name - will - by default be taken from the last TIFF or JPEG file specified, with - the .gam - extension added automatically. The <span style="font-weight: bold;">-O</span> - parameter will override this default.<br> + is the union of the gamuts of each file. This is useful for creating + an image specific gamut mapping that can be applied to a set of + images with consistent results between the images. Note that the + output gamut file name will by default be taken from the last TIFF + or JPEG file specified, with the .gam extension added automatically. + The <span style="font-weight: bold;">-O</span> parameter will + override this default.<br> <br> <span style="font-weight: bold;">NOTES</span><br> <br> @@ -342,12 +323,9 @@ f:x:y and black points. For the purposes of latter gamut mapping, it is assumed that the image should retain it's position within the colorspace dynamic range. For an L*a*b* image, the values value - 100,0,0 - and 0,0,0 for white and black are assumed. An image in L*a*b* should - be - adjusted be neutral to, and sit within the dynamic range of those - white - and black points.<br> + 100,0,0 and 0,0,0 for white and black are assumed. An image in + L*a*b* should be adjusted be neutral to, and sit within the dynamic + range of those white and black points.<br> <br> <br> <span style="font-weight: bold;"></span><br> diff --git a/doc/txt2ti3.html b/doc/txt2ti3.html index 744a576..5d021fc 100644 --- a/doc/txt2ti3.html +++ b/doc/txt2ti3.html @@ -1,98 +1,112 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> -<head> - <title>txt2ti3</title> - <meta http-equiv="content-type" - content="text/html; charset=ISO-8859-1"> - <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 -format. -<h3>Usage Summary</h3> -<small><span style="font-family: monospace;">txt2ti3 [-v] [-l limit] -[-d] [devfile] infile [specfile] outfile</span><br - 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> -</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> --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;"> -<i style="font-family: monospace;">infile </i><span - style="font-family: monospace;"> + <head> + <title>txt2ti3</title> + <meta http-equiv="content-type" content="text/html; + charset=ISO-8859-1"> + <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 + format. + <h3>Usage Summary</h3> + <small><span style="font-family: monospace;">txt2ti3 [-v] [-l limit] + [-d] [devfile] infile [specfile] outbase</span><br + 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> + </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> + -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;"> + <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: 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> -<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> -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> -<br> -A variety of different packaging of Gretag/Logo 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> -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> -<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> -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> -<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> -<br> -<br> -</body> +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: + 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> + <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> + 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> + <br> + A variety of different packaging of Gretag/Logo 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> + 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> + <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> + 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> + <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> + <br> + <br> + </body> </html> diff --git a/doc/xicclu.html b/doc/xicclu.html index 8377c69..cf572fe 100644 --- a/doc/xicclu.html +++ b/doc/xicclu.html @@ -1,551 +1,838 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> -<head> - <title>xicclu</title> - <meta http-equiv="content-type" - content="text/html; charset=ISO-8859-1"> - <meta name="author" content="Graeme Gill"> -</head> -<body> -<h2><b>xicc/xicclu</b> </h2> -<h3>Summary <br> -</h3> -Lookup individual color values forward or inverted though an ICC -profile table. <b>xicclu</b> is the analogue of the icclib tool <a - href="icclu.html">icclu</a>, but expands the capability to reverse -lookup the Lut tables, and displaying PCS values in CIECAM02 Jab space. -<b>xicclu</b> -can also be used to plot the device value composition down the neutral -axis, -for device profiles.<br> -<h3>Usage Summary</h3> - <small><span style="font-family: monospace;">xicclu [-</span><i - style="font-family: monospace;">options</i><span - style="font-family: monospace;">] profile</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#v">-v level</a><span - style="font-family: monospace;"> -Verbosity level 0 - 2 (default = 1)</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#g">-g</a><span - style="font-family: monospace;"> - Plot slice instead of looking colors up. (Default white to black)<br> - <a href="#Gs">-G s:L:a:b</a> Override -plot slice start with Lab or Jab co-ordinate<br> - <a href="#Ge">-G e:L:a:b</a> Override -plot slice end with Lab or Jab co-ordinate<br - style="font-family: monospace;"> -</span><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#f">-f function</a><span - style="font-family: monospace;"> f = forward, b = -backwards, g = gamut, p = preview</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> + <head> + <title>xicclu</title> + <meta http-equiv="content-type" content="text/html; + charset=ISO-8859-1"> + <meta name="author" content="Graeme Gill"> + </head> + <body> + <h2><b>xicc/xicclu</b> </h2> + <h3>Summary <br> + </h3> + Lookup individual color values forward or inverted though an ICC + profile table or CAL file. <b>xicclu</b> is the analogue of the + icclib tool <a href="icclu.html">icclu</a>, but expands the + capability to reverse lookup the Lut tables, and displaying PCS + values in CIECAM02 Jab space. <b>xicclu</b> can also be used to + plot the device value composition down the neutral axis for device + profiles, or CAL file contents.<br> + <br> + Few of the options that apply to ICC profiles apply to CAL files, + although device value options such as <b>-e</b> or <b>-E</b> will + work. To lookup inverted CAL values, use <b>-f b</b>.<br> + <h3>Usage Summary</h3> + <small><span style="font-family: monospace;">xicclu [-</span><i + style="font-family: monospace;">options</i><span + style="font-family: monospace;">] profile_or_cal</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#v">-v level</a><span + style="font-family: monospace;"> + Verbosity level 0 - 2 (default = 1)</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#g">-g</a><span + style="font-family: monospace;"> + Plot slice instead of looking colors up. (Default + white to black)<br> + <a href="#Gs">-G s:L:a:b</a> + Override plot slice start with Lab or Jab co-ordinate<br> + <a href="#Ge">-G e:L:a:b</a> + Override plot slice end with Lab or Jab co-ordinate<br + style="font-family: monospace;"> + </span><span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#f">-f function</a><span + style="font-family: monospace;"> f = forward, + b = backwards, g = gamut, p = preview</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> if -= inverted forward, ib = inverted backwards</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#i">-i intent</a><span - style="font-family: monospace;"> a = -absolute, r = relative colorimetric,</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> -</span></small><small><span style="font-family: monospace;"> p = -perceptual, </span></small><small><span style="font-family: monospace;">s = -saturation</span><span style="font-family: monospace;"></span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#o">-o order</a><span - style="font-family: monospace;"> n -= normal (priority: lut > matrix > monochrome)</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> + + + + + + inverted forward, ib = inverted backwards</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#i">-i intent</a><span + style="font-family: monospace;"> a + = absolute, r = relative colorimetric,</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> + + + + + + </span></small><small><span style="font-family: monospace;"> p = + perceptual, </span></small><small><span style="font-family: + monospace;">s = saturation</span><span style="font-family: + monospace;"></span><br style="font-family: monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#o">-o order</a><span + style="font-family: monospace;"> + + + + + + n = normal (priority: lut > matrix > monochrome)</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> r -= reverse (priority: monochrome > matrix > -lut)</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#p">-p oride</a><span - style="font-family: monospace;"> x -= XYZ_PCS, X = XYZ * 100, l = Lab_PCS, L = LCh, y = Yxy,<br> - j = CIECAM02 -Appearance Jab, J = CIECAM02 Appearance JCh<br> -</span><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#s">-s scale</a><span - style="font-family: monospace;"> -Scale device range 0.0 - scale rather than 0.0 - 1.0</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#k">-k [zhxrlv]</a><span - style="font-family: monospace;"> Black generation: z -= zero K,</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> += + + + + + + reverse (priority: monochrome > matrix > lut)</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#p">-p oride</a><span + style="font-family: monospace;"> + + + + + + x = XYZ_PCS, X = XYZ * 100, l = Lab_PCS, L = LCh, y = Yxy,<br> + j = + CIECAM02 Appearance Jab, J = CIECAM02 Appearance JCh<br> + </span><span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#s">-s scale</a><span + style="font-family: monospace;"> +Scale + + + + + + device range 0.0 - scale rather than 0.0 - 1.0<br> + </span></small><br> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"><a href="#e">-e flag</a> + + + Video encode device input as:<br> + <a href="#E">-E flag</a> + + + Video decode device output 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" + lev</span></small></span></small><small><span + style="font-family: monospace;"><br style="font-family: + monospace;"> + </span> <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#k">-k [zhxrlv]</a><span + style="font-family: monospace;"> Black + generation: z = zero K,</span><br style="font-family: + monospace;"> + <span style="font-family: monospace;"> -h = 0.5 K, x = max K, r = ramp K (def.)</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> +h + + + + + + = 0.5 K, x = max K, r = ramp K (def.)</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> -l = extra PCS input is portion of K locus</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> +l + + + + + + = extra PCS input is portion of K locus</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> -v = extra PCS input is K target value</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#kp">-k p stle stpo enpo enle -shape</a><br style="font-family: monospace;"> -<span style="font-family: monospace;"> +v + + + + + + = extra PCS input is K target value</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#kp">-k p stle stpo enpo + enle shape</a><br style="font-family: monospace;"> + <span style="font-family: monospace;"> -stle: K level at White 0.0 - 1.0</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> +stle: + + + + + + K level at White 0.0 - 1.0</span><br style="font-family: + monospace;"> + <span style="font-family: monospace;"> -stpo: start point of transition Wh 0.0 - Bk 1.0</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> +stpo: + + + + + + start point of transition Wh 0.0 - Bk 1.0</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> -enpo: End point of transition Wh 0.0 - Bk 1.0</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> +enpo: + + + + + + End point of transition Wh 0.0 - Bk 1.0</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> -enle: K level at Black 0.0 - 1.0</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> +enle: + + + + + + K level at Black 0.0 - 1.0</span><br style="font-family: + monospace;"> + <span style="font-family: monospace;"> -shape: 1.0 = straight, 0.0-1.0 concave, 1.0-2.0 -convex</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#kq">-k q stle0 stpo0 enpo0 -enle0 shape0 stle2 stpo2 -enpo2 enle2 shape2</a><br style="font-family: monospace;"> -<span style="font-family: monospace;"> +shape: + + + + + + 1.0 = straight, 0.0-1.0 concave, 1.0-2.0 convex</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#kq">-k q stle0 stpo0 + enpo0 enle0 shape0 stle2 stpo2 enpo2 enle2 shape2</a><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> Transfer -extra PCS input to dual curve limits</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#K">-K parameters</a><span - style="font-family: monospace;"> Same as -k, but target is K -locus rather than K value itself</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#l">-l tlimit</a><span - style="font-family: monospace;"> set -total ink limit, 0 - 400% (estimate by default)</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#L">-L klimit</a><span - style="font-family: monospace;"> set -black ink limit, 0 - 100% (estimate by default)</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#a">-a</a><span - style="font-family: monospace;"> +extra + + + + + + PCS input to dual curve limits</span><br style="font-family: + monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#K">-K parameters</a><span + style="font-family: monospace;"> Same as -k, but target is + K locus rather than K value itself</span><br style="font-family: + monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#l">-l tlimit</a><span + style="font-family: monospace;"> + set total ink limit, 0 - 400% (estimate by default)</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#L">-L klimit</a><span + style="font-family: monospace;"> + set black ink limit, 0 - 100% (estimate by default)</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#a">-a</a><span + style="font-family: monospace;"> show -actual target values if clipped<br> - <a href="#b">-b</a> +actual + + + + + + target values if clipped<br> + <a href="#b">-b</a> use -CAM Jab for clipping<br style="font-family: monospace;"> -</span><span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#m">-m</a><span - style="font-family: monospace;"> - -merge output processing into clut</span><span - style="font-family: monospace;"></span><span - style="font-weight: bold; font-family: monospace;"></span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> </span><a - style="font-family: monospace;" href="#c">-c viewcond</a><span - style="font-family: monospace;"> set viewing -conditions -for CIECAM02,</span><br style="font-family: monospace;"> - </small><small><span style="font-family: monospace;"> +CAM + + + + + + Jab for clipping<br style="font-family: monospace;"> + </span><span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#m">-m</a><span + style="font-family: monospace;"> + + merge output processing into clut</span><span + style="font-family: monospace;"></span><span style="font-weight: + bold; font-family: monospace;"></span><br style="font-family: + monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#c">-c viewcond</a><span + style="font-family: monospace;"> set viewing + conditions for CIECAM02,</span><br style="font-family: + monospace;"> + </small><small><span style="font-family: monospace;"> -either an enumerated choice, or a parameter:value change</span><span - style="font-family: monospace;"></span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"></span></small><small><span - style="font-family: monospace;"> - pp - Practical Reflection Print -(ISO-3664 P2)</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> +either + + + + + + an enumerated choice, or a parameter:value change</span><span + style="font-family: monospace;"></span><br style="font-family: + monospace;"> + <span style="font-family: monospace;"></span></small><small><span + style="font-family: monospace;"> + pp - Practical Reflection Print (ISO-3664 P2)</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> -pe - Print evaluation environment (CIE 116-1995)<br> -</span></small><small><span style="font-family: monospace;"> +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;"> -<span style="font-family: monospace;"> - mt - Monitor in typical work environment</span><br - style="font-family: monospace;"> -<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;"> + <span style="font-family: monospace;"> + mt - Monitor in typical work environment</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> + - mb - Monitor in bright work environment</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> - md - Monitor in darkened work -environment</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> - jm - Projector in dim environment</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> - jd - Projector in dark environment</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> - pcd - Photo CD - original scene -outdoors</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> - ob - Original scene - Bright Outdoors</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> - cx - Cut Sheet Transparencies on a viewing box</span></small><small><span - style="font-family: monospace;"></span><span - style="font-family: monospace;"></span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> + + + + + + mb - Monitor in bright work environment</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> + md - Monitor in darkened work + environment</span><br style="font-family: monospace;"> + <span style="font-family: monospace;"> + jm - Projector in dim environment</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> + jd - Projector in dark environment</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> + pcd - Photo CD - original scene outdoors</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> + ob - Original scene - Bright Outdoors</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> + cx - Cut Sheet Transparencies on a + viewing box</span></small><small><span style="font-family: + monospace;"></span><span style="font-family: monospace;"></span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> s:surround -n = auto, a = average, m = dim, d = dark,</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> +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;"> + + + + + + 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, Abs: D50)</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> +Adapted + + + + + + white point as XYZ (default media white, Abs: D50)</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;"> +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)</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> +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)</span><br style="font-family: + monospace;"> + <span style="font-family: monospace;"></span></small><small><span + style="font-family: monospace;"><small><span style="font-family: + monospace;"> f:flare Flare -light % of image luminance (default 1)</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> - -f:X:Y:Z Flare color -as XYZ (default media white, Abs: D50)</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> -f:x:y -Flare color as x, y</span><br style="font-family: monospace;"> -<br style="font-family: monospace;"> -<span style="font-family: monospace;"> -</span><a style="font-family: monospace;" href="#p1"><i>inoutfile</i></a><span - style="font-family: monospace;"> The input -ICC profile</span><br style="font-family: monospace;"> -<br style="font-family: monospace;"> -<span style="font-family: monospace;"> The colors to -be translated should be fed into -standard in,</span><br style="font-family: monospace;"> -<span style="font-family: monospace;"> one input -color per line, white space separated.</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> A line -starting with a # will be ignored.</span><br - style="font-family: monospace;"> -<span style="font-family: monospace;"> A line not -starting with a number will terminate the -program.</span></small> -<br> -<h3>Flags and Parameters</h3> -<a name="v"></a> The <b>-v</b> parameter sets the level of verbosity. -Default is level 1, which repeats each input value, the colorspaces of -input and output, the type of conversion algorithm used, and if the -result was clipped. Level 2 adds prints extra information about the -profile before doing the conversions. Level 0 turns off all verbosity, -just outputting the results of each conversion. Use the latter to -capture batch output ready for further processing.<br> -<br> -<a name="g"></a>The <b>-g</b> flag causes a plot of the device values -along a slice through the Lab or Jab colorspace, rather than allowing -the interactive looking up of color -values. By default this will be the neutral axis -from the white point to the black point, but the start and end can be -overridden using the <span style="font-weight: bold;">-G</span> -parameters. -This is useful in determining the existing black generation in a CMYK -profile, -or exploring the behavior of various black generation options using -the -<b>-k</b> parameters. The profile must be a device profile, and the PCS -must -be either Lab or Jab. The default plot is up the neutral axis is from -the white to -the black point (scale 0 to 100%), and shows the percentage of each -device colorant. To examine a profiles B2A table black -generation, -use the flag <b>-fb</b> to select the B2A table, or to invert the A2B -table, -and be able to explore black generation behavior, use the <b>-fif</b> -flag. -The appropriate intent can be selected with the <b>-i</b> flag, - as -can other flags appropriate to the function selected. See <a - href="#xg">example</a>.<br> -<br> -<a name="Gs"></a>The <span style="font-weight: bold;">-G </span><small><span - style="font-family: monospace;"><span style="font-weight: bold;">s:L:a:b</span></span></small> -parameter overrides the plot slice start point of white, with some -other point specified in Lab or Jab Profile Connection Space. The -parameter must be a single string that combines<span - style="font-weight: bold;"> s:</span> with the three numbers separated -by the '<span style="font-weight: bold;">:'</span> character (no -spaces).<br> -<br> -<a name="Ge"></a>The <span style="font-weight: bold;">-G </span><small><span - style="font-family: monospace;"><span style="font-weight: bold;">e:L:a:b</span></span></small> -parameter overrides the plot slice end point of black, with some -other point specified in Lab or Jab Profile Connection Space. The -parameter must be a single string that combines<span - style="font-weight: bold;"> s:</span> with the three numbers separated -by the '<span style="font-weight: bold;">:'</span> character (no -spaces).<br> -<br> -<a name="f"></a> The <b>-f</b> flag selects which type of table or -conversion is to be used. In addition to the usual four tables that can -be accessed in a fully populated Lut based profile, two additional -options are available in <b>xicclu</b>. One is to invert the forward -table, and the other is to invert the backward table. For non Lut based -profiles, -fif is equivalent to -fb, and -fib is equivalent to -ff. -Note that the -fib combination may not be fully supported.<br> -<br> -<a name="i"></a> The <b>-i</b> flag selects the intent table used for -a lut based -profile. It also selects between relative and absolute colorimetric for -non-lut base profiles.<br> -<br> -<a name="o"></a> A profile is allowed to contain more than the minimum -number of elements or table needed to describe a certain transform, and -may contain redundant descriptions. By default, Lut based table -information will be used first if present, followed by matrix/shaper -information, and only using monochrome information if it is all that is -present. The <b>-o</b> flag, reverses this order. <br> -<br> -<a name="p"></a> Normally the native PCS (Profile Connection Space) of -a device or abstract profile is used, but the <b>-p</b> flag allows -this to be overridden: <span style="font-weight: bold;">-px</span>: -XYZ (scaled to 1.0), <span style="font-weight: bold;">-pX</span>: XYZ -scaled to 100, <span style="font-weight: bold;">-pl</span>: L*a*b*, <span - style="font-weight: bold;">-pL</span>: LCh, <span - style="font-weight: bold;">-py</span>: Yxy space, <span - style="font-weight: bold;">-pj</span>: CIECAM02 appearance space Jab, -or <span style="font-weight: bold;">-pJ</span>: CIECAM02 appearance -space JCh.<span style="font-weight: bold;"><br> -</span>Note that the CIECAM02 output space selection by default uses -the colorimetric table of the profile, but that the perceptual or -saturation tables may be used by selecting them using the <span - style="font-weight: bold;">-i</span> parameter. If the absolute -colorimetric intent is chosen using <span style="font-weight: bold;">-ia</span> -in combinations with <span style="font-weight: bold;">-pj</span>, -then Jab with -a fixed white reference is used, which emulates an absolute CIECAM02 -Jab -appearance space. <br> -<br> -<a name="s"></a> Usually device values are processed and displayed -using a normalized value range between 0.0 and 1.0 Sometimes other -systems scale them to some other range (such as 100 or 255) due to an -underlying binary representation. The <span style="font-weight: bold;">-s</span> -flag lets you input and display such data in its normal range. For -instance, if your device values have a range between 0 and 255, use <span - style="font-weight: bold;">-s 255.</span><br> -<br> -<a name="k"></a> When inverting a CMYK profile, (ie. using the -fif -flag), an input PCS value can have many possible CMYK solutions. To be -able to return a unique solution, a black level (or black inking rule) -should be chosen. The choice here reflect similar choices in black -generation available in other tools (eg. <a href="colprof.html">colprof</a>, -<a href="collink.html"> collink</a>), with the addition of two extra -options.<br> -<br> - Possible arguments to the <b>-k</b> option are:<br> -<br> -<b> -kz</b> selects minimum black (0.0)<br> -<b> -kh</b> selects a black value of 0.5<br> -<b> -kx</b> selects the maximum possible black (1.0)<br> -<b> -kr</b> selects a linear black ramp, starting at minimum black for -highlight, and maximum black for shadow (equivalent to -kp 0 0 1 1 1). -This is the default.<br> -<b> -kl</b> uses an extra (fourth) value entered after the input PCS -value, to select a black locus target between 0.0 and 1.0.<br> -<b> -kv</b> uses an extra (fourth) value entered after the input PCS -value, to select a black value target value between 0.0 and 1.0.<br> -<br> -<b><a name="kp"></a>-k p stle stpo enpo enle shape</b> allows an -arbitrary black value ramp to be defined, consisting of a starting -value (stle) for highlights, a breakpoint L value (stpo) where it -starts to transition to the shadow level, an end breakpoint L (enpo) -where it flattens out again, and the finishing black level (enle) for -the shadows. There is also a curve parameter, that modifies the -transition from stle to enle to either be concave (ie. the -transition starts gradually and and finished more abruptly) using -values 0.0-1.0, with 0.0 being most concave, or convex (the transition -starts more abruptly but finishes gradually), using values 1.0-2.0, -with 2.0 being the most convex.<br> -<br> -Typical black value generation curve with parameters something -like: -kp 0 .05 1 .9 .8<br> -<br> -<tt> 1.0 K | - enpo<br> - +light + + + + + + % of image luminance (default 1)<br> + </span></small> + + + + + g:glare Glare light % of ambient + (default 1)</span><br style="font-family: monospace;"> + <span style="font-family: monospace;"> + g:X:Y:Z Glare color + as XYZ (default media white, Abs: D50)</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> + + + + + g:x:y FGare color as + x, y</span><br style="font-family: monospace;"> + <br style="font-family: monospace;"> + <span style="font-family: monospace;"> </span><a + style="font-family: monospace;" href="#p1"><i>inoutfile</i></a><span + style="font-family: monospace;"> The + input ICC profile or CAL file.</span><br style="font-family: + monospace;"> + <br style="font-family: monospace;"> + <span style="font-family: monospace;"> The + colors to be translated should be fed into standard in,</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> one input + color per line, white space separated.</span><br + style="font-family: monospace;"> + <span style="font-family: monospace;"> A line + starting with a # will be ignored.</span><br style="font-family: + monospace;"> + <span style="font-family: monospace;"> A line + not starting with a number will terminate the program.</span></small> + <br> + <h3>Flags and Parameters</h3> + <a name="v"></a> The <b>-v</b> parameter sets the level of + verbosity. Default is level 1, which repeats each input value, the + colorspaces of input and output, the type of conversion algorithm + used, and if the result was clipped. Level 2 adds prints extra + information about the profile before doing the conversions. Level 0 + turns off all verbosity, just outputting the results of each + conversion. Use the latter to capture batch output ready for further + processing.<br> + <br> + <a name="g"></a>The <b>-g</b> flag causes a plot of the device + values along a slice through the Lab or Jab colorspace, rather than + allowing the interactive looking up of color values. By default this + will be the neutral axis from the white point to the black point, + but the start and end can be overridden using the <span + style="font-weight: bold;">-G</span> parameters. This is useful in + determining the existing black generation in a CMYK profile, or + exploring the behavior of various black generation options using the + <b>-k</b> parameters. The profile must be a device profile, and the + PCS must be either Lab or Jab. The default plot is up the neutral + axis is from the white to the black point (scale 0 to 100%), and + shows the percentage of each device colorant. To examine a profiles + B2A table black generation, use the flag <b>-fb</b> to select the + B2A table, or to invert the A2B table, and be able to explore black + generation behavior, use the <b>-fif</b> flag. The appropriate + intent can be selected with the <b>-i</b> flag, as can other + flags appropriate to the function selected. See <a href="#xg">example</a>.<br> + <br> + If a CAL file is used, then <b>-g</b> will simply plot the each + channels calibration curve. It will also plot the invers curve for <b>-f + + b</b>.<br> + <br> + <a name="Gs"></a>The <span style="font-weight: bold;">-G </span><small><span + style="font-family: monospace;"><span style="font-weight: bold;">s:L:a:b</span></span></small> + parameter overrides the plot slice start point of white, with some + other point specified in Lab or Jab Profile Connection Space. The + parameter must be a single string that combines<span + style="font-weight: bold;"> s:</span> with the three numbers + separated by the '<span style="font-weight: bold;">:'</span> + character (no spaces).<br> + <br> + <a name="Ge"></a>The <span style="font-weight: bold;">-G </span><small><span + style="font-family: monospace;"><span style="font-weight: bold;">e:L:a:b</span></span></small> + parameter overrides the plot slice end point of black, with some + other point specified in Lab or Jab Profile Connection Space. The + parameter must be a single string that combines<span + style="font-weight: bold;"> s:</span> with the three numbers + separated by the '<span style="font-weight: bold;">:'</span> + character (no spaces).<br> + <br> + <a name="f"></a> The <b>-f</b> flag selects which type of table or + conversion is to be used. In addition to the usual four tables that + can be accessed in a fully populated Lut based profile, two + additional options are available in <b>xicclu</b>. One is to invert + the forward table, and the other is to invert the backward table. + For non Lut based profiles, -fif is equivalent to -fb, and -fib is + equivalent to -ff. Note that the -fib combination may not be fully + supported.<br> + <br> + <a name="i"></a> The <b>-i</b> flag selects the intent table used + for a lut based profile. It also selects between relative and + absolute colorimetric for non-lut base profiles.<br> + <br> + <a name="o"></a> A profile is allowed to contain more than the + minimum number of elements or table needed to describe a certain + transform, and may contain redundant descriptions. By default, + Lut based table information will be used first if present, followed + by matrix/shaper information, and only using monochrome information + if it is all that is present. The <b>-o</b> flag, reverses this + order. <br> + <br> + <a name="p"></a> Normally the native PCS (Profile Connection Space) + of a device or abstract profile is used, but the <b>-p</b> flag + allows this to be overridden: <span style="font-weight: bold;">-px</span>: + XYZ (scaled to 1.0), <span style="font-weight: bold;">-pX</span>: + XYZ scaled to 100, <span style="font-weight: bold;">-pl</span>: + L*a*b*, <span style="font-weight: bold;">-pL</span>: LCh, <span + style="font-weight: bold;">-py</span>: Yxy space, <span + style="font-weight: bold;">-pj</span>: CIECAM02 appearance space + Jab, or <span style="font-weight: bold;">-pJ</span>: CIECAM02 + appearance space JCh.<span style="font-weight: bold;"><br> + </span>Note that the CIECAM02 output space selection by default uses + the colorimetric table of the profile, but that the perceptual or + saturation tables may be used by selecting them using the <span + style="font-weight: bold;">-i</span> parameter. If the absolute + colorimetric intent is chosen using <span style="font-weight: + bold;">-ia</span> in combinations with <span style="font-weight: + bold;">-pj</span>, then Jab with a fixed white reference is + used, which emulates an absolute CIECAM02 Jab appearance space. <br> + <br> + <a name="s"></a> Usually device values are processed and displayed + using a normalized value range between 0.0 and 1.0 Sometimes other + systems scale them to some other range (such as 100 or 255) due to + an underlying binary representation. The <span style="font-weight: + bold;">-s</span> flag lets you input and display such data in its + normal range. For instance, if your device values have a range + between 0 and 255, use <span style="font-weight: bold;">-s 255.</span><br> + <br> + <a name="e"></a>The <b>-e</b> <i>flag</i> applies a Video encoding + to the input. See <a + href="collink.html#E"><b>-E</b></a> for + the list of encodings.<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> + <small><span style="font-family: monospace;"><small><span + style="font-family: monospace;"> + n + + + + + normal RGB 0..1 full range levels (default)<br> + + t + + + + + RGB (16-235)/255 "TV" 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> + </span></small></span></small><br> + <a name="k"></a> When inverting a CMYK profile, (ie. using the -fif + flag), an input PCS value can have many possible CMYK solutions. To + be able to return a unique solution, a black level (or black inking + rule) should be chosen. The choice here reflect similar choices in + black generation available in other tools (eg. <a + href="colprof.html">colprof</a>, <a href="collink.html"> collink</a>), + + + + + with the addition of two extra options.<br> + <br> + Possible arguments to the <b>-k</b> option are:<br> + <br> + <b> -kz</b> selects minimum black (0.0)<br> + <b> -kh</b> selects a black value of 0.5<br> + <b> -kx</b> selects the maximum possible black (1.0)<br> + <b> -kr</b> selects a linear black ramp, starting at minimum black + for highlight, and maximum black for shadow (equivalent to -kp 0 0 1 + 1 1). This is the default.<br> + <b> -kl</b> uses an extra (fourth) value entered after the input PCS + value, to select a black locus target between 0.0 and 1.0.<br> + <b> -kv</b> uses an extra (fourth) value entered after the input PCS + value, to select a black value target value between 0.0 and 1.0.<br> + <br> + <b><a name="kp"></a>-k p stle stpo enpo enle shape</b> allows + an arbitrary black value ramp to be defined, consisting of a + starting value (stle) for highlights, a breakpoint L value (stpo) + where it starts to transition to the shadow level, an end breakpoint + L (enpo) where it flattens out again, and the finishing black level + (enle) for the shadows. There is also a curve parameter, that + modifies the transition from stle to enle to either be concave + (ie. the transition starts gradually and and finished more + abruptly) using values 0.0-1.0, with 0.0 being most concave, or + convex (the transition starts more abruptly but finishes gradually), + using values 1.0-2.0, with 2.0 being the most convex.<br> + <br> + Typical black value generation curve with parameters something like: + -kp 0 .05 1 .9 .8<br> + <br> + <tt> 1.0 K | + enpo<br> + | - _______ -enle<br> - + + + + + + + _______ enle<br> + | - /<br> - + + + + + + + /<br> + | - /<br> - + + + + + + + /<br> + | - /<br> - + + + + + + + /<br> + | - /<br> - stle -| ------/<br> - - +-------------------<br> - 0.0 K -0.0 stpo 1.0<br> - + + + + + + + /<br> + + stle | ------/<br> + + +-------------------<br> + 0.0 K + 0.0 + stpo 1.0<br> + White -Black<br> -</tt><br> -<b><a name="kq"></a>-k q stle0 stpo0 enpo0 enle0 shape0 stle2 stpo2 -enpo2 enle2 shape2</b> is a combination of the <b>-kv</b> and <b>-kp</b> -functionality, with the black being preserved in CMYK to CMYK linking, -with the output black constrained to be between the first and second -set of curve parameters.<br> -<br> -<a name="K"></a> <span style="font-weight: bold;">-K parameters.</span> -Any of the <span style="font-weight: bold;">-k</span> options above -can use the <span style="font-weight: bold;">-K</span> version, in -which rather than a black value target being defined by the inking -rule, a black <span style="text-decoration: underline;">locus</span> -target is defined. For each lookup, the minimum possible black level -and the maximum possible black level is determined, the former -corresponding to a locus target of 0, and the latter corresponding to a -locus target of 1. For instance, at -the -white point, no black will be used in the output, even if the black -locus specifies a maximum (since the maximum amount of black that -can be used to print white is actually zero). Similarly, at the black -point, black may well be used, even if the black locus specifies -zero black (since a certain amount of black is needed to achieve the -desired density of color). <br> -<tt> </tt><span style="text-decoration: underline;"></span><br> - The <b>-g</b> flag can be used together with the <b>-fif</b> -flag, to plot -out the resulting black channel behaviour for various <b>-k</b> -or <span style="font-weight: bold;">-K </span>parameter -values.<br> -<br> -<b><a name="l"></a>-l</b> <i>tlimit</i> Sets the -total ink limit (TAC, Total Area Coverage) for the CMYK inverse forward -lookup, as a total percentage from 0% to 400%. If none is provided, it -will be estimated from the profile relcolor B2A table. The ink limit -will be in final calibrated device values if the profile includes -calibration information.<br> -<br> -<b><a name="L"></a>-L</b> <i>klimit</i> Sets the black -ink limit for the CMYK inverse forward lookup, as a total percentage -from 0% to 100%. If none is provided, it will be estimated from the -profile relcolor B2A table. The ink limit -will be in final calibrated device values if the profile includes -calibration information.<br> -<br> -<a name="a"></a> If the <b>-a</b> flag is used for inverse forward -lookups, then if -the target PCS value cannot be reproduced by the device (ie. it clips), -then the achievable, clipped PCS value is displayed.<br> -<br> -<a name="b"></a> If the <b>-b</b> flag is used for inverse forward -lookups, then out of gamut clipping will be performed in the CIECAM02 -Jab appearance colorspace, rather than L*a*b* colorspace.<br> -<br> -<a name="m"></a> The <b>-m</b> flag turns on an internal processing -option, in which the per device curve lookup table processing is merged -into the main multi-dimensional interpolation lut lookup.<br> -<br> -<a name="c"></a>Whenever PCS values are to be specified or displayed in -Jab/CIECAM02 -colorspace, a set of viewing conditions will be used to determine the -details of the conversion. The <b>-c</b> parameter allows the -specification of the viewing conditions. Viewing conditions can be -specified in two basic ways. One -is to select from the list of "pre canned", enumerated viewing -conditions, choosing one that is closest to the conditions that are -appropriate for the media type and situation. Alternatively, the -viewing conditions parameters can be specified in detail individually. -If both methods are used, them the chosen enumerated condition will be -used as a base, and its parameters will then be individually overridden.<br> -<br> -<a name="p1"></a> The final parameter is the name of the <a - href="File_Formats.html#ICC">ICC</a> profile to be used. On the -MSWindows platform a .icm extension is generally used, and on Apple or -Unix/Linux platforms a .icc extension is often used.<br> -<h3>Usage and Discussion</h3> -Typical usage for an output profile might be:<br> -<br> - xicclu -ff -ip profile.icm<br> -<br> -Normally the program is interactive, allowing the user to type in input -color -values, each number separated by a space, and the resulting output -color -being looked up and displayed after pressing return. To batch process -a -group of color values, prepare a text file containing each input value -on -a -separate line, and use the input indirection facilities of your command -line -shell to redirect this input file into the standard input of xicclu. -The -output can be captured to a file by redirecting standard output to a -file. -In most shells this would be done something like this:<br> -<br> - xicclu -ff -ip profile.icm < inputvalues.txt > -outputvalues.txt<br> -<br> -<a name="xg"></a>When plotting the neutral axis behavior, plotting the -existing B2A table -behavior would typically be done something like this:<br> -<br> - xicclu -g -fb profile.icm<br> -<br> -Exploring possible black generation and ink limiting behavior might be -done -like this:<br> -<br> - xicclu -g -fif -kp 0 .1 .9 1 .5 -l230 -L95 -profile.icm<br> -<br> -<br> -<br> -<br> -<br> -<br> -<br> -</body> + + + + + + Black<br> + </tt><br> + <b><a name="kq"></a>-k q stle0 stpo0 enpo0 enle0 shape0 stle2 stpo2 + enpo2 enle2 shape2</b> is a combination of the <b>-kv</b> and <b>-kp</b> + functionality, with the black being preserved in CMYK to CMYK + linking, with the output black constrained to be between the first + and second set of curve parameters.<br> + <br> + <a name="K"></a> <span style="font-weight: bold;">-K parameters.</span> + Any of the <span style="font-weight: bold;">-k</span> options above + can use the <span style="font-weight: bold;">-K</span> version, in + which rather than a black value target being defined by the inking + rule, a black <span style="text-decoration: underline;">locus</span> + target is defined. For each lookup, the minimum possible black level + and the maximum possible black level is determined, the former + corresponding to a locus target of 0, and the latter corresponding + to a locus target of 1. For instance, at the white point, no black + will be used in the output, even if the black locus specifies a + maximum (since the maximum amount of black that can be used to print + white is actually zero). Similarly, at the black point, black may + well be used, even if the black locus specifies zero black (since a + certain amount of black is needed to achieve the desired density of + color). <br> + <tt> </tt><span style="text-decoration: underline;"></span><br> + The <b>-g</b> flag can be used together with the <b>-fif</b> + flag, to plot out the resulting black channel behaviour for various + <b>-k</b> or <span style="font-weight: bold;">-K </span>parameter + values.<br> + <br> + <b><a name="l"></a>-l</b> <i>tlimit</i> Sets the + total ink limit (TAC, Total Area Coverage) for the CMYK inverse + forward lookup, as a total percentage from 0% to 400%. If none is + provided, it will be estimated from the profile relcolor B2A table. + The ink limit will be in final calibrated device values if the + profile includes calibration information.<br> + <br> + <b><a name="L"></a>-L</b> <i>klimit</i> Sets the black + ink limit for the CMYK inverse forward lookup, as a total percentage + from 0% to 100%. If none is provided, it will be estimated from the + profile relcolor B2A table. The ink limit will be in final + calibrated device values if the profile includes calibration + information.<br> + <br> + <a name="a"></a> If the <b>-a</b> flag is used for inverse forward + lookups, then if the target PCS value cannot be reproduced by the + device (ie. it clips), then the achievable, clipped PCS value is + displayed.<br> + <br> + <a name="b"></a> If the <b>-b</b> flag is used for inverse forward + lookups, then out of gamut clipping will be performed in the + CIECAM02 Jab appearance colorspace, rather than L*a*b* colorspace.<br> + <br> + <a name="m"></a> The <b>-m</b> flag turns on an internal processing + option, in which the per device curve lookup table processing is + merged into the main multi-dimensional interpolation lut lookup.<br> + <br> + <a name="c"></a>Whenever PCS values are to be specified or displayed + in Jab/CIECAM02 colorspace, a set of viewing conditions will be used + to determine the details of the conversion. The <b>-c</b> parameter + allows the specification of the viewing conditions. Viewing + conditions can be specified in two basic ways. One is to select from + the list of "pre canned", enumerated viewing conditions, choosing + one that is closest to the conditions that are appropriate for the + media type and situation. Alternatively, the viewing conditions + parameters can be specified in detail individually. If both methods + are used, them the chosen enumerated condition will be used as a + base, and its parameters will then be individually overridden.<br> + <br> + <a name="p1"></a> The final parameter is the name of the <a + href="File_Formats.html#ICC">ICC</a> profile to be used. On the + MSWindows platform a .icm extension is generally used, and on Apple + or Unix/Linux platforms a .icc extension is often used.<br> + <h3>Usage and Discussion</h3> + Typical usage for an output profile might be:<br> + <br> + xicclu -ff -ip profile.icm<br> + <br> + Normally the program is interactive, allowing the user to type in + input color values, each number separated by a space, and the + resulting output color being looked up and displayed after pressing + return. To batch process a group of color values, prepare a text + file containing each input value on a separate line, and use the + input indirection facilities of your command line shell to redirect + this input file into the standard input of xicclu. The output can be + captured to a file by redirecting standard output to a file. In most + shells this would be done something like this:<br> + <br> + xicclu -ff -ip profile.icm < inputvalues.txt + > outputvalues.txt<br> + <br> + <a name="xg"></a>When plotting the neutral axis behavior, plotting + the existing B2A table behavior would typically be done something + like this:<br> + <br> + xicclu -g -fb profile.icm<br> + <br> + Exploring possible black generation and ink limiting behavior might + be done like this:<br> + <br> + xicclu -g -fif -kp 0 .1 .9 1 .5 -l230 -L95 + profile.icm<br> + <br> + <br> + <br> + <br> + <br> + <br> + <br> + </body> </html> |
