Function	Mouse Button
Rotate	Left / Left + Shift
Pan	Mid / Left + Ctrl
Zoom	Right / Wheel / Left + Alt
Set center of rotation	Double-click left

Function	Key
Reset view	r
Show all	a
Upright	u

There is now partial support for the - Eye-One Pro Rev E (aka Eye-One Pro 2) instrument, but a Rev E can - be operated in legacy mode if the environment variable +

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

- XDG_CACHE_HOME
+ XDG_CACHE_HOME

Argyll tries to follow the XDG - Base Directory Specification, and uses the , and uses the XDG_CACHE_HOME environment - variable to place per instrument calibration information (Eye-One - Pro and ColorMunki instruments).
+ variable to place per instrument calibration information, and + .ccmx and .ccss files.

- XDG_CONFIG_DIRS
- XDG_DATA_DIRS
+ XDG_CONFIG_DIRS
+ XDG_DATA_DIRS

On Unix type operating systems, configuration and profiles for displays are placed relative to these environment variables.

-
-
+

See Performance Tuning for other variables.
diff --git a/doc/FWA.html b/doc/FWA.html index c1d4c6d..c6b1f4b 100644 --- a/doc/FWA.html +++ b/doc/FWA.html @@ -3,7 +3,7 @@ Fluorescent Whitener Additive Compensation + charset=windows-1252">

Fluorescent Whitener Additive Compensation (FWA Compensation)

@@ -179,13 +179,13 @@ specifying the same illuminant, and (optionally) the same observer model.

- In practice it is possible to compensate for the color shift that + [ In practice it is possible to compensate for the color shift that results in viewing the media under non-D50 illumination or using a non 1931_2 observer, or allowing for FWA effects without severe incompatibility because all rendering intents except absolute rendering normalize to the media color, rendering the media white as white, even though the absolute values are not measured using a D50 - illuminant.
+ illuminant. ]

Using FWA compensation for single, general use profiles

For creating ICC profiles that will be interchanged with other unknown ICC profiles, or used with non-print source or destination diff --git a/doc/File_Formats.html b/doc/File_Formats.html index aa0f4f4..1741701 100644 --- a/doc/File_Formats.html +++ b/doc/File_Formats.html @@ -25,6 +25,8 @@ MPP
TIFF
VRML
+ X3D
+ X3DOM

.ti1

Target Information 1 data. This is an ASCII text, CGATS, @@ -176,7 +178,29 @@ these can be viewed with a suitable standalone VRML viewer, or a plug in for a web browser. VRML97 is International Standard ISO/IEC 14772-1:1997. See http://www.vrml.org/ - for more information.
+ for more information. See 3D Viewing Format + for switching to VRML output format.
+
+

X3D

+ X3D is a royalty-free ISO standard XML-based file format for + representing 3D computer graphics. It is successor to the Virtual + Reality Modeling Language (VRML). See http://www.web3d.org/ for more + information. See 3D Viewing Format for + switching X3D output format.
+
+

X3DOM

+ X3DOM is an open-source framework and runtime for 3D graphics on the + Web. It can be freely used for non-commercial and commercial + purposes, and is dual-licensed under MIT and GPL license. The + javascript runtime displays embeded X3D files in browsers that + support WebGL.
+ See http://www.x3dom.org/ for + more information about this format.
+ To check if your browser supports X3DOM, try this test page.
+ For more information about ArgyllCMS use of it, see 3D Viewing Format.

diff --git a/doc/Installing.html b/doc/Installing.html index a759044..79d8ade 100644 --- a/doc/Installing.html +++ b/doc/Installing.html @@ -2,22 +2,20 @@ + charset=windows-1252"> + charset=windows-1252"> Argyll Installation -

- Installing the software

Installing the software

Argyll doesn't come with any installation programs or scripts, so installation is a manual process. Because things are mostly self-contained, this isn't particularly onerous. In general the - steps - are:
+ steps are:

1) Provide somewhere for the executables to reside
2) Provide a means of the shell finding the executables
@@ -28,22 +26,19 @@ system:

Microsoft + Windows
Apple OS X
Linux/UNIX X11

- If you have a Spyder 2, Spyder 4, Xrite i1 DisplayPro or + If you have a Spyder 2, Spyder 4 or 5, Xrite i1 DisplayPro or ColorMunki Display colorimeter, please also see oeminst.

- -
- -
- -
- -

+
+
+
+

diff --git a/doc/Installing_Linux.html b/doc/Installing_Linux.html index 608ff7d..a26d64c 100644 --- a/doc/Installing_Linux.html +++ b/doc/Installing_Linux.html @@ -2,9 +2,9 @@ + charset=windows-1252"> + charset=windows-1252"> Argyll Installation on Linux @@ -46,6 +46,11 @@ + + + + + the /etc/rc.local startup script. You may also have to run xset @@ -53,6 +58,11 @@ + + + + + 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.
@@ -172,45 +182,88 @@ probably need to disable libmtp (look in the udev configuration).

The JETI specbos 1211 and 1201 makes use of - the FTDI Virtual - COM Port Drivers (VCP), that should come with any recent - version of Linux.
+ style="font-weight: bold;"> and 1201, 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.

No device configuration needed:

- Some systems have in place a security configuration such that + A few systems have in place a security configuration such that anyone logging in at the console of a machine has access to all the local devices.

USB - instruments access using udev:
+ instruments access using udev with existing /etc/udev/rules.d or + /usr/lib/udev/rules.d/69-cd-sensors.rules + file.

- Most recent systems - use udev to manage device names and permissions, but by default - color instruments may not be accessible to normal system users.
+ Recent Fedora based + systems include Gnome Color Manager, which comes with a udev rule + for color instruments. You can check this by looking for the /etc/udev/rules.d or in /usr/lib/udev/rules.d/69-cd-sensors.rules + file. If this exists and is up to date enough to include the + instrument you want to use, then all you have to do is add yourself + to the colord group, ie:
+
+ sudo usermod -a -G colord $USER
+
+ If the 69-cd-sensors.rules file is out of date and does not + include the latest instruments supported by Argyll, then the + simplest thing to do is to replace the 69-cd-sensors.rules + file with the usb/55-Argyll.rules. You will need + to do this as root, and set the owner as root, group root, + permissions 644. You may need to re-plug in your instrument to get + changes to the udev rules recognised.
+

USB + instruments access using udev, with no existing /etc/udev/rules.d or /usr/lib/udev/rules.d/69-cd-sensors.rules + file.
+

+ Most recent systems use udev to manage device names and permissions, + but by default color instruments may not be accessible to normal + system users.
To solve this a udev rule file needs to be added that modifies the group and permission of any Color Measurement Instruments, and you may then need to add yourself to that group.

+ First check whether other rules are in /etc/udev/rules.d or in /usr/lib/udev/rules.d, + and use the appropriate directory.
+ (You may also want to check in that directory whether + 55-Argyll.rules or some other .rules file that is setup to enable + color instruments already exists in that directory.)
+
Copy the file usb/55-Argyll.rules from the binary or source distribution into /etc/udev/rules.d/55-Argyll.rules - with owner root, group root, permissions 644.
- (There may already be a file that handles some of the color - instruments as part of your installation. You need to check though - that it is up to date.)
+ or /usr/lib/udev/rules.d/55-Argyll.rules + + + + (as appropriate) with owner root, group root, + permissions 644.

If you are on an older system that uses a udev that doesn't recognize the syntax used in 55-Argyll.rules, or that doesn't have rules to create the libusb /dev/bus/usb/00X/00Y device entries, you should install the usb/45-Argyll.rules file - instead.
+ style="font-weight: bold;">usb/45-Argyll.rules file instead + - See below.

On recent systems the new rules file will be notices as soon as you plug the instrument in again.
@@ -221,128 +274,15 @@ + + + + + /sbin/udevcontrol reload_rules or /sbin/udevstart or reboot to get the new file noticed.

- ----------------- cut here ---------------------
- # udev rule to recognize instruments and make them accessible to - user applications.
- # Copy this to /etc/udev/rules.d/55-Argyll.rules
-
- # Skip all this to speed things up if it'a not a usb add.
- ACTION!="add", GOTO="argyll_rules_end"
- SUBSYSTEM!="usb", GOTO="argyll_rules_end"
-
- # Recognize the color measurement devices
-
- # Colorimtre HCFR
- ATTRS{idVendor}=="04db", ATTRS{idProduct}=="005b", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # MonacoOPTIX (Same as i1 Display 1)
- ATTRS{idVendor}=="0670", ATTRS{idProduct}=="0001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # HueyL (not tested)
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # HueyL (not tested)
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5010", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # i1Display 3
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5020", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # ColorMunki Smile
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="6003", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # DTP20
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d020", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # DTP92Q (not tested)
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d092", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # DTP94
- ATTRS{idVendor}=="0765", ATTRS{idProduct}=="d094", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # i1Pro
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2000", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # i1Monitor
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # i1Display
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2003", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # i1 io table (not tested)
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2004", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # Huey
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2005", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # i1 iSis (not tested)
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2006", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # ColorMunki
- ATTRS{idVendor}=="0971", ATTRS{idProduct}=="2007", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # Spyder 1
- ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0100", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # Spyder 2
- ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0200", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # Spyder 3
- ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0300", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
- # Spyder 4
- ATTRS{idVendor}=="085c", ATTRS{idProduct}=="0400", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # ColorHug, old and new
- ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="f8da", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
- ATTRS{idVendor}=="273f", ATTRS{idProduct}=="1001", - ENV{COLOR_MEASUREMENT_DEVICE}="1"
-
-
- # Let udev-acl manage these devices, if it's available
- TEST=="/var/run/ConsoleKit/database", - ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1"
-
- # Otherwise, restrict access to members of the plugdev group,
- # which the user may have to add to the system.
- ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}!="*?", - MODE="660", GROUP="plugdev"
-
- # Set ID_VENDOR and ID_MODEL acording to VID and PID
- IMPORT{program}="usb-db %p"
-
- LABEL="argyll_rules_end"
- ----------------- cut here ---------------------
-
(You may want to refer to this document for more guidance on modifying udev rules, as well as @@ -352,50 +292,48 @@ href="http://www.google.com/search?hl=en&q=man+udev&btnG=Search&meta YOU THEN MAY NEED TO:

If your system is not using - the new ACL to manage device access for console users (the file /lib/udev/udev-acl doesn't exist - on your system), then you will need to add yourself to the plugdev group, if you are not - already a member of it. You can do this either by using a "Users and - Groups" system administration tool, or on the command line running - as root:
+ the ACL to manage device access for console users (the file /var/run/ConsoleKit/database + doesn't exist on your system), then you will need to add yourself to + the colord group, if you + are not already a member of it. You can do this either by using a + "Users and Groups" system administration tool, or on the command + line running as root:

-    sudo usermod -a -G plugdev yourusernamehere
+    sudo usermod -a -G colord $USER

or
    su root
-     usermod -a -G plugdev yourusernamehere
+     usermod -a -G colord $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 - plugdev yourusernamehere".
+ colord $USER".
If this doesn't work you will have to run "id yourusername" to list the current supplemental
- groups, and add them plus plugdev using just "usermod -G + groups, and add them plus colord using just "usermod -G group1,group2,... yourusername")

- You may find that the plugdev - group doesn't exist on your system, and if so you will need to - create it:
+ You may find that the colord group doesn't exist on + your system, and if so you will need to create it:

- sudo groupadd -r plugdev
+ sudo groupadd -r colord

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

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

You can check whether the instrument is being recognized and set to - the plugdev group by comparing the output of ls -l -R /dev/bus/usb without and then with the instrument plugged in.

You can test whether your instrument is accessible by plugging it in and then running "spotread -?" and looking for it listed after the -c option.
-

USB instruments @@ -404,6 +342,11 @@ instruments + + + + + access using hotplug:

Under much older versions of Linux, @@ -419,78 +362,6 @@ instruments with owner root, group root, permissions 644.

-     ----------------- cut here ---------------------
- # hotplug device mapping to handling script.
- # Copy this to /etc/hotplug/usb/Argyll.usermap
- #
- # Detect instruments by their USB VID and PID
- #
- # DTP20
- Argyll 0x0003 0x0765 0xd020 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # DTP92Q - not tested
- Argyll 0x0003 0x0765 0xd092 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # DTP94
- Argyll 0x0003 0x0765 0xd094 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # MonacoOPTIX (Same as i1 Display 1)
- Argyll 0x0003 0x0670 0x0001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # i1 Display
- Argyll 0x0003 0x0971 0x2003 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # i1 Display 3
- Argyll 0x0003 0x0765 0x5020 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # i1 Monitor
- Argyll 0x0003 0x0971 0x2001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # i1 Pro
- Argyll 0x0003 0x0971 0x2000 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # ColorMunki
- Argyll 0x0003 0x0971 0x2007 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # ColorMunki Smile
- Argyll 0x0003 0x0765 0x6003 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # Colorimtre HCFR
- Argyll 0x0003 0x04DB 0x005B 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # Spyder 2
- Argyll 0x0003 0x085C 0x0200 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # Spyder 3
- Argyll 0x0003 0x085C 0x0300 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # Spyder 4
- Argyll 0x0003 0x085C 0x0400 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # Huey
- Argyll 0x0003 0x0971 0x2005 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- #
- # ColorHug
- Argyll 0x0003 0x04D8 0xF8DA 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
- Argyll 0x0003 0x273F 0x1001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 - 0x00 0x00000000
-     ----------------- cut here ---------------------

(For even older versions, append the lines above to /etc/hotplug/usb.usermap, and @@ -502,49 +373,37 @@ instruments with owner root, group root, permissions 744.

-     ----------------- cut here ---------------------
- #!/bin/sh
- # Copy to /etc/hotplug/usb/Argyll
- #
- # Argyll hotplug script. Adds the USB devices to the plugdev group.
- if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
- then
-     chgrp plugdev "${DEVICE}"
-     chmod 660 "${DEVICE}"
- fi
-     ----------------- cut here ---------------------
-
YOU THEN NEED TO:

You will then need to add - yourself to the plugdev + yourself to the colord group, if you are not already a member of it. You can do this either by using a "Users and Groups" system administration tool, or on the command line running as root:

-    sudo usermod -a -G plugdev yourusernamehere
+    sudo usermod -a -G colord $USER

or
    su root
-     usermod -a -G plugdev yourusernamehere
+     usermod -a -G colord $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 - plugdev yourusernamehere".
+ colord $USER".
If this doesn't work you will have to run "id yourusername" to list the current suplemental
- groups, and add plugdev using just "usermod -G + groups, and add colord using just "usermod -G group1,group2,... yourusername")

- You may find that the plugdev + You may find that the colord group doesn't exist on your system, and if so you will need to create it:

- sudo groupadd -r plugdev
+ sudo groupadd -r colord

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

You may have to log out and then in again for the groups to become effecive.
@@ -561,6 +420,11 @@ instruments + + + + + access:
If you have a serial instrument then you may find that by default @@ -573,16 +437,16 @@ instruments administration tool, or on the command line using "usermod":

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

or

-    sudo usermod -a -G tty,uucp yourusernamehere
+    sudo usermod -a -G tty,uucp $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 - plugdev yourusernamehere".
+ colord $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 diff --git a/doc/Installing_MSWindows.html b/doc/Installing_MSWindows.html index c08e16d..40dcd2c 100644 --- a/doc/Installing_MSWindows.html +++ b/doc/Installing_MSWindows.html @@ -31,7 +31,8 @@ You should also configure your %PATH% environment variable to give access to the executables from your command line environment.

- For Windows 8, look in
+ For Windows 8 & 8.1, + look in
    Desktop -> Settings -> Control Panel -> System And Security -> System -> Advanced System Settings -> Environment Variables
@@ -60,9 +61,9 @@
So if the current value of PATH is "%SystemRoot%\system32;%SystemRoot%" and you unpacked Argyll version - 1.6.3 in d:\bin\, then you + 1.7.0 in d:\bin\, then you would modify PATH to be - "%SystemRoot%\system32;%SystemRoot%;d:\bin\Argyll_V1.6.3\bin", - + "%SystemRoot%\system32;%SystemRoot%;d:\bin\Argyll_V1.7.0\bin", - i.e. you append the path to the Argyll binaries to your PATH, separated by the ';' character. The change will take effect when you start a new command shell, which you start from Start @@ -77,14 +78,14 @@ doc sub-directory, and instrument USB drivers in the usb directory.

NOTE: Vista 64/Windows 7 & 8 64 bit - and Beep prompt: Microsoft (in its infinite - wisdom) has removed the built in speaker driver, and now relies on - systems having a sound card and speakers's installed and turned on - to hear system beeps. So if you're wondering where the beeps have - gone when using chartread, now you - know.
+ style="font-weight: bold;">Vista 64/Windows 7, 8 & 8.1 + 64 bit and Beep + prompt: Microsoft (in its + infinite wisdom) has removed the built in speaker driver, and now + relies on systems having a sound card and speakers's installed and + turned on to hear system beeps. So if you're wondering where the + beeps have gone when using chartread, + now you know.

NOTE: Microsofts generic VGA Driver does not appear to support setting the display VideoLUTs. You will @@ -134,7 +135,7 @@
If you are using the JETI specbos 1211 or 1201, - then you may need to install the Klein K10A then you may need to install the FTDI Virtual COM Port Drivers (VCP), if they are not already on your system.

@@ -147,7 +148,8 @@ Windows 2000

Windows 8
+ size="+1">Windows 8 & 8.1

To install the Argyll driver for the first instrument:
-     (Plug in instrument)
+     Settings -> Power -> Hold Shift Key down and click + "Restart" -> Troubleshoot -> Advanced Options -> Startup + Settings -> Restart ->
+     (After Reboot) -> "Disable Driver Signature + Enforcement" (number 7 on the list)
+     (After system starts, Plug in instrument)
    Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager ->
    Other Devices -> <instrument being @@ -191,7 +199,13 @@
To install the Argyll Driver:
-     (Plug in instrument)
+     Settings -> Power -> Hold Shift Key down and click + "Restart" -> Troubleshoot -> Advanced Options -> Startup + Settings -> Restart ->
+     (After Reboot) -> Disable Driver Signature + Enforcement" (number 7 on the list)
+     (After system starts, Plug in instrument)
    Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager
    (Locate the instrument in the device list. It may diff --git a/doc/Installing_OSX.html b/doc/Installing_OSX.html index 8a17291..fb01e4a 100644 --- a/doc/Installing_OSX.html +++ b/doc/Installing_OSX.html @@ -1,313 +1,354 @@ - - - - - - - Argyll Installation on Apple OS X - - -

Installing the software on Apple OS X
-

-
- You will need to unpack the downloaded file in the location you have - chosen to hold the executable files. Typically this might be in /usr/bin, or perhaps $HOME/bin/, or even $HOME.
-
- You can unpack it by control-click on the downloaded file and “Open - With” BOMArchiveHelper or Archive Utility. Drag the resulting folder - to where you want it, e.g. into your home folder (/Users/usrnam - where usrnam is your username).
-
- Alternatively you can unpack it on the command line using the - command tar -zxf archivename.tgz, which will - create a directory Argyll_VX.X.X, - where X.X.X is the version number, and the executables will be in Argyll_VX.X.X/bin.
-
- 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 will have to configure your $PATH environment variable to give - access to the executable from your command line environment, by - editing your .profile file. - You can do this using a graphical editor, by using the open command:
-
- ~$open .profile
-
- or by using some other editor, such as vi.
-
- And add a line similar to the following line to your .path file
-
- PATH=$PATH:$HOME/Argyll_VX.X.X/bin
-
- where "$HOME/Argyll_VX.X.X/bin" is the path to the executable - directory.
-
- If you are unfamiliar with how to do this, 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-directory, as well as all - the current documentation in a doc sub-directory.
-
- 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 incovenient.
-
- 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                    - Value           -
-     UserName + + + + + + + Value           +
+     UserName                   string                   - 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                    - Value           -
-     UserName + + + + + + + Value           +
+     UserName                   string                   - 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 - 1201 and 1211
-

-
- If you are using the JETI specbos 1211 and 1201, - 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 directory 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 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>
             - <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/K10A.jpg b/doc/K10A.jpg new file mode 100644 index 0000000..1a93349 Binary files /dev/null and b/doc/K10A.jpg differ diff --git a/doc/Scenarios.html b/doc/Scenarios.html index e82a8a4..7b5899f 100644 --- a/doc/Scenarios.html +++ b/doc/Scenarios.html @@ -75,6 +75,11 @@ handled when calibration is being used

Linking Profiles

Image dependent gamut + mapping using device links
+

Soft Proofing Link
+

Transforming colorspaces of raster files

Creating Video Calibration 3DLuts

@@ -152,6 +157,17 @@ + + + + + + + + + + + @@ -219,6 +235,17 @@ + + + + + + + + + + + @@ -590,6 +617,17 @@ + + + + + + + + + + + @@ -649,6 +687,17 @@ + + + + + + + + + + + @@ -806,6 +855,17 @@ + + + + + + + + + + + @@ -873,37 +933,6 @@ - - - - HCT :
-
- HutchColor HCT

-
-
- and Christophe - - - - - - - - - - - - - - - - - - - - @@ -917,6 +946,24 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm + + HCT :
+
+ HutchColor HCT

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

+
+ and the LaserSoft @@ -928,9 +975,6 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm - - Métairie's Digital TargeT 003 and Christophe @@ -976,35 +1020,20 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm - Métairie's Digital Target - 3 :
+ Imaging DCPro Target:

- CMP_DT_003

- and the LaserSoft - - - - - - - - - - - - - - - - - - - - - - + The Datacolor SpyderCheckr:
+
+ Datacolor
+ SpyderCheckr

+
+ One of the QPcard's:
+ QPcard @@ -1027,21 +1056,6 @@ href="http://www.christophe-metairie-photographie.com/eng%20digital%20target.htm - - Imaging DCPro Target:
-
- LaserSoft DCPro
- Target

-
- The Datacolor SpyderCheckr:
-
- Datacolor
- SpyderCheckr

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

Even though the profiling process is carried out on top of the @@ -2808,6 +2938,11 @@ a 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, @@ -2848,6 +2983,53 @@ a 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* + or ProPhoto, etc.), then using the colorspace gamut as the source + gamut for gamut mapping is generally a bad idea, as it leads to + overly compressed and dull images. The correct approach is to use a + source gamut that represents the gamut of the images themselves. + This can be created using tiffgamut, and an example workflow is as + follows:
+
+ 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.
+
+ 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 @@ -2872,6 +3054,11 @@ a the viewing conditions and assumes adaptation to the differences in the luminence range, but otherwise not attempting to compress or change the gamut.
+
+ 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

@@ -2938,16 +3125,31 @@ a Argyll's normal test patch display will be used by default, as long as any video encoding range considerations are dealt with (see - Signal encoding below). An alternative when working with MadVR V - 0.86.9 or latter, is to use the madTPG to display the patches in - which case the MadVR video encoding range setting will operate. This - can give some quality benefits due to MadVR's use of dithering. To - display patches using MadVR rather than Argyll, start madTPG and - then use the option "-d madvr" in dispcal, dispread and dispwin. - Leave the MadTPG "VideoLUT" and "3dluts" buttons in their - default (enabled) state, as the various tools will - automatically take care of disabling the 3dLut and/or calibration - curves as needed.
+ Signal encoding below).
+
+ An alternative when working with MadVR V 0.86.9 or latter, is to use + the madTPG to display the patches in which case the MadVR video + encoding range setting will operate. This can give some quality + benefits due to MadVR's use of dithering. To display patches using + MadVR rather than Argyll, start madTPG and then use the option "-d + + + + madvr" in dispcal, dispread and dispwin. Leave the MadTPG + "VideoLUT" and "3dluts" buttons in their default (enabled) + state, as the various tools will automatically take care of + disabling the 3dLut and/or calibration curves as needed.
+
+ 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 @@ -2982,6 +3184,17 @@ a package could be used, or ArgyllCMS dispcal's + + + + + + + + + + + interactive adjustment mode can be used to set the white point. Note that while adjusting the neutral axis for neutrality may @@ -3004,7 +3217,18 @@ a and 3dLut will set the final response. If this approach is taken, then the resulting calibration file should be provided to dispread as the -k parameter or -K parameter. See also below Choice + href="dispcal.html#K">-K parameter. See also below Choice + + + + + + + + + + + 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 @@ -3087,8 +3311,12 @@ a scale full range RGB values to Video levels for the TV. If the latter is not possible, then use the -E options on dispcal and dispread. (See Signal encoding bellow for more details on - this). Don't use the -E options on dispcal and dispread if you are - using MadVR to display test patches using the "-d madvr" option.
+ 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 @@ -3206,9 +3434,9 @@ a near black will get clipped to the display black point, loosing shadow detail. To avoid this, some sort of black point mapping is usually desirable. There are two mechanisms available in collink: - a) BT.1886 black point mapping, or b) using one of the smart gamut - mapping intents that does black point mapping (e.g. la, p, pa, ms - or s).
+ 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

@@ -3223,30 +3451,56 @@ a practice that much video material is adjusted to look as intended when displayed on a reference monitor having a display gamma of somewhere between 2.2 and 2.4, viewed in a dim viewing - environment. The modern standard covering the display transfer - curve is BT.1886, - which defines a pure power 2.4 curve with a black point offset. So - another means of making the viewing adjustment is to apply the - BT.1886-like response to Rec709 encoded material. Collink supports - this using the -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.
+ 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 rendered to a model BT.1886 display in dim - viewing conditions, and then CIECAM02 is used to adjust for the - actual display viewing conditions. Once again, control over the - degree of viewing conditions adjustment is possible by varying the - viewing condition parameters.
+ 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:
@@ -3282,7 +3536,7 @@ a
The display can then be measured:

- dispread -v -k TV.cal TV
+ dispread -v -k -Z8 TV.cal TV

or using madTPG:

@@ -3312,14 +3566,14 @@ a BT.1886 black point and viewing conditions adjustment, say one of the following:

- collink -v -Ib:2.4 -G -ir Rec709.icm TV.icm + collink -v -Ib:2.4 -b -G -ir Rec709.icm TV.icm HD.icm   # dark conditions - collink -v -Ib     -G -ir + collink -v -Ib     -b -G -ir Rec709.icm TV.icm HD.icm   # dim conditions - good default - collink -v -Ib:2.1 -G -ir Rec709.icm TV.icm + collink -v -Ib:2.1 -b -G -ir Rec709.icm TV.icm HD.icm   # mid to dim conditions - collink -v -Ib:2.0 -G -ir Rec709.icm TV.icm + 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 @@ -3400,7 +3654,7 @@ a For PC use, where the encoding is full range RGB: - collink -v -3e -Ib -G -ir -a TV.cal Rec709.icm TV.icm + 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 @@ -3416,8 +3670,8 @@ a 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 -G -ir -a TV.cal Rec709.icm - TV.icm HD.icm + 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 @@ -3441,10 +3695,21 @@ a normal desktop and MadVR, then it is recommended that you install the display ICC profile and use the -H option: -     collink -v -3m -et -Et -Ib -G -ir -H TV.cal - Rec709.icm TV.icm HD.icm +     collink -v -3m -et -Et -Ib -b -G -ir -H + TV.cal Rec709.icm TV.icm HD.icm -     collink -v -3m -et -Et -Ib -G -ir -H +     collink -v -3m -et -Et -Ib -b -G -ir -H + + + + + + + + + + + @@ -3458,7 +3723,18 @@ a TV.cal EBU3213_PAL.icm TV.icm SD_PAL.icm -     collink -v -3m -et -Et -Ib -G -ir -H +     collink -v -3m -et -Et -Ib -b -G -ir -H + + + + + + + + + + + @@ -3476,10 +3752,21 @@ a curves using dithering, and allow it to set the graphics card to linear by using the -a option: -     collink -v -3m -et -Et -Ib -G -ir -a TV.cal - Rec709.icm TV.icm HD.icm +     collink -v -3m -et -Et -Ib -b -G -ir -a + TV.cal Rec709.icm TV.icm HD.icm -     collink -v -3m -et -Et -Ib -G -ir -a +     collink -v -3m -et -Et -Ib -b -G -ir -a + + + + + + + + + + + @@ -3493,7 +3780,18 @@ a TV.cal EBU3213_PAL.icm TV.icm SD_PAL.icm -     collink -v -3m -et -Et -Ib -G -ir -a +     collink -v -3m -et -Et -Ib -b -G -ir -a + + + + + + + + + + + @@ -3544,11 +3842,12 @@ a 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 a - VRML 3d visualization of the point set using the -W flag. It is - good to take a look at the verifyd.wrl file using a VRML viewer. - You may want to create several test sets that look at particular - aspects, ie. neutral axis response, pure colorant responses, etc. + 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 @@ -3556,12 +3855,12 @@ a would: copy verify.ti1 ref.ti1 - fakeread -v -b TV.icm Rec709.icm ref + 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:2.15" then the equivalent fakeread option - "-b 2.15:TV.icm" should be used, etc. + 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 @@ -3569,12 +3868,13 @@ a simulating the reproduction of this test set: copy verify.ti1 checkA.ti1 - fakeread -v -et -p HD.icm -Et TV.icm checkA + 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 -p HD.icm -Et -K TV.cal TV.icm checkA + 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 @@ -3590,10 +3890,10 @@ a verify -v -N -w -x ref.ti3 checkA.ti3 This will give a numerical report of the delta E's, and also - generate a VRML plot of the errors in L*a*b* space. The important - thing is to take a look at the checkA.wrl file, to see if gamut - clipping is occurring - this is the case if the large error - vectors are on the sides or top of the gamut. Note that the + generate an X3DOM plot of the errors in L*a*b* space. The + important thing is to take a look at the checkA.x3d.html file, to + see if gamut clipping is occurring - this is the case if the large + error vectors are on the sides or top of the gamut. Note that the perfect cube device space values become a rather distorted cube like shape in the perceptual L*a*b* space. If the vectors are small in the bulk of the space, then this indicates that the link @@ -3612,22 +3912,23 @@ a iccgamut -ff -ia Rec709 iccgamut -ff -ia TV.icm - viewgam -i Rec709.gam TV.gam gamuts.wrl + viewgam -i Rec709.gam TV.gam gamuts - and look at the gamuts.wrl file, as well as taking notice of % of - the video volume that the display intersects. The VRML solid + 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 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: + 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 checkB + 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 diff --git a/doc/VideoEOTFs.html b/doc/VideoEOTFs.html new file mode 100644 index 0000000..526477c --- /dev/null +++ b/doc/VideoEOTFs.html @@ -0,0 +1,47 @@ + + + + Video Electro Optical Transfer Functions + + + + Video Electro-Optical Transfer Functions + + Introduction + hgskajghjsahgjhgas + + Encoding verses decoding & Viewing conditions + + kjshkjhsakdhakj + + Log-Log plots + jhjkhkjhkjhkh + + perceptual errors - DE2000 1 DE lines plotted on a log-log + graph + "Pure Gamma" curves + + They don't exist, unless your display has a perfect, zero black. But + even if it does have a perfect black, the black as seen by your eye + won't be perfect unless you are in a pitch black room and the + display is all black, because any stray light in the room or from + other non-black elements on the display will dilute the perfect + black due to glare. + + ksjdhiksahdkajsl + + Output Offset Black + Input Offset Black + + sdjhkashdkjas + + BT.1886 + + hjsdjhgsajgda + + + + + + diff --git a/doc/afiles b/doc/afiles index e58ab5a..db6632f 100644 --- a/doc/afiles +++ b/doc/afiles @@ -22,6 +22,7 @@ Environment.html Scenarios.html FWA.html FWA_measure.jpg +VideoEOTFs.html instruments.html ArgyllFlow.jpg ArgyllFlowThumb.jpg @@ -53,13 +54,16 @@ Chroma4.jpg ColorMunki.jpg ColorMunkiCreate.jpg i1pro2.jpg +K10A.jpg iccgamutmapping.html +3dformat.html gamutmapping1.jpg monitorcontrols.html gamma.html calvschar.html WideGamutColmters.html CrushedDisplyBlacks.html +ArgyllCMS_arts_tag.html i1proDriver.html i1proDriver.xls i1proHiRes.html @@ -136,7 +140,7 @@ SG_footer.txt i1scan14.jpg HCT.jpg CMP_DT_003.jpg -CMP_Digital_Target-3.jpg +CMP_Digital_Target-4.jpg colorchecker.jpg SpyderChecker.jpg LSDC.jpg diff --git a/doc/average.html b/doc/average.html index 31adf9b..231df92 100644 --- a/doc/average.html +++ b/doc/average.html @@ -1,43 +1,53 @@ - + - - average - - - - -spectro/average -Summary -Average or merge two or more .ti3 -measurement -files. -Usage - -usage: average [-options] input1.ti3 -input2.ti3 ... output.ti3 - -v              -Verbose - -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. - -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. - - + + average + + + + + spectro/average + Summary + Average or merge two or more .ti3 + measurement + files. + If only one input file is provided, all the patches with the same + device values will be average together. + Usage + + usage: average [-options] + input1.ti3 + input2.ti3 ... output.ti3 + -v              + Verbose + -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. + + 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. + + diff --git a/doc/ccxxmake.html b/doc/ccxxmake.html index 8ef31b7..f83afc8 100644 --- a/doc/ccxxmake.html +++ b/doc/ccxxmake.html @@ -3,7 +3,7 @@ ccxxmake + charset=windows-1252"> @@ -41,8 +41,7 @@ subsequent measurements on that Display using such Colorimeters, by using it with the dispcal, dispread and spotread - -X option, or it can be installed, and + -X option, or it can be installed, and will then appear in the available display type selection (-y option). @@ -53,7 +52,7 @@ style="font-weight: bold;">ccmx (Colorimeter Correction Matrix) files. Usage Summary - ccxxmake [-options] + ccxxmake -t dtech [-options] correction.ccmx -v              @@ -71,6 +70,9 @@ + + + Verbose mode -S                                         Create @@ -91,6 +93,9 @@ rather + + + than CCMX -f file1.ti3[,file2.ti3]                @@ -114,6 +119,9 @@ two + + + .ti3 files rather than measure. -display @@ -132,6 +140,9 @@ two + + + displayname [X11 only] Choose X11 display name -d @@ -180,6 +194,9 @@ m + + + n                  Choose the @@ -203,6 +220,9 @@ list + + + (default 1) -dweb[:port]          @@ -222,6 +242,9 @@ list + + + Display via a web server at port (default 8080) @@ -236,31 +259,23 @@ list - [MSWin] Display via MadVR Video Renderer - -p                    - - - - + [MSWin] Display via MadVR Video Renderer + -dcc[:n]              + Display via n'th ChromeCast (default 1, ? for list) + -p                    - Use telephoto mode (ie. for a projector) (if available) - -y X -                - @@ -273,13 +288,14 @@ list + Use telephoto mode (ie. for a projector) (if available) + -y X +                + - Display type - instrument specific list to choose from. (CCMX) - -P @@ -295,8 +311,13 @@ list - ho,vo,ss[,vs]      Position test - window and scale it + Display type - instrument specific list to choose from. + (CCMX) + -z disptype           + Different display type for spectrometer (see -y) + -P ho,vo,ss[,vs]      + Position test window and scale it                        ho,vi: 0.0 @@ -320,6 +341,9 @@ center, + + + 1.0 = right/bottom etc.                        ss: @@ -344,6 +368,9 @@ normal, + + + 2.0 = double etc.                        @@ -355,6 +382,9 @@ normal, + + + ss,vs: = optional horizontal, vertical scale. -N                    @@ -420,6 +456,9 @@ on + + + Disable initial calibration of instrument if possible @@ -459,6 +501,9 @@ on + + + "command"          Invoke shell "command" each time a color is set -o @@ -491,6 +536,9 @@ sequence + + + combination steps (default 3) -W @@ -509,6 +557,9 @@ sequence + + + n|h|x              Override serial @@ -532,6 +583,9 @@ n + + + none, h = HW, x = Xon/Xoff -D [level] @@ -558,31 +612,226 @@ overall - escription + + + + description -I "displayname"      Set display make and model - description - -T + description + (optional) + -t + + + dtech +              + Set display technology type + + c                   + + + CRT +     + m                   + + + Plasma +     + l                   + + + LCD +     + 1                   + + + LCD CCFL +     + 2               + + +     LCD + CCFL IPS +     + 3               + + +     LCD + CCFL VPA +     + 4               + + +     LCD + CCFL TFT +     + L               + + +     LCD + CCFL Wide Gamut +     + 5               + + +     LCD + CCFL Wide Gamut IPS +     + 6               + + +     LCD + CCFL Wide Gamut VPA +     + 7               + + +     LCD + CCFL Wide Gamut TFT +     + e               + + +     LCD + White LED +     + 8               + + +     LCD + White LED IPS +     + 9               + + +     LCD + White LED VPA +     + a               + +     LCD + White LED TFT +     + b               +     LCD + RGB LED +     + b               +     LCD + RGB LED IPS +     + c               +     LCD + RGB LED VPA +     + d               +     LCD + RGB LED TFT +     + h               +     LCD + RG Phosphor +     + e               +     LCD + RG Phosphor IPS +     + f               + + +     LCD + RG Phosphor VPA +     + g               + + +     LCD + RG Phosphor TFT +     + o               + + +     LED + OLED +     + a               + + +     LED + AMOLED +     + p               + + +     DLP + Projector +     + h               + + +     DLP + Projector RGB Filter Wheel +     + i               + + +     DPL + Projector RGBW Filter Wheel +     + j               + + +     DLP + Projector RGBCMY Filter Wheel +     + u               + + +     Unknown + -U c                  + - "displaytech"      Set display technology description - (ie. CRT, LCD etc.) - -U c                  @@ -601,9 +850,15 @@ overall + + +      Override refresh, non-refresh display mode -Y R:rate             + + + Override measured refresh rate with rate Hz -YA . Some experimentation may be needed using dispwin on such systems, to discover what screen has access to the VideoLUT hardware, and which screens the @@ -726,7 +984,9 @@ overall URL will be printed once the server is started, or you could run ipconfig (MSWin) or /sbin/ifconfig (Linux or OS X) - and identify an internet address for your machine that way. + and identify an internet address for your machine that way. You may + have to modify any firewall to permit port 8080 to be accessed on + your machine. -dmadvr [MSWin only] causes test patches to be displayed using the MadVR @@ -735,6 +995,14 @@ overall rendering does not need or support VideoLUT access. Test patch colors will be processed by the MadVR 3dLut. + -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. 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. + The -p flag allows measuring in telephoto mode, using instruments that support this mode, e.g. the ColorMunki. Telephoto mode is one for taking @@ -767,6 +1035,12 @@ overall Installed CCMX files will automatically select the appropriate base type. + The -z flag allows setting a different + Display Type for the reference spectral instrument, such as refresh + or non-refresh type, if it supports it. You may have to use this if + you are setting a specific base type for the colorimeter using -y, + and the spectrometer doesn't have this display type. + 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 @@ -829,6 +1103,9 @@ overall + + + of particular instruments for more details. This may give better accuracy for display measurements. @@ -895,32 +1172,26 @@ overall included in the parameter, and not mistaken for the start of another flag, or as a final command line parameter. - The -I parameter allows setting of the - display description string in the resulting The -I parameter allows optional setting of + the display description string in the resulting ccmx/ccss file. Since the default display description is probably very generic, it is highly recommended that a - description of the make and model of the display be provided here, - or set a display technology description using -T (see below). The default or - given display description will be printed before the menu. With most - command line shells, it will be necessary to enclose the parameter - with double quotes, so that spaces and other special characters are - included in the parameter, and not mistaken for the start of another - flag, or as a final command line parameters. + description of the make and model of the display be provided here. + The default or given display description will be printed before the + menu. With most command line shells, it will be necessary to enclose + the parameter with double quotes, so that spaces and other special + characters are included in the parameter, and not mistaken for the + start of another flag, or as a final command line parameters. - The -T parameter allows setting of the - display technology description string in the resulting ccmx/ccss file. The - applicability of the calibration mainly depends on the technology - type of the display, so a description of the technology (ie. "CRT", - "LCD", "LCD + backlight type + LCD type", etc.) is highly recommended, because it - can make the calibration more widely usable. With most command line - shells, it will be necessary to enclose the parameter with double - quotes, so that spaces and other special characters are included in - the parameter, and not mistaken for the start of another flag, or as - a final command line parameters. + The -t parameter allows setting of the + display technology type from the available list. You can get a usage + that includes the list using "ccxxmake -??". This is a required + parameter, since it conveys information about the refresh type and + settling time of the display. If the specific details of the display + are not known (i.e. backlight type, pannel type etc.), then choose + the next most generic type. If none of these are applicable, choose + "Unknown". The -U parameter allows setting of the user interface selection character this display type can be selected by, @@ -939,13 +1210,15 @@ overall + + + -Y n options overrides the refresh display mode set by the -y display type - selection, with -Y r - forcing refresh display mode, and -Y n forcing a non-refresh - display mode. Not all instruments support a display measurement - refresh mode, or the ability to override the mode set by the display - type selection. + href="spotread.html#y">-y display type selection, with -Y r forcing refresh display mode, + and -Y n forcing a non-refresh display mode. Not all + instruments support a display measurement refresh mode, or the + ability to override the mode set by the display type selection. The -Y R:rate options overrides calibration of the instrument refresh rate. This diff --git a/doc/collink.html b/doc/collink.html index 778b682..edd58b1 100644 --- a/doc/collink.html +++ b/doc/collink.html @@ -3,7 +3,7 @@ collink + charset=windows-1252"> @@ -41,6 +41,15 @@ + + + + + + + + + @@ -95,6 +104,15 @@ existing + + + + + + + + + @@ -133,6 +151,15 @@ clut + + + + + + + + + @@ -165,6 +192,15 @@ preserve + + + + + + + + + @@ -222,6 +258,15 @@ Include + + + + + + + + + @@ -242,6 +287,15 @@ Include -H file.cal        + + + + + + + + + Append calibration curves to 3dlut   -w [J,a,b]     Use forced - whitepoint hack [optional color to map the white to] - + -b             + + + + + + + Use RGB->RGB forced black point hack + -c viewcond set source viewing conditions for CIECAM02, -           + + + + + + + + + + c = transparency (default average) +           w:X:Y:Z       Adapted @@ -1007,6 +1267,15 @@ Adapted + + + + + + + + + @@ -1038,6 +1307,15 @@ Adapted + + + + + + + + + @@ -1068,6 +1346,15 @@ Adaptatation + + + + + + + + + @@ -1100,6 +1387,15 @@ Background + + + + + + + + + @@ -1135,6 +1431,15 @@ light + + + + + + + + + @@ -1162,6 +1467,15 @@ light + + + + + + + + + @@ -1180,6 +1494,15 @@ light + + + + + + + + + @@ -1207,6 +1530,15 @@ source + + + + + + + + + @@ -1240,6 +1572,15 @@ source + + + + + + + + + @@ -1280,6 +1621,15 @@ t + + + + + + + + + @@ -1311,6 +1661,15 @@ z + + + + + + + + + @@ -1345,6 +1704,15 @@ p + + + + + + + + + @@ -1380,6 +1748,15 @@ q + + + + + + + + + @@ -1418,6 +1795,15 @@ destination + + + + + + + + + @@ -1451,6 +1837,15 @@ destination + + + + + + + + + @@ -1474,6 +1869,15 @@ destination + + + + + + + + + @@ -1497,6 +1901,15 @@ destination + + + + + + + + + @@ -1517,9 +1930,17 @@ destination + + + + + + + + + MadVR .3dlut   file - -I b               + -I B               @@ -1527,6 +1948,23 @@ destination + Use BT.1886 source EOTF with technical gamma 2.4 + -I b:g.g +           Use + BT.1886-like source EOTF with effective gamma g.g + -I b:p.p:g.g +       Use effective gamma g.g source EOTF + with p.p prop. output black point offset + -I + g:g.g +           Use + effective gamma g.g source EOTF with all output black + point offset + -e flag            @@ -1540,10 +1978,6 @@ destination - Apply BT.1886-like mapping with effective gamma 2.2 to input - -I - b:g.g           @@ -1557,13 +1991,11 @@ destination - Apply BT.1886-like mapping with effective gamma g.g to - input - -I B -               + Video encode input as: + -E flag            @@ -1574,9 +2006,6 @@ destination - Apply BT.1886 mapping with technical gamma 2.4 to input - -I B:g.g           @@ -1590,14 +2019,17 @@ destination - Apply BT.1886-like mapping with technical gamma g.g to input - -e flag            + Video encode output as: +      + n                @@ -1612,12 +2044,13 @@ destination - Video encode input as: - -E flag            + normal RGB 0..1 levels (default) +      + t                @@ -1634,11 +2067,15 @@ destination - Video encode output as: -      - n                + + + RGB (16-235)/255 "TV" levels +      + T +                @@ -1648,9 +2085,6 @@ destination - normal RGB 0..1 levels (default) -      - t                @@ -1660,7 +2094,7 @@ destination - RGB (16-235)/255 "TV" levels + RGB (16-235)/255 "TV" levels, clip WTW [Input Only]      6                @@ -1672,6 +2106,15 @@ destination + + + + + + + + + Rec601 YCbCr SD (16-235,240)/255 "TV" levels      7                @@ -1684,6 +2127,15 @@ destination + + + + + + + + + Rec709 1125/60Hz YCbCr HD (16-235,240)/255 "TV" levels      5                @@ -1696,6 +2148,15 @@ destination + + + + + + + + + Rec709 1250/50Hz YCbCr HD (16-235,240)/255 "TV" levels      2                @@ -1708,6 +2169,15 @@ destination + + + + + + + + + Rec2020 YCbCr UHD (16-235,240)/255 "TV" levels      C                @@ -1720,6 +2190,15 @@ destination + + + + + + + + + Rec2020 Constant Luminance YCbCr UHD (16-235,240)/255 "TV" levels      @@ -1733,6 +2212,15 @@ destination + + + + + + + + + xvYCC Rec601 YCbCr Rec709 Prims. SD (16-235,240)/255 "TV" levels      @@ -1746,6 +2234,15 @@ destination + + + + + + + + + xvYCC Rec709 YCbCr Rec709 Prims. HD (16-235,240)/255 "TV" levels    + + + + + + + + + + gammap_p.x3d.html and gammap_s.x3d.html diagostics tiffgamut tool. More details about the gamut mapping, inverse AtoB mode. - The gamut provided to the -g - or -G flag should be in the - same colorspace that collink - is using internally to connect the two profiles. For all intents - except the last one (no. 7), - - - - - - - - - - - - - - - - - + The gamut provided to the -g or -G flag should be in the same colorspace that collink is using internally to + connect the two profiles. For all intents except the last one (no. 7), the space should be Jab + appearance space, with the viewing conditions generally being those + of the source profile viewing conditions. The source profile will + normally be the one used to create a source image gamut using tiffgamut. + + Simple mode gamut mapping options: + +       -i in_intent + + @@ -2139,16 +2675,6 @@ ICC - the space should be Jab appearance space, with the viewing - conditions generally being those of the source profile viewing - conditions. The source profile will normally be the one used to - create a source image gamut using tiffgamut. - - Simple mode gamut mapping options: - -       -i in_intent - - @@ -2307,6 +2833,13 @@ ICC in fine tuning paper emulation in absolute colorimetric mapping mode. + The -b flag forces RGB source 0,0,0 to map + to RGB destination 0,0,0. This may be useful for Video + proofing/calibration purposes, where the source is a standard + colorspace such as Rec709, and the display device is well behaved + with black at 0,0,0. By forcing the black mapping, any slight + raising of the black due to display profile tolerances is avoided. + The -c and -d options allow specification of the viewing conditions for the source and destination colorspaces respectively. The viewing condition @@ -2405,6 +2938,15 @@ ICC + + + + + + + + + @@ -2435,6 +2977,15 @@ ICC + + + + + + + + + @@ -2465,6 +3016,15 @@ ICC + + + + + + + + + @@ -2495,6 +3055,15 @@ ICC + + + + + + + + + @@ -2525,6 +3094,15 @@ ICC + + + + + + + + + @@ -2561,6 +3139,15 @@ White            &nb + + + + + + + + + @@ -2698,10 +3285,78 @@ White            &nb There is more information on the Typical Usage Scenarios page. - The -I b flag applies extra input - processing, applying BT.1886-like +The -I [b|B|g|G][:p.p][:g.g] series + of options, substitutes an alternative EOTF (Electro-Optical + Transfer Function) for the one specified by the matrix input + profile. This is typically used for creating Video display + emulations. + + The basic curve is a pure power curve with scaling and a combination + of input black offset and/or output black offset. The choice of flag + determines the way the power value is interpreted, and the default + balance between input and output black offset handling. + + The lower case b and g flags use an effective power + value specification, where the 50% input maps to the same output + value as a pure power curve with a perfect black. These are the + recommended flags to use, since this means that the overall contrast + of the reproduction will not be affected so much by differences and + variations in the black level, or how the black level is accounted + for. The default effective power value is 2.2. + + The upper case B and G flags use a technical power + value specification, where the power value is the actual one that + will be used. The end result will vary much more with the black + level of the display though. The default technical power value is + 2.4. + + The b and B flags default to the black level being + accounted for as a full input offset, where the power curve is + shifted and scaled to match the black point, preserving the black + shadow tonality. This is what BT.1886 + uses. + + The g and G flags default to the black level being + accounted for as a full output offset, where the power curve is + scaled to allow for the black point, losing some black shadow + tonality with higher black points. This is what many people think of + as a "pure" power curve, even though this is not possible unless the + display has a perfect zero black level. + + The optional :g.g value is the power to be used. This will + be an effective value if the b or g flags is used, + or the technical value if the B or G flag is used. + This is the primary way to make an allowance for the brightness of + the viewing environment for Video . Darker viewing environments + probably need a larger gamma value, while lighter viewing + environments probably need a lower value. + + The second optional :p.p value is the proportion of black + value that should be accounted for as output offset (the gamma value + must also be specified after this). This defaults to 0.0 for the b + and B flags, and 1.0 for the g and G flags, + but by specifying it explicitly as a value between 0.0 and 1.0, a + hybrid curve characteristic can be obtained. Setting a hybrid value + is a way of maintaining black shadow tonality while being able to + control how much detail is retained in those shadows. An appropriate + value may depend on exactly how the video material was mastered. + + Illustrative combinations are: + + -I b        +            Full + input offset (BT.1886 like) with effective gamma of 2.2 + -I g                   + + + + + + + Full output offset with effective gamma of 2.2 + -I B                  @@ -2709,46 +3364,107 @@ White            &nb + Full input offset (BT.1886 like) with technical gamma of 2.4. + This exactly implements the BT.1886 specification. + -I G                  - video gamma mapping using an effective gamma of 2.2 by default, and - overridable using -I b:g.g where g.g is the gamma. - The gamma is an effective gamma, meaning that its effect on 50% - input is the same as that of a pure power curve, in spite of any - black offset added by BT.1886. This has the benefit of making the - overall effect of brightness independent of the black level of the - display. Setting an effective gamma other than 2.2 is one way of - making the viewing condition adjustment for the different conditions - of video encoding and decoding, or for modelling the source - colorspace as a rendering on a video display. This would be used as - an alternative to using gamut mapping mode and setting explicit - input and output viewing conditions, or in combination with - appearance adjustments. BT.1886 will only work with matrix type - input profiles. The default value of 2.2 is probably suitable for - dim viewing conditions, and it may be desirable to override this - default if your viewing conditions are darker or lighter. For - lighter conditions, try "-I b:2.2". For darker conditions, try "-I - b:2.6". + + + Full output offset with technical gamma of 2.2 - The -I B flag applies extra input - processing, applying BT.1886 - video gamma mapping using the BT.1886 gamma of 2.4 by default, and - overridable using -I b:g.g where g.g is the gamma. - The gamma is the technical gamma, or power applied to the input - image, and this means that its effect on 50% input will depend on - the black level of the display, making the overall brightness - somewhat unpredictable. For a more predictable effect, use -I b. + -I b:2.3             + + + + + + + + Full input offset (BT.1886 like) with effective gamma of 2.3 + + -I g:2.3             + + + + + + + + Full output offset with effective gamma of 2.3 + -I B:2.35           + + + + + + + + Full input offset (BT.1886 like) with technical gamma of 2.35 + -I G:2.35           + + + + + + + + Full output offset with technical gamma of 2.35 + + -I b:0.4:2.3        + 60% input offset, 40% output offset with effective gamma of 2.3 + -I g:0.4:2.3        + + + + + + + + Same as above. + -I B:0.4:2.35      60% input + offset, 40% output offset with technical gamma of 2.35 + -I G:0.4:2.35      Same as + above. The -e flag applies a Video encoding to the input. See below and -E for the list of encodings. +      + style="font-family: monospace;">     + T +                + + + + + + + + + + + + + + + + + + + RGB (16-235)/255 "TV" levels, clip WTW + [Input Only] +      + x                @@ -2759,6 +3475,15 @@ White            &nb + + + + + + + + + xvYCC Rec601 YCbCr Rec709 Prims. SD (16-235,240)/255 "TV" levels      @@ -2772,6 +3497,15 @@ White            &nb + + + + + + + + + xvYCC Rec709 YCbCr Rec709 Prims. HD (16-235,240)/255 "TV" levels @@ -2785,6 +3519,13 @@ White            &nb as UHD Rec2020, or Digital Cinema SMPTE431 P3, then the corresponding ICC profile should be provided as the source profile. + The -e T option uses the same encoding as -e t, but + rather than handling WTW (Whiter Than White, or out of range values) + using extrapolation, it clips them to the valid range. This can be + useful if you are dealing with source material that has WTW values, + but your TV or Video display clips these out of range values in a + way that alters the hue. + The -E flag applies a Video encoding to the output. The possible encoding are: @@ -2800,6 +3541,15 @@ White            &nb + + + + + + + + + normal RGB 0..1 full range levels (default)      t                @@ -2812,8 +3562,22 @@ White            &nb - RGB (16-235)/255 "TV" levels -      + + + + + + + + + + RGB (16-235)/255 "TV" levels+      + 6                @@ -2824,6 +3588,15 @@ White            &nb + + + + + + + + + Rec601 YCbCr SD (16-235,240)/255 "TV" levels      7                @@ -2836,6 +3609,15 @@ White            &nb + + + + + + + + + Rec709 1125/60Hz YCbCr HD (16-235,240)/255 "TV" levels      5                @@ -2848,6 +3630,15 @@ White            &nb + + + + + + + + + Rec709 1250/50Hz YCbCr HD (16-235,240)/255 "TV" levels      2                @@ -2860,6 +3651,15 @@ White            &nb + + + + + + + + + Rec2020 YCbCr UHD (16-235,240)/255 "TV" levels      C                @@ -2872,12 +3672,22 @@ White            &nb + + + + + + + + + Rec2020 Constant Luminance YCbCr UHD (16-235,240)/255 "TV" - levels - - + levels + + The T The -P option causes a diagnostic 3D - VRML plots to be created that + X3DOM plots to be created that illustrate the gamut mapping generated. The inprofile argument specifies the @@ -2911,6 +3721,15 @@ White            &nb + + + + + + + + + diff --git a/doc/colprof.html b/doc/colprof.html index 022f984..b3b6df2 100644 --- a/doc/colprof.html +++ b/doc/colprof.html @@ -29,6 +29,14 @@ + + + + + + + + @@ -65,6 +73,14 @@ + + + + + + + +           Default intent: Perceptual, Rel. Colorimetric, Saturation, Abs. @@ -90,6 +106,14 @@ + + + + + + + + @@ -119,6 +143,14 @@ + + + + + + + + @@ -134,7 +166,8 @@        Don't put the input .ti3 data in the profile -k zhxr - Black generation: z = zero K, + Black Ink generation: z = + zero K,             @@ -161,6 +194,14 @@ x + + + + + + + + @@ -197,6 +238,14 @@ White + + + + + + + + @@ -233,6 +282,14 @@ Wh + + + + + + + + @@ -269,6 +326,14 @@ Wh + + + + + + + + @@ -304,6 +369,14 @@ Black + + + + + + + + @@ -340,6 +413,14 @@ concave, + + + + + + + + @@ -363,6 +444,14 @@ concave, + + + + + + + + Same as -k, but target is K locus rather than K value itself @@ -399,6 +488,14 @@ cLUT + + + + + + + + @@ -434,6 +531,14 @@ s + + + + + + + + @@ -470,6 +575,14 @@ S + + + + + + + + @@ -497,6 +610,14 @@ S + + + + + + + + @@ -529,6 +650,14 @@ and + + + + + + + + @@ -539,11 +668,27 @@ and primaries to be +ve+ -B X,Y,Z           + + + + + + + Display Black Point override hack -V demphasis       + + + + + + + + Degree of dark region cLUT grid emphasis 1.0-3.0 (default 1.00 = none) -f [illum] @@ -562,6 +707,14 @@ and + + + + + + + + M0, M1, M2,A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp ]@@ -578,6 +731,14 @@ and + + + + + + + + Choose illuminant for computation of CIE XYZ from spectral data & FWA: @@ -604,6 +765,14 @@ D50M2, + + + + + + + + D65, F5, F8, F10 or file.sp -o observ @@ -623,6 +792,14 @@ D50M2, + + + + + + + + @@ -662,6 +839,14 @@ for + + + + + + + + @@ -687,6 +872,14 @@ for + + + + + + + + @@ -713,6 +906,14 @@ for + + + + + + + + @@ -739,6 +940,14 @@ for + + + + + + + + @@ -773,6 +982,14 @@ for + + + + + + + + @@ -815,6 +1032,14 @@ for + + + + + + + + @@ -840,6 +1065,14 @@ for + + + + + + + + @@ -867,6 +1100,14 @@ for + + + + + + + + rl - White Point Matched Colorimetric (Lab) -c viewcond        @@ -883,6 +1124,14 @@ for + + + + + + + + @@ -909,6 +1158,14 @@ for + + + + + + + + @@ -934,6 +1191,14 @@ for + + + + + + + + @@ -960,6 +1225,14 @@ for + + + + + + + + @@ -985,6 +1258,14 @@ for + + + + + + + + @@ -1010,6 +1291,14 @@ for + + + + + + + + @@ -1064,6 +1353,14 @@ for + + + + + + + + @@ -1111,6 +1408,14 @@ for + + + + + + + + g:glare       Glare light % of ambient (default 1) @@ -1150,7 +1455,15 @@ for - Create gamut gammap_p.wrl and gammap_s.wrl diagostics + + + + + + + + + Create gamut gammap_p.x3d.html and gammap_s.x3d.html diagostics -O outputfile        Override @@ -1167,6 +1480,14 @@ Override + + + + + + + + @@ -1313,6 +1634,14 @@ the + + + + + + + + @@ -1339,6 +1668,14 @@ the + + + + + + + + @@ -1400,6 +1737,14 @@ the + + + + + + + + @@ -1426,6 +1771,14 @@ the + + + + + + + + @@ -1451,6 +1804,14 @@ the + + + + + + + + @@ -1476,6 +1837,14 @@ the + + + + + + + + @@ -1501,6 +1870,14 @@ the + + + + + + + + @@ -1534,6 +1911,14 @@ White            &nb + + + + + + + + @@ -1708,6 +2093,26 @@ White            &nb black and primary values, so as to work with these programs, but this will reduce the accuracy of the profile. + -B X,Y,Z This option is for display profiles + only, and allows overriding the black point of the resulting + profile. The XYZ value is in absolute instrument measurement units. + This option should be used only in special circumstances, for + instance if the display has a very low black point and the + instrument is not capable of measuring the black point accurately or + consistently. In this case a manual estimate of the black point + could be made and provided as the argument to -B. It may also be + useful for displays with black points that approach perfect black + (ie. Plasma or OLED) where a value of 0,0,0 may be more accurate + than typical instrument measurements. A value that is too different + to the default computed black point will likely result in a profile + with strange behavior near black. + Note that the default contents of the .ti3 created by dispread is normalised to be 100 for the + white point Y value, and similarly values returned by icclu -ia -px + are normalized to a white Y value of 1.0, which is not what the -B + option expects, so some care needs to be taken in specifying and + evaluating the resulting black point XYZ values. + The -V demphasis parameter allows sets the degree to which cLUT grid spacing should emphasize the accuracy of modelling the device response in the dark regions, over that of the @@ -1735,14 +2140,14 @@ White            &nb Ultra Violet to the one the instrument actually used in the measurement. There are two ways this can be used: - The first and most common is to use the -f flag with the -i - illuminant parameter, to make the color values more accurately - reflect their appearance under the viewing illuminant. This will - work accurately if you specify the actual illuminant spectrum you are using to view the - print, using the -i flag. If you are - doing proofing, you need to apply this to The first and most useful is to use the -f flag with + the -i illuminant parameter (i.e. "-f -i D50"), to + make the color values more accurately reflect their appearance under + the viewing illuminant. This will work accurately if you specify the + actual illuminant spectrum + you are using to view the print, using the -i + flag. If you are doing proofing, you need to apply this to both your source profile, and your destination profile. Note that it is not sufficient to specify an illuminant with the same white point as the one you are @@ -1763,6 +2168,14 @@ White            &nb + + + + + + + + @@ -1785,6 +2198,7 @@ White            &nb ref/D50_X.X.sp set of illuminant spectra are the D50 spectrum with different levels of U.V. added or subtracted, ref/D50_1.0.sp being the standard D50 illuminant, and may be somewhere to start. + [Note: Generally using -f with the standard (-i) D50 illuminant spectrum will predict that the device will produce bluer output than the default of not @@ -1797,13 +2211,14 @@ White            &nb result will be, as the overall color correction compensates for the blueness. The opposite will happen for an input profile.] - The second way of using the -f flag is to provide it with a - instrument simulation illuminant spectrum parameter, in addition to - the default D50 or -i parameter CIE XYZ - calculation illuminant. This more complicated scenario - simulates the measurement of the spectral reflectance of the samples - under a particular instrument illuminant, then computes the CIE XYZ - values of that reflectance spectrum under the default D50 or -i + The second way of using the -f flag is to provide it + with a instrument simulation illuminant spectrum parameter, in + addition to the default D50 or -i parameter CIE XYZ + calculation illuminant (i.e. "-f M1", or "-f A -i D65" + etc.). This more complicated scenario simulates the measurement + of the spectral reflectance of the samples under a particular + instrument illuminant, then computes the CIE XYZ values of + that reflectance spectrum under the default D50 or -i parameter illuminant. This is not used to give a more accurate real world result, but to provide simulations of various standardized measurement conditions. For instance, to reproduce ISO @@ -1817,10 +2232,10 @@ White            &nb equivalent to    -f D50     -f M2        equivalent to    -f D50M2 - - Note that using -f M2 - gives a result that is comparable to that of a U.V. cut filter - instrument. See also the discussion About + + Note that using -f + M2 gives a result that is comparable to that of a U.V. cut + filter instrument. See also the discussion About Fluorescent Whitening Agent compensation. The -i parameter allows specifying a @@ -2064,7 +2479,7 @@ White            &nb been applied) into the device gamut. The -P option causes diagnostic 3D VRML plots to be created that + href="File_Formats.html#X3DOM">X3DOM plots to be created that illustrate the gamut mappings generated for the perceptual and saturation intent tables. diff --git a/doc/colverify.html b/doc/colverify.html index 3f8bc72..daebbdd 100644 --- a/doc/colverify.html +++ b/doc/colverify.html @@ -3,7 +3,7 @@ colverify + charset=windows-1252"> @@ -24,46 +24,75 @@ Normalise + + + each files reading to white Y -N               Normalise + + + each files reading to white XYZ + -m               + Normalise each files reading to its white X+Y+Z + -M               + Normalise both files reading to mean white XYZ -D               Use + + + D50 100.0 as L*a*b* white reference -c           + + + Show CIE94 delta E values -k           Show CIEDE2000 delta E values + -h               + + + Plot a histogram of delta E's -s           Sort patch value by error -w           - create VRML vector visualisation (measured.wrl) + + + + create X3DOM vector visualisation (measured.x3d.html) -W           - create VRML marker & vector visualisation - (measured.wrl)+ create X3DOM marker & vector visualisation + (measured.x3d.html) -x           - Use VRML axes + + + + Use X3DOM axes -f [illum]       Use Fluorescent Whitening Agent compensation [opt. simulated inst. illum.:                    + + + M0, M1, M2, A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp] -i illum         @@ -72,12 +101,18 @@ Use                    + + + A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp -o observ        Choose CIE Observer for spectral data:                    + + + 1931_2 (def.), 1964_10, S&B 1955_2, shaw, J&V 1978_2 -L profile.icm   Skip any first file out of @@ -103,6 +138,14 @@ Use to the XYZ of white for each set before comparison. White is assumed to be the patch with the largest Y value. + The -m flag causes the two sets of values to be normalized + to the X+Y+Z of white for each set before comparison. White is + assumed to be the patch with the largest Y value. + + The -M flag causes the two sets of values to be normalized + to the average XYZ of the whites from each set before comparison. + White is assumed to be the patch with the largest Y value. + The -D flag causes the white reference point for the conversion to L*a*b* to be D50 with a Y value of 100%. By default the sample with the largest Y value is found, and the L*a*b* white @@ -122,11 +165,14 @@ Use CIEDE2000 delta E has a closer correspondence with perceived color differences than either CIE76 or CIE94 delta E values. + The -h flag will display a histogram plot of the fit delta + E's. The X scale is delta E, the Y scale is % + If the -s flag is used in combination with the -v flag, then the test point by test point output will be sorted from worst to best. - The -w creates a VRML + The -w creates a X3DOM 3D visualization of the differences between the test points in D50 L*a*b* space, each difference being shown as a line vector. If the -W flag is used, then the target @@ -135,7 +181,7 @@ Use CGATS file) by using the same file for both "target" and "measured" values. - The -x flag adds Lab axes to the VRML output. + The -x flag adds Lab axes to the X3DOM output. The -f flag enables Fluorescent Whitening Agent (FWA) compensation. This only works if spectral data is available and, the @@ -180,10 +226,10 @@ Use The same parameter value should be used as was used during the creation of the profile. - The -L profile.icm parameter causes colverify to ignore - any patches from the first file that are out of gamut according to - the profile. This can be useful in evaluating accuracy without - tainting it by impossible to reach colors. + The -L profile.icm parameter causes colverify to + ignore any patches from the first file that are out of gamut + according to the profile. This can be useful in evaluating accuracy + without tainting it by impossible to reach colors. The -X file.ccmx option applies the given 3x3 calibration matrix to the values from the second file before doing diff --git a/doc/dispcal.html b/doc/dispcal.html index e23a8d0..993124d 100644 --- a/doc/dispcal.html +++ b/doc/dispcal.html @@ -1,28 +1,28 @@ - - - - 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]               @@ -57,17 +57,29 @@ - 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 @@ -110,8 +122,20 @@ for - VideoLUT access. - + -d n                 Choose the @@ -154,8 +178,6 @@ list - 1) - -dweb[:port]         @@ -167,6 +189,9 @@ list + + 1) + -dweb[:port]         @@ -188,9 +213,6 @@ list - Display via a web server at port (default 8080) - -dmadvr -              @@ -207,19 +229,16 @@ list - [MSWin] Display via MadVR Video Renderer - -c + + Display via a web server at port (default 8080) + -dmadvr +              @@ -247,37 +266,9 @@ 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] - -O description       + + [MSWin] Display via MadVR Video Renderer + -dcc[:n]             @@ -285,6 +276,14 @@ list + + Display via n'th ChromeCast (default 1, ? for list) + -c @@ -311,16 +310,6 @@ list - Fast ICC Profile Description string (Default "outfile") - -u                   -Update -previous -calibration -and -(if --o -used) -ICC @@ -339,6 +328,38 @@ ICC + + 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       @@ -354,12 +375,6 @@ ICC - profile VideoLUTs - -q [lmh]             @@ -389,12 +404,21 @@ ICC + + Fast ICC Profile Description string (Default "outfile") + -u                   +Update +previous +calibration +and +(if +-o +used) +ICC - Quality - Low, Medium (def), High - -p                   @@ -417,10 +441,6 @@ ICC - Use telephoto mode (ie. for a projector) (if available) - -y X -                 @@ -439,6 +459,13 @@ ICC + + profile VideoLUTs + -q [lmh]             @@ -454,20 +481,6 @@ ICC - Display type - instrument specific list to choose from. - -t [temp]            -White -Daylight -locus -target, -optional -target -temperaturee -in @@ -497,22 +510,14 @@ in + + Quality - Low, Medium (def), High + -p                   + - deg. K (deflt.) - -T [temp]            -White -Black -Body -locus -target, -optional -target -temperaturee @@ -541,16 +546,22 @@ temperaturee + + Use telephoto mode (ie. for a projector) (if available) + -y X +                 + + + + + + - in deg. K - -w x,y               @@ -584,11 +595,22 @@ temperaturee - Set the target white point as chromaticity coordinates - -b bright + -t [temp]            +White +Daylight +locus +target, +optional +target +temperaturee +in + @@ -622,11 +644,6 @@ temperaturee - Set the target white brightness in cd/m^2 - -g gamma             @@ -637,6 +654,19 @@ temperaturee + + deg. K (deflt.) + -T [temp]            +White +Black +Body +locus +target, +optional +target +temperaturee @@ -660,9 +690,6 @@ temperaturee - Set the target response curve gamma (Def. 2.4) -                       @@ -684,6 +711,12 @@ temperaturee + + in deg. K + -w x,y               @@ -696,9 +729,6 @@ temperaturee - Use "-gl" for L*a*b* curve -                @@ -731,17 +761,13 @@ temperaturee + + Set the target white point as chromaticity coordinates + -b bright            -      Use "-gs" for sRGB curve -                       -Use -"-g709" -for -REC -709 -curve -(should -use @@ -775,8 +801,6 @@ use - -a as well!) -                       @@ -787,6 +811,12 @@ use + + Set the target white brightness in cd/m^2 + -g gamma             @@ -810,9 +840,6 @@ use - Use "-g240" for SMPTE 240M curve (should use -a as well!) -                       @@ -834,6 +861,10 @@ use + + Set the target response curve gamma (Def. 2.4) +                       @@ -846,7 +877,6 @@ use - Use "-G2.4 -f0" for BT.1886                                           @@ -873,27 +903,16 @@ use - - -G gamma -             - Set the target response curve actual technical gamma - -f [degree]          -Amount -of -black -level -accounted -for -with -output + + Use "-gl" for L*a*b* curve +                @@ -921,8 +940,6 @@ output - offset (default all output offset) - -a ambient           @@ -940,6 +957,17 @@ output + +      Use "-gs" for sRGB curve +                       +Use +"-g709" +for +REC +709 +curve +(should +use @@ -956,19 +984,6 @@ 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 - -B bkbright          @@ -997,17 +1012,14 @@ output + + -a as well!) +                       - Set the target black brightness in cd/m^2 - -e [n]               @@ -1041,18 +1053,16 @@ output - Run n verify passes on final curves - -z -                   + + Use "-g240" for SMPTE 240M curve (should use -a as well!) +                       @@ -1080,21 +1090,6 @@ output - Run only verify pass on installed calibration curves - -P - ho,vo,ss[,vs]     Position test window - and scale it -                       -ho,vi: -0.0 -= -left/top, -0.5 -= -center, -1.0 @@ -1112,6 +1107,8 @@ center, + + Use "-G2.4 -f0" for BT.1886                                           @@ -1128,16 +1125,6 @@ center, - = right/bottom etc. -                       -ss: -0.5 -= -half, -1.0 -= -normal, -2.0 @@ -1159,6 +1146,22 @@ normal, + + + -G gamma +             + Set the target response curve actual technical gamma + -f [degree]          +Amount +of +black +level +accounted +for +with +output @@ -1171,9 +1174,6 @@ normal, - = double etc. -                       @@ -1194,10 +1194,6 @@ normal, - ss,vs: = optional horizontal, vertical scale. - -F -                   @@ -1210,6 +1206,9 @@ normal, + + offset (default all output offset) + -a ambient           @@ -1231,11 +1230,6 @@ normal, - Fill whole screen with black background - -E -                   @@ -1248,21 +1242,6 @@ normal, - Video - encode output as (16-235)/255 "TV" levels - -n              -     -[X11 -only] -Don't -set -override -redirect -on @@ -1274,11 +1253,29 @@ on + + 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                   + + Use forced black point hack + -B bkbright          + @@ -1296,14 +1293,6 @@ on - test window - -J -              -      Run instrument calibration first - -N                   @@ -1330,6 +1319,13 @@ on + + Set the target black brightness in cd/m^2 + -e [n]               @@ -1337,18 +1333,6 @@ on - Disable initial calibration of instrument if possible - -H -              -      Use high resolution spectrum mode (if - available) - - -X file.ccmx         @@ -1382,16 +1366,17 @@ on - Apply Colorimeter Correction Matrix - -X - file.ccss          -Use -Colorimeter -Calibration + + Run n verify passes on final curves + -z +                   @@ -1421,14 +1406,6 @@ Calibration - Spectral Samples for calibration - -Q observ -     Choose CIE Observer for spectrometer or CCSS - colorimeter data: -             @@ -1444,6 +1421,22 @@ Calibration + + Run only verify pass on installed calibration curves + -P + ho,vo,ss[,vs]     Position test window + and scale it +                       +ho,vi: +0.0 += +left/top, +0.5 += +center, +1.0 @@ -1462,11 +1455,6 @@ Calibration - 1931_2 (def.), 1964_10, S&B 1955_2, shaw, - J&V 1978_2, 1964_10c - -I b|w               @@ -1493,6 +1481,17 @@ Calibration + + = right/bottom etc. +                       +ss: +0.5 += +half, +1.0 += +normal, +2.0 @@ -1500,51 +1499,10 @@ Calibration - Drift compensation, Black: -Ib, White: -Iw, Both: -Ibw - -Y - R:rate            - 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 - -W n|h|x             -Override -serial -port -flow -control: -n -= -none, @@ -1578,12 +1536,10 @@ none, - h = HW, x = Xon/Xoff - -D [level]           + + = double etc. +                       @@ -1615,14 +1571,13 @@ none, + + ss,vs: = optional horizontal, vertical scale. + -F +                   - Print debug diagnostics to stderr - inoutfile            @@ -1656,79 +1611,6 @@ 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 - specified as a single string, e.g. -d @@ -1738,6 +1620,12 @@ none, + + Fill whole screen with black background + -E +                   @@ -1761,260 +1649,23 @@ none, + + Video + encode output as (16-235)/255 "TV" levels + -n              +     +[X11 +only] +Don't +set +override +redirect +on - 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. - - 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 you may have to start the video playback - software and load a video clip in pause for this to work. MadVR - rendering does not need or support VideoLUT access, but be aware - that the state of the Graphics Card VideoLUTs may affect the - results, and therefore may have to be set appropriately using - dispwin. Test patch colors will not be processed by the - MadVR 3dLut by default. - - -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 @@ -2048,15 +1699,6 @@ 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 - approximately gamma 2.2 (-gs), -the @@ -2067,6 +1709,15 @@ the + + test window + -J +              +      Run instrument calibration first + -N                   @@ -2090,66 +1741,6 @@ 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! - - -G gamma -As @@ -2171,6 +1762,20 @@ As + + Disable initial calibration of instrument if possible + -H +              +      Use high resolution spectrum mode (if + available) + + -X file.ccmx         + @@ -2183,100 +1788,6 @@ 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 ration too severely. If the device contrast ratio is - not so good, and the native black hue is noticeably different to - that of the chosen white point (which is often the case for 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 @@ -2308,159 +1819,1278 @@ If + + Apply Colorimeter Correction Matrix + -X + file.ccss          +Use +Colorimeter +Calibration + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Spectral Samples for calibration + -Q observ +     Choose CIE Observer for spectrometer or CCSS + colorimeter data: +             + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 1931_2 (def.), 1964_10, S&B 1955_2, shaw, + J&V 1978_2, 1964_10c + -I b|w               + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Drift compensation, Black: -Ib, White: -Iw, Both: -Ibw + -Y + + + + + + + + + + + + + + + R:rate            + + + + + + + + + + + + + + + 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 + -W n|h|x             +Override +serial +port +flow +control: +n += +none, + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + h = HW, x = Xon/Xoff + -D [level]           + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Print debug diagnostics to stderr + inoutfile            + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 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 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 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 you may have to start the video playback + software and load a video clip in pause for this to work. MadVR + rendering does not need or support VideoLUT access, but be aware + that the state of the Graphics Card VideoLUTs may affect the + results, and therefore may have to be set appropriately using + dispwin. Test patch colors will not be processed by the + MadVR 3dLut by default. + + -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. + + -g gamma +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 + approximately gamma 2.2 (-gs), +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! + + -G gamma +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. + + -A rate: +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).This +can +improve +a + + + + + + + + + - 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. - - -B Set - the target brightness of black in cd/m^2. Setting too high a value - may give strange results as it interacts with trying to achieve the - target "advertised" gamma curve shape. You could try using -f 1 if - this causes a problem. - - -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. 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).This -can -improve -a @@ -2494,481 +3124,482 @@ 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 or - ColorMunki. By default an adaptive integration time measurement mode - will be used for emission measurements, but some instruments support - a fixed integration time mode that can be used with display devices. - This may give increased consistency and faster measurement times, - but may also give less accurate low level readings. - - 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 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. - - - - - - - + + 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 071fa7d..a30ab25 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              @@ -43,16 +43,24 @@ -      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 @@ -83,8 +91,16 @@ m - for VideoLUT access. - + -d n                 Choose the @@ -115,7 +131,15 @@ list - (default 1) + + + + + + + + + (default 1) -dweb[:port]         @@ -141,8 +165,16 @@ list - Display via a web server at port (default 8080) - -dmadvr + + + + + + + + + Display via a web server at port (default 8080) + -dmadvr              @@ -155,13 +187,25 @@ list - [MSWin] Display via MadVR Video Renderer - -c listno -        Set - communication port from the following list (default 1) - -dcc[:n]             + + +Display via n'th ChromeCast (default 1, ? for list)
+ -c listno +        Set + communication port from the following list (default 1)
+ -p                   @@ -185,9 +229,17 @@ list - Use telephoto mode (ie. for a projector) (if available)
- -y X + + + + + + + + + Use telephoto mode (ie. for a projector) (if available)
+ -y X                 Display @@ -213,9 +265,17 @@ Display - type - instrument specific list to choose from.
- -k + + + + + + + + + type - instrument specific list to choose from.
+ -k file.cal          @@ -239,9 +299,17 @@ Display - Load calibration file into display while reading
- -K + + + + + + + + + Load calibration file into display while reading
+ -K file.cal          Apply @@ -266,12 +334,28 @@ Apply - calibration file to test values while reading
+ + + + + + + + + calibration file to test values while reading
-V                   - [MSWin] Enable MadVR color management (3dLut)
+ + + + + + + + + [MSWin] Enable MadVR color management (3dLut)
-s              @@ -295,11 +379,19 @@ 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 @@ -330,7 +422,15 @@ center, - 1.0 = right/bottom etc.
+ + + + + + + + + 1.0 = right/bottom etc.
                      ss: 0.5 @@ -361,7 +461,15 @@ normal, - 2.0 = double etc.
+ + + + + + + + + 2.0 = double etc.
                      @@ -378,9 +486,17 @@ normal, - ss,vs: = optional horizontal, vertical scale.
- -F + + + + + + + + + ss,vs: = optional horizontal, vertical scale.
+ -F                   @@ -404,9 +520,17 @@ normal, - Fill whole screen with black background
- -E + + + + + + + + + Fill whole screen with black background
+ -E                   @@ -415,10 +539,52 @@ normal, - Video - encode output as (16-235)/255 "TV" levels
- Video + encode output as (16-235)/255 "TV" levels
+ -Z + nbits             + + + + + + + + + + + + + + + + Quantize +test +values +to +fit + + + + + + + + + + + + in nbits
+ -n                   [X11 @@ -449,8 +615,16 @@ redirect - on test window
- -J + + + + + + + + + on test window
+ -J              @@ -474,8 +648,16 @@ redirect -      Run calibration first
-
+ -N                   @@ -499,16 +681,24 @@ 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 @@ -539,8 +729,16 @@ Y - 100
-
+ -X file.ccmx         @@ -564,8 +762,16 @@ Y - Apply Colorimeter Correction Matrix
- -X + + + + + + + + + Apply Colorimeter Correction Matrix
+ -X file.ccss          Use Colorimeter @@ -592,13 +798,21 @@ 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:
            @@ -622,11 +836,19 @@ 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, @@ -657,14 +879,38 @@ Both: - -Ibw
+ + + + + + + + + -Ibw
-Y + + + + + + + + R:rate             - Override measured refresh rate with rate Hz - -Y A + + + + + + + + + Override measured refresh rate with rate Hz
+ -Y A                 @@ -679,25 +925,33 @@ 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
-
+ -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 @@ -728,10 +982,18 @@ 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            @@ -755,72 +1017,80 @@ 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 @@ -844,240 +1114,280 @@ 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.
-
- 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 you may have to start the video playback - software and load a video clip in pause for this to work. MadVR - rendering does not need or support VideoLUT access, so the -K option should be used to read calibrated values. - Be aware that the state of the Graphics Card VideoLUTs may affect - the results, and therefore may have to be set appropriately using - dispwin. By default the test patch colors will not be - processed by the MadVR 3dLut (see the -V flag).
-
- -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. 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.
-
- -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, + + + + + + + + + 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 you may have to start the video playback + software and load a video clip in pause for this to work. MadVR + rendering does not need or support VideoLUT access, so the -K option should be used to read calibrated values. + Be aware that the state of the Graphics Card VideoLUTs may affect + the results, and therefore may have to be set appropriately using + dispwin. By default the test patch colors will not be + processed by the MadVR 3dLut (see the -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).This can improve @@ -1104,144 +1414,152 @@ 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 or - ColorMunki. By default an adaptive integration time measurement mode - will be used for emission measurements, but some instruments support - a fixed integration time mode that can be used with display devices. - This may give increased consistency and faster measurement times, - but may also give less accurate low level readings.
-
- 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 -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.
-
-
-
- - + + + + + + + + + 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 -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 f1d75f5..6036e76 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 @@ -47,17 +47,21 @@ 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 @@ -72,8 +76,12 @@ optionally - choose a different display m for Video LUT access.
- -d n                 [Not X11] @@ -88,8 +96,12 @@ X11] - Choose the display from the following list (default 1)
- + -dweb[:port]         @@ -100,16 +112,24 @@ X11] - Display via a web server at port (default 8080)
- -dmadvr -              - [MSWin] Display via MadVR Video Renderer
- -P - ho,vo,ss[,vs]     Position test window - and scale it
+ + + + + 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
                      ho,vi: 0.0 @@ -124,8 +144,12 @@ 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 @@ -140,7 +164,11 @@ ss: - = half, 1.0 = normal, 2.0 = double etc.
+ + + + + = half, 1.0 = normal, 2.0 = double etc.
                      @@ -149,9 +177,13 @@ ss: - ss,vs: = optional horizontal, vertical scale.
- -F + + + + + ss,vs: = optional horizontal, vertical scale.
+ -F                   Fill whole @@ -166,30 +198,38 @@ whole - screen with black background
- -E + + + + + screen with black background
+ -E                   - 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 @@ -204,9 +244,13 @@ just - video LUT loading & Beeps
- -n + + + + + video LUT loading & Beeps
+ -n                   Test native @@ -221,7 +265,11 @@ 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 @@ -236,9 +284,13 @@ the - currently loaded Video LUT to 'filename'
- -c + + + + + currently loaded Video LUT to 'filename'
+ -c                   Load a @@ -253,10 +305,14 @@ a - linear display calibration (clear calibration)
- -V + + + + + linear display calibration (clear calibration)
+ -V                   Verify that @@ -271,9 +327,13 @@ that - calfile/profile cal. is currently loaded in LUT
- -I + + + + + calfile/profile cal. is currently loaded in LUT
+ -I                   @@ -286,10 +346,14 @@ that - Install profile for display and use it's calibration
- -U + + + + + Install profile for display and use it's calibration
+ -U                   @@ -302,8 +366,12 @@ that - Un-install profile for display
+ + + + + Un-install profile for display
-S d                 Specify the @@ -318,7 +386,11 @@ the - install/uninstall scope for OS X [nlu] or Vista [lu]
+ + + + + install/uninstall scope for OS X [nlu] or Vista [lu]
                      d is @@ -333,10 +405,14 @@ is - one of: n = network, l = local system, u = user (default)
- -L + + + + + one of: n = network, l = local system, u = user (default)
+ -L                   @@ -349,10 +425,14 @@ is - Load installed profiles cal. into Video LUT
- -X + + + + + Load installed profiles cal. into Video LUT
+ -X                   @@ -365,10 +445,14 @@ 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 @@ -383,13 +467,17 @@ debug - diagnostics to stderr
- calfile
+ calfile              Load display @@ -404,59 +492,63 @@ 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 @@ -471,242 +563,261 @@ the - difficulty cause by TwinView and MergedFB in X11 based systems, you - can optionally specify a separate display number after the display - that is going to be used to present test patches, for accessing the - VideoLUT hardware. This must be specified as a single string, e.g. -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.
-
- 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 you may have to start the video playback - software and load a video clip in pause for this to work. MadVR - rendering does not need or support VideoLUT access, but be aware - that the state of the Graphics Card VideoLUTs may affect the results - (check this using dispwin). Test patch colors will be - processed by the MadVR 3dLut by default (see -n - flag).
-
- 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. 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.
-
-
-
-
- - + + + + + 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 you may have to start the video playback + software and load a video clip in pause for this to work. MadVR + rendering does not need or support VideoLUT access, but be aware + that the state of the Graphics Card VideoLUTs may affect the results + (check this using dispwin). Test patch colors will be + processed by the MadVR 3dLut by default (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.
+
+
+
+
+ + diff --git a/doc/fakeread.html b/doc/fakeread.html index 2a7b5c0..376e971 100644 --- a/doc/fakeread.html +++ b/doc/fakeread.html @@ -3,7 +3,7 @@ fakeread + charset=windows-1252"> @@ -34,6 +34,9 @@ style="font-family: monospace;">profile.[icm|mpp|ti3] + + + inoutfile
-v @@ -44,24 +47,45 @@ Video encode device input to sepration as:
     n              + + + normal 0..1 full range RGB levels (default)
     t              + + + (16-235)/255 "TV" RGB levels
     6              + + + Rec601 YCbCr SD (16-235,240)/255 "TV" levels
     7              + + + Rec709 1125/60Hz YCbCr HD (16-235,240)/255 "TV" levels
     5              + + + Rec709 1250/50Hz YCbCr HD (16-235,240)/255 "TV" levels
     2              + + + Rec2020 YCbCr UHD (16-235,240)/255 "TV" levels
     C              + + + Rec2020 Constant Luminance YCbCr UHD (16-235,240)/255 "TV" levels
-p separation.icm Use device link separation @@ -69,7 +93,13 @@ -E flag           Video decode separation device output. See -e above
- -k file.cal       + -Z nbits        Quantize test values to fit in nbits
+ -k file.cal       + + + Apply calibration (include in .ti3 output)
-i file.cal       Include calibration in .ti3 output, but don't apply it
@@ -82,32 +112,42 @@ -0 pow            Apply power to device chanel 0-9
- -b output.icm     Apply - BT.1886-like mapping with effective gamma 2.2
- -b g.g:output.icm Apply BT.1886-like mapping with - effective gamma g.g
- -B output.icm     Apply - BT.1886 mapping with technical gamma 2.4
- -B g.g:output.icm Apply BT.1886 mapping with - technical gamma g.g
+ -B + display.icm          + Use BT.1886 source EOTF with technical gamma 2.4
+ -b g.g:display.icm      Use + BT.1886-like source EOTF with effective gamma g.g
+ -b p.p:g.g:display.icm Use effective gamma g.g + source EOTF with p.p prop. output black point offset
+ -g g.g:display.icm      Use + effective gamma g.g source EOTF with all output black point + offset
-I intent         r = relative colorimetric, a = absolute (default)
-A L,a,b          Scale black point to target Lab value
-l                + + + Output Lab rather than XYZ
-s                + + + Lookup MPP - spectral values
+ href="File_Formats.html#MPP">MPP spectral values
-R level          Add average random deviation of <level>% to output PCS values
-u                + + + Make random deviations have uniform distributions rather than normal
-S @@ -130,6 +170,9 @@ + + + Base name for input[.ti1]/output[ The -E flag applies a Video decoding to the output of the separation. See - -e for the list of decodings.
+ + + + -e for the list of decodings. Setting a + video encoding for output will also set quantization of 8 bits (see + -Z flag below). If your video connection is better than 8 bits (ie. + 10 or 12 bits), then you may wish to raise this default.
+
+ -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.

The -k file.cal parameter specifies a - calibration file created by printcal or dispcal, and the supplied calibration + calibration file created by printcal or + dispcal, and the supplied calibration curves will be applied to the chart device values after any separation and before the device profile. This allows emulating a system that uses per device channel calibration. The calibration @@ -193,26 +258,24 @@ computation of ink limits.

The -i file.cal parameter specifies a - printer calibration file created by printcal or dispcal, and the - calibration curves will be included in the included in the resulting - .ti3 file, so that they can be passed through to the ICC profile, to - allow accurate computation of ink limits. The calibration printcal + or dispcal, and the calibration curves + will be included in the included in the resulting .ti3 file, so that + they can be passed through to the ICC profile, to allow accurate + computation of ink limits. The calibration is not applied to tchart values. Note that if the supplied ICC profile contains VCGT calibration curves, that these will be included in the resulting .ti3 by default.

The -K file.cal parameter specifies - a calibration file created by printcal or dispcal, and the - inverse of the supplied calibration curves will be applied to the - chart device values after any separation and before the device - profile. This allows for undoing calibration curves that may be part - of a video calibration device link, so that the (calibrated device - value) device profile will work as expected.
+ a calibration file created by printcal + or dispcal, and the inverse of the + supplied calibration curves will be applied to the chart device + values after any separation and before the device profile. This + allows for undoing calibration curves that may be part of a video + calibration device link, so that the (calibrated device value) + device profile will work as expected.

The -r parameter is a way of simulating instability in the behaviour of the @@ -230,59 +293,18 @@ them to the power of the parameter. This applies a transfer curve to the simulated device response.

- The -b output.icm flag applies extra input - processing, applying BT.1886-like - - - - - - - - - - - - video gamma mapping using an effective gamma of 2.2 by default, and - overridable using -b g.g:output.icm where g.g is the - gamma. output.icm is the display ICC profile that provides - the black point that the BT.1886 curves will target. The gamma is an - effective gamma, meaning that its effect on 50% input is the same as - that of a pure power curve, in spite of any black offset added by - BT.1886. This has the benefit of making the overall effect of - brightness independent of the black level of the display. Setting an - effective gamma other than 2.2 is one way of making the viewing - condition adjustment for the different conditions of video encoding - and decoding, or for modelling the source colorspace as a rendering - on a video display. BT.1886 will only work with matrix type input - profiles. Typically this will be used to create a verification test + The -[b|B|g|G] [p.p:][g.g:]display.icm + series of options, substitutes an alternative EOTF (Electro-Optical + Transfer Function) for the one specified by the matrix input + profile. display.icm is the display ICC profile that + provides the black point that the gamma curve curves will target. + Typically these options will be used to create a verification test set for checking the operation of a device link or 3dLut created - using collink, using the same BT.1886 - parameters.
-
- The -B output.icm flag applies extra - input processing, applying BT.1886-like - - - - - - - - - - - - video gamma mapping using a gamma of 2.4 by default, and overridable - using -B g.g:output.icm where g.g is the gamma. output.icm - is the display ICC profile that provides the black point that the - BT.1886 curves will target. The gamma is the technical gamma, or - power applied to the input image, and this means that its effect on - 50% input will depend on the black level of the display, making the - overall brightness somewhat unpredictable. For a more predictable - effect, use -b.
+ using collink, using the same gamma + curve parameters. See collink -I b + for a full explanation of these parameters, and Verifying Video Calibration for more + detail.

The -I parameter allows changing the intent used in looking up the ICC diff --git a/doc/i1proHiRes.html b/doc/i1proHiRes.html index d6d8078..d6eef6a 100644 --- a/doc/i1proHiRes.html +++ b/doc/i1proHiRes.html @@ -3,7 +3,7 @@ The i1pro Hi Res. Mode + charset=windows-1252"> @@ -42,6 +42,8 @@ + + width at half maximum) of about 25nm. Doing a measurement at 3.3nm resolution reveals that the optical limit seems to be about 15nm, so there is some hope of improvement from that perspective.

@@ -56,7 +58,7 @@ which seems to have a diffraction grating/light sensor with a less smooth spectral efficiency curve than the Rev A - D models, the task of up-sampling the emissive calibration data with sufficient - accuracy is a more difficult.
+ accuracy is more difficult.

The verification experiment

@@ -77,6 +79,8 @@ href="http://www.jeti.com/cms/index.php/instruments-55/radiometer/specbos-1211"> + + specbos 1211 reference Tele-Spectro-Radiometer.

2) Using an i1pro2 in standard 10nm mode.
@@ -157,13 +161,17 @@ href="http://www.jeti.com/cms/index.php/instruments-55/radiometer/specbos-1211"> improve colorimetric measurement accuracy of display devices. Accuracy may conceivably be improved a little more than indicated by this experiment for i1pro rev A-D instruments which have a smoother - diffraction grating/light sensor characteristic, or it is also + diffraction grating/light sensor characteristic, but it is also conceivable that an unfortunate combination of display spectra and - the i1pro2 may result in reduced accuracy. The High Resolution mode - is primarily useful for showing more spectral detail, and should - probably not be used for colorimetric measurement when the highest - possible robustness and reliability is desired. The potential for - improved accuracy may be of benefit in other situations though.
+ the i1pro2 may result in reduced accuracy. More extensive testing of + a range of instruments and illuminants would be needed to allay such + a concern.
+
+ In summary: the High Resolution mode is unquestionably useful + for showing more spectral detail, and demonstrates promise of + improved accuracy, but should probably not be used used for + colorimetric measurement when the highest possible confidence is + desired.

Raw Data:

The raw measurement data is available in this .ti3 archive.
diff --git a/doc/iccgamut.html b/doc/iccgamut.html index fe555cf..47df32c 100644 --- a/doc/iccgamut.html +++ b/doc/iccgamut.html @@ -3,18 +3,21 @@ iccgamut + charset=windows-1252">

xicc/iccgamut

- Create a gamut file or VRML file of the color gamut of an ICC + Create a gamut file or X3DOM file of the color gamut of an ICC profile.
iccgamut allows creation of gamut files from the forward or backwards table of an ICC profile, in Lab or CIECAM02 Jab colorspace, and can also representing the - gamut as a VRML file.
+ gamut as a X3DOM file.
+
+ See 3D Viewing + Format for switching to VRML or X3D output format.

Usage

iccgamut [-options]
-d sres       Surface resolution @@ -31,23 +36,21 @@ -w            emit - - - VRML .wrl file as well as CGATS .gam file

-n            Don't - add VRML axes or white/black point
- -k            -Add + add X3DOM axes or white/black point
+ -k            +Add - VRML markers for prim. & sec. "cusp" points

-f function   f = forward*, b = backwards

@@ -74,6 +79,8 @@ r + + = reverse (priority: monochrome > matrix > lut)
-p oride
        + + pc - Critical print evaluation environment (ISO-3664 P1)
@@ -120,6 +133,8 @@ either + + mt - Monitor in typical work environment
        @@ -127,6 +142,8 @@ either + + mb - Monitor in bright work environment
    @@ -154,6 +171,8 @@ s:surround   + + n = auto, a = average, m = dim, d = dark,
               @@ -161,6 +180,8 @@ s:surround   + +    c = transparency (default average)
         @@ -168,6 +189,8 @@ w:X:Y:Z      + + Adapted white point as XYZ (default media white)
         @@ -175,6 +198,8 @@ w:x:y        + + Adapted white point as x, y
         @@ -182,6 +207,8 @@ a:adaptation + + Adaptation luminance in cd.m^2 (default 50.0)
         @@ -190,6 +217,8 @@ Background + + % of image luminance (default 20)
         l:imagewhite Image white in cd.m^2 if surround = auto (default 250)
         @@ -208,11 +239,15 @@ f:flare               + + g:X:Y:Z      Glare color as XYZ (default media white)
         + + g:x:y        Glare color as x, y
-s             @@ -220,6 +255,8 @@ Create + + special cube surface topology plot
profilegamut [.gam] and/or VRML [.wrl] file.
+ monospace;" href="File_Formats.html#X3DOM">X3DOM [.x3d.html] file. +

Comments
The parameters are all those that control which table in the ICC profile to use, as well as what color space to convert it to.
@@ -246,11 +284,11 @@ Create and is a good place to start. Small values may take a lot of time to generate, and will produce big files.

- The -w flag causes a VRML file to be produced, as well as a + The -w flag causes a X3DOM file to be produced, as well as a gamut file.

The -n flag suppresses the L*a*b* axes being created in the - VRML.
+ X3DOM.

The -k flag adds markers for each of the primary and secondary "cusp" points (Red, Yellow, @@ -332,7 +370,7 @@ Create
and the resulting files will be profile.gam and profile.wrl.
+ underline;">profile.x3d.html.

To create a gamut suitable for CIECAM02 gamut mapping space in colprof or collink, something like
diff --git a/doc/iccgamutmapping.html b/doc/iccgamutmapping.html index d180372..8deab44 100644 --- a/doc/iccgamutmapping.html +++ b/doc/iccgamutmapping.html @@ -1,163 +1,210 @@ - - About ICC profiles and Gamut Mapping - - - -
About ICC profiles and Gamut Mapping
-
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:
-
-AtoB0, BtoA0:   Perceptual
-AtoB1, BtoA1:   Colorimetric
-AtoB2, BtoA2:   Saturation
-
-The colorimetric intent is meant to convey the exact device color -behaviour, without any gamut mapping. Typically it is used to store the -devices behaviour (characterization), and is also used where exact -color reproduction is required, such as for proofing. The Colorimetric -tables double up for both relative colorimetric and -absolute colorimetric with the application of a white point restoration.
-
-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.
-
-[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.]
-
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).
-
-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 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.
-
-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.]
-
ICC Version 4 behaviour
-(Note that Argyll does not currently support ICC V4)
-
-By default, ICC Version 4 profile operate exactly the same as the ICC -V2 profile in regard to gamut mapping. A slight adjustment was made to -the permitted tag contents, to allow things like Display profiles to -contain the full range of AtoB and BtoA tables, so that they could also -be gamut mapped. But an optional part of ICCV4, is to use the 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 -behavior, this sort of expansion and re-compression will be the normal -thing.
-
-The chief drawback, is that only one (non colorimetric) intent can -really be supported, that of saturation.
-
-The typically expected behaviour of perceptual intent gamut mapping, is -to -compress any areas of the source gamut that lie outside the destination -gamut, but for areas that fall within the destination gamut, change -them as little as possible, consistent with keeping smooth and -proportional with respect to the compressed colors. This preserves the -source "look" as much as -possible, while ensuring that out of gamut colors are smoothly brought -within the destination gamut.
-
-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.
-
-
-
-
-
-
-
-
- + + About ICC profiles and Gamut Mapping + + + +
About ICC profiles and Gamut Mapping
+
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:
+
+ AtoB0, BtoA0:   Perceptual
+ AtoB1, BtoA1:   Colorimetric
+ AtoB2, BtoA2:   Saturation
+
+ The colorimetric intent is meant to convey the exact device color + behaviour, without any gamut mapping. Typically it is used to store + the + devices behaviour (characterization), and is also used where exact + color reproduction is required, such as for proofing. The + Colorimetric + tables double up for both relative colorimetric and + absolute colorimetric with the application of a white point + restoration.
+
+ 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.
+
+ [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.]
+
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).
+
+ 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 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.
+
+ 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.]
+
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 + 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.
+
+ This approach has a number of drawbacks though. One is that the + colors + get gamut mapped twice. Gamut mapping is sometimes not very precise, + and the geometry of the transforms may not cancel out, especially + since + different profile vendors may choose different algorithms in their + gamut mapping. By "cancel out", I mean that even if you were linking + the same source colorspace to the same destination colorspace, the + gamut may be expanded (say) in the process of mapping to the PRMG, + and + then compressed again in mapping from the RMG to the device space, + and + these expansions and compressions may not quite match. Given that + the + PRMG is a relatively large gamut, larger than many real devices + actual + behavior, this sort of expansion and re-compression will be the + normal + thing.
+
+ 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.
+
+ 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.
+
+
+
+
+
+
+
+
+ diff --git a/doc/illumread.html b/doc/illumread.html index 0dcf5bd..9b65b2f 100644 --- a/doc/illumread.html +++ b/doc/illumread.html @@ -1,271 +1,309 @@ - - - - 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
- -D [level] -            - Print debug diagnostics to stderr
-
+ -T +                    + + + Test mode - restore & save measurements to
+                         + + *_i.sp, *_r.sp, *_p.sp, *_mpir.sp, *_cpir.sp files
+ -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 -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 an alternative might be to use a piece of the - intended paper for this purpose. It's unclear which may give a - better result.]
-
- 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).
-
-
-
-
-
-
-
-
-
-
-
- - + + + + 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).
+
+
+
+
+
+
+
+
+
+
+
+ + diff --git a/doc/instruments.html b/doc/instruments.html index 0bcc62d..f5897d5 100644 --- a/doc/instruments.html +++ b/doc/instruments.html @@ -34,9 +34,25 @@ + + + + + + + - Tele-Spectro-Radiometer

+ Klein:
+
+     K10-A   +             +             +             +     - Display Colorimeter. Reported also to work with + the K-1, K-8 and K-10
+
X-Rite:
    DTP20 "Pulse"                             @@ -64,6 +80,13 @@ + + + + + + + @@ -99,6 +122,13 @@ + + + + + + + @@ -134,6 +164,13 @@ + + + + + + + @@ -171,6 +208,13 @@ + + + + + + + @@ -206,6 +250,13 @@ + + + + + + + @@ -241,6 +292,13 @@ + + + + + + + @@ -276,6 +334,13 @@ + + + + + + + @@ -311,6 +376,13 @@ + + + + + + + @@ -400,6 +472,13 @@ + + + + + + + @@ -436,6 +515,13 @@ + + + + + + + @@ -481,6 +567,13 @@ + + + + + + + @@ -518,6 +611,13 @@ + + + + + + + @@ -560,6 +660,13 @@ + + + + + + + @@ -580,6 +687,12 @@        - 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 @@ -608,6 +721,13 @@ + + + + + + + @@ -634,6 +754,13 @@ + + + + + + + @@ -940,6 +1067,13 @@ + + + + + + + @@ -995,8 +1129,8 @@ this measurement. A rough guide is as follows:

- +
@@ -1008,6 +1142,12 @@ + + + + @@ -1065,8 +1205,8 @@ style="font-weight: bold;">specbos 1211 and 1201 Tele-Spectro-Radiometer
- +

Availability:

@@ -1075,9 +1215,53 @@ href="http://www.jeti.com/">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 and - characterization, amongst many other uses.
+ for monitor, projector and cinema calibration & + characterization, and colorimeter calibration, amongst many other + uses.
+
+

+
+
+
Klein K10-A Colorimeter
+
+
+

+ Availability:
+
+ The Klein K10-A from + + + + + + + Klein Instruments + + + + + + + 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.
+

@@ -1354,6 +1538,13 @@ + + + + + + + @@ -1409,6 +1600,13 @@ + + + + + + + @@ -1445,6 +1643,13 @@ + + + + + + + @@ -1497,6 +1702,13 @@ Gretag + + + + + + + @@ -1739,6 +1951,13 @@ Gretag + + + + + + + @@ -1764,6 +1983,13 @@ Gretag + + + + + + + @@ -1798,6 +2024,13 @@ Gretag + + + + + + + @@ -1834,6 +2067,13 @@ Gretag + + + + + + + @@ -1897,6 +2137,13 @@ 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.
@@ -1943,6 +2190,11 @@ href="http://www8.hp.com/us/en/products/oas/product-detail.html?oid=5225568">HP     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 @@ -1991,6 +2243,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2031,6 +2290,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2067,6 +2333,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2128,6 +2401,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2164,6 +2444,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2241,7 +2528,14 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey - + + + + + + + + LCD display        A Liquid Crystal Display, that is of the Non-Refresh type. [Default, CB1]
    c    @@ -2269,6 +2563,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2428,6 +2729,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2473,6 +2781,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2513,6 +2828,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2529,6 +2851,222 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey style="font-weight: bold;">Spyder4Elite and Spyder4Pro instruments, but is only capable of monochrome readings.
+
+
+

+ Spyder 5 + colorimeter
+
+
+
+ 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                         + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - 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   + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +          Wide Gamut LCD, RGB LED + Backlight - wide gamut Liquid Crystal Display with RGB LED + backlight.
+     x +             LCD, CCFL + Type 2 + Backlight              + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - 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 @@ -2563,6 +3101,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2617,6 +3162,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2653,6 +3205,13 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey + + + + + + + @@ -2694,35 +3253,77 @@ href="http://www.pantone.com/pages/products/product.aspx?pid=562&ca=2">Huey    l                   + + + + + + + LCD, CCFL Backlight [Default]
   c                  + + + + + + + CRT display
   p                  + + + + + + + Projector
   e                  + + + + + + + LCD, White LED Backlight
   F                  + + + + + + + Factory matrix (For Calibration) [CB1]
   R                 + + + + + + + Raw Reading (For Factory matrix Calibration) [CB2]

diff --git a/doc/invprofcheck.html b/doc/invprofcheck.html index 9851774..bd611b3 100644 --- a/doc/invprofcheck.html +++ b/doc/invprofcheck.html @@ -39,10 +39,10 @@ Show CIE94 delta E values
-k           Show CIEDE2000 delta E values
-w           -create VRML visualisation (profile.wrl)

-x           -Use VRML axes
+Use X3DOM axes
-e           Color vectors acording to delta E
@@ -60,7 +60,7 @@ table. A grid of device values is created, and the transform from PCS->device, and then device->PCS is computed in L*a*b* space. The average, maximum and RMS error delta E values are computed and displayed in the chosen delta E metric. A VRML plot of the error vectors can + href="File_Formats.html#X3DOM">X3DOM plot of the error vectors can be created. invprofcheck tries to only test in-gamut color values. Note that because it scans a device grid, for a CMYK device, the density of test points will be @@ -114,16 +114,16 @@ closer correspondence with perceived color differences than either CIE76 or CIE94 delta E values.

-The -w creates a VRML 3D +The -w creates a X3DOM 3D visualization of the differences between the test points and the profiles prediction of the resulting colors.

-The -x flag adds Lab axes to the VRML output.
+The -x flag adds Lab axes to the X3DOM output.

The -e flag causes the error -vectors in the VRML output to be color coded according to their +vectors in the X3DOM output to be color coded according to their lengths, from longest to shortest: yellow, red, magenta, blue, cyan and green.

diff --git a/doc/mpplu.html b/doc/mpplu.html index 2f0b955..8d4e755 100644 --- a/doc/mpplu.html +++ b/doc/mpplu.html @@ -11,7 +11,7 @@
Summary
Lookup individual color values though an MPP profile. Also -create MPP gamut files or VRML +create MPP gamut files or X3DOM views.
Usage
mpplu [-v level] [-f func] @@ -63,9 +63,9 @@ data:
Create gamut output
-w         - Create gamut VRML as well
+ Create gamut X3DOM as well
-n             -Don't add VRML axes
+Don't add X3DOM axes
-a n           Gamut transparency level
-d @@ -78,7 +78,7 @@ surface detail level
   1 - check partial derivative for device input
            -    2 - create overlap diagnostic VRML gamut +    2 - create overlap diagnostic X3DOM gamut surface
profile.mpp Profile to be used
@@ -157,15 +157,15 @@ description from the profile, creating a
The -w flag causes the gamut surface to be generated in VRML format + href="File_Formats.html#X3DOM">X3DOM format as well as .gam format.

The -n flag suppresses the VRML axes.
+ style="font-weight: bold;">-n flag suppresses the X3DOM axes.

The -a n parameter sets a transparency -level in the VRML surface.
+level in the X3DOM surface.

The -d parameter controls the level of detail displayed in the gamut surface. The parameter roughly corresponds to a deltaE value, so diff --git a/doc/oeminst.html b/doc/oeminst.html index ffbc0f0..d1daccd 100644 --- a/doc/oeminst.html +++ b/doc/oeminst.html @@ -3,7 +3,7 @@ oeminst + charset=windows-1252"> @@ -16,7 +16,7 @@ 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, it can enable the full range of manufacturers + For the Spyder 4 or 5, it can enable the full range of manufacturers colorimeter calibration selections, as well as install CCSS files.
For the eye-one display 3 it can locate and translate X-Rite .EDR files to CCSS files and install them to enable a full range of @@ -38,6 +38,7 @@ + Verbose
-n                      @@ -49,6 +50,7 @@ + Don't install, show where files would be installed
-c                      @@ -61,6 +63,7 @@ + Don't install, save files to current directory
-S @@ -74,6 +77,7 @@ + Specify the install scope u = user (def.), l = local system]
infile                  @@ -86,6 +90,7 @@ + setup.exe CD install file(s) or .dll(s) containing install files
infile.[edr|ccss|ccmx] @@ -97,6 +102,7 @@ + EDR file(s) to translate and install or CCSS or CCMX files to install
                         @@ -109,6 +115,7 @@ + If no file is provided, oeminst will look for the install CD.
@@ -151,6 +158,7 @@ + 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 @@ -187,6 +195,7 @@ 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 instrument does not have the full range of vendor - instrument calibration options without the presence of the - instrument vendors calibration information for the device. This - calibration information is not provided with Argyll, since it has - not been made available under a compatible license.
+ + 4 or Spyder 5 instrument does not + have the full range of vendor instrument calibration options + without the presence of the instrument vendors calibration + information for the device. This calibration information is not + provided with Argyll, since it has not been made available under a + compatible license.

- The purchaser of a Spyder 4 instrument should have received a copy - of this calibration information along with their instrument from - the original vendor, and oeminst + The purchaser of a Spyder 4 or 5 instrument should have received a + copy of this calibration information along with their instrument + from the original vendor, and oeminst enables the full range of calibration choice for their instrument, by locating the necessary information in the users copy of the instrument install files.
@@ -233,8 +244,12 @@ href="http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html">XDG drivers have not been installed, or the user does not wish to install them, or no vendors drivers are available for the users platform (i.e. Linux), then oeminst - will also attempt to locate the Spyder 4 installation CDROM, and - make use of the calibration information from there.
+ will also attempt to locate the Spyder 4 or 5 installation CDROM, + and make use of the calibration information from there. If you + have downloaded the OEM software from the vendors website, then + you should run oeminst on the install package you + downloaded.
+

The i1d3 @@ -279,6 +294,7 @@ 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 colorimeter model that they were created for.

If you are going to use the same CCSS or CCMX file all the time, - then you may want to set the ARGYLL_COLMTER_CAL_SPEC_SET + then you may want to set the ARGYLL_COLMTER_CAL_SPEC_SET environment variable.

diff --git a/doc/profcheck.html b/doc/profcheck.html index ef0bc5b..a85e07e 100644 --- a/doc/profcheck.html +++ b/doc/profcheck.html @@ -3,7 +3,7 @@ profcheck + charset=windows-1252"> @@ -11,22 +11,25 @@
Summary
Check an ICC profile against .ti3 test chart - data.
+ data, and optionally create a pruned .ti3 file.

Usage Summary
profcheck - [-options] - data.ti3 iccprofile.icm
- - -v - [level]      - Verbosity level (default 1), 2 to print each DE
-c              Show + + + + + CIE94 delta E values
-k           @@ -35,157 +38,204 @@ Show -w              create - VRML visualization (iccprofile.wrl)

-x              Use - VRML axes
+ + + + + + X3DOM axes
-m              Make -VRML +X3DOM + + + + + lines a minimum of 0.5
-e              Color vectors - acording to delta E
- -d + + + + + + acording to delta E
+ -s              + Sort output by delta E
+ -h              + + + + + Plot a histogram of delta E's
+ -P + de           + Create a pruned .ti3 with points less or equal to de delta E
+ -d devval1,deval2,devvalN
                 Specify - a device value to sort - against
+ + + + + + a device value to sort against
-p              Sort + + + + + device value by PCS/Lab target
- - -f + -f [illum]      Use Fluorescent Whitening Agent compensation [opt. simulated inst. illum.:
                  + + + + + M0, M1, M2, A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp]
-i illum        Choose illuminant for computation of CIE XYZ from spectral data & FWA:
                 + + + + + A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp
-o - observ    -    Choose CIE - Observer - for spectral data:
+ observ       Choose CIE Observer for + spectral data:
                   - 1931_2 - (def.), - 1964_10, S&B - 1955_2, shaw, J&V 1978_2
+ + + + + + 1931_2 (def.), 1964_10, S&B 1955_2, shaw, + J&V 1978_2
-I intent       r = relative colorimetric, a = absolute (default)
data.ti3     -    - Test - point data file
+    Test point data file
iccprofile.icm Profile to check
Usage Details and Discussion
profcheck provides a way of checking how well an ICC profile conforms to the test - sample data that was used to create it (or other test samples - that are from the same device). This is the same sort of check done - within - the profile making tool (colprof), but - having a - separate tool provides some flexibility. The absolute forward - table in the profile is used to create PCS values from the sample - points, and the profiles PCS value then compared to the PCS values - of - the measured sample points. Note the lower delta E values are not - always a better measure of how good a profile is. The aim of a - profile - is to model the underlying characteristics of a device, not to - slavishly reproduce the sampled data point values. Sampled data - point - values contain device variation and instrument reading inaccuracies, - and a good profiler will try and filter out this noise, resulting in - some deliberate differences between the profile and the sample - points - used to create it.
+ sample data that was used to create it (or other test samples that + are from the same device). This is the same sort of check done + within the profile making tool (colprof), + but having a separate tool provides some flexibility. The + absolute forward table in the profile is used to create PCS values + from the sample points, and the profiles PCS value then compared to + the PCS values of the measured sample points. Note the lower delta E + values are not always a better measure of how good a profile is. The + aim of a profile is to model the underlying characteristics of a + device, not to slavishly reproduce the sampled data point values. + Sampled data point values contain device variation and instrument + reading inaccuracies, and a good profiler will try and filter out + this noise, resulting in some deliberate differences between the + profile and the sample points used to create it.

The -v flag prints out extra information during the - checking. A - value greater than 1 will print the color values of each test point.
+ checking. A value greater than 1 will print the color values of each + test point.

The -c option causes the differences between the test values - and - the profile prediction of the color for each device value to be - displayed - in CIE94 delta E, rather than plain L*a*b* delta E. CIE94 delta E - has a - closer - correspondence with perceived color differences than the default - CIE76 - delta E values.
+ and the profile prediction of the color for each device value to be + displayed in CIE94 delta E, rather than plain L*a*b* delta E. CIE94 + delta E has a closer correspondence with perceived color differences + than the default CIE76 delta E values.

The -k option causes the differences between the test values - and - the profile prediction of the color for each device value to be - displayed - in CIEDE2000 delta E, rather than plain L*a*b* delta E. CIEDE2000 - delta - E has a - closer - correspondence with perceived color differences than either CIE76 or - CIE94 delta E values.
-
- The -w creates a VRML - 3D - visualization - of the differences between the test points and the profiles - prediction - of - the resulting colors.
-
- The -x flag adds Lab axes to the VRML output.
+ and the profile prediction of the color for each device value to be + displayed in CIEDE2000 delta E, rather than plain L*a*b* delta E. + CIEDE2000 delta E has a closer correspondence with perceived color + differences than either CIE76 or CIE94 delta E values.
+
+ The -w creates a X3DOM + 3D visualization of the delta E's between the test points and the + profiles prediction of the resulting colors.
+
+ The -x flag adds Lab axes to the X3DOM output.

The -m flag makes each error line a minimum of 0.5 delta E long, so that all the points are visible. This makes it easier to - view - the distribution of test points in the reference set.
+ view the distribution of test points in the reference set.

The -e flag causes the - error - vectors in the VRML output to be color coded according to their - lengths, from longest to shortest: yellow, red, magenta, blue, cyan - and - green.
+ error vectors in the X3DOM output to be color coded according to + their lengths, from longest to shortest: yellow, red, magenta, blue, + cyan and green.
+
+ The -s flag will cause the -v2 patch by patch delta E output + to be sort from largest to smallest. This is useful in identifying + badly read patches.
+
+ The -h flag will display a histogram plot of the fit delta + E's. The X scale is delta E, the Y scale is %
+
+ 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 + delta E of less than or equal to the given delta E threshold. This + can be useful if you know that there are faulty or poor accuracy + readings in the data set. Use profcheck -h to examine the fit delta + E histogram to choose a threshold that cuts off the tail, and then + profcheck -P to create the pruned data set. You can check that this + is appropriate if a profcheck -h on the resulting profile no longer + has a long tail. Note that using this procedure will be of + no benefit if the tail is due to an inherently poor fit of the + profile to the data rather than reading innacuracy, even if it makes + the fit appear to be better.
+
+ NOTE that the pruning does not take any special care as to + what test points are pruned - it may prune important points such as + white and black points!

The -d parameters allow the specification of a particular - device value, - and the test point by test point output will be sorted by distance - from - the - given device value. This can be useful in determining how well - "supported" - the profile is in a particular area of the colorspace.
+ device value, and the test point by test point output will be sorted + by distance from the given device value. This can be useful in + determining how well "supported" the profile is in a particular area + of the colorspace.

If the -p flag is used in combination with the -d - parameters, - then the test point by test point output will be sorted by distance - in - PCS - (Lab) space rather than distance in device space.
+ parameters, then the test point by test point output will be sorted + by distance in PCS (Lab) space rather than distance in device space.

The -f flag enables Fluorescent Whitening Agent (FWA) compensation. This only works if spectral data is available and, the @@ -197,31 +247,27 @@ Sort illumination spectrum to be used as the similated instrument illuminant, overriding the default D50 or CIE computation illuminant used for FWA (see -i below). See colprof -f for - a fuller explanation. The same value should be used as was used - during the creation of the + href="colprof.html#f">colprof -f for a fuller explanation. The + same value should be used as was used during the creation of the profile.

The -i flag allows specifying a standard or custom - illumination - spectrum, applied to the spectral test point values 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 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 + illumination spectrum, applied to the spectral test point values 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 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 same value should be used as was used during the - creation of the - profile.
+ creation of the profile.

The -o flag allows specifying a tristimulus observer, and is used to compute PCS (Profile Connection Space) tristimulus values. The following choices are available:
1931_2 selects the standard CIE 1931 2 degree - observer. - The default.
+ observer. The default.
1964_10 selects the standard CIE 1964 10 degree observer.
1955_2 selects the Stiles and Birch 1955 2 degree @@ -232,16 +278,15 @@ Sort observer

The same parameter value should be used as was used during the - creation - of the profile.
+ creation of the profile.

The -I parameter allows changing the intent used in looking up the ICC profile colors to relative colorimetric. This would not be used if you are - checking a profile against the .ti3 file that was used to create it, - since, since profiles are always made - from absolute colorimetric measurement values.
+ underline;">not be used if you are checking a profile + against the .ti3 file that was used to create it, since, since + profiles are always made from absolute colorimetric measurement + values.

diff --git a/doc/scanin.html b/doc/scanin.html index ac6ccc8..96d3cc2 100644 --- a/doc/scanin.html +++ b/doc/scanin.html @@ -3,7 +3,7 @@ scanin + charset=windows-1252"> @@ -59,6 +59,7 @@ style="font-family: monospace;">                   Generate + a chart reference (.cht) file
                    Output + patch values in .val file
                    Use + image to measure color to convert printer pbase .ti2 to .ti3
@@ -81,22 +84,26 @@ Use style="font-family: monospace;">                  Same + as -c, but accumulates more values to pbase .ti3
                      from + subsequent pages
-r                   Replace + device values in pbase .ti3
                      Default + is to create a scanner .ti3 file
-F @@ -105,10 +112,12 @@ Default                       Don't + auto recognize, locate using four fiducual marks
-p                   Compensate + for perspective distortion
                    Recognize + chart in normal orientation only
                      Default + is to recognize all possible chart angles
-m                   Return + true mean (default is robust mean)
-G gamma             - Approximate - gamma encoding of image
+ Approximate gamma encoding of image
-v [n]               Verbosity + level 0-9
-d                 diag + - B&W of input image
                      diag + - Horizontal edge detection
                      diag + - Vertical edge detection
                      diag + - Groups detected
     l                 diag + - Lines detected
     L                 diag + - All lines detected
     + I                 diag + - lines used to improve fit
     + c                 diag + - lines perspective corrected
                 diag + - lines rotated
     s                 diag + - sample boxes rotated
     o                 diag + - sample box outlines
     n                 diag + - sample box names
     a                 diag + - sample box areas
     p                 diag + - pixel areas sampled
-O outputfile       Override the @@ -250,13 +278,15 @@ diag resolutions, and will cope with some degree of noise in the scan (due to screening artefacts on the original, or film grain), but it isn't really designed to accept very high resolution input. For - anything over 600DPI, you should consider down sampling the scan - using a filtering downsample, before submitting the file to scanin. - Similarly, any file with a large level of noise (due to screening or - scanner artefacts) should consider down sampling the image or - filtering it with some average preserving filter before submitting - it to scanin. Examining the diagnostic output (ie. -dig and -dil) - may help in determining whether noise is an issue.
+ anything over 1200 pixels on a side, you should consider down + sampling the scan using a filtering down-sample, before submitting + the file to scanin. Similarly, any file with a large level of noise + (due to screening or scanner artefacts, or a noisy surrounding + texture) should consider cropping out the noisy surrounding, or down + sampling the image or filtering it with some average preserving + filter before submitting it to scanin. Examining the diagnostic + output (ie. -dig and -dil) may help in determining whether noise is + an issue.

There are 5 basic modes that scanin operates in.

@@ -309,12 +339,14 @@ diag create the input device profile. The file arguments in -c mode are: The TIFF file that is to be processed containing the image of a print test chart, the + image recognition template file for the test chart generated by the printtarg tool, the input device ICC or MPP profile, the base name for the .ti2 file containing the test chart printer device values and their patch identifiers and the base name for the resulting .ti3 file, and + finally an optional name for the image recognition diagnostic output. The resulting .ti3 file will have the same base name as the input TIFF file. If there is more than one page in the test diff --git a/doc/spec2cie.html b/doc/spec2cie.html index c928f9a..d25b0a0 100644 --- a/doc/spec2cie.html +++ b/doc/spec2cie.html @@ -3,38 +3,43 @@ fakeread + charset=windows-1252">
spectro/spec2cie

Summary
- Convert spectral .ti3 - readings into CIE XYZ or L*a*b* readings. FWA compensation may be - applied.
+ Convert reflective spectral .ti3 + readings into CIE XYZ and D50 L*a*b* readings. Apply FWA, plot + spectrums.

Usage
spec2cie [options] input.ti3 + + output.ti3 -v            Verbose mode
- -I illum   -    Override - actual instrument illuminant - in .ti3 file: + -I illum   + + +    Override actual instrument illuminant in .ti3 + 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) + + + (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.:                 + + M0, M1, M2, A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp]            - -     - A, C, D50 (def.), D50M2, D65, F5, +     A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp - -o - observ -    Choose CIE Observer for spectral - data: + -o observ + + +    Choose CIE Observer for spectral data:                + + 1931_2 (def.), - 1964_10, S&B - 1955_2, shaw, J&V 1978_2 + 1964_10, S&B 1955_2, shaw, J&V 1978_2 -n             Don't output + + spectral values -p             - Plot - each values spectrum - - input.ti3      + Plot each values spectrum + input.ti3      Measurement + + file output.ti3     - Converted - measurement file + + + Converted measurement file

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

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

+ Setting an actual instrument/simulated instrument/CIE illuminant + only has an effect for reflective/transmissive spectra. Emissive + spectra don't have an illuminant, and will simply be converted to + XYZ using the given observer.
+

The -I parameter allows specifying a an - illumination - spectrum for the actual instrument illuminant, overriding that - computed from - the type of instrument (recorded in the .ti3 file). This is rarely - used. This parameter is can - only be used in combination with the -f - flag. If a - filename is specified instead, it will be assumed to be an Argyll - specific .sp - custom spectrum file. - Illuminant details are:
+ illumination spectrum for the actual instrument illuminant, + overriding that computed from the type of instrument (recorded in + the .ti3 file). This is rarely used. This parameter is can only be + used in combination with the -f + flag. If a filename is specified instead, it will be assumed to be + an Argyll specific .sp custom + spectrum file. Illuminant details are:

        A   CIE - tungsten - filament lamp 2848K
+ tungsten filament lamp 2848K
        D50 CIE daylight 5000K
        D65 CIE daylight 6500K
        F5 CIE Fluorescent @@ -107,8 +114,7 @@ Measurement         F8 CIE Fluorescent 5000K, CRI 95
        F10 CIE Fluorescent - 5000K, - CRI 81
+ 5000K, CRI 81

The -f flag enables Fluorescent Whitening @@ -121,6 +127,8 @@ Measurement standard or custom illumination spectrum to be used as the similated instrument illuminant, overriding the default D50 or CIE computation illuminant used for FWA (see -i below). See + + colprof -f for a fuller explanation.

The -i parameter allows specifying a @@ -129,8 +137,7 @@ Measurement 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 + to be an Argyll specific .sp custom spectrum file. This only works if spectral data is available. Illuminant details are:

@@ -181,22 +188,18 @@ Measurement Note that if an observer other than 1931 2 degree is chosen, the resulting ICC profile will not be standard, and cannot be freely interchanged with other profiles that that us the standard 1931 2 - degree - observer. Profiles should only be linked with other profiles that - have - the same illuminant and observer.
-
+ degree observer. Profiles should only be linked with other profiles + that have the same illuminant and observer.

The -n flag - disables the output of the spectral values. If just the XYZ and - L*a*b* - values are needed, this makes for a smaller, easier to read file.
+ disables the output of the spectral values. If just the XYZ and D50 + L*a*b* values are needed, this makes for a smaller, easier to read + file.

The -p flag causes each spectrum to be plotted. If FWA compensation is used, - then - the before/after compensation spectrums will be shown.
+ then the before/after compensation spectruma will be shown.

diff --git a/doc/spotread.html b/doc/spotread.html index aaac0a1..f3964f5 100644 --- a/doc/spotread.html +++ b/doc/spotread.html @@ -3,14 +3,18 @@ spotread + charset=windows-1252">
spectro/spotread

Summary
Use an instrument to read a single color value. This can be a useful - diagnostic aid. + diagnostic aid.
+
+ [ A commercial tool that does much of what spotread does and more, + is the ArgyllPRO ColorMeter. + ]

Usage Summary
spotread [-options] [logfile]
@@ -29,6 +33,14 @@ + + + + + + + + @@ -53,6 +65,14 @@ + + + + + + + + @@ -82,6 +102,14 @@ + + + + + + + + @@ -105,6 +133,14 @@ + + + + + + + + @@ -128,6 +164,14 @@ + + + + + + + + @@ -150,6 +194,14 @@ + + + + + + + + @@ -160,6 +212,14 @@ style=" font-family: monospace;" href="#ew">-ew                   + + + + + + + + Use display white point relative chromatically adjusted mode
-p
-i illum      Choose illuminant for computation of - CIE XYZ from spectral data & FWA:

            @@ -343,6 +459,14 @@ D50 + + + + + + + + @@ -369,6 +493,14 @@ D50 + + + + + + + + @@ -394,6 +526,14 @@ D50 + + + + + + + + @@ -414,6 +554,14 @@ D50 + + + + + + + + @@ -434,6 +582,14 @@ D50 + + + + + + + + @@ -454,6 +610,14 @@ D50 + + + + + + + + @@ -474,6 +638,14 @@ D50 + + + + + + + + @@ -497,6 +669,14 @@ D50 + + + + + + + + @@ -518,6 +698,14 @@ D50 + + + + + + + + @@ -539,6 +727,14 @@ D50 + + + + + + + + @@ -560,6 +756,14 @@ D50 + + + + + + + + @@ -580,12 +784,49 @@ D50 + + + + + + + + Disable initial calibration of instrument if possible
+ -O +                    + + + + + + + + + + + + + + + + + + + + + + + + + + Do one cal. or measure and exit
-H @@ -606,6 +847,14 @@ D50 + + + + + + + + @@ -631,6 +880,14 @@ Samples + + + + + + + + @@ -650,10 +907,26 @@ Samples + + + + + + + +      Override refresh, non-refresh display mode
-Y R:rate             + + + + + + + + Override measured refresh rate with rate Hz
-Y A
+ The Graph plots light wavelength on the X axis, and either absolute + or relative level on the Y axis.
+
+

Instrument 0.05

Klein K10-A
+ 0.05
+

DTP92

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Measurement Mode
+ Y Units
+
Emission
+ mW/(m².sr.nm)
Ambient
+ mW/(m².nm)
+
Emission Flash
+ mW/(m².sr.nm.s) + + + + + +
+
Ambient Flash
+ mW/(m².nm.s)
+
Reflective
+ %/nm
+
Transmissive
+ %/nm
+
+
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 @@ -833,29 +1180,33 @@ none, 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.
+ using ccxxmake, and installed using oeminst. The default and Base Calibration + types will be indicated in the usage.

The -I parameter allows specifying a - standard or custom illumination spectrum to be used as the similated - instrument illuminant when FWA compensation is used during - measurement, overriding the default D50 or CIE computation - illuminant used for FWA (see -i below). See colprof -f for a fuller explanation.
+ standard or custom illumination spectrum to be used as the simulated + 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.

The -i parameter allows specifying a - standard or custom illumination spectrum applied to reflective or transmissive - spectral data 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 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.
+ spectral data 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.

The -Q flag allows specifying a tristimulus observer, and is used to compute PCS (Profile Connection Space) @@ -930,6 +1281,11 @@ none, computer. It is advisable to only use this option on the second and subsequent measurements in a single session.

+ -O Do a calibration or a single measurement + and exit. To take a measurement with an instrument that always does + a calibration first, calibrate it and then use -O with -N. The -O + option is intended to simplify scripted use of spotread.
+
The -H option turns on high resolution spectral mode, if the instrument supports it. See Operation of particular @@ -966,6 +1322,14 @@ a + + + + + + + + @@ -982,6 +1346,14 @@ a + + + + + + + + -Y n options overrides the refresh display mode set by the -y display type selection, with -Y r forcing refresh display mode, @@ -997,12 +1369,12 @@ a
The -Y A option uses a non-adaptive integration time emission measurement - mode, if the instrument supports it, such as the Eye-One Pro or - ColorMunki. By default an adaptive integration time measurement mode - will be used for emission measurements, but some instruments support - a fixed integration time mode that can be used with display devices. - This may give increased consistency and faster measurement times, - but may also give less accurate low level readings.
+ mode, if the instrument supports it, such as the Eye-One Pro, + ColorMunki, i1d3 or K10. By default an adaptive integration time + measurement mode will be used for emission measurements, but some + instruments support a fixed integration time mode that can be used + with display devices. This may give faster measurement times, but + may also give less accurate low level readings.

The -W n|h|x parameter overrides the default serial communications flow control @@ -1041,9 +1413,13 @@ a the range 0 .. 100 for reflective or transmissive readings, and absolute cd/m^2 for display, emissive and ambient readings.

- The L*a*b* values are computed relative to a D50 100 scale white - point. (Note that using display white relative mode makes the L*a*b - relative to the display white point.)
+ By default the L*a*b* values are computed relative to a fixed D50 + 100 scale white point, so values for emissive sources are not + particularly useful.
+ Using the display white relative mode uses a Bradford chromatic + transform to transform from the measured white to a D50 white (the + same as ArgyllCMS ICC profile deals a display white), and then + computes the D50 L*a*b from that.

If Fluorescent Whiter Additive (FWA) compensated readings are to be made, then this needs to be enabled with the correct command line diff --git a/doc/targen.html b/doc/targen.html index ee12f27..3aa1bb4 100644 --- a/doc/targen.html +++ b/doc/targen.html @@ -41,6 +41,8 @@ + + 0: Print grey
            @@ -56,6 +58,8 @@ + +      1: Video grey
         @@ -72,6 +76,8 @@ + +       2: Print RGB
    @@ -95,6 +101,8 @@ + + 5: CMY
   @@ -115,6 +123,8 @@ + +        7: CMYK + Light CMK
          @@ -139,6 +149,8 @@ Red + + + Blue
        @@ -168,6 +180,8 @@ Red + +         12: CMYK + Light CM + Medium CM
@@ -190,6 +204,8 @@ Red + +            0: Additive
    @@ -218,6 +234,8 @@ Red + +           4: Black
          @@ -234,6 +252,8 @@ Red + +            5: Orange
         @@ -251,6 +271,8 @@ Red + + 6: Red
                     @@ -267,6 +289,8 @@ Red + + 7: Green
                     @@ -283,6 +307,8 @@ Red + + 8: Blue
                     @@ -299,6 +325,8 @@ Red + + 9: White
                     @@ -315,6 +343,8 @@ Red + + 10: Light Cyan
                     @@ -331,6 +361,8 @@ Red + + 11: Light Magenta
                     @@ -347,6 +379,8 @@ Red + + 12: Light Yellow
        @@ -362,6 +396,8 @@ Red + +              13: Light Black
@@ -380,6 +416,8 @@ Red + + 14: Medium Cyan
                     @@ -396,6 +434,8 @@ Red + + 15: Medium Magenta
                     @@ -412,6 +452,8 @@ Red + + 16: Medium Yellow
         @@ -427,6 +469,8 @@ Red + +           17: Medium Black
           @@ -443,6 +487,8 @@ Red + +           18: Light Light Black
-G              @@ -459,6 +505,8 @@ Red + + Generate good optimzed points rather than Fast
         @@ -498,6 +548,8 @@ Red + + Single channel steps (default 0)

-m steps
-f @@ -573,6 +631,8 @@ steps + + patches      @@ -587,6 +647,8 @@ steps + + Add iterative & adaptive full spread patches to total (default 836)
                     @@ -603,6 +665,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              @@ -899,12 +987,14 @@ device - Dump diagnostic outfile.wrl file (Lab locations)
+ + + Dump diagnostic outfile.x3d.html file (Lab locations)
-W              - Dump diagnostic outfile.wrl file (Device locations)

Usage Details and Discussion

@@ -997,6 +1089,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 @@ -1057,6 +1151,8 @@ device + + -b flags, is not to duplicate test values already created by a previous type.

@@ -1236,6 +1332,8 @@ device + + steps patches.

The -F flag and parameters is used to @@ -1253,8 +1351,16 @@ device methods are used, then the target number of points will be achieved. For this reason, the -f N -q method is probably the easiest to use.

+ The -O flag disables the normal patch + re-ordering used for display RGB sets. Displays are assumed to have + a "settling time", and the delay needed for this settling time can + be minimzed by sort the patches so that they are in an order which + minimizes the change in levels between patches. -O disables + this re-ordering, leaving the patches in whatever order they were + generated.
+
The -w flag causes a diagnostic VRML .wrl file to be created, in + href="File_Formats.html#X3DOM">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 @@ -1274,6 +1380,11 @@ device number of rows, and then adjusting the total number of patches to fill the last row or paper size, in a trial and error fashion.

+ Note that some people create charts with larger numbers of patches + for the ColorMunki by altering an Eye-One Pro chart, and making + scanning jigs to guide the instrument more accurately. This may + reduce patch reading accuracy unless suitable care is taken.
+
   Size (mm/Standard Name), No. Patches

diff --git a/doc/tiffgamut.html b/doc/tiffgamut.html index 5b67603..6aea52d 100644 --- a/doc/tiffgamut.html +++ b/doc/tiffgamut.html @@ -3,19 +3,19 @@ tiffgamut + charset=windows-1252">
xicc/tiffgamut

Summary
- Create a gamut file or VRML file of the color gamut of the contents + Create a gamut file or X3DOM file of the color gamut of the contents of a set of TIFF or JPEG image.

tiffgamut allows creation of gamut files from the pixel values in a set of TIFF and/or JPEG raster images, as defined by an ICC profile, in L*a*b* or CIECAM02 - Jab colorspace, and can also represent the gamut as a VRML file. + Jab colorspace, and can also represent the gamut as a X3DOM file. This can be used for visualizing and comparing the gamut of an image to the colorspace it is in, or a colorspace it might get transformed into, and can also be used to create an image source gamut for use @@ -29,7 +29,12 @@ intent for appearance space gamut mappings, and the same input viewing conditions to be used in collink or colprof using the -c - flag, i.e. "tiffgamut -pj -cmt sRGB.icm image.tif"
+ flag, i.e. "tiffgamut -pj -cmt sRGB.icm image.tif" See Image dependent gamut mapping using + device links for an example workflow.
+
+ 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 @@ -37,6 +42,8 @@ -v            + + Verbose
-d sres       Surface resolution @@ -45,18 +52,24 @@ emit - VRML .wrl file as well as CGATS .gam file

-n            Don't - add VRML axes or white/black point
+ + + add X3DOM axes or white/black point
-k            Add + + markers for prim. & sec. "cusp" points
-f perc       Filter by popularity, perc = percent to use

@@ -80,6 +95,8 @@ s r + + = reverse (priority: monochrome > matrix > lut)
-p oride
@@ -107,11 +126,15 @@ either    + + pe - Print evaluation environment (CIE 116-1995)
           + + pc - Critical print evaluation environment (ISO-3664 P1)
@@ -122,6 +145,8 @@ either + + mb - Monitor in bright work environment
     @@ -146,36 +171,48 @@ either s:surround   + + n = auto, a = average, m = dim, d = dark,
               + +    c = transparency (default average)
         w:X:Y:Z      + + Adapted white point as XYZ (default media white)
         w:x:y        + + Adapted white point as x, y
         a:adaptation + + Adaptation luminance in cd.m^2 (default 50.0)
         b:background + + Background % of image luminance (default 20)
         l:imagewhite Image white in cd.m^2 if surround = auto (default 250)
         @@ -196,6 +235,8 @@ f:flare      monospace;">          + + g:x:y        Glare color as x, y
-O outputfile Override the default output filename & @@ -211,11 +252,11 @@ f:flare      and is a good place to start. Small values may take a lot of time to generate, and will produce big files.

- The -w flag causes a VRML file to be produced, as well as a + The -w flag causes a X3DOM file to be produced, as well as a gamut file.

The -n flag suppresses the L*a*b* axes being created in the - VRML.
+ X3DOM.

The -k flag adds markers for each of the primary and secondary "cusp" points (Red, Yellow, diff --git a/doc/txt2ti3.html b/doc/txt2ti3.html index 5d021fc..0fc467d 100644 --- a/doc/txt2ti3.html +++ b/doc/txt2ti3.html @@ -3,17 +3,15 @@ txt2ti3 + charset=windows-1252">
profile/txt2ti3

Summary
- Convert - Gretag/Logo/X-Rite or other CGATS format RGB or CMYK test chart - results - into Argyll .ti3 - CGATS + Convert Gretag/Logo/X-Rite/Barbieri or other CGATS + format RGB or CMYK test chart results into + Argyll .ti3 CGATS format.
Usage Summary
txt2ti3 [-v] [-l limit] @@ -21,91 +19,83 @@ style="font-family: monospace;">
-2 -      create a dummy .ti2 file as well.
+ italic;">      + create a dummy .ti2 file as well.
-l limit      - set ink - limit, 0 - - - 400% (default max in file)
+ set ink limit, 0 - 400% (default max in file)
-d            Set + type of device as Display, not Output
-i            Set + type of device as Input, not Output
[devfile]     Input - Device - CMYK - target file (typically file.txt)
+ Device CMYK target file (typically file.txt)
infile        Input CIE, + Spectral or Device & Spectral file (typically file.txt)
[specfile]    Input - Spectral - file (typically file.txt)
outbasefile   Base name for output.ti3 and .ti2 - file + monospace;"> and .ti2 file

Usage Details and Discussion
- txt2ti3 takes the Gretag/Logo/X-Rite/etc. test chart - results, and converts them - into Argyll .ti3 CGATS - files.
+ txt2ti3 takes the Gretag/Logo/X-Rite/Barbieri/etc. test chart + results, and converts them into Argyll .ti3 CGATS files.
It is quite common to find profile test chart data from various standards bodies and industry organizations in one of these formats, - so it is - useful to be able to convert them for use with Argyll. ICC profiles - created using Gretag Profile Maker also commonly contain the test - chart - results embedded in the profile, inside an ICC tag.
+ so it is useful to be able to convert them for use with Argyll. ICC + profiles created using Gretag Profile Maker also commonly contain + the test chart results embedded in the profile, inside an ICC tag.

- A variety of different packaging of Gretag/Logo data can be - accepted:
+ A variety of different packaging of Gretag/Logo/X-Rite/Barbieri data + can be accepted:

1 source files, consisting of a combined device value and CIE and/or spectral values.
2 source files, consisting of a file containing the device values, and a file containing the CIE and/or spectral values.
2 source files, consisting of a file containing the device values - and - the CIE values, and a file containing the spectral values.
+ and the CIE values, and a file containing the spectral values.
3 source files, consisting of a file containing the device values, a file containing the CIE values, and a file containing the spectral values.

X-Rite ColorPort seems to produce a single source file containing - combined device value and CIE - and/or spectral values.
+ combined device value and CIE and/or spectral values.

The Gretag/Logo test chart results format seem to change with each minor release of Profile Maker, so this tool may not work in all cases.

+ Use the Barbieri .CIE file
+
The outbasefile is the - base - of the output file(s), to which txt2ti3 will automatically append a - .ti3 and .ti2 extension.
+ base of the output file(s), to which txt2ti3 will automatically + append a .ti3 and .ti2 extension.

The input files may have data that is scaled to one of three levels: 1.0, 100.0 or 255.0, and txt2ti3 attempts to guess what the - appropriate - range is, in order to scale to Argyll's standard range 0 .. 100.0.
+ appropriate range is, in order to scale to Argyll's standard range 0 + .. 100.0.

diff --git a/doc/viewgam.html b/doc/viewgam.html index 0bf5c04..9c3e3f0 100644 --- a/doc/viewgam.html +++ b/doc/viewgam.html @@ -1,125 +1,146 @@ - - viewgam - - - - -
gamut/viewgam
-
Summary
-Convert one or more gamuts into a VRML -3D visualization -file. This allows visual comparison of several gamut surfaces.
-Also allows creating the intersection (overlap) between two gamuts. -This is useful in measuring and visualizing the coverage of one gamut -of another.
-
Usage
-
-viewgam { [-c color] [-t -trans] [-w|s] infile.gam } ... outfile.wrl
-                -For each input gamut file:
- -c color        + + viewgam + + + + +
gamut/viewgam
+
Summary
+ Convert one or more gamuts into a X3DOM 3D visualization file. + This allows visual comparison of several gamut surfaces.
+ Also allows creating the intersection (overlap) between two gamuts. + This is useful in measuring and visualizing the coverage of one + gamut of another.
+
+ See 3D Viewing Format for switching to + VRML or X3D output format.
+
Usage
+
+ viewgam { [-c color] + [-t trans] [-w|s] infile.gam } ... outfile.x3d.html
+                 +For + + + each input gamut file:
+ -c color        Color to -make gamut, -r = red, g = green, b = blue
-                +make + + + gamut, r = red, g = green, b = blue
+                    -c = cyan, m = magenta, y = yellow, w = white
-                   -n = natural color
- -t trans        +c + + + = cyan, m = magenta, y = yellow, w = white
+                    +n + + + = natural color
+ -t trans        Set transparency -from 0.0 (opaque) to 1.0 (invisible)
- -w              -Show as a wireframe
- -s              -Show as a solid surface
- infile.gam      Name -of infile.gam file
-
- -n             -Don't add Lab axes
- -i Compute -and print intersecting volume of first 2 gamuts
- -I isect.gam   Same as -i, but save intersection gamut -to isect.gam
- outfile.wrl Name of output -outfile.wrl file -
-
Usage Details and Discussion
-viewgam creates a VRML file that allows the viewing and -comparing -of multiple gamut files by representing them as solid surfaces, -wireframes, -etc. It takes as input a list of gamut files, each file preceded by any -options that are to apply to the display of that particular -gamut. -
-
-The options that can be specified for each input gamut are:
-
--c color allows the color of the surface or wireframe to -be -specified. Any of a number of predefined colors (red, green, blue, -cyan, -magenta, yellow, white) can be used, as well as allowing the color to -reflect -the natural color of that point in the colorspace.
-
--t trans allows the transparency of the surface to -be -specified. A value of 0.2 might be a good place to start. Using -transparency -generally leads to a slower display than the default opaque surface -treatment, but can make it possible to see within a solid gamut surface.
-
--w forces the gamut surface to be rendered as a wireframe.
-
--s forces the gamut surface to be rendered as a solid surface.
-
-By default, the first gamut is treated as a solid with natural -coloring, -with the second and subsequent gamuts being wireframes with colors of -white, -red, cyan, yellow, green and blue, with decreasing visibility.
-
-The -n flag turns off display of the default L*a*b* axes in the -output.
-
-The -i flag computes the -intersecting volume of the first two gamuts (in cubic color units, -usually L*a*b*), as well as the volumes of the two gamuts and the -percentage the intersection is of the two gamuts. This is a useful -measure of the coverage one gamut has of another. If -I is used, then as well as printing -the volume, the intersecting gamut will be saved to the isect.gam file.
-
-The final argument is the name of the VRML file to save the resulting -composite -3D visualization file to.
-
- +from + + + 0.0 (opaque) to 1.0 (invisible)
+ -w              +Show + + + as a wireframe
+ -s              +Show + + + as a solid surface
+ infile.gam      + Name of infile.gam file
+
+ -n             +Don't + + + add Lab axes
+ -i Compute and + print intersecting volume of first 2 gamuts
+ -I isect.gam   Same as -i, but save intersection + gamut to isect.gam
+ outfile     Base + + name of output outfile.x3d.html file
+
Usage Details and Discussion
+ viewgam creates a X3DOM file that allows the viewing + and comparing of multiple gamut files by representing them as solid + surfaces, wireframes, etc. It takes as input a list of gamut files, + each file preceded by any options that are to apply to the display + of that particular gamut.
+
+ The options that can be specified for each input gamut are:
+
+ -c color allows the color of the surface or wireframe + to be specified. Any of a number of predefined colors (red, green, + blue, cyan, magenta, yellow, white) can be used, as well as allowing + the color to reflect the natural color of that point in the + colorspace.
+
+ -t trans allows the transparency of the surface + to be specified. A value of 0.2 might be a good place to start. + Using transparency generally leads to a slower display than the + default opaque surface treatment, but can make it possible to see + within a solid gamut surface.
+
+ -w forces the gamut surface to be rendered as a wireframe.
+
+ -s forces the gamut surface to be rendered as a solid + surface.
+
+ By default, the first gamut is treated as a solid with natural + coloring, with the second and subsequent gamuts being wireframes + with colors of white, red, cyan, yellow, green and blue, with + decreasing visibility.
+
+ The -n flag turns off display of the default L*a*b* axes in + the output.
+
+ The -i flag computes the + intersecting volume of the first two gamuts (in cubic color units, + usually L*a*b*), as well as the volumes of the two gamuts and the + percentage the intersection is of the two gamuts. This is a useful + measure of the coverage one gamut has of another. If -I is used, then as well as + printing the volume, the intersecting gamut will be saved to the isect.gam file.
+
+ The final argument is the base name of the X3DOM file to save the + resulting composite 3D visualization file to. If the name given + doesn't have an extension, one will be automatically added.
+
+ -- cgit v1.2.3

Measurement Mode +	Y Units +
Emission +	mW/(m².sr.nm)
Ambient +	mW/(m².nm) +
Emission Flash +	mW/(m².sr.nm.s) + + + + + + +
Ambient Flash +	mW/(m².nm.s) +
Reflective +	%/nm +
Transmissive +	%/nm +

3D Viewing Format +

ArgyllCMS's 'arts' (Absolute to media Relative Transform + Space matrix) ICC tag (V1.0) +

The problem

The solution

Conclusion

Argyll CMS documentation index (V1.6.3) +

Argyll CMS documentation index (V1.7.0)

Introduction

Copyright and Licensing: -

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

Graphic - User Interfaces -

Main - Tools and the command line -

Copyright and Licensing: +

Topical - Discussions

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

Flow - diagram of Major Tools:

Graphic + User Interfaces +

Main + Tools and the command line +

Main Tools by - category:

Calibrating devices -

Creating test targets for profiling or print calibration -

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 +

Creating Device Profiles

Creating Device Link Profiles

Converting colors or applying print calibration +

Color Tweaking tools +

Creating gamut views

Diagnostic and test tools +

Obtaining test results for profiling or print calibration -

Other Tools

Creating Device Profiles

Main Tools + Alphabetic Listing:

Creating Device Link Profiles

Converting colors or applying print calibration -

Color Tweaking tools -

Creating gamut views

Diagnostic and test tools -

Other Tools

Main Tools - Alphabetic Listing:

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.6.3 -> V1.7.0] 1st May 2015

[V1.6.2 -> V1.6.3] 26th January 2014

Setup JAM:

Fluorescent Whitener Additive Compensation (FWA Compensation)

Using FWA compensation for single, general use profiles

.ti1

X3D

X3DOM

- Installing the software

Installing the software

No device configuration needed:

USB - instruments access using udev: + instruments access using udev with existing /etc/udev/rules.d or + /usr/lib/udev/rules.d/69-cd-sensors.rules + file.

USB + instruments access using udev, with no existing /etc/udev/rules.d or /usr/lib/udev/rules.d/69-cd-sensors.rules + file. +

USB instruments @@ -404,6 +342,11 @@ instruments + + + + + access using hotplug:

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 - 1201 and 1211 -

HCFR Colorimeter

HCFR Colorimeter

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

Image dependent gamut mapping using device + links +

Soft Proofing Link

Transforming colorspaces of raster files

2) White point calibration & neutral axis calibration.

8) Viewing conditions adjustment and gamut mapping

Putting it all together:

Video Electro-Optical Transfer Functions +

Introduction

Encoding verses decoding & Viewing conditions +

3D Viewing Format
+

ArgyllCMS's 'arts' (Absolute to media Relative Transform + Space matrix) ICC tag (V1.0)
+

Argyll CMS documentation index (V1.6.3)
+

Copyright and Licensing:
-

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

Graphic - User Interfaces
-

Main - Tools and the command line
-

Copyright and Licensing:
+

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
-

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
+

Obtaining test results for profiling or print calibration
-

Converting colors or applying print calibration
-

Color Tweaking tools
-

Diagnostic and test tools
-

USB - instruments access using udev:
+ instruments access using udev with existing /etc/udev/rules.d or + /usr/lib/udev/rules.d/69-cd-sensors.rules + file.

USB + instruments access using udev, with no existing /etc/udev/rules.d or /usr/lib/udev/rules.d/69-cd-sensors.rules + file.
+

Installing the software on Apple OS X
-

Installing the software on Apple OS X
+

X-Rite EyeOne Pro
-

X-Rite EyeOne Pro
+

JETI specbos - 1201 and 1211
-

Image dependent gamut mapping using device + links
+

Video Electro-Optical Transfer Functions
+

Encoding verses decoding & Viewing conditions
+

"Pure Gamma" curves
+

Input Offset Black
+

Comments
-

Comments
+

Comments
-

Comments
+

Comments
-

Comments
+