There is now support for most of the - the Eye-One Pro Rev E (aka Eye-One Pro 2) instrument features, but - a Rev E can be operated in legacy mode if the environment variable +
ArgyllCMS supports most of the the + Eye-One Pro Rev E (aka Eye-One Pro 2) instrument features, but a + Rev E can be operated in legacy mode if the environment variable ARGYLL_DISABLE_I1PRO2_DRIVER is set (ie. set it to "yes").
+

-
+ ARGYLL_XRGA
+
If the ARGYLL_XRGA + environment variable is set to:
+
+     XRGA, then all Getag-MacBeth/X-Rite + reflective measurements will be converted to XRGA.
+     XRDI, then all Getag-MacBeth/X-Rite + reflective measurements will be converted to XRDI.
+     GMDI, then all Getag-MacBeth/X-Rite + reflective measurements will be converted to GMDI.
+
+ If not set (or set to some other string), then the native + calibration will be used. Note that the values must be upper case.
+
XDG_CACHE_HOME

@@ -257,6 +465,14 @@ Base + + + + + + + + Directory Specification, and uses the XDG_CACHE_HOME environment variable to place per instrument calibration information, and diff --git a/doc/FWA.html b/doc/FWA.html index c6b1f4b..e83a64f 100644 --- a/doc/FWA.html +++ b/doc/FWA.html @@ -225,9 +225,10 @@ instruments provide an illuminant measurement capability over the visible spectrum, for FWA compensation it is desirable to know the Ultra Violet (UV) component of the illuminant. Few color instruments - are capable of reading to such short wavelengths though. Argyll - provides an indirect way of estimating the UV component of an - illuminant using its illumread + are capable of reading to such short wavelengths though (the JETI specbos 1211 is an + exception). Argyll provides an indirect way of estimating the UV + component of an illuminant using its illumread utility. Using illumread in combination with FWA compensation is the recommended approach to modelling real world appearance of paper containing FWA.
diff --git a/doc/File_Formats.html b/doc/File_Formats.html index ae59dd2..aeddc6d 100644 --- a/doc/File_Formats.html +++ b/doc/File_Formats.html @@ -200,7 +200,7 @@ To check if your browser supports X3DOM, try this test page.
For more information about ArgyllCMS use of it, see 3D Viewing Format.
+ href="3dformat.html">3D Viewing Format.

diff --git a/doc/Installing_Linux.html b/doc/Installing_Linux.html index a26d64c..87d7fba 100644 --- a/doc/Installing_Linux.html +++ b/doc/Installing_Linux.html @@ -51,6 +51,8 @@ + + the /etc/rc.local startup script. You may also have to run xset @@ -63,6 +65,8 @@ + + b 100 1000 100 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.
@@ -181,17 +185,16 @@ /etc/udev/rules.d/55-Argyll.rules file, but for older systems you probably need to disable libmtp (look in the udev configuration).

- The JETI specbos 1211 and 1201, and the Klien - - - - - K10A makes use of the JETI specbos 1211, 1201, + 1511, 1501 and the Klien K10A makes use of the FTDI Virtual COM Port Drivers (VCP), that should come with any recent version - of Linux. You may have to add yourself to the dialout group - to be able to open the instrument.
+ of Linux. Older versions of Linux may not support the FTDI FT231XS + chip that the JETI specbos 1511, 1501 use. You may + have to add yourself to the + tty, uucp + or dialout group to have permission to open the + instrument.

@@ -255,6 +258,8 @@ + + (as appropriate) with owner root, group root, permissions 644.

@@ -279,6 +284,8 @@ + + /sbin/udevcontrol reload_rules or /sbin/udevstart or reboot to get the new file noticed.
@@ -347,6 +354,8 @@ instruments + + access using hotplug:
Under much older versions of Linux, @@ -395,7 +404,8 @@ instruments If this doesn't work you will have to run "id yourusername" to list the current suplemental
groups, and add colord using just "usermod -G - group1,group2,... yourusername")
+ group1,group2,... yourusername"
+ Another option may be to use gpasswd -a $USER colord))

You may find that the colord group doesn't exist on your system, and if so you will need to @@ -403,10 +413,10 @@ instruments
sudo groupadd -r colord

- and then add youself to the colord group.
+ and then add yourself to the colord group.

You may have to log out and then in again for the groups to become - effecive.
+ effective.

You can test whether your instrument is accessible by plugging it in and then running "spotread -?" and looking for it listed after the
If you have a serial instrument then you may find that by default you don't have permission to access the serial ports or a Serial to USB adapter. Most systems make the serial ports available to any - user in the tty and uucp group, so the best way of - getting access to the serial ports is to add yourself to those - groups. You can do this either by using a "Users and Groups" system - administration tool, or on the command line using "usermod":
+ user in the tty, uucp or dialout group, + so the best way of getting access to the serial ports is to add + yourself to the correct group. (You can identify the correct group + by looking at the group name shown by ls -l /dev/ttyS* )
+
+ You can add yourself to a group either by using a "Users + and Groups" system administration tool, or on the command line using + "usermod":

    su root
-     usermod -a -G tty,uucp $USER
+     usermod -a -G dialout $USER

or

-    sudo usermod -a -G tty,uucp $USER
+    sudo usermod -a -G dialout $USER

(If the usermod program isn't found as root, it might be in /usr/sbin, ie. use /usr/sbin/usermod .... etc.
If usermod doesn't recognize the -a flag try "usermod -A - colord $USER".
+ dialout $USER".
If this doesn't work you will have to run "id yourusername" to list the current suplemental
- groups, and add a tty or uucp group using just "usermod -G - group1,group2,... yourusername")
+ groups, and add a tty, uucp or dialout group using just + "usermod -G group1,group2,... yourusername"
+ Another option may be to use gpasswd -a $USER dialout)

You may have to log out and then in again for the group to become - effecive.
+ effective.

diff --git a/doc/Installing_MSWindows.html b/doc/Installing_MSWindows.html index bb610cd..21f39ca 100644 --- a/doc/Installing_MSWindows.html +++ b/doc/Installing_MSWindows.html @@ -9,8 +9,8 @@ [Netscape]"> Argyll Installation on Microsoft Windows - +

Installing the software on Microsoft Windows

- For Windows 8 & 8.1, - look in
+ For Windows 8, 8.1 + & 10, look in
    Desktop -> Settings -> Control Panel -> System And Security -> System -> Advanced System Settings -> Environment Variables
@@ -133,22 +133,24 @@ for these instruments, although it is possible to select the libusb0.sys driver as an alternative to the default HID driver.

- If you are using the JETI specbos 1211 or 1201, - or the Klein K10A then you may need to install the FTDI Virtual COM - Port Drivers (VCP), if they are not already on your system.
+ If you are using the JETI specbos 1211, 1201, + 1511, 1501 and the Klien K10A then you may need + to install the FTDI + Virtual COM Port Drivers (VCP), if they are not already on + your system. You may have to update to the latest FTDI driver to + work with the FTDI FT231XS chip that the JETI specbos 1511, + 1501 use.

Jump to your operating system version:

- Windows 8
+ Windows 8, 8.1 & 10
Windows 7
Windows Vista
Windows XP
Windows 2000

Windows 8 & 8.1Windows 8, 8.1 & 10

- - - - - - Argyll Installation on Apple OS X - - -
Installing the software on Apple OS X
-
-
- You will need to unpack the downloaded file in such a way that the - files it contains end up in the location you have chosen to hold its - contents.
-
- If you want to install it system wide, then you probably want to - unpack it in the /Applications folder, so that it ends up in - the /Applications/Argyll_VX.X.X folder.
- Another option is just to install it somewhere under your $HOME - folder, such as $HOME/Argyll_VX.X.X - or $HOME/bin/Argyll_VX.X.X, - depending on how you like to organize your applications and utility - programs. ($HOME is the shell symbolic name for your home folder, - typically /Users/username. Another abbreviation for it is the - ~ character.)
-
- 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 /Applications, $HOME - or $HOME/bin.
-
- Alternatively you can unpack it on the command line using the - command tar -zxf archivename.tgz, which will - create a folder Argyll_VX.X.X - in your current folder, where X.X.X is the version number, and the - executables will be in Argyll_VX.X.X/bin - sub-folder.
-
- 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).
-
- You should configure your $PATH environment variable to give the - shell access to the executable from your command line environment - without having to spell out the whole path every time, by editing - your .profile file, which - will be in your $HOME folder. You can open a graphical editor on - this file by using the open command:
-
- open $HOME/.profile
-
- or alternatively, use some other text editor that you are familiar - with.
-
- Add a line similar to the following line to your .profile file:
-
- PATH=$PATH:/Applications/Argyll_VX.X.X/bin
-
- where "/Applications/Argyll_VX.X.X/bin" is the path to the folder - that contains the ArgyllCMS executables.
- Save your changes and exit the editor.
-
- If you want further guidance in setting up and using a command line - environment, then please consult an appropriate tutorial, e.g. <ShellIntro>.
-
- The .tgz file also contains several useful reference files (such as - scanner chart recognition templates, sample illumination spectrum - etc.) in the ref sub-folder, as well as all the current - documentation in a doc sub-folder.
-
- For most devices there is nothing special to do. Plug in and go. - Some devices may not work without some extra help though:
-
X-Rite ColorMunki
- 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:
-
- 1) Turn off the X-Rite service for the ColorMunki. See <http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980>.
-
- 2) Run all Argyll programs that need to access the instrument as - root. For instance:
-
-     sudo spotread
-
- and then you will be asked for the root password.
- While these methods will work, they are inconvenient.
-
- 3) Alter the X-Rite drivers Daeomon so that it runs under your user - account.
-
- To do this you need to edit the script that controls the X-Rite - Daemon.
-
-     cd ~
-     whoami
-     cp - /Library/LaunchDaemons/com.xrite.device.colormunki.plist temp.plist
-     open temp.plist
-
- and add one child below the root:
-
+ + + + + + + Argyll Installation on Apple OS X + + +
Installing the software on Apple OS X
+
+
+ You will need to unpack the downloaded file in such a way that the + files it contains end up in the location you have chosen to hold its + contents.
+
+ If you want to install it system wide, then you probably want to + unpack it in the /Applications folder, so that it ends up in + the /Applications/Argyll_VX.X.X folder.
+ Another option is just to install it somewhere under your $HOME + folder, such as $HOME/Argyll_VX.X.X + or $HOME/bin/Argyll_VX.X.X, + depending on how you like to organize your applications and utility + programs. ($HOME is the shell symbolic name for your home folder, + typically /Users/username. Another abbreviation for it is the + ~ character.)
+
+ 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 /Applications, $HOME + or $HOME/bin.
+
+ Alternatively you can unpack it on the command line using the + command tar -zxf archivename.tgz, which will + create a folder Argyll_VX.X.X + in your current folder, where X.X.X is the version number, and the + executables will be in Argyll_VX.X.X/bin + sub-folder.
+
+ 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).
+
+ You should configure your $PATH environment variable to give the + shell access to the executable from your command line environment + without having to spell out the whole path every time, by editing + your .profile file, which + will be in your $HOME folder. You can open a graphical editor on + this file by using the open command:
+
+ open $HOME/.profile
+
+ or alternatively, use some other text editor that you are familiar + with.
+
+ Add a line similar to the following line to your .profile file:
+
+ PATH=$PATH:/Applications/Argyll_VX.X.X/bin
+
+ where "/Applications/Argyll_VX.X.X/bin" is the path to the folder + that contains the ArgyllCMS executables.
+ Save your changes and exit the editor.
+
+ If you want further guidance in setting up and using a command line + environment, then please consult an appropriate tutorial, e.g. <ShellIntro>.
+
+ The .tgz file also contains several useful reference files (such as + scanner chart recognition templates, sample illumination spectrum + etc.) in the ref sub-folder, as well as all the current + documentation in a doc sub-folder.
+
+ For most devices there is nothing special to do. Plug in and go. + Some devices may not work without some extra help though:
+
X-Rite ColorMunki
+ 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:
+
+ 1) Turn off the X-Rite service for the ColorMunki. See <http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980>.
+
+ 2) Run all Argyll programs that need to access the instrument as + root. For instance:
+
+     sudo spotread
+
+ and then you will be asked for the root password.
+ While these methods will work, they are inconvenient.
+
+ 3) Alter the X-Rite drivers Daeomon so that it runs under your user + account.
+
+ To do this you need to edit the script that controls the X-Rite + Daemon.
+
+     cd ~
+     whoami
+     cp + /Library/LaunchDaemons/com.xrite.device.colormunki.plist temp.plist
+     open temp.plist
+
+ and add one child below the root:
+
    Item                             Type                    @@ -122,9 +122,10 @@ Type            &nbs - Value           -
-     UserName + + Value           +
+     UserName                   string                   @@ -136,62 +137,63 @@ string            &n - myusername
-
- where "myusername" is your username shown by whoami, and save the - file. You then need to copy the modified file back:
-
-     sudo cp temp.plist - /Library/LaunchDaemons/com.xrite.device.colormunki.plist
-
- You will then need to restart the machine for this change to take - effect, or invoke the following commands:
-
-    sudo launchctl unload - /Library/LaunchDaemons/com.xrite.device.colormunki.plist
-    sudo launchctl load - /Library/LaunchDaemons/com.xrite.device.colormunki.plist
-
- NOTE that after running - Argyll tools, you may have to turn the X-Rite service off then on - again, or disconnect and reconnect the instrument.
-
-
X-Rite EyeOne Pro
-
- 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:
-
- 1) Turn off the X-Rite service for the EyeOne Pro. See <http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980>.
-
- 2) Run all Argyll programs that need to access the instrument as - root. For instance:
-
-     sudo spotread
-
- and then you will be asked for the root password.
- While these methods will work, they are inconvenient.
-
- 3) Alter the X-Rite drivers Daemon so that it runs under your user - account.
-
- To do this you need to edit the script that controls the X-Rite - Daemon.
-
-     cd ~
-     whoami
-     cp - /Library/LaunchDaemons/com.xrite.device.i1.plist temp.plist
-     open temp.plist
-
- and add one child below the root:
-
+ + myusername
+
+ where "myusername" is your username shown by whoami, and save the + file. You then need to copy the modified file back:
+
+     sudo cp temp.plist + /Library/LaunchDaemons/com.xrite.device.colormunki.plist
+
+ You will then need to restart the machine for this change to take + effect, or invoke the following commands:
+
+    sudo launchctl unload + /Library/LaunchDaemons/com.xrite.device.colormunki.plist
+    sudo launchctl load + /Library/LaunchDaemons/com.xrite.device.colormunki.plist
+
+ NOTE that after running + Argyll tools, you may have to turn the X-Rite service off then on + again, or disconnect and reconnect the instrument.
+
+
X-Rite EyeOne Pro
+
+ 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:
+
+ 1) Turn off the X-Rite service for the EyeOne Pro. See <http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980>.
+
+ 2) Run all Argyll programs that need to access the instrument as + root. For instance:
+
+     sudo spotread
+
+ and then you will be asked for the root password.
+ While these methods will work, they are inconvenient.
+
+ 3) Alter the X-Rite drivers Daemon so that it runs under your user + account.
+
+ To do this you need to edit the script that controls the X-Rite + Daemon.
+
+     cd ~
+     whoami
+     cp + /Library/LaunchDaemons/com.xrite.device.i1.plist temp.plist
+     open temp.plist
+
+ and add one child below the root:
+
    Item                             Type                    @@ -203,9 +205,10 @@ Type            &nbs - Value           -
-     UserName + + Value           +
+     UserName                   string                   @@ -217,26 +220,27 @@ string            &n - myusername
-
- where "myusername" is your username shown by whoami, and save the - file. You then need to copy the modified file back:
-
-     sudo cp temp.plist - /Library/LaunchDaemons/com.xrite.device.i1.plist
-
- You will then need to restart the machine for this change to take - effect, or invoke the following commands:
-
-    sudo launchctl unload - /Library/LaunchDaemons/com.xrite.device.i1.plist
-    sudo launchctl load - /Library/LaunchDaemons/com.xrite.device.i1.plist
-
- NOTE that after running - Argyll tools, you may have to turn the X-Rite service off then on - again, or disconnect and reconnect the instrument.
-
+ + myusername
+
+ where "myusername" is your username shown by whoami, and save the + file. You then need to copy the modified file back:
+
+     sudo cp temp.plist + /Library/LaunchDaemons/com.xrite.device.i1.plist
+
+ You will then need to restart the machine for this change to take + effect, or invoke the following commands:
+
+    sudo launchctl unload + /Library/LaunchDaemons/com.xrite.device.i1.plist
+    sudo launchctl load + /Library/LaunchDaemons/com.xrite.device.i1.plist
+
+ NOTE that after running + Argyll tools, you may have to turn the X-Rite service off then on + again, or disconnect and reconnect the instrument.
+

JETI specbos @@ -248,68 +252,70 @@ specbos - 1201 and 1211 and Klein K10A
-
-
- If you are using the JETI specbos 1211 and 1201, - or the Klein K10A then you may need to install the FTDI Virtual COM - Port Drivers (VCP), if they are not already on your system.
-
-
HCFR Colorimeter
- The default OS X class drivers will grab this device, preventing - Argyll from accessing it. To overcome this, you need to install a - codeless kernel extension if you wish to use the HCFR colorimeter, - that prevents this from happening. From the command line you need to - create a folder called Argyll.kext somewhere convenient, and then - place in it one file called Info.plist, containing the following:
-
-     ----------------- cut here ---------------------
-    <?xml version="1.0" encoding="UTF-8"?>
-    <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST - 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
-    <plist version="1.0">
-    <dict>
-    - <key>CFBundleDevelopmentRegion</key> - <string>English</string>
-    - <key>CFBundleGetInfoString</key> <string>Libusb - USB device Shield</string>
-      - <key>CFBundleIdentifier</key> - <string>com.libusb.USB_Shield</string>
-    - <key>CFBundleInfoDictionaryVersion</key> - <string>6.0</string>
-    <key>CFBundleName</key> - <string>Libusb USB device Shield</string>
-    - <key>CFBundlePackageType</key> - <string>KEXT</string>
-    <key>CFBundleSignature</key> - <string>????</string>
-    <key>CFBundleVersion</key> - <string>6.0</string>
-      - <key>IOKitPersonalities</key>
-        <dict>
-        - <key>HCFR</key>
-          <dict>
-            - <key>CFBundleIdentifier</key> - <string>com.apple.driver.AppleUSBComposite</string>
-             -    <key>IOClass</key> - <string>AppleUSBComposite</string>
-            - <key>IOProviderClass</key> - <string>IOUSBDevice</string>
-           -    <key>idVendor</key> - <integer>1243</integer>
+ + 1201 and 1211 and Klein K10A
+

+
+ If you are using the JETI specbos 1211, 1201, + 1511, 1501 and the Klien K10A then you may need to + install the FTDI + Virtual COM Port Drivers (VCP), if they are not already on + your system. You may have to update to the latest FTDI driver to + work with the FTDI FT231XS chip that the JETI specbos 1511, + 1501 use.
+

HCFR Colorimeter

+ The default OS X class drivers will grab this device, preventing + Argyll from accessing it. To overcome this, you need to install a + codeless kernel extension if you wish to use the HCFR colorimeter, + that prevents this from happening. From the command line you need to + create a folder called Argyll.kext somewhere convenient, and then + place in it one file called Info.plist, containing the following:
+
+     ----------------- cut here ---------------------
+    <?xml version="1.0" encoding="UTF-8"?>
+    <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST + 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+    <plist version="1.0">
+    <dict>
+    + <key>CFBundleDevelopmentRegion</key> + <string>English</string>
+    + <key>CFBundleGetInfoString</key> <string>Libusb + USB device Shield</string>
+      + <key>CFBundleIdentifier</key> + <string>com.libusb.USB_Shield</string>
+    + <key>CFBundleInfoDictionaryVersion</key> + <string>6.0</string>
+    <key>CFBundleName</key> + <string>Libusb USB device Shield</string>
+    + <key>CFBundlePackageType</key> + <string>KEXT</string>
+    <key>CFBundleSignature</key> + <string>????</string>
+    <key>CFBundleVersion</key> + <string>6.0</string>
+      + <key>IOKitPersonalities</key>
+        <dict>
+        + <key>HCFR</key>
+          <dict>
+            + <key>CFBundleIdentifier</key> + <string>com.apple.driver.AppleUSBComposite</string>
+             +    <key>IOClass</key> + <string>AppleUSBComposite</string>
+            + <key>IOProviderClass</key> + <string>IOUSBDevice</string>
+           +    <key>idVendor</key> + <integer>1243</integer>
             @@ -320,35 +326,36 @@ specbos - <key>idProduct</key> - <integer>91</integer>
-            - </dict>
-    </dict>
-    - <key>OSBundleCompatibleVersion</key> - <string>1.8</string>
-    <key>OSBundleLibraries</key>
-    <dict>
-        - <key>com.apple.kernel.iokit</key> - <string>6.0</string>
-        </dict>
-    </dict>
-    </plist>
- ----------------- cut here ---------------------
-
- (You can also copy this from the source installation in - usb/Argyll.kext)
-
- You then need to install it by using:
-
- sudo cp -R Argyll.kext /System/Library/Extensions
-
- supplying the appropriate root password when prompted.
- Reboot the system to activate the extension.
-
-

- - + + <key>idProduct</key> + <integer>91</integer>
+            + </dict>
+    </dict>
+    + <key>OSBundleCompatibleVersion</key> + <string>1.8</string>
+    <key>OSBundleLibraries</key>
+    <dict>
+        + <key>com.apple.kernel.iokit</key> + <string>6.0</string>
+        </dict>
+    </dict>
+    </plist>
+ ----------------- cut here ---------------------
+
+ (You can also copy this from the source installation in + usb/Argyll.kext)
+
+ You then need to install it by using:
+
+ sudo cp -R Argyll.kext /System/Library/Extensions
+
+ supplying the appropriate root password when prompted.
+ Reboot the system to activate the extension.
+
+

+ + diff --git a/doc/JETI_1501.jpg b/doc/JETI_1501.jpg new file mode 100644 index 0000000..ac348d6 Binary files /dev/null and b/doc/JETI_1501.jpg differ diff --git a/doc/License4.txt b/doc/License4.txt new file mode 100644 index 0000000..61be41a --- /dev/null +++ b/doc/License4.txt @@ -0,0 +1,22 @@ +************************************************************************* +Copyright (c) 1997-2015 Graeme W. Gill + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN +THE SOFTWARE. + +************************************************************************* diff --git a/doc/Performance.html b/doc/Performance.html index 340cec0..c45084b 100644 --- a/doc/Performance.html +++ b/doc/Performance.html @@ -2,139 +2,72 @@ + charset=windows-1252"> + charset=windows-1252"> Argyll Performance Tuning -

- Performance Tuning

Performance Tuning

Some operations in Argyll can be particularly slow, so it is worth examining ways of improving performance, or trading memory - consumption - for performance.
+ consumption for performance.
+
+ (See here for how to set Environment + variables.)

Creating Device Links and Profiles

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 + 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.
+ of the available RAM on the system, with a minimum of 50 Mbytes.

The reverse cache size can be changed by setting an environment - variable - ARGYLL_REV_CACHE_MULT 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).
+ variable ARGYLL_REV_CACHE_MULT + 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).

If you find that colprof - or collink - are working very slowly, but that your CPU's are nearly idle, then - this + or collink 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 lower - the amount of memory Argyll uses by setting ARGYLL_REV_CACHE_MULT to a value - less than 1.0 (ie. try 0.5).
+ 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 lower the amount of memory + Argyll uses by setting ARGYLL_REV_CACHE_MULT + to a value less than 1.0 (ie. try 0.5).

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.
+ 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.

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 ARGYLL_REV_ACC_GRID_RES_MULT + 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 ARGYLL_REV_ACC_GRID_RES_MULT 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.
-
-

Setting an environment variable:

-
- To set an environment variable an MSWindows DOS shell, either use - set, - e.g.;
-
-     set ARGYLL_REV_CACHE_MULT=1.5
-
- which will set the value for that session, or set it in
-
- Control Panel->System->Advanced->Environment Variables..
-
- in either user or system variables.
-
- You can examine individual variables using
-
-     echo %VARIABLE_NAME%
-
- or see all of them using
-
-    set
-
-
- For OS X or Linux, the exact procedure will depend on the shell you - are - running, but
- is usually something like:
-
-     export ARGYLL_REV_CACHE_MULT=1.5
- or
-     set ARGYLL_REV_CACHE_MULT=1.5
- or
-     ARGYLL_REV_CACHE_MULT=1.5
-
- and may need separately exporting, something like:
-
-     export ARGYLL_REV_CACHE_MULT
-
- Generally it should be configured in the shell start-up - script, - if you - want the setting to be used
- for every session.
-
- You can examine individual variables using
-
-     echo $VARIABLE_NAME
-
- or see all of them using
+ 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.

-    set

diff --git a/doc/Scenarios.html b/doc/Scenarios.html index c8bb154..8aa5d64 100644 --- a/doc/Scenarios.html +++ b/doc/Scenarios.html @@ -1,134 +1,134 @@ - - - - Argyll Usage Scenarios - - - -

Typical usage Scenarios and Examples

- Choose a task from the list below. For more details on alternative - options, follow the links to the individual tools being used.
-
- Note that by default it is assumed that ICC profile have the file - extension .icm, but that on - Apple OS X and Unix/Linux platforms, the .icc extension is expected and should be used.
-

Profiling Displays

Checking you can access your - display
-

Adjusting and Calibrating a - displays

Adjusting, calibrating and - profiling in one step
-

Creating display test values

Taking readings from a - display

Creating a display profile

Installing a display profile

Expert tips when measuring displays

Calibrating and profiling a display that doesn't - have VideoLUT access.

- Profiling Scanners and other input devices such as - cameras
-

Types of test charts

Taking readings from a - scanner

Creating a scanner profile

- Profiling Printers

Creating a print profile - test chart

Printing a - print profile test chart

Reading a print test chart - using an instrument

Reading a print test chart - using a scanner

Creating a printer profile
-

Choosing a black generation - curve

-
-

Calibrating Printers

Calibrated - print workflows

Creating a - print calibration test chart

Creating a - printer calibration
-

Using a printer - calibration

How profile ink limits are - handled when calibration is being used
-

Linking Profiles

Image dependent gamut - mapping using device links
-

Soft Proofing Link
-

Transforming colorspaces of raster files

Creating Video Calibration 3DLuts

Verifying Video Calibration 3DLuts

-
-

Profiling Displays

- Argyll supports adjusting, calibrating and profiling of displays - using one of a number of instruments - see instruments 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.
-
-

Checking you can access your display
-

- You might first want to check that you are accessing and can - calibrate your display. You can do this using the dispwin - tool. If you just run dispwin 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 dispwin (by giving it - an unrecognized option, e.g. -?) - then it will show a list of available displays next to the -d - flag. Make sure that you are accessing the display you intend to - calibrate and profile, and that the VideoLUT is effective (the -r flag can be used to just run - the VideoLUT test). You can also try clearing the VideoLUTs using - the -c flag, and loading a - deliberately strange looking calibration strange.cal that is provided in the Argyll ref directory.
-
- Note that calibrating and/or profiling remote displays is possible using X11 or a web - browser (see -d option of - dispcal and dispread), or by using some external program to send - test colors to a display (see -C - and -M options of dispcal + + + + Argyll Usage Scenarios + + + +

Typical usage Scenarios and Examples

+ Choose a task from the list below. For more details on alternative + options, follow the links to the individual tools being used.
+
+ Note that by default it is assumed that ICC profile have the file + extension .icm, but that on + Apple OS X and Unix/Linux platforms, the .icc extension is expected and should be used.
+

Profiling Displays

Checking you can access your + display
+

Adjusting and Calibrating a + displays

Adjusting, calibrating and + profiling in one step
+

Creating display test values

Taking readings from a + display

Creating a display profile

Installing a display profile

Expert tips when measuring displays

Calibrating and profiling a display that doesn't + have VideoLUT access.

+ Profiling Scanners and other input devices such as + cameras
+

Types of test charts

Taking readings from a + scanner

Creating a scanner profile

+ Profiling Printers

Creating a print profile + test chart

Printing a + print profile test chart

Reading a print test chart + using an instrument

Reading a print test chart + using a scanner

Creating a printer profile
+

Choosing a black generation + curve

+
+

Calibrating Printers

Calibrated + print workflows

Creating a + print calibration test chart

Creating a + printer calibration
+

Using a printer + calibration

How profile ink limits are + handled when calibration is being used
+

Linking Profiles

Image dependent gamut + mapping using device links
+

Soft Proofing Link
+

Transforming colorspaces of raster files

Creating Video Calibration 3DLuts

Verifying Video Calibration 3DLuts

+
+

Profiling Displays

+ Argyll supports adjusting, calibrating and profiling of displays + using one of a number of instruments - see instruments 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.
+
+

Checking you can access your display
+

+ You might first want to check that you are accessing and can + calibrate your display. You can do this using the dispwin + tool. If you just run dispwin 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 dispwin (by giving it + an unrecognized option, e.g. -?) + then it will show a list of available displays next to the -d + flag. Make sure that you are accessing the display you intend to + calibrate and profile, and that the VideoLUT is effective (the -r flag can be used to just run + the VideoLUT test). You can also try clearing the VideoLUTs using + the -c flag, and loading a + deliberately strange looking calibration strange.cal that is provided in the Argyll ref directory.
+
+ Note that calibrating and/or profiling remote displays is possible using X11 or a web + browser (see -d option of + dispcal and dispread), or by using some external program to send + test colors to a display (see -C + and -M options of dispcal and dispread), but you may want to refer to Calibrating @@ -184,26 +184,29 @@ - and profiling a display that doesn't have VideoLUT access.
-
-

Adjusting and Calibrating Displays

- Please read What's the difference between - Calibration and Characterization ? if you are unclear as to - the difference .
-
- 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.
-
- You can run dispcal -r to check on how - your display is currently set up. (you may have to run this as .
+
+

Adjusting and Calibrating Displays

+ Please read What's the difference between + Calibration and Characterization ? if you are unclear as to + the difference .
+
+ 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.
+
+ You can run dispcal -r to check on how + your display is currently set up. (you may have to run this as dispcal -yl @@ -265,331 +268,343 @@ - -r for an LCD display, or dispcal -yc -r for a - CRT display with most of the colorimeter instruments. If so, this - will apply to all of the following examples.)
-
- Once this is done, dispcal 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.
-
- A typical calibration that leaves the brightness and white point - alone, might be:
-
- dispcal -v TargetA
-
- which will result in a "TargetA.cal" calibration file, that can then - be used during the profiling stage.
-
- 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 dispread.
-
- Dispcal 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 dispcal - and dispread 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. LCD displays seem to be less - influenced by what else is on the screen.
-
- If dispcal is run without - arguments, it will provide a usage screen. The -c parameter allows selecting a - communication port for an instrument, or selecting the instrument - you want to use, and the -d 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 -P 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 dispwin tool.
-
- For a more detailed discussion on interactively adjusting the - display controls using dispcal, - see dispcal-adjustment. Once - you have adjusted and calibrated your display, you can move on to - the next step.
-
- When you have calibrated and profiled your display, you can keep it - calibrated using the dispcal -u - option.
-
-

Adjusting, calibrating and profiling in one - step.

- If a simple matrix/shaper display profile is all that is desired, dispcal can be used to do this, - permitting display adjustment, calibration and profiling all in one - operation. This is done by using the dispcal -o - flag:
-
- dispcal -v - -o TargetA
-
- This will create both a TargetA.cal file, but also a TargetA.icm - file. See -o and -O for other variations.
-
- For more flexibility in creating a display profile, the separate - steps of creating characterization test values using targen, reading them from the - display using dispread, and - then creating a profile using colprof - are used. The following steps illustrate this:
-

Profiling in several steps: Creating display - test values

- If the dispcal 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.
-
- The first step in profiling any output device, is to create a set of - device colorspace test values. The important parameters needed are: -
-

What colorspace does the device use ?
How many test patches do I want to use ?
What information do I already have about how the device - behaves ?

- 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.
- 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.
-
- 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.
-
- 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:
-
- targen -v - -d3 -f500 - DisplayA
-
- 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:
-
- targen -v - -d3 -f500 - -cOldDisplay.icm DisplayA
-
- The output of targen will be the file DisplayA.ti1, - containing the device space test values, as well as expected CIE - values used for chart recognition purposes.
-
-

Profiling in several steps: Taking readings - from a display

- 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.
-
- dispread -v - DisplayA
-
- If we created a calibration for the display using dispcal, then we will want to use this - when we take the display readings (e.g. TargetA.cal from the - calibration example)..
-
- dispread -v - -k TargetA.cal DisplayA
-
- dispread 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 -d - parameter, and an alternate location and size for the test window - using the -P parameter as - with dispcal.
-

Profiling in several steps: Creating a display - profile

- 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.
-
- To create a matrix/shaper profile, the following suffices:
-
- colprof -v - -D"Display A" -qm - -as DisplayA
-
- 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:
-
- colprof -v - -D"Display A" -qm - -S - fogra39l.icm -cpp -dmt DisplayA
-
- 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.
- If a calibration file was used with dispread, - 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.
-

Installing a display profile

- dispwin provides a convenient way of - installing a profile as the default system profile for the chosen - display:
-
- dispwin -I - DisplayA.icm
-
- 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 -I - option will load a calibration (ICC profile or .cal file) into the - current display.
-
- 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 Microsoft Color Control Panel Applet for Windows XP - available for download from Microsoft to do this, but NOTE however that it seems to - have a bug, in that it - sometimes associates the profiles with the wrong monitor 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. ]
- On Microsoft Vista, you need to use dispwin -L or some other tool to - load the installed profiles calibration at startup.
-
- To use dispwin to load the installed profiles calibration to the - display, use
-
- dispwin -L
-
- As per usual, you can select the appropriate display using the -d flag.
-
- This can be automated on MSWindows and X11/Linux by adding this - command to an appropriate startup script.
- More system specific details, including how to create such startup - scripts are here.
-
- If you are using Microsoft Vista, - there is a known bug 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 - dispwin -L - may not restore the calibration, because Vista filters out setting - (what it thinks) is a calibration that is already loaded. Use dispwin -c -L - as a workaround, as this will first clear the calibration, then - re-load the current calibration.
-
- On X11/Linux systems, you could try adding dispwin - -L to your ~/.config/autostart 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 dispwin -E 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.
-
-

Expert tips when measuring displays:
-

- 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.
-
- If you are using an Eye-One Pro or ColorMunki spectrometer, then you - may wish to use the high resolution - spectral mode (-H). - This may be better at capturing the often narrow wavelength peaks - that are typical of display primary colors.
-
- 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 compensate - for dark calibration changes (-Ib) - 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.
-
- 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 for an LCD display, or dispcal -yc -r for a + CRT display with most of the colorimeter instruments. If so, this + will apply to all of the following examples.)
+
+ Once this is done, dispcal 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.
+
+ A typical calibration that leaves the brightness and white point + alone, might be:
+
+ dispcal -v TargetA
+
+ which will result in a "TargetA.cal" calibration file, that can then + be used during the profiling stage.
+
+ 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 dispread.
+
+ Dispcal 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 dispcal + and dispread 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. LCD displays seem to be less + influenced by what else is on the screen.
+
+ If dispcal is run without + arguments, it will provide a usage screen. The -c parameter allows selecting a + communication port for an instrument, or selecting the instrument + you want to use, and the -d 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 -P 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 dispwin tool.
+
+ For a more detailed discussion on interactively adjusting the + display controls using dispcal, + see dispcal-adjustment. Once + you have adjusted and calibrated your display, you can move on to + the next step.
+
+ When you have calibrated and profiled your display, you can keep it + calibrated using the dispcal -u + option.
+
+

Adjusting, calibrating and profiling in one + step.

+ If a simple matrix/shaper display profile is all that is desired, dispcal can be used to do this, + permitting display adjustment, calibration and profiling all in one + operation. This is done by using the dispcal -o + flag:
+
+ dispcal -v + -o TargetA
+
+ This will create both a TargetA.cal file, but also a TargetA.icm + file. See -o and -O for other variations.
+
+ For more flexibility in creating a display profile, the separate + steps of creating characterization test values using targen, reading them from the + display using dispread, and + then creating a profile using colprof + are used. The following steps illustrate this:
+

Profiling in several steps: Creating display + test values

+ If the dispcal 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.
+
+ The first step in profiling any output device, is to create a set of + device colorspace test values. The important parameters needed are: +
+

What colorspace does the device use ?
How many test patches do I want to use ?
What information do I already have about how the device + behaves ?

+ 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.
+ 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.
+
+ 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.
+
+ 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:
+
+ targen -v + -d3 -f500 + DisplayA
+
+ 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:
+
+ targen -v + -d3 -f500 + -cOldDisplay.icm DisplayA
+
+ The output of targen will be the file DisplayA.ti1, + containing the device space test values, as well as expected CIE + values used for chart recognition purposes.
+
+

Profiling in several steps: Taking readings + from a display

+ 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.
+
+ dispread -v + DisplayA
+
+ If we created a calibration for the display using dispcal, then we will want to use this + when we take the display readings (e.g. TargetA.cal from the + calibration example)..
+
+ dispread -v + -k TargetA.cal DisplayA
+
+ dispread 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 -d + parameter, and an alternate location and size for the test window + using the -P parameter as + with dispcal.
+

Profiling in several steps: Creating a display + profile

+ 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.
+
+ To create a matrix/shaper profile, the following suffices:
+
+ colprof -v + -D"Display A" -qm + -as DisplayA
+
+ 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:
+
+ colprof -v + -D"Display A" -qm + -S + fogra39l.icm -cpp -dmt DisplayA
+
+ A fallback to using a specific source profile/gamut is to use a + general compression percentage as a gamut mapping:
+
+ colprof -v + -D"Display A" -qm + -S 20 -cpp -dmt DisplayA
+
+ 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.
+ If a calibration file was used with dispread, + 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.
+

Installing a display profile

+ dispwin provides a convenient way of + installing a profile as the default system profile for the chosen + display:
+
+ dispwin -I + DisplayA.icm
+
+ 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 -I + option will load a calibration (ICC profile or .cal file) into the + current display.
+
+ 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 Microsoft Color Control Panel Applet for Windows XP + available for download from Microsoft to do this, but NOTE however that it seems to + have a bug, in that it + sometimes associates the profiles with the wrong monitor 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. ]
+ On Microsoft Vista, you need to use dispwin -L or some other tool to + load the installed profiles calibration at startup.
+
+ To use dispwin to load the installed profiles calibration to the + display, use
+
+ dispwin -L
+
+ As per usual, you can select the appropriate display using the -d flag.
+
+ This can be automated on MSWindows and X11/Linux by adding this + command to an appropriate startup script.
+ More system specific details, including how to create such startup + scripts are here.
+
+ If you are using Microsoft Vista, + there is a known bug 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 + dispwin -L + may not restore the calibration, because Vista filters out setting + (what it thinks) is a calibration that is already loaded. Use dispwin -c -L + as a workaround, as this will first clear the calibration, then + re-load the current calibration.
+
+ On X11/Linux systems, you could try adding dispwin + -L to your ~/.config/autostart 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 dispwin -E 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.
+
+

Expert tips when measuring displays:
+

+ 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.
+
+ If you are using an Eye-One Pro or ColorMunki spectrometer, then you + may wish to use the high resolution + spectral mode (-H). + This may be better at capturing the often narrow wavelength peaks + that are typical of display primary colors.
+
+ 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 compensate + for dark calibration changes (-Ib) + 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.
+
+ 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 compensate for display white level @@ -650,20 +665,23 @@ - (-Iw) changes by doing on - the fly calibrations during the measurements. Instrument black level - drift and display white level drift can be combined (-Ibw).
-
- 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 + + + + (-Iw) changes by doing on + the fly calibrations during the measurements. Instrument black level + drift and display white level drift can be combined (-Ibw).
+
+ 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 Colorimeter @@ -723,117 +741,120 @@ - Correction Matrix. 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 ccmx files is here.
-
-

Calibrating and profiling a display that - doesn't have VideoLUT access.

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.
-

There are two basic options in this situation:
-

1) Don't attempt to calibrate, just profile the display.
- 2) Calibrate, but incorporate the calibration in some other - way in the workflow.
-

The first case requires nothing special - just skip calibration - (see the previous section Profiling in several - steps: Creating display test values).

In the second case, there are three choices:
-

2a) Use dispcal to create a calibration and a quick profile - that incorporates the calibration into the profile.
- 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.
- 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.
-

The first case requires nothing special, use dispcal in a normal - fashioned with the -o - option to generate a quick profile.The profile created will not contain a 'vcgt' - tag, but instead will have the calibration curves incorporated - into the profile itself. If calibration parameters are chosen that - change the displays white point or brightness, then this will - result in a slightly unusual profile that has a white point that - does not correspond with 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.
-

In the second case, the calibration file created using dispcal - should be provided to dispread using the -K flag:
-

dispread -v - -K TargetA.cal DisplayA

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.
- You can then use applycal 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.
-

- 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.:
-
- cctiff SourceProfile.icm DisplayA.icm DisplayA.cal - infile.tif outfile.tif
- or
- cctiff SourceProfile.icm DisplayA.icm DisplayA.cal - infile.jpg outfile.jpg
-
-

Profiling Scanners and other input devices - such as cameras
-

- 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.
-

Types of test charts

- 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.
- An accessible and affordable source of such targets is Wolf Faust a - www.coloraid.de.
- Another source is LaserSoft www.silverfast.com.
- The Kodak Q-60 Color Input Target is also a typical example:
-
- Kodak Q60 chart image

-
- 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:
- ColorChecker 24 patch

-
- Other popular charts are the X-Rite/GretagMacbeth ColorChecker DC + + + + Correction Matrix. 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 ccmx files is here.
+
+

Calibrating and profiling a display that + doesn't have VideoLUT access.

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.
+

There are two basic options in this situation:
+

1) Don't attempt to calibrate, just profile the display.
+ 2) Calibrate, but incorporate the calibration in some other + way in the workflow.
+

The first case requires nothing special - just skip calibration + (see the previous section Profiling in several + steps: Creating display test values).

In the second case, there are three choices:
+

2a) Use dispcal to create a calibration and a quick profile + that incorporates the calibration into the profile.
+ 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.
+ 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.
+

The first case requires nothing special, use dispcal in a normal + fashioned with the -o + option to generate a quick profile.The profile created will not contain a 'vcgt' + tag, but instead will have the calibration curves incorporated + into the profile itself. If calibration parameters are chosen that + change the displays white point or brightness, then this will + result in a slightly unusual profile that has a white point that + does not correspond with 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.
+

In the second case, the calibration file created using dispcal + should be provided to dispread using the -K flag:
+

dispread -v + -K TargetA.cal DisplayA

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.
+ You can then use applycal 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.
+

+ 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.:
+
+ cctiff SourceProfile.icm DisplayA.icm DisplayA.cal + infile.tif outfile.tif
+ or
+ cctiff SourceProfile.icm DisplayA.icm DisplayA.cal + infile.jpg outfile.jpg
+
+

Profiling Scanners and other input devices + such as cameras
+

+ 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.
+

Types of test charts

+ 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.
+ An accessible and affordable source of such targets is Wolf Faust a + www.coloraid.de.
+ Another source is LaserSoft www.silverfast.com.
+ The Kodak Q-60 Color Input Target is also a typical example:
+
+ Kodak Q60 chart image

+
+ 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:
+ ColorChecker 24 patch

+
+ Other popular charts are the X-Rite/GretagMacbeth ColorChecker DC and ColorChecker @@ -894,17 +915,20 @@ - SG charts:
-
-

-
- The GretagMacbeth Eye-One Pro Scan Target 1.4 can also be used:
-
- Eye-One Scan Target 1.4

-
+ + + + SG charts:
+
+ GretagMacbeth ColorChecker DC chart

+
+ The GretagMacbeth Eye-One Pro Scan Target 1.4 can also be used:
+
+ Eye-One Scan Target 1.4

+
Also supported is the HutchColor @@ -965,22 +989,28 @@ - HCT :
-
- HutchColor HCT

-
-
- and Christophe - M�tairie's Digital TargeT 003 and Christophe - M�tairie's Digital Target - 4 :
-
- CMP_DT_003

-
+ + + + HCT :
+
+ HutchColor HCT

+
+
+ and Christophe + M�tairie's Digital TargeT 003, Christophe + M�tairie's Digital Target - 4 , and Christophe + M�tairie's Digital Target - 7:
+
+ CMP_DT_003

+
and the LaserSoft @@ -1041,25 +1071,28 @@ - Imaging DCPro Target:
-
- LaserSoft DCPro
- Target

-
- The Datacolor SpyderCheckr:
-
- Datacolor
- SpyderCheckr

-
- The Datacolor SpyderCheckr24:
-
-

-
- One of the QPcard's:
- :
+
+ LaserSoft DCPro
+ Target

+
+ The Datacolor SpyderCheckr:
+
+ Datacolor
+ SpyderCheckr

+
+ The Datacolor SpyderCheckr24:
+
+

+
+ One of the QPcard's:
+ QPcard @@ -1114,7 +1147,10 @@ - 201: : QPcard @@ -1169,86 +1205,89 @@ href="http://www.qpcard.com/en_b2c/color-reference-cards/instant-camera-raw-prof - 202:
-
- QPCard201

-
-

Taking readings from a scanner or camera
-

- 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 scanin -p 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.
-
- 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).
-
- 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 scanin tool needs to be given - a template .cht 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.
-
-

For an IT8.7/2 chart, this is the ref/it8.cht 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 here.
- NOTE that the reference file for the IT8.7/2 chart supplied with Monaco EZcolor 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.)
-
- For the ColorChecker 24 patch chart, the ref/ColorChecker.cht file - should be used, and there is also a ref/ColorChecker.cie 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 ref/ColorChecker.ti2:
- chartread -n - ColorChecker.ti2
- Note that due to the small number of patches, a profile created - from such a chart is not likely to be very detailed.
-
- For the ColorChecker DC chart, the ref/ColorCheckerDC.cht file should be used, and - there will be a ColorCheckerDC reference file supplied by - X-Rite/GretagMacbeth with the chart.
-
- 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.
- A limited CIE reference file is available from X-Rite here, - but it is not in the usual CGATS format. To convert it to a CIE - reference file useful for scanin, - you will need to edit the X-Rite file using a plain text editor, - first deleting everything before the line starting with "A1" and + + + + 202:
+
+ QPCard201

+
+

Taking readings from a scanner or camera
+

+ 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 scanin -p 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.
+
+ 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).
+
+ 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 scanin tool needs to be given + a template .cht 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.
+
+

For an IT8.7/2 chart, this is the ref/it8.cht 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 here.
+ NOTE that the reference file for the IT8.7/2 chart supplied with Monaco EZcolor 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.)
+
+ For the ColorChecker 24 patch chart, the ref/ColorChecker.cht file + should be used, and there is also a ref/ColorChecker.cie 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 ref/ColorChecker.ti2:
+    chartread -n + ColorChecker.ti2
+ Note that due to the small number of patches, a profile created + from such a chart is not likely to be very detailed.
+
+ For the ColorChecker DC chart, the ref/ColorCheckerDC.cht file should be used, and + there will be a ColorCheckerDC reference file supplied by + X-Rite/GretagMacbeth with the chart.
+
+ 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.
+ A limited CIE reference file is available from X-Rite here, + but it is not in the usual CGATS format. To convert it to a CIE + reference file useful for scanin, + you will need to edit the X-Rite file using a plain text editor, + first deleting everything before the line starting with "A1" and everything after "N10", then prepending this @@ -1308,92 +1347,108 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t - header, and appending this footer, - 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.
- 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,
- then you may - need to convert the reference information from spectral ColorCheckerSG.txt file to CIE - value ColorCheckerSG.cie - reference file, follow the following steps:
-      txt2ti3 - ColorCheckerSG.txt ColorCheckerSG
-      spec2cie - ColorCheckerSG.ti3 ColorCheckerSG.cie
-
- For the Eye-One Pro Scan Target 1.4 chart, the ref/i1_RGB_Scan_1.4.cht - 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 ref/i1_RGB_Scan_1.4.ti2:
-     chartread -n - i1_RGB_Scan_1.4
- and then rename the resulting i1_RGB_Scan_1.4.ti3 - file to i1_RGB_Scan_1.4.cie
-
- For the HutchColor HCT chart, the ref/Hutchcolor.cht - file should be used, and the reference .txt file downloaded from the HutchColor website.
-
- For the Christophe M�tairie's Digital TargeT 003 chart with 285 - patches, the ref/CMP_DT_003.cht - file should be used, and the cie reference files come with the chart.
-
- For the Christophe M�tairie's Digital Target-4 chart with 570 - patches, the ref/CMP_Digital_Target-4.cht - file should be used, and the cie reference files come with the chart.
-
- For the LaserSoft DCPro chart, the ref/LaserSoftDCPro.cht file should be used, and - reference .txt file - downloaded from the Silverfast - website.
-
- For the Datacolor SpyderCheckr, the ref/SpyderChecker.cht file should be used, and a - reference ref/SpyderChecker.cie - file made from measuring a sample chart is also available. - Alternately you could create your own reference file by - transcribing the values - on the Datacolor website.
-
- For the Datacolor SpyderCheckr, the ref/SpyderChecker24.cht file should be used, and a + + + + header, and appending this footer, + making sure there are no blank lines inserted in the process. Name + the resulting file ColorCheckerSG.cie.
+ 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.
+ If you do happen to have access to a more comprehensive instrument + measurement of the ColorChecker SG, or you have measured it + yourself using chart reading software other than ArgyllCMS, then + you may need to + convert the reference information from spectral only ColorCheckerSG.txt file to CIE + value ColorCheckerSG.cie + reference file, follow the following steps:
+      txt2ti3 + ColorCheckerSG.txt ColorCheckerSG
+      spec2cie + ColorCheckerSG.ti3 ColorCheckerSG.cie
+
+ For the Eye-One Pro Scan Target 1.4 chart, the ref/i1_RGB_Scan_1.4.cht + 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 ref/i1_RGB_Scan_1.4.ti2:
+     chartread -n + i1_RGB_Scan_1.4
+ and then rename the resulting i1_RGB_Scan_1.4.ti3 + file to i1_RGB_Scan_1.4.cie
+
+ For the HutchColor HCT chart, the ref/Hutchcolor.cht + file should be used, and the reference .txt file downloaded from the HutchColor website.
+
+ For the Christophe M�tairie's Digital TargeT 003 chart with 285 + patches, the ref/CMP_DT_003.cht + file should be used, and the cie reference files come with the chart.
+
+ For the Christophe M�tairie's Digital Target-4 chart with 570 + patches, the ref/CMP_Digital_Target-4.cht + file should be used, and the cie reference files come with the chart.
+
+ For the Christophe M�tairie's Digital Target-7 chart with 570 + patches, the ref/CMP_Digital_Target-7.cht + file should be used, and the spectral .txt file should be + converted to a cie reference file:
+     txt2ti3 + DT7_XXXXX_Spectral.txt temp
+     spec2cie temp.ti3 + DT7_XXXXX.cie
+
+ For the LaserSoft DCPro chart, the ref/LaserSoftDCPro.cht file should be used, and + reference .txt file + downloaded from the Silverfast + website.
+
+ For the Datacolor SpyderCheckr, the ref/SpyderChecker.cht file should be used, and a + reference ref/SpyderChecker.cie + file made from measuring a sample chart is also available. + Alternately you could create your own reference file by + transcribing the values + on the Datacolor website.
+
+ For the Datacolor SpyderCheckr, the ref/SpyderChecker24.cht file should be used, and a reference ref/SpyderChecker24.cie - file made from measuring a sample chart is also available. - Alternately you could create your own reference file by - transcribing the values - on the Datacolor website.
-
- For the QPCard 201, the ref/QPcard_201.cht - file should be used, and a reference ref/QPcard_201.cie file made from measuring a - sample chart is also available.
-
- For the QPCard 202, the ref/QPcard_202.cht - file should be used, and a reference ref/QPcard_202.cie file made from measuring a - sample chart is also available.
-

-
- For any other type of chart, a chart recognition template file will - need to be created (this is beyond the scope of the current + + + + file made from measuring a sample chart is also available. + Alternately you could create your own reference file by + transcribing the values + on the Datacolor website.
+
+ For the QPCard 201, the ref/QPcard_201.cht + file should be used, and a reference ref/QPcard_201.cie file made from measuring a + sample chart is also available.
+
+ For the QPCard 202, the ref/QPcard_202.cht + file should be used, and a reference ref/QPcard_202.cie file made from measuring a + sample chart is also available.
+

+
+ 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 .cht_format @@ -1453,402 +1508,405 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t - documentation).
-
- To create the scanner .ti3 file, run the scanin tool as - follows (assuming an IT8 chart is being used):
-
- scanin -v scanner.tif It8.cht It8ref.txt
-
- "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 "scanner.ti3".
-
- scanin 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. -
-
- 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 -dipn - and examine the diag.tif - 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 -F parameters. The fiducial marks should - be listed in a clockwise direction starting at the top left.
-

Creating a scanner or camera input profile

- 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.
-
- 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.
-
- If the purpose of the input profile is to use it as a substitute for - a colorimeter, then the -u 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.
-
- To create a matrix/shaper profile, the following suffices:
-
- colprof -v - -D"Scanner A" - -qm -as scanner
-
- For an XYZ PCS LUT based profile then the following would be used:
-
- colprof -v - -D"Scanner A" -qm - -ax scanner
-
- For the purposes of a poor mans colorimeter, the following would - generally be used:
-
- colprof -v - -D"Scanner A" -qm - -ax -u scanner
-
- 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.
-
- If profiling a camera in RAW 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 -u flag and avoid - setting the white point to that of the profile chart:
-
- colprof -v - -D"Camera" -qm - -am -u scanner
-
-
-

Profiling Printers
-

- 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.
-

Creating a print profile test chart

- The first step in profiling any output device, is to create a set of - device colorspace test values. The important parameters needed are:
-

What colorspace does the device use ?
How many test patches do I want to use/what paper size do I - want to use ?
What instrument am I going to use to read the patches ?
-
If it is a CMYK device, what is the total ink limit ?
-
What information do I already have about how the device - behaves ?

- 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 iccdump.
-
- 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.
-
- 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.
-
- 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.
-
- The documentation for the targen tool - lists a table - of paper sizes and number of patches for typical situations.
-
- 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.
-
- 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.
-
- 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.
-
- 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.
-
-
- 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%.
-
- The simplest approach is to make a set of test values that is - independent of the characteristics of the particular device:
-
- targen -v - -d2 -f1053 - PrinterA
-
- targen -v - -d4 -l260 - -f1053 PrinterB
-
- The number of patches chosen here happens to be right for an A4 - paper size being read using a Spectroscan instrument. See the table in the targen documentation for some other - suggested numbers.
-
- 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:
-
- targen -v - -d2 -f1053 - -c OldPrinterA PrinterA
-
- targen -v - -d4 -l260 - -f1053 -c - OldPrinterB PrinterB
-
-
- The output of targen 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.
-
-

Printing a print profile test chart
-
-

- 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.
-
- For an X-Rite DTP41, the following would be typical:
-
- printtarg -v - -i41 -pA4 - PrinterA
-
- For a Gretag Eye-One Pro, the following would be typical:
-
- printtarg -v - -ii1 -pA4 - PrinterA
-
- For using with a scanner as a colorimeter, the Gretag Spectroscan - layout is suitable, but the -s 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 targen, when using the printtarg -s flag, e.g. 1026 - patches for an A4R page, etc.) The following would be typical:
-
- printtarg -v - -s -iSS - -pA4R PrinterA
-
- printtarg 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 -s - flag is used, one or more PrinterA.cht files is created to allow the - scanin program to recognize the chart.
-
- To create TIFF raster files rather than PostScript, use the -t - flag.
-
- GSview is a good program to - use to check what the PostScript file will look like, without - actually printing it out. You could also use Photoshop or ImageMagick for this purpose.
-
- The last step is to print the chart out.
-
- 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 -e and -t - flags).
-
-

Reading a print test chart using an instrument

- Once the test chart has been printed, the color of the patches needs - to be read using a suitable instrument.
-
- 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 instruments - for a current list.
-
- The instrument needs to be connected to your computer before running - the chartread 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.
-
- If you run chartread so as to print - out its usage message (ie. by using a -? or -- - flags), then it will list any identified serial ports or USB - connected instruments, and their corresponding number for the -c option. By default, chartread will try to connect to the - first available USB instrument, or an instrument on the first serial - port.
-
- 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 -c option would also be - specified.
-
- e.g. for a Spectroscan on the second port:
-
- chartread -c2 - PrinterA
-
- For a DTP41 to the default serial port:
-
- chartread - PrinterA
-
- chartread will interactively - prompt you through the process of reading each sheet or strip. See chartread for more details on the - responses for each type of instrument. Continue with Creating a printer profile.
-
-

Reading a print test chart using a scanner or - camera
-

-
- 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.
-
- The main limitation of the scanner-as-colorimeter approach are:
-
- * The scanner dynamic range and/or precision may not match the - printers or what is required for a good profile.
- * The spectral interaction of the scanner test chart and printer - test chart with the scanner spectral response can cause color - errors.
- * Spectral differences caused by different black amounts in the - print test chart can cause color errors.
- * The scanner reference chart gamut may be much smaller than the - printers gamut, making the scanner profile too inaccurate to be - useful.
-
- 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.
-
- The end result is often a profile that has a noticeable color cast, - compared to a profile created using a colorimeter or spectrometer.
-
-
- It is assumed that you have created a scanner or camera profile - following the procedure - 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 -u - flag to avoid clipping scanned value whiter than the input - calibration chart.
-
- Scan or photograph your printer chart (or charts) on the scanner or + + + + documentation).
+
+ To create the scanner .ti3 file, run the scanin tool as + follows (assuming an IT8 chart is being used):
+
+ scanin -v scanner.tif It8.cht It8ref.txt
+
+ "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 "scanner.ti3".
+
+ scanin 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. +
+
+ 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 -dipn + and examine the diag.tif + 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 -F parameters. The fiducial marks should + be listed in a clockwise direction starting at the top left.
+

Creating a scanner or camera input profile

+ 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.
+
+ 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.
+
+ If the purpose of the input profile is to use it as a substitute for + a colorimeter, then the -u 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.
+
+ To create a matrix/shaper profile, the following suffices:
+
+ colprof -v + -D"Scanner A" + -qm -as scanner
+
+ For an XYZ PCS LUT based profile then the following would be used:
+
+ colprof -v + -D"Scanner A" -qm + -ax scanner
+
+ For the purposes of a poor mans colorimeter, the following would + generally be used:
+
+ colprof -v + -D"Scanner A" -qm + -ax -u scanner
+
+ 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.
+
+ If profiling a camera in RAW 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 -u flag and avoid + setting the white point to that of the profile chart:
+
+ colprof -v + -D"Camera" -qm + -am -u scanner
+
+
+

Profiling Printers
+

+ 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.
+

Creating a print profile test chart

+ The first step in profiling any output device, is to create a set of + device colorspace test values. The important parameters needed are:
+

What colorspace does the device use ?
How many test patches do I want to use/what paper size do I + want to use ?
What instrument am I going to use to read the patches ?
+
If it is a CMYK device, what is the total ink limit ?
+
What information do I already have about how the device + behaves ?

+ 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 iccdump.
+
+ 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.
+
+ 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.
+
+ 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.
+
+ The documentation for the targen tool + lists a table + of paper sizes and number of patches for typical situations.
+
+ 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.
+
+ 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.
+
+ 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.
+
+ 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.
+
+
+ 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%.
+
+ The simplest approach is to make a set of test values that is + independent of the characteristics of the particular device:
+
+ targen -v + -d2 -f1053 + PrinterA
+
+ targen -v + -d4 -l260 + -f1053 PrinterB
+
+ The number of patches chosen here happens to be right for an A4 + paper size being read using a Spectroscan instrument. See the table in the targen documentation for some other + suggested numbers.
+
+ 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:
+
+ targen -v + -d2 -f1053 + -c OldPrinterA PrinterA
+
+ targen -v + -d4 -l260 + -f1053 -c + OldPrinterB PrinterB
+
+
+ The output of targen 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.
+
+

Printing a print profile test chart
+
+

+ 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.
+
+ For an X-Rite DTP41, the following would be typical:
+
+ printtarg -v + -i41 -pA4 + PrinterA
+
+ For a Gretag Eye-One Pro, the following would be typical:
+
+ printtarg -v + -ii1 -pA4 + PrinterA
+
+ For using with a scanner as a colorimeter, the Gretag Spectroscan + layout is suitable, but the -s 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 targen, when using the printtarg -s flag, e.g. 1026 + patches for an A4R page, etc.) The following would be typical:
+
+ printtarg -v + -s -iSS + -pA4R PrinterA
+
+ printtarg 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 -s + flag is used, one or more PrinterA.cht files is created to allow the + scanin program to recognize the chart.
+
+ To create TIFF raster files rather than PostScript, use the -t + flag.
+
+ GSview is a good program to + use to check what the PostScript file will look like, without + actually printing it out. You could also use Photoshop or ImageMagick for this purpose.
+
+ The last step is to print the chart out.
+
+ 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 -e and -t + flags).
+
+

Reading a print test chart using an instrument

+ Once the test chart has been printed, the color of the patches needs + to be read using a suitable instrument.
+
+ 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 instruments + for a current list.
+
+ The instrument needs to be connected to your computer before running + the chartread 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.
+
+ If you run chartread so as to print + out its usage message (ie. by using a -? or -- + flags), then it will list any identified serial ports or USB + connected instruments, and their corresponding number for the -c option. By default, chartread will try to connect to the + first available USB instrument, or an instrument on the first serial + port.
+
+ 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 -c option would also be + specified.
+
+ e.g. for a Spectroscan on the second port:
+
+ chartread -c2 + PrinterA
+
+ For a DTP41 to the default serial port:
+
+ chartread + PrinterA
+
+ chartread will interactively + prompt you through the process of reading each sheet or strip. See chartread for more details on the + responses for each type of instrument. Continue with Creating a printer profile.
+
+

Reading a print test chart using a scanner or + camera
+

+
+ 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.
+
+ The main limitation of the scanner-as-colorimeter approach are:
+
+ * The scanner dynamic range and/or precision may not match the + printers or what is required for a good profile.
+ * The spectral interaction of the scanner test chart and printer + test chart with the scanner spectral response can cause color + errors.
+ * Spectral differences caused by different black amounts in the + print test chart can cause color errors.
+ * The scanner reference chart gamut may be much smaller than the + printers gamut, making the scanner profile too inaccurate to be + useful.
+
+ 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.
+
+ The end result is often a profile that has a noticeable color cast, + compared to a profile created using a colorimeter or spectrometer.
+
+
+ It is assumed that you have created a scanner or camera profile + following the procedure + 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 -u + flag to avoid clipping scanned value whiter than the input + calibration chart.
+
+ Scan or photograph your printer chart (or charts) on the scanner or camera previously profiled. The @@ -1909,97 +1967,100 @@ 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.
-
- I will assume the resulting scan/photo input file is called PrinterB.tif (or PrinterB1.tif, PrinterB2.tif 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.
-
- The scanner recognition files created when printtarg was run is assumed to - be called PrinterB.cht. - Using the scanner profile created previously (assumed to be called scanner.icm), the printer test - chart scan patches are converted to CIE values using the scanin tool:
-
- scanin -v -c PrinterB.tif - PrinterB.cht scanner.icm PrinterB
-
- If there were multiple test chart pages, the results would be - accumulated page by page using the -ca - option, ie., if there were 3 pages:
-
- scanin -v -c PrinterB1.tif - PrinterB1.cht scanner.icm PrinterB
- scanin -v -ca PrinterB2.tif - PrinterB2.cht scanner.icm PrinterB
- scanin -v -ca PrinterB3.tif - PrinterB3.cht scanner.icm PrinterB
-
- Now that the PrinterB.ti3 - data has been obtained, the profile continue in the next section - with Creating a printer profile.
-
- 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 -dipn - and examine the diag.tif - diagnostic file.
-

Creating a printer profile
-

- 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.
-
- Where the resulting profile will be used conventionally (ie. using collink -s, - or cctiff 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 colprof -S - 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.
-
- "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.
-
- 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.
-
- 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. collink + + + + scanner or camera must be configured and used exactly the same + as it was when it was profiled.
+
+ I will assume the resulting scan/photo input file is called PrinterB.tif (or PrinterB1.tif, PrinterB2.tif 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.
+
+ The scanner recognition files created when printtarg was run is assumed to + be called PrinterB.cht. + Using the scanner profile created previously (assumed to be called scanner.icm), the printer test + chart scan patches are converted to CIE values using the scanin tool:
+
+ scanin -v -c PrinterB.tif + PrinterB.cht scanner.icm PrinterB
+
+ If there were multiple test chart pages, the results would be + accumulated page by page using the -ca + option, ie., if there were 3 pages:
+
+ scanin -v -c PrinterB1.tif + PrinterB1.cht scanner.icm PrinterB
+ scanin -v -ca PrinterB2.tif + PrinterB2.cht scanner.icm PrinterB
+ scanin -v -ca PrinterB3.tif + PrinterB3.cht scanner.icm PrinterB
+
+ Now that the PrinterB.ti3 + data has been obtained, the profile continue in the next section + with Creating a printer profile.
+
+ 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 -dipn + and examine the diag.tif + diagnostic file.
+

Creating a printer profile
+

+ 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.
+
+ Where the resulting profile will be used conventionally (ie. using collink -s, + or cctiff 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 colprof -S + 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.
+
+ "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.
+
+ 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.
+
+ 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. collink -g or -G), then @@ -2061,82 +2122,94 @@ then - it can save considerable processing time and space if the -b flag is - used, and the -S flag not used.
-
- For an RGB printer intended to print RGB originals, the following - might be a typical profile usage:
-
- colprof -v - -D"Printer A" -qm - -S sRGB.icm - -cmt -dpp - PrinterA
-
- or if you intent to print from Fogra, SWOP or other standard CMYK - style originals:
-
- colprof -v - -D"Printer A" -qm - -S - fogra39l.icm -cmt -dpp PrinterA
-
- If you know what colorspace your originals are in, use that as the - argument to -S.
-
- If your viewing environment for the display and print doesn't match - the ones implied by the -cmt and -dpp options, leave them out, and - evaluate what, if any appearance transformation is appropriate for - your environment at a later stage.
-
- 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. -

Choosing a black generation curve (and other - CMYK printer options)
-

- 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 colprof for the - details of the options.
-
- Note 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.
-
- 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.
-
- If you want to experiment with the various black generation - parameters, then it might be a good idea to create a preliminary - profile (using -ql -b -no, +
+ For an RGB printer intended to print RGB originals, the following + might be a typical profile usage:
+
+ colprof -v + -D"Printer A" -qm + -S sRGB.icm + -cmt -dpp + PrinterA
+
+ or if you intent to print from Fogra, SWOP or other standard CMYK + style originals:
+
+ colprof -v + -D"Printer A" -qm + -S + fogra39l.icm -cmt -dpp PrinterA
+
+ If you know what colorspace your originals are in, use that as the + argument to -S.
+
+ If your viewing environment for the display and print doesn't match + the ones implied by the -cmt and -dpp options, leave them out, and + evaluate what, if any appearance transformation is appropriate for + your environment at a later stage.
+
+ A fallback to using a specific source profile/gamut is to use a + general compression percentage as a gamut mapping:
+
+ colprof -v + -D"Printer A" -qm + -S 20 -cmt -dpp PrinterA
+
+ 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. +

Choosing a black generation curve (and other + CMYK printer options)
+

+ 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 colprof for the + details of the options.
+
+ Note 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.
+
+ 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.
+
+ If you want to experiment with the various black generation + parameters, then it might be a good idea to create a preliminary + profile (using -ql -b -no, -ni and no -S), @@ -2196,406 +2269,409 @@ then - and then used xicclu to explore the - effect of the parameters.
-
- For instance, say we have our CMYK .ti3 file PrinterB.ti3. First we make a - preliminary profile called PrinterBt:
-
- copy PrinterB.ti3 PrinterBt.ti3 (Use - "cp" on Linux or OSX of course.)
- colprof -v - -qm -b -cmt -dpp - PrinterBt
-
- 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%:
-
- xicclu -g -kz -l290 -fif -ir PrinterBt.icm
-
- Which might be a graph something like this:
-
- Graph of CMYK neutral axis with minimum K

Graph of CMYK neutral axis with minimum K

-
- 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.
-
- Then let's see what the maximum black level down the neutral axis - can be:
-
- xicclu -g -kx -l290 -fif -ir PrinterBt.icm
-
- Which might be a graph something like this:
-
- Graph of CMYK neutral axis with maximum K

Graph of CMYK neutral axis with maximum K

-
- 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.
-
- Any K curve we specify must lie between the black curves of the - above two graphs.
-
- 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.
-
- -k parameters

-
-
- 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:
-
- xicclu -g -kp 0 0 .93 .87 1.0 -l290 -fif -ir PrinterBt.icm
-
- Graph of CMYK neutral axis with kp 0 0 1.0 1.0 1.0 -l290

Graph of CMYK neutral axis with kp 0 0 1.0 1.0 1.0 -l290

-
- 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:
-
- xicclu -g -kp 0 0 .93 .87 - 0.65 -l290 -fif -ir PrinterBt.icm
-
- Graph of CMYK neutral axis with -kp 0 .05 1 .9 1 -l290

Graph of CMYK neutral axis with -kp 0 .05 1 .9 1 -l290

-
- This looks just about perfect, so the the curve parameters can now - be used to generate our real profile:
-
- colprof -v - -D"Printer B" -qm - -kp 0 0 .93 - .87 0.65 -S sRGB.icm -cmt - -dpp PrinterB
-
- and the resulting B2A table black curve can be checked using xicclu:
-
- xicclu -g -fb -ir PrinterB.icm
-
- sadsadas

-
-
-

- Examples of other inkings:
-
- A smoothed zero black inking:
-
- xicclu -g -kp 0 .7 .93 .87 - 1.0 -l290 -fif -ir PrinterBt.icm
-
- sadsadas

-
- A low black inking:
-
- xicclu -g -kp 0 0 .93 .87 - 0.15 -l290 -fif -ir PrinterBt.icm
-
- sadsadas

-
-
- A high black inking:
-
- xicclu -g -kp 0 0 .93 .87 - 1.2 -l290 -fif -ir PrinterBt.icm
-
- sadsadas

-
- -

Overriding the ink limit
-

- Normally the total ink limit will be read from the PrinterB.ti3 file, and will be - set at a level 10% lower than the number used in creating the test - chart values using targen -l. If you - want to override this with a lower limit, then use the -l flag.
-
- colprof -v - -D"Printer B" -qm - -S sRGB.icm - -cmt -dpp - -kr -l290 - PrinterB
-
- Make sure you check the delta E report at the end of the profile - creation, to see if the profile is behaving reasonably.
-
- One way of checking that your ink limit is not too high, is to use "xicc -fif -ia" to check, by - setting different ink limits using the -l option, feeding Lab = 0 0 0 into it, and checking - the resulting black point. Starting with the ink limit used - with targen 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.
-
-

Calibrating Printers
-

- Profiling creates a - description of how a device behaves, while calibration on the other hand is - intended to change - 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.
-
- NOTE: 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.
-

Calibrated print workflows

- There are two main workflows that printer calibration curves can be - applied to:
-
- Workflow with native calibration - capability:
-
- 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 printcal. - The calibration is then installed into the printer. Subsequent - profiling will be performed on the calibrated 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.)
-
- Workflow without native calibration - capability:
-
- 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 printcal,. During the subsequent - profiling, the - calibration curves will need to be applied to the profile test chart - in the process of using printtarg. - 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 cctiff to apply color profiles and calibration, OR by creating a version of the - profile that has had the calibration curves incorporated into it - using the applycal tool. - The latter is useful when some CMM (color management module) other - than cctiff is being used.
-
- 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. - -

Creating a print calibration test chart

- 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.
-
- 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.
-
- For instance, to create a 50 steps per channel calibration test - chart for our RGB and CMYK devices, the following would be - sufficient:
-
- targen -v - -d2 -s50 - -e3 -f0 PrinterA_c
-
- targen -v - -d4 -s50 - -e4 -f0 PrinterB_c
-
- For an outline of how to then print and read the resulting test - chart, see Printing a print - profile test chart, and Reading - a print test chart using an instrument. 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.
-
- NOTE that if you are - calibrating a raw printer driver, and there is considerable dot - gain, then you may want to use the -p - 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 -p.
-

Creating a printer calibration
-

- The printcal tool turns a calibration - chart .ti3 file into a .cal 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.)
-
- 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.
-
- 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 -x# percent option, where # represents the choice of - channel this will be applied to. The parameter is the percentage of - device maximum.
-
- The minimum level defaults to 0, but can be overridden using the -n# deltaE 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.
-
- 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 -t# percent - 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.
-
- Once a device has been calibrated, it can be re-calibrated to the - same aim target.
-
- Verification uses a calibration test chart printed through the - calibration, and compares the achieved response to the aim target.
-
- The simplest possible way of creating the PrinterA.cal file is:
-
- printcal -i PrinterA_c
-
- For more detailed information, you can add the -v and -p flags:
-
- printcal -v -p -i PrinterB_c
-
- (You will need to select the plot window and hit a key to advance - past each plot).
-
- For re-calibration, the name of the previous calibration file will - need to be supplied, and a new calibration
- file will be created:
-
- printcal -v -p -r PrinterB_c_old - PrinterB_c_new
-
- Various aim points are normally set automatically by printcal, but these can be - overridden using the -x, -n and -t - options. e.g. say we wanted to set the maximum ink for Cyan to 80% - and Black to 95%, we might use:
-
- printcal -v -p -i -xc 80 - -xk 95 PrinterB_c
-
- -

Using a printer calibration

- The resulting calibration curves can be used with the following - other Argyll tools:
-
+ + + + and then used xicclu to explore the + effect of the parameters.
+
+ For instance, say we have our CMYK .ti3 file PrinterB.ti3. First we make a + preliminary profile called PrinterBt:
+
+ copy PrinterB.ti3 PrinterBt.ti3 (Use + "cp" on Linux or OSX of course.)
+ colprof -v + -qm -b -cmt -dpp + PrinterBt
+
+ 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%:
+
+ xicclu -g -kz -l290 -fif -ir PrinterBt.icm
+
+ Which might be a graph something like this:
+
+ Graph of CMYK neutral axis with minimum K

+
+ 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.
+
+ Then let's see what the maximum black level down the neutral axis + can be:
+
+ xicclu -g -kx -l290 -fif -ir PrinterBt.icm
+
+ Which might be a graph something like this:
+
+ Graph of CMYK neutral axis with maximum K

+
+ 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.
+
+ Any K curve we specify must lie between the black curves of the + above two graphs.
+
+ 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.
+
+ -k parameters

+
+
+ 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:
+
+ xicclu -g -kp 0 0 .93 .87 1.0 -l290 -fif -ir PrinterBt.icm
+
+ Graph of CMYK neutral axis with kp 0 0 1.0 1.0 1.0 -l290

+
+ 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:
+
+ xicclu -g -kp 0 0 .93 .87 + 0.65 -l290 -fif -ir PrinterBt.icm
+
+ Graph of CMYK neutral axis with -kp 0 .05 1 .9 1 -l290

+
+ This looks just about perfect, so the the curve parameters can now + be used to generate our real profile:
+
+ colprof -v + -D"Printer B" -qm + -kp 0 0 .93 + .87 0.65 -S sRGB.icm -cmt + -dpp PrinterB
+
+ and the resulting B2A table black curve can be checked using xicclu:
+
+ xicclu -g -fb -ir PrinterB.icm
+
+ sadsadas

+
+
+

+ Examples of other inkings:
+
+ A smoothed zero black inking:
+
+ xicclu -g -kp 0 .7 .93 .87 + 1.0 -l290 -fif -ir PrinterBt.icm
+
+ sadsadas

+
+ A low black inking:
+
+ xicclu -g -kp 0 0 .93 .87 + 0.15 -l290 -fif -ir PrinterBt.icm
+
+ sadsadas

+
+
+ A high black inking:
+
+ xicclu -g -kp 0 0 .93 .87 + 1.2 -l290 -fif -ir PrinterBt.icm
+
+ sadsadas

+
+ +

Overriding the ink limit
+

+ Normally the total ink limit will be read from the PrinterB.ti3 file, and will be + set at a level 10% lower than the number used in creating the test + chart values using targen -l. If you + want to override this with a lower limit, then use the -l flag.
+
+ colprof -v + -D"Printer B" -qm + -S sRGB.icm + -cmt -dpp + -kr -l290 + PrinterB
+
+ Make sure you check the delta E report at the end of the profile + creation, to see if the profile is behaving reasonably.
+
+ One way of checking that your ink limit is not too high, is to use "xicc -fif -ia" to check, by + setting different ink limits using the -l option, feeding Lab = 0 0 0 into it, and checking + the resulting black point. Starting with the ink limit used + with targen 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.
+
+

Calibrating Printers
+

+ Profiling creates a + description of how a device behaves, while calibration on the other hand is + intended to change + 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.
+
+ NOTE: 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.
+

Calibrated print workflows

+ There are two main workflows that printer calibration curves can be + applied to:
+
+ Workflow with native calibration + capability:
+
+ 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 printcal. + The calibration is then installed into the printer. Subsequent + profiling will be performed on the calibrated 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.)
+
+ Workflow without native calibration + capability:
+
+ 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 printcal,. During the subsequent + profiling, the + calibration curves will need to be applied to the profile test chart + in the process of using printtarg. + 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 cctiff to apply color profiles and calibration, OR by creating a version of the + profile that has had the calibration curves incorporated into it + using the applycal tool. + The latter is useful when some CMM (color management module) other + than cctiff is being used.
+
+ 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. + +

Creating a print calibration test chart

+ 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.
+
+ 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.
+
+ For instance, to create a 50 steps per channel calibration test + chart for our RGB and CMYK devices, the following would be + sufficient:
+
+ targen -v + -d2 -s50 + -e3 -f0 PrinterA_c
+
+ targen -v + -d4 -s50 + -e4 -f0 PrinterB_c
+
+ For an outline of how to then print and read the resulting test + chart, see Printing a print + profile test chart, and Reading + a print test chart using an instrument. 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.
+
+ NOTE that if you are + calibrating a raw printer driver, and there is considerable dot + gain, then you may want to use the -p + 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 -p.
+

Creating a printer calibration
+

+ The printcal tool turns a calibration + chart .ti3 file into a .cal 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.)
+
+ 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.
+
+ 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 -x# percent option, where # represents the choice of + channel this will be applied to. The parameter is the percentage of + device maximum.
+
+ The minimum level defaults to 0, but can be overridden using the -n# deltaE 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.
+
+ 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 -t# percent + 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.
+
+ Once a device has been calibrated, it can be re-calibrated to the + same aim target.
+
+ Verification uses a calibration test chart printed through the + calibration, and compares the achieved response to the aim target.
+
+ The simplest possible way of creating the PrinterA.cal file is:
+
+ printcal -i PrinterA_c
+
+ For more detailed information, you can add the -v and -p flags:
+
+ printcal -v -p -i PrinterB_c
+
+ (You will need to select the plot window and hit a key to advance + past each plot).
+
+ For re-calibration, the name of the previous calibration file will + need to be supplied, and a new calibration
+ file will be created:
+
+ printcal -v -p -r PrinterB_c_old + PrinterB_c_new
+
+ Various aim points are normally set automatically by printcal, but these can be + overridden using the -x, -n and -t + options. e.g. say we wanted to set the maximum ink for Cyan to 80% + and Black to 95%, we might use:
+
+ printcal -v -p -i -xc 80 + -xk 95 PrinterB_c
+
+ +

Using a printer calibration

+ The resulting calibration curves can be used with the following + other Argyll tools:
+
    printtarg     To apply @@ -2664,7 +2740,10 @@ chart, - and/or to have it included in .ti3 file.
+ + + + and/or to have it included in .ti3 file.
    cctiff         To apply @@ -2733,7 +2812,10 @@ an - image file.
+ + + + image file.
    applycal     @@ -2794,7 +2876,10 @@ an - To incorporate calibration into an ICC profile.
+ + + + To incorporate calibration into an ICC profile.
    chartread   To override @@ -2863,349 +2948,346 @@ a - profile chart.
-
-
- In a workflow with native - calibration capability, the calibration curves would be used with - printarg during subsequent profiling - so that any ink limit calculations will reflect final device values, - while not otherwise using the calibration within the ICC workflow:
-
-     printtarg -v -ii1 - -pA4 -I - PrinterA_c.cal PrinterA
-
- 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).
-
-
- In a workflow without - native calibration capability, the calibration curves would be used - with printarg to apply - the calibration to the test patch samples during subsequent profiling, as well as embedding - it in the resulting .ti3 to allow all the tools to be able to - compute final device value ink limits:
-
-     printtarg -v -ii1 - -pA4 -K - PrinterA_c.cal PrinterA
-
- To apply calibration to an ICC profile, so that a calibration - unaware CMM can be used:
-
-     applycal PrinterA.cal PrinterA.icm PrinterA_cal.icm
-
- To apply color management and calibration to a raster image:
-
-     cctiff - Source.icm PrinterA.icm PrinterA_c.cal - infile.tif outfile.tif
-
- or
-
-     cctiff - Source.icm PrinterA_c.icm - infile.tif outfile.tif
-
- [ Note that cctiff will also process JPEG raster images. ]
-
- Another useful tool is synthcal, that - allows creating linear or synthetic calibration files for disabling - calibration or testing.
- Similarly, fakeread also supports - applying calibration curves and embedding them in the resulting .ti3 - file
-
- If you want to create a pre-conditioning profile for use with targen -c, then use the PrinterA.icm - profile, NOT PrinterA_c.icm that has calibration curves - applied.
-

How profile ink limits are handled when - calibration is being used.

- 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 'targ' text tag, by way of the printtarg -I or -K 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.
-
-
-

Linking Profiles

- 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.
-
- The overall process is to link the input space and output space - profiles using collink, 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.
-
- Three examples will be given here, showing the three different modes - than collink supports.
-
- In simple mode, the two profiles are - linked together in a similar fashion to other CMMs 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:
-
- collink -v - -qm -s -ip -op - SouceProfile.icm DestinationProfile.icm Source2Destination.icm
-
-
- In gamut mapping mode, 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 collink. - 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:
-
- collink -v - -qm -g -ip -cmt - -dpp MonitorSouceProfile.icm - DestinationProfile.icm Source2Destination.icm
-
- [ If your viewing environment for the display and print doesn't - match the ones implied by the -cmt and - -dpp options, leave them out, and - evaluate what, if any appearance transformation is appropriate for - your environment at a later stage. ]
-
- In inverse output table gamut mapping mode, - 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 collink. - In addition, the B2A table is not - 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:
-
- For a CLUT table based RGB printer destination profile, the - following would be appropriate:
-
- collink -v - -qm -G -ip -cmt - -dpp MonitorSouceProfile.icm - RGBDestinationProfile.icm Source2Destination.icm
-
- 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:
-
- collink -v - -qm -G -ip -cmt - -dpp -l250 - -kr MonitorSouceProfile.icm - CMYKDestinationProfile.icm Source2Destination.icm
-
- Note that you should set the source (-c) - and destination (-d) viewing conditions - for the type of device the profile represents, and the conditions - under which it will be viewed.
-
-

Image dependent gamut mapping using device - links
-

- When images are stored in large gamut colorspaces (such as. L*a*b*, - ProPhoto, scRGB etc.), then using the colorspace gamut as the source - gamut for gamut mapping is generally a bad idea, as it leads to - overly compressed and dull images. The correct approach is to use a - source gamut that represents the gamut of the images themselves. - This can be created using tiffgamut, and an example workflow is as - follows:
-
- tiffgamut -f80 -pj -cmt ProPhoto.icm - image.tif
-
- collink -v - -qh -G image.gam -ip - -cmt -dpp - ProPhoto.icm RGBDestinationProfile.icm - Source2Destination.icm
-
- cctiff Source2Destination.icm - image.tif printfile.tif
-
- The printfile.tif is then send to the printer without color - management, (i.e. in the same way the printer characterization test - chart was printed), since it is in the printers native colorspace.
-
- You can adjust how conservatively the image gamut is preserved using - the tiffgamut -f parameter. Omitting it or using a larger value (up - to 100) preserves the color gradations of even the lesser used - colors, at the cost of compressing the gamut more.
- Using a smaller value will preserve the saturation of the most - popular colors, at the cost of not preserving the color gradations - of less popular colors.
-
- You can create a gamut that covers a set of source images by - providing more than one image file name to tiffgamut. This may be - more efficient for a group of related images, and ensures that - colors are transformed in exactly the same way for all of the - images.
-
- An alternative generating a gamut for a specific set of images, is - to use a general smaller gamut definition (i.e. the sRGB profile), - or a gamut that represents the typical range of colors you wish to - preserve.
-
- The arguments to collink should be appropriate for the output device - type - see the collink examples in the above section.
-

Soft Proofing Link

- 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:
-
- collink -v - -qm -G -ila -cpp - -dmt -t250 CMYKDestinationProfile.icm - MonitorProfile.icm SoftProof.icm
-
- 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.
-
- If your viewing environment for the display and print doesn't match - the ones implied by the -cpp and -dmt options, then either leave them out - or substitute values that do match your environment.
- -

Transforming colorspaces of raster files

- Although a device profile or device link profile may be useful with - other programs and systems, Argyll provides the tool cctiff for directly applying a device to - device transform to a TIFF or - JPEG 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 -i - 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.
-
- If a device link is to be used, the following is a typical example:
-
- cctiff Source2Destination.icm - infile.tif outfile.tif
- or
- cctiff Source2Destination.icm - infile.jpg outfile.jpg
-
-
- If a source and destination profile are to be used, the - following would be a typical example:
-
- cctiff -ip - SourceProfile.icm -ip DestinationProfile.icm - infile.tif outfile.tif
- or
- cctiff -ip - SourceProfile.icm -ip DestinationProfile.icm - infile.jpg outfile.jpg
-
-
-

Creating Video Calibration 3DLuts

- 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.
-
- To facilitate Video calibration of certain Video systems, ArgyllCMS - supports some 3DLut output options as part of collink.
-
- 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.
-

1) How to display test patches.
-

- 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 + + + + profile chart.
+
+
+ In a workflow with native + calibration capability, the calibration curves would be used with + printarg during subsequent profiling + so that any ink limit calculations will reflect final device values, + while not otherwise using the calibration within the ICC workflow:
+
+     printtarg -v -ii1 + -pA4 -I + PrinterA_c.cal PrinterA
+
+ 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).
+
+
+ In a workflow without + native calibration capability, the calibration curves would be used + with printarg to apply + the calibration to the test patch samples during subsequent profiling, as well as embedding + it in the resulting .ti3 to allow all the tools to be able to + compute final device value ink limits:
+
+     printtarg -v -ii1 + -pA4 -K + PrinterA_c.cal PrinterA
+
+ To apply calibration to an ICC profile, so that a calibration + unaware CMM can be used:
+
+     applycal PrinterA.cal PrinterA.icm PrinterA_cal.icm
+
+ To apply color management and calibration to a raster image:
+
+     cctiff Source.icm PrinterA.icm + PrinterA_c.cal infile.tif outfile.tif
+
+ or
+
+     cctiff Source.icm PrinterA_c.icm + infile.tif outfile.tif
+
+ [ Note that cctiff will also process JPEG raster images. ]
+
+ Another useful tool is synthcal, that + allows creating linear or synthetic calibration files for disabling + calibration or testing.
+ Similarly, fakeread also supports + applying calibration curves and embedding them in the resulting .ti3 + file
+
+ If you want to create a pre-conditioning profile for use with targen -c, then use the PrinterA.icm + profile, NOT PrinterA_c.icm that has calibration curves + applied.
+

How profile ink limits are handled when + calibration is being used.

+ 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 'targ' text tag, by way of the printtarg -I or -K 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.
+
+
+

Linking Profiles

+ 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.
+
+ The overall process is to link the input space and output space + profiles using collink, 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.
+
+ Three examples will be given here, showing the three different modes + than collink supports.
+
+ In simple mode, the two profiles are + linked together in a similar fashion to other CMMs 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:
+
+ collink -v + -qm -s -ip -op + SouceProfile.icm DestinationProfile.icm Source2Destination.icm
+
+
+ In gamut mapping mode, 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 collink. + 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:
+
+ collink -v + -qm -g -ip -cmt + -dpp MonitorSouceProfile.icm + DestinationProfile.icm Source2Destination.icm
+
+ [ If your viewing environment for the display and print doesn't + match the ones implied by the -cmt and + -dpp options, leave them out, and + evaluate what, if any appearance transformation is appropriate for + your environment at a later stage. ]
+
+ In inverse output table gamut mapping mode, + 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 collink. + In addition, the B2A table is not + 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:
+
+ For a CLUT table based RGB printer destination profile, the + following would be appropriate:
+
+ collink -v + -qm -G -ip -cmt + -dpp MonitorSouceProfile.icm + RGBDestinationProfile.icm Source2Destination.icm
+
+ 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:
+
+ collink -v + -qm -G -ip -cmt + -dpp -l250 + -kr MonitorSouceProfile.icm + CMYKDestinationProfile.icm Source2Destination.icm
+
+ Note that you should set the source (-c) + and destination (-d) viewing conditions + for the type of device the profile represents, and the conditions + under which it will be viewed.
+
+

Image dependent gamut mapping using device + links
+

+ When images are stored in large gamut colorspaces (such as. L*a*b*, + ProPhoto, scRGB etc.), then using the colorspace gamut as the source + gamut for gamut mapping is generally a bad idea, as it leads to + overly compressed and dull images. The correct approach is to use a + source gamut that represents the gamut of the images themselves. + This can be created using tiffgamut, and an example workflow is as + follows:
+
+ tiffgamut -f80 -pj -cmt ProPhoto.icm + image.tif
+
+ collink -v + -qh -G image.gam -ip + -cmt -dpp + ProPhoto.icm RGBDestinationProfile.icm Source2Destination.icm
+
+ cctiff Source2Destination.icm + image.tif printfile.tif
+
+ The printfile.tif is then send to the printer without color + management, (i.e. in the same way the printer characterization test + chart was printed), since it is in the printers native colorspace.
+
+ You can adjust how conservatively the image gamut is preserved using + the tiffgamut -f parameter. Omitting it or using a larger value (up + to 100) preserves the color gradations of even the lesser used + colors, at the cost of compressing the gamut more.
+ Using a smaller value will preserve the saturation of the most + popular colors, at the cost of not preserving the color gradations + of less popular colors.
+
+ You can create a gamut that covers a set of source images by + providing more than one image file name to tiffgamut. This may be + more efficient for a group of related images, and ensures that + colors are transformed in exactly the same way for all of the + images.
+
+ An alternative generating a gamut for a specific set of images, is + to use a general smaller gamut definition (i.e. the sRGB profile), + or a gamut that represents the typical range of colors you wish to + preserve.
+
+ The arguments to collink should be appropriate for the output device + type - see the collink examples in the above section.
+

Soft Proofing Link

+ 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:
+
+ collink -v + -qm -G -ila -cpp + -dmt -t250 CMYKDestinationProfile.icm + MonitorProfile.icm SoftProof.icm
+
+ 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.
+
+ If your viewing environment for the display and print doesn't match + the ones implied by the -cpp and -dmt options, then either leave them out + or substitute values that do match your environment.
+ +

Transforming colorspaces of raster files

+ Although a device profile or device link profile may be useful with + other programs and systems, Argyll provides the tool cctiff for directly applying a device to + device transform to a TIFF or + JPEG 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 -i + 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.
+
+ If a device link is to be used, the following is a typical example:
+
+ cctiff Source2Destination.icm + infile.tif outfile.tif
+ or
+ cctiff Source2Destination.icm + infile.jpg outfile.jpg
+
+
+ If a source and destination profile are to be used, the + following would be a typical example:
+
+ cctiff -ip + SourceProfile.icm -ip DestinationProfile.icm + infile.tif outfile.tif
+ or
+ cctiff -ip + SourceProfile.icm -ip DestinationProfile.icm + infile.jpg outfile.jpg
+
+
+

Creating Video Calibration 3DLuts

+ 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.
+
+ To facilitate Video calibration of certain Video systems, ArgyllCMS + supports some 3DLut output options as part of collink.
+
+ 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.
+

1) How to display test patches.
+

+ 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 @@ -3213,52 +3295,55 @@ a - 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.
-
- Another option is to use a ChromeCast - using the option "-dcc" in dispcal, dispread and dispwin. - Note that the ChromeCast as a test patch source is probably the - least accurate of your choices, since it up-samples the test - patch and transforms from RGB to YCC and back, but should be - accurate within � 1 bit. You may have to modify any firewall to - permit port 8081 to be accessed on your machine if it falls back to - the Default receiver (see installation - instructions for your platform). -

2) White point calibration & neutral axis calibration.

- 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:
-

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.
-
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 + + + + 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.
+
+ Another option is to use a ChromeCast + using the option "-dcc" in dispcal, dispread and dispwin. + Note that the ChromeCast as a test patch source is probably the + least accurate of your choices, since it up-samples the test + patch and transforms from RGB to YCC and back, but should be + accurate within � 1 bit. You may have to modify any firewall to + permit port 8081 to be accessed on your machine if it falls back to + the Default receiver (see installation + instructions for your platform). +
2) White point calibration & neutral axis calibration.
+ 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:
+
- 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.
  +
- 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 dispcal's @@ -3277,27 +3362,30 @@ a - 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.
- [Recommended] Calibrate the white point and neutral - axis using ArgyllCMS dispcal. 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 -k parameter or +
- [Recommended] Calibrate the white point and neutral + axis using ArgyllCMS dispcal. 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 -k parameter or -K parameter. See also below Choice @@ -3313,475 +3401,477 @@ a - of where to apply display per channel calibration curves.
- 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.
- If an explicit calibration is used, then it is a good idea to add - some test points down the neutral axis when profiling (targen -g parameter).
-
- 3) Choice of where to apply display per channel calibration - curves
-
- 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:
-
- a) 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 "dispwin -I profile.icm",
- or when using MadVR 0.86.9 or latter by creating a 3dLut with - appended calibration curves using -H - display.cal.
-
- b) The calibration can be incorporated into the Device - Link/3dLUT by providing it to collink as the -a display.cal. 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.
-
- The choice is dictated by a number of considerations:
-
- 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.
  -
- Does the video playback always 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 ref 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.
  -
- 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).
- 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.
  -
-
4) Output device calibration and profiling.
- Output device profiling should basically follow the guide above in Adjusting and Calibrating a displays and Profiling Displays. 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 Signal encoding bellow for more details on - this). It may also improve the accuracy of the display profile if - you use the dispread -Z option to - quantize the test values to the precision of the display - system. Don't use the -E options on dispcal and dispread, nor - the -Z option on dispread if you are using MadVR to display test - patches using the "-d madvr" option.
-
- 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.
-
5) Target colorspace
-
- In practical terms, there are five common Video and Digital Cinema - encoding colorspaces.
-
- For Standard Definition:
-
-     EBU 3213 or "PAL 576i" primaries.
-
-     SMPTE RP 145 or "NTSC 480i" primaries.
-
- For High Definition:
-
-     Rec 709 primaries.
-
- For Ultra High Defintion
-
-     Rec 2020 primaries.
-
- For Digital Cinema
-
-     SMPTE-431-2 or "DCI-P3"
-
- PAL and NTSC have historically had poorly specified transfer curve - encodings, and the Rec 709 HDTV encoding curve is the modern recommendation, - but the overall interpretation of Video sources may in fact be - partly determined by the expected standard Video display device - characteristics (see Viewing conditions adjustment and gamut - mapping below for more details).
-
- To enable targeting these colorspaces, ArgyllCMS provides 5 ICC - profiles in the ref directory to use as source - colorspaces:
-
-     EBU3213_PAL.icm
-
-     SMPTE_RP145_NTSC.icm
-
-     Rec709.icm
-
-     Rec2020.icm
-
-     SMPTE431_P3.icm
-
6) Signal encoding
- 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.
-
- The signal encoding comes into play in two situations: 1) - Calibrating and profiling the display, and 2) Using the resulting - Device Link/3DLut.
- 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.
-
- 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.
-
- 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 (-d madvr). In this case, MadVR should be configured - appropriately for full range or Video range encoding, and the -E - flag should not be used with dispcal or dispread, since - MadVR will be taking care of such conversions.
-
- 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.
-
- 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.
-
- 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.
-
7) Black point mapping
-
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) Custom EOTF with input and/or output black point mapping, or b) - using one of the smart gamut mapping intents that does black point - mapping (e.g. la, p, pa, ms or s).
-
-
8) Viewing conditions adjustment and gamut mapping
-

-
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.
-
-
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 EOTF - (Electro-Optical Transfer Curve) is BT.1886, - which defines a pure power 2.4 curve with an input offset and - scale applied to account for the black point offset while - retaining dark shadow tonality. So another means of making the - viewing adjustment is to use the BT.1886-like EOTF for Rec709 - encoded material. Collink supports this using the -I b, and allows some control over the - degree of viewing conditions adjustment by overriding the BT.1886 - gamma using the -I b:g.g - parameter. This is the recommended approach to start with, - since it gives good results with a single parameter.
-
-
The addition of a second optional parameter -I b:p.p:g.g - allows control over the degree of black point offset accounted for - as an output offset, as opposed to input offset Once the effective - gamma value has been chosen to suite the viewing conditions and - set the overall contrast for mid greys, increasing the proportion - of black offset accounted for in the output of the curve is a way - of reducing the deep shadow detail, if it is being overly - emphasized.
-
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.
-
A third alternative is to combine the two approaches. The source - is defined as Rec709 primaries with a BT.1886-like EOTF display in - dim viewing conditions, and then CIECAM02 is used to adjust for - the actual display viewing conditions. Once again, control over - the degree of viewing conditions adjustment is possible by varying - the viewing condition parameters
-
-

-
-
9) Correcting for any black point inaccuracy in the display - profile
-
-
Some video display devices have particularly good black points, - and any slight raising of the black due to innacuracies in the - display profile near black can be objectionable. As well as using - the targen -V flag to improve - accuracy near black during profiling, if the display is known to - be well behaved (ie. that it's darkest black is actually at RGB - value 0,0,0), then the collink -b - flag can be used, to force the source RGB 0,0,0 to map to the - display 0,0,0.
-
-
Putting it all together:
- In this example we choose to create a display calibration first - using dispcal, and create a simple matrix profile as well:
-
- dispcal -v -o -qm -k0 -w 0.3127,0.3290 -gs -o TVmtx.icm - TV
-
- We are targeting a D65 white point (-w 0.3127,0.3290) and - an sRGB response curve.
-
- If you are using the madTPG you would use:
-
- dispcal -v -d madvr -o -qm -k0 -w 0.3127,0.3290 -gs -o - TVmtx.icm TV
-
- 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 targen -V parameter can help improve the - accuracy in this region at the expense of slightly lower accuracy in - lighter regions.
-
- targen -v -d3 -s30 -g100 -f1000 -cTVmtx.icm -V1.8 TV
-
- The display can then be measured:
-
- dispread -v -k -Z8 TV.cal TV
-
- or using madTPG:
-
- dispread -v -d madvr -K TV.cal TV
-
- 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:
-
- colprof -v -qh -bl TV
-
- 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.
-
- If you would like to use the display ICC profile for general color - managed applications, then you would compute a more complete - profile:
-
- colprof -v -qh TV
-
- 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:
-
- collink -v -Ib:2.4 -b -G -ir Rec709.icm TV.icm - HD.icm   # dark conditions- collink -v -Ib     -b -G -ir - Rec709.icm TV.icm HD.icm   # dim conditions - good - default- collink -v -Ib:2.1 -b -G -ir Rec709.icm TV.icm - HD.icm   # mid to dim conditions- collink -v -Ib:2.0 -b -G -ir Rec709.icm TV.icm - HD.icm   # mid to light conditions
-
- or you could do it using pure CIECAM02 adjustment and a black point - mapping:
-
- collink -v -ctv -dmd -da:1 -G -ila Rec709.icm TV.icm - HD.icm # very dark conditions- collink -v -ctv -dmd -da:3 -G -ila Rec709.icm - TV.icm HD.icm # dim conditions- collink -v -ctv -dmd -da:7 -G -ila Rec709.icm - TV.icm HD.icm # mid to dim conditions - good default- collink -v -ctv -dmd -da:15 -G -ila Rec709.icm - TV.icm HD.icm # mid conditions
-
- or using both to model a reference video display system that is - adapted to your viewing conditions:
- - collink -v -Ib -c md -dmd -da:5 -G -ila - Rec709.icm TV.icm HD.icm # very dark conditions- collink -v -Ib -c md -dmd -da:10 -G -ila Rec709.icm - TV.icm HD.icm # dim conditions- collink -v -Ib -c md -dmd -da:18 -G -ila Rec709.icm - TV.icm HD.icm # mid to dark conditions- collink -v -Ib -c md -dmd -da:30 -G -ila Rec709.icm - TV.icm HD.icm   # mid to dark conditions
-
- 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:
-
-     dispwin TV.cal
-
- or the simple matrix profile installed:
-
-     dispwin -I TVmtx.icm
-
- or a the more complete display profile could be installed:
-
- dispwin -I TV.icm
-
- See also here 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".
-
- 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 -E - flag in the dispcal and dispread command lines above.
-
- 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.
-
- For faster exploration of different collink option, you could omit - the "colprof -bl" option, and use collink "-g" instead of "-G", - since this
- 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 ..".
-
- 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).
-
- 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.
-
-
- eeColor
-
- For PC use, where the encoding is full range RGB:
-
- collink -v -3e -Ib -b -G -ir -a TV.cal Rec709.icm TV.icm - HD.icm
-
- 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.
-
- See <http://www.avsforum.com/t/1464890/eecolor-processor-argyllcms> - for some more details.
-
- 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
-
- collink -v -3e -et -Et -Ib -b -G -ir -a TV.cal - Rec709.icm TV.icm HD.icm
-
- 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.
-
- MadVR
-
- 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.
-
- If you are just building one 3dLut then Rec709 source is a good one - to pick.
-
- 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:
-
-     collink -v -3m -et -Et -Ib -b -G -ir -H - TV.cal Rec709.icm TV.icm HD.icm- + + + + of where to apply display per channel calibration curves.

+ 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. +

+ If an explicit calibration is used, then it is a good idea to add + some test points down the neutral axis when profiling (targen -g parameter). + + 3) Choice of where to apply display per channel calibration + curves + + 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: + + a) 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 "dispwin -I profile.icm", + or when using MadVR 0.86.9 or latter by creating a 3dLut with + appended calibration curves using -H + display.cal. + + b) The calibration can be incorporated into the Device + Link/3dLUT by providing it to collink as the -a display.cal. 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. + + The choice is dictated by a number of considerations: + + 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. + + Does the video playback always 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 ref 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. + + 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). + 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. + + + 4) Output device calibration and profiling. + Output device profiling should basically follow the guide above in Adjusting and Calibrating a displays and Profiling Displays. 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 Signal encoding bellow for more details on + this). It may also improve the accuracy of the display profile if + you use the dispread -Z option to + quantize the test values to the precision of the display + system. Don't use the -E options on dispcal and dispread, nor + the -Z option on dispread if you are using MadVR to display test + patches using the "-d madvr" option. + + 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. + 5) Target colorspace + + In practical terms, there are five common Video and Digital Cinema + encoding colorspaces. + + For Standard Definition: + +     EBU 3213 or "PAL 576i" primaries. + +     SMPTE RP 145 or "NTSC 480i" primaries. + + For High Definition: + +     Rec 709 primaries. + + For Ultra High Defintion + +     Rec 2020 primaries. + + For Digital Cinema + +     SMPTE-431-2 or "DCI-P3" + + PAL and NTSC have historically had poorly specified transfer curve + encodings, and the Rec 709 HDTV encoding curve is the modern recommendation, + but the overall interpretation of Video sources may in fact be + partly determined by the expected standard Video display device + characteristics (see Viewing conditions adjustment and gamut + mapping below for more details). + + To enable targeting these colorspaces, ArgyllCMS provides 5 ICC + profiles in the ref directory to use as source + colorspaces:    + +     EBU3213_PAL.icm + +     SMPTE_RP145_NTSC.icm + +     Rec709.icm + +     Rec2020.icm + +     SMPTE431_P3.icm + 6) Signal encoding + 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. + + The signal encoding comes into play in two situations: 1) + Calibrating and profiling the display, and 2) Using the resulting + Device Link/3DLut. + 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. + + 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. + + 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 (-d madvr). In this case, MadVR should be configured + appropriately for full range or Video range encoding, and the -E + flag should not be used with dispcal or dispread, since + MadVR will be taking care of such conversions. + + 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. + + 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. + + 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. + 7) Black point mapping + 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) Custom EOTF with input and/or output black point mapping, or b) + using one of the smart gamut mapping intents that does black point + mapping (e.g. la, p, pa, ms or s). + + 8) Viewing conditions adjustment and gamut mapping + + 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. + + 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 EOTF + (Electro-Optical Transfer Curve) is BT.1886, + which defines a pure power 2.4 curve with an input offset and + scale applied to account for the black point offset while + retaining dark shadow tonality. So another means of making the + viewing adjustment is to use the BT.1886-like EOTF for Rec709 + encoded material. Collink supports this using the -I b, and allows some control over the + degree of viewing conditions adjustment by overriding the BT.1886 + gamma using the -I b:g.g + parameter. This is the recommended approach to start with, + since it gives good results with a single parameter. + + The addition of a second optional parameter -I b:p.p:g.g allows control over the + degree of black point offset accounted for as an output offset, as + opposed to input offset Once the effective gamma value has been + chosen to suite the viewing conditions and set the overall + contrast for mid greys, increasing the proportion of black offset + accounted for in the output of the curve is a way of reducing the + deep shadow detail, if it is being overly emphasized. + 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. + A third alternative is to combine the two approaches. The source + is defined as Rec709 primaries with a BT.1886-like EOTF display in + dim viewing conditions, and then CIECAM02 is used to adjust for + the actual display viewing conditions. Once again, control over + the degree of viewing conditions adjustment is possible by varying + the viewing condition parameters + + + + 9) Correcting for any black point inaccuracy in the display + profile + + Some video display devices have particularly good black points, + and any slight raising of the black due to innacuracies in the + display profile near black can be objectionable. As well as using + the targen -V flag to improve + accuracy near black during profiling, if the display is known to + be well behaved (ie. that it's darkest black is actually at RGB + value 0,0,0), then the collink -b + flag can be used, to force the source RGB 0,0,0 to map to the + display 0,0,0. + + Putting it all together: + In this example we choose to create a display calibration first + using dispcal, and create a simple matrix profile as well: + + dispcal -v -o -qm -k0 -w 0.3127,0.3290 -gs -o TVmtx.icm + TV + + We are targeting a D65 white point (-w 0.3127,0.3290) and + an sRGB response curve. + + If you are using the madTPG you would use: + + dispcal -v -d madvr -o -qm -k0 -w 0.3127,0.3290 -gs -o + TVmtx.icm TV + + 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 targen -V parameter can help improve the + accuracy in this region at the expense of slightly lower accuracy in + lighter regions. + + targen -v -d3 -s30 -g100 -f1000 -cTVmtx.icm -V1.8 TV + + The display can then be measured: + + dispread -v -k -Z8 TV.cal TV + + or using madTPG: + + dispread -v -d madvr -K TV.cal TV + + 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: + + colprof -v -qh -bl TV + + 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. + + If you would like to use the display ICC profile for general color + managed applications, then you would compute a more complete + profile: + + colprof -v -qh TV + + 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: + + collink -v -Ib:2.4 -b -G -ir Rec709.icm TV.icm + HD.icm   # dark conditions + collink -v -Ib     -b -G -ir + Rec709.icm TV.icm HD.icm   # dim conditions - good + default + collink -v -Ib:2.1 -b -G -ir Rec709.icm TV.icm + HD.icm   # mid to dim conditions + collink -v -Ib:2.0 -b -G -ir Rec709.icm TV.icm + HD.icm   # mid to light conditions + + or you could do it using pure CIECAM02 adjustment and a black point + mapping: + + collink -v -ctv -dmd -da:1 -G -ila Rec709.icm TV.icm + HD.icm # very dark conditions + collink -v -ctv -dmd -da:3 -G -ila Rec709.icm + TV.icm HD.icm # dim conditions + collink -v -ctv -dmd -da:7 -G -ila Rec709.icm + TV.icm HD.icm # mid to dim conditions - good default + collink -v -ctv -dmd -da:15 -G -ila Rec709.icm + TV.icm HD.icm # mid conditions + + or using both to model a reference video display system that is + adapted to your viewing conditions: + + collink -v -Ib -c md -dmd -da:5 -G -ila + Rec709.icm TV.icm HD.icm # very dark conditions + collink -v -Ib -c md -dmd -da:10 -G -ila Rec709.icm + TV.icm HD.icm # dim conditions + collink -v -Ib -c md -dmd -da:18 -G -ila Rec709.icm + TV.icm HD.icm # mid to dark conditions + collink -v -Ib -c md -dmd -da:30 -G -ila Rec709.icm + TV.icm HD.icm   # mid to dark conditions + + 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: + +     dispwin TV.cal + + or the simple matrix profile installed: + +     dispwin -I TVmtx.icm + + or a the more complete display profile could be installed: + + dispwin -I TV.icm + + See also here 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". + + 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 -E + flag in the dispcal and dispread command lines above. + + 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. + + For faster exploration of different collink option, you could omit + the "colprof -bl" option, and use collink "-g" instead of "-G", + since this + 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 ..". + + 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). + + 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. + + + eeColor + + For PC use, where the encoding is full range RGB: + + collink -v -3e -Ib -b -G -ir -a TV.cal Rec709.icm TV.icm + HD.icm + + 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. + + See <http://www.avsforum.com/t/1464890/eecolor-processor-argyllcms> + for some more details. + + 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 + + collink -v -3e -et -Et -Ib -b -G -ir -a TV.cal + Rec709.icm TV.icm HD.icm + + 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. + + MadVR + + 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. + + If you are just building one 3dLut then Rec709 source is a good one + to pick. + + 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: + +     collink -v -3m -et -Et -Ib -b -G -ir -H + TV.cal Rec709.icm TV.icm HD.icm +     collink -v -3m -et -Et -Ib -b -G -ir -H @@ -3808,8 +3898,11 @@ a - TV.cal EBU3213_PAL.icm TV.icm SD_PAL.icm - + + + + TV.cal EBU3213_PAL.icm TV.icm SD_PAL.icm+     collink -v -3m -et -Et -Ib -b -G -ir -H @@ -3836,15 +3929,18 @@ a - TV.cal SMPTE_RP145_NTSC.icm TV.icm SD_NTSC.icm
-
- 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:
-
-     collink -v -3m -et -Et -Ib -b -G -ir -a - TV.cal Rec709.icm TV.icm HD.icm- + + + + TV.calSMPTE_RP145_NTSC.icm TV.icm SD_NTSC.icm
+
+ 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:
+
+     collink -v -3m -et -Et -Ib -b -G -ir -a + TV.cal Rec709.icm TV.icm HD.icm+     collink -v -3m -et -Et -Ib -b -G -ir -a @@ -3871,8 +3967,11 @@ a - TV.cal EBU3213_PAL.icm TV.icm SD_PAL.icm- + + + + TV.calEBU3213_PAL.icm TV.icm SD_PAL.icm+     collink -v -3m -et -Et -Ib -b -G -ir -a @@ -3899,181 +3998,184 @@ a - TV.cal SMPTE_RP145_NTSC.icm TV.icm SD_NTSC.icm
-
- the consequence though is that the appearance of other application - will shift when MadVR is using the 3dLut and loading the calibration - curves.
-
- 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.
-
- 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.- - -

Verifying Video Calibration

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.
-
-

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:
-

targen -v -d3 -e1 -m6 -f0 -W verify
-

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 an - X3DOM 3d visualization of the point set using the -W flag. It is - good to take a look at the verifyd.x3d.html file using a Web - browser. You may want to create several test sets that look at - particular aspects, ie. neutral axis response, pure colorant - responses, etc.
-

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:-

copy verify.ti1 ref.ti1 - fakeread -v -b -Z8 TV.icm Rec709.icm ref -

You should adjust the parameters as necessary, so that the - reference matches the link options. For instance, if your link - options included "-I b:0.2:2.15" then the equivalent fakeread - option "-b 0.2:2.15:TV.icm" should be used, etc.
-

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:
-

copy verify.ti1 checkA.ti1- fakeread -v -et -Z8 -p HD.icm -Et TV.icm checkA -

If you used collink -a, then the calibration incorporated in the - device link needs to be undone to match what the display profile - expects:

fakeread -v -et -Z8 -p HD.icm -Et -K TV.cal TV.icm - checkA

and then you can verify: -

colverify -v -n -w -x ref.ti3 checkA.ti3 -

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.]-

verify -v -N -w -x ref.ti3 checkA.ti3
-

This will give a numerical report of the delta E's, and also - generate an X3DOM plot of the errors in L*a*b* space. The - important thing is to take a look at the checkA.x3d.html file, to - see if gamut clipping is occurring - this is the case if the large - error vectors are on the sides or top of the gamut. Note that the - perfect cube device space values become a rather distorted cube - like shape in the perceptual L*a*b* space. If the vectors are - small in the bulk of the space, then this indicates that the link - 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:
-

verify -v -N -w -x -L TV.icm ref.ti3 - checkA.ti3 - -

You can explicitly compare the gamuts of your video space and - your display using the gamut tools:
-

iccgamut -ff -ia Rec709- iccgamut -ff -ia TV.icm- viewgam -i Rec709.gam TV.gam gamuts
-

and look at the gamuts.x3d.html file, as well as taking notice of - % of the video volume that the display intersects. The X3DOM solid - volume will be the video gamut, while the wire frame is the - display gamut. If you are not targetting D65 with your display, - you should use iccgamut -ir instead of -ia, so as - to align the white points.
-

The main verification check is to actually measure the display - response and compare it against the reference. Make sure the - display is setup as you would for video playback and then use - dispread:
-

copy verify.ti1 checkB.ti1- dispread -v -Z8 checkB
-

You would add any other options needed (such as -y 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: [Note 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. ]
-

dispread -v -d madvr -V checkB
-

Verify the same way as above:
-

verify -v -n -w -x ref.ti3 checkB.ti3 -

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:-

verify -v -n -w -x -L TV.icm ref.ti3 - checkB.ti3

-
-

-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - + + + + TV.cal SMPTE_RP145_NTSC.icm TV.icm SD_NTSC.icm
+
+ the consequence though is that the appearance of other application + will shift when MadVR is using the 3dLut and loading the calibration + curves.
+
+ 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.
+
+ 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.+ + +

Verifying Video Calibration

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.
+
+

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:
+

targen -v -d3 -e1 -m6 -f0 -W verify
+

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 an + X3DOM 3d visualization of the point set using the -W flag. It is + good to take a look at the verifyd.x3d.html file using a Web + browser. You may want to create several test sets that look at + particular aspects, ie. neutral axis response, pure colorant + responses, etc.
+

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:+

copy verify.ti1 ref.ti1 + fakeread -v -b -Z8 TV.icm Rec709.icm ref +

You should adjust the parameters as necessary, so that the + reference matches the link options. For instance, if your link + options included "-I b:0.2:2.15" then the equivalent fakeread + option "-b 0.2:2.15:TV.icm" should be used, etc.
+

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:
+

copy verify.ti1 checkA.ti1+ fakeread -v -et -Z8 -p HD.icm -Et TV.icm checkA +

If you used collink -a, then the calibration incorporated in the + device link needs to be undone to match what the display profile + expects:

fakeread -v -et -Z8 -p HD.icm -Et -K TV.cal TV.icm + checkA

and then you can verify: +

colverify -v -n -w -x ref.ti3 checkA.ti3 +

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.]+

verify -v -N -w -x ref.ti3 checkA.ti3
+

This will give a numerical report of the delta E's, and also + generate an X3DOM plot of the errors in L*a*b* space. The + important thing is to take a look at the checkA.x3d.html file, to + see if gamut clipping is occurring - this is the case if the large + error vectors are on the sides or top of the gamut. Note that the + perfect cube device space values become a rather distorted cube + like shape in the perceptual L*a*b* space. If the vectors are + small in the bulk of the space, then this indicates that the link + 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:
+

verify -v -N -w -x -L TV.icm ref.ti3 + checkA.ti3 + +

You can explicitly compare the gamuts of your video space and + your display using the gamut tools:
+

iccgamut -ff -ia Rec709+ iccgamut -ff -ia TV.icm+ viewgam -i Rec709.gam TV.gam gamuts
+

and look at the gamuts.x3d.html file, as well as taking notice of + % of the video volume that the display intersects. The X3DOM solid + volume will be the video gamut, while the wire frame is the + display gamut. If you are not targetting D65 with your display, + you should use iccgamut -ir instead of -ia, so as + to align the white points.
+

The main verification check is to actually measure the display + response and compare it against the reference. Make sure the + display is setup as you would for video playback and then use + dispread:
+

copy verify.ti1 checkB.ti1+ dispread -v -Z8 checkB
+

You would add any other options needed (such as -y 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: [Note 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. ]
+

dispread -v -d madvr -V checkB
+

Verify the same way as above:
+

verify -v -n -w -x ref.ti3 checkB.ti3 +

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:+

verify -v -n -w -x -L TV.icm ref.ti3 + checkB.ti3

+
+

+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + diff --git a/doc/XRGA.html b/doc/XRGA.html new file mode 100644 index 0000000..295d7b2 --- /dev/null +++ b/doc/XRGA.html @@ -0,0 +1,137 @@ + + + + + + + Argyll XRGA conversion + + +
+

Conversion to/from XRGA
+

+ After purchasing Gretag-Macbeth, X-Rite harmonized the subtly + different calibration standards the two companies were using for + their reflective measurement instruments, in order to minimize + changes with the introduction of new instruments. The result was the + XRGA + standard, introduced in September 2010.
+
+ Current X-Rite instruments are natively calibrated to XRGA, while + older instruments from X-Rite are calibrated to XRDI, and + Gretag-Macbeth instruments to GMDI standards. To smooth the + interchange of old and new instruments, a spectral conversion + + + is possible between these different standards. While such a + conversion is not perfect, it reduces the discontinuities between + old instrument families and current X-Rite instruments.
+
+ By default, Argyll will use the native calibration of Gretag-Macbeth + and X-Rite instruments. These are summarized here:
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

DTP20 + "Pulse" +	XRDI +
DTP22 + Digital Swatchbook	XRDI +
DTP41	XRDI +
DTP51	XRDI +
Spectrolino/ + SpectroScan	GMDI +
Eye-One Pro + Rev A-D	GMDI +
ColorMunki + Design or Photo	XRGA +
Eye-One Pro2 + (Eye-One Pro Rev E)	XRGA +

+
+
+ You can override this and force reflective data to be a particular + calibration standard in two ways:
+
+ Using the -A command line option in spotread and chartread:
+
+     -A N|A|X|G
+
+         The N argument sets + the calibration to Native.
+         The A argument sets + the calibration to XRGA.
+         The X argument sets + the calibration to XRDI.
+         The G argument sets + the calibration to GMDI.
+
+
+ Or by setting an environment variable:
+ (Note that command line options will override this.)
+
+
+ ARGYLL_XRGA
+
+

If the ARGYLL_XRGA environment variable is set to:
+
+     XRGA, then all Getag-MacBeth/X-Rite + reflective measurements will be converted to XRGA.
+     XRDI, then all Getag-MacBeth/X-Rite + reflective measurements will be converted to XRDI.
+     GMDI, then all Getag-MacBeth/X-Rite + reflective measurements will be converted to GMDI.
+
+ If not set (or set to some other string), then the native + calibration will be used. Note that the values must be upper case.
+

+
+ All of the above except the DTP51 can have a conversion + applied.
+ (The DTP51 returns only colorimetric data, while the conversion + requires spectral data.)
+
+ + diff --git a/doc/afiles b/doc/afiles index a73a8ba..d820c7f 100644 --- a/doc/afiles +++ b/doc/afiles @@ -3,6 +3,7 @@ DocLicense.txt License.txt License2.txt License3.txt +License4.txt ArgyllDoc.html ChangesSummary.html ColorManagement.html @@ -48,6 +49,7 @@ i1p.jpg sl.jpg ss.jpg JETI_1211.jpg +JETI_1501.jpg ColorHug.jpg EX1.jpg SMCube.jpg @@ -135,6 +137,7 @@ viewgam.html xicclu.html oeminst.html ucmm.html +XRGA.html Q60.jpg DC.jpg SG.jpg @@ -144,6 +147,7 @@ i1scan14.jpg HCT.jpg CMP_DT_003.jpg CMP_Digital_Target-4.jpg +CMP_Digital_Target-7.jpg colorchecker.jpg SpyderChecker.jpg SpyderChecker24.jpg diff --git a/doc/average.html b/doc/average.html index 231df92..e67ab2d 100644 --- a/doc/average.html +++ b/doc/average.html @@ -10,8 +10,7 @@

spectro/average

Summary

Average or merge two or more .ti3 - measurement - files.
+ measurement files.
If only one input file is provided, all the patches with the same device values will be average together.

Usage

@@ -19,35 +18,78 @@ usage: average [-options] - input1.ti3 - input2.ti3 ... output.ti3
-v              - Verbose
+ + + + Verbose
+ -e +              + Median rather than average
+ -g              + + Geometric Median of PCS in encoded space+ -L              + + Geometric Median of PCS in L*a*b* space+ -X              + + Geometric Median of PCS in XYZ space
-m              Merge + + + rather than average
input1.ti3      First + + + input file
input2.ti3      Second + + + input file
...             + + + etc.
output.ti3      Resulting + + + averaged or merged output file

All keywords and other table data will be taken from the first input file. By default the input files are averaged, but they can be - merged - by using the -m flag.
+ merged by using the -m + flag.

The fields must be the same and in the same order. For averaging, - the - device values must be the same and in the same order.
+ the device values must be the same and in the same order.
+
+ If the -e option is used, then the independent median (i.e. + Marginal median) of the field values is used, rather than the + average.
+
+ If the -g option is used, then Geometric + Median of PCS values is computed in their encoded space (i.e. + XYZ or L*a*b*).
+
+ If the -L option is used, then Geometric Median of PCS + values is computed in L*a*b* space.
+
+ If the -X option is used, then Geometric Median of PCS + values is computed in XYZ space.

diff --git a/doc/chartread.html b/doc/chartread.html index e9dddaf..19f4add 100644 --- a/doc/chartread.html +++ b/doc/chartread.html @@ -28,6 +28,8 @@ Verbose + + mode
-c listno -d
@@ -66,6 +72,8 @@ measurement + + Display type - instrument specific list to choose from.
-e -p
-x [lx]            Take + + manually entered values, either L*a*b* (-xl) or XYZ (-xx).
-l -I file.cal        Override @@ -136,6 +154,8 @@ partly + + Set filter configuration:
n                  @@ -143,6 +163,8 @@ partly + + None
p                  @@ -150,6 +172,8 @@ partly + + Polarising filter
6                  @@ -157,6 +181,8 @@ partly + + D65
u                  @@ -164,8 +190,14 @@ partly + + U.V. Cut
+ -A N|A|X|G         + + XRGA conversion (default N)
-N @@ -190,6 +222,8 @@ partly + + Apply Colorimeter Correction Matrix
-X file.ccss          @@ -203,6 +237,8 @@ Samples + + for calibration
-Q observ1931_2 (def.) -S                 @@ -242,6 +282,8 @@ strip + + & unexpected value warnings
-W n|h|x           @@ -250,6 +292,8 @@ Override + + serial port flow control: n = none, h = HW, x = Xon/Xoff
.ti2]/output[ parameter allows overriding the .ti2 calibration curves placed in the resulting .ti3 file with the actual calibration that was used for that particular print.
@@ -421,6 +469,21 @@ Override simulation, or Ultra Violet Cut filter, and this option allows the instrument to be configured appropriately.

+ The -A options allows overriding the default + or environment variable set XRGA + conversion:
+
+     -A N|A|X|G
+
+         The N argument sets + the calibration to Native (default).
+         The A argument sets + the calibration to XRGA.
+         The X argument sets + the calibration to XRDI.
+         The G argument sets + the calibration to GMDI.
+
-N Any instrument that requires regular calibration will ask for calibration on initial start-up. Sometimes this can be awkward if diff --git a/doc/colprof.html b/doc/colprof.html index 755226b..d5df56e 100644 --- a/doc/colprof.html +++ b/doc/colprof.html @@ -9,9 +9,11 @@

profile/colprof

Summary

- Create an ICC profile from - the .ti3 test chart patch - values.
+ Create an RGB, CMY or CMYK ICC + profile from the .ti3 test + chart patch values.
+ [ Note that currently, Monochrome and N-Color profiles are not + supported. ]

Usage Summary

colprof [-options] inoutfile -v         @@ -43,6 +45,10 @@ + + + + @@ -81,6 +87,10 @@ + + + + @@ -124,6 +134,10 @@ + + + + @@ -163,6 +177,10 @@ + + + + @@ -216,6 +234,10 @@ x + + + + @@ -262,6 +284,10 @@ White + + + + @@ -308,6 +334,10 @@ Wh + + + + @@ -354,6 +384,10 @@ Wh + + + + @@ -399,6 +433,10 @@ Black + + + + @@ -445,6 +483,10 @@ concave, + + + + @@ -471,6 +513,10 @@ concave, + + + + @@ -524,6 +570,10 @@ cLUT + + + + @@ -569,6 +619,10 @@ s + + + + @@ -615,6 +669,10 @@ S + + + + @@ -646,6 +704,10 @@ S + + + + @@ -694,6 +756,10 @@ and + + + + @@ -709,6 +775,10 @@ and + + + + Display Black Point override hack -V demphasis       @@ -725,6 +795,10 @@ and + + + + Degree of dark region cLUT grid emphasis 1.0-3.0 (default 1.00 = none) -f [illum] @@ -749,6 +823,10 @@ and + + + + @@ -775,6 +853,10 @@ and + + + + @@ -811,6 +893,10 @@ D50M2, + + + + @@ -848,6 +934,10 @@ D50M2, + + + + @@ -858,77 +948,13 @@ D50M2, -r avgdev    Average deviation of device+instrument readings as a percentage (default 0.5%) - -s src.icc         -Apply -gamut -mapping -to -output -profile -perceptual -B2A -table -for - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - given source - -S src.icc         - - - - - - - - - - - - - - - - - - - - - - - - - + -s src.icm|cperc Apply gamut + mapping to output profile perceptual B2A table for given source, + or compression percentage + -S src.icm|experc Apply gamut + mapping to output profile perceptual and saturation B2A table, + or expansion percentage + -nP                @@ -937,9 +963,6 @@ for - Apply gamut mapping to output profile perceptual and saturation - B2A table - -nP                @@ -969,13 +992,13 @@ for + Use colormetric source gamut to make output profile perceptual + table + -nS                - Use colormetric source gamut to make output profile perceptual - table - -nS                @@ -1048,6 +1071,10 @@ for + + + + @@ -1100,6 +1127,10 @@ for + + + + @@ -1108,6 +1139,10 @@ for pa - Perceptual Appearance
                 + + + + lp - Luminance Preserving Perceptual         @@ -1138,6 +1173,10 @@ for + + + + @@ -1166,6 +1205,10 @@ for + + + + @@ -1201,6 +1244,10 @@ for + + + + @@ -1237,6 +1284,10 @@ for + + + + @@ -1272,6 +1323,10 @@ for + + + + @@ -1308,6 +1363,10 @@ for + + + + @@ -1343,6 +1402,10 @@ for + + + + @@ -1378,6 +1441,10 @@ for + + + + @@ -1442,6 +1509,10 @@ for + + + + @@ -1491,6 +1562,10 @@ for + + + + @@ -1539,6 +1614,10 @@ for + + + + @@ -1575,6 +1654,10 @@ Override + + + + @@ -1650,7 +1733,8 @@ Override Perceptual, r to set Relative Colorimetric, s to set Saturation, and a to - set Absolute colorimetric. + set Absolute colorimetric. Some CMM's will use this to determine the + default intent that they will use. The -q parameter sets the level of effort and/or detail in the resulting profile. For table based profiles @@ -1731,6 +1815,10 @@ the + + + + @@ -1767,6 +1855,10 @@ the + + + + @@ -1838,6 +1930,10 @@ the + + + + @@ -1874,6 +1970,10 @@ the + + + + @@ -1909,6 +2009,10 @@ the + + + + @@ -1944,6 +2048,10 @@ the + + + + @@ -1979,6 +2087,10 @@ the + + + + @@ -2022,6 +2134,10 @@ White            &nb + + + + @@ -2281,6 +2397,10 @@ White            &nb + + + + @@ -2428,31 +2548,54 @@ White            &nb -s -S In order to generate perceptual and saturation - intent B2A tables for output profiles, it is necessary to specify at - least one profile to define what source gamut should be used in the - source to destination gamut mapping. [For more information on why a source gamut is needed, see About ICC profiles and - Gamut Mapping] The -S parameter is used to do this, - and doing so causes perceptual and saturation tables to be + Gamut Mapping]. The -S parameter is used to do + this, and doing so causes perceptual and saturation tables to be generated. If only a perceptual intent is needed, then the -s flag can be used, and the saturation intent will use the same table - as the perceptual intent. Note that a input, output, display or - device colororspace profile should be specified, not a non-device - colorspace, device link, abstract or named color profile. - If no source gamut is specified for a cLUT Display profile, then an - ICC Version 2.2.0 profile will be created with only an A2B0 and B2A0 - tag. If a source gamut is specified, then an ICC Version 2.4.0 - profile will be created with a full complement of B2A tags to - support all intents. The source gamut is created from the - corresponding intent table of the provided profile to the output - table being created. A TIFF or JPEG file containing an embedded ICC - profile may be supplied as the argument. + as the perceptual intent. + + There are two ways of specifying a source gamut 1) Specify a + specific source ICC profile or 2) Specify a general compression of + the output gamut as a percentage. With the second choice, incoming + colors that are up to the percentage outside the devices gamut will + be compressed to fit into it. The same percentage is used for + expansion if a saturation table is generated, or a separate + percentage can be specified by including both a -s and -S + percentage. You can optionally specify both and input ICC + profile and a general compression percentage by using the -S option + twice, in which case the input profile determines just the luminance + range mapping, with the percentage determining the gamut volume + compression. If a percentage compression is specified without an ICC + profile, then the incoming luminance range will be assumed to be + full range (perfect white to perfect black), which is compatible + with idealized colorspaces such as sRGB, AdobeRGB and other working + RGB spaces. The input viewing conditions are applicable to the + assumed full range input. + + If no source ICC or compression percentage is specified for a cLUT + Display profile, then an ICC Version 2.2.0 profile will be created + with only an A2B0 and B2A0 tag. If a source gamut is specified, then + an ICC Version 2.4.0 profile will be created with a full complement + of B2A tags to support all intents. + + The source gamut is created from the corresponding intent table of + the provided profile to the output table being created. A TIFF or + JPEG file containing an embedded ICC profile may be supplied as the + argument, instead of an ICC profile. + Note that input profiles and matrix profiles will only contain a colorimetric intent table or matrix, and hence the -s and -S option is not relevant. + Note that an input, output, display or device colororspace + profile should be specified, not a non-device colorspace, device + link, abstract or named color profile. -nP: Normally when a source profile is provided to define the source @@ -2499,7 +2642,9 @@ White            &nb space should be Jab appearance space, with the viewing conditions generally being those of the input profile viewing conditions. The input profile will normally be the one used to create a source image - gamut using tiffgamut. + gamut using tiffgamut. Note + that a source gamut is not used if a general compression ratio gamut + mapping is used. The -p option allows specifying one or more abstract profiles that will be applied to the output tables, diff --git a/doc/dispcal.html b/doc/dispcal.html index d66caf5..ff96ff2 100644 --- a/doc/dispcal.html +++ b/doc/dispcal.html @@ -1,28 +1,28 @@ - - - - dispcal - - - - - spectro/dispcal - Summary - Given calibration target information [white point, maximum - brightness, and response curve ("gamma")], display a series of test - patches on the display, and using the colorimetric values read, - create a calibration lookup tables that make the display meet the - desired target. The type of instrument is determined by the - communication port selected. Emission and display measurement - instruments are supported. - Usage - dispcal - [-options] inoutfile - -v [n] + + + + dispcal + + + + + spectro/dispcal + Summary + Given calibration target information [white point, maximum + brightness, and response curve ("gamma")], display a series of test + patches on the display, and using the colorimetric values read, + create a calibration lookup tables that make the display meet the + desired target. The type of instrument is determined by the + communication port selected. Emission and display measurement + instruments are supported. + Usage + dispcal + [-options] inoutfile + -v [n]               @@ -70,18 +70,18 @@ - - Verbose mode - -display displayname [X11 only] Choose X11 display - name - -d n[,m] -             - [X11 only]Choose the display from the following list (default - 1), + + Verbose mode + -display displayname [X11 only] Choose X11 display + name + -d n[,m] +             + [X11 only]Choose the display from the following list (default + 1),                       and optionally @@ -137,9 +137,9 @@ for - - VideoLUT access. - + -d n                 Choose the @@ -195,8 +195,8 @@ list - - 1) + + 1) -dweb[:port]         @@ -243,9 +243,9 @@ list - - Display via a web server at port (default 8080) - -dmadvr + + Display via a web server at port (default 8080) + -dmadvr              @@ -276,8 +276,8 @@ list - - [MSWin] Display via MadVR Video Renderer + + [MSWin] Display via MadVR Video Renderer -dcc[:n]             @@ -288,13 +288,13 @@ list - - Display via n'th ChromeCast (default 1, ? for list) - + -c @@ -342,37 +342,37 @@ list - - listno -        Set communication port from - the following list (default 1) - -r -              -      Report on the calibrated display then - exit - -R -              -      Report on the uncalibrated display then - exit - -m -              -      Skip adjustment of the monitor - controls - -o [profile.icm]     Create - fast matrix/shaper profile [different filename to outfile.icm] + + listno +        Set communication port from + the following list (default 1) + -r +              +      Report on the calibrated display then + exit + -R +              +      Report on the uncalibrated display then + exit + -m +              +      Skip adjustment of the monitor + controls + -o [profile.icm]     Create + fast matrix/shaper profile [different filename to outfile.icm] -O description       @@ -420,8 +420,8 @@ list - - Fast ICC Profile Description string (Default "outfile") + + Fast ICC Profile Description string (Default "outfile") -u                   Update previous @@ -477,12 +477,12 @@ ICC - - profile VideoLUTs - -q [lmh] + -q [lmh]             @@ -530,8 +530,8 @@ ICC - - Quality - Low, Medium (def), High + + Quality - Low, Medium (def), High -p                   @@ -568,10 +568,10 @@ ICC - - Use telephoto mode (ie. for a projector) (if available) - -y X + + Use telephoto mode (ie. for a projector) (if available) + -y X                 @@ -619,12 +619,12 @@ ICC - - Display type - instrument specific list to choose from. - -t [temp] + -t [temp]            White Daylight @@ -680,10 +680,10 @@ in - - deg. K (deflt.) - + -T [temp]            White Black @@ -739,11 +739,11 @@ temperaturee - - in deg. K - -w x,y + -w x,y               @@ -791,11 +791,11 @@ temperaturee - - Set the target white point as chromaticity coordinates - -b bright + -b bright            @@ -843,11 +843,11 @@ temperaturee - - Set the target white brightness in cd/m^2 - -g gamma + -g gamma             @@ -895,9 +895,9 @@ temperaturee - - Set the target response curve gamma (Def. 2.4) + + Set the target response curve gamma (Def. 2.4)                       @@ -945,9 +945,9 @@ temperaturee - - Use "-gl" for L*a*b* curve + + Use "-gl" for L*a*b* curve                @@ -995,8 +995,8 @@ temperaturee - -      Use "-gs" for sRGB curve + +      Use "-gs" for sRGB curve                       Use "-g709" @@ -1052,8 +1052,8 @@ use - - -a as well!) + + -a as well!)                       @@ -1101,9 +1101,9 @@ use - - Use "-g240" for SMPTE 240M curve (should use -a as well!) + + Use "-g240" for SMPTE 240M curve (should use -a as well!)                       @@ -1151,7 +1151,7 @@ use - + Use "-G2.4 -f0" for BT.1886                                           @@ -1192,13 +1192,13 @@ use - - - -G gamma -             - Set the target response curve actual technical gamma + + + -G gamma +             + Set the target response curve actual technical gamma -f [degree]          Amount of @@ -1254,8 +1254,8 @@ output - - offset (default all output offset) + + offset (default all output offset) -a ambient           @@ -1303,17 +1303,17 @@ output - - Use viewing condition adjustment for ambient in Lux - -k factor -            - Amount to try and correct black point hue. Default 1.0, LCD - default 0.0 - -A rate -              - Rate of blending from neutral to black point. Default 4.0 + + Use viewing condition adjustment for ambient in Lux + -k factor +            + Amount to try and correct black point hue. Default 1.0, LCD + default 0.0 + -A rate +              + Rate of blending from neutral to black point. Default 4.0 -b                   @@ -1322,10 +1322,10 @@ output - - Use forced black point hack - + -B bkbright          @@ -1373,12 +1373,12 @@ output - - Set the target black brightness in cd/m^2 - -e [n] + -e [n]               @@ -1426,12 +1426,12 @@ output - - Run n verify passes on final curves - -z + + Run n verify passes on final curves + -z                   @@ -1479,13 +1479,13 @@ output - - Run only verify pass on installed calibration curves - -P - ho,vo,ss[,vs]     Position test window - and scale it + + Run only verify pass on installed calibration curves + -P + ho,vo,ss[,vs]     Position test window + and scale it                       ho,vi: 0.0 @@ -1541,8 +1541,8 @@ center, - - = right/bottom etc. + + = right/bottom etc.                       ss: 0.5 @@ -1598,9 +1598,9 @@ normal, - - = double etc. -                       @@ -1635,10 +1635,10 @@ normal, - - ss,vs: = optional horizontal, vertical scale. - -F + + ss,vs: = optional horizontal, vertical scale. + -F                   @@ -1686,11 +1686,11 @@ normal, - - Fill whole screen with black background - -E + + Fill whole screen with black background + -E                   @@ -1717,13 +1717,13 @@ normal, - - Video - encode output as (16-235)/255 "TV" levels - -nVideo + encode output as (16-235)/255 "TV" levels + -n                   [X11 @@ -1779,14 +1779,14 @@ on - - test window - -J -              -      Run instrument calibration first - -J +              +      Run instrument calibration first + -N                   @@ -1834,18 +1834,18 @@ on - - Disable initial calibration of instrument if possible - -H -              -      Use high resolution spectrum mode (if - available) - - + -H +              +      Use high resolution spectrum mode (if + available) + + -X file.ccmx         @@ -1893,9 +1893,9 @@ on - - Apply Colorimeter Correction Matrix - -X + + Apply Colorimeter Correction Matrix + -X file.ccss          Use Colorimeter @@ -1946,14 +1946,14 @@ Calibration - - Spectral Samples for calibration - -Q observ -     Choose CIE Observer for spectrometer or CCSS - colorimeter data: + + Spectral Samples for calibration + -Q observ +     Choose CIE Observer for spectrometer or CCSS + colorimeter data:             @@ -2001,11 +2001,11 @@ Calibration - - 1931_2 (def.), 1964_10, S&B 1955_2, shaw, - J&V 1978_2, 1964_10c + + 1931_2 (def.), 1964_10, S&B 1955_2, shaw, + J&V 1978_2, 1964_10c -I b|w               @@ -2053,8 +2053,8 @@ Calibration - - Drift compensation, Black: -Ib, White: -Iw, Both: -Ibw + + Drift compensation, Black: -Ib, White: -Iw, Both: -Ibw -Y @@ -2071,7 +2071,7 @@ Calibration - + R:rate            @@ -2088,36 +2088,36 @@ Calibration - - Override measured refresh rate with rate Hz - -Y A -             -     Use non-adaptive integration time mode (if - available). - -Y - p -             -     Don't wait for the instrument to be placed on - the display - -C "command" -         Invoke shell - "command" each time a color is set - -M "command" -         Invoke shell - "command" each time a color is measured - + -Y A +             +     Use non-adaptive integration time mode (if + available).
+ -Y + p +             +     Don't wait for the instrument to be placed on + the display
+ -C "command" +         Invoke shell + "command" each time a color is set
+ -M "command" +         Invoke shell + "command" each time a color is measured
+ -W n|h|x             Override serial @@ -2173,12 +2173,12 @@ none, - - h = HW, x = Xon/Xoff
- -D [level]
+ -D [level]           @@ -2226,12 +2226,12 @@ none, - - Print debug diagnostics to stderr
- inoutfile
+ inoutfile            @@ -2279,79 +2279,79 @@ none, - - Base name for created - or updated .cal and .icm output files
-
-

Comments
-

- This is the tool is used for adjusting and calibrating a display to - reach specified target behaviour, and optionally profiling it. - For best results on a CRT, you should run this against a neutral - grey desktop background, and avoid having any bright images or - windows on the screen at the time you run dispcal. You could also - use the -B option to black - the whole screen out, although this will make it impossible to - control dispcal unless you have more than one display.
-
- The -v flag reports progress information, - as well as other statistics about the progress of calibration. A - numerical argument greater than 1 gives greater verbosity. 2 will - give per step adjustment and repeat information, while 3 will give - even greater technical detail.
-
- When running on a UNIX based system that used - the X11 Windowing System, dispcal will by default use the - $DISPLAY environment variable to determine which local or remote - display and screen to read from. This can be overridden by supplying - an X11 display name to the -display - option. Note that if Xinerama is active, you can't select the screen - using $DISPLAY or -display, you have to select it using the -d parameter.
-
- By default the main display will be the location of - the test window. If the system has more than one display or screen, - an alternate display/screen can be selected with the -d parameter. If you invoke dispcal so as to display the - usage information (i.e. "dispcal -?" or "dispcal --"), then the - discovered displays/screens will be listed. Multiple displays may - not be listed, if they appear as a single display to the operating - system (ie. the multi-display support is hidden in the video card - driver). On UNIX based system that used the X11 Windowing System, - the -d parameter will - override the screen specified by the $DISPLAY or parameter.
-
- Note that if VideoLUTs for a - display are not accessible (i.e. no hardware calibration - capability), dispcal will - will issue a warning, but continue creating a calibration based on - the display "as-is" rather than its native response. See the -o flag for an explanation of the - implications of having no access to the VideoLUTs.
-
- On X11 the inability to access VideoLUTs could be because you are - trying to access a remote display, and the remote display doesn't - support the XF86VidMode extension, or perhaps you are running - multiple monitors using NVidia TwinView, or MergedFB, and trying to - access anything other than the primary monitor. TwinView and - MergedFB don't properly support the XF86VidMode extension for - multiple displays. You can use dispwin -r - to test whether the VideoLUTs are accessible for a particular - display. See also below, on how to select a different display for - VideoLUT access. Also note that dispcal will fail if the Visual - depth doesn't match the VideoLUT depth. Typically the VideoLUTs have - 256 entries per color component, so the Visual generally needs to be - 24 bits, 8 bits per color component.
-
- Because of the difficulty cause by TwinView and - MergedFB in X11 based systems, you can optionally specify a separate - display number after the display that is going to be used to present - test patches, for accessing the VideoLUT hardware. This must be + + Base name for created + or updated .cal and .icm output files
+
+

Comments
+

+ This is the tool is used for adjusting and calibrating a display to + reach specified target behaviour, and optionally profiling it. + For best results on a CRT, you should run this against a neutral + grey desktop background, and avoid having any bright images or + windows on the screen at the time you run dispcal. You could also + use the -B option to black + the whole screen out, although this will make it impossible to + control dispcal unless you have more than one display.
+
+ The -v flag reports progress information, + as well as other statistics about the progress of calibration. A + numerical argument greater than 1 gives greater verbosity. 2 will + give per step adjustment and repeat information, while 3 will give + even greater technical detail.
+
+ When running on a UNIX based system that used + the X11 Windowing System, dispcal will by default use the + $DISPLAY environment variable to determine which local or remote + display and screen to read from. This can be overridden by supplying + an X11 display name to the -display + option. Note that if Xinerama is active, you can't select the screen + using $DISPLAY or -display, you have to select it using the -d parameter.
+
+ By default the main display will be the location of + the test window. If the system has more than one display or screen, + an alternate display/screen can be selected with the -d parameter. If you invoke dispcal so as to display the + usage information (i.e. "dispcal -?" or "dispcal --"), then the + discovered displays/screens will be listed. Multiple displays may + not be listed, if they appear as a single display to the operating + system (ie. the multi-display support is hidden in the video card + driver). On UNIX based system that used the X11 Windowing System, + the -d parameter will + override the screen specified by the $DISPLAY or parameter.
+
+ Note that if VideoLUTs for a + display are not accessible (i.e. no hardware calibration + capability), dispcal will + will issue a warning, but continue creating a calibration based on + the display "as-is" rather than its native response. See the -o flag for an explanation of the + implications of having no access to the VideoLUTs.
+
+ On X11 the inability to access VideoLUTs could be because you are + trying to access a remote display, and the remote display doesn't + support the XF86VidMode extension, or perhaps you are running + multiple monitors using NVidia TwinView, or MergedFB, and trying to + access anything other than the primary monitor. TwinView and + MergedFB don't properly support the XF86VidMode extension for + multiple displays. You can use dispwin -r + to test whether the VideoLUTs are accessible for a particular + display. See also below, on how to select a different display for + VideoLUT access. Also note that dispcal will fail if the Visual + depth doesn't match the VideoLUT depth. Typically the VideoLUTs have + 256 entries per color component, so the Visual generally needs to be + 24 bits, 8 bits per color component.
+
+ Because of the difficulty cause by TwinView and + MergedFB in X11 based systems, you can optionally specify a separate + display number after the display that is going to be used to present + test patches, for accessing the VideoLUT hardware. This must be specified as a single string, e.g. -d @@ -2399,273 +2399,273 @@ none, - - 1,2 . Some experimentation may be needed using dispwin on such systems, to discover what - screen has access to the VideoLUT hardware, and which screens the - test patches appear on. You may be able to calibrate one screen, and - then share the calibration with another screen. Profiling can be - done independently to calibration on each screen.
-
- -dweb or - -dweb:port starts a - standalone web server on your machine, which then allows a local or - remote web browser to display the the color test patches. By default - port 8080 is used, but this - can be overridden by appending a : - and the port number i.e. -dweb:8001. - The URL will be http:// - then name of the machine or its I.P. address followed by a colon and - the port number - e.g something like http://192.168.0.1:8080. If you use the verbose - option (-v) then a likely - URL will be printed once the server is started, or you could run ipconfig (MSWin) or /sbin/ifconfig (Linux or OS X) - and identify an internet address for your machine that way. JavaScript - needs to be enabled in your web browser for this to work. You may - have to modify any firewall to permit port 8080 to be accessed on - your machine.
-
- Note that if you use this method of displaying test patches, that - there is no access to the display VideoLUTs and that the colors will - be displayed with 8 bit per component precision, and any - screen-saver or power-saver will not be disabled. You will also be - at the mercy of any color management applied by the web browser, and - may have to carefully review and configure such color management. - See the -o flag for an explanation of the - implications of having no access to the VideoLUTs.
-
- -dmadvr - [MSWin only] causes test patches to be displayed using the MadVR - video renderer. Note that will have to start MadTPG before - running dispcal, and that while you can adjust the "Test Pattern - Configuration" controls, you should not normally alter the - "Existing Calibration" controls, as dispcal will set these - appropriately.
-
- -dcc or -dcc:no - causes test patches to be displayed using and available ChromeCast to - your TV. Use -dcc:? to display a list of ChromeCasts on your - local network. Note that the ChromeCast as a test patch source is - probably the least accurate of your choices, since it - up-samples the test patch and transforms from RGB to YCC and back, - but should be accurate within � 1 bit. You may have to modify any - firewall to permit port 8081 to be accessed on your machine if it + + 1,2 . Some experimentation may be needed using dispwin on such systems, to discover what + screen has access to the VideoLUT hardware, and which screens the + test patches appear on. You may be able to calibrate one screen, and + then share the calibration with another screen. Profiling can be + done independently to calibration on each screen.
+
+ -dweb or + -dweb:port starts a + standalone web server on your machine, which then allows a local or + remote web browser to display the the color test patches. By default + port 8080 is used, but this + can be overridden by appending a : + and the port number i.e. -dweb:8001. + The URL will be http:// + then name of the machine or its I.P. address followed by a colon and + the port number - e.g something like http://192.168.0.1:8080. If you use the verbose + option (-v) then a likely + URL will be printed once the server is started, or you could run ipconfig (MSWin) or /sbin/ifconfig (Linux or OS X) + and identify an internet address for your machine that way. JavaScript + needs to be enabled in your web browser for this to work. You may + have to modify any firewall to permit port 8080 to be accessed on + your machine.
+
+ Note that if you use this method of displaying test patches, that + there is no access to the display VideoLUTs and that the colors will + be displayed with 8 bit per component precision, and any + screen-saver or power-saver will not be disabled. You will also be + at the mercy of any color management applied by the web browser, and + may have to carefully review and configure such color management. + See the -o flag for an explanation of the + implications of having no access to the VideoLUTs.
+
+ -dmadvr + [MSWin only] causes test patches to be displayed using the MadVR + video renderer. Note that will have to start MadTPG before + running dispcal, and that while you can adjust the "Test Pattern + Configuration" controls, you should not normally alter the + "Existing Calibration" controls, as dispcal will set these + appropriately.
+
+ -dcc or -dcc:no + causes test patches to be displayed using and available ChromeCast to + your TV. Use -dcc:? to display a list of ChromeCasts on your + local network. Note that the ChromeCast as a test patch source is + probably the least accurate of your choices, since it + up-samples the test patch and transforms from RGB to YCC and back, + but should be accurate within � 1 bit. You may have to modify any + firewall to permit port 8081 to be accessed on your machine if it falls back to the Default receiver (see installation - - instructions for your platform).
-
- -c The - instrument is assumed to communicate through a USB or serial - communication port, and the port can be selected with the -c - option, if the instrument is not connected to the first port. If you - invoke dispcal so as to - display the usage information (i.e. "dispcal -?" or "dispcal --"), - then the discovered USB and serial ports will be listed. On - UNIX/Linux, a list of all possible serial ports are shown, but not - all of them may actually be present on your system.
-
- The -r and - -R flags - perform a quick measurement of current display behaviour, reports - and then exits. If the -r - flag is used the measurement are taken using the currently loaded - calibration (Video LUT) curves, and in the case of MadVR renderer - test patch display the Color Management 3dLut. If -R is use, then the uncalibrated - ("raw" or "native") behaviour is measured (ie. no VideoLut or CM). - Reported are:
-
-     Black Brightness in cd/m^2
-     White Brightness in cd/m^2
-     The approximate Gamma
-     The white point x,y chromaticity co-ordinates
-     The correlated color temperature in Kelvin, and - the CIEDE200 to the Black Body locus.
-     The correlated Daylight temperature in Kelvin, - and the CIEDE200 to the Daylight locus.
-     The visual color temperature in Kelvin, and the - CIEDE200 to the Black Body locus.
-     The visual Daylight temperature in Kelvin, and - the CIEDE200 to the Daylight locus.
-     The visual color temperature in Kelvin
- (for -R "raw":)
-     The apparent VideoLUT entry number of significant - bits.
-
- Note that the correlated color temperature is the temperature of a - black body radiator that has the closest color to the white point - measured using the traditional CIE 1960 UCS space color difference - formula. The correlated daylight temperature is a similar thing, - except the CIE daylight locus is used. The visual color temperature - values are calculated similarly to the correlated color - temperatures, but using the modern CIEDE2000 color difference - formula to calculate a better visual approximation to the closest - temperature to the displays white point. There will be no difference - between the UCS and CIEDE2000 temperatures if the display white - point actually lies on the particular locus.
-
- The -m - option skips the usual process of adjusting the display monitor - contrast, brightness and white point controls, and skips straight to - calibration.
-
- -o [profile.icm] Normally dispcal creates just a - calibration file, which can then be used for subsequent - characterization using dispread and - profiling using colprof. If the -o flag is used, dispcal will also create a - shaper/matrix profile. By default it will create a profile named inoutfile.icm, but a differently - named file can be created or updated by specifying the name after - the -o flag. If the -u flag is used with -o, then the ICC profile vcgt calibration curves will be - updated.
-
- Note that if VideoLUT access is not possible for the display, that - hardware calibration is not possible. dispcal will create - calibration curves anyway with a warning, and if a profile is - created, it will not contain a 'vcgt' tag, but instead will have the - calibration curves incorporated into the profile itself. If - calibration parameters are chosen that change the displays white - point or brightness, then this will result in a slightly unusual - profile that has a white point that does not correspond with - R=G=B=1.0. Some systems may not cope properly with this type of - profile. See the tutorial for a - further explanation.
-
- The -O parameter allows setting of the - shaper/matrix profile description tag. The parameter should be a - string that describes the device and profile. With most command line - shells, it will be necessary to enclose the parameter with double - quotes, so that spaces and other special characters are included in - the parameter, and not mistaken for the start of another flag, or as - a final command line parameter. Many programs that deal with ICC - profiles use the description tag to identify a profile, rather than - the profile filename, so using a descriptive string is important in - being able to find a profile. By default, the profile file name will - be used as the description.
-
- -u Normally - dispcal creates a new - calibration file and optional profile, based on the requested - targets and the response of the display. This can take a fair amount - of time, particularly if a high quality level has been selected, so - to speed up the process of keeping a display in calibration the -u flag can be used. This uses - the same calibration targets as the previous calibration but does a - smaller number of refinement passes, enough to improve the accuracy - of the calibration to account for drift in the device. If the -o flag is used as well, then - the ICC profile will have - its vcgt tag updated with the new calibration. This keeps the - profile up to date with the display. Normally dispcal -u will use the same - quality level that was specified in the previous calibration, but - this can be overridden using the -q - flag. Any options that attempt to change the calibration target (ie. - white point, brightness, gamma etc.) will be ignored. Adjustment of - the display monitor controls is skipped. A profile cannot be updated - if the display does not support hardware calibration (no VideoLUT - access).
-
- Quality - Low, Medium (def), High. The -q flag determines how much time - and effort to go to in calibrating the display. The higher the - quality, the more test readings will be done, the more refinement - passes will be done, the tighter will be the accuracy tolerance, and - the more detailed will be the calibration of the display. The result - will ultimately be limited by the accuracy of the instrument, the - repeatability of the display and instrument, and the resolution of - the Video Lookup table entries and Digital or Analogue output - (RAMDAC).
-
- The -p flag - allows measuring in telephoto mode, using instruments that support - this mode, e.g. the ColorMunki. Telephoto mode is one for taking - emissive measurements from a distance (ie. telespectometer, - tele-colorimeter) mode, and typically would be used for measuring - projector type displays. If a device does not support a specific - telephoto mode, then the normal emissive mode may be suitable for - measuring projectors.
-
- The -y - flag allows setting the Display Type. The selection typically - determines two aspects of of the instrument operation: 1) It may set the measuring mode - to suite refresh or non-refresh displays. - Typically only LCD (Liquid Crystal) displays have a non-refresh - nature. 2) It may select an - instrument calibration matrix suitable for a particular display - type. The selections available depends on the type and model of - instrument, and a list of the options for the discovered instruments - will be shown in the usage - information. For more details on what particular instruments support - and how this works, see Operation of - particular instruments. 3) Any installed CCSS files - (if applicable), or CCMX files. These files are typically created - using ccxxmake, and installed using oeminst. The default and Base Calibration - types will be indicated in the usage.
-
- -t Set the target white point - locus to the equivalent of a Daylight spectrum of the given - temperature in degrees Kelvin. By default the white point target - will be the native white of the display, and it's color temperature - and delta E to the daylight spectrum locus will be shown during - monitor adjustment, and adjustments will be recommended to put the - display white point directly on the Daylight locus. If a Daylight - color temperature is given as an argument to -t, then this will become the - target of the adjustment, and the recommended adjustments will be - those needed to make the monitor white point meet the target. - Typical values might be 5000 for matching printed output, or - 6500, which gives a brighter, bluer look. A white point temperature - different to that native to the display may limit the maximum - brightness possible.
-
- -T Same functionality as - the -t option, except the - white point locus will be the Black Body, or Planckian locus, rather - than the Daylight locus. While these two white point loci are quite - close, they are subtly different. If a temperature is given as an - argument, this will become the Black Body target temperature during - adjustment.
-
- -w An - alternative to specifying a white point target in Daylight or - Black Body degrees Kevin, is to specify it in chromaticity - co-ordinates. This allows the white point to be a color other than - one on the Daylight or Black Body. Note that the x,y numbers must be - specified as a single string (no space between the numbers and the - comma).
-
- -b Set - the target brightness of white in cd/m^2. If this number cannot be - reached, the brightest output possible is chosen, consistent with - matching the white point target. Note that many of the instruments - are not particularly accurate when assessing the absolute display - brightness in cd/m^2. NOTE - that some LCD screens behave a little strangely near their absolute - white point, and may therefore exhibit odd behavior at values just - below white. It may be advisable in such cases to set a brightness - slightly less than the maximum such a display is capable of.
-
+ + instructions for your platform).
+
+ -c The + instrument is assumed to communicate through a USB or serial + communication port, and the port can be selected with the -c + option, if the instrument is not connected to the first port. If you + invoke dispcal so as to + display the usage information (i.e. "dispcal -?" or "dispcal --"), + then the discovered USB and serial ports will be listed. On + UNIX/Linux, a list of all possible serial ports are shown, but not + all of them may actually be present on your system.
+
+ The -r and + -R flags + perform a quick measurement of current display behaviour, reports + and then exits. If the -r + flag is used the measurement are taken using the currently loaded + calibration (Video LUT) curves, and in the case of MadVR renderer + test patch display the Color Management 3dLut. If -R is use, then the uncalibrated + ("raw" or "native") behaviour is measured (ie. no VideoLut or CM). + Reported are:
+
+     Black Brightness in cd/m^2
+     White Brightness in cd/m^2
+     The approximate Gamma
+     The white point x,y chromaticity co-ordinates
+     The correlated color temperature in Kelvin, and + the CIEDE200 to the Black Body locus.
+     The correlated Daylight temperature in Kelvin, + and the CIEDE200 to the Daylight locus.
+     The visual color temperature in Kelvin, and the + CIEDE200 to the Black Body locus.
+     The visual Daylight temperature in Kelvin, and + the CIEDE200 to the Daylight locus.
+     The visual color temperature in Kelvin
+ (for -R "raw":)
+     The apparent VideoLUT entry number of significant + bits.
+
+ Note that the correlated color temperature is the temperature of a + black body radiator that has the closest color to the white point + measured using the traditional CIE 1960 UCS space color difference + formula. The correlated daylight temperature is a similar thing, + except the CIE daylight locus is used. The visual color temperature + values are calculated similarly to the correlated color + temperatures, but using the modern CIEDE2000 color difference + formula to calculate a better visual approximation to the closest + temperature to the displays white point. There will be no difference + between the UCS and CIEDE2000 temperatures if the display white + point actually lies on the particular locus.
+
+ The -m + option skips the usual process of adjusting the display monitor + contrast, brightness and white point controls, and skips straight to + calibration.
+
+ -o [profile.icm] Normally dispcal creates just a + calibration file, which can then be used for subsequent + characterization using dispread and + profiling using colprof. If the -o flag is used, dispcal will also create a + shaper/matrix profile. By default it will create a profile named inoutfile.icm, but a differently + named file can be created or updated by specifying the name after + the -o flag. If the -u flag is used with -o, then the ICC profile vcgt calibration curves will be + updated.
+
+ Note that if VideoLUT access is not possible for the display, that + hardware calibration is not possible. dispcal will create + calibration curves anyway with a warning, and if a profile is + created, it will not contain a 'vcgt' tag, but instead will have the + calibration curves incorporated into the profile itself. If + calibration parameters are chosen that change the displays white + point or brightness, then this will result in a slightly unusual + profile that has a white point that does not correspond with + R=G=B=1.0. Some systems may not cope properly with this type of + profile. See the tutorial for a + further explanation.
+
+ The -O parameter allows setting of the + shaper/matrix profile description tag. The parameter should be a + string that describes the device and profile. With most command line + shells, it will be necessary to enclose the parameter with double + quotes, so that spaces and other special characters are included in + the parameter, and not mistaken for the start of another flag, or as + a final command line parameter. Many programs that deal with ICC + profiles use the description tag to identify a profile, rather than + the profile filename, so using a descriptive string is important in + being able to find a profile. By default, the profile file name will + be used as the description.
+
+ -u Normally + dispcal creates a new + calibration file and optional profile, based on the requested + targets and the response of the display. This can take a fair amount + of time, particularly if a high quality level has been selected, so + to speed up the process of keeping a display in calibration the -u flag can be used. This uses + the same calibration targets as the previous calibration but does a + smaller number of refinement passes, enough to improve the accuracy + of the calibration to account for drift in the device. If the -o flag is used as well, then + the ICC profile will have + its vcgt tag updated with the new calibration. This keeps the + profile up to date with the display. Normally dispcal -u will use the same + quality level that was specified in the previous calibration, but + this can be overridden using the -q + flag. Any options that attempt to change the calibration target (ie. + white point, brightness, gamma etc.) will be ignored. Adjustment of + the display monitor controls is skipped. A profile cannot be updated + if the display does not support hardware calibration (no VideoLUT + access).
+
+ Quality - Low, Medium (def), High. The -q flag determines how much time + and effort to go to in calibrating the display. The higher the + quality, the more test readings will be done, the more refinement + passes will be done, the tighter will be the accuracy tolerance, and + the more detailed will be the calibration of the display. The result + will ultimately be limited by the accuracy of the instrument, the + repeatability of the display and instrument, and the resolution of + the Video Lookup table entries and Digital or Analogue output + (RAMDAC).
+
+ The -p flag + allows measuring in telephoto mode, using instruments that support + this mode, e.g. the ColorMunki. Telephoto mode is one for taking + emissive measurements from a distance (ie. telespectometer, + tele-colorimeter) mode, and typically would be used for measuring + projector type displays. If a device does not support a specific + telephoto mode, then the normal emissive mode may be suitable for + measuring projectors.
+
+ The -y + flag allows setting the Display Type. The selection typically + determines two aspects of of the instrument operation: 1) It may set the measuring mode + to suite refresh or non-refresh displays. + Typically only LCD (Liquid Crystal) displays have a non-refresh + nature. 2) It may select an + instrument calibration matrix suitable for a particular display + type. The selections available depends on the type and model of + instrument, and a list of the options for the discovered instruments + will be shown in the usage + information. For more details on what particular instruments support + and how this works, see Operation of + particular instruments. 3) Any installed CCSS files + (if applicable), or CCMX files. These files are typically created + using ccxxmake, and installed using oeminst. The default and Base Calibration + types will be indicated in the usage.
+
+ -t Set the target white point + locus to the equivalent of a Daylight spectrum of the given + temperature in degrees Kelvin. By default the white point target + will be the native white of the display, and it's color temperature + and delta E to the daylight spectrum locus will be shown during + monitor adjustment, and adjustments will be recommended to put the + display white point directly on the Daylight locus. If a Daylight + color temperature is given as an argument to -t, then this will become the + target of the adjustment, and the recommended adjustments will be + those needed to make the monitor white point meet the target. + Typical values might be 5000 for matching printed output, or + 6500, which gives a brighter, bluer look. A white point temperature + different to that native to the display may limit the maximum + brightness possible.
+
+ -T Same functionality as + the -t option, except the + white point locus will be the Black Body, or Planckian locus, rather + than the Daylight locus. While these two white point loci are quite + close, they are subtly different. If a temperature is given as an + argument, this will become the Black Body target temperature during + adjustment.
+
+ -w An + alternative to specifying a white point target in Daylight or + Black Body degrees Kevin, is to specify it in chromaticity + co-ordinates. This allows the white point to be a color other than + one on the Daylight or Black Body. Note that the x,y numbers must be + specified as a single string (no space between the numbers and the + comma).
+
+ -b Set + the target brightness of white in cd/m^2. If this number cannot be + reached, the brightest output possible is chosen, consistent with + matching the white point target. Note that many of the instruments + are not particularly accurate when assessing the absolute display + brightness in cd/m^2. NOTE + that some LCD screens behave a little strangely near their absolute + white point, and may therefore exhibit odd behavior at values just + below white. It may be advisable in such cases to set a brightness + slightly less than the maximum such a display is capable of.
+
-g gamma Set @@ -2714,14 +2714,14 @@ Set - - the target response curve gamma. This is normally an exponential - curve (output = input ^gamma), and defaults to 2.4 on MSWindows and - Macintosh OS X 10.6 or latter and Linux/Unix (which is typical of a - CRT type displays real response), and 1.8 on a Macintosh (prior to - OS X 10.6). Four pre-defined curves can be used as well: the sRGB - colorspace response curve, which is an exponent curve with a - straight segment at the dark end and an overall response of + + the target response curve gamma. This is normally an exponential + curve (output = input ^gamma), and defaults to 2.4 on MSWindows and + Macintosh OS X 10.6 or latter and Linux/Unix (which is typical of a + CRT type displays real response), and 1.8 on a Macintosh (prior to + OS X 10.6). Four pre-defined curves can be used as well: the sRGB + colorspace response curve, which is an exponent curve with a + straight segment at the dark end and an overall response of approximately gamma 2.2 (-gs), the @@ -2770,65 +2770,65 @@ the - - L* curve, which is the response of the CIE L*a*b* perceptual - colorspace (-gl). the REC - 709 video standard response curve (-g709) - and the SMPTE 240M video standard response curve (-g240)
-
- Note that a real display - can't reproduce any of these ideal curves, since it will have a - non-zero black point, whereas all the ideal curves assume zero light - at zero input. In the case of a gamma curve target, dispcal uses an - actual technical power curve shape that aims for the same relative - output at 50% input as the ideal gamma power curve. To allow for the - non-zero black level of a real display, by default dispcal will offset the target - curve values so that zero input gives the actual black level of the - display (output offset). This ensures that the target curve better - corresponds to the typical natural behavior of displays, but it may - not be the most visually even progression from display minimum, but - this behavior can be changed using the -f option (see below).
-
- Also note that many color - spaces are encoded with, and labelled as having a gamma of - approximately 2.2 (ie. sRGB, - REC 709, SMPTE 240M, Macintosh OS X 10.6), but are actually intended - to be displayed on a display with a typical CRT gamma of 2.4 viewed in a darkened - environment. This is because this 2.2 - gamma is a source gamma encoding in bright viewing conditions such - as a television studio, while typical display viewing conditions are - quite dark by comparison, and a contrast expansion of (approx.) - gamma 1.1 is desirable to make the images look as intended. So if - you are displaying images encoded to the sRGB standard, or - displaying video through the calibration, just setting the gamma - curve to sRGB or REC 709 (respectively) is probably not what you want! What you - probably want to do, is to set the gamma curve to about gamma 2.4, - so that the contrast range is expanded appropriately, or alternatively - use sRGB or REC 709 or a gamm of 2.2 but also use the -a - parameter to specify the actual ambient viewing conditions, so that - dispcal can make an - appropriate contrast enhancement. If your instrument is capable of - measuring ambient light levels, then you can do so during the - interactive display control adjustment. See - <http://www.color.org/sRGB.xalter> for details of how sRGB is - intended to be used.
-
- It is hard to know whether Apple Macintosh computers prior to OS X - 10.6 should also have such an adjustment, since it is not really - possible to know whether colors labelled as being in such a - colorspace are actually encoded in that gamma with the expectation - that they will be displayed on a display with that actual response, - or whether they are intended to be displayed on a display that - contrast expands by a power 1.1. Both situations might be the - case, depending on how source material is created!
-
+ + L* curve, which is the response of the CIE L*a*b* perceptual + colorspace (-gl). the REC + 709 video standard response curve (-g709) + and the SMPTE 240M video standard response curve (-g240)
+
+ Note that a real display + can't reproduce any of these ideal curves, since it will have a + non-zero black point, whereas all the ideal curves assume zero light + at zero input. In the case of a gamma curve target, dispcal uses an + actual technical power curve shape that aims for the same relative + output at 50% input as the ideal gamma power curve. To allow for the + non-zero black level of a real display, by default dispcal will offset the target + curve values so that zero input gives the actual black level of the + display (output offset). This ensures that the target curve better + corresponds to the typical natural behavior of displays, but it may + not be the most visually even progression from display minimum, but + this behavior can be changed using the -f option (see below).
+
+ Also note that many color + spaces are encoded with, and labelled as having a gamma of + approximately 2.2 (ie. sRGB, + REC 709, SMPTE 240M, Macintosh OS X 10.6), but are actually intended + to be displayed on a display with a typical CRT gamma of 2.4 viewed in a darkened + environment. This is because this 2.2 + gamma is a source gamma encoding in bright viewing conditions such + as a television studio, while typical display viewing conditions are + quite dark by comparison, and a contrast expansion of (approx.) + gamma 1.1 is desirable to make the images look as intended. So if + you are displaying images encoded to the sRGB standard, or + displaying video through the calibration, just setting the gamma + curve to sRGB or REC 709 (respectively) is probably not what you want! What you + probably want to do, is to set the gamma curve to about gamma 2.4, + so that the contrast range is expanded appropriately, or alternatively + use sRGB or REC 709 or a gamm of 2.2 but also use the -a + parameter to specify the actual ambient viewing conditions, so that + dispcal can make an + appropriate contrast enhancement. If your instrument is capable of + measuring ambient light levels, then you can do so during the + interactive display control adjustment. See + <http://www.color.org/sRGB.xalter> for details of how sRGB is + intended to be used.
+
+ It is hard to know whether Apple Macintosh computers prior to OS X + 10.6 should also have such an adjustment, since it is not really + possible to know whether colors labelled as being in such a + colorspace are actually encoded in that gamma with the expectation + that they will be displayed on a display with that actual response, + or whether they are intended to be displayed on a display that + contrast expands by a power 1.1. Both situations might be the + case, depending on how source material is created!
+
-G gamma As @@ -2877,99 +2877,99 @@ As - - explained above, the gamma value provided to the -g option is used to set and - actual response curve that makes an allowance for the non-zero black - of the actual display, and will have the same relative output at 50% - input as the ideal gamma power curve, and so best matches typical - expectations. The -G option - is an alternative that allows the actual - power to be specified instead, meaning that when combined with the - displays non-zero black value, the response at 50% input will - probably not match that of the ideal power curve with that gamma - value.
-
- -f [degree]: - As explained in for the -g - and -G options, real - displays do not have a zero black response, while all the target - response curves do, so this has to be allowed for in some way. The - default way of handling this (equivalent to -f 1.0) is to - allow for this at the output of the ideal response curve, by - offsetting and scaling the output values. This defined a curve that will match the responses - that many other systems provide and may be a better match to the - natural response of the display, but will give a less visually even - response from black. The - other alternative is to offset and scale the input values into the - ideal response curve so that zero input gives the actual non-zero - display response. This ensures the most visually even progression - from display minimum, but might be hard to achieve since it is - different to the naturally response of a display. A subtlety is to - provide a split between how much of the offset is accounted for as - input to the ideal response curve, and how much is accounted for at - the output, and this can be done by providing a parameter -f degree, where the degree is - 0.0 accounts for it all as input offset, and 1.0 accounts for all of - it as output offset. If -f - is used without a specified degree, a degree of 0.0 is assumed, the - opposite of the default. Note - that using all input offset (degree == 0.0) is equivalent to the use - of the BT.1886 transfer - function.
-
- -a ambient: - As explained for the -g - parameter, often colors are encoded in a situation with viewing - conditions that are quite different to the viewing conditions of a - typical display, with the expectation that this difference in - viewing conditions will be allowed for in the way the display is - calibrated. The -a option - is a way of doing this. By default dispcal - will not make any allowances for viewing conditions, but will - calibrate to the specified response curve, but if the -a option is used, or the - ambient level is measured during the interactive display controls - portion of the calibration, an appropriate viewing conditions - adjustment will be performed. For a gamma value or sRGB, the - original viewing conditions will be assumed to be that of the sRGB - standard viewing conditions, while for REC 709 and SMPTE 240M they - will be assumed to be television studio viewing conditions. By - specifying or measuring the ambient lighting for your display, a - viewing conditions adjustment based on the CIECAM02 color appearance - model will be made for the brightness of your display and the - contrast it makes with your ambient light levels.
-
- -k factor: - Normally this will be set automatically, based on the measured black - level of the display. A -k - factor of 1.0 will make all colors down the neutral axis (R=G=B) - have the same hue as the chosen white point. Near the black point, - red, green or blue can only be added, not subtracted from zero, so - the process of making the near black colors have the desired hue, - will lighten them to some - extent. For a device with a good contrast ratio or a black point - that has nearly the same hue as the white, this should not affect - the contrast ratio too severely. If the device contrast ratio is not - so good, and the native black hue is noticeably different to that of - the chosen white point (which is often the case for LCD type displays, or CRT type displays with one - channel which has a poor level of black), this could have a - noticeably detrimental effect on an already limited contrast ratio, - and result in a black that is not as good as it can be, and a lower - -k factor should be used. -k values can range between 0.0 - (no correction of black) to 1.0 (full correction of black). If less - than full correction is chosen, then the resulting calibration - curves will have the target white point down most of the curve, but - will then blend over to the native or compromise black point that is - blacker, but not of the right hue. The rate of this blend can be - controlled with the -A - parameter (see below). For applications where maximum contrast ratio - is important (such as Video), use -k0.
-
+ + explained above, the gamma value provided to the -g option is used to set and + actual response curve that makes an allowance for the non-zero black + of the actual display, and will have the same relative output at 50% + input as the ideal gamma power curve, and so best matches typical + expectations. The -G option + is an alternative that allows the actual + power to be specified instead, meaning that when combined with the + displays non-zero black value, the response at 50% input will + probably not match that of the ideal power curve with that gamma + value.
+
+ -f [degree]: + As explained in for the -g + and -G options, real + displays do not have a zero black response, while all the target + response curves do, so this has to be allowed for in some way. The + default way of handling this (equivalent to -f 1.0) is to + allow for this at the output of the ideal response curve, by + offsetting and scaling the output values. This defined a curve that will match the responses + that many other systems provide and may be a better match to the + natural response of the display, but will give a less visually even + response from black. The + other alternative is to offset and scale the input values into the + ideal response curve so that zero input gives the actual non-zero + display response. This ensures the most visually even progression + from display minimum, but might be hard to achieve since it is + different to the naturally response of a display. A subtlety is to + provide a split between how much of the offset is accounted for as + input to the ideal response curve, and how much is accounted for at + the output, and this can be done by providing a parameter -f degree, where the degree is + 0.0 accounts for it all as input offset, and 1.0 accounts for all of + it as output offset. If -f + is used without a specified degree, a degree of 0.0 is assumed, the + opposite of the default. Note + that using all input offset (degree == 0.0) is equivalent to the use + of the BT.1886 transfer + function.
+
+ -a ambient: + As explained for the -g + parameter, often colors are encoded in a situation with viewing + conditions that are quite different to the viewing conditions of a + typical display, with the expectation that this difference in + viewing conditions will be allowed for in the way the display is + calibrated. The -a option + is a way of doing this. By default dispcal + will not make any allowances for viewing conditions, but will + calibrate to the specified response curve, but if the -a option is used, or the + ambient level is measured during the interactive display controls + portion of the calibration, an appropriate viewing conditions + adjustment will be performed. For a gamma value or sRGB, the + original viewing conditions will be assumed to be that of the sRGB + standard viewing conditions, while for REC 709 and SMPTE 240M they + will be assumed to be television studio viewing conditions. By + specifying or measuring the ambient lighting for your display, a + viewing conditions adjustment based on the CIECAM02 color appearance + model will be made for the brightness of your display and the + contrast it makes with your ambient light levels.
+
+ -k factor: + Normally this will be set automatically, based on the measured black + level of the display. A -k + factor of 1.0 will make all colors down the neutral axis (R=G=B) + have the same hue as the chosen white point. Near the black point, + red, green or blue can only be added, not subtracted from zero, so + the process of making the near black colors have the desired hue, + will lighten them to some + extent. For a device with a good contrast ratio or a black point + that has nearly the same hue as the white, this should not affect + the contrast ratio too severely. If the device contrast ratio is not + so good, and the native black hue is noticeably different to that of + the chosen white point (which is often the case for LCD type displays, or CRT type displays with one + channel which has a poor level of black), this could have a + noticeably detrimental effect on an already limited contrast ratio, + and result in a black that is not as good as it can be, and a lower + -k factor should be used. -k values can range between 0.0 + (no correction of black) to 1.0 (full correction of black). If less + than full correction is chosen, then the resulting calibration + curves will have the target white point down most of the curve, but + will then blend over to the native or compromise black point that is + blacker, but not of the right hue. The rate of this blend can be + controlled with the -A + parameter (see below). For applications where maximum contrast ratio + is important (such as Video), use -k0.
+
-A rate: If @@ -3018,641 +3018,641 @@ If - - the black point is not being set completely to the same hue as the - white point (ie. because the -k - factor is less than 1.0), then the resulting calibration curves will - have the target white point down most of the curve, but will then - blend over to the native or compromise black point that is blacker, - but not of the right hue. The rate of this blend can be controlled - with the -A parameter. The - default value 4.0, which results in a target that switches from the - white point target to the black, moderately close to the black - point. While this typically gives a good visual result with the - target neutral hue being maintained to the point where the crossover - to the black hue is not visible, it may be asking too much of some - displays (typically LCD type displays), and there may be some visual - effects due to inconsistent color with viewing angle. For this - situation a smaller value may give a better visual result (e.g. try - values of 3.0 or 2.0. A value of 1.0 will set a pure linear blend - from white point to black point). If there is too much coloration - near black, try a larger value, e.g. 6.0 or 8.0.
-
- The -b flag forces source 0,0,0 to map - to destination 0,0,0. This may be useful with displays that have a - very dark black point, and with an instrument is unable to measure - it precisely, and where it is known in some other way that the - display is very well behaved from black (i.e. that it has no - "dead zone" above zero device input). Using this option with a - display that is not well behaved, may result in a loss of - shadow detail. This will override any -k factor.
-
- -B Set - the target brightness of black in cd/m^2 (i.e. the absolute Y - value). Setting too high a value may give strange results as it - interacts with trying to achieve the target "advertised" gamma curve - shape. You could try using -f 1 if this causes a problem.
-
- -e [n] Run n verify passes on the final - curves. This is an extra set of instrument readings, that can be - used to estimate how well the device will match the targets with the - computed calibration curves. Note that the usefulness of the - verification is sometimes limited by the repeatability of the device - & instrument readings. This is often evident for CRT displays, - which (due to their refresh rate) flicker. More than one - verification pass can be done by providing the parameter n, and by then comparing the - successive verifications, some idea of the repeatability can be - ascertained. The verification uses a fixed number of semi-random - test values to test the calibration.
-
- -z 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. Note that if the initial - calibration was modified due to it being out of gamut of the - display, verify will show the resulting discrepancy. You can use dispwin to load a .cal file into the display - before running dispcal -z. - 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 -a parameter - for verify.
-
- The -P - parameter allows you to position and size the test patch window. By - default it is places in the center of the screen, and sized - appropriately for the type of instrument, or 10% of the width of the - display if the display size is unknown.. The ho and vo values govern the horizontal - and vertical offset respectively. A value of 0.0 positions the - window to the far left or top of the screen, a value of 0.5 - positions it in the center of the screen (the default), and 1.0 - positions it to the far right or bottom of the screen. If three - parameters are provided, then the ss - parameter is a scale factor for the test window size. A value of 0.5 - for instance, would produce a half sized window. A value of 2.0 will - produce a double size window. If four parameters are provided, then - the last two set independent horizontal and vertical scaling - factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be - specified as a single string (no space between the numbers and the - comma). For example, to create a double sized test window at the top - right of the screen, use -P 1,0,2 - . To create a window twice as wide as high: -P 1,0,2,1.
-
- The -F - flag causes the while screen behind the test window to be masked - with black. This can aid black accuracy when measuring CRT displays - or projectors.
-
- The -E - 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.
-
- -n When - running on a UNIX based system that used the X11 Windowing System, dispcal - normally selects the override redirect so that the test window will - appear above any other windows on the display. On some systems this - can interfere with window manager operation, and the -n - option turns this behaviour off.
-
- The -J - option runs through the black and sensor relative calibration - routines for the Xrite DTP92 and DTP94 instruments, the black level - calibration for the Eye-One Display 1, and a CRT frequency - calibration for the Eye-One Display 2. For the black calibration the - instrument should be placed on an opaque, black surface, and any - stray light should be avoided by placing something opaque over the - instrument. If a Spectrolino is being used, then a white and black - calibration will always be performed before the instrument can be - placed on the display, unless the -N - flag is used. Generally it is not necessary to do a calibration - every time an instrument is used, just now and again. There is also - no point in doing a CRT frequency calibration, as this will be - done automatically at the commencement of patch reading, and will be - lost between runs.
-
- -N Any - instrument that requires regular calibration will ask for - calibration on initial start-up. Sometimes this can be awkward if - the instrument is being mounted in some sort of measuring jig, or - annoying if several sets of readings are being taken in quick - succession. The -N - suppresses this initial calibration if a valid and not timed out - previous calibration is recorded in the instrument or on the host - computer. It is advisable to only use this option on the second and - subsequent measurements in a single session.
-
- The -H - option turns on high resolution spectral mode, if the instrument - supports it, such as the Eye-One Pro. See Operation of particular instruments - for more details. This may give better accuracy for display - measurements.
-
- The -X file.ccmx option reads - a Colorimeter Correction Matrix - from the given file, and applies it to the colorimeter instruments - readings. This can improve a colorimeters accuracy for a particular - type of display. A list of contributed ccmx files is here.
-
- The -X file.ccss option reads - a Colorimeter Calibration - Spectral Sample from the given file, and uses it to set the - colorimeter instruments calibration. This will only work with - colorimeters that rely on sensor spectral sensitivity calibration - information (ie. the X-Rite i1d3, - or the DataColor Spyder4 & - Spyder 5).This can improve a colorimeters accuracy for a - particular type of display.
-
- The -Q flag allows specifying a tristimulus - observer, and is used to compute PCS (Profile Connection Space) - tristimulus values from spectral readings or using a colorimeter - that has CCSS capability. The following choices are available:
- 1931_2 selects the standard CIE 1931 2 degree - observer. The default.
- 1964_10 selects the standard CIE 1964 10 degree - observer.
- 1955_2 selects the Stiles and Birch 1955 2 degree - observer
- 1978_2 selects the Judd and Voss 1978 2 degree - observer
- shaw selects the Shaw and Fairchild 1997 2 degree - observer
- 1964_10c selects a version of the CIE 1964 10 degree - observer that has been adjusted using a 3x3 matrix to better agree - with the 1931 2 degree observer.
-
- NOTE that if you select - anything other than the default 1931 2 degree observer, that the Y - values will not be cd/m^2, due to the Y curve not being the CIE 1924 - photopic V(λ) luminosity function.
-
- The -I b|w options invoke - instrument black level, and display white level compensation - (respectively). Instrument black level drift compensation attempts - to combat instrument black calibration drift by using a display - black test patch as a reference. If an instrument is not - acclimatised sufficiently to the measurement conditions, changes in - temperature can affect the black readings. Display white level drift - compensation attempts to combat changes in display brightness as it - warms up by measuring a white patch every so often, and using it to - normalise all the other readings. If just instrument black drift - compensation is needed, use -Ib. - If just display white level compensation is needed, use -Iw. If both are needed, use -Ibw or -Iwb.
-
- The -Y R:rate - 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.
-
- The -Y A - option uses a non-adaptive integration time emission measurement - mode, if the instrument supports it, such as the Eye-One Pro, - ColorMunki, i1d3 and K10. By default an adaptive integration time - measurement mode will be used for emission measurements, but some - instruments support a fixed integration time mode that can be used - with display devices. This may give faster measurement times, but - may also give less accurate low level readings.
-
- The -Y p - 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.
-
- The -C "command" option allows a - method of relaying each test value to some other display than that - on the system running dispcal (for instance, a photo frame, PDA - screen etc.), by causing the given command to be invoked to the - shell, with six arguments. The first three arguments are the RGB - test color as integers in the range 0 to 255, the second three - parameters are the RGB test color as floating point numbers in the - range 0.0 to 1.0. The script or tool should relay the given color to - the screen in some manner (e.g. by generating a raster file of the - given color and sending it to the display being profiled), before - returning. Note that a test window will also be created on the - system running dispread.
-
- The -M "command" option allows a - method of gathering each test value from some external source, such - as an instrument that is not directly supported by Argyll. The given - command is involked to the shell, with six arguments. The first - three arguments are the RGB test color as integers in the range 0 to - 255, the second three parameters are the RGB test color as floating - point numbers in the range 0.0 to 1.0. The script or tool should - create a file called "command.meas" - that contains the XYZ values for the given RGB (or measured from the - test window) in cd/m^2 as three numbers separated by spaces, before - returning. If the command returns a non-zero return value, dispcal - will abort. Note that a test window will also be created on the - system running dispcal.
-
- The -W n|h|x - parameter overrides the default serial communications flow control - setting. The value n turns - all flow control off, h - sets hardware handshaking, and x - sets Xon/Xoff handshaking. This commend may be useful in workaround - serial communications issues with some systems and cables.
-
- The -D 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.
-
- inoutfile - The final parameter on the command line is the base filename for the - .cal file and the optional ICC - profile. Normally this will be created (or an existing file will be - overwritten). If the -u - flag is used, then these files will be updated. If a different ICC - profile name needs to be specified, do so as an argument to the -o flag.
-
- NOTE that on an X11 system, - if the environment variable ARGYLL_IGNORE_XRANDR1_2 - is set (ie. set it to "yes"), then the presence of the XRandR 1.2 - extension will be ignored, and other extensions such as Xinerama and - XF86VidMode extension will be used. This may be a way to work around - buggy XRandR 1.2 implementations.
-
-

Discussion and guide to display control - adjustment:

-
- The adjustment of the display controls (brightness, contrast, R, G - & B channel controls etc.) is very dependent on the particular - monitor. Different types and brands of monitors will have different - controls, or controls that operate in different ways. Some displays - have almost no user controls, and so you may well be best skipping - display adjustment, and going straight to calibration.
-
- Almost all LCD displays lack a real contrast control. Those that do present such a - control generally fake it by adjusting the video signal. For this - reason it is usually best to set an LCD's contrast control at its neutral setting (ie. the - setting at which it doesn't change the video signal). Unfortunately, - it can be hard to know what this neutral setting is. On some - displays it is 50%, others 75%. If the LCD display has a "reset to - factory defaults" mode, then try using this first, as a way of - setting the contrast - control to neutral. The LCD brightness - control generally adjusts the level of backlighting the display - gets, which affects the maximum brightness, and also tends to raise - or lower the black level in proportion, without changing the - displays response curve shape or overall contrast ratio. If your LCD - display has a backlight - control as well as a brightness - control, then the brightness control is also probably being faked, - and you are probably better off setting it to it's neutral setting, - and using the backlight - control in place of brightness - in the following adjustments.
-
- Some high end displays have the ability to mimic various standard - colorspaces such as sRGB or AdobeRGB. You could choose to calibrate - and profile the display in such an emulation mode, although you - probably don't want to fight the emulations white point and gamma. - To get the best out of such a display you really want to choose it's - "Native Gamut" setting, whatever that is called. Note that some - people have reported bad experiences in trying to use "6-axis custom - controls" on displays such as the Dell U2410, so attempting to use - such a mode should be approached with caution. Ideally such a mode - should be used to give just the underlying native display response, - but the settings to achieve this may be very difficult to determine, - and/or it may not be possible, depending on how such a mode distorts - the RGB signals.
-
- On CRT based displays, the brightness - control generally adjusts the black level of the display (sometimes - called the offset), and as - a side effect, tends to change the maximum brightness too. A CRT contrast control generally - adjusts the maximum brightness (sometimes called gain) without affecting the - black level a great deal. On a CRT both the brightness and contrast controls will tend to - affect the shape or gamma of the display response curve.
-
- Many displays have some sort of color temperature adjustment. This - may be in the form of some pre-set color temperatures, or in the - form of individual Red, Green and Blue channel gain adjustments. - Some CRT displays also have R, G & B channel offset adjustments - that will affect the color temperatures near black, as well as - affect the individual channels curve shape. The color temperature - adjustment will generally affect the maximum brightness, and may - also affect the black level and the shape of the display response - curves.
-
- Some special (expensive) LCD displays may have a white point - adjustment that changes the color of the backlight. If you do not - have one of these types of LCD displays, then attempting to change - the white point of the display (even if it appears to have a "white point selection" or R/G/B "gain" controls") may not be a good idea, as once - again these controls are probably being faked by manipulating the - signal levels. Even if you do manage to change the white point - significantly, it may do things like change the mid tone color too - dramatically, or create a display response that is hard to correct - with calibration, or results in side effects such as quantization - (banding) or other undesirable effects. You may have to try out - various controls (and your aim points for the display calibration), - to decide what is reasonable to attempt on an LCD display.
-
- Due to the variety of controls as well as the interaction between - them, it can be an iterative process to arrive at a good monitor - set-up, before proceeding on to calibrating and profiling a display. - For this reason, dispcal - offers a menu of adjustment modes, so that the user can - interactively and iteratively adjust the display controls to meet - the desired targets.
-
- 1) Black level (CRT: Brightness)
- 2) White point (Color temperature, R,G,B, Gain/Contrast)
- 3) White level (CRT: Gain/Contrast, LCD: - Brightness/Backlight)
- 4) Black point (R,G,B, Offset/Brightness)
- 5) Check all
- 6) Measure and set ambient for viewing condition adjustment
- 7) Continue on to calibration
- 8) Exit
-
- There are four basic adjustment modes. Normally one would proceed - through them in the order above, then perhaps repeat the first - adjustment, before checking the overall settings. The White point - and White level modes operate slightly differently, depending on - whether a white target point has been set using the -t -T or -w options, and on whether a - brightness target has been set using the -b option.
-
-
- The first mode lets you adjust the black level of a CRT display. - Given the current white level, it calculates a value that should - produce a 1% display brightness if the black level is set correctly. - After doing some initial measurements, it will show the target - brightness value (in cd/m^2) on one line, and then underneath it - will show continuously updated readings from the display. The left - most character will switch from '\' to '/' or back again each time a - reading is updated. Some instruments can be quite slow in measuring - dark colors, and it's best to wait for a reading update before - changing the controls more than once. Underneath the target value is - displayed the current reading, and to the right of this is a '+', - '-' or '=' symbol, which gives a hint as to which way to adjust the - brightness control to improve the match to the target.
-
- Adjust CRT brightness to get target level. - Press space when done.
-    Target - 0.60
- / Current 0.68 - -
-
- Once happy with the adjustment, press space to go back to the menu.
-
-
- The second mode lets you adjust the color of the white point of the - display. If a target white point has been set, it will show the - target brightness value (in cd/m^2) on one line, together with the - target chromaticity co-ordinates for the white point, and then - underneath it will show continuously updated readings from the - display. The left most character will switch from '\' to '/' or back - again each time a reading is updated. Underneath the target - brightness value is displayed the current reading, and then the - current chromaticity co-ordinate values. To the right of this is the - current delta E of the white point from the target, and further to - the right are hints '+', '-' or '=' as to which direction to - adjust the individual Red, Green and Blue gain settings to move the - white point in the direction of the target, and reduce the delta E. - If the symbol is doubled, then this channel will have the greatest - effect. If you do not have individual channel gain controls, then - try choosing amongst color temperature pre-sets, to find one with - the lowest delta E. Depending on the stability of the display, the - coarseness of the controls, and the repeatability of the instrument, - you may not be able to get a perfectly zero delta E.
-
-    Adjust R,G & B gain to get - target x,y. Press space when done.
-    Target B 60.00, x 0.3451, y 0.3516
- / Current B 60.05, x 0.3426, y 0.3506 DE - 1.4 R+ G+ B--
-
- If you did not set a white point target, then the information shown - is a little different - it will show the initial white point value, - as well as the color temperature, and the CIEDE2000 of the white - point to either the Daylight or Black Body locus (depending on - whether the -T flag was - set). The constantly updated values show the same thing, and the - Red, Green and Blue control hints show the direction to adjust the - controls to place the white point on the locus. The control that - will have the most direct effect on the color temperature will be - the Blue, while the Green will most directly move the white point - towards or away from the locus, thereby reducing the delta E of the - white point to the locus (but there is interaction).
-
- Adjust R,G & B gain to desired white point. - Press space when done.
- Initial B 47.25, x - 0.3417, y 0.3456, CDT 5113 DE 6.9
- \ Current B 47.38, x 0.3420, - y 0.3460 CDT 5104 DE 6.7 R-- G+ B-
-
- The brightness value is just there as a guide to what effect - the adjustment is having on the overall brightness. Usually the - white level brightness is adjusted using the next adjustment mode. - Once happy with the adjustment, press space to go back to the menu.
-
-
- The third mode lets you adjust the brightness of white on the - display. If you set a target brightness using the -b - parameter, it will show the target brightness value (in cd/m^2) on - one line, and then underneath it will show continuously updated - readings from the display. The left most character will switch from - '\' to '/' or back again each time a reading is updated. Underneath - the target value is displayed the current reading, and to the right - of this is a '+', '-' or '=' symbol, which gives a hint as to which - way to adjust the CRT contrast or LCD brightness control to improve - the match to the target.
-
-    Adjust CRT Contrast or LCD - Brightness to get target level. Press space when done.
-    Target 60.00
- / Current 59.96 +
-
- If you did not set a brightness target, it will show the initial - brightness as the target, and the current brightness, which you can - then set any way you want:
-
- Adjust CRT Contrast or LCD Brightness to desired - level. Press space when done.
- Initial 47.32
- / Current 47.54
-
- Once happy with the adjustment, press space to go back to the menu.
-
-
- The fourth mode lets you adjust the color of the black point of the - display, if the display has Red, Green and Blue channel offset - controls. It will show the target 1% brightness value (in cd/m^2) on - one line, together with the target chromaticity co-ordinates for the - black point, and then underneath it will show continuously updated - readings from the display. The left most character will switch from - '\' to '/' or back again each time a reading is updated. Underneath - the target brightness value is displayed the current reading, and - then the current chromaticity co-ordinate values. To the right of - this is the current delta E of the black point from the target, and - further to the right are hints '+', '-' or '=' as to which - direction to adjust the individual Red, Green and Blue offset - settings to move the black point in the right direction. If the - symbol is doubled, then this channel will have the greatest effect. -
-
- Adjust R,G & B offsets to get target x,y. - Press space when done.
-    Target B 0.60, x 0.3451, y 0.3516
- \ Current B 0.62, x 0.2782, y 0.2331 DE - 10.3 R+ G++ B-
-
- The 1% brightness value is just there as a guide to what - effect the adjustment is having on the 1% brightness level. The - combined channel offsets may have an effect on this in combination - with the CRT brightness control. Press space to go back to the menu.
-
-
- The fifth selection checks on the overall settings. If targets - have been set, it will be like:
-
- Target Brightness = 50.00, Current = 47.44, - error = -5.1%
- Target 50% Level = 10.32, Current = 8.10, - error = -4.4%
- Target Near Black = 0.47, Current = 0.68, - error = 0.4%
- Target white = x 0.3458, y 0.3586, Current = x 0.3420, y - 0.3454, error = 7.55 DE
- Target black = x 0.3458, y 0.3586, Current = x 0.2908, y - 0.2270, error = 29.69 DE
-
- or if no targets are set:
-
- Current Brightness = 46.28
- Target 50% - Level = 10.07, Current = 7.52, error = -5.5%
- Target Near Black - = 0.46, Current = 0.46, error = -0.0%
- Current white = x - 0.3439, y 0.3466, VCT 5098K DE 3.0
- Target black = x - 0.3439, y 0.3466, Current = x 0.3093, y 0.2165, error = 30.30 DE
-
- and will then go back to the menu.
-
- The sixth selection 6) - allows the reading of you ambient lighting conditions if your - instrument supports such a mode. Doing so will enable the -a option to compensate for your - viewing conditions in the subsequent calibration. See -a.
-
- Once you're happy with the display set-up, you can either - proceed on to the rest of the calibration by selecting 7), or exit and re-start by - selecting 8). You might - want to re-start if you want to change the calibration targets.
-
-

Other caveats:

- NOTE that some LCD screens - behave a little strangely near their absolute white point, and may - therefore exhibit odd behavior at values just below white. It may be - advisable in such cases to set a brightness slightly less than the - maximum such a display is capable of.
-
- The program attempts to stop any screensaver or powersaver from - interfering with the measurements, but this may not be effective on - some systems, so it may be necessary to manually disable the - screensaver and/or powersaver before commencing the calibration with - a large number of patches.
-
- The calibration tables produced maintain the maximum level of - precision available on a system. If the display has VideoLUTs - available (Video Lookup Tables that the frame buffer values pass - through on their way to the display) and thier outputs are better - than 8 bits per component, then the resulting curves can reflect - this, although few current operating systems and/or display cards - actually support better than 8 bit per component output.
-
- If calibration curves are created for a display in which VideoLUTs - are not available, then the resulting calibration file will be - marked to indicate this, and a subsequent profile created with the - calibration will not have the calibration converted to the 'vcgt' - tag, since such a tag can't be loaded into the displays VideoLUTs.
-
- If communications break down with a USB connected instrument, you - may have to unplug it, and plug it in again to recover operation.
-
- Some systems (Apple OS X in particular) have a special set of user - interface controls ("Universal Access") that allows altering the - display in ways designed to assist visually impaired users, by - increasing contrast etc. This will interfere badly with any attempts - to calibrate or profile such a system, and must be turned off in - order to do so. Note that certain magic keyboard sequences can turn - this on by accident.
-
-
-
-
-
- - + + the black point is not being set completely to the same hue as the + white point (ie. because the -k + factor is less than 1.0), then the resulting calibration curves will + have the target white point down most of the curve, but will then + blend over to the native or compromise black point that is blacker, + but not of the right hue. The rate of this blend can be controlled + with the -A parameter. The + default value 4.0, which results in a target that switches from the + white point target to the black, moderately close to the black + point. While this typically gives a good visual result with the + target neutral hue being maintained to the point where the crossover + to the black hue is not visible, it may be asking too much of some + displays (typically LCD type displays), and there may be some visual + effects due to inconsistent color with viewing angle. For this + situation a smaller value may give a better visual result (e.g. try + values of 3.0 or 2.0. A value of 1.0 will set a pure linear blend + from white point to black point). If there is too much coloration + near black, try a larger value, e.g. 6.0 or 8.0.
+
+ The -b flag forces source 0,0,0 to map + to destination 0,0,0. This may be useful with displays that have a + very dark black point, and with an instrument is unable to measure + it precisely, and where it is known in some other way that the + display is very well behaved from black (i.e. that it has no + "dead zone" above zero device input). Using this option with a + display that is not well behaved, may result in a loss of + shadow detail. This will override any -k factor.
+
+ -B Set + the target brightness of black in cd/m^2 (i.e. the absolute Y + value). Setting too high a value may give strange results as it + interacts with trying to achieve the target "advertised" gamma curve + shape. You could try using -f 1 if this causes a problem.
+
+ -e [n] Run n verify passes on the final + curves. This is an extra set of instrument readings, that can be + used to estimate how well the device will match the targets with the + computed calibration curves. Note that the usefulness of the + verification is sometimes limited by the repeatability of the device + & instrument readings. This is often evident for CRT displays, + which (due to their refresh rate) flicker. More than one + verification pass can be done by providing the parameter n, and by then comparing the + successive verifications, some idea of the repeatability can be + ascertained. The verification uses a fixed number of semi-random + test values to test the calibration.
+
+ -z 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. Note that if the initial + calibration was modified due to it being out of gamut of the + display, verify will show the resulting discrepancy. You can use dispwin to load a .cal file into the display + before running dispcal -z. + 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 -a parameter + for verify.
+
+ The -P + parameter allows you to position and size the test patch window. By + default it is places in the center of the screen, and sized + appropriately for the type of instrument, or 10% of the width of the + display if the display size is unknown.. The ho and vo values govern the horizontal + and vertical offset respectively. A value of 0.0 positions the + window to the far left or top of the screen, a value of 0.5 + positions it in the center of the screen (the default), and 1.0 + positions it to the far right or bottom of the screen. If three + parameters are provided, then the ss + parameter is a scale factor for the test window size. A value of 0.5 + for instance, would produce a half sized window. A value of 2.0 will + produce a double size window. If four parameters are provided, then + the last two set independent horizontal and vertical scaling + factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be + specified as a single string (no space between the numbers and the + comma). For example, to create a double sized test window at the top + right of the screen, use -P 1,0,2 + . To create a window twice as wide as high: -P 1,0,2,1.
+
+ The -F + flag causes the while screen behind the test window to be masked + with black. This can aid black accuracy when measuring CRT displays + or projectors.
+
+ The -E + 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.
+
+ -n When + running on a UNIX based system that used the X11 Windowing System, dispcal + normally selects the override redirect so that the test window will + appear above any other windows on the display. On some systems this + can interfere with window manager operation, and the -n + option turns this behaviour off.
+
+ The -J + option runs through the black and sensor relative calibration + routines for the Xrite DTP92 and DTP94 instruments, the black level + calibration for the Eye-One Display 1, and a CRT frequency + calibration for the Eye-One Display 2. For the black calibration the + instrument should be placed on an opaque, black surface, and any + stray light should be avoided by placing something opaque over the + instrument. If a Spectrolino is being used, then a white and black + calibration will always be performed before the instrument can be + placed on the display, unless the -N + flag is used. Generally it is not necessary to do a calibration + every time an instrument is used, just now and again. There is also + no point in doing a CRT frequency calibration, as this will be + done automatically at the commencement of patch reading, and will be + lost between runs.
+
+ -N Any + instrument that requires regular calibration will ask for + calibration on initial start-up. Sometimes this can be awkward if + the instrument is being mounted in some sort of measuring jig, or + annoying if several sets of readings are being taken in quick + succession. The -N + suppresses this initial calibration if a valid and not timed out + previous calibration is recorded in the instrument or on the host + computer. It is advisable to only use this option on the second and + subsequent measurements in a single session.
+
+ The -H + option turns on high resolution spectral mode, if the instrument + supports it, such as the Eye-One Pro. See Operation of particular instruments + for more details. This may give better accuracy for display + measurements.
+
+ The -X file.ccmx option reads + a Colorimeter Correction Matrix + from the given file, and applies it to the colorimeter instruments + readings. This can improve a colorimeters accuracy for a particular + type of display. A list of contributed ccmx files is here.
+
+ The -X file.ccss option reads + a Colorimeter Calibration + Spectral Sample from the given file, and uses it to set the + colorimeter instruments calibration. This will only work with + colorimeters that rely on sensor spectral sensitivity calibration + information (ie. the X-Rite i1d3, + or the DataColor Spyder4 & + Spyder 5).This can improve a colorimeters accuracy for a + particular type of display.
+
+ The -Q flag allows specifying a tristimulus + observer, and is used to compute PCS (Profile Connection Space) + tristimulus values from spectral readings or using a colorimeter + that has CCSS capability. The following choices are available:
+ 1931_2 selects the standard CIE 1931 2 degree + observer. The default.
+ 1964_10 selects the standard CIE 1964 10 degree + observer.
+ 1955_2 selects the Stiles and Birch 1955 2 degree + observer
+ 1978_2 selects the Judd and Voss 1978 2 degree + observer
+ shaw selects the Shaw and Fairchild 1997 2 degree + observer
+ 1964_10c selects a version of the CIE 1964 10 degree + observer that has been adjusted using a 3x3 matrix to better agree + with the 1931 2 degree observer.
+
+ NOTE that if you select + anything other than the default 1931 2 degree observer, that the Y + values will not be cd/m^2, due to the Y curve not being the CIE 1924 + photopic V(λ) luminosity function.
+
+ The -I b|w options invoke + instrument black level, and display white level compensation + (respectively). Instrument black level drift compensation attempts + to combat instrument black calibration drift by using a display + black test patch as a reference. If an instrument is not + acclimatised sufficiently to the measurement conditions, changes in + temperature can affect the black readings. Display white level drift + compensation attempts to combat changes in display brightness as it + warms up by measuring a white patch every so often, and using it to + normalise all the other readings. If just instrument black drift + compensation is needed, use -Ib. + If just display white level compensation is needed, use -Iw. If both are needed, use -Ibw or -Iwb.
+
+ The -Y R:rate + 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.
+
+ The -Y A + option uses a non-adaptive integration time emission measurement + mode, if the instrument supports it, such as the Eye-One Pro, + ColorMunki, i1d3 and K10. By default an adaptive integration time + measurement mode will be used for emission measurements, but some + instruments support a fixed integration time mode that can be used + with display devices. This may give faster measurement times, but + may also give less accurate low level readings.
+
+ The -Y p + 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.
+
+ The -C "command" option allows a + method of relaying each test value to some other display than that + on the system running dispcal (for instance, a photo frame, PDA + screen etc.), by causing the given command to be invoked to the + shell, with six arguments. The first three arguments are the RGB + test color as integers in the range 0 to 255, the second three + parameters are the RGB test color as floating point numbers in the + range 0.0 to 1.0. The script or tool should relay the given color to + the screen in some manner (e.g. by generating a raster file of the + given color and sending it to the display being profiled), before + returning. Note that a test window will also be created on the + system running dispread.
+
+ The -M "command" option allows a + method of gathering each test value from some external source, such + as an instrument that is not directly supported by Argyll. The given + command is involked to the shell, with six arguments. The first + three arguments are the RGB test color as integers in the range 0 to + 255, the second three parameters are the RGB test color as floating + point numbers in the range 0.0 to 1.0. The script or tool should + create a file called "command.meas" + that contains the XYZ values for the given RGB (or measured from the + test window) in cd/m^2 as three numbers separated by spaces, before + returning. If the command returns a non-zero return value, dispcal + will abort. Note that a test window will also be created on the + system running dispcal.
+
+ The -W n|h|x + parameter overrides the default serial communications flow control + setting. The value n turns + all flow control off, h + sets hardware handshaking, and x + sets Xon/Xoff handshaking. This commend may be useful in workaround + serial communications issues with some systems and cables.
+
+ The -D 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.
+
+ inoutfile + The final parameter on the command line is the base filename for the + .cal file and the optional ICC + profile. Normally this will be created (or an existing file will be + overwritten). If the -u + flag is used, then these files will be updated. If a different ICC + profile name needs to be specified, do so as an argument to the -o flag.
+
+ NOTE that on an X11 system, + if the environment variable ARGYLL_IGNORE_XRANDR1_2 + is set (ie. set it to "yes"), then the presence of the XRandR 1.2 + extension will be ignored, and other extensions such as Xinerama and + XF86VidMode extension will be used. This may be a way to work around + buggy XRandR 1.2 implementations.
+
+

Discussion and guide to display control + adjustment:

+
+ The adjustment of the display controls (brightness, contrast, R, G + & B channel controls etc.) is very dependent on the particular + monitor. Different types and brands of monitors will have different + controls, or controls that operate in different ways. Some displays + have almost no user controls, and so you may well be best skipping + display adjustment, and going straight to calibration.
+
+ Almost all LCD displays lack a real contrast control. Those that do present such a + control generally fake it by adjusting the video signal. For this + reason it is usually best to set an LCD's contrast control at its neutral setting (ie. the + setting at which it doesn't change the video signal). Unfortunately, + it can be hard to know what this neutral setting is. On some + displays it is 50%, others 75%. If the LCD display has a "reset to + factory defaults" mode, then try using this first, as a way of + setting the contrast + control to neutral. The LCD brightness + control generally adjusts the level of backlighting the display + gets, which affects the maximum brightness, and also tends to raise + or lower the black level in proportion, without changing the + displays response curve shape or overall contrast ratio. If your LCD + display has a backlight + control as well as a brightness + control, then the brightness control is also probably being faked, + and you are probably better off setting it to it's neutral setting, + and using the backlight + control in place of brightness + in the following adjustments.
+
+ Some high end displays have the ability to mimic various standard + colorspaces such as sRGB or AdobeRGB. You could choose to calibrate + and profile the display in such an emulation mode, although you + probably don't want to fight the emulations white point and gamma. + To get the best out of such a display you really want to choose it's + "Native Gamut" setting, whatever that is called. Note that some + people have reported bad experiences in trying to use "6-axis custom + controls" on displays such as the Dell U2410, so attempting to use + such a mode should be approached with caution. Ideally such a mode + should be used to give just the underlying native display response, + but the settings to achieve this may be very difficult to determine, + and/or it may not be possible, depending on how such a mode distorts + the RGB signals.
+
+ On CRT based displays, the brightness + control generally adjusts the black level of the display (sometimes + called the offset), and as + a side effect, tends to change the maximum brightness too. A CRT contrast control generally + adjusts the maximum brightness (sometimes called gain) without affecting the + black level a great deal. On a CRT both the brightness and contrast controls will tend to + affect the shape or gamma of the display response curve.
+
+ Many displays have some sort of color temperature adjustment. This + may be in the form of some pre-set color temperatures, or in the + form of individual Red, Green and Blue channel gain adjustments. + Some CRT displays also have R, G & B channel offset adjustments + that will affect the color temperatures near black, as well as + affect the individual channels curve shape. The color temperature + adjustment will generally affect the maximum brightness, and may + also affect the black level and the shape of the display response + curves.
+
+ Some special (expensive) LCD displays may have a white point + adjustment that changes the color of the backlight. If you do not + have one of these types of LCD displays, then attempting to change + the white point of the display (even if it appears to have a "white point selection" or R/G/B "gain" controls") may not be a good idea, as once + again these controls are probably being faked by manipulating the + signal levels. Even if you do manage to change the white point + significantly, it may do things like change the mid tone color too + dramatically, or create a display response that is hard to correct + with calibration, or results in side effects such as quantization + (banding) or other undesirable effects. You may have to try out + various controls (and your aim points for the display calibration), + to decide what is reasonable to attempt on an LCD display.
+
+ Due to the variety of controls as well as the interaction between + them, it can be an iterative process to arrive at a good monitor + set-up, before proceeding on to calibrating and profiling a display. + For this reason, dispcal + offers a menu of adjustment modes, so that the user can + interactively and iteratively adjust the display controls to meet + the desired targets.
+
+ 1) Black level (CRT: Brightness)
+ 2) White point (Color temperature, R,G,B, Gain/Contrast)
+ 3) White level (CRT: Gain/Contrast, LCD: + Brightness/Backlight)
+ 4) Black point (R,G,B, Offset/Brightness)
+ 5) Check all
+ 6) Measure and set ambient for viewing condition adjustment
+ 7) Continue on to calibration
+ 8) Exit
+
+ There are four basic adjustment modes. Normally one would proceed + through them in the order above, then perhaps repeat the first + adjustment, before checking the overall settings. The White point + and White level modes operate slightly differently, depending on + whether a white target point has been set using the -t -T or -w options, and on whether a + brightness target has been set using the -b option.
+
+
+ The first mode lets you adjust the black level of a CRT display. + Given the current white level, it calculates a value that should + produce a 1% display brightness if the black level is set correctly. + After doing some initial measurements, it will show the target + brightness value (in cd/m^2) on one line, and then underneath it + will show continuously updated readings from the display. The left + most character will switch from '\' to '/' or back again each time a + reading is updated. Some instruments can be quite slow in measuring + dark colors, and it's best to wait for a reading update before + changing the controls more than once. Underneath the target value is + displayed the current reading, and to the right of this is a '+', + '-' or '=' symbol, which gives a hint as to which way to adjust the + brightness control to improve the match to the target.
+
+ Adjust CRT brightness to get target level. + Press space when done.
+    Target + 0.60
+ / Current 0.68 + -
+
+ Once happy with the adjustment, press space to go back to the menu.
+
+
+ The second mode lets you adjust the color of the white point of the + display. If a target white point has been set, it will show the + target brightness value (in cd/m^2) on one line, together with the + target chromaticity co-ordinates for the white point, and then + underneath it will show continuously updated readings from the + display. The left most character will switch from '\' to '/' or back + again each time a reading is updated. Underneath the target + brightness value is displayed the current reading, and then the + current chromaticity co-ordinate values. To the right of this is the + current delta E of the white point from the target, and further to + the right are hints '+', '-' or '=' as to which direction to + adjust the individual Red, Green and Blue gain settings to move the + white point in the direction of the target, and reduce the delta E. + If the symbol is doubled, then this channel will have the greatest + effect. If you do not have individual channel gain controls, then + try choosing amongst color temperature pre-sets, to find one with + the lowest delta E. Depending on the stability of the display, the + coarseness of the controls, and the repeatability of the instrument, + you may not be able to get a perfectly zero delta E.
+
+    Adjust R,G & B gain to get + target x,y. Press space when done.
+    Target B 60.00, x 0.3451, y 0.3516
+ / Current B 60.05, x 0.3426, y 0.3506 DE + 1.4 R+ G+ B--
+
+ If you did not set a white point target, then the information shown + is a little different - it will show the initial white point value, + as well as the color temperature, and the CIEDE2000 of the white + point to either the Daylight or Black Body locus (depending on + whether the -T flag was + set). The constantly updated values show the same thing, and the + Red, Green and Blue control hints show the direction to adjust the + controls to place the white point on the locus. The control that + will have the most direct effect on the color temperature will be + the Blue, while the Green will most directly move the white point + towards or away from the locus, thereby reducing the delta E of the + white point to the locus (but there is interaction).
+
+ Adjust R,G & B gain to desired white point. + Press space when done.
+ Initial B 47.25, x + 0.3417, y 0.3456, CDT 5113 DE 6.9
+ \ Current B 47.38, x 0.3420, + y 0.3460 CDT 5104 DE 6.7 R-- G+ B-
+
+ The brightness value is just there as a guide to what effect + the adjustment is having on the overall brightness. Usually the + white level brightness is adjusted using the next adjustment mode. + Once happy with the adjustment, press space to go back to the menu.
+
+
+ The third mode lets you adjust the brightness of white on the + display. If you set a target brightness using the -b + parameter, it will show the target brightness value (in cd/m^2) on + one line, and then underneath it will show continuously updated + readings from the display. The left most character will switch from + '\' to '/' or back again each time a reading is updated. Underneath + the target value is displayed the current reading, and to the right + of this is a '+', '-' or '=' symbol, which gives a hint as to which + way to adjust the CRT contrast or LCD brightness control to improve + the match to the target.
+
+    Adjust CRT Contrast or LCD + Brightness to get target level. Press space when done.
+    Target 60.00
+ / Current 59.96 +
+
+ If you did not set a brightness target, it will show the initial + brightness as the target, and the current brightness, which you can + then set any way you want:
+
+ Adjust CRT Contrast or LCD Brightness to desired + level. Press space when done.
+ Initial 47.32
+ / Current 47.54
+
+ Once happy with the adjustment, press space to go back to the menu.
+
+
+ The fourth mode lets you adjust the color of the black point of the + display, if the display has Red, Green and Blue channel offset + controls. It will show the target 1% brightness value (in cd/m^2) on + one line, together with the target chromaticity co-ordinates for the + black point, and then underneath it will show continuously updated + readings from the display. The left most character will switch from + '\' to '/' or back again each time a reading is updated. Underneath + the target brightness value is displayed the current reading, and + then the current chromaticity co-ordinate values. To the right of + this is the current delta E of the black point from the target, and + further to the right are hints '+', '-' or '=' as to which + direction to adjust the individual Red, Green and Blue offset + settings to move the black point in the right direction. If the + symbol is doubled, then this channel will have the greatest effect. +
+
+ Adjust R,G & B offsets to get target x,y. + Press space when done.
+    Target B 0.60, x 0.3451, y 0.3516
+ \ Current B 0.62, x 0.2782, y 0.2331 DE + 10.3 R+ G++ B-
+
+ The 1% brightness value is just there as a guide to what + effect the adjustment is having on the 1% brightness level. The + combined channel offsets may have an effect on this in combination + with the CRT brightness control. Press space to go back to the menu.
+
+
+ The fifth selection checks on the overall settings. If targets + have been set, it will be like:
+
+ Target Brightness = 50.00, Current = 47.44, + error = -5.1%
+ Target 50% Level = 10.32, Current = 8.10, + error = -4.4%
+ Target Near Black = 0.47, Current = 0.68, + error = 0.4%
+ Target white = x 0.3458, y 0.3586, Current = x 0.3420, y + 0.3454, error = 7.55 DE
+ Target black = x 0.3458, y 0.3586, Current = x 0.2908, y + 0.2270, error = 29.69 DE
+
+ or if no targets are set:
+
+ Current Brightness = 46.28
+ Target 50% + Level = 10.07, Current = 7.52, error = -5.5%
+ Target Near Black + = 0.46, Current = 0.46, error = -0.0%
+ Current white = x + 0.3439, y 0.3466, VCT 5098K DE 3.0
+ Target black = x + 0.3439, y 0.3466, Current = x 0.3093, y 0.2165, error = 30.30 DE
+
+ and will then go back to the menu.
+
+ The sixth selection 6) + allows the reading of you ambient lighting conditions if your + instrument supports such a mode. Doing so will enable the -a option to compensate for your + viewing conditions in the subsequent calibration. See -a.
+
+ Once you're happy with the display set-up, you can either + proceed on to the rest of the calibration by selecting 7), or exit and re-start by + selecting 8). You might + want to re-start if you want to change the calibration targets.
+
+

Other caveats:

+ NOTE that some LCD screens + behave a little strangely near their absolute white point, and may + therefore exhibit odd behavior at values just below white. It may be + advisable in such cases to set a brightness slightly less than the + maximum such a display is capable of.
+
+ The program attempts to stop any screensaver or powersaver from + interfering with the measurements, but this may not be effective on + some systems, so it may be necessary to manually disable the + screensaver and/or powersaver before commencing the calibration with + a large number of patches.
+
+ The calibration tables produced maintain the maximum level of + precision available on a system. If the display has VideoLUTs + available (Video Lookup Tables that the frame buffer values pass + through on their way to the display) and thier outputs are better + than 8 bits per component, then the resulting curves can reflect + this, although few current operating systems and/or display cards + actually support better than 8 bit per component output.
+
+ If calibration curves are created for a display in which VideoLUTs + are not available, then the resulting calibration file will be + marked to indicate this, and a subsequent profile created with the + calibration will not have the calibration converted to the 'vcgt' + tag, since such a tag can't be loaded into the displays VideoLUTs.
+
+ If communications break down with a USB connected instrument, you + may have to unplug it, and plug it in again to recover operation.
+
+ Some systems (Apple OS X in particular) have a special set of user + interface controls ("Universal Access") that allows altering the + display in ways designed to assist visually impaired users, by + increasing contrast etc. This will interfere badly with any attempts + to calibrate or profile such a system, and must be turned off in + order to do so. Note that certain magic keyboard sequences can turn + this on by accident.
+
+
+
+
+
+ + diff --git a/doc/dispread.html b/doc/dispread.html index 52a38c2..12077eb 100644 --- a/doc/dispread.html +++ b/doc/dispread.html @@ -1,25 +1,25 @@ - - - - dispread - - - - -

spectro/dispread

Summary

- Display test patches on a monitor, read the colorimetric value - result with the colorimeter, and create the chart readings file. The - type of instrument is determined by the communication port selected. - Emission and display measurement instruments are supported.
-
- If you want to read a display manually rather than automatically, - see chartread and the -d option.
-

Usage

- dispread [-options] - inoutfile
+ + + + dispread + + + + +

spectro/dispread

Summary

+ Display test patches on a monitor, read the colorimetric value + result with the colorimeter, and create the chart readings file. The + type of instrument is determined by the communication port selected. + Emission and display measurement instruments are supported.
+
+ If you want to read a display manually rather than automatically, + see chartread and the -d option.
+

Usage

+ dispread [-options] + inoutfile
-v              @@ -54,17 +54,17 @@ - -      Verbose mode
- -display displayname [X11 only] Choose X11 display - name
- -d n[,m] -             - [X11 only]Choose the display from the following list (default - 1),
+ +      Verbose mode
+ -display displayname [X11 only] Choose X11 display + name
+ -d n[,m] +             + [X11 only]Choose the display from the following list (default + 1),
                      and optionally @@ -106,9 +106,9 @@ m - - for VideoLUT access.
-
+ -d n                 Choose the @@ -150,8 +150,8 @@ list - - (default 1)
+ + (default 1)
-dweb[:port]         @@ -188,9 +188,9 @@ list - - Display via a web server at port (default 8080)
- -dmadvr + + Display via a web server at port (default 8080)
+ -dmadvr              @@ -214,22 +214,22 @@ list - - [MSWin] Display via MadVR Video Renderer
+ + [MSWin] Display via MadVR Video Renderer
-dcc[:n]             - -Display via n'th ChromeCast (default 1, ? for list)
- -c listno -        Set - communication port from the following list (default 1)
- -c listno +        Set + communication port from the following list (default 1)
+ -p                   @@ -264,10 +264,10 @@ list - - Use telephoto mode (ie. for a projector) (if available)
- -y X + + Use telephoto mode (ie. for a projector) (if available)
+ -y X                 Display @@ -304,10 +304,10 @@ Display - - type - instrument specific list to choose from.
- -k + + type - instrument specific list to choose from.
+ -k file.cal          @@ -342,10 +342,10 @@ Display - - Load calibration file into display while reading
- -K + + Load calibration file into display while reading
+ -K file.cal          Apply @@ -381,8 +381,8 @@ Apply - - calibration file to test values while reading
+ + calibration file to test values while reading
-V                   @@ -398,8 +398,8 @@ Apply - - [MSWin] Enable MadVR color management (3dLut)
+ + [MSWin] Enable MadVR color management (3dLut)
-s              @@ -434,12 +434,12 @@ Apply - -      Save spectral information (default don't - save)
- -P ho,vo,ss[,vs]     Position - test window and scale it
+ +      Save spectral information (default don't + save)
+ -P ho,vo,ss[,vs]     Position + test window and scale it
                      ho,vi: 0.0 @@ -481,8 +481,8 @@ center, - - 1.0 = right/bottom etc.
+ + 1.0 = right/bottom etc.
                      ss: 0.5 @@ -524,8 +524,8 @@ normal, - - 2.0 = double etc.
+ + 2.0 = double etc.
                      @@ -553,10 +553,10 @@ normal, - - ss,vs: = optional horizontal, vertical scale.
- -F + + ss,vs: = optional horizontal, vertical scale.
+ -F                   @@ -591,10 +591,10 @@ normal, - - Fill whole screen with black background
- -E + + Fill whole screen with black background
+ -E                   @@ -614,11 +614,11 @@ normal, - - Video - encode output as (16-235)/255 "TV" levels
- -Z + + Video + encode output as (16-235)/255 "TV" levels
+ -Z nbits             @@ -638,7 +638,7 @@ normal, - + Quantize test values @@ -658,9 +658,9 @@ fit - - in nbits
-
+ -n                   [X11 @@ -702,9 +702,9 @@ redirect - - on test window
- -J + + on test window
+ -J              @@ -739,9 +739,9 @@ redirect - -      Run calibration first
-
+ -N                   @@ -776,17 +776,17 @@ redirect - - Disable initial calibration of instrument if possible
- -H -              -      Use high resolution spectrum mode (if - available)
- -w + + Disable initial calibration of instrument if possible
+ -H +              +      Use high resolution spectrum mode (if + available)
+ -w                   Disable normalisation @@ -828,9 +828,9 @@ Y - - 100
-
+ -X file.ccmx         @@ -865,9 +865,9 @@ Y - - Apply Colorimeter Correction Matrix
- -X + + Apply Colorimeter Correction Matrix
+ -X file.ccss          Use Colorimeter @@ -905,14 +905,14 @@ Calibration - - Spectral Samples for calibration
- -Q observ -     Choose CIE Observer for spectrometer or CCSS - colorimeter data:
+ + Spectral Samples for calibration
+ -Q observ +     Choose CIE Observer for spectrometer or CCSS + colorimeter data:
            @@ -947,12 +947,12 @@ Calibration - - 1931_2 (def.), 1964_10, S&B 1955_2, shaw, - J&V 1978_2, 1964_10c
- (def.), 1964_10, S&B 1955_2, shaw, + J&V 1978_2, 1964_10c
+ -I b|w               Drift compensation, @@ -994,8 +994,8 @@ Both: - - -Ibw
+ + -Ibw
-Y @@ -1008,7 +1008,7 @@ Both: - + R:rate             @@ -1021,12 +1021,12 @@ Both: - - Override measured refresh rate with rate Hz - -Y A + + Override measured refresh rate with rate Hz
+ -Y A                 @@ -1052,31 +1052,31 @@ Both: - - Use non-adaptive integration time mode (if available).
- -Y - p -             -     Don't wait for the instrument to be placed on - the display
- -C "command" -         Invoke shell - "command" each time a color is set
- -M "command" -         Invoke shell - "command" each time a color is measured
- -x x
+ -Y + p +             +     Don't wait for the instrument to be placed on + the display
+ -C "command" +         Invoke shell + "command" each time a color is set
+ -M "command" +         Invoke shell + "command" each time a color is measured
+ -x x                 -Take - manually entered - XYZ values
-
+ -W n|h|x             Override serial @@ -1118,11 +1118,11 @@ n - - none, h = HW, x = Xon/Xoff
- -D [level] -           Print debug - diagnostics to stderr
+ + none, h = HW, x = Xon/Xoff
+ -D [level] +           Print debug + diagnostics to stderr
inoutfile            @@ -1157,73 +1157,73 @@ n - - Base name for input[.ti1]/output[.ti3] file.
-
- Examples
-
- dispread -c1 -i92 mycrt
-

Comments
-

- This is the tool for exercising a display, in order to measure its - color characteristics. The device test colors are defined by the - outfile.ti1 file, while the resulting device+colorimetric and - optional spectral readings are stored in the outfile.ti3 file. - Display calibration curves can be applied during the measurements, - and the curves included in the resulting .ti3 data file using the -kflag. See dispcal for information on how to - calibrate the display before profiling it. For best results, you - should run this against a neutral grey desktop background, and avoid - having any bright images or windows on the screen at the time you - run it.
-
- The -v flag reports progress information.
-
- -display: - When running on a UNIX based system that used the X11 Windowing - System, dispread will by default use the $DISPLAY - environment variable to determine which display and screen to read - from. This can be overridden by supplying an X11 display name to the - -display option. Note that - if Xinerama is active, you can't select the screen using $DISPLAY or - -display, you have to select it using the -d parameter.
-
- -d: By - default the main display will be the location of the test window. If - the system has more than one display or screen, an alternate - display/screen can be selected with the -d parameter. If you invoke dispread so as to display the - usage information (i.e. "dispread -?" or "dispread --"), then the - discovered displays/screens will be listed. Multiple displays may - not be listed, if they appear as a single display to the operating - system (ie. the multi-display support is hidden in the video card - driver). On UNIX based system that used the X11 Windowing System, - the -d parameter will - override the screen specified by the $DISPLAY or -display parameter.
-
- On X11 the inability to access VideoLUTs could be because you are - trying to access a remote display, and the remote display doesn't - support the XF86VidMode extension, or perhaps you are running - multiple monitors using NVidia TwinView, or MergedFB, and trying to - access anything other than the primary monitor. TwinView and - MergedFB don't properly support the XF86VidMode extension for - multiple displays. You can use dispwin -r - to test whether the VideoLUTs are accessible for a particular - display. See also below, on how to select a different display for - VideoLUT access. Also note that dispcal will fail if the Visual - depth doesn't match the VideoLUT depth. Typically the VideoLUTs have - 256 entries per color component, so the Visual generally needs to be - 24 bits, 8 bits per color component.
-
- Because of the difficulty cause by TwinView and - MergedFB in X11 based systems, you can optionally specify a separate - display number after the display that is going to be used to present - test patches, for accessing the VideoLUT hardware. This must be + + Base name for input[.ti1]/output[.ti3] file.
+
+ Examples
+
+ dispread -c1 -i92 mycrt
+

Comments
+

+ This is the tool for exercising a display, in order to measure its + color characteristics. The device test colors are defined by the + outfile.ti1 file, while the resulting device+colorimetric and + optional spectral readings are stored in the outfile.ti3 file. + Display calibration curves can be applied during the measurements, + and the curves included in the resulting .ti3 data file using the -kflag. See dispcal for information on how to + calibrate the display before profiling it. For best results, you + should run this against a neutral grey desktop background, and avoid + having any bright images or windows on the screen at the time you + run it.
+
+ The -v flag reports progress information.
+
+ -display: + When running on a UNIX based system that used the X11 Windowing + System, dispread will by default use the $DISPLAY + environment variable to determine which display and screen to read + from. This can be overridden by supplying an X11 display name to the + -display option. Note that + if Xinerama is active, you can't select the screen using $DISPLAY or + -display, you have to select it using the -d parameter.
+
+ -d: By + default the main display will be the location of the test window. If + the system has more than one display or screen, an alternate + display/screen can be selected with the -d parameter. If you invoke dispread so as to display the + usage information (i.e. "dispread -?" or "dispread --"), then the + discovered displays/screens will be listed. Multiple displays may + not be listed, if they appear as a single display to the operating + system (ie. the multi-display support is hidden in the video card + driver). On UNIX based system that used the X11 Windowing System, + the -d parameter will + override the screen specified by the $DISPLAY or -display parameter.
+
+ On X11 the inability to access VideoLUTs could be because you are + trying to access a remote display, and the remote display doesn't + support the XF86VidMode extension, or perhaps you are running + multiple monitors using NVidia TwinView, or MergedFB, and trying to + access anything other than the primary monitor. TwinView and + MergedFB don't properly support the XF86VidMode extension for + multiple displays. You can use dispwin -r + to test whether the VideoLUTs are accessible for a particular + display. See also below, on how to select a different display for + VideoLUT access. Also note that dispcal will fail if the Visual + depth doesn't match the VideoLUT depth. Typically the VideoLUTs have + 256 entries per color component, so the Visual generally needs to be + 24 bits, 8 bits per color component.
+
+ Because of the difficulty cause by TwinView and + MergedFB in X11 based systems, you can optionally specify a separate + display number after the display that is going to be used to present + test patches, for accessing the VideoLUT hardware. This must be specified as a single string, e.g. -d @@ -1258,423 +1258,423 @@ n - - 1,2 . Some experimentation may be needed using dispwin on such systems, to discover what - screen has access to the VideoLUT hardware, and which screens the - test patches appear on. You may be able to calibrate one screen, and - then share the calibration with another screen. Profiling can be - done independently to calibration.
-
- -dweb or - -dweb:port starts a - standalone web server on your machine, which then allows a local or - remote web browser to display the the color test patches. By default - port 8080 is used, but this - can be overridden by appending a : - and the port number i.e. -dweb:8001. - The URL will be http:// - then name of the machine or its I.P. address followed by a colon and - the port number - e.g something like http://192.168.0.1:8080. If you use the verbose - option (-v) then a likely - URL will be printed once the server is started, or you could run ipconfig (MSWin) or /sbin/ifconfig (Linux or OS X) - and identify an internet address for your machine that way. - JavaScript needs to be enabled in your web browser for this to - work. You may have to modify any firewall to permit port 8080 to be - accessed on your machine.
-
- Note that if you use this method of displaying test patches, that - there is no access to the display VideoLUTs and that the colors will - be displayed with 8 bit per component precision, and any - screen-saver or power-saver will not be disabled. You will also be - at the mercy of any color management applied by the web browser, and - may have to carefully review and configure such color management. - See the -o flag for an explanation of - the implications of having no access to the VideoLUTs.
-
- -dmadvr - [MSWin only] causes test patches to be displayed using the MadVR - video renderer. Note that will have to start MadTPG before - running dispread, and that while you can adjust the "Test Pattern - Configuration" controls, you should not normally alter the - "Existing Calibration" controls, as dispread will set these - appropriately. See also -V flag.
-
- -dcc or -dcc:no - causes test patches to be displayed using and available ChromeCast to - your TV. Use -dcc:? to display a list of ChromeCasts on your - local network. Note that the ChromeCast as a test patch source is - probably the least accurate of your choices, since it - up-samples the test patch and transforms from RGB to YCC and back, - but should be accurate within � 1 bit. You may have to modify any - firewall to permit port 8081 to be accessed on your machine if it + + 1,2 . Some experimentation may be needed using dispwin on such systems, to discover what + screen has access to the VideoLUT hardware, and which screens the + test patches appear on. You may be able to calibrate one screen, and + then share the calibration with another screen. Profiling can be + done independently to calibration.
+
+ -dweb or + -dweb:port starts a + standalone web server on your machine, which then allows a local or + remote web browser to display the the color test patches. By default + port 8080 is used, but this + can be overridden by appending a : + and the port number i.e. -dweb:8001. + The URL will be http:// + then name of the machine or its I.P. address followed by a colon and + the port number - e.g something like http://192.168.0.1:8080. If you use the verbose + option (-v) then a likely + URL will be printed once the server is started, or you could run ipconfig (MSWin) or /sbin/ifconfig (Linux or OS X) + and identify an internet address for your machine that way. + JavaScript needs to be enabled in your web browser for this to + work. You may have to modify any firewall to permit port 8080 to be + accessed on your machine.
+
+ Note that if you use this method of displaying test patches, that + there is no access to the display VideoLUTs and that the colors will + be displayed with 8 bit per component precision, and any + screen-saver or power-saver will not be disabled. You will also be + at the mercy of any color management applied by the web browser, and + may have to carefully review and configure such color management. + See the -o flag for an explanation of + the implications of having no access to the VideoLUTs.
+
+ -dmadvr + [MSWin only] causes test patches to be displayed using the MadVR + video renderer. Note that will have to start MadTPG before + running dispread, and that while you can adjust the "Test Pattern + Configuration" controls, you should not normally alter the + "Existing Calibration" controls, as dispread will set these + appropriately. See also -V flag.
+
+ -dcc or -dcc:no + causes test patches to be displayed using and available ChromeCast to + your TV. Use -dcc:? to display a list of ChromeCasts on your + local network. Note that the ChromeCast as a test patch source is + probably the least accurate of your choices, since it + up-samples the test patch and transforms from RGB to YCC and back, + but should be accurate within � 1 bit. You may have to modify any + firewall to permit port 8081 to be accessed on your machine if it falls back to the Default receiver (see installation - - instructions for your platform).
-
- -c: The - instrument is assumed to communicate through a USB or serial - communication port, and the port can be selected with the -c - option, if the instrument is not connected to the first port. If you - invoke dispread so as to - display the usage information (i.e. "dispread -?" or "dispread --"), - then the discovered USB and serial ports will be listed. On - UNIX/Linux, a list of all possible serial ports are shown, but not - all of them may actually be present on your system.
-
- The -p flag - allows measuring in telephoto mode, using instruments that support - this mode, e.g. the ColorMunki. Telephoto mode is one for taking - emissive measurements from a distance (ie. telespectometer, - tele-colorimeter) mode, and typically would be used for measuring - projector type displays. If a device does not support a specific - telephoto mode, then the normal emissive mode may be suitable for - measuring projectors.
-
- The -y flag - allows setting the Display Type. The selection typically determines - two aspects of of the instrument operation: 1) It may set the measuring mode - to suite refresh or non-refresh displays. - Typically only LCD (Liquid Crystal) displays have a non-refresh - nature. 2) It may select an - instrument calibration matrix suitable for a particular display - type. The selections available depends on the type and model of - instrument, and a list of the options for the discovered instruments - will be shown in the usage - information. For more details on what particular instruments support - and how this works, see Operation of - particular instruments. 3) Any installed CCSS files - (if applicable), or CCMX files. These files are typically created - using ccxxmake, and installed using oeminst. The default and Base Calibration - types will be indicated in the usage.
-
- -s: By - default only the colorimetric information (XYZ value) will be saved, - but for instruments that support spectral readings (such as the - Gretag Spectrolino), the -s option will save the spectral - readings to the .ti3 file as well.
-
- -k: If a - display video lookup table calibration .cal file is provided, it will - be loaded into the display VideoLUTs - 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 colprof - can include it as a vcgt - tag in the resulting profile. This is the normal way to profile a calibrated display. The - calibration file has usually been created using dispcal. 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 -K mode (see below). If a - calibration file is not supplied using -k or -K, - then the display will be measured in whatever calibration state it - is in, and no calibration information is saved to the resulting .ti3 - file.
- If the calibration file provided created using video range encoding - (dispcal -E), then the -E option in dispread will be - triggered automatically.
- NOTE that the calibration is - loaded into the display hardware just before the instrument starts - measurement, after the test window first appears.
-
- -K: If a - display video lookup table calibration .cal file is provided, it will - be applied to the test values for each measurement, and also - included in the resulting .ti3 data file, so that colprof can include it as a vcgt tag in the resulting - profile. This is NOT - normally the best way to profile a calibrated display, since the - frame buffer may have lower precision than the VideoLUTs output - values. This is the way calibration should be applied if MadVR is - being used to display the test patches. If a calibration file is not - supplied using -k or -K, then the display will be - measured in whatever calibration state it is in, and no calibration - information is saved to the resulting .ti3 file.
- If the calibration file provided created using video range encoding - (dispcal -E), then the -E option in dispread will be - triggered automatically.
-
- -V: [MSWin] If using MadVR to display test - patches, then enable Color Managenent (3dLut). This would be used - for verification measurement.
-
- The -P - parameter allows you to position and size the test patch window. By - default it is places in the center of the screen, and sized - appropriately for the type of instrument, or 10% of the width of the - display if the display size is unknown. The ho and vo values govern the horizontal - and vertical offset respectively. A value of 0.0 positions the - window to the far left or top of the screen, a value of 0.5 - positions it in the center of the screen (the default), and 1.0 - positions it to the far right or bottom of the screen. If three - parameters are provided, then the ss - parameter is a scale factor for the test window size. A value of 0.5 - for instance, would produce a half sized window. A value of 2.0 will - produce a double size window. If four parameters are provided, then - the last two set independent horizontal and vertical scaling - factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be - specified as a single string (no space between the numbers and the - comma). For example, to create a double sized test window at the top - right of the screen, use -P 1,0,2 - . To create a window twice as wide as high: -P 1,0,2,1.
-
- The -F - flag causes the while screen behind the test window to be masked - with black. This can aid black accuracy when measuring CRT displays - or projectors.
-
- The -E - 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 -k or -K flag was created using video range - encoding, then this option will be triggered automatically. This - will also set quantization of 8 bits (see -Z flag below). If your - video connection is better than 8 bits (ie. 10 or 12 bits), then you - may wish to raise this default.
-
- -Z nbits Normally the target device values - are floating point numbers that may get rounded and quantized in the - process of printing them or reproducing them on the display device. - If some of this quantization can be accounted for, it may improve - the accuracy of the resulting profile, and the Q parameter allows this - quantization to be specified. The parameter is the number of binary - digits (bits) that the device values should be quantized to. An idea - of the number of bits of precision that makes its way to your - display can be obtained by using dispcal - -R If Video encoding is selected (see -E flag above), then 8 - bits is selected by default. On systems using an VGA connection or - Display Port with a graphics card with VideoLUT entries with greater - than 8 bits depth, or if using the MadVR rendered with dithering, - then a higher bit depth is typically possible.
-
- -n: When - running on a UNIX based system that used the X11 Windowing System, dispread - normally selects the override redirect so that the test window will - appear above any other windows on the display. On some systems this - can interfere with window manager operation, and the -n - option turns this behaviour off.
-
- The -J - option runs through the black and sensor relative calibration - routines for the Xrite DTP92 and DTP94 instrument, the black level - calibration for the Eye-One Display 1, and a CRT frequency - calibration for the Eye-One Display 2. For the black calibration the - instrument should be placed on an opaque, black surface, and any - stray light should be avoided by placing something opaque over the - instrument. If a Spectrolino is being used, then a white and black - calibration will always be performed before the instrument can be - placed on the display, unless the -N flag is used. - Generally it is not necessary to do a calibration every time an - instrument is used, just now and again. There is no point in - doing a CRT frequency calibration, as this will be done - automatically at the commencement of patch reading.
-
- -N Any - instrument that requires regular calibration will ask for - calibration on initial start-up. Sometimes this can be awkward if - the instrument is being mounted in some sort of measuring jig, or - annoying if several sets of readings are being taken in quick - succession. The -N - suppresses this initial calibration if a valid and not timed out - previous calibration is recorded in the instrument or on the host - computer. It is advisable to only use this option on the second and - subsequent measurements in a single session.
-
- The -H - option turns on high resolution spectral mode, if the instrument - supports it. See Operation of particular - instruments for more details. This may give better accuracy - for display measurements.
-
- The -w flag disables the normalisation of - the white patch value to 100.0, resulting in values that are in - cd/m^2. This is mainly for diagnostic purposes.
-
- The -X file.ccmx option reads - a Colorimeter Correction Matrix - from the given file, and applies it to the colorimeter instruments - readings. This can improve a colorimeters accuracy for a particular - type of display. A list of contributed ccmx files is here.
-
- The -X file.ccss option reads - a Colorimeter Calibration - Spectral Sample from the given file, and uses it to set the - colorimeter instruments calibration. This will only work with - colorimeters that rely on sensor spectral sensitivity calibration - information (ie. the X-Rite i1d3, - or the DataColor Spyder4 & - Spyder 5).This can improve a colorimeters accuracy for a - particular type of display.
-
- The -Q flag allows specifying a tristimulus - observer, and is used to compute PCS (Profile Connection Space) - tristimulus values from spectral readings or using a colorimeter - that has CCSS capability. The following choices are available:
- 1931_2 selects the standard CIE 1931 2 degree - observer. The default.
- 1964_10 selects the standard CIE 1964 10 degree - observer.
- 1955_2 selects the Stiles and Birch 1955 2 degree - observer
- 1978_2 selects the Judd and Voss 1978 2 degree - observer
- shaw selects the Shaw and Fairchild 1997 2 degree - observer
- 1964_10c selects a version of the CIE 1964 10 degree - observer that has been adjusted using a 3x3 matrix to better agree - with the 1931 2 degree observer.
-
- NOTE that if you select - anything other than the default 1931 2 degree observer, that the Y - values will not be cd/m^2, due to the Y curve not being the CIE 1924 - photopic V(λ) luminosity function.
-
- The -I b|w options invoke - instrument black level, and display white level compensation - (respectively). Instrument black level drift compensation attempts - to combat instrument black calibration drift by using a display - black test patch as a reference. If an instrument is not - acclimatised sufficiently to the measurement conditions, changes in - temperature can affect the black readings. Display white level drift - compensation attempts to combat changes in display brightness as it - warms up by measuring a white patch every so often, and using it to - normalise all the other readings. If just instrument black drift - compensation is needed, use -Ib. - If just display white level compensation is needed, use -Iw. If both are needed, use -Ibw or -Iwb.
-
- The -Y R:rate - 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.
-
- The -Y A - option uses a non-adaptive integration time emission measurement - mode, if the instrument supports it, such as the Eye-One Pro, - ColorMunki, i1d3 and K10. By default an adaptive integration time - measurement mode will be used for emission measurements, but some - instruments support a fixed integration time mode that can be used - with display devices. This may give faster measurement times, but - may also give less accurate low level readings.
-
- The -Y p - 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.
-
- The -C - "command" option allows a - method of relaying each test value to some other display than that - on the system running dispread (for instance, a photo frame, PDA - screen etc.), by causing the given command to be invoked to the - shell, with six arguments. The first three arguments are the RGB - test color as integers in the range 0 to 255, the second three - parameters are the RGB test color as floating point numbers in the - range 0.0 to 1.0. The script or tool should relay the given color to - the screen in some manner (e.g. by generating a raster file of the - given color and sending it to the display being profiled), before - returning. Note that a test window will also be created on the - system running dispread.
-
- The -M "command" option allows a - method of gathering each test value from some external source, such - as an instrument that is not directly supported by Argyll. The given - command is involked to the shell, with six arguments. The first - three arguments are the RGB test color as integers in the range 0 to - 255, the second three parameters are the RGB test color as floating - point numbers in the range 0.0 to 1.0. The script or tool should - create a file called "command.meas" - that contains the XYZ values for the given RGB (or measured from the - test window) in cd/m^2 as three numbers separated by spaces, before - returning. If the command returns a non-zero return value, dispread - will abort. Note that a test window will also be created on the - system running dispread.
-
- The -x flag causes dispread to expect - values to be manually entered for each reading, rather than using an - instrument to do the measurements. This mode is ideal if your - instrument is not supported by Argyll. XYZ values should be entered. - It is possible to navigate about the test values being measured, so - as to do them in any order, as well as re-do values, in case of any - mistakes.
-
- The -W n|h|x - parameter overrides the default serial communications flow control - setting. The value n turns - all flow control off, h - sets hardware handshaking, and x - sets Xon/Xoff handshaking. This commend may be useful in workaround - serial communications issues with some systems and cables.
-
- The -D 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.
-
- The final parameter on the command line is the - base filename for the .ti1 - input file, and the .ti3 - output file. dispread will add the .ti1 and .ti3 extensions - automatically.
-
- NOTE that on an X11 system, - if the environment variable ARGYLL_IGNORE_XRANDR1_2 - is set (ie. set it to "yes"), then the presence of the XRandR 1.2 - extension will be ignored, and other extensions such as Xinerama and - XF86VidMode extension will be used. This may be a way to work around - buggy XRandR 1.2 implementations.
-
-

- If a large number of patches is being read, the screensaver on many - systems can interfere with the operation of dispread. It is - therefore advisable in these cases to manually turn off the - screensaver before commencing the measurements.
-
- If communications break down with a USB connected instrument, you - may have to unplug it, and plug it in again to recover.
-
- Some systems (Apple OSX in particular) have a special set of user - interface controls ("Universal Access") that allows altering the - display in ways designed to assist visually impaired users, by - increasing contrast etc. This will interfere badly with any attempts - to calibrate or profile such a system, and must be turned off in - order to do so. Note that certain magic keyboard sequences can turn - this on by accident.
-
-
-
- - + + instructions for your platform).
+
+ -c: The + instrument is assumed to communicate through a USB or serial + communication port, and the port can be selected with the -c + option, if the instrument is not connected to the first port. If you + invoke dispread so as to + display the usage information (i.e. "dispread -?" or "dispread --"), + then the discovered USB and serial ports will be listed. On + UNIX/Linux, a list of all possible serial ports are shown, but not + all of them may actually be present on your system.
+
+ The -p flag + allows measuring in telephoto mode, using instruments that support + this mode, e.g. the ColorMunki. Telephoto mode is one for taking + emissive measurements from a distance (ie. telespectometer, + tele-colorimeter) mode, and typically would be used for measuring + projector type displays. If a device does not support a specific + telephoto mode, then the normal emissive mode may be suitable for + measuring projectors.
+
+ The -y flag + allows setting the Display Type. The selection typically determines + two aspects of of the instrument operation: 1) It may set the measuring mode + to suite refresh or non-refresh displays. + Typically only LCD (Liquid Crystal) displays have a non-refresh + nature. 2) It may select an + instrument calibration matrix suitable for a particular display + type. The selections available depends on the type and model of + instrument, and a list of the options for the discovered instruments + will be shown in the usage + information. For more details on what particular instruments support + and how this works, see Operation of + particular instruments. 3) Any installed CCSS files + (if applicable), or CCMX files. These files are typically created + using ccxxmake, and installed using oeminst. The default and Base Calibration + types will be indicated in the usage.
+
+ -s: By + default only the colorimetric information (XYZ value) will be saved, + but for instruments that support spectral readings (such as the + Gretag Spectrolino), the -s option will save the spectral + readings to the .ti3 file as well.
+
+ -k: If a + display video lookup table calibration .cal file is provided, it will + be loaded into the display VideoLUTs + 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 colprof + can include it as a vcgt + tag in the resulting profile. This is the normal way to profile a calibrated display. The + calibration file has usually been created using dispcal. 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 -K mode (see below). If a + calibration file is not supplied using -k or -K, + then the display will be measured in whatever calibration state it + is in, and no calibration information is saved to the resulting .ti3 + file.
+ If the calibration file provided created using video range encoding + (dispcal -E), then the -E option in dispread will be + triggered automatically.
+ NOTE that the calibration is + loaded into the display hardware just before the instrument starts + measurement, after the test window first appears.
+
+ -K: If a + display video lookup table calibration .cal file is provided, it will + be applied to the test values for each measurement, and also + included in the resulting .ti3 data file, so that colprof can include it as a vcgt tag in the resulting + profile. This is NOT + normally the best way to profile a calibrated display, since the + frame buffer may have lower precision than the VideoLUTs output + values. This is the way calibration should be applied if MadVR is + being used to display the test patches. If a calibration file is not + supplied using -k or -K, then the display will be + measured in whatever calibration state it is in, and no calibration + information is saved to the resulting .ti3 file.
+ If the calibration file provided created using video range encoding + (dispcal -E), then the -E option in dispread will be + triggered automatically.
+
+ -V: [MSWin] If using MadVR to display test + patches, then enable Color Managenent (3dLut). This would be used + for verification measurement.
+
+ The -P + parameter allows you to position and size the test patch window. By + default it is places in the center of the screen, and sized + appropriately for the type of instrument, or 10% of the width of the + display if the display size is unknown. The ho and vo values govern the horizontal + and vertical offset respectively. A value of 0.0 positions the + window to the far left or top of the screen, a value of 0.5 + positions it in the center of the screen (the default), and 1.0 + positions it to the far right or bottom of the screen. If three + parameters are provided, then the ss + parameter is a scale factor for the test window size. A value of 0.5 + for instance, would produce a half sized window. A value of 2.0 will + produce a double size window. If four parameters are provided, then + the last two set independent horizontal and vertical scaling + factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be + specified as a single string (no space between the numbers and the + comma). For example, to create a double sized test window at the top + right of the screen, use -P 1,0,2 + . To create a window twice as wide as high: -P 1,0,2,1.
+
+ The -F + flag causes the while screen behind the test window to be masked + with black. This can aid black accuracy when measuring CRT displays + or projectors.
+
+ The -E + 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 -k or -K flag was created using video range + encoding, then this option will be triggered automatically. This + will also set quantization of 8 bits (see -Z flag below). If your + video connection is better than 8 bits (ie. 10 or 12 bits), then you + may wish to raise this default.
+
+ -Z nbits Normally the target device values + are floating point numbers that may get rounded and quantized in the + process of printing them or reproducing them on the display device. + If some of this quantization can be accounted for, it may improve + the accuracy of the resulting profile, and the Q parameter allows this + quantization to be specified. The parameter is the number of binary + digits (bits) that the device values should be quantized to. An idea + of the number of bits of precision that makes its way to your + display can be obtained by using dispcal + -R If Video encoding is selected (see -E flag above), then 8 + bits is selected by default. On systems using an VGA connection or + Display Port with a graphics card with VideoLUT entries with greater + than 8 bits depth, or if using the MadVR rendered with dithering, + then a higher bit depth is typically possible.
+
+ -n: When + running on a UNIX based system that used the X11 Windowing System, dispread + normally selects the override redirect so that the test window will + appear above any other windows on the display. On some systems this + can interfere with window manager operation, and the -n + option turns this behaviour off.
+
+ The -J + option runs through the black and sensor relative calibration + routines for the Xrite DTP92 and DTP94 instrument, the black level + calibration for the Eye-One Display 1, and a CRT frequency + calibration for the Eye-One Display 2. For the black calibration the + instrument should be placed on an opaque, black surface, and any + stray light should be avoided by placing something opaque over the + instrument. If a Spectrolino is being used, then a white and black + calibration will always be performed before the instrument can be + placed on the display, unless the -N flag is used. + Generally it is not necessary to do a calibration every time an + instrument is used, just now and again. There is no point in + doing a CRT frequency calibration, as this will be done + automatically at the commencement of patch reading.
+
+ -N Any + instrument that requires regular calibration will ask for + calibration on initial start-up. Sometimes this can be awkward if + the instrument is being mounted in some sort of measuring jig, or + annoying if several sets of readings are being taken in quick + succession. The -N + suppresses this initial calibration if a valid and not timed out + previous calibration is recorded in the instrument or on the host + computer. It is advisable to only use this option on the second and + subsequent measurements in a single session.
+
+ The -H + option turns on high resolution spectral mode, if the instrument + supports it. See Operation of particular + instruments for more details. This may give better accuracy + for display measurements.
+
+ The -w flag disables the normalisation of + the white patch value to 100.0, resulting in values that are in + cd/m^2. This is mainly for diagnostic purposes.
+
+ The -X file.ccmx option reads + a Colorimeter Correction Matrix + from the given file, and applies it to the colorimeter instruments + readings. This can improve a colorimeters accuracy for a particular + type of display. A list of contributed ccmx files is here.
+
+ The -X file.ccss option reads + a Colorimeter Calibration + Spectral Sample from the given file, and uses it to set the + colorimeter instruments calibration. This will only work with + colorimeters that rely on sensor spectral sensitivity calibration + information (ie. the X-Rite i1d3, + or the DataColor Spyder4 & + Spyder 5).This can improve a colorimeters accuracy for a + particular type of display.
+
+ The -Q flag allows specifying a tristimulus + observer, and is used to compute PCS (Profile Connection Space) + tristimulus values from spectral readings or using a colorimeter + that has CCSS capability. The following choices are available:
+ 1931_2 selects the standard CIE 1931 2 degree + observer. The default.
+ 1964_10 selects the standard CIE 1964 10 degree + observer.
+ 1955_2 selects the Stiles and Birch 1955 2 degree + observer
+ 1978_2 selects the Judd and Voss 1978 2 degree + observer
+ shaw selects the Shaw and Fairchild 1997 2 degree + observer
+ 1964_10c selects a version of the CIE 1964 10 degree + observer that has been adjusted using a 3x3 matrix to better agree + with the 1931 2 degree observer.
+
+ NOTE that if you select + anything other than the default 1931 2 degree observer, that the Y + values will not be cd/m^2, due to the Y curve not being the CIE 1924 + photopic V(λ) luminosity function.
+
+ The -I b|w options invoke + instrument black level, and display white level compensation + (respectively). Instrument black level drift compensation attempts + to combat instrument black calibration drift by using a display + black test patch as a reference. If an instrument is not + acclimatised sufficiently to the measurement conditions, changes in + temperature can affect the black readings. Display white level drift + compensation attempts to combat changes in display brightness as it + warms up by measuring a white patch every so often, and using it to + normalise all the other readings. If just instrument black drift + compensation is needed, use -Ib. + If just display white level compensation is needed, use -Iw. If both are needed, use -Ibw or -Iwb.
+
+ The -Y R:rate + 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.
+
+ The -Y A + option uses a non-adaptive integration time emission measurement + mode, if the instrument supports it, such as the Eye-One Pro, + ColorMunki, i1d3 and K10. By default an adaptive integration time + measurement mode will be used for emission measurements, but some + instruments support a fixed integration time mode that can be used + with display devices. This may give faster measurement times, but + may also give less accurate low level readings.
+
+ The -Y p + 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.
+
+ The -C + "command" option allows a + method of relaying each test value to some other display than that + on the system running dispread (for instance, a photo frame, PDA + screen etc.), by causing the given command to be invoked to the + shell, with six arguments. The first three arguments are the RGB + test color as integers in the range 0 to 255, the second three + parameters are the RGB test color as floating point numbers in the + range 0.0 to 1.0. The script or tool should relay the given color to + the screen in some manner (e.g. by generating a raster file of the + given color and sending it to the display being profiled), before + returning. Note that a test window will also be created on the + system running dispread.
+
+ The -M "command" option allows a + method of gathering each test value from some external source, such + as an instrument that is not directly supported by Argyll. The given + command is involked to the shell, with six arguments. The first + three arguments are the RGB test color as integers in the range 0 to + 255, the second three parameters are the RGB test color as floating + point numbers in the range 0.0 to 1.0. The script or tool should + create a file called "command.meas" + that contains the XYZ values for the given RGB (or measured from the + test window) in cd/m^2 as three numbers separated by spaces, before + returning. If the command returns a non-zero return value, dispread + will abort. Note that a test window will also be created on the + system running dispread.
+
+ The -x flag causes dispread to expect + values to be manually entered for each reading, rather than using an + instrument to do the measurements. This mode is ideal if your + instrument is not supported by Argyll. XYZ values should be entered. + It is possible to navigate about the test values being measured, so + as to do them in any order, as well as re-do values, in case of any + mistakes.
+
+ The -W n|h|x + parameter overrides the default serial communications flow control + setting. The value n turns + all flow control off, h + sets hardware handshaking, and x + sets Xon/Xoff handshaking. This commend may be useful in workaround + serial communications issues with some systems and cables.
+
+ The -D 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.
+
+ The final parameter on the command line is the + base filename for the .ti1 + input file, and the .ti3 + output file. dispread will add the .ti1 and .ti3 extensions + automatically.
+
+ NOTE that on an X11 system, + if the environment variable ARGYLL_IGNORE_XRANDR1_2 + is set (ie. set it to "yes"), then the presence of the XRandR 1.2 + extension will be ignored, and other extensions such as Xinerama and + XF86VidMode extension will be used. This may be a way to work around + buggy XRandR 1.2 implementations.
+
+

+ If a large number of patches is being read, the screensaver on many + systems can interfere with the operation of dispread. It is + therefore advisable in these cases to manually turn off the + screensaver before commencing the measurements.
+
+ If communications break down with a USB connected instrument, you + may have to unplug it, and plug it in again to recover.
+
+ Some systems (Apple OSX in particular) have a special set of user + interface controls ("Universal Access") that allows altering the + display in ways designed to assist visually impaired users, by + increasing contrast etc. This will interfere badly with any attempts + to calibrate or profile such a system, and must be turned off in + order to do so. Note that certain magic keyboard sequences can turn + this on by accident.
+
+
+
+ + diff --git a/doc/dispwin.html b/doc/dispwin.html index dac6b8e..05db989 100644 --- a/doc/dispwin.html +++ b/doc/dispwin.html @@ -1,38 +1,38 @@ - - - - dispwin - - - - -

spectro/dispwin

Summary

- This tool has several different but related functions. When given as - a file argument an ICC profile containing vcgt "gamma" curves, or an - Argyll video calibration .cal file, it will load that calibration - into the chosen display. It can also install or uninstall a profile - in the system for the chosen display, or set the display calibration - to that in the currently installed system profile. By default it - displays a test window the same as that used by dispcal and - dispread, to test this functionality. It can also be used to test - the ability to load video card LUT curves to each display, and to - test how the console Bell will sound when used with some instruments - (ie. Eye-One Pro).
-
- [Note that in OS X 10.7 Lion, changes to the default system profile - permissions mean that you can't set a calibration persistently when - the default system profile is being used, unless you run as root - (ie. use sudo). Note that you do not - need to run as root to install a user profile (-Su, the default - install type.)]
-

Usage

- dispwin - [options] [calfile]
- -v + + + dispwin + + + + +

spectro/dispwin

Summary

+ This tool has several different but related functions. When given as + a file argument an ICC profile containing vcgt "gamma" curves, or an + Argyll video calibration .cal file, it will load that calibration + into the chosen display. It can also install or uninstall a profile + in the system for the chosen display, or set the display calibration + to that in the currently installed system profile. By default it + displays a test window the same as that used by dispcal and + dispread, to test this functionality. It can also be used to test + the ability to load video card LUT curves to each display, and to + test how the console Bell will sound when used with some instruments + (ie. Eye-One Pro).
+
+ [Note that in OS X 10.7 Lion, changes to the default system profile + permissions mean that you can't set a calibration persistently when + the default system profile is being used, unless you run as root + (ie. use sudo). Note that you do not + need to run as root to install a user profile (-Su, the default + install type.)]
+

Usage

+ dispwin + [options] [calfile]
+ -v                   Verbose @@ -51,18 +51,18 @@ Verbose - - mode
- -display displayname [X11 only] Choose X11 display name
- -d n[,m] -             - [X11 only] Choose the - display from the following list (default 1),
+ + mode
+ -display displayname [X11 only] Choose X11 display name
+ -d n[,m] +             + [X11 only] Choose the + display from the following list (default 1),
                      and optionally @@ -81,9 +81,9 @@ optionally - - choose a different display m for Video LUT access.
- -d n                 [Not X11] @@ -102,9 +102,9 @@ X11] - - Choose the display from the following list (default 1)
- + -dweb[:port]         @@ -119,22 +119,22 @@ X11] - - Display via a web server at port (default 8080)
- -dmadvr -              - [MSWin] Display via MadVR Video Renderer
+ + Display via a web server at port (default 8080)
+ -dmadvr +              + [MSWin] Display via MadVR Video Renderer
-dcc[:n]             - -Display via n'th ChromeCast (default 1, ? for - list)
- -P - ho,vo,ss[,vs]     Position test window - and scale it
+ + Display via n'th ChromeCast (default 1, ? for + list)
+ -P + ho,vo,ss[,vs]     Position test window + and scale it
                      ho,vi: 0.0 @@ -153,9 +153,9 @@ ho,vi: - - = left/top, 0.5 = center, 1.0 = right/bottom etc.
+ + = left/top, 0.5 = center, 1.0 = right/bottom etc.
                      ss: 0.5 @@ -174,8 +174,8 @@ ss: - - = half, 1.0 = normal, 2.0 = double etc.
+ + = half, 1.0 = normal, 2.0 = double etc.
                      @@ -188,10 +188,10 @@ ss: - - ss,vs: = optional horizontal, vertical scale.
- -F + + ss,vs: = optional horizontal, vertical scale.
+ -F                   Fill whole @@ -210,10 +210,10 @@ whole - - screen with black background
- -E + + screen with black background
+ -E                   @@ -221,25 +221,25 @@ whole - - Video - encode output as (16-235)/255 "TV" levels
- -i -              -      Run forever with random values
- -G filename -          Display RGB - colors from CGATS file
- -m -              -      Manually step through colors
- Video + encode output as (16-235)/255 "TV" levels
+ -i +              +      Run forever with random values
+ -G filename +          Display RGB + colors from CGATS file
+ -m +              +      Manually step through colors
+ -r                   Test just @@ -258,10 +258,10 @@ just - - video LUT loading & Beeps
- -n + + video LUT loading & Beeps
+ -n                   Test native @@ -280,8 +280,8 @@ native - - display values (rather than through Video LUT and C.M.)
+ + display values (rather than through Video LUT and C.M.)
-s filename.cal      Save the @@ -300,10 +300,10 @@ the - - currently loaded Video LUT to 'filename'
- -c + + currently loaded Video LUT to 'filename'
+ -c                   Load a @@ -322,11 +322,11 @@ a - - linear display calibration (clear calibration)
- -V + + linear display calibration (clear calibration)
+ -V                   Verify that @@ -345,10 +345,10 @@ that - - calfile/profile cal. is currently loaded in LUT
- -I + + calfile/profile cal. is currently loaded in LUT
+ -I                   @@ -365,11 +365,11 @@ that - - Install profile for display and use it's calibration
- -U + + Install profile for display and use it's calibration
+ -U                   @@ -386,9 +386,9 @@ that - - Un-install profile for display
+ + Un-install profile for display
-S d                 Specify the @@ -407,8 +407,8 @@ the - - install/uninstall scope for OS X [nlu] or Vista [lu]
+ + install/uninstall scope for OS X [nlu] or Vista [lu]
                      d is @@ -427,11 +427,11 @@ is - - one of: n = network, l = local system, u = user (default)
- -L + + one of: n = network, l = local system, u = user (default)
+ -L                   @@ -448,11 +448,11 @@ is - - Load installed profiles cal. into Video LUT
- -X + + Load installed profiles cal. into Video LUT
+ -X                   @@ -469,11 +469,11 @@ is - - [X11 only] Run in daemon - loader mode for given X11 server
- X11 only] Run in daemon + loader mode for given X11 server
+ -D [level]           Print debug @@ -492,14 +492,14 @@ debug - - diagnostics to stderr
- calfile
+ calfile              Load display @@ -518,60 +518,60 @@ display - - calibration (.cal or .icm) into - LUT, and exit.
-
-

Comments
-

- The -v flag makes the program more - verbose..
-
- display: - When running on a UNIX based system that used the X11 Windowing - System, dispwin will by default use the $DISPLAY environment - variable to determine which display and screen to read from. This - can be overridden by supplying an X11 display name to the -display option. Note that if - Xinerama is active, you can't select the screen using $DISPLAY or - -display, you have to select it using the -d parameter.
-
- -d: By - default the location of the test window will be the main display. If - the system has more than one display or screen, an alternate - display/screen can be selected with the -d parameter. If you invoke dispwin so as to display the - usage information (i.e. "dispcal -?" or "dispcal --"), then the - discovered displays/screens will be listed. Multiple displays may - not be listed if they appear as a single display to the operating - system (ie. the multi-display support is hidden in the video card - driver). On UNIX based system that used the X11 Windowing System, - the -d parameter will - override the screen specified by the $DISPLAY or -display parameter.
-
- Note that if VideoLUTs for a - display are not accessible (i.e. no hardware calibration - capability), dispwin will - will issue a warning or fail when it attempts to access them.
-
- On X11 the inability to access VideoLUTs could be because you are - trying to access a remote display, and the remote display doesn't - support the XF86VidMode extension, or perhaps you are running - multiple monitors using NVidia TwinView, or MergedFB, and trying to - access anything other than the primary monitor. TwinView and - MergedFB don't properly support the XF86VidMode extension for - multiple displays. You can use dispwin -r - to test whether the VideoLUTs are accessible for a particular - display. See also below, on how to select a different display for - VideoLUT access. Also note that dispcal will fail if the Visual - depth doesn't match the VideoLUT depth. Typically the VideoLUTs have - 256 entries per color component, so the Visual generally needs to be - 24 bits, 8 bits per color component.
-
+ + calibration (.cal or .icm) into + LUT, and exit.
+
+

Comments
+

+ The -v flag makes the program more + verbose..
+
+ display: + When running on a UNIX based system that used the X11 Windowing + System, dispwin will by default use the $DISPLAY environment + variable to determine which display and screen to read from. This + can be overridden by supplying an X11 display name to the -display option. Note that if + Xinerama is active, you can't select the screen using $DISPLAY or + -display, you have to select it using the -d parameter.
+
+ -d: By + default the location of the test window will be the main display. If + the system has more than one display or screen, an alternate + display/screen can be selected with the -d parameter. If you invoke dispwin so as to display the + usage information (i.e. "dispcal -?" or "dispcal --"), then the + discovered displays/screens will be listed. Multiple displays may + not be listed if they appear as a single display to the operating + system (ie. the multi-display support is hidden in the video card + driver). On UNIX based system that used the X11 Windowing System, + the -d parameter will + override the screen specified by the $DISPLAY or -display parameter.
+
+ Note that if VideoLUTs for a + display are not accessible (i.e. no hardware calibration + capability), dispwin will + will issue a warning or fail when it attempts to access them.
+
+ On X11 the inability to access VideoLUTs could be because you are + trying to access a remote display, and the remote display doesn't + support the XF86VidMode extension, or perhaps you are running + multiple monitors using NVidia TwinView, or MergedFB, and trying to + access anything other than the primary monitor. TwinView and + MergedFB don't properly support the XF86VidMode extension for + multiple displays. You can use dispwin -r + to test whether the VideoLUTs are accessible for a particular + display. See also below, on how to select a different display for + VideoLUT access. Also note that dispcal will fail if the Visual + depth doesn't match the VideoLUT depth. Typically the VideoLUTs have + 256 entries per color component, so the Visual generally needs to be + 24 bits, 8 bits per color component.
+
-d n[,m]Because of the @@ -590,257 +590,257 @@ the - - difficulty cause by TwinView and MergedFB in X11 based systems, you - can optionally specify a separate display number after the display - that is going to be used to present test patches, for accessing the - VideoLUT hardware. This must be specified as a single string, e.g. -d 1,2 . Some experimentation - may be needed on such systems, to discover what screen has access to - the VideoLUT hardware, and which screens the test patches appear on. - You may be able to calibrate one screen, and then share the - calibration with another screen. Profiling can be done independently - to calibration.
-
- -dweb or - -dweb:port starts a - standalone web server on your machine, which then allows a local or - remote web browser to display the the color test patches. By default - port 8080 is used, but this - can be overridden by appending a : - and the port number i.e. -dweb:8001. - The URL will be http:// - then name of the machine or its I.P. address followed by a colon and - the port number - e.g something like http://192.168.0.1:8080. If you use the verbose - option (-v) then a likely - URL will be printed once the server is started, or you could run ipconfig (MSWin) or /sbin/ifconfig (Linux or OS X) - and identify an internet address for your machine that way. JavaScript - needs to be enabled in your web browser for this to work. You may - have to modify any firewall to permit port 8080 to be accessed on - your machine.
-
- Note that if you use this method of accessing a display, that there - is no access to the display Video Lookup tables, and that any - operation that depends on accessing the VideoLUTs will either - generate a warning or fail.
-
- -dmadvr - [MSWin only] causes test patches to be displayed using the MadVR - video renderer. Note that will have to start MadTPG before - running dispread, and that while you can adjust the "Test Pattern - Configuration" controls, you should not normally alter the - "Existing Calibration" controls, as dispread will set these - appropriately. See -n flag.
-
- -dcc or -dcc:no - causes test patches to be displayed using and available ChromeCast to - your TV. Use -dcc:? to display a list of ChromeCasts on your - local network. Note that the ChromeCast as a test patch source is - probably the least accurate of your choices, since it - up-samples the test patch and transforms from RGB to YCC and back, - but should be accurate within � 1 bit. You may have to modify any - firewall to permit port 8081 to be accessed on your machine if it + + difficulty cause by TwinView and MergedFB in X11 based systems, you + can optionally specify a separate display number after the display + that is going to be used to present test patches, for accessing the + VideoLUT hardware. This must be specified as a single string, e.g. -d 1,2 . Some experimentation + may be needed on such systems, to discover what screen has access to + the VideoLUT hardware, and which screens the test patches appear on. + You may be able to calibrate one screen, and then share the + calibration with another screen. Profiling can be done independently + to calibration.
+
+ -dweb or + -dweb:port starts a + standalone web server on your machine, which then allows a local or + remote web browser to display the the color test patches. By default + port 8080 is used, but this + can be overridden by appending a : + and the port number i.e. -dweb:8001. + The URL will be http:// + then name of the machine or its I.P. address followed by a colon and + the port number - e.g something like http://192.168.0.1:8080. If you use the verbose + option (-v) then a likely + URL will be printed once the server is started, or you could run ipconfig (MSWin) or /sbin/ifconfig (Linux or OS X) + and identify an internet address for your machine that way. JavaScript + needs to be enabled in your web browser for this to work. You may + have to modify any firewall to permit port 8080 to be accessed on + your machine.
+
+ Note that if you use this method of accessing a display, that there + is no access to the display Video Lookup tables, and that any + operation that depends on accessing the VideoLUTs will either + generate a warning or fail.
+
+ -dmadvr + [MSWin only] causes test patches to be displayed using the MadVR + video renderer. Note that will have to start MadTPG before + running dispread, and that while you can adjust the "Test Pattern + Configuration" controls, you should not normally alter the + "Existing Calibration" controls, as dispread will set these + appropriately. See -n flag.
+
+ -dcc or -dcc:no + causes test patches to be displayed using and available ChromeCast to + your TV. Use -dcc:? to display a list of ChromeCasts on your + local network. Note that the ChromeCast as a test patch source is + probably the least accurate of your choices, since it + up-samples the test patch and transforms from RGB to YCC and back, + but should be accurate within � 1 bit. You may have to modify any + firewall to permit port 8081 to be accessed on your machine if it falls back to the Default receiver (see installation - - instructions for your platform).
-
- The -P - parameter allows you to position and size the test patch window. By - default it is places in the center of the screen, and sized - appropriately for the type of instrument, or 10% of the width of the - display if the display size is unknown.. The ho and vo values govern the horizontal - and vertical offset respectively. A value of 0.0 positions the - window to the far left or top of the screen, a value of 0.5 - positions it in the center of the screen (the default), and 1.0 - positions it to the far right or bottom of the screen. If three - parameters are provided, then the ss - parameter is a scale factor for the test window size. A value of 0.5 - for instance, would produce a half sized window. A value of 2.0 will - produce a double size window. If four parameters are provided, then - the last two set independent horizontal and vertical scaling - factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be - specified as a single string (no space between the numbers and the - comma). For example, to create a double sized test window at the top - right of the screen, use -P 1,0,2 - . To create a window twice as wide as high: -P 1,0,2,1.
-
- The -F - flag causes the while screen behind the test window to be masked - with black. This can aid black accuracy when measuring CRT displays - or projectors.
-
- The -E - 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.
-
- By default dispwin will put - a test window on the selected display, and display some test colors, - before darkening then brightening the screen by loading video - LUT values, test the bell sounds, then restore the original values - and exit.
-
- If the -i - flag is set, then dispwin - will display the preset sequence, then random test colors forever.
-
- If the -G - parameter is set, then dispwin - will display the sequence of RGB color in the supplied CGATS file, - e.g. a .ti1 file. Typically this might the used with the -m option to manually measure a - set of test patches.
-
- If the -m - flag is set, then dispwin - will display the preset sequence then exits, but advances manually - after each return key.
-
- If the -r - flag is set, then dispwin - will test just the loading of video LUT values by first darkening, - then lightening the screen, before exiting.
-
- If the -n - flag is set, then dispwin - will display the colors directly on the display, rather than having - the color values translated through the currently loaded Video LUTs. - In the case of using the MadVR renderer to display the patches, any - 3dLut will also be disabled.
-
- If a -s filename.cal option is - used, then rather than displaying a test window, dispwin will save the currently - loaded calibration curves to the given calibration file. Note that - other functions such as clearing or loading a calibration can be - performed after this action.
-
- If a -c - flag is used, then rather than displaying a test window, dispwin will load the selected - display with a linear set of Video LUT curves, effectively clearing - the calibration, and will then exit. Note that other functions such - as loading a calibration can be performed after this action.
-
- If a -V - flag is used, then rather than loading the calibration specified as - the final argument, the currently loaded calibration will be - verified as being the same as the given calibration file. If this is - combined with the -L flag, the currently - loaded calibration will be verified as being the same as the - installed system profile for the display.
-
- -I: The ICC - profile specified as the final argument will be installed as the - default operating system profile for the chosen display, and the - display calibration will be set to the calibration tag ('vcgt' tag, - if any) in that profile.. On MSWindows and OS X this means that the - profile will be copied to the appropriate color profile directory - and registered with the operating system. For Linux X11 systems, the - profile will be installed using the ucmm - convention, and the X11 _ICC_PROFILE property in the root window, - and also the the XrandR 1.2 X11 _ICC_PROFILE output property on - systems that are running XrandR 1.2 or later. The latter is - following this convention - for allowing applications to locate the display profile for a - particular X11 display, and expands it to accomodate XrandR 1.2. - Note that for X11 systems, the properties are not persistent, and - will need to be loaded each time the X11 server is started (see the - -L flag). To make sure that the profile calbration - 'vcgt' tag gets loaded into the Graphics Card at system start, - please read the guide here.
-
- -U: The ICC - profile specified as the final argument will be un-installed as the - default operating system profile for the chosen display. The display - calibration will remain unchanged.
-
- -S d: Some - systems have more than one profile scope that an installed profile - will apply to, and this parameter allows overriding the default user - scope. On OS X, there is a choice of three scopes: n: for network scope, if people - are sharing profiles over a network, l: local system scope, which installs the profile - for all users of a system, and the default u, which covers just the user - installing the profile. On Linux or Microsoft Vista, just the local - system l and user u scope are available. Note that - you may need to run dispwin with elevated privileges(sudo) to be - able to successfully use network or local system scope. This option - also applies to uninstalling a profile. Note that to install a user - profile for the root account, you will have to login as root (sudo - will not achieve this).
-
- -L: This - option fetches the current installed system profile for the chosen - display, and sets the display to the calibration tag ('vcgt' tag, if - any) in the profile. This is a convenient way of initializing the - display on system startup from the installed display profile, if the - system doesn't not do this automatically .
-
- -X: Daemon - mode (experimental). When running on a UNIX based system that used - the X11 Windowing System, this option runs dispwin in a "daemon" - mode where it monitors the given X11 server, waiting for any changes - in monitors that may require loading a matching ICC profile (ie. - such as re-configuring, plugging in a different monitor etc.) - This only works if XRandR 1.2 is available on the server. By default - dispwin runs silently, and will not terminate. If the -v option is given, it will emit - messages to stdout to show what it is doing. When it is first - invoked, it will load the installed profiles of all the screens of - the given X11 server.
-
- The -D flag causes diagnostics to be printed - to stdout. A level can be set between 1 .. 9, that may give - progressively more verbose information. This can be useful in - tracking down why an operation fails.
-
- The final optional parameter on the command line - is the name of an ICC profile that contains a Video LUT vcgt tag, or an Argyll .cal format display calibration. If - this parameter is provided, then the selected display will be loaded - with the given calibration. If the -V - flag was given, then it is verified that this calibration is the - currently loaded one. This may be useful in initializing a - system to the current calibration on system startup, although a - better way may be to install the profile (-I option), and then just use -L. Note that the vcgt tag - interpretation within Argyll is consistent with that of the - originators of the tag. Other ICC profile vcgt implementations may - not be so consistent.
-
- NOTE that on an X11 system, - if the environment variable ARGYLL_IGNORE_XRANDR1_2 - is set (ie. set it to "yes"), then the presence of the XRandR 1.2 - extension will be ignored, and other extensions such as Xinerama and - XF86VidMode extension will be used. This may be a way to work around - buggy XRandR 1.2 implementations.
-
- NOTE on MSWin systems that you will have to disable any - other calibration installer program if you want to be able to - control calibration using dispwin. Note also that there are other - programs that will interfere with calibration loading, such as - igfxpers.exe that gets installed with nVidia "Optimus" technology.
-
-
-
-
- - + + instructions for your platform).
+
+ The -P + parameter allows you to position and size the test patch window. By + default it is places in the center of the screen, and sized + appropriately for the type of instrument, or 10% of the width of the + display if the display size is unknown.. The ho and vo values govern the horizontal + and vertical offset respectively. A value of 0.0 positions the + window to the far left or top of the screen, a value of 0.5 + positions it in the center of the screen (the default), and 1.0 + positions it to the far right or bottom of the screen. If three + parameters are provided, then the ss + parameter is a scale factor for the test window size. A value of 0.5 + for instance, would produce a half sized window. A value of 2.0 will + produce a double size window. If four parameters are provided, then + the last two set independent horizontal and vertical scaling + factors. Note that the ho,vo,ss or ho,vo,hs,vs numbers must be + specified as a single string (no space between the numbers and the + comma). For example, to create a double sized test window at the top + right of the screen, use -P 1,0,2 + . To create a window twice as wide as high: -P 1,0,2,1.
+
+ The -F + flag causes the while screen behind the test window to be masked + with black. This can aid black accuracy when measuring CRT displays + or projectors.
+
+ The -E + 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.
+
+ By default dispwin will put + a test window on the selected display, and display some test colors, + before darkening then brightening the screen by loading video + LUT values, test the bell sounds, then restore the original values + and exit.
+
+ If the -i + flag is set, then dispwin + will display the preset sequence, then random test colors forever.
+
+ If the -G + parameter is set, then dispwin + will display the sequence of RGB color in the supplied CGATS file, + e.g. a .ti1 file. Typically this might the used with the -m option to manually measure a + set of test patches.
+
+ If the -m + flag is set, then dispwin + will display the preset sequence then exits, but advances manually + after each return key.
+
+ If the -r + flag is set, then dispwin + will test just the loading of video LUT values by first darkening, + then lightening the screen, before exiting.
+
+ If the -n + flag is set, then dispwin + will display the colors directly on the display, rather than having + the color values translated through the currently loaded Video LUTs. + In the case of using the MadVR renderer to display the patches, any + 3dLut will also be disabled.
+
+ If a -s filename.cal option is + used, then rather than displaying a test window, dispwin will save the currently + loaded calibration curves to the given calibration file. Note that + other functions such as clearing or loading a calibration can be + performed after this action.
+
+ If a -c + flag is used, then rather than displaying a test window, dispwin will load the selected + display with a linear set of Video LUT curves, effectively clearing + the calibration, and will then exit. Note that other functions such + as loading a calibration can be performed after this action.
+
+ If a -V + flag is used, then rather than loading the calibration specified as + the final argument, the currently loaded calibration will be + verified as being the same as the given calibration file. If this is + combined with the -L flag, the currently + loaded calibration will be verified as being the same as the + installed system profile for the display.
+
+ -I: The ICC + profile specified as the final argument will be installed as the + default operating system profile for the chosen display, and the + display calibration will be set to the calibration tag ('vcgt' tag, + if any) in that profile.. On MSWindows and OS X this means that the + profile will be copied to the appropriate color profile directory + and registered with the operating system. For Linux X11 systems, the + profile will be installed using the ucmm + convention, and the X11 _ICC_PROFILE property in the root window, + and also the the XrandR 1.2 X11 _ICC_PROFILE output property on + systems that are running XrandR 1.2 or later. The latter is + following this convention + for allowing applications to locate the display profile for a + particular X11 display, and expands it to accomodate XrandR 1.2. + Note that for X11 systems, the properties are not persistent, and + will need to be loaded each time the X11 server is started (see the + -L flag). To make sure that the profile calbration + 'vcgt' tag gets loaded into the Graphics Card at system start, + please read the guide here.
+
+ -U: The ICC + profile specified as the final argument will be un-installed as the + default operating system profile for the chosen display. The display + calibration will remain unchanged.
+
+ -S d: Some + systems have more than one profile scope that an installed profile + will apply to, and this parameter allows overriding the default user + scope. On OS X, there is a choice of three scopes: n: for network scope, if people + are sharing profiles over a network, l: local system scope, which installs the profile + for all users of a system, and the default u, which covers just the user + installing the profile. On Linux or Microsoft Vista, just the local + system l and user u scope are available. Note that + you may need to run dispwin with elevated privileges(sudo) to be + able to successfully use network or local system scope. This option + also applies to uninstalling a profile. Note that to install a user + profile for the root account, you will have to login as root (sudo + will not achieve this).
+
+ -L: This + option fetches the current installed system profile for the chosen + display, and sets the display to the calibration tag ('vcgt' tag, if + any) in the profile. This is a convenient way of initializing the + display on system startup from the installed display profile, if the + system doesn't not do this automatically .
+
+ -X: Daemon + mode (experimental). When running on a UNIX based system that used + the X11 Windowing System, this option runs dispwin in a "daemon" + mode where it monitors the given X11 server, waiting for any changes + in monitors that may require loading a matching ICC profile (ie. + such as re-configuring, plugging in a different monitor etc.) + This only works if XRandR 1.2 is available on the server. By default + dispwin runs silently, and will not terminate. If the -v option is given, it will emit + messages to stdout to show what it is doing. When it is first + invoked, it will load the installed profiles of all the screens of + the given X11 server.
+
+ The -D flag causes diagnostics to be printed + to stdout. A level can be set between 1 .. 9, that may give + progressively more verbose information. This can be useful in + tracking down why an operation fails.
+
+ The final optional parameter on the command line + is the name of an ICC profile that contains a Video LUT vcgt tag, or an Argyll .cal format display calibration. If + this parameter is provided, then the selected display will be loaded + with the given calibration. If the -V + flag was given, then it is verified that this calibration is the + currently loaded one. This may be useful in initializing a + system to the current calibration on system startup, although a + better way may be to install the profile (-I option), and then just use -L. Note that the vcgt tag + interpretation within Argyll is consistent with that of the + originators of the tag. Other ICC profile vcgt implementations may + not be so consistent.
+
+ NOTE that on an X11 system, + if the environment variable ARGYLL_IGNORE_XRANDR1_2 + is set (ie. set it to "yes"), then the presence of the XRandR 1.2 + extension will be ignored, and other extensions such as Xinerama and + XF86VidMode extension will be used. This may be a way to work around + buggy XRandR 1.2 implementations.
+
+ NOTE on MSWin systems that you will have to disable any + other calibration installer program if you want to be able to + control calibration using dispwin. Note also that there are other + programs that will interfere with calibration loading, such as + igfxpers.exe that gets installed with nVidia "Optimus" technology.
+
+
+
+
+ + diff --git a/doc/i1proDriver.html b/doc/i1proDriver.html index 0894f59..e29d639 100644 --- a/doc/i1proDriver.html +++ b/doc/i1proDriver.html @@ -1,157 +1,195 @@ - - The i1pro Driver - - - - -

How can I -have confidence in the i1pro Driver ?
-

-A question that has been asked is : "You've -written your own driver for the Eye-One Pro. How can I have confidence -that the measurements are accurate, and will match those made with the -original manufacturers driver ?"
-
-This is a quite reasonable question. The following attempts to answer -it.
-

Why does Argyll use it's own -i1pro driver ?

-Primarily because the Original Manufacturers Driver (OMD) isn't -available for all the platforms that ArgyllCMS supports (Linux in -particular). A side benefit is that it's possible to tweak many of the -driver parameters for slightly better results and more flexibility. It -has also helped in understanding the characteristics and limitations of -such instruments.
-

Does it match the OMD ?

-In principle the behaviour should be very similar. While the Argyll -driver has been written from scratch, it does use exactly the same -calibration values from
-inside the instrument, and attempts to use the calibration values and -process the raw instrument readings in an equivalent manner to that of -the OMD.
-
-But the proof of the pudding is in the measuring, so to actually verify -this, the following experiment was conducted:
-
-The Argyll version used was V1.2.0
-
-The Macbeth 24 patch ColorChecker was used as a sample target. For each -patch (and the calibration tile), the following steps were performed:
-
-1) Place the instrument on the calibration tile.
-
-2) Use Argyll spotread to calibrate the Argyll driver.
-
-3) Change drivers to the OMD.
-
-4) Use the OMD to calibrate the instrument.
-
-5) Move the instrument to the patch on the ColorChecker.
-
-6) Read the color using the OMD.
-
-7) Change the back to the Argyll driver.
-
-8) Using the calibration made in step 2), read the color using Argyll.
-
-Each calibration or reading was performed 15 seconds from the previous -one, to put the instrument lamp in a repeatable state.
-The instrument was kept in exactly the same position for calibration -and patch measurement with the two drivers.
-(The whole idea is to reduce all other sources of error, other than the -driver itself.)
-
-This measurement was repeated just once for each patch + the -calibration tile. This was done in one run, and the readings were not -specially selected.
-

Results:

-The following D50 L*a*b* values were recorded for each measurement:
-
-A)    The OMD internally calculated L*a*b* value
-B)    The L*a*b* value calculated by Argyll from the OMD -spectral values.
-C)    The L*a*b* value calculated from the Argyll measured -spectral values.
-D)    The L*a*b* value calculated from the Argyll -Hi-Resolution mode measured spectral values.
-
-A is compare to B, to check -that the spectral to standard observer calculations are equivalent.
-
-    The result was an average Delta E (CIE76) of 0.006, -with a maximum of 0.012.
-
-    This shows that there is very close agreement in the -way spectral values are converted to XYZ and L*a*b*.
-
-B is compared to C to check -that the Argyll driver behaves the same as the OMD.
-
-    The result was an average Delta E (CIE76) of 0.028, -with a maximum of 0.051.
-
-    This shows that the OMD and Argyll driver are in -close agreement in spectral measurement.
-    This error is an order of magnitude smaller than -uniformity induced errors typical in the media being measured.
-
-A is compared to C to check -that the Argyll driver and spectral to XYZ differences don't compound.
-
-    The result was an average -Delta E (CIE76) of 0.026, with -a maximum of 0.048.
-
-    Rather than compounding, any spectral to XYZ -differences tend to cancel -out slightly. This is the bottom line -experimental difference between -the two drivers. The actual underlying difference may in fact be less -than this, but it would be necessary to do multiple test runs to -filter out experimental error.
-
-C is compare to D to check -that the Argyll Hi-Resolution mode is behaving reasonably.
-
-    The result was an average Delta E (CIE76) of 0.158, -with a maximum of 0.353.
-
-    Because the ColorChecker samples have relatively -smooth reflectance spectra, it can be expected that
-    the normal and Hi-Res mode results should be fairly -similar. And indeed, this is the case. The biggest
-    differences are for patches -with the largest spectral transitions in them, which is to be expected -as the
-    Hi-Res measurement more -closely follows the spectral shape, while the differences for -spectrally flat
-    patches is neglegable, since both can follow the -spectral shape well.
-
-Example Yellow-Green Patch, Hi-Res & Normal spectrum:
- Yellow-Green patch, Hi-Res vs. Normal

-
-

Conclusions:

-The experimental average difference of 0.026 -Delta E76 shown above provides evidence that despite using a completely -different instrument driver to that supplied with the instrument, the -ArgyllCMS Eye-One pro measurement values have comparable accuracy, and -can be relied upon to match measurements made using the original -manufactures driver.
-

Raw Data:

-The raw data is available in this spread -sheet.
-
-
-
-
-
-
- + + The i1pro Driver + + + + +

How can I + have confidence in the i1pro Driver ?
+

+ A question that has been asked is : "You've + written your own driver for the Eye-One Pro. How can I have + confidence + that the measurements are accurate, and will match those made with + the + original manufacturers driver ?"
+
+ This is a quite reasonable question. The following attempts to + answer + it.
+

Why does Argyll use it's own + i1pro driver ?

+ Primarily because the Original Manufacturers Driver (OMD) isn't + available for all the platforms that ArgyllCMS supports (Linux in + particular). A side benefit is that it's possible to tweak many of + the + driver parameters for slightly better results and more flexibility. + It + has also helped in understanding the characteristics and limitations + of + such instruments.
+

Does it match the OMD ?

+ In principle the behaviour should be very similar. While the Argyll + driver has been written from scratch, it does use exactly the same + calibration values from
+ inside the instrument, and attempts to use the calibration values + and + process the raw instrument readings in an equivalent manner to that + of + the OMD.
+
+ But the proof of the pudding is in the measuring, so to actually + verify + this, the following experiment was conducted:
+
+ The Argyll version used was V1.2.0
+ The OMD is the original version prior to the introduction of the + i1pro2, and hence reporting the native instrument measurements, + rather than applying a conversion to the XRGA standard
+
+ The Macbeth 24 patch ColorChecker was used as a sample target. For + each + patch (and the calibration tile), the following steps were + performed:
+
+ 1) Place the instrument on the calibration tile.
+
+ 2) Use Argyll spotread to calibrate the Argyll driver.
+
+ 3) Change drivers to the OMD.
+
+ 4) Use the OMD to calibrate the instrument.
+
+ 5) Move the instrument to the patch on the ColorChecker.
+
+ 6) Read the color using the OMD.
+
+ 7) Change the back to the Argyll driver.
+
+ 8) Using the calibration made in step 2), read the color using + Argyll.
+
+ Each calibration or reading was performed 15 seconds from the + previous + one, to put the instrument lamp in a repeatable state.
+ The instrument was kept in exactly the same position for calibration + and patch measurement with the two drivers.
+ (The whole idea is to reduce all other sources of error, other than + the + driver itself.)
+
+ This measurement was repeated just once for each patch + the + calibration tile. This was done in one run, and the readings were + not + specially selected.
+

Results:

+ The following D50 L*a*b* values were recorded for each measurement:
+
+ A)    The OMD internally calculated L*a*b* value
+ B)    The L*a*b* value calculated by Argyll from the OMD + spectral values.
+ C)    The L*a*b* value calculated from the Argyll measured + spectral values.
+ D)    The L*a*b* value calculated from the Argyll + Hi-Resolution mode measured spectral values.
+
+ A is compare to B, to + check + that the spectral to standard observer calculations are + equivalent.
+
+     The result was an average Delta E (CIE76) of + 0.006, + with a maximum of 0.012.
+
+     This shows that there is very close agreement in + the + way spectral values are converted to XYZ and L*a*b*.
+
+ B is compared to C to + check + that the Argyll driver behaves the same as the OMD.
+
+     The result was an average Delta E (CIE76) of + 0.028, + with a maximum of 0.051.
+
+     This shows that the OMD and Argyll driver are in + close agreement in spectral measurement.
+     This error is an order of magnitude smaller than + uniformity induced errors typical in the media being measured.
+
+ A is compared to C to + check + that the Argyll driver and spectral to XYZ differences don't + compound.
+
+     The result was an average + Delta E (CIE76) of 0.026, + with + a maximum of 0.048.
+
+     Rather than compounding, any spectral to XYZ + differences tend to cancel + out slightly. This is the bottom + line + experimental difference between + the two drivers. The actual underlying difference may in fact be + less + than this, but it would be necessary to do multiple test runs to + filter out experimental error.
+
+ C is compare to D to check + that the Argyll Hi-Resolution mode is behaving reasonably.
+
+     The result was an average Delta E (CIE76) of + 0.158, + with a maximum of 0.353.
+
+     Because the ColorChecker samples have relatively + smooth reflectance spectra, it can be expected that
+     the normal and Hi-Res mode results should be + fairly + similar. And indeed, this is the case. The biggest
+     differences are for patches + with the largest spectral transitions in them, which is to be + expected + as the
+     Hi-Res measurement more + closely follows the spectral shape, while the differences for + spectrally flat
+     patches is neglegable, since both can follow the + spectral shape well.
+
+ Example Yellow-Green Patch, Hi-Res & Normal spectrum:
+ Yellow-Green patch,
+ Hi-Res vs. Normal

+
+

Conclusions:

+ The experimental average difference of 0.026 + Delta E76 shown above provides evidence that despite using a + completely + different instrument driver to that supplied with the instrument, + the + ArgyllCMS Eye-One pro measurement values have comparable accuracy, + and + can be relied upon to match measurements made using the original + manufactures driver.
+

Raw Data:

+ The raw data is available in this spread + sheet.
+
+
+
+
+
+
+ diff --git a/doc/iccgamut.html b/doc/iccgamut.html index ead8f7c..e6fb097 100644 --- a/doc/iccgamut.html +++ b/doc/iccgamut.html @@ -16,8 +16,8 @@ in Lab or CIECAM02 Jab colorspace, and can also representing the gamut as a X3DOM file.

- See 3D Viewing - Format for switching to VRML or X3D output format.
+ See 3D Viewing Format for switching to + VRML or X3D output format.

Usage

iccgamut [-options]
-d sres       Surface resolution @@ -36,6 +37,7 @@ -w            emit + X3DOM .x3d.html file as well as CGATS .gam file
-n            @@ -45,11 +47,13 @@ Don't + add X3DOM axes or white/black point
-k            Add + X3DOM markers for prim. & sec. "cusp" points
-f @@ -66,6 +70,7 @@ s + = saturation, a = absolute (default), d = profile default
@@ -81,6 +86,7 @@ r + = reverse (priority: monochrome > matrix > lut)
-p oride
        @@ -125,6 +133,7 @@ either + pc - Critical print evaluation environment (ISO-3664 P1)
@@ -135,6 +144,7 @@ either + mt - Monitor in typical work environment
        @@ -144,6 +154,7 @@ either + mb - Monitor in bright work environment
    @@ -173,6 +184,7 @@ s:surround   + n = auto, a = average, m = dim, d = dark,
               @@ -182,6 +194,7 @@ s:surround   +    c = transparency (default average)
         @@ -191,6 +204,7 @@ w:X:Y:Z      + Adapted white point as XYZ (default media white)
         @@ -200,6 +214,7 @@ w:x:y        + Adapted white point as x, y
         @@ -209,6 +224,7 @@ a:adaptation + Adaptation luminance in cd.m^2 (default 50.0)
         @@ -219,6 +235,7 @@ Background + % of image luminance (default 20)
         l:imagewhite Image white in cd.m^2 if surround = auto (default 250)
         @@ -241,6 +259,7 @@ f:flare      + g:X:Y:Z      Glare color as XYZ (default media white)
         @@ -248,8 +267,11 @@ f:flare      + g:x:y        Glare color as x, y
+ -x pcent       + Expand/compress gamut cylindrically by percent
-s             Create @@ -257,6 +279,7 @@ Create + special cube surface topology plot
profile
+ The -x parameter allows expanding or compressing the + resulting gamut in a cylindrical direction by the given percentage + :- i.e "-x 120" will expand by 20%. This may be useful for creating + a general compression gamut mapping by using such an expanded device + gamut as input to collink -g or -G.
+
The -s 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 diff --git a/doc/iccgamutmapping.html b/doc/iccgamutmapping.html index 8deab44..11994c1 100644 --- a/doc/iccgamutmapping.html +++ b/doc/iccgamutmapping.html @@ -10,13 +10,12 @@
How ICC profiles support different intents
cLUT (Color Lookup Table) based ICC profiles support multiple intents by having a table for - each - intent. In a typical device cLUT profile, there are up to 6 cLUT's, - three for input (AtoB tables, that convert from device space to PCS - (Profile connection space)), and three for output (BtoA tables, that - convert from PCS to device space). The tables allow the use of - different color transforms, each transform being tailored for a - different effect:
+ each intent. In a typical device cLUT profile, there are up to 6 + cLUT's, three for input (AtoB tables, that convert from device space + to PCS (Profile connection space)), and three for output (BtoA + tables, that convert from PCS to device space). The tables allow the + use of different color transforms, each transform being tailored for + a different effect:

AtoB0, BtoA0:   Perceptual
AtoB1, BtoA1:   Colorimetric
@@ -24,179 +23,144 @@
The colorimetric intent is meant to convey the exact device color behaviour, without any gamut mapping. Typically it is used to store - the - devices behaviour (characterization), and is also used where exact - color reproduction is required, such as for proofing. The - Colorimetric - tables double up for both relative colorimetric and + the devices behaviour (characterization), and is also used where + exact color reproduction is required, such as for proofing. The + Colorimetric tables double up for both relative colorimetric and absolute colorimetric with the application of a white point restoration.

The Perceptual and Saturation tables are meant to contain gamut - mapping - combined with the device characterization. The allowance for this in - both the AtoB direction, as well as the BtoA direction permits a - profile to gamut map from the device gamut to some intermediate - gamut, - and then from the intermediate gamut to the device gamut.
+ mapping combined with the device characterization. The allowance for + this in both the AtoB direction, as well as the BtoA direction + permits a profile to gamut map from the device gamut to some + intermediate gamut, and then from the intermediate gamut to the + device gamut.

[Note that Shaper/Matrix profiles are always Colorimetric intent, - since - there is only a single transformation, and it does not have the - necessary flexibility to accommodate gamut mapping.]
+ since there is only a single transformation, and it does not have + the necessary flexibility to accommodate gamut mapping.]

ICC Version 2 behaviour

Apart from defining the general purpose of the different tables, the ICC Version 2 specification doesn't specify exactly how they are to achieve this, so it is up to the profile maker to make a choice in - this - regard. There is no common gamut boundary specified for the PCS, and - such an approach limits the achievable intents in any case (see ICC - Version 4 behaviour for an explanation why).
+ this regard. There is no common gamut boundary specified for the + PCS, and such an approach limits the achievable intents in any case + (see ICC Version 4 behaviour for an explanation why).

What I've chosen to do with Argyll profiles, is to make all the AtoB tables the same as colorimetric. This means that the conversion used for the source profile is always colorimetric, and also means that - the - source gamut seen by the destination profile is the source - colorspace - gamut. This means that the gamut mapping is done solely in the BtoA - tables, - and that their task is to map the source colorspace gamut to the - destination colorspace gamut. So to construct the perceptual and - saturation intent mapping tables, a source profile or source gamut - needs to be specified, so that a gamut mapping can be constructed.
+ the source gamut seen by the destination profile is the source + colorspace gamut. This means that the gamut mapping is done solely + in the BtoA tables, and that their task is to map the source + colorspace gamut to the destination colorspace gamut. So to + construct the perceptual and saturation intent mapping tables, a + source profile or source gamut needs to be specified, so that a + gamut mapping can be constructed.

The advantages of this approach is that the behaviour is precisely defined, a full range of gamut mapping options is available, and compatibility with matrix profiles (which do not have gamut mapping transforms) and other foreign profiles can be assured, by simply - using - such profiles as colorimetric sources. The main disadvantage is that - the gamut mapping will only operate exactly as intended when the - profile is linked with the source profile it was setup for. This is - really a fundamental limitation of the idea of having pre-computed - gamut mapping color transforms, that the ICC profile format was - intended to support.
+ using such profiles as colorimetric sources. The main disadvantage + is that the gamut mapping will only operate exactly as intended when + the profile is linked with the source profile it was setup for. This + is really a fundamental limitation of the idea of having + pre-computed gamut mapping color transforms, that the ICC profile + format was intended to support.

Some non-Argyll profile have gamut mapping transforms in their Perceptual and Saturation A2B tables, and this means that the - apparent - gamut of a source through these tables may be different to the - actual - device gamut. To accommodate using these profiles with CMM's (Color - Management Modules) that do not permit the separate choice of intent - tables for the source and destination profiles, Argyll will by - default - use the gamut defined by the source profile perceptual table to - create the gamut mapping of the destination perceptual table, and - the - source saturation table to make the destination saturation table. - Note - that this can affect the exact nature of the gamut mapping, the - distortion of the source gamut changing the apparent relationship - between it and the destination gamut - see "ICC Version 4 behavior" - for - an illustration of the kind of changes this causes. [This default - can - be overridden though using the colprof -nP and -nS flags.]
+ apparent gamut of a source through these tables may be different to + the actual device gamut. To accommodate using these profiles with + CMM's (Color Management Modules) that do not permit the separate + choice of intent tables for the source and destination profiles, + Argyll will by default use the gamut defined by the source profile + perceptual table to create the gamut mapping of the destination + perceptual table, and the source saturation table to make the + destination saturation table. Note that this can affect the exact + nature of the gamut mapping, the distortion of the source gamut + changing the apparent relationship between it and the destination + gamut - see "ICC Version 4 behavior" for an illustration of the kind + of changes this causes. [This default can be overridden though using + the colprof -nP and -nS flags.]

ICC Version 4 behaviour
(Note that Argyll does not currently support ICC V4)

- By default, ICC Version 4 profile operates similarly to the ICC - V2 profile in regard to gamut mapping, with the exception that a + By default, ICC Version 4 profile operates similarly to the ICC V2 + profile in regard to gamut mapping, with the exception that a minimally specified reference medium and reference viewing conditions are introduced for perceptual (and presumably saturation) tables, allowing at least the luminance range to have a well defined behavior when mixing and matching the perceptual A2B and B2A tables - of different profiles. A slight adjustment was made to - the permitted tag contents, to allow things like Display profiles to - contain the full range of AtoB and BtoA tables, so that they could - also - be gamut mapped. An optional part of ICCV4, introduces a more - comprehensively specified Profile - Reference Medium Gamut - (PRMG) as an - intermediate gamut boundary between the source colorspace, and the - destination colorspace. If this option is used, then an additional - tag - in the ICCV4 profile indicates that this is the case. This then - solves - the problem of the gamut mapping having to know the source and - destination gamuts to operate. Instead, the gamut mapping is split - into - two parts, the first where the source gamut to RMG is done by the - AtoB - tables, and then the RMG to destination gamut is done by the BtoA - tables. Profiles can therefore be mix and matches, while retaining - true - gamut mapping.
+ of different profiles. A slight adjustment was made to the permitted + tag contents, to allow things like Display profiles to contain the + full range of AtoB and BtoA tables, so that they could also be gamut + mapped. An optional part of ICCV4, introduces a more comprehensively + specified Profile Reference Medium + Gamut (PRMG) as an intermediate gamut boundary between the + source colorspace, and the destination colorspace. If this option is + used, then an additional tag in the ICCV4 profile indicates that + this is the case. This then solves the problem of the gamut mapping + having to know the source and destination gamuts to operate. + Instead, the gamut mapping is split into two parts, the first where + the source gamut to RMG is done by the AtoB tables, and then the RMG + to destination gamut is done by the BtoA tables. Profiles can + therefore be mix and matches, while retaining true gamut mapping.

This approach has a number of drawbacks though. One is that the - colors - get gamut mapped twice. Gamut mapping is sometimes not very precise, - and the geometry of the transforms may not cancel out, especially - since - different profile vendors may choose different algorithms in their - gamut mapping. By "cancel out", I mean that even if you were linking - the same source colorspace to the same destination colorspace, the - gamut may be expanded (say) in the process of mapping to the PRMG, - and - then compressed again in mapping from the RMG to the device space, - and - these expansions and compressions may not quite match. Given that - the - PRMG is a relatively large gamut, larger than many real devices - actual + colors get gamut mapped twice. Gamut mapping is sometimes not very + precise, and the geometry of the transforms may not cancel out, + especially since different profile vendors may choose different + algorithms in their gamut mapping. By "cancel out", I mean that even + if you were linking the same source colorspace to the same + destination colorspace, the gamut may be expanded (say) in the + process of mapping to the PRMG, and then compressed again in mapping + from the RMG to the device space, and these expansions and + compressions may not quite match. Given that the PRMG is a + relatively large gamut, larger than many real devices actual behavior, this sort of expansion and re-compression will be the - normal - thing.
+ normal thing.

The chief drawback, is that only one (non colorimetric) intent can really be supported, that of saturation.

The typically expected behavior of perceptual intent gamut mapping, - is - to - compress any areas of the source gamut that lie outside the - destination - gamut, but for areas that fall within the destination gamut, change - them as little as possible, consistent with keeping smooth and - proportional with respect to the compressed colors. This preserves - the - source "look" as much as - possible, while ensuring that out of gamut colors are smoothly - brought - within the destination gamut.
+ is to compress any areas of the source gamut that lie outside the + destination gamut, but for areas that fall within the destination + gamut, change them as little as possible, consistent with keeping + smooth and proportional with respect to the compressed colors. This + preserves the source "look" as much as possible, while ensuring that + out of gamut colors are smoothly brought within the destination + gamut.

Typical behavior of a saturation intent, is (at least), to not only compress out of gamut source colors to fit within the destination, - but - to expand any source boundary that falls within the destination - gamut - outwards match the destination gamut. Some practical saturation - gamut - mappings may go further than this, and expand a little beyond the - destination gamut to ensure fully saturated boundary colors, and - also - enhance the saturation of all colors mapped through it.
-
- By mapping the source gamut to - the RMG in the A2B, all information about what areas of the source - gamut are - inside or outside of the destination gamut are lost, so the - destination - gamut mapping can not known which colors may be left unchanged, and - which really need compressing. All it can do is map the RMG to match - the destination gamut, - thereby effecting a saturation style intent.
-
- Once again, this is a fundamental limitation of using pre-computed - gamut mappings. The only effective way of overcoming such - limitations - is to move to a more active color management architecture, in which - gamut mappings are computed at link time, to accommodate the actual - source and destination gamuts.
+ but to expand any source boundary that falls within the destination + gamut outwards match the destination gamut. Some practical + saturation gamut mappings may go further than this, and expand a + little beyond the destination gamut to ensure fully saturated + boundary colors, and also enhance the saturation of all colors + mapped through it.
+
+ By mapping the source gamut to the RMG in the A2B, all + information about what areas of the source gamut are inside or + outside of the destination gamut are lost, so the destination gamut + mapping can not known which colors may be left unchanged, and which + really need compressing. All it can do is map the RMG to match the + destination gamut, thereby effecting a saturation style intent.
+
+ If the source was not expanded out to fill the RMG in some area by + the A2B, then the resulting output will be over compressed and end + up looking dull, because the B2A table has no choice but assume that + there may be colors that do fill the RMG.
+
+ Once again, this is all a fundamental limitation of using + pre-computed gamut mappings. The only effective way of overcoming + such limitations is to move to a more active color management + architecture, in which gamut mappings are computed at link time, to + accommodate the actual source and destination gamuts.

- - - illumread - - - - -
spectro/illumread
-
Summary
- 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 spotread should be used instead.)
-
Usage Summary
- illumread [-options] - illuminant.sp
- -v + + + illumread + + + + +
spectro/illumread
+
Summary
+ 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 spotread should be used instead.)
+
Usage Summary
+ illumread [-options] + illuminant.sp
+ -v              - Verbose mode
- -S -              - Plot the readings in a graph window.
- -c comport
+ -S +              + Plot the readings in a graph window.
+ -c comport            Set - COM port, 1..4 (default 1)
-
+ -N                    Disable - initial calibration of instrument if possible
- -H -              -       Use high resolution spectrum mode - (if available)
+ + + + initial calibration of instrument if possible
+ -H +              +       Use high resolution spectrum mode + (if available)
-Y r                  - Set refresh measurement mode
- -W n|h|x              Override - serial port flow control: n = none, h = HW, x = Xon/Xoff
- -T + + + + serial port flow control: n = none, h = HW, x = Xon/Xoff
+ -T                    - Test mode - restore & save measurements to
+ + + + Test mode - restore & save measurements to
                        - *_i.sp, *_r.sp, *_p.sp, *_mpir.sp, *_cpir.sp files
- -D [level] -            - Print debug diagnostics to stderr
- + -D [level] +            + Print debug diagnostics to stderr
+ illuminant.sp         File - to save measurement to
-
-
Usage Details and Discussion
- illumread 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 FWA compensation. 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.
-
- The -v flag causes extra information to be - printed out during chartread operation.
-
- The -S 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.
-
- The instrument is assumed to communicate through a - USB or serial communication port, and the initial port can be - selected with the -c option, if the instrument is not - connected to the first port. If you invoke illumread 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.
-
- -N Any - instrument that requires regular calibration will ask for - calibration on initial start-up. Sometimes this can be awkward if - the instrument is being mounted in some sort of measuring jig, or - annoying if several sets of readings are being taken in quick - succession. The -N - suppresses this initial calibration if a valid and not timed out - previous calibration is recorded in the instrument or on the host - computer. It is advisable to only use this option on the second and - subsequent measurements in a single session.
-
- The -H - option turns on high resolution spectral mode, if the instrument - supports it. See Operation of particular - instruments for more details.
-
- The -Y r - 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.
-
- The -W n|h|x - parameter overrides the default serial communications flow control - setting. The value n turns - all flow control off, h - sets hardware handshaking, and x - sets Xon/Xoff handshaking. This commend may be useful in workaround - serial communications issues with some systems and cables.
-
- The -T flag invokes the test mode. In test - mode the three measurements are saved to files illuminant_i.sp - (Illuminant spectrum), illuminant_r.sp (Illuminant - off paper spectrum), and illuminant_p.sp (Instrument - measured paper reflectance spectrum), and these will be loaded if - discovered, allowing a replay of the calculation without requiring - any measurement. In addition, two diagnostic files illuminant_mpir.sp + + + + to save measurement to
+
+
Usage Details and Discussion
+ illumread 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 FWA compensation. 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.
+
+ The -v flag causes extra information to be + printed out during chartread operation.
+
+ The -S 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.
+
+ The instrument is assumed to communicate through a + USB or serial communication port, and the initial port can be + selected with the -c option, if the instrument is not + connected to the first port. If you invoke illumread 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.
+
+ -N Any + instrument that requires regular calibration will ask for + calibration on initial start-up. Sometimes this can be awkward if + the instrument is being mounted in some sort of measuring jig, or + annoying if several sets of readings are being taken in quick + succession. The -N + suppresses this initial calibration if a valid and not timed out + previous calibration is recorded in the instrument or on the host + computer. It is advisable to only use this option on the second and + subsequent measurements in a single session.
+
+ The -H + option turns on high resolution spectral mode, if the instrument + supports it. See Operation of particular + instruments for more details.
+
+ The -Y r + 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.
+
+ The -W n|h|x + parameter overrides the default serial communications flow control + setting. The value n turns + all flow control off, h + sets hardware handshaking, and x + sets Xon/Xoff handshaking. This commend may be useful in workaround + serial communications issues with some systems and cables.
+
+ The -T flag invokes the test mode. In test + mode the three measurements are saved to files illuminant_i.sp + (Illuminant spectrum), illuminant_r.sp (Illuminant + off paper spectrum), and illuminant_p.sp (Instrument + measured paper reflectance spectrum), and these will be loaded if + discovered, allowing a replay of the calculation without requiring + any measurement. In addition, two diagnostic files illuminant_mpir.sp (Measured paper under illuminant spectrum) and illuminant_cpir.sp - (Computed paper under illuminant spectrum) will be saved.
-
- The -D 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.
-
- The illuminant.sp is the name of the file to save the - resulting illuminant spectrum to. The format used is .sp.
-
-

- Unlike the other measurement utilities, illumread 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.
-
- It will display a menu:
-
- Press 1 .. 6
- 1) Measure direct illuminant
- 2) Measure illuminant reflected from paper
- 3) Measure paper
- 4) Select another instrument, Currently 1 'usb:/bus4/dev2/ - (GretagMacbeth i1 Pro)'
- 5) Compute illuminant spectrum, average result with 0 previous - readings & save it
- 6) Compute illuminant spectrum from this reading & save result
- 7) Exit
-
- There are three measurements to be made, after which the illuminant - can be computed and saved. Before each measurement, the instrument - may need calibrating.
-
- 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.
-
- 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.
-
- 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.
-
- To be able to estimate the level of Ultra Violet (UV) light in the - illuminant, a reasonable sized piece of white paper needs to be - used. The paper should have some noticeable level of FWA - (Fluorescent Whitener Additive, or Optical Brightening Agents) in - it, so that it responds to UV light. A piece of cheap copier paper - is ideal, since cheap paper is typically whitened with large amounts - of FWA. If the paper is thin (less than 160 gsm) then two or three - sheets should be used to prevent any background showing through. If - the intention is to use the illuminant spectrum for proofing to a - particular paper, then it's best to use the intended paper for this - purpose.
-
- The first measurement 1), - is to use either the ambient or emissive measurement mode to measure - the illumination directly.
-
-
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 spotread -S to - check that the reflection characteristic is close to flat.]
-
-
-
-
- The second measurement 2), - is to measure the illuminant after it has reflected from the paper.
-
-
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.
-
-
-
-
- The third measurement 3), - is to measure the paper directly using the instrument reflective - mode measurement.
-

-
- If a different instrument is needed, use 4) to select from the available instruments attached - to your computer.
-
- Once these three measurements have been made, then the illuminant - readings spectrum can be computed and save using 6), or a series of readings can - be made with each reading being averages with the previous readings - before saving it by using 5). - 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.
-
- 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).
-
-
- Illumread can then be terminated using 7).
-
-
-
-
-
-
-
-
-
-
-
- - + + + + (Computed paper under illuminant spectrum) will be saved.
+
+ The -D 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.
+
+ The illuminant.sp is the name of the file to save the + resulting illuminant spectrum to. The format used is .sp.
+
+

+ Unlike the other measurement utilities, illumread 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.
+
+ It will display a menu:
+
+ Press 1 .. 6
+ 1) Measure direct illuminant
+ 2) Measure illuminant reflected from paper
+ 3) Measure paper
+ 4) Select another instrument, Currently 1 'usb:/bus4/dev2/ + (GretagMacbeth i1 Pro)'
+ 5) Compute illuminant spectrum, average result with 0 previous + readings & save it
+ 6) Compute illuminant spectrum from this reading & save result
+ 7) Exit
+
+ There are three measurements to be made, after which the illuminant + can be computed and saved. Before each measurement, the instrument + may need calibrating.
+
+ 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.
+
+ 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.
+
+ 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.
+
+ To be able to estimate the level of Ultra Violet (UV) light in the + illuminant, a reasonable sized piece of white paper needs to be + used. The paper should have some noticeable level of FWA + (Fluorescent Whitener Additive, or Optical Brightening Agents) in + it, so that it responds to UV light. A piece of cheap copier paper + is ideal, since cheap paper is typically whitened with large amounts + of FWA. If the paper is thin (less than 160 gsm) then two or three + sheets should be used to prevent any background showing through. If + the intention is to use the illuminant spectrum for proofing to a + particular paper, then it's best to use the intended paper for this + purpose.
+
+ The first measurement 1), + is to use either the ambient or emissive measurement mode to measure + the illumination directly.
+
+

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 spotread -S to + check that the reflection characteristic is close to flat.]
+
+ Measuring Ambient

+
+ The second measurement 2), + is to measure the illuminant after it has reflected from the paper.
+
+

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, and also avoiding measuring specular + reflection if the paper is glossy.
+
+ Measuring via
+ Paper

+
+ The third measurement 3), + is to measure the paper directly using the instrument reflective + mode measurement.
+

+ If a different instrument is needed, use 4) to select from the available instruments attached + to your computer.
+
+ Once these three measurements have been made, then the illuminant + readings spectrum can be computed and save using 6), or a series of readings can + be made with each reading being averages with the previous readings + before saving it by using 5). + 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.
+
+ 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).
+
+
+ Illumread can then be terminated using 7).
+
+
+
+
+
+
+
+
+
+
+
+ + diff --git a/doc/instruments.html b/doc/instruments.html index 1e287fc..d7f5d30 100644 --- a/doc/instruments.html +++ b/doc/instruments.html @@ -1,28 +1,28 @@ - - - - Operation of particular instruments - - - -

Operation of particular instruments

- Please note that instruments are - being driven by ArgyllCMS drivers, and that any problems or - queries regarding instrument
- operation should be - directed to the Argyll's author(s) or the Argyll mailing list, and - not to any other party.
-
- The following instruments are directly supported:
- (Please note the installation instructions for each - platform - they contain important information for getting your - instruments working.)
-
- JETI:
-
+ + + + Operation of particular instruments + + + +

Operation of particular instruments

+ Please note that instruments are + being driven by ArgyllCMS drivers, and that any problems or + queries regarding instrument
+ operation should be + directed to the Argyll's author(s) or the Argyll mailing list, and + not to any other party.
+
+ The following instruments are directly supported:
+ (Please note the installation instructions for each + platform - they contain important information for getting your + instruments working.)
+
+ JETI:
+
    specbos 1211 & 1201                    @@ -49,10 +49,27 @@ - - Tele-Spectro-Radiometer
-
- Image Engineering:
-
+ + + + + + + + + + + + - Tele-Spectro-Radiometer
+     spectraval 1511& 1501                + + + + +    - Tele-Spectro-Radiometer
+
+ Image Engineering:
+
    EX1                                               @@ -108,20 +125,6 @@ - - Tele-Spectro-Radiometer
-
- Klein:
-
-     K10-A   -             -             -             -     - Display Colorimeter. Reported also to work with - the K-1, K-8 and K-10
-
- X-Rite:
-     DTP20 "Pulse" -                             @@ -132,6 +135,390 @@ + + - Tele-Spectro-Radiometer
+
+ Klein:
+
+     K10-A   +             +             +             +     - Display Colorimeter. Reported also to work with + the K-1, K-8 and K-10
+
+ X-Rite:
+     DTP20 "Pulse" +                             + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - "swipe" type reflective spectrometer, that can be used untethered.
+     DTP22 Digital Swatchbook            + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - spot type reflective spectrometer.
+     DTP41                                         + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - spot and strip reading reflective spectrometer.
+     DTP41T +    +                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - spot and strip reading reflective/transmissive spectrometer.
+     DTP51                                         + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - strip reading reflective colorimeter.
+     DTP92                                         + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - CRT display colorimeter.
+     DTP94 "Optix + + + + + + + @@ -169,8 +556,6 @@ - - "swipe" type reflective spectrometer, that can be used untethered.
-     DTP22 Digital Swatchbook            @@ -184,6 +569,9 @@ + + XR" or "Optix XR2" or "Optix Pro"- display colorimeter.
+     @@ -218,8 +606,6 @@ - - spot type reflective spectrometer.
-     DTP41                                         @@ -243,6 +629,63 @@ + + ColorMunki + Design or Photo +          - spot and "swipe" + reflective/emissive spectrometer (UV cut only).
+     ColorMunki Create or Smile   +          - display + colorimeter. (Similar to an Eye-One Display 2)
+     Lenovo W + + - built in laptop + Huey display colorimeter.
+     Eye-One Display 3 + + - i1 DisplayPro and ColorMunki Display
+             +             +             +             +           [ The OEM + i1Display Pro, NEC SpectraSensor Pro,
+ + + +    Quato Silver Haze 3 OEM and HP + DreamColor i1d3 are also reported to work.]
+ Eye-One Pro2 + +      - spot and + "swipe" reflective/emissive spectrometer.
+
+ Gretag-Macbeth (now X-Rite):
+ Spectrolino + + - spot reflective/emissive + spectrometer
+ SpectroScan + + - spot reflective/emissive, XY table + reflective spectrometer
+ SpectroScanT + + - spot reflective/emissive/transmissive, XY + table reflective spectrometer
+ Eye-One Pro "EFI ES-1000" + - spot and "swipe" reflective/emissive + spectrometer
+ Eye-One Monitor + + - spot and "swipe" emissive spectrometer
+     Eye-One Display 1 or 2 or + LT        - display + colorimeter
+     HP DreamColor or + APS +                 @@ -267,10 +710,6 @@ - - spot and strip reading reflective spectrometer.
-     DTP41T -    -                      @@ -304,6 +743,10 @@ + + - display colorimeter. (Treated as a Eye-One Display 2)
+     CalMAN X2 +                                  @@ -318,8 +761,6 @@ - - spot and strip reading reflective/transmissive spectrometer.
-     DTP51                                         @@ -363,12 +804,23 @@ + + - display colorimeter. (Treated as a Eye-One Display 2)
+     Huey + + +        - display colorimeter
+
+ Sequel imaging (Now X-Rite):
+      MonacoOPTIX +    +        - display colorimeter (Treated + as an Eye-One Display 1)
+                                                            - - strip reading reflective colorimeter.
-     DTP92                                         @@ -416,14 +868,18 @@ - - CRT display colorimeter.
-     DTP94 "Optix + + [The Sequel Chroma 4 & 5, and Sencore ColorPro V, IV & III + also work.]
+
+ Lacie Blue + Eye:                                  @@ -465,8 +921,6 @@ - XR" or "Optix XR2" or "Optix Pro"- display colorimeter.
-     @@ -483,6 +937,16 @@ + + - see Eye-One Display
+
+ DataColor ColorVision:
+      Spyder 2 +    +    +        - display colorimeter (Note + that the user must supply firmware)
+                                                           @@ -514,62 +978,6 @@ - ColorMunki - Design or Photo -          - spot and "swipe" - reflective/emissive spectrometer (UV cut only).
-     ColorMunki Create or Smile   -          - display - colorimeter. (Similar to an Eye-One Display 2)
-     Lenovo W - - - built in laptop - Huey display colorimeter.
-     Eye-One Display 3 - - - i1 DisplayPro and ColorMunki Display
-             -             -             -             -           [ The OEM - i1Display Pro, NEC SpectraSensor Pro,
- - - -    Quato Silver Haze 3 OEM and HP - DreamColor i1d3 are also reported to work.]
- Eye-One Pro2 - -      - spot and - "swipe" reflective/emissive spectrometer.
-
- Gretag-Macbeth (now X-Rite):
- Spectrolino - - - spot reflective/emissive - spectrometer
- SpectroScan - - - spot reflective/emissive, XY table - reflective spectrometer
- SpectroScanT - - - spot reflective/emissive/transmissive, XY - table reflective spectrometer
- Eye-One Pro "EFI ES-1000" - - spot and "swipe" reflective/emissive - spectrometer
- Eye-One Monitor - - - spot and "swipe" emissive spectrometer
-     Eye-One Display 1 or 2 or - LT        - display - colorimeter
-     HP DreamColor or - APS -                 @@ -596,6 +1004,28 @@ + + [The Spyder 1 also seems to work.]
+      Spyder 3 +    +    +        - display colorimeter.
+      Spyder 4 +    +    +        - display colorimeter (Note + that the user must supply calibration + data)
+      Spyder 5 +    +    +        - display colorimeter (Note + that the user must supply calibration + data)
+
+ Other:
+     Colorim�tre + HCFR                        @@ -617,9 +1047,6 @@ - - display colorimeter. (Treated as a Eye-One Display 2)
-     CalMAN X2 -                                  @@ -656,6 +1083,10 @@ + + - display colorimeter
+     ColorHug & + ColorHug2               @@ -667,18 +1098,6 @@ - - display colorimeter. (Treated as a Eye-One Display 2)
-     Huey - - -        - display colorimeter
-
- Sequel imaging (Now X-Rite):
-      MonacoOPTIX -    -        - display colorimeter (Treated - as an Eye-One Display 1)
-                                                            @@ -716,6 +1135,288 @@ + + - display colorimeter
+     Palette/SwatchMate Cube +           - reflective + colorimeter
+
+ Other instruments can be supported indirectly, since patch result + files created by other packages can be imported into Argyll.
+
+ General information about:
+
+     Strip reading instruments
+     X-Y Table instruments
+     Spot reading instruments
+
+
+ There is a list of contributed ccmx (Colorimeter Correction + Matrix) files.
+
+

Strip reading instruments

+ When used with a DT20, DTP41, DTP51, Eye-One Pro or ColorMunki + 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:
+
+     About to read strip XX :
+
+ 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.
+
+ For the DTP51 you should + feed the strip into the instrument, and the microswitch will trigger + the read.
+
+ For the DTP41 you should + line the appropriate strip up in the machine, and press its button.
+
+ For the Eye-One Pro you + should set the guide to the appropriate strip, place the instrument + ahead 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.
+
+ For the ColorMunki 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 high density ColorMunki chart (printtarg -h), 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.
+
+ Using the DTP20 or the Eye-One Pro or ColorMunki with a randomized + chart layout, the strip may be scanned from either direction. If a + randomized chart layout has not been used for the Eye-One Pro or ColorMunki, then the chart + should only be read in the one direction (use chartread -B).
+
+ 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 installation.
+
+ If the strip is read successfully there will be a single "success" + beep, and the line will be followed with:
+
+     Ready to read strip XX :
+     Strip read OK
+
+ 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
+ failed strip:
+
+     Ready to read strip XX :
+     Strip read failed due to misread (Not enough + patches)
+
+     Hit Esc to give up, any other key to retry:
+
+ If you are unable to successfully read a strip after several + retries, you can skip that strip using the 'n' key, and save
+ the chart readings without that strip.
+
+ 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:
+
+     Ready to read strip XX :
+     (Warning) Seem to have read strip YY + rather than XX !
+     Hit Return to use it anyway, any other key to + retry, Esc, ^C or Q to give up:
+
+ 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.
+ 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).
+ Erroneous warnings are less likely if a previous profile for a + device was given to targen + to set more accurate expectations.
+
+ You may also see the following type of warning:
+
+     Ready to read strip XX :
+     (Warning) Patch error YY.YYY (>35 not good, + >95 bad)
+    There is at least one patch with an very unexpected + response!
+     Hit Return to use it anyway, any other key to + retry, Esc, ^C or Q to give up:
+
+ 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 targen + to set more accurate expectations.
+
+ You can also navigate the next strip to be read using the 'f' key to move forward and the + 'b' keys + 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 'n' 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 'd' 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 resume reading the chart by using the chartread -r flag. [You could + resume reading the chart patch by patch using the chartread -r -p if you are + unable to read a strip successfully.]
+
+ When reading in patch by patch mode, there are a few additional + navigation options, such as F to move forward 10 + patches, B to move + backwards 10 patches, and g + to go to a specific patch.
+
+ You can abort the whole process at any time by hitting Escape, and + the readings will not be saved.
+
+

X-Y Table instruments

+ When you are using an XY table type instrument, such as a Gretag SpectroScan, 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:
+
+     Please make sure that the white reference is in + slot 1, then
+     place sheet 1 of 4 on table, then
+     hit return to continue, Esc to give up
+
+ After hitting return you will be prompted to line up three squares + on the sheet, one at a time:
+
+     Using the XY table controls, locate patch A1 with + the sight,
+     then hit return to continue, Esc to give up
+
+ On completing this, the instrument will commence reading each sheet.
+
+

Spot reading instruments

+ When used with a DT22 or SpectroLino or use the patch by + patch reading mode (chartread -p) + with the Eye-One Pro or ColorMunki + instrument, or use the external values mode (chartread -x), 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:
+
+     Ready to read patch 'XX' :
+
+ where XX is the patch label, and this is followed by the available + options to navigate, read the strip, or finish.
+
+ 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).
+
+ There should be an audible prompt on a successful or failed reading. +
+
+ 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 installation.
+
+ If the patch is read successfully, the line will be completed with:
+
+     Ready to read patch XX :
+     Patch read OK
+
+ 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
+ failed patch:
+
+     Ready to read patch XX : read_strip + returned 'Strip misread' (Bad reading)
+
+     Strip read failed due to misread
+     Hit Esc to give up, any other key to retry:
+
+ You can navigate the next patch to be read using the 'f' key to move forward and the + 'b' keys + to move backwards, while 'F' + and 'B' 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 'n' + to move forward to the next unread patch. When you are finished, use + the 'd' 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 resume reading the + chart by using the chartread -r + flag.
+
+ You can abort the whole process at any time by hitting Escape, and + the readings will not be saved.
+
+ +

Display Type
+

+ Many of the colorimeters have a display @@ -726,10 +1427,6 @@ - [The Sequel Chroma 4 may also work.]
-
- Lacie Blue - Eye: @@ -772,20 +1469,196 @@ + + type 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.
+
+ 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 refresh are CRT + (Cathode Ray Tube), Single chip DLP (Digital Light Processing) and + Plasma displays. An example of a non-refresh + 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.
+
+ 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.
+
+ See Comparison_of_display_technology + for some background on different display technologies.
+
+

Refresh Rate Measurement

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 spotread using the 'F' key. + The particular instruments have a range of accuracy when making + this measurement. A rough guide is as follows:
+
+

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Instrument	Typical error in Hz.
spectrobos 1211/1201/1501/1511 +	0.05 +
Klein K10-A +	0.05 +
DTP92 +	0.1 +
i1 Display 2 +	0.5 +
Spyder 2 +	0.7 +
Spyder 3 +	3 +
Spyder 4 +	3 +
i1 Display Pro +	0.05 +
i1 Pro Spectro. +	0.05 +
ColorMunki Spectro. +	0.05 +

specbos 1211 and 1201 + Tele-Spectro-Radiometer
+

+ Availability:
+
+ The specbos 1211 and 1201 from JETI 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 & + characterization, lighting measurement and colorimeter + calibration, amongst many other uses.
+

The JETI specbos 1211 and 1201 makes use + of the FTDI FT232R Virtual COM Port Drivers (VCP), that may need + installing for your operating system. See installation + instructions.

+
+

spectraval 1511 and 1501 + Tele-Spectro-Radiometer
+

+ Availability:
+
+ The spectraval 1511 and 1501 from JETI are currently available + instruments. These are high grade instruments capable of emissive + measurements, and are often used for monitor, projector and cinema + calibration & characterization and colorimeter calibration, + amongst many other uses.
+
+ The JETI specbos 1511 and 1501 makes use of + the newer FTDI FT231XS Virtual COM Port Drivers (VCP), that may need + installing for your operating system. See installation + + instructions.
+
+ Bluetooth: These instruments can be operated via Bluetooth by + first pairing the instrument with your computer and enabling the + Bluetooth serial port, and then allowing the ArgyllCMS tools to + identify the instrument over the serial port.
+
+

+ Image + Engineering EX1
+

+
+ Availability:
+
+ The Image - - see Eye-One Display
-
- DataColor ColorVision:
- Spyder 2 - - - - display colorimeter (Note - that the user must supply firmware)
- @@ -797,6 +1670,22 @@ + + Engineering EX1 is a currently available instruments. This is + a high resolution spectrometer intended for the measurement of light + sources. +

Klein K10-A Colorimeter
+

+ Availability:
+
+ The Klein K10-A from @@ -820,6 +1709,8 @@ + + Klein Instruments @@ -833,27 +1724,6 @@ - [The Spyder 1 also seems to work.]
-      Spyder 3 -    -    -        - display colorimeter.
-      Spyder 4 -    -    -        - display colorimeter (Note - that the user must supply calibration - data)
-      Spyder 5 -    -    -        - display colorimeter (Note - that the user must supply calibration - data)
-
- Other:
-     Colorim�tre - HCFR                        @@ -864,6 +1734,308 @@ + + is a currently available instrument. It is noted for it's speed, + high precision, and ability to measure to very low light + levels.This is a high end instruments capable of contact and tele + - emissive, and ambient measurements, and are often used for + monitor, projector and cinema calibration and characterization.
+

Note that unlike the operation of other instruments, the Ambient + mode is purely manual - the diffuser must be fitted and then the + appropriate calibration setting chosen (Typically with "Lux" in + the name).
+

By default, more measurements are taken and averaged together + when the light level is low. This can be disabled and a single + measurement taken per reading, to gain maximum speed by using the + -Y A flag.
+

The K-1, K-8 and K-10 are also + reported to work.
+

The Klien K10A makes use of the FTDI FT232R Virtual + COM Port Drivers (VCP), that may need installing for your + operating system. See installation + instructions.

+
+ ColorMunki Design or Photo reflective/emissive spectrometer
+
+

+
+ Availability:
+
+ The ColorMunki Design or Photo from X-Rite 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 chart + illustrates the differences (Note that the ColorMunki Design comes + with Pantone libraries). 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 .
+
+ Limitations & Features:
+
+ 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 here for + a discussion about what FWA compensation is).
+
+ Like the Eye-One Pro, this instrument does support the high resolution spectral mode.
+
+ OS X and X-Rite drivers
+
+ Please note the installation instructions.
+
+ Tips & Tricks:
+
+ 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.
+
+ Patch recognition:
+
+ 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.
+
+ In chartread, the -T ratio 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 -T ratio argument can be used to + modify this criteria. To loosen the tolerance, use a number greater + than 1.0 (ie. 1.5, 2.0).
+
+ Note that printtarg provides the -h 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.]
+
+ Native Calibration Standard:
+
+ Reflection measurements are natively X-Rite XRGA.
+
+
+ +

+ DTP20 + "Pulse" reflective spectrometer
+
+

+
+ Availability:
+
+ The DTP20 from X-Rite was discontinued during + 2007, but may still be available from old stock or second hand.
+
+ Special features:
+
+ The DTP20 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 chartread, which will recognize + the chart, and download all the measurements.
+ 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 chartread too.
+
+ Un-tethered spot measurements can also be read in using spotread, 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.
+
+ Note 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: -v
+
+ Chart printing:
+
+ 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 printtarg -m + parameter, or find a printing path that preserves the test chart + size correctly.
+
+ Operation:
+
+ When reading in tethered (on-line) mode, that the instrument + takes several seconds to + download the measurements after each strip, and that the indicator + will be in "rainbow" mode while this occurs. Wait until the + indicator turns solid green again before starting to measure the + next strip.
+
+ To reset 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).
+
+ To calibrate 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.
+
+ If the chart is particularly small, + 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
+ 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.
+
+ The speed of scan can be + quite critical with this instrument. In particular, it doesn't work + very well if the scan is too slow. + You don't want to go too fast either, as this reduces the number of + samples per patch.
+
+ Native Calibration Standard:
+
+ Reflection measurements are natively historical X-Rite standard + (XRDI).
+
+
+ +

+ DTP22 + Digital Swatchbook reflective spectrometer
+
+

+
+ Availability:
+
+ The DTP22 from X-Rite is a discontinued + instrument. It may still be available second hand. It is + capable of reading colored patches one at a time.
+
+ Native Calibration Standard:
+
+ Reflection measurements are natively historical X-Rite standard + (XRDI).
+
+
+ +

+ DTP41 reflective, DTP41T + reflective/transmissive spectrometers
+
+

+
+ Availability:
+
+ The DTP41 and DTP41T from X-Rite is a discontinued + instrument. It may still be available second hand.
+
+ The series II instruments (DTP41B + and DTP41TB) offer both + serial and USB connection. Note that currently only serial operation + using Argyll is possible with these instruments.
+
+ Native Calibration Standard:
+
+ Reflection measurements are natively historical X-Rite standard + (XRDI).
+
+

+ DTP51 + reflective colorimeter
+
+

+
+ Availability:
+
+ The DTP51 from X-Rite is a discontinued + instrument. It may still be available second hand.
+
+ Operation:
+
+ The DTP51's switch is triggered by inserting a strip + into the slot.
+
+ Native Calibration Standard:
+
+ Reflection measurements are natively historical X-Rite standard + (XRDI).
+
+
+ +

+ DTP92 CRT display colorimeter
+
+

+
+ Availability:
+
+ The DTP92 from X-Rite is a discontinued + instrument. It may still be available second hand. It will + only read CRT technology displays.
+
+ Operation:
+
+ The Display Selections for this instrument are:
+
+ c @@ -901,8 +2073,6 @@ - - display colorimeter
- ColorHug @@ -923,6 +2093,34 @@ + + CRT display A Cathode Ray + Tube display, that is of the Refresh type [Default, CB2].
+
+

+ DTP94, "Optix XR" or "Optix XR2" or "Optix Pro" display colorimetrers
+
+

+
+ Availability:
+
+ The DTP94 from X-Rite 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.
+
+ Operation:
+
+ The Display Selections for this instrument are:
+
+     l     @@ -941,288 +2139,8 @@ - - display colorimeter
-     Palette/SwatchMate Cube         - - reflective colorimeter
-
- Other instruments can be supported indirectly, since patch result - files created by other packages can be imported into Argyll.
-
- General information about:
-
-     Strip reading instruments
-     X-Y Table instruments
-     Spot reading instruments
-
-
- There is a list of contributed ccmx (Colorimeter Correction - Matrix) files.
-
-

Strip reading instruments

- When used with a DT20, DTP41, DTP51, Eye-One Pro or ColorMunki - 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:
-
-     About to read strip XX :
-
- 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.
-
- For the DTP51 you should - feed the strip into the instrument, and the microswitch will trigger - the read.
-
- For the DTP41 you should - line the appropriate strip up in the machine, and press its button.
-
- For the Eye-One Pro you - should set the guide to the appropriate strip, place the instrument - ahead 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.
-
- For the ColorMunki 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 high density ColorMunki chart (printtarg -h), 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.
-
- Using the DTP20 or the Eye-One Pro or ColorMunki with a randomized - chart layout, the strip may be scanned from either direction. If a - randomized chart layout has not been used for the Eye-One Pro or ColorMunki, then the chart - should only be read in the one direction (use chartread -B).
-
- 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 installation.
-
- If the strip is read successfully there will be a single "success" - beep, and the line will be followed with:
-
-     Ready to read strip XX :
-     Strip read OK
-
- 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
- failed strip:
-
-     Ready to read strip XX :
-     Strip read failed due to misread (Not enough - patches)
-
-     Hit Esc to give up, any other key to retry:
-
- If you are unable to successfully read a strip after several - retries, you can skip that strip using the 'n' key, and save
- the chart readings without that strip.
-
- 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:
-
-     Ready to read strip XX :
-     (Warning) Seem to have read strip YY - rather than XX !
-     Hit Return to use it anyway, any other key to - retry, Esc, ^C or Q to give up:
-
- 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.
- 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).
- Erroneous warnings are less likely if a previous profile for a - device was given to targen - to set more accurate expectations.
-
- You may also see the following type of warning:
-
-     Ready to read strip XX :
-     (Warning) Patch error YY.YYY (>35 not good, - >95 bad)
-    There is at least one patch with an very unexpected - response!
-     Hit Return to use it anyway, any other key to - retry, Esc, ^C or Q to give up:
-
- 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 targen - to set more accurate expectations.
-
- You can also navigate the next strip to be read using the 'f' key to move forward and the - 'b' keys - 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 'n' 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 'd' 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 resume reading the chart by using the chartread -r flag. [You could - resume reading the chart patch by patch using the chartread -r -p if you are - unable to read a strip successfully.]
-
- When reading in patch by patch mode, there are a few additional - navigation options, such as F to move forward 10 - patches, B to move - backwards 10 patches, and g - to go to a specific patch.
-
- You can abort the whole process at any time by hitting Escape, and - the readings will not be saved.
-
-

X-Y Table instruments

- When you are using an XY table type instrument, such as a Gretag SpectroScan, 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:
-
-     Please make sure that the white reference is in - slot 1, then
-     place sheet 1 of 4 on table, then
-     hit return to continue, Esc to give up
-
- After hitting return you will be prompted to line up three squares - on the sheet, one at a time:
-
-     Using the XY table controls, locate patch A1 with - the sight,
-     then hit return to continue, Esc to give up
-
- On completing this, the instrument will commence reading each sheet.
-
-

Spot reading instruments

- When used with a DT22 or SpectroLino or use the patch by - patch reading mode (chartread -p) - with the Eye-One Pro or ColorMunki - instrument, or use the external values mode (chartread -x), 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:
-
-     Ready to read patch 'XX' :
-
- where XX is the patch label, and this is followed by the available - options to navigate, read the strip, or finish.
-
- 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).
-
- There should be an audible prompt on a successful or failed reading. -
-
- 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 installation.
-
- If the patch is read successfully, the line will be completed with:
-
-     Ready to read patch XX :
-     Patch read OK
-
- 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
- failed patch:
-
-     Ready to read patch XX : read_strip - returned 'Strip misread' (Bad reading)
-
-     Strip read failed due to misread
-     Hit Esc to give up, any other key to retry:
-
- You can navigate the next patch to be read using the 'f' key to move forward and the - 'b' keys - to move backwards, while 'F' - and 'B' 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 'n' - to move forward to the next unread patch. When you are finished, use - the 'd' 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 resume reading the - chart by using the chartread -r - flag.
-
- You can abort the whole process at any time by hitting Escape, and - the readings will not be saved.
-
- -

Display Type
-

- Many of the colorimeters have a display @@ -1255,6 +2173,10 @@ + + LCD display A Liquid + Crystal Display, that is of the Non-Refresh type [default, CB1].
+ c @@ -1265,174 +2187,12 @@ - type 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.
-
- 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 refresh are CRT - (Cathode Ray Tube), Single chip DLP (Digital Light Processing) and - Plasma displays. An example of a non-refresh - 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.
-
- 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.
-
- See Comparison_of_display_technology - for some background on different display technologies.
-
-

Refresh Rate Measurement

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 spotread using the 'F' key. - The particular instruments have a range of accuracy when making - this measurement. A rough guide is as follows:
-
-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Instrument	Typical error in Hz.
spectrobos 1211/1201 -	0.05 -
Klein K10-A -	0.05 -
DTP92 -	0.1 -
i1 Display 2 -	0.5 -
Spyder 2 -	0.7 -
Spyder 3 -	3 -
Spyder 4 -	3 -
i1 Display Pro -	0.05 -
i1 Pro Spectro. -	0.05 -
ColorMunki Spectro. -	0.05 -

specbos 1211 and 1201 - Tele-Spectro-Radiometer
-

- Availability:
-
- The specbos 1211 and 1201 from JETI 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 & - characterization, lighting measurement and colorimeter - calibration, amongst many other uses.
-

Image Engineering EX1
-

-
- Availability:
-
- The Image - Engineering EX1 is a currently available instruments. This is - a high resolution spectrometer intended for the measurement of light - sources. -

Klein K10-A Colorimeter
-

- Availability:
-
- The Klein K10-A from @@ -1446,7 +2206,6 @@ href="http://www.image-engineering.de/iq-products/iq-tools/measurement-devices/e - Klein Instruments @@ -1460,277 +2219,6 @@ href="http://www.image-engineering.de/iq-products/iq-tools/measurement-devices/e - is a currently available instrument. It is noted for it's speed, - high precision, and ability to measure to very low light - levels.This is a high end instruments capable of contact and tele - - emissive, and ambient measurements, and are often used for - monitor, projector and cinema calibration and characterization.
-

Note that unlike the operation of other instruments, the Ambient - mode is purely manual - the diffuser must be fitted and then the - appropriate calibration setting chosen (Typically with "Lux" in - the name).
-

By default, more measurements are taken and averaged together - when the light level is low. This can be disabled and a single - measurement taken per reading, to gain maximum speed by using the - -Y A flag.
-

The K-1, K-8 and K-10 are also - reported to work.

-
- ColorMunki Design or Photo reflective/emissive spectrometer
-
-

-
- Availability:
-
- The ColorMunki Design or Photo from X-Rite 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 chart - 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 .
-
- Limitations & Features:
-
- 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 here for - a discussion about what FWA compensation is).
-
- Like the Eye-One Pro, this instrument does support the high resolution spectral mode.
-
- OS X and X-Rite drivers
-
- Please note the installation instructions.
-
- Tips & Tricks:
-
- 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.
-
- Patch recognition:
-
- 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.
-
- In chartread, the -T ratio 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 -T ratio argument can be used to - modify this criteria. To loosen the tolerance, use a number greater - than 1.0 (ie. 1.5, 2.0).
-
- Note that printtarg provides the -h 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.]
-
-
-
- -

- DTP20 - "Pulse" reflective spectrometer
-
-

-
- Availability:
-
- The DTP20 from X-Rite was discontinued during - 2007, but may still be available from old stock or second hand.
-
- Special features:
-
- The DTP20 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 chartread, which will recognize - the chart, and download all the measurements.
- 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 chartread too.
-
- Un-tethered spot measurements can also be read in using spotread, 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.
-
- Note 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: -v
-
- Chart printing:
-
- 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 printtarg -m - parameter, or find a printing path that preserves the test chart - size correctly.
-
- Operation:
-
- When reading in tethered (on-line) mode, that the instrument - takes several seconds to - download the measurements after each strip, and that the indicator - will be in "rainbow" mode while this occurs. Wait until the - indicator turns solid green again before starting to measure the - next strip.
-
- To reset 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).
-
- To calibrate 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.
-
- If the chart is particularly small, - 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
- 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.
-
- The speed of scan can be - quite critical with this instrument. In particular, it doesn't work - very well if the scan is too slow. - You don't want to go too fast either, as this reduces the number of - samples per patch.
-
-
- -

- DTP22 - Digital Swatchbook reflective spectrometer
-
-

-
- Availability:
-
- The DTP22 from X-Rite is a discontinued - instrument. It may still be available second hand. It is - capable of reading colored patches one at a time.
-
-
- -

- DTP41 reflective, DTP41T - reflective/transmissive spectrometers
-
-

-
- Availability:
-
- The DTP41 and DTP41T from X-Rite is a discontinued - instrument. It may still be available second hand.
-
- The series II instruments (DTP41B - and DTP41TB) offer both - serial and USB connection. Note that currently only serial operation - using Argyll is possible with these instruments.
-
-

- DTP51 - reflective colorimeter
-
-

-
- Availability:
-
- The DTP51 from X-Rite is a discontinued - instrument. It may still be available second hand.
-
- Operation:
-
- The DTP51's switch is triggered by inserting a strip - into the slot.
-
-
- -

- DTP92 CRT display colorimeter
-
-

-
- Availability:
-
- The DTP92 from X-Rite is a discontinued - instrument. It may still be available second hand. It will - only read CRT technology displays.
-
- Operation:
-
- The Display Selections for this instrument are:
-
-     c    @@ -1746,6 +2234,26 @@ href="http://www.image-engineering.de/iq-products/iq-tools/measurement-devices/e + + CRT display         A Cathode Ray + Tube display, that is of the Refresh type [CB2].
+     g    + Generic    +            Generic + display [CB3]
+
+
+ +

+ Spectrolino reflective/emissive spectrometer
+
+

+
+ Availability:
+
+ The Spectrolino from +Gretag @@ -1778,33 +2286,6 @@ href="http://www.image-engineering.de/iq-products/iq-tools/measurement-devices/e - CRT display A Cathode Ray - Tube display, that is of the Refresh type [Default, CB2].
-
-

- DTP94, "Optix XR" or "Optix XR2" or "Optix Pro" display colorimetrers
-
-

-
- Availability:
-
- The DTP94 from X-Rite 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.
-
- Operation:
-
- The Display Selections for this instrument are:
-
- l @@ -1830,7 +2311,263 @@ href="http://www.image-engineering.de/iq-products/iq-tools/measurement-devices/e + + 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.
+
+ Native Calibration Standard:
+
+ Reflection measurements are natively historical Gretag MacBeth + standard (GMDI).
+
+ +

+ SpectroScan reflective/emissive and SpectroScanT + reflective/emissive/transmissive spectrometers
+
+

+
+ Availability:
+
+ The SpectroScan and + SpectroScanT from Gretag + MacBeth (Now X-Rite) is a discontinued instrument. It is the + combination of an X-Y table and the Spectrolino instrument. The SpectroScanT 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.
+
+ If measuring transparencies using a SpectroScanT, the Enter + key on the instrument may be used to trigger each reading. It will + be recognized after each previous reading has been completed.
+
+ Native Calibration Standard:
+
+ Reflection measurements are natively historical Gretag MacBeth + standard (GMDI).
+
+

+
+ Eye-One Pro2:
+ Eye-One Pro 2

+
+ Availability:
+
+ The Eye-One Pro2 (AKA + + Eye-One Pro Rev E) from X-Rite is a currently available + instrument. It is available in several 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 chart + 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 i1 + + + Basic Pro 2.
+
+ 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 Eye-One Pro reflective/emissive + spectrometer below + for details on the operation of this type of instrument.
+
+ Native Calibration Standard:
+
+ Reflection measurements are natively X-Rite XRGA.
+
+

+ Eye-One Pro and + Eye-One Pro2 reflective/emissive spectrometer
+
+

+
+ Availability:
+
+ The Eye-One Pro from + X-Rite (was Gretag MacBeth) is a + discontinued instrument.
+
+ The EFI ES-1000 (which is a re-badged Eye-One Pro) is also reported + to work with Argyll.
+
+ 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 here 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.
+
+ There have been four revisions of the Eye-One Pro, Rev. A, B, D and + E (AKA Eye-One Pro2 - see above). 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.
+
+ NOTE 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.
+
+ See also How can I have confidence in + the i1pro Driver ?
+
+ Patch recognition:
+
+ 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.
+
+ In chartread, the -T ratio 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 -T ratio argument can be used to + modify this criteria. To loosen the tolerance, use a number greater + than 1.0 (ie. 1.5, 2.0).
+
+ Native Calibration Standard:
+
+ Reflection measurements are natively historical Gretag MacBeth + standard (GMDI) for RevA-D,
+ and natively X-Rite XRGA + for Rev E.
+
+ Special features:
+
+ 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 -H + flag on the command line to dispcal, + dispread, chartread, and spotread. It can also be toggled + on and off within spotread + using the h key.
+
+ 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.
+
+ See Does the i1pro High Resolution mode + improve accuracy ?
+
+ High res. and standard res. spectrum.

+
+

C.R.T high res. and standard res. spectrum.

+
+

+ Eye-One Monitor + emissive spectrometer
+
+

+
+ Availability:
+
+ The Eye-One Monitor + from X-Rite (was Gretag + MacBeth) is a discontinued instrument. It was a lower cost version + of the Eye-One Pro without + reflective measurement capability. See Eye-One Pro + reflective/emissive spectrometer for details on the operation of this instrument.
+
+
+

+ Eye-One Display + 1, Eye-One Display 2, Eye-One Display LT, ColorMunki Create, + ColorMunki Smile colorimeters,
+
+

+
+ Instrument Availability:
+
+ The ColorMunki Smile + colorimeter is a currently available instrument.
+ The Eye-One Display LT and + Eye-One Display 2 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.
+ The ColorMunki Create + 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.
+ The HP DreamColor + colorimeter can also be used, and will appear as an i1Display2 + colorimeter [note that it is calibrated for the DreamColor display].
+ The HP APS (Advanced + Profiling Solution) colorimeter is also reported to work, and will + appear as an i1Display2.
+ The CalMAN X2 colorimeter + is also reported to work, and will appear as an i1Display2 + colorimeter.
+ The Lacie Blue Eye colorimeter is also reported to + work, and will appear as an i1Display2 colorimeter.
+
+ The Eye-One Display 1 is a + discontinued instrument.
+
+ The Eye-One Display LT came with a less expensive package with more + limited software from the manufacture.
+ The Eye-One Display 2 package came with more software + features, but the instruments are virtually identical, and + will operate identically using Argyll.
+ The ColorMunki Create + package is another alternative, and will operate identically using + Argyll.
+
+ Operation:
+
+ The Display Selections for the ColorMunki @@ -1847,9 +2584,6 @@ href="http://www.image-engineering.de/iq-products/iq-tools/measurement-devices/e - LCD display         A Liquid - Crystal Display, that is of the Non-Refresh type [default, CB1].
-     c    @@ -1876,6 +2610,14 @@ href="http://www.image-engineering.de/iq-products/iq-tools/measurement-devices/e + + Smile are:
+
+     f +    LCD with CCFL back-light    +      A Liquid Crystal display that uses a Cold + Cathode Fluorescent back lighting. [Default, CB1]
+     e    @@ -1897,25 +2639,6 @@ href="http://www.image-engineering.de/iq-products/iq-tools/measurement-devices/e - CRT display         A Cathode Ray - Tube display, that is of the Refresh type [CB2].
-     g    - Generic    -            Generic - display [CB3]
-
-
- -

- Spectrolino reflective/emissive spectrometer
-
-

-
- Availability:
-
- The Spectrolino from -Gretag @@ -1935,6 +2658,14 @@ Gretag + + LCD with LED back-light + A Liquid Crystal display that uses + Light Emitting Diode back lighting.
+
+ other instruments will offer:
+
+ l @@ -1963,226 +2694,6 @@ 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.
-
- -

- SpectroScan reflective/emissive and SpectroScanT - reflective/emissive/transmissive spectrometers
-
-

-
- Availability:
-
- The SpectroScan and - SpectroScanT from Gretag - MacBeth (Now X-Rite) is a discontinued instrument. It is the - combination of an X-Y table and the Spectrolino instrument. The SpectroScanT 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.
-
- If measuring transparencies using a SpectroScanT, the Enter - key on the instrument may be used to trigger each reading. It will - be recognized after each previous reading has been completed.
-
-

-
- Eye-One Pro2:
- Eye-One Pro 2

-
- 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 Eye-One Pro reflective/emissive - spectrometer below - for details on the operation of this type of instrument.
-
-

- Eye-One Pro and - Eye-One Pro2 reflective/emissive spectrometer
-
-

-
- Availability:
-
- The Eye-One Pro from - X-Rite (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 chart - 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 i1 Basic - Pro.
-
- The EFI ES-1000 (which is a re-badged Eye-One Pro) is also reported - to work with Argyll.
-
- 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 here 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.
-
- 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.
-
- NOTE 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.
-
- See also How can I have confidence in - the i1pro Driver ?
-
- Patch recognition:
-
- 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.
-
- In chartread, the -T ratio 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 -T ratio argument can be used to - modify this criteria. To loosen the tolerance, use a number greater - than 1.0 (ie. 1.5, 2.0).
-
- Special features:
-
- 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 -H - flag on the command line to dispcal, - dispread, chartread, and spotread. It can also be toggled - on and off within spotread - using the h key.
-
- 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.
-
- See Does the i1pro High Resolution mode - improve accuracy ?
-
- High res. and standard res. spectrum.

-
-

- Eye-One Monitor - emissive spectrometer
-
-

-
- Availability:
-
- The Eye-One Monitor - from X-Rite (was Gretag - MacBeth) is a discontinued instrument. It was a lower cost version - of the Eye-One Pro without - reflective measurement capability. See Eye-One Pro - reflective/emissive spectrometer for details on the operation of this instrument.
-
-
-

- Eye-One Display - 1, Eye-One Display 2, Eye-One Display LT, ColorMunki Create, - ColorMunki Smile colorimeters,
-
-

-
- Instrument Availability:
-
- The ColorMunki Smile - colorimeter is a currently available instrument.
- The Eye-One Display LT and - Eye-One Display 2 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.
- The ColorMunki Create - 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.
- The HP DreamColor - colorimeter can also be used, and will appear as an i1Display2 - colorimeter [note that it is calibrated for the DreamColor display].
- The HP APS (Advanced - Profiling Solution) colorimeter is also reported to work, and will - appear as an i1Display2.
- The CalMAN X2 colorimeter - is also reported to work, and will appear as an i1Display2 - colorimeter.
- The Lacie Blue Eye colorimeter is also reported to - work, and will appear as an i1Display2 colorimeter.
-
- The Eye-One Display 1 is a - discontinued instrument.
-
- The Eye-One Display LT came with a less expensive package with more - limited software from the manufacture.
- The Eye-One Display 2 package came with more software - features, but the instruments are virtually identical, and - will operate identically using Argyll.
- The ColorMunki Create - package is another alternative, and will operate identically using - Argyll.
-
- Operation:
-
- The Display Selections for the ColorMunki @@ -2212,16 +2723,13 @@ Gretag + + LCD display         A Liquid + Crystal Display, that is of the Non-Refresh type. [Default, CB1]
+     c    - Smile are:
-
-     f -    LCD with CCFL back-light    -      A Liquid Crystal display that uses a Cold - Cathode Fluorescent back lighting. [Default, CB1]
-     e    @@ -2252,13 +2760,6 @@ Gretag - LCD with LED back-light    -       A Liquid Crystal display that uses - Light Emitting Diode back lighting.
-
- other instruments will offer:
-
-     l     @@ -2283,6 +2784,59 @@ Gretag + + CRT display          A + Cathode Ray Tube display, that is of the Refresh type. [CB2]
+
+
+

+ i1 DisplayPro and ColorMunki Display colorimeters (i1 Display 3)
+
+ i1 Display Pro

+
+ Instrument Availability:
+
+ Both instruments are currently available.
+
+ The ColorMunki Display is a less expensive package + with more limited software from the manufacture, and has hardware + that 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. Because of the measurement speed limitation, the + measurement of display refresh rate and synchronization of its + measurements to a refresh display is not possible with the + ColorMunki Display.
+
+ The i1Display Pro package + 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 unable to measure the + refresh period, so is less repeatable in this mode than the + i1Display Pro).
+
+ Both instruments are capable of using CCSS (Colorimeter Calibration Spectral + Sample) files, and this also gives the instrument the + capability of using a non-default standard observer. CCSS files can + be created using the ccxxmake tool, and + installed or translated from the .EDR files that are provided with + the instrument CD using the oeminst + utility using a spectrometer as a reference.
+
+ There are some OEM versions of this instrument around too, and the SpectraCal OEM i1Display, ChromaPure, NEC + SpectraSensor Pro and HP @@ -2306,9 +2860,6 @@ Gretag - LCD display         A Liquid - Crystal Display, that is of the Non-Refresh type. [Default, CB1]
-     c    @@ -2316,6 +2867,77 @@ Gretag + + DreamColor instruments are also reported to work. They will + appear as a be a the same as the i1Display Pro.
+ [Note 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 oeminst.]
+
+ 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.
+
+ Operation:
+
+ The Display Selections for this instrument are:
+
+     n     A + non-refresh type display [Default, CB1].
+     r +     A refresh type display - The refresh period + is measured, and the integration time adjusted appropriately. [CB2]
+
+ With the manufacturers .edr files & reference Argyll .ccss files + installed, the following selections are:
+
+     n      A + non-refresh type display [Default, CB1].
+     r +      A refresh type display - The refresh + period is measured, and the integration time adjusted appropriately. + [CB2]
+     c      CRT + (Hitachi CM2112MET, Diamond View 1772ie)
+     l       LCD CCFL + IPS (CCFL AC EIZO HP with CORRECTION)
+     L      LCD CCFL + Wide Gamut IPS (WG CCFL NEC241 271)
+     b      LCD RGB + LED IPS (RGBLED HP SOYO)
+     e      LCD White + LED IPS (WLED AC LG Samsung)
+     p      Projector + (Marantz HP Panasonic Projectors Hybrid EDR)
+
+ By default the integration time is adaptive, taking longer when the + light level is low. This can be disabled and a fixed integration + time used to gain maximum speed at the cost of greatly reduced low + light accuracy, by using the -Y A flag.
+
+ Note when measuring CRT displays:
+
+ 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.
+
+

+ Huey colorimeter
+
+

+
+ Availability:
+
+ The Huey and Huey @@ -2326,6 +2948,15 @@ Gretag + + Pro are discontinued instruments. They may still be available + as old stock, or second hand.
+
+ Operation:
+
+ The Display Selections for this instrument are:
+
+ l @@ -2356,55 +2987,6 @@ Gretag - CRT display A - Cathode Ray Tube display, that is of the Refresh type. [CB2]
-
-
-

- i1 DisplayPro and ColorMunki Display colorimeters (i1 Display 3)
-
- i1 Display Pro

-
- Instrument Availability:
-
- Both instruments are currently available..
-
- The ColorMunki Display is a less expensive package - 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.
-
- The i1Display Pro package - 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 unable to measure the - refresh period, so is less repeatable in this mode than the - i1Display Pro).
-
- Both instruments are capable of using CCSS (Colorimeter Calibration Spectral - Sample) files, and this also gives the instrument the - capability of using a non-default standard observer. CCSS files can - be created using the ccxxmake tool, and - installed or translated from the .EDR files that are provided with - the instrument CD using the oeminst - utility using a spectrometer as a reference.
-
- There are some OEM versions of this instrument around too, and the SpectraCal OEM i1Display, ChromaPure, NEC - SpectraSensor Pro and HP @@ -2425,84 +3007,6 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - DreamColor instruments are also reported to work. They will - appear as a be a the same as the i1Display Pro.
- [Note 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 oeminst.]
-
- 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.
-
- Operation:
-
- The Display Selections for this instrument are:
-
-     n     A - non-refresh type display [Default, CB1].
-     r -     A refresh type display - The refresh period - is measured, and the integration time adjusted appropriately. [CB2]
-
- With the manufacturers .edr files & reference Argyll .ccss files - installed, the following selections are:
-
-     n      A - non-refresh type display [Default, CB1].
-     r -      A refresh type display - The refresh - period is measured, and the integration time adjusted appropriately. - [CB2]
-     c      CRT - (Hitachi CM2112MET, Diamond View 1772ie)
-     l       LCD CCFL - IPS (CCFL AC EIZO HP with CORRECTION)
-     L      LCD CCFL - Wide Gamut IPS (WG CCFL NEC241 271)
-     b      LCD RGB - LED IPS (RGBLED HP SOYO)
-     e      LCD White - LED IPS (WLED AC LG Samsung)
-     p      Projector - (Marantz HP Panasonic Projectors Hybrid EDR)
-
- By default the integration time is adaptive, taking longer when the - light level is low. This can be disabled and a fixed integration - time used to gain maximum speed at the cost of greatly reduced low - light accuracy, by using the -Y A flag.
-
- Note when measuring CRT displays:
-
- 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.
-
-

- Huey colorimeter
-
-

-
- Availability:
-
- The Huey and Huey - Pro are discontinued instruments. They may still be available - as old stock, or second hand.
-
- Operation:
-
- The Display Selections for this instrument are:
-
-     l     @@ -2510,6 +3014,10 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP + + LCD display         A Liquid + Crystal Display, that is of the Non-Refresh type. [Default, CB1]
+     c    @@ -2550,9 +3058,6 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - LCD display         A Liquid - Crystal Display, that is of the Non-Refresh type. [Default, CB1]
-     c    @@ -2570,6 +3075,35 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP + + CRT display         A Cathode Ray + Tube display, that is of the Refresh type. [CB2]
+
+
+

+ MonacoOPTIX + colorimeters
+
+

+
+ Instrument Availability:
+
+ Availability:
+
+ The MonacoOPTIX 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.
+
+ Operation:
+
+ The Display Selections for this instrument are:
+
+ c @@ -2600,34 +3134,6 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - CRT display A Cathode Ray - Tube display, that is of the Refresh type. [CB2]
-
-
-

- MonacoOPTIX - colorimeters
-
-

-
- Instrument Availability:
-
- Availability:
-
- The MonacoOPTIX 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.
-
- Operation:
-
- The Display Selections for this instrument are:
-
-     c    @@ -2655,6 +3161,10 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP + + CRT display         A Cathode Ray + Tube display, that is of the Refresh type.
+     l     @@ -2675,9 +3185,6 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - CRT display         A Cathode Ray - Tube display, that is of the Refresh type.
-     l     @@ -2715,6 +3222,44 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP + + LCD display         A Liquid + Crystal Display or alternate Calibration, that is of the Non-Refresh + type.
+
+

+ Spyder 2 + colorimeter
+
+

+
+ Availability:
+
+ The Spyder 2 has been superseded by the + Spyder 5, but may be available second hand.
+ [The Spyder 1 has also been reported as working, but this has not + been confirmed.]
+
+ Operation:
+
+ Important Note about the + ColorVision Spyder 2 instrument support:
+
+ This instrument cannot function without the driver software having + access to the vendor supplied PLD firmware pattern for it.
+ This firmware is not provided with Argyll, since it is not available + under a compatible license.
+
+ 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 + oeminst tool.
+
+ The Display Selections for this instrument are:
+
+ l @@ -2725,42 +3270,6 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - LCD display A Liquid - Crystal Display, that is of the Non-Refresh type.
-
-

- Spyder 2 - colorimeter
-
-

-
- Availability:
-
- The Spyder 2 has been superseded by the - Spyder 5, but may be available second hand.
- [The Spyder 1 has also been reported as working, but this has not - been confirmed.]
-
- Operation:
-
- Important Note about the - ColorVision Spyder 2 instrument support:
-
- This instrument cannot function without the driver software having - access to the vendor supplied PLD firmware pattern for it.
- This firmware is not provided with Argyll, since it is not available - under a compatible license.
-
- 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 - oeminst tool.
-
- The Display Selections for this instrument are:
-
-     l     @@ -2808,8 +3317,9 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - LCD display        A Liquid Crystal - Display, that is of the Non-Refresh type. [Default, CB1]
+ + LCD display        A Liquid Crystal + Display, that is of the Non-Refresh type. [Default, CB1]
    c    @@ -2858,133 +3368,144 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - CRT display         A Cathode Ray - Tube display, that is of the Refresh type. [CB2]
-
-
- Linux USB hub problems:
-
- 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".
-
-

- Spyder 3 - colorimeter
-
- Spyder3

-
- Availability:
-
- The Spyder3Elite, Spyder3Pro and Spyder3Express have being - superseded by the Spyder 5, but may still stocked by some dealers, - and may be available second hand. The Spyder3Elite and Spyder3Pro - appear to be identical hardware with different software from the - manufacturer. The Spyder3Express - lacks the ambient sensor.
-
- [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.]
-
- Operation:
-
- The ambient light sensor can be used with the Spyder3Elite and Spyder3Pro instruments, but is - only capable of monochrome readings.
-
- The Display Selections for this instrument are:
-
- n | l A - non-refresh type display [Default, CB1]
- r | c - A refresh type display. [CB2]
-
-
-

- Spyder 4 - colorimeter
-
- Spyder4

-
- Availability:
-
- The Spyder4Elite, Spyder4Pro and Spyder4Express have being - superseded by the Spyder 5, but may still stocked by some dealers, - and may be available second hand. The Spyder4Elite and Spyder4Pro appear to be - identical hardware with different software from the manufacturer. - The Spyder4Express lacks - the ambient sensor.
-
- Operation:
-
- These instruments are capable of using using CCSS (Colorimeter Calibration Spectral - Sample) files, and this also gives the instrument the - capability of using a non-default standard observer. CCSS files can - be created using the ccxxmake tool - using a spectrometer as a reference.
-
- Important Note about the - DataColor Spyder 4 vendor display type/calibration support:
-
- This instrument does not have a full range of display type - calibration selections available without the vendor supplied - calibration data for it.
- This calibration data is not provided with Argyll, since it is not - available under a compatible license.
- 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 oeminst - tool.
-
- The Display Selections for this instrument are:
-
-     n | l   -    A non-refresh type display with a generic calibration - [Default, CB1].
-     r | c    A - refresh type display with a generic calibration.[CB2]
-
- The Display Selections for this instrument when the manufacturers - calibration information has been installed is:
-
-     n      -      A non-refresh type display with a generic - calibration [Default, CB1].
-     r    -      A refresh type display with a generic - calibration.[CB2]
-     f    -          LCD, CCFL + + + + + + + + + + + + CRT display         A Cathode Ray + Tube display, that is of the Refresh type. [CB2]
+
+
+ Linux USB hub problems:
+
+ 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".
+
+

+ Spyder 3 + colorimeter
+
+ Spyder3

+
+ Availability:
+
+ The Spyder3Elite, Spyder3Pro and Spyder3Express have being + superseded by the Spyder 5, but may still stocked by some dealers, + and may be available second hand. The Spyder3Elite and Spyder3Pro + appear to be identical hardware with different software from the + manufacturer. The Spyder3Express + lacks the ambient sensor.
+
+ [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.]
+
+ Operation:
+
+ The ambient light sensor can be used with the Spyder3Elite and Spyder3Pro instruments, but is + only capable of monochrome readings.
+
+ The Display Selections for this instrument are:
+
+ n | l A + non-refresh type display [Default, CB1]
+ r | c + A refresh type display. [CB2]
+
+
+

+ Spyder 4 + colorimeter
+
+ Spyder4

+
+ Availability:
+
+ The Spyder4Elite, Spyder4Pro and Spyder4Express have being + superseded by the Spyder 5, but may still stocked by some dealers, + and may be available second hand. The Spyder4Elite and Spyder4Pro appear to be + identical hardware with different software from the manufacturer. + The Spyder4Express lacks + the ambient sensor.
+
+ Operation:
+
+ These instruments are capable of using using CCSS (Colorimeter Calibration Spectral + Sample) files, and this also gives the instrument the + capability of using a non-default standard observer. CCSS files can + be created using the ccxxmake tool + using a spectrometer as a reference.
+
+ Important Note about the + DataColor Spyder 4 vendor display type/calibration support:
+
+ This instrument does not have a full range of display type + calibration selections available without the vendor supplied + calibration data for it.
+ This calibration data is not provided with Argyll, since it is not + available under a compatible license.
+ 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 oeminst + tool.
+
+ The Display Selections for this instrument are:
+
+     n | l   +    A non-refresh type display with a generic calibration + [Default, CB1].
+     r | c    A + refresh type display with a generic calibration.[CB2]
+
+ The Display Selections for this instrument when the manufacturers + calibration information has been installed is:
+
+     n      +      A non-refresh type display with a generic + calibration [Default, CB1].
+     r    +      A refresh type display with a generic + calibration.[CB2]
+     f    +          LCD, CCFL Backlight                         @@ -3033,17 +3554,28 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - - normal gamut Liquid Crystal Display with standard Cold Cathode - Fluorescent Lamp backlight.
-     L -         Wide Gamut LCD, CCFL - Backlight      - wide gamut Liquid Crystal - Display with Cold Cathode Fluorescent Lamps backlight.
-     e -             LCD, White - LED Backlight        -           - normal - gamut Liquid Crystal Display with a White LED backlight.
+ + + + + + + + + + + + - normal gamut Liquid Crystal Display with standard Cold Cathode + Fluorescent Lamp backlight.
+     L +         Wide Gamut LCD, CCFL + Backlight      - wide gamut Liquid Crystal + Display with Cold Cathode Fluorescent Lamps backlight.
+     e +             LCD, White + LED Backlight        +           - normal + gamut Liquid Crystal Display with a White LED backlight.
    B   @@ -3092,12 +3624,23 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP -          Wide Gamut LCD, RGB LED - Backlight - wide gamut Liquid Crystal Display with RGB LED - backlight.
-     x -             LCD, CCFL - Type 2 + + + + + + + + + + + +          Wide Gamut LCD, RGB LED + Backlight - wide gamut Liquid Crystal Display with RGB LED + backlight.
+     x +             LCD, CCFL + Type 2 Backlight              @@ -3146,37 +3689,6 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - - normal gamut Liquid Crystal Display with alternative Cold Cathode - Fluorescent Lamp backlight (Laptop ?)
-
- The ambient light sensor can be used with the Spyder4Elite and Spyder4Pro instruments, but is - only capable of monochrome readings.
-
-
-

- Spyder 5 - colorimeter
-
- Spyder4

-
- Availability:
-
- The Spyder5Elite, Spyder5Pro and Spyder5Express are a currently - available instruments. The Spyder5Elite - and Spyder5Pro appear to be - identical hardware with different software from the manufacturer. - The Spyder5Express lacks - the ambient sensor.
-
- Operation:
-
- These instruments are capable of using using CCSS (Colorimeter @@ -3184,51 +3696,85 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - Calibration Spectral Sample) files, and this also gives the - instrument the capability of using a non-default standard observer. - CCSS files can be created using the ccxxmake tool - using a spectrometer as a reference.
-
- Important Note about the - DataColor Spyder 5 vendor display type/calibration support:
-
- This instrument does not have a full range of display type - calibration selections available without the vendor supplied - calibration data for it.
- This calibration data is not provided with Argyll, since it is not - available under a compatible license.
- You can use CCSS files as an alternative (see above), or as the - purchaser of a Spyder 5 instrument you should have received a copy - of the calibration data along with the instrument or have been - directed to download it from the manufacturers website, and should - therefore be able to enable the full range of display type - selections in Argyll by using the oeminst tool.
-
- The Display Selections for this instrument are:
-
-     n | l   -    A non-refresh type display with a generic calibration - [Default, CB1].
-     r | c    A - refresh type display with a generic calibration.[CB2]
-
- The Display Selections for this instrument when the manufacturers - calibration information has been installed is:
-
-     n      -      A non-refresh type display with a generic - calibration [Default, CB1].
-     r    -      A refresh type display with a generic - calibration.[CB2]
-     f    -          LCD, CCFL + + + + + - normal gamut Liquid Crystal Display with alternative Cold Cathode + Fluorescent Lamp backlight (Laptop ?)
+
+ The ambient light sensor can be used with the Spyder4Elite and Spyder4Pro instruments, but is + only capable of monochrome readings.
+
+
+

+ Spyder 5 + colorimeter
+
+ Spyder4

+
+ Availability:
+
+ The Spyder5Elite, Spyder5Pro and Spyder5Express are a currently + available instruments. The Spyder5Elite + and Spyder5Pro appear to be + identical hardware with different software from the manufacturer. + The Spyder5Express lacks + the ambient sensor.
+
+ Operation:
+
+ These instruments are capable of using using CCSS (Colorimeter Calibration Spectral + Sample) files, and this also gives the instrument the + capability of using a non-default standard observer. CCSS files can + be created using the ccxxmake tool + using a spectrometer as a reference.
+
+ Important Note about the + DataColor Spyder 5 vendor display type/calibration support:
+
+ This instrument does not have a full range of display type + calibration selections available without the vendor supplied + calibration data for it.
+ This calibration data is not provided with Argyll, since it is not + available under a compatible license.
+ You can use CCSS files as an alternative (see above), or as the + purchaser of a Spyder 5 instrument you should have received a copy + of the calibration data along with the instrument or have been + directed to download it from the manufacturers website, and should + therefore be able to enable the full range of display type + selections in Argyll by using the oeminst + tool.
+
+ The Display Selections for this instrument are:
+
+     n | l   +    A non-refresh type display with a generic calibration + [Default, CB1].
+     r | c    A + refresh type display with a generic calibration.[CB2]
+
+ The Display Selections for this instrument when the manufacturers + calibration information has been installed is:
+
+     n      +      A non-refresh type display with a generic + calibration [Default, CB1].
+     r    +      A refresh type display with a generic + calibration.[CB2]
+     f    +          LCD, CCFL Backlight                         @@ -3277,17 +3823,28 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - - normal gamut Liquid Crystal Display with standard Cold Cathode - Fluorescent Lamp backlight.
-     L -         Wide Gamut LCD, CCFL - Backlight      - wide gamut Liquid Crystal - Display with Cold Cathode Fluorescent Lamps backlight.
-     e -             LCD, White - LED Backlight        -           - normal - gamut Liquid Crystal Display with a White LED backlight.
+ + + + + + + + + + + + - normal gamut Liquid Crystal Display with standard Cold Cathode + Fluorescent Lamp backlight.
+     L +         Wide Gamut LCD, CCFL + Backlight      - wide gamut Liquid Crystal + Display with Cold Cathode Fluorescent Lamps backlight.
+     e +             LCD, White + LED Backlight        +           - normal + gamut Liquid Crystal Display with a White LED backlight.
    B   @@ -3336,12 +3893,23 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP -          Wide Gamut LCD, RGB LED - Backlight - wide gamut Liquid Crystal Display with RGB LED - backlight.
-     x -             LCD, CCFL - Type 2 + + + + + + + + + + + +          Wide Gamut LCD, RGB LED + Backlight - wide gamut Liquid Crystal Display with RGB LED + backlight.
+     x +             LCD, CCFL + Type 2 Backlight              @@ -3390,22 +3958,33 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - - normal gamut Liquid Crystal Display with alternative Cold Cathode - Fluorescent Lamp backlight (Laptop ?)
-
- The ambient light sensor can be used with the Spyder5Elite and Spyder5Pro instruments, but is - only capable of monochrome readings.
-
-

Colorim�tre HCFR - colorimeter
-
-

-
- Availability:
-
+ + + + + + + + + + + + - normal gamut Liquid Crystal Display with alternative Cold Cathode + Fluorescent Lamp backlight (Laptop ?)
+
+ The ambient light sensor can be used with the Spyder5Elite and Spyder5Pro instruments, but is + only capable of monochrome readings.
+
+

Colorim�tre HCFR + colorimeter
+
+

+
+ Availability:
+
The Colorim�tre @@ -3454,26 +4033,37 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - HCFR Probe is a kit instrument from HCFR. -
-
- OS X
-
- Please note the installation instructions.
-
- Operation:
-
- 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.
-
- The Display Selections for this instrument are:
-
+ + + + + + + + + + + + HCFR Probe is a kit instrument from HCFR. +
+
+ OS X
+
+ Please note the installation instructions.
+
+ Operation:
+
+ 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.
+
+ The Display Selections for this instrument are:
+
    l     @@ -3522,8 +4112,19 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - LCD display         A Liquid - Crystal Display [Default].
+ + + + + + + + + + + + LCD display         A Liquid + Crystal Display [Default].
    c    @@ -3572,38 +4173,49 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - CRT display         A Cathode Ray - Tube display.
-     R Raw - Reading       Raw sensor readings, - used for calibration [CB1]
-
-

ColorHug
-
-

-
- Availability:
-
- The ColorHug - is a low cost display colorimeter instrument from Hughski.
- ArgyllCMS will also work with the ColorHug2.
-
- Operation:
-
- Due to the nature of its sensor, the ColorHug accuracy is quite - dependent on the instrument calibration matrix. (The ColorHug2 - is much more forgiving though). 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.
-
- The Display Selections for this instrument are:
-
+ + + + + + + + + + + + CRT display A Cathode Ray + Tube display.
+ R Raw + Reading Raw sensor readings, + used for calibration [CB1]
+
+

ColorHug
+
+

+
+ Availability:
+
+ The ColorHug + is a low cost display colorimeter instrument from Hughski.
+ ArgyllCMS will also work with the ColorHug2.
+
+ Operation:
+
+ Due to the nature of its sensor, the ColorHug accuracy is quite + dependent on the instrument calibration matrix. (The ColorHug2 + is much more forgiving though). 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.
+
+ The Display Selections for this instrument are:
+
   l                   @@ -3622,7 +4234,18 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - LCD, CCFL Backlight [Default]
+ + + + + + + + + + + + LCD, CCFL Backlight [Default]
   c                  @@ -3642,7 +4265,18 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - CRT display
+ + + + + + + + + + + + CRT display
   p                  @@ -3662,7 +4296,18 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - Projector
+ + + + + + + + + + + + Projector
   e                  @@ -3681,7 +4326,18 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - LCD, White LED Backlight
+ + + + + + + + + + + + LCD, White LED Backlight
   F                  @@ -3701,7 +4357,18 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - Factory matrix (For Calibration) [CB1]
+ + + + + + + + + + + + Factory matrix (For Calibration) [CB1]
   R                 @@ -3721,31 +4388,53 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - Raw Reading (For Factory matrix Calibration) [CB2]
-
-

+ + + + + + + + + + + + Raw Reading (For Factory matrix Calibration) [CB2]
+
+

Palette/SwatchMate - Cube
-
- SwatchMate Cube

-
- Availability:
-
- The Cube from Palette/SwatchMate - is a currently available entry level Colorimeter, with somewhat - limited accuracy. The ArgyllCMS driver provides two - alternative calibrations that noticably improve - this accuracy.
-
- The Calibration Selections for this instrument are:
-
- m + + + + + + + + + + + + Cube
+
+ SwatchMate Cube

+
+ Availability:
+
+ The Cube from Palette/SwatchMate + is a currently available entry level Colorimeter, with somewhat + limited accuracy. The ArgyllCMS driver provides two + alternative calibrations that noticably improve + this accuracy.
+
+ The Calibration Selections for this instrument are:
+
+    m                 @@ -3753,7 +4442,18 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - Matt surfaces [Default]
+ + + + + + + + + + + + Matt surfaces [Default]
   g                  @@ -3773,8 +4473,19 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - Gloss surfaces
-    N + + + + + + + + + + + + Gloss surfaces
+    N                 @@ -3782,54 +4493,69 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP - Native Calibration
-
- Operation:
-
- The Cube must be connected via USB for operation with ArgyllCMS, and - can be connected either by USB or using Bluetooth LE when used with - ArgyllPRO ColorMeter on - capable Android devices.
-
- The Cube goes to sleep fairly rapidly and must be woken up by - pressing the top of it before connecting via USB to be recognized by - ArgyllCMS, although once connected, and with an ArgyllCMS utility - running, it should stay awake.
-
- When connecting via Bluetooth to ColorMeter, the foreground - application will be the one that connects to it.
-
- The ability to measure values into its own memory and recover them - later is not supported, since it is not possible to use the - ArgyllCMS calibrations with this feature.
-
- Calibration:
-
- As well as the normal white calibration step, the ArgyllCMS driver - offers two option supplemental calibration steps that can improve - accuracy, but both require appropriate calibration conditions. You - can use spotread with the 'k' command - to trigger this calibration.
-
- The black calibration requires a light trap, and the easiest - way of providing this is to place the Cube in a location that is - dark (i.e. not illuminated directly by any light) and some distance - from any surface. A practical approach I have used is to place the - measuring end in a thick black sock, and hide it from direct - illumination while this calibration step is done.
-
- The gloss calibration requires a black glossy surface. I - have used a paint catalog gloss paint black sample square for this, - but some other completely black glossy surface of sufficient size - such as a glossy black plastic item or a smooth surface painted in - gloss black paint should also work.
-
-
-
-
-
-
-
-
- - + + + + + + + + + + + + Native Calibration
+
+ The Cube makes use of the newer FTDI FT231XS Virtual + COM Port Drivers (VCP), that may need installing for your operating + system. See installation instructions.
+
+ Operation:
+
+ The Cube must be connected via USB for operation with ArgyllCMS, and + can be connected either by USB or using Bluetooth LE when used with + ArgyllPRO ColorMeter on + capable Android devices.
+
+ The Cube goes to sleep fairly rapidly and must be woken up by + pressing the top of it before connecting via USB to be recognized by + ArgyllCMS, although once connected, and with an ArgyllCMS utility + running, it should stay awake.
+
+ When connecting via Bluetooth to ColorMeter, the foreground + application will be the one that connects to it.
+
+ The ability to measure values into its own memory and recover them + later is not supported, since it is not possible to use the + ArgyllCMS calibrations with this feature.
+
+ Calibration:
+
+ As well as the normal white calibration step, the ArgyllCMS driver + offers two option supplemental calibration steps that can improve + accuracy, but both require appropriate calibration conditions. You + can use spotread with the 'k' command + to trigger this calibration.
+
+ The black calibration requires a light trap, and the easiest + way of providing this is to place the Cube in a location that is + dark (i.e. not illuminated directly by any light) and some distance + from any surface. A practical approach I have used is to place the + measuring end in a thick black sock, and hide it from direct + illumination while this calibration step is done.
+
+ The gloss calibration requires a black glossy surface. I + have used a paint catalog gloss paint black sample square for this, + but some other completely black glossy surface of sufficient size + such as a glossy black plastic item or a smooth surface painted in + gloss black paint should also work.
+
+
+
+
+
+
+
+
+ + diff --git a/doc/oeminst.html b/doc/oeminst.html index d1daccd..b52f1f2 100644 --- a/doc/oeminst.html +++ b/doc/oeminst.html @@ -9,11 +9,11 @@

spectro/oeminst

Summary

- A special purpose tool that installs various Instruments - Manufacturers support files to enable various instrument operations - when used with Argyll, as well as install colorimeter calibration - and spectral sample files so that they appear in the display type - list (-y option).
+ A special purpose tool that installs Instruments Manufacturers + support files to enable various instrument operations when used with + Argyll, as well as install colorimeter calibration and spectral + sample files so that they appear in the display type list (-y + option).
For the Spyder 2, it can install the instrument manufacturers PLD firmware pattern, which is necessary for it to operate.
For the Spyder 4 or 5, it can enable the full range of manufacturers @@ -39,6 +39,8 @@ + + Verbose
-n                      @@ -51,6 +53,8 @@ + + Don't install, show where files would be installed
-c                      @@ -64,6 +68,8 @@ + + Don't install, save files to current directory
-S @@ -78,9 +84,14 @@ + + Specify the install scope u = user (def.), l = local system]
infile                  + Manufacturers setup.exe install file(s) or .dll(s) containing + install files
+ infile.[edr|ccss|ccmx] @@ -91,17 +102,6 @@ - setup.exe CD install file(s) or .dll(s) containing install files
- infile.[edr|ccss|ccmx] - - - - - - - - EDR file(s) to translate and install or CCSS or CCMX files to install
@@ -116,6 +116,8 @@ + + If no file is provided, oeminst will look for the install CD.

@@ -159,6 +161,8 @@ + + 2 instrument cannot function without the presence of the instrument vendors PLD firmware pattern for the device. This firmware is not provided with Argyll, since it has not been made @@ -196,6 +200,8 @@ href="http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html">XDG + + Base Directory specifications are used as a basis for storing the file). Programs that access instruments such as spotread, XDG + + 4 or Spyder 5 instrument does not have the full range of vendor instrument calibration options without the presence of the instrument vendors calibration @@ -295,6 +303,8 @@ href="http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html">XDG + + Base Directory specifications are used as a basis for storing the file). Programs that access instruments such as spotread, XDG have to mount the CDROM manually, and give oeminst the path to the CDROM setup/setup.exe file as the argument inputfile.
+
+ If you have not been provided with a CDROM, then you may be able to + download an MSWindows install package from the Manufacturers website, + and then run oeminst on that file.

NOTE that under OS X 10.6 (Snow Leopard) and latter, you may need to run oeminst diff --git a/doc/profcheck.html b/doc/profcheck.html index a85e07e..079190c 100644 --- a/doc/profcheck.html +++ b/doc/profcheck.html @@ -30,6 +30,7 @@ Show + CIE94 delta E values
-k           @@ -43,6 +44,7 @@ create + X3DOM visualization (iccprofile.x3d.html)
-x           @@ -53,6 +55,7 @@ Use + X3DOM axes
-m              Make @@ -62,6 +65,7 @@ X3DOM + lines a minimum of 0.5
-e              Color @@ -71,14 +75,17 @@ vectors + acording to delta E
-s              + Sort output by delta E
-h              + Plot a histogram of delta E's
-P de           @@ -94,6 +101,7 @@ Specify + a device value to sort against
-p           @@ -104,6 +112,7 @@ Sort + device value by PCS/Lab target
-f @@ -115,6 +124,7 @@ Sort + M0, M1, M2, A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp]
-i illum        Choose @@ -126,6 +136,7 @@ Sort + A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp
@@ -139,6 +150,7 @@ Sort + 1931_2 (def.), 1964_10, S&B 1955_2, shaw, @@ -174,7 +186,10 @@ Sort
The -v flag prints out extra information during the checking. A value greater than 1 will print the color values of each - test point.
+ test point on a line. The line consists of:
+ [Delta_E] Patch_no: + Device values -> Profile PCS values should + be .ti3 PCS values

The -c option causes the differences between the test values and the profile prediction of the color for each device value to be @@ -208,7 +223,8 @@ Sort badly read patches.

The -h flag will display a histogram plot of the fit delta - E's. The X scale is delta E, the Y scale is %
+ E's, as well as print each bin's details. The X scale is delta E, + the Y scale is % area of each bin.

The -P N.NN option will create a pruned .ti3 file called data_pN.NN that contains just the measurement points that have a fit diff --git a/doc/spec2cie.html b/doc/spec2cie.html index 7911948..2780161 100644 --- a/doc/spec2cie.html +++ b/doc/spec2cie.html @@ -1,7 +1,7 @@ - fakeread + spec2cie @@ -9,38 +9,60 @@

spectro/spec2cie

Summary

- Convert reflective spectral .ti3 - readings into CIE XYZ and D50 L*a*b* readings. Apply FWA, plot - spectrums.
+ Convert spectral .ti3 or .sp readings into CIE XYZ and D50 + L*a*b* readings. Apply FWA, plot spectrums.
+ This is assumed to be for a reflective media by default - i.e. that + the input .ti3 or .sp file values are spectral reflectances, unless + the input is marked as DEVICE_CLASS + + + EMISINPUT (See the description of the .ti3 format. This + would have to be done manually, as no ArgyllCMS tools generate such + data.)

Usage

- spec2cie [options] input.ti3 + spec2cie [options] input.[ti3|sp] - output.ti3 + + + + output.[ti3|sp] -v - + + Verbose mode -I illum - Override actual instrument illuminant in .ti3 - file: + + + + Override actual + instrument illuminant in .ti3 or .sp file: - A, C, D50, D50M2, D65, F5, F8, F10 or - file.sp - + A, C, D50, D50M2, + D65, F5, F8, F10 or file.sp + + + + (only used in conjunction with -f) -f [illum] Use - Fluorescent Whitening Agent compensation [simulated inst. - illum.: - + href="colprof.html#f">-f [illum] + Use Fluorescent Whitening + Agent compensation [simulated inst. illum.: + + + + @@ -48,56 +70,61 @@ file.sp] -i illum - Choose illuminant for computation of CIE XYZ - from spectral data & FWA: + Choose illuminant for + computation of CIE XYZ from spectral data & FWA: - A, C, D50 (def.), D50M2, D65, F5, - F8, F10 or file.sp + A, C, D50 + (def.), D50M2, D65, F5, F8, F10 or file.sp -o observ - Choose CIE Observer for spectral data: + + + + Choose CIE Observer for + spectral data: - + + + + 1931_2 (def.), 1964_10, S&B 1955_2, shaw, J&V 1978_2 or file.cmf - -n + -n Don't output - spectral values - -p - - Plot each values spectrum - input.ti3 -Measurement - - file - output.ti3 - + spectral values + -p + - Converted measurement file + Plot each values spectrum+ input.[ti3|sp] + Measurement file + output.[ti3|sp] + Converted measurement file

Comments

This program takes the (usually reflective) spectral data in a .ti3 - file, converts them to XYZ and D50 L*a*b* and fills the XYZ_[XYZ] - and LAB_[LAB] columns in the output .ti3 file. If the columns - XYZ_[XYZ] and/or LAB_[LAB] are missing in the input file, they are - added to the output file.
+ or .sp file, converts them to XYZ and D50 L*a*b* and fills the + XYZ_[XYZ] and LAB_[LAB] columns in the output .ti3 or .sp file. If + the columns XYZ_[XYZ] and/or LAB_[LAB] are missing in the input + file, they are added to the output file.

If FWA correction is applied, then the spectra saved will be FWA corrected, as well as the XYZ and D50 L*a*b* values.

- All other columns are copied from the input to the output .ti3 file.
+ All other columns are copied from the input to the output .ti3 or + .sp file.

Setting an actual instrument/simulated instrument/CIE illuminant only has an effect for reflective/transmissive spectra. Emissive @@ -139,15 +166,18 @@ Measurement + + + colprof -f for a fuller explanation.

The -i parameter allows specifying a standard or custom illumination spectrum, applied to spectral .ti3 - data to compute PCS (Profile Connection Space) tristimulus values. A, - D50, D65, F5, F8, F10 are a - selection of standard illuminant spectrums, with D50 being - the default. If a filename is specified instead, it will be assumed - to be an Argyll specific .sp + pr .sp data to compute PCS (Profile Connection Space) tristimulus + values. A, D50, D65, F5, F8, + F10 are a selection of standard illuminant spectrums, with D50 + being the default. If a filename is specified instead, it will be + assumed to be an Argyll specific .sp custom spectrum file. This only works if spectral data is available. Illuminant details are:

diff --git a/doc/spotread.html b/doc/spotread.html index 3fe030f..36ee999 100644 --- a/doc/spotread.html +++ b/doc/spotread.html @@ -37,6 +37,15 @@ + + + + + + + + + @@ -70,6 +79,15 @@ + + + + + + + + + @@ -108,6 +126,15 @@ + + + + + + + + + @@ -140,6 +167,15 @@ + + + + + + + + + @@ -172,6 +208,15 @@ + + + + + + + + + @@ -203,6 +248,15 @@ + + + + + + + + + @@ -227,6 +281,15 @@ + + + + + + + + + Use display white point relative chromatically adjusted mode
-p
-E extrafilterfile    Apply extra filter compensation file
+ -A N|A|X|G            + + + + + + + + XRGA conversion (default N)
-x                    @@ -694,6 +892,15 @@ D50 + + + + + + + + + @@ -724,6 +931,15 @@ D50 + + + + + + + + + @@ -754,6 +970,15 @@ D50 + + + + + + + + + @@ -784,6 +1009,15 @@ D50 + + + + + + + + + @@ -813,6 +1047,15 @@ D50 + + + + + + + + + @@ -843,6 +1086,15 @@ D50 + + + + + + + + + @@ -860,6 +1112,14 @@ D50                    Use high resolution spectrum mode (if available)
+ -R fname.sp           + + + + + + + Preset reference to spectrum
-X file.ccmx          @@ -878,6 +1138,15 @@ D50 + + + + + + + + + @@ -912,6 +1181,15 @@ Samples + + + + + + + + + @@ -937,6 +1215,15 @@ Samples + + + + + + + + + @@ -958,6 +1245,15 @@ Samples + + + + + + + + + Override measured refresh rate with rate Hz
-Y A
+ -Y W:fname.sp         + + + + + + + Save white tile ref. spectrum to file
+ -Y L       +    Test for i1Pro Lamp + Drift, and remediate it
-W n|h|x              Override @@ -991,6 +1298,15 @@ none, + + + + + + + + + @@ -1025,6 +1341,15 @@ none, + + + + + + + + + @@ -1061,10 +1386,10 @@ none, The Graph plots light wavelength on the X axis, and either absolute or relative level on the Y axis.

- +

- +

- - + - - - - - - - - - - @@ -1185,11 +1519,19 @@ none, allows measuring in ambient illumination mode using instruments that support this mode (i.e. Eye-One Display 2). Values returned are absolute, and include the various color temperatures and Color - Rendering Index (see -T). + Rendering Index (see -T). + + If the instrument does not support ambient mode, emissive mode will be used instead. An adaptive integration time will be used in devices that support it.

+ For an instrument that supports it (i.e. the Emulated transmission + measurement mode of the JETI 1211), then using -a after the + -t switch will select the alternate 90/diffuse transmission + geometry (i.e. using the ambient adapter for transmission + measurement).
+
The -f flag allows measuring a flash with those instruments that support scanning emissive measurements. The instrument needs to be triggered @@ -1223,13 +1565,10 @@ none, reflectance instrument illuminant when FWA compensation is used during measurement, overriding the default D50 or CIE computation illuminant used for FWA (see -i below). If - - - using M0, M1 or M2, then the -i - option is not normally used. See colprof - - - -f for a fuller explanation.
+ intending to use standard M0, M1 or M2 + conditions, then use just the -I option and not the -i + option. See colprof -f for a fuller + explanation.

The -i parameter allows specifying a standard or custom reflectance illumination spectrum applied to compute CIE tristimulus values. A, D50, D50M2, D65, F5, F8, F10 are a selection of standard illuminant spectrums, with D50 - being the default. If using -I M0, M1 or M2, - then this -i option is not normally used. If a - filename is specified instead, it will be assumed to be an Argyll - specific .sp spectrum file. If - FWA compensation is used during measurement, this illuminant will be - used by default as the simulated instrument illuminant.
+ being the default. If using -I to obtain standard M0, + M1 or M2 conditions, then this -i option is not + normally used. If a filename is specified instead, it will be + assumed to be an Argyll specific .sp + spectrum file. If FWA compensation is used during measurement, this + illuminant will be used by default as the simulated instrument + illuminant.

The -Q flag allows specifying a tristimulus observer, and is used to compute PCS (Profile Connection Space) @@ -1275,6 +1615,21 @@ none, style="font-weight: bold;">Note that this is currently only supported by the Spectrolino driver.]

+ The -A options allows overriding the default + or environment variable set XRGA + conversion:
+
+     -A N|A|X|G
+
+         The N argument sets + the calibration to Native (default).
+         The A argument sets + the calibration to XRGA.
+         The X argument sets + the calibration to XRDI.
+         The G argument sets + the calibration to GMDI.
+
The -x option causes the reading to be displayed as XYZ and Yxy values, rather than the default XYZ and L*a*b*
@@ -1327,6 +1682,13 @@ none, supports it. See Operation of particular instruments for more details.

+ The -R fname.sp + option allows specifying a reference spectrum to preset the + reference values used to calculate delta E etc. This can be useful + in checking against a previously saved value ('s' command), + or in checking the instruments consistency against it's reflective white reference spectrum.
+
The -X file.ccmx option reads a Colorimeter Correction Matrix @@ -1343,10 +1705,8 @@ none, colorimeters that rely on sensor spectral sensitivity calibration information (ie. the X-Rite i1d3, or the DataColor Spyder4 & - Spyder5).This - can - improve - a colorimeters accuracy for a particular type of display.
+ Spyder5).This can improve a colorimeters accuracy for a + particular type of display.

The -Y r and @@ -1360,6 +1720,15 @@ none, + + + + + + + + + @@ -1397,6 +1766,39 @@ none, sets Xon/Xoff handshaking. This commend may be useful in workaround serial communications issues with some systems and cables.

+ The -Y W:fname.sp option allows + saving an instruments reference white tile reflectance spectrum to a + file. Reflective instruments use a white reference tile to calibrate + against, and typically the spectral reflectance of the white tile is + recorded inside the instrument to calibrate to. The saved spectrum + can be used to compare against the measurements of a reference grade + measurement of the white tile to check for tile deterioration, or + can be used as a reference for checking on instrument calibration + accuracy or consistency (See the -R option). Not + all instruments support this option (Currently the Spectrolino, + i1Pro, i1Pro2 and ColorMunki spectrometer.)
+
+ The -Y l|L option is a special function + for X-Rite i1Pro instruments. + These instruments use an incandescent lamp as a light source for + reflectance measurement, and some instruments after some patterns of + use, can suffer from Lamp output thermal drift, due to the build up + of filament tungsten on the bulb inner surface. This function first + measures the Lamp drift, and then if the -Y L version is + used and the drift is greater than normal (0.06 - 0.1 Delta E), it + will attempt to remediate the problem by turning the lamp on for + some seconds so that it reaches normal operating temperature and is + able to re-circulate the tungsten back onto the filament properly. + It will then wait for the lamp to cool, and re-measure the drift. + These operations can take a few minutes, and it is advisable to let + the instrument cool off further after this operation, for 2 - 5 + minutes, to allow it to return to normal operation conditions.
+
+ The remediation function should be used infrequently or if the + repeatability of the instrument seems to be poorer than usual, as + frequent use may consume lamp life unnecessarily. If the lamp is + nearing its end of life, this function may not be effecive.
+
The -D 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 diff --git a/doc/synthcal.html b/doc/synthcal.html index 89f3fed..229f506 100644 --- a/doc/synthcal.html +++ b/doc/synthcal.html @@ -1,108 +1,138 @@ - + - - synthcal - - - - -

spectro/synthcal

Summary

-Create synthetic calibration file. The default is a linear calibration -file.
-

Usage

-synthcal [-options] basename
- -t -N            i = -input, o = output, d = display (default)
- -d col_comb     choose colorant combination -from the following:
-                 + + synthcal + + + + +
spectro/synthcal
+
Summary
+ Create synthetic calibration file. The default is a linear + calibration + file.
+
Usage
+ synthcal [-options] basename
+ -r + res          Set + the calibration resolution (default 256)
+ -t + N            + i = + input, o = output, d = display (default)
+ -d col_comb     choose colorant + combination + from the following:
+                  0: -Print grey
-                 +Print + grey
+                  1: -Video grey
-                 +Video + grey
+                  2: -Print RGB
-                 +Print + RGB
+                  3: -Video RGB
-                 -4: -CMYK
+Video + RGB
                 -5: -CMY
+ 4: + CMYK
                 + 5: + CMY
+                  6: -CMYK + Light CM
-                 +CMYK + + Light CM
+                  7: -CMYK + Light CMK
-                 +CMYK + + Light CMK
+                  8: -CMYK + Red + Blue
-                 +CMYK + + Red + Blue
+                  9: -CMYK + Orange + Green
-                 +CMYK + + Orange + Green
+                  10: -CMYK + Light CMK + Light Light K
-                 +CMYK + + Light CMK + Light Light K
+                  11: -CMYK + Orange + Green + Light CM
-                 +CMYK + + Orange + Green + Light CM
+                  12: -CMYK + Light CM + Medium CM
- -D colorant     Add or delete colorant from -combination:
-                 +CMYK + + Light CM + Medium CM
+ -D colorant     Add or delete colorant + from + combination:
+                  (Use --?? to list known colorants)
- -o -o1,o2,o3,    Set non-linear curve offset -(default 0.0)
- -s -s1,s2,s3,    Set non-linear curve scale -(default 1.0)
- -p p1,p2,p3,    Set non-linear curve powers -(default 1.0)
- outfile         Base name -for output .cal file
-

Comments
-

-This is the tool creates a calibration (.cal) -file that has a linear table -for each channel. This is useful in setting up a display for -evaluation, disabling printer calibration, testing, or to recover a -display that has a strange set of -Video LUTs loaded.
-
-The -t option -selects the type of device the calibration file is intended for. -Default is display.
-
-The -d option -selects the device colorspace. The default for input and display is Video RGB, while the default for output is CMYK.
-
- The -D parameter modifies the colorspace set -by -d by allowing individual -colorants to be added or subtracted from the colorspace.
-
-Optionally it can be used to create a non-linear calibration file, -useful for diagnostics. Each of the device channel curves can be -given a gamma (power curve) shape, scaled to a maximum other than -1.0, and offset from a value other than 0.0.
-
- +-?? + to list known colorants)
+ -o + o1,o2,o3,    Set non-linear curve offset + (default 0.0)
+ -s + s1,s2,s3,    Set non-linear curve scale + (default 1.0)
+ -p p1,p2,p3,    Set non-linear curve powers + (default 1.0)
+ outfile         + Base name + for output .cal file
+

Comments
+

+ This is the tool creates a calibration (.cal) + file that has a linear table + for each channel. This is useful in setting up a display for + evaluation, disabling printer calibration, testing, or to recover a + display that has a strange set of + Video LUTs loaded.
+
+ The -r + parameter + selects the table resolution. The default is 256.
+
+ The -t + option + selects the type of device the calibration file is intended for. + Default is display.
+
+ The -d + option + selects the device colorspace. The default for input and display is + Video RGB, while the default for output + is CMYK.
+
+ The -D parameter modifies the colorspace + set + by -d by allowing + individual + colorants to be added or subtracted from the colorspace.
+
+ Optionally it can be used to create a non-linear calibration file, + useful for diagnostics. Each of the device channel curves can be + given a gamma (power curve) shape, scaled to a maximum other than + 1.0, and offset from a value other than 0.0.
+
+ diff --git a/doc/targen.html b/doc/targen.html index 81b331b..ef84f81 100644 --- a/doc/targen.html +++ b/doc/targen.html @@ -12,8 +12,10 @@ Generate a profiling test target values .ti1 file. targen is used to generate the device channel test point values for - grayscale, RGB, CMY, CMYK or N-color output or display - devices. + grayscale, RGB, CMY, CMYK or N-color output or display devices.
+
+ [ Note though that colprof will only create RGB, CMY or CMYK + profiles. ]

Usage Summary

targen [options] outfile
@@ -43,6 +45,8 @@ + + 0: Print grey
            @@ -60,6 +64,8 @@ + +      1: Video grey
         @@ -78,6 +84,8 @@ + +       2: Print RGB
    @@ -103,6 +111,8 @@ + + 5: CMY
   @@ -125,6 +135,8 @@ + +        7: CMYK + Light CMK
          @@ -151,6 +163,8 @@ Red + + + Blue
        @@ -182,6 +196,8 @@ Red + +         12: CMYK + Light CM + Medium CM
@@ -206,6 +222,8 @@ Red + +            0: Additive
    @@ -236,6 +254,8 @@ Red + +           4: Black
          @@ -254,6 +274,8 @@ Red + +            5: Orange
         @@ -273,6 +295,8 @@ Red + + 6: Red
                     @@ -291,6 +315,8 @@ Red + + 7: Green
                     @@ -309,6 +335,8 @@ Red + + 8: Blue
                     @@ -327,6 +355,8 @@ Red + + 9: White
                     @@ -345,6 +375,8 @@ Red + + 10: Light Cyan
                     @@ -363,6 +395,8 @@ Red + + 11: Light Magenta
                     @@ -381,6 +415,8 @@ Red + + 12: Light Yellow
        @@ -398,6 +434,8 @@ Red + +              13: Light Black
@@ -418,6 +456,8 @@ Red + + 14: Medium Cyan
                     @@ -436,6 +476,8 @@ Red + + 15: Medium Magenta
                     @@ -454,6 +496,8 @@ Red + + 16: Medium Yellow
         @@ -471,6 +515,8 @@ Red + +           17: Medium Black
           @@ -489,6 +535,8 @@ Red + +           18: Light Light Black
-G              @@ -507,6 +555,8 @@ Red + + Generate good optimzed points rather than Fast
         @@ -550,6 +602,8 @@ Red + + Single channel steps (default 0)

-m steps
-f @@ -633,6 +693,8 @@ steps + + patches      @@ -649,6 +711,8 @@ steps + + Add iterative & adaptive full spread patches to total (default 836)
                     @@ -667,6 +731,8 @@ steps + + Default is Optimised Farthest Point Sampling (OFPS)

-r
-R
-q -Q

-l ilimit -p power
-O              - Don't re-order display RGB patches for minimum delay
- -w
+ -U +              + Don't filter out duplicate patches
+ -w              @@ -989,6 +1083,8 @@ device + + Dump diagnostic outfile.x3d.html file (Lab locations)
-W

Usage Details and Discussion

@@ -1091,6 +1189,8 @@ device + + 5 will generate steps at 0.0 0.25 0.5 0.75 and 1.0, while the option -s 5 -p 2.0 will generate steps at 0.0 0.0625 0.25 0.5625 and 1.0. By default, no per @@ -1153,6 +1253,8 @@ device + + -b flags, is not to duplicate test values already created by a previous type.

@@ -1323,18 +1425,11 @@ device 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 -p power - value in changing the distribution of -s steps, -g steps, -m steps - and -b - - - - - - steps patches.
+ href="targen.html#p">-p power value in changing the + distribution of -s steps, + -g steps, -m steps and -b steps patches.

The -F flag and parameters is used to define an L*a*b* sphere to filter the test points through. Only test @@ -1359,12 +1454,15 @@ device this re-ordering, leaving the patches in whatever order they were generated.

+ The -U flag disables the normal filtering + out of duplicate patches.
+
The -w flag causes a diagnostic X3DOM .x3d.html file to be created, in - which the test points are plotted as small spheres in L*a*b* - colorspace. Note that for a CMYK device, the point spacing may seem - strange, since the extra K dimension is compressed into the 3 - dimensional L*a*b* space. If the X3DOM .x3d.html file to be + created, in which the test points are plotted as small spheres in + L*a*b* colorspace. Note that for a CMYK device, the point spacing + may seem strange, since the extra K dimension is compressed into the + 3 dimensional L*a*b* space. If the -W flag is given, the plot will be in device space, with only the first 3 dimensions of each point being plotted.
diff --git a/doc/ti3_format.html b/doc/ti3_format.html index 559aa12..ca1be87 100644 --- a/doc/ti3_format.html +++ b/doc/ti3_format.html @@ -58,6 +58,7 @@ + "DISPLAY", "INPUT" or "EMISINPUT".
@@ -75,6 +76,13 @@ what the valid device gamut is, and what total ink limit should be used in creating the profile tables.

+ An "OUTPUT" type device may + have an ILLUMINANT_WHITE_POINT_XYZ + keyword that contains the XYZ of the illuminant used to compute the + CIE values from spectral reflectance or transmittance values. If + this tag is absent, the illuminant is assumes to be ICC standard + D50.
+
A "DISPLAY" type device may have a LUMINANCE_XYZ_CDM2 keyword that contains the absolute XYZ value of white in candelas @@ -83,6 +91,7 @@ + 119.657745 121.474236".

A display device may also have a Image dependent gamut mapping using device links for an example workflow.

- See 3D Viewing - Format for switching to VRML or X3D output format.
+ See 3D Viewing Format for switching to + VRML or X3D output format.

Usage Summary

tiffgamut [-v level] [profile.icm | embedded.tif/jpg] infile1.tif/jpg @@ -47,6 +47,7 @@ + Verbose
-d sres       Surface resolution @@ -58,6 +59,7 @@ emit + X3DOM .x3d.html file as well as CGATS .gam file
-n            @@ -67,6 +69,7 @@ Don't + add X3DOM axes or white/black point
-k            @@ -76,6 +79,7 @@ Add + markers for prim. & sec. "cusp" points
-f perc       Filter by popularity, perc = percent to use

@@ -105,6 +110,7 @@ r + = reverse (priority: monochrome > matrix > lut)
-p oride
@@ -138,6 +145,7 @@ either + pe - Print evaluation environment (CIE 116-1995)
           @@ -146,6 +154,7 @@ either + pc - Critical print evaluation environment (ISO-3664 P1)
@@ -159,6 +168,7 @@ either + mb - Monitor in bright work environment
     @@ -186,6 +196,7 @@ s:surround   + n = auto, a = average, m = dim, d = dark,
               @@ -195,6 +206,7 @@ s:surround   +    c = transparency (default average)
         @@ -204,6 +216,7 @@ w:X:Y:Z      + Adapted white point as XYZ (default media white)
         @@ -213,6 +226,7 @@ w:x:y        + Adapted white point as x, y
         @@ -222,6 +236,7 @@ a:adaptation + Adaptation luminance in cd.m^2 (default 50.0)
         @@ -231,6 +246,7 @@ b:background + Background % of image luminance (default 20)
         l:imagewhite Image white in cd.m^2 if surround = auto (default 250)
         @@ -257,8 +274,13 @@ f:flare      + g:x:y        Glare color as - x, y
+ x, y
+ -x + pcent      Expand/compress gamut + cylindrically by percent
-O outputfile Override the default output filename & extension.

@@ -340,6 +362,12 @@ f:flare      viewing environment, or controlling particular viewing condition parameters. This is only functional if an ICC profile is provided.

+ The -x parameter allows expanding or compressing the + resulting gamut in a cylindrical direction by the given percentage + :- i.e "-x 120" will expand by 20%. This may be useful for creating + a general compression gamut mapping by using such an expanded device + gamut as input to collink -g or -G.
+
The -O parameter allows the output file name & extension to be specified independently of the last tiff/jpeg filename. Note that the full filename must be diff --git a/doc/txt2ti3.html b/doc/txt2ti3.html index 0fc467d..783d3b6 100644 --- a/doc/txt2ti3.html +++ b/doc/txt2ti3.html @@ -28,12 +28,17 @@ -d            Set + type of device as Display, not Output
-i            Set - type of device as Input, not Output
+ + type of device as Input, not Output
+ -T +            + Transpose sample name Letters and Numbers
[devfile]     Input @@ -44,6 +49,7 @@ Set Input CIE, + Spectral or Device & Spectral file (typically file.txt)
[specfile]
+ If the -T flag is used, then the patch location will be transposed + from letter/number to letter/numer - i.e.
+
+     B5 -> E2
+

diff --git a/doc/xicclu.html b/doc/xicclu.html index 831977d..bd98058 100644 --- a/doc/xicclu.html +++ b/doc/xicclu.html @@ -3,7 +3,7 @@ xicclu + charset=windows-1252"> @@ -29,9 +29,9 @@ -v level       - Verbosity level 0 - 2 (default = 1)
- + -g Plot slice instead of looking colors up. (Default @@ -39,8 +39,11 @@ -G s:L:a:b     Override plot slice start with Lab or Jab co-ordinate
-G e:L:a:b     - Override plot slice end with Lab or Jab co-ordinate
+ Override plot slice end with Lab or Jab co-ordinate
+ -V             + + Use 'vcgt' calibration tag from profile
-f function    f = forward, @@ -54,6 +57,8 @@ if + + inverted forward, ib = inverted backwards
p = perceptual, s = saturation
+ monospace;">s = saturation, A = disp. abs. measurements
-o order       @@ -79,6 +87,8 @@ if + + n = normal (priority: lut > matrix > monochrome)
                @@ -89,6 +99,8 @@ r + + reverse (priority: monochrome > matrix > lut)
j = CIECAM02 Appearance Jab, J = CIECAM02 Appearance JCh
@@ -111,16 +125,22 @@ Scale + + device range 0.0 - scale rather than 0.0 - 1.0

-e flag        + + Video encode device input as:
-E flag        + + Video decode device output as:
     n           @@ -159,6 +179,8 @@ h + + = 0.5 K, x = max K, r = ramp K (def.)
               @@ -169,6 +191,8 @@ l + + = extra PCS input is portion of K locus
               @@ -179,6 +203,8 @@ v + + = extra PCS input is K target value

               @@ -202,6 +230,8 @@ stpo: + + start point of transition Wh 0.0 - Bk 1.0
               @@ -212,6 +242,8 @@ enpo: + + End point of transition Wh 0.0 - Bk 1.0
               @@ -222,6 +254,8 @@ enle: + + K level at Black 0.0 - 1.0
               @@ -232,6 +266,8 @@ shape: + + 1.0 = straight, 0.0-1.0 concave, 1.0-2.0 convex

-b             use @@ -282,6 +322,8 @@ CAM + + Jab for clipping
-m
@@ -319,6 +363,8 @@ pe + + - Print evaluation environment (CIE 116-1995)
           @@ -328,6 +374,8 @@ pc + + - Critical print evaluation environment (ISO-3664 P1)
@@ -342,6 +390,8 @@ pc + + mb - Monitor in bright work environment
     @@ -372,6 +422,8 @@ n + + = auto, a = average, m = dim, d = dark,
               @@ -382,6 +434,8 @@ n + +     c = transparency (default average)
          @@ -392,6 +446,8 @@ Adapted + + white point as XYZ (default media white, Abs: D50)
          @@ -402,6 +458,8 @@ Adapted + + white point as x, y
          a:adaptation @@ -411,6 +469,8 @@ Adaptation + + luminance in cd.m^2 (default 50.0)
@@ -428,12 +488,16 @@ light + + % of image luminance (default 1)
          + + g:glare      Glare light % of ambient (default 2)
    @@ -445,6 +509,8 @@ light + + g:x:y        FGare color as x, y

@@ -497,6 +563,8 @@ light If a CAL file is used, then -g will simply plot the each channels calibration curve. It will also plot the invers curve for -f + + b.

The -G :' character (no spaces).

+ The -V flag tells xicclu to load the given + ICC profile, and the extract the 'vcgt' display calibration curves + from the profile. The calibration curves can then be looked up in + the normal way, or plotted using -g.
+
The -f 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 @@ -529,6 +602,9 @@ light The -i flag selects the intent table used for a lut based profile. It also selects between relative and absolute colorimetric for non-lut base profiles.
+ The -A flag selects Display absolute measurement mode, where the + Luminance tag value is used restore absolute measurement XYZ values. + The PCS will be force to be XYZ with this selection.

A profile is allowed to contain more than the minimum number of elements or table needed to describe a certain @@ -566,9 +642,8 @@ light between 0 and 255, use -s 255.

The -e flag applies a Video encoding - to the input. See -E for - the list of encodings.
+ to the input. See -E for the + list of encodings.

The -E flag applies a Video encoding to the output. The possible encoding are:
@@ -580,6 +655,8 @@ light + + normal RGB 0..1 full range levels (default)
     t                @@ -587,6 +664,8 @@ light + + RGB (16-235)/255 "TV" levels
     6                @@ -594,6 +673,8 @@ light + + Rec601 YCbCr SD (16-235,240)/255 "TV" levels
     7                @@ -601,6 +682,8 @@ light + + Rec709 1125/60Hz YCbCr HD (16-235,240)/255 "TV" levels
     5                @@ -608,6 +691,8 @@ light + + Rec709 1250/50Hz YCbCr HD (16-235,240)/255 "TV" levels
     2                @@ -615,6 +700,8 @@ light + + Rec2020 YCbCr UHD (16-235,240)/255 "TV" levels
     C                @@ -622,6 +709,8 @@ light + + Rec2020 Constant Luminance YCbCr UHD (16-235,240)/255 "TV" levels

@@ -635,6 +724,8 @@ light + + with the addition of two extra options.

Possible arguments to the -k option are:
@@ -675,6 +766,8 @@ light + + _______ enle
                 |      @@ -684,6 +777,8 @@ light + + /
                 |     @@ -693,6 +788,8 @@ light + + /
                 |      @@ -702,6 +799,8 @@ light + + /
                 |      @@ -711,6 +810,8 @@ light + + /
           stle | ------/
@@ -726,6 +827,8 @@ White            &nb + + Black

-k q stle0 stpo0 enpo0 enle0 shape0 stle2 stpo2 -- cgit v1.2.3

Measurement Mode @@ -1073,20 +1398,29 @@ none,
Emission +	Emission	mW/(m².sr.nm)	mW/(m².sr.nm)
Ambient +	Ambient	mW/(m².nm) +	mW/(m².nm)
Emission Flash +	Emission Flash	mW/(m².sr.nm.s) +	mW/(m².sr.nm.s) + + + + + + + + + @@ -1097,21 +1431,21 @@ none,
Ambient Flash +	Ambient Flash	mW/(m².nm.s) +	mW/(m².nm.s)
Reflective +	Reflective	%/nm +	%/nm
Transmissive +	Transmissive	%/nm +	%/nm

The solution

Conclusion

Argyll CMS documentation index (V1.8.3) -

Introduction

ArgyllCMS documentation index (V1.9.1) +

Introduction

Operating Environments

Operating Environments

Copyright, Licensing & Trade Mark: +

What sort of project is this ? (re: + contributions) +

Graphic + User Interfaces +

Main + Tools and the command line +

Topical + Discussions

Flow + diagram of Major Tools:

Main Tools by + category:

Calibrating devices +

Creating test targets for profiling or print calibration +

Obtaining test results for profiling or print calibration +

Copyright, Licensing & Trade Mark: -

What sort of project is this ? (re: - contributions) -

Graphic - User Interfaces -

Main - Tools and the command line -

Creating Device Profiles

Topical - Discussions

Flow - diagram of Major Tools:

Main Tools by - category:

Calibrating devices -

Creating test targets for profiling or print calibration -

Creating Device Link Profiles

Obtaining test results for profiling or print calibration -

Converting colors or applying print calibration +

Color Tweaking tools +

Creating gamut views

Creating Device Profiles

Diagnostic and test tools +

Creating Device Link Profiles

Converting colors or applying print calibration -

Color Tweaking tools -

Creating gamut views

Other Tools

Diagnostic and test tools -

Main Tools + Alphabetic Listing:

Other Tools

Main Tools - Alphabetic Listing:

Errors, Corrections and Omissions:

Errors, Corrections and Omissions:

Summary of Argyll CMS Changes since last release

For a complete and more detailed list of changes, please see the log.txt file.

[V1.8.3 -> V1.9.1] 28th September 2016

[V1.8.2 -> V1.8.3] 26th October 2015

Setting an environment variable

Environment variables -

Environment variables

Installing the software on Microsoft Windows

Installing the software on Apple OS X -

X-Rite ColorMunki

Installing the software on Apple OS X +

X-Rite ColorMunki

X-Rite EyeOne Pro -

X-Rite EyeOne Pro +

JETI specbos @@ -248,68 +252,70 @@ specbos - 1201 and 1211 and Klein K10A -

HCFR Colorimeter

HCFR Colorimeter

- Performance Tuning

Performance Tuning

Creating Device Links and Profiles

Setting an environment variable:

Typical usage Scenarios and Examples

- Profiling Scanners and other input devices such as - cameras -

- Profiling Printers

Profiling Displays

Checking you can access your display -

Typical usage Scenarios and Examples

+ Profiling Scanners and other input devices such as + cameras +

+ Profiling Printers

Argyll CMS documentation index (V1.8.3)
-

ArgyllCMS documentation index (V1.9.1)
+

Copyright, Licensing & Trade Mark:
+

What sort of project is this ? (re: + contributions)
+

Graphic + User Interfaces
+

Main + Tools and the command line
+

Calibrating devices
+

Creating test targets for profiling or print calibration
+

Obtaining test results for profiling or print calibration
+

Copyright, Licensing & Trade Mark:
-

What sort of project is this ? (re: - contributions)
-

Graphic - User Interfaces
-

Main - Tools and the command line
-

Calibrating devices
-

Creating test targets for profiling or print calibration
-

Obtaining test results for profiling or print calibration
-

Converting colors or applying print calibration
+

Color Tweaking tools
+

Diagnostic and test tools
+

Converting colors or applying print calibration
-

Color Tweaking tools
-

Diagnostic and test tools
-

Environment variables
-

Installing the software on Apple OS X
-

Installing the software on Apple OS X
+

X-Rite EyeOne Pro
-

X-Rite EyeOne Pro
+

JETI specbos @@ -248,68 +252,70 @@ specbos - 1201 and 1211 and Klein K10A
-

- Profiling Scanners and other input devices such as - cameras
-

Checking you can access your display
-

+ Profiling Scanners and other input devices such as + cameras
+