CT&A Help
CT&A Help
(CT&A)
help manual
Version 6.0.7
Color Translator & Analyzer (CT&A) help manual
© 2004-2022 Danny Pascale
All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic,
or mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without
the written permission of the publisher.
Products that are referred to in this document may be either trademarks and/or registered trademarks of the
respective owners.
While every precaution has been taken in the preparation of this document, the publisher and the author
assume no responsibility for errors or omissions, or for damages resulting from the use of information
contained in this document or from the use of programs and source code that may accompany it. In no event
shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or
alleged to have been caused directly or indirectly by this document.
1. INTRODUCTION .......................................................................................................................................... 7
1.1 CT&A OVERVIEW ........................................................................................................................................ 9
1.1.1 QuickStart: RGB vs RGB ............................................................................................................... 11
1.1.2 QuickStart: Munsell tools ............................................................................................................... 15
1.1.3 QuickStart: Spectral tools .............................................................................................................. 16
1.2 PURCHASING, UPGRADES, LEGAL INFO ...................................................................................................... 27
1.2.1 Purchasing ..................................................................................................................................... 27
1.2.2 Upgrades ....................................................................................................................................... 27
1.2.3 License Agreement / Legal notice ................................................................................................. 28
1.2.4 Copyrights and Trademarks .......................................................................................................... 30
1.2.5 Credits ............................................................................................................................................ 30
1.3 ACTIVATION-DEACTIVATION ....................................................................................................................... 31
1.3.1 Checking activation and program version...................................................................................... 38
2. TOOLBAR WINDOW ................................................................................................................................. 39
2.1 TOOLBAR STATUS LIGHTS .......................................................................................................................... 41
2.2 SUPPORTED INSTRUMENTS ........................................................................................................................ 43
2.3 INSTRUMENT INFO ..................................................................................................................................... 45
2.4 LAMP RESTORE ......................................................................................................................................... 49
3. PREFERENCES DIALOG .......................................................................................................................... 51
4. RGB VS RGB TOOL .................................................................................................................................. 59
4.1 RGB VS RGB MENU ................................................................................................................................. 61
4.2 RGB VS RGB TABLES & GRAPHICS ........................................................................................................... 65
4.2.1 CAT matrices ................................................................................................................................. 67
4.2.2 Illuminant data ................................................................................................................................ 68
4.2.3 RGB to XYZ data ........................................................................................................................... 69
4.2.4 RGB Space data ............................................................................................................................ 70
4.2.5 ColorChecker data ......................................................................................................................... 71
4.3 RGB SPACE INTERFACE ............................................................................................................................ 73
4.3.1 Space selection.............................................................................................................................. 74
4.3.2 Sliders ............................................................................................................................................ 75
4.3.3 Data displays ................................................................................................................................. 77
4.3.4 L*a*b* / L*u*v* input ....................................................................................................................... 80
4.4 COLOR DECK INTERFACE .......................................................................................................................... 85
4.4.1 Deck selection ................................................................................................................................ 86
4.4.2 Illuminant selection ........................................................................................................................ 88
4.4.3 L*C*h pad ....................................................................................................................................... 89
4.4.4 List view ......................................................................................................................................... 92
4.4.5 Color strip ....................................................................................................................................... 93
4.4.6 Data displays ................................................................................................................................. 94
4.5 CHROMATICITY DIAGRAM ........................................................................................................................... 97
4.6 MOUSE INPUT INTERFACE ........................................................................................................................ 101
4.7 DELTAE* DISPLAY ................................................................................................................................... 103
4.8 COLOR PATCHES DISPLAYS...................................................................................................................... 105
4.9 TEXT ON BACKGROUNDS - WCAG CONTRAST RATIO ................................................................................ 109
4.10 CUSTOM RGB SPACE DIALOG ............................................................................................................. 113
4.11 MODE SETTINGS ................................................................................................................................ 119
5. MUNSELL TOOLS ................................................................................................................................... 127
5.1 MUNSELL TOOLS INTERFACE .................................................................................................................... 129
5.2 MUNSELL TOOLS INSTRUMENT INPUT ........................................................................................................ 133
1. Introduction
• Table of Contents
• CT&A overview
QuickStart guide: RGB vs RGB tool
QuickStart guide: Munsell tools
QuickStart guide: Spectral tools
• Purchasing, Upgrades, Legal info
• Activation / Deactivation
• Index
Tools Topics
• Toolbar window
• Preferences dialog
• RGB vs RGB tool
• Munsell tools
• CRI tools
• Density tools
• FluoCheck tools
• Graph tools
• ISO 3664+ tools
• Metamerism Index (MI) tools
• RAL DESIGN tool
• Whiteness tools
Other Topics
• Technical data
• Tutorials
• Version history
• Technical support
The RGB vs RGB and Munsell tools are bidirectional color-space Translator and comparator tools,
essentially the "T" of CT&A. You can use the RGB vs RGB tool to compare two colors which are within a
predefined or custom RGB space, or which are part of color chips catalogues, herein called "Color Decks." You
can convert a color from a Color Deck to an RGB space or find the closest color from an RGB space in a Color
Deck. Of course, RGB space to RGB space and Color Deck to Color Deck conversions are also possible.
Inputs can be converted to many other color spaces, such as "xyY", "XYZ", Munsell HVC", and others. The
RGB vs RGB tool does not require a color measurement instrument although data can be inputted using such
an instrument, which has to be purchased separately (a list of supported instruments is available here).
The Munsell tools enables you to convert from Munsell notation to an RGB space and L*a*b*, and the other
way around, from an RGB space or L*a*b* to Munsell notation. It can also convert measurements made with
the supported spectrophotometers to Munsell.
Important: Four spectral tools (CRI, ISO3664+, MI, RAL Design) can use a file as input, with NO connected
instrument, or input from from an instrument, if available. The other spectral tools only accept an input from an
instrument. Except for the FluoCheck tools, all spectral tools accept input from an i1Pro, i1Pro 2, or i1Pro 3
spectrophotometer, manufactured by X-Rite; the FluoCheck tools require an i1Pro 2 or i1Pro 3. Please note
that the Eye-One Display i1Display Pro, Spyder5 and SpyderX are colorimeters which measure only tristimulus
data and cannot be used with the spectral tools.
The spectral data is processed and Analysed, this is the "A" of CT&A, to provide the required information.The
spectral tools are grouped in eight windows:
• Color Rendering Index (CRI): The CRI tools comprise the current CRI method (CIE 13.3: 1995) and three
proposed replacement metrics: the Color Quality Scale (CQS, NIST Version 9.0.3), the CRI2012 (nCRI
Version 12.0), and the TM-30 Method (you can switch between versions TM-30-15 and TM-30-18/TM-30-20,
the latter being harmonized to CIE 224:2017). It also computes specifically designed metrics for gamut area
(GAI: Gamut Area Index) and memory colors (MCRI: Memory Color Rendering Index). The CRI tools accept
file input with spectral data provided in either 5 nm or 10 nm intervals; a connected instrument is not required.
A dedicated export dialog enables you to generate customized text reports.
The screenshot just below represents the RGB vs RGB window without its additional patch layouts; these
additional patches are shown on the next page.
• The LEFT and RIGHT sides both offer the selection of either "RGB Space mode" or "Color Deck mode".
• Within the RGB Space interface, data can be inserted in RGB, L*a*b* or L*u*v* coordinates, depending on
the input mode (see display/input boxes). Data fields with a grayish background do not accept input.
• In the image shown above, input for Space #1 can be done either with the sliders or the RGB input fields.
• In addition, for a Space, data can be inputted by clicking in the "xy" chromaticity diagram window (CIE1931, 2
deg.); the input is directed to the space selected in the mouse input control window.
• L*a*b*, L*u*v*, L*a*b* (D50), or L*u*v* (D50) are alternate input modes for all RGB spaces; they are selected
with the checkboxes in the bottom of the space interfaces.
• For a Deck, input can be done by clicking in any color patch surrounding the center patch, by selecting a
color within the multi-color strip, or by clicking the arrows on the top and bottom of the strip. A color chip
selection mode based on a scrolling patch list can also be selected by clicking on the "List" radio button.
• In "Compare mode", shown above, the inputs are independent of one another.
• In "Convert mode", input on one side is converted on the other side; the side being converted "TO" has all
inputs disabled.
In the screenshot below, we see the RGB vs RGB window enlarged to show extra patches and colored text.
In the bottom-left, we see larger patches presented side by side; you can select a gray, white or black
background by just clicking on the patches. In the top-right, we see the patches on different backgrounds
simultaneously. In the bottom-right, we see text of each color on white and black backgrounds, as well as on a
background of the other color; the text content, the font, and the font style and size can be edited.
The numbers which appear in the six labels located within the patches on the right indicate the Contrast Ratio
of the two colors used in each patch combination, as defined in the Web Content Accessibility Guidelines
(WCAG) 2.0. The colors of “AA” and “AAA” symbols (Green=Pass; Red=Fail) indicate compliance at these two
contrast conformance levels, AAA being the highest, for both Normal text (first label line) or Large text (second
label line). The two red or green vertical bars in the text area indicate if the contrast requirements are met for
the currently selected text size and style, which can be categorized as either Normal text or Large text.
In the screenshot below, we can enter L*a*b*/L*u*v* data on both sides. You will notice, when entering data
manually in the L*a*b* or L*u*v* data fields, that the other data displays (RGB, L*C*h, etc.) for this space are
NOT automatically updated, and a red button with "GO!" written in it appears: . To update the other
data displays, you should first enter all L*a*b* or L*u*v* values and then click on the GO! button (alternately,
press the Return or the Enter key). This manual refresh procedure was devised because the L*a*b* and L*u*v*
spaces can describe the entire visible spectrum while the R'G'B' spaces only represent a subset of it. When
entering data, it is very likely that the color described by the input data is outside of the R'G'B' space gamut,
and clipping will occur; in such a case, clipping will be flagged by one or more red exclamation points located
below the "R", "G", and "B" labels. If you press the "GO!" button when clipping is flagged, the software will
select the closest color corresponding to the input data within the RGB space.
For more information on the RGB vs RGB tool, go to the following section:
• RGB vs RGB tool
• Text and WCAG data
• Custom RGB space dialog
• Mode Settings (Compare, Convert, etc.)
• The Munsell tools can accept user-typed input and input from a supported spectrophotometer. A
CONNECTED INSTRUMENT IS NOT REQUIRED in order to use these tools.
• Please note that some controls will remain disabled and some data fields will not be available (shown as
"N.A.") if the program is not activated.
• Click on "Save to file..." to save a report of the tools data, including the measured spectral data if applicable.
User-typed input
• Input is on the left side of the window and output on the right side. From top to bottom you can: input RGB
and get Munsell Hue Value/Chroma (HVC); input Munsell HVC and get both RGB and L*a*b* outputs; input
L*a*b* and get Munsell HVC.
• The RGB space for both input and output is selected in the RGB input section. The list of RGB spaces is the
same as the one available in the RGB vs RGB tools, including the Custom RGB space. You can thus define
a Custom RGB space in the RGB vs RGB tool and use it in the Munsell tools.
• The illuminant assigned to both input and output L*a*b* is selected in the L*a*b* input section. The list of
illuminants comprises many standard Illuminants, including the Custom illuminant assigned to the Custom
RGB space in the RGB vs RGB tool.
• Using popup menus available with a right-click over the input and output fields, as well as dedicated buttons
and checkboxes of the interface, you can assign the output of a conversion to the input of another. You can
thus evaluate the overall “roundtrip” accuracy of the conversion. This accuracy is affected by rounding,
clipping, interpolation and extrapolation accuracy, and the sparsity of the Munsell reference database.
• The CIELAB or CIEDE2000 color difference between the input L*a*b*, which may come from a reference or a
measurement, and output L*a*b*, from the Munsell to L*a*b* conversion, is shown in the L*a*b* input section.
Do a right-click over the Delta-E data fields to select the color difference formula.
Instrument input
• For instrument input, it is assumed that your instrument is properly connected and detected, as discussed in
the beginning of this section, and that the "Calibrate" and "Measure" buttons are enabled.
• If you are using an i1Pro 2 with the "i1Pro / i1Pro 2 (XRGA)" driver, an i1Pro 3, or an i1Pro 3 Plus, all
measurements will be taken with the three "Measurement Conditions", M0 (Ill-A), M1 (D50), and M2 (UV-cut).
If you are using an i1Pro, or an i1Pro 2 with the "i1Pro / i1Pro 2 (non-XRGA)" driver, the program will select
the default measurement conditions supported by the instrument and data will not be shown for the other
measurement conditions (Note: Munsell coordinates are provided only in reflectance mode).
• Setup-1: If using an instrument, calibrate it by clicking on the "Calibrate" button.
Four spectral tools (CRI, ISO 3664+, MI, RAL Design) can use a file as input, with NO connected instrument,
or input from from an instrument, if available. The other spectral tools only accept an input from an instrument.
The FluoCheck tools require an i1Pro 2 or i1Pro 3, all other spectral tools accept inputs from an i1Pro, i1Pro 2,
or i1Pro 3 spectrophotometer, manufactured by X-Rite. The Density and Graph tools also support the M3
Measurement Conditions when using the i1Pro 3 Plus, which has a Polarizer head adapter. Here are the
possible configurations:
Important: For all spectral tools which do not support file input, you need to have an i1Pro, i1Pro2, or i1Pro 3
spectrophotometer connected to the computer on which CT&A is running.
Note: Some versions of the i1Pro and i1Pro 2 are not fitted with an ambient adapter. These instruments are
usually bundled with dedicated software sold by a third party vendor (i.e. NOT X-Rite).
Before taking measurements, the instrument must be properly recognized by the program; this is confirmed by
a small green light beside the instrument selection menu in the toolbar window, and by the "Calibrate" and data
entry buttons of the tools' window being enabled (some data entry buttons and controls will remain disabled
and some data fields will not be available if the program is not activated). If you plug an instrument in your
computer after the program start, you can attempt to connect the instrument by selecting "Try to connect
again..." in the Instrument menu. A status of the selected instrument can always be obtained by clicking on the
"Info" button located in the toolbar window.
Note: In Windows, if the i1Pro/ i1Pro 2 or i1Pro 3 USB drivers are not installed, please consult the
"CT&A_Readme.txt" file located within the main CT&A application folder. This file can be opened directly with
the "Start menu/BabelColor/CT&A Readme" shortcut.
You can click (left-click) on the indicator to move it to the previous measurement if required, or do a right-click
to lock it on a given measurement. You can also do a left-click on a locked indicator; the new position will be
locked.
In each tool, only the measurement modes (Ambient, Emission, Reflectance, or Flash) compatible with the tool
and the instrument can be used. Some tools require/offer more than one measurement mode. At all times, you
can calibrate the current tool measurement mode by clicking the "Calibrate" button located in the bottom-left of
each tool window.
The "Save to file...", "Save image...", "Save report...", "Save meas...", and "Print report..." buttons are
shown in the bottom of a tool window when the related features are available. Clicking the "Close" button will
close a tool window without erasing the current data; opening the tool again using the toolbar or the "Tools"
menu will bring back a tool window in its last used state. However, all tool data should manually be saved
before closing the program since this data is not automatically saved with this action.
• The CRI tools can accept input from a file or from a supported instrument. A CONNECTED INSTRUMENT IS
NOT REQUIRED in order to use these tools. Information of the supported metrics is presented in the CRI
tools description section.
• Please note that only the interface and processed data related to the standard CRI (CIE 13.3: 1995) is shown
when the program is not activated. The interface and processed data for the other metrics is not available.
• For instrument input, it is assumed that your instrument is properly connected and detected, as discussed in
the beginning of this section, and that the "Get Ambient", "Tune" and "Calibrate" buttons are enabled. It is
also assumed that your instrument supports the use of an ambient adapter as some versions of the i1Pro
and i1Pro 2 are sold without this capability.
• The instrument should be calibrated before making any measurements. Click on the "Calibrate" button of the
CRI window and follow the indications to perform an "Ambient" mode calibration.
• File input: At any time, you can use a data file as input in place of a measurement. A file may contain one or
more spectrums. Acceptable file formats are described in the CRI input file requirements section. There are
two methods to open/load a file:
• 1st method: Click on the "Load..." button and select the file to open with the file input dialog.
• 2nd method: Drag-and-drop the file to open on the "Load..." button OR on the table located beside
the input buttons. You can also drag-and-drop multiple files at a time.
• When the table contains multiple measurements, select the measurement for which you want to see the
processed data by clicking in one of the first two columns of a row. Do a right-click on the measurements
table to erase all measurements or only the selected ones, or rename all measurements.
• Click on "Save to file..." to open the CRI file options dialog. You can save all data in a single file or each
measurement in a separate file, or both.
• Click on "TM-30-20 reports..." to open the TM-30-20 report selector dialog. You can save TM-30-20 reports
as images formatted as per the recommended “Simple”, “Intermediate” or “Full” formats.
• It is assumed that your instrument is properly connected and detected, as discussed in the beginning of this
section, and that the "Calibrate" and "Get x" buttons are enabled. Please note that some data entry buttons
and controls will remain disabled if the program is not activated.
• Setup-1: If you are using an i1Pro 3 with an “i1Pro 3” driver, or an i1Pro 2 with the "i1Pro / i1Pro 2 (XRGA)"
driver, you can select the "Measurement Conditions": M0 (Ill-A), M1 (D50), M2 (UV-cut). In addition, for the
i1Pro 3 Plus, the M3 (Pol., i.e. Polarized) Measurement Conditions are available. If you are using an i1Pro, or
an i1Pro 2 with the "i1Pro / i1Pro 2 (non-XRGA)" driver, the program will select the default measurement
conditions supported by the instrument.
• Setup-2: Select a "Measurement type": Reflection density, Dot Area, Print Contrast, Hue error - Grayness -
Saturation. Data is kept independently for each measurement type.
• Setup-3: Select a "Density standard" defined as per ISO 5-3: Status A, Status E (DIN), Status I (DIN NB,
SPI), Status T. You can change the density standard at any time; all previous measurements will be
recomputed according to the selected standard.
• Setup-4: If required, select a "Formula" (for Dot Area and Apparent Trap) and set the "n Factor" (for Dot
Area/Yule-Nielson).
• Setup-5: If available, select a "White base" (for Reflection density, Print Contrast, Hue error - Grayness -
Saturation).
• Setup-6: If available, select the "Filter" mode (for Reflection density, Dot Area, Print Contrast).
• Setup-7: Calibrate the instrument by clicking the "Calibrate" button.
• If "Paper" is selected for the "White base", click on the "Get" button and follow the instructions.
• Up to five sets of measurements can be done for each Density tool. Select the measurement set by clicking
on a radio button in the "Measurement control" group. You should also see the selected number (#1, #2, etc.)
in the upper-left cell of the data table.
• To automatically change the measurement number in the "Measurement control" group, simply check the
"Auto-select" box.
• Once a measurement is completed, you can grab it as the reference using the "Grab (Ref.)" button.
• Once there is at least two complete measurements, you can display the average by checking the "Show
avg." box. You can grab the average as the reference.
• Click on "Save to file..." to save the data of the selected "Measurement type". You can also save the data
acquired in all Density tools.
• Note: The measurements made with the M3 Measurement Conditions are separate from those made with
the M0/M1/M2 Measurement Conditions which are recorded at the same time.
• Important: An i1Pro 2 which supports the M0 (Ill-A), M1 (D50), and M2 (UV-cut) Measurement Conditions is
required to use these tools (an i1Pro cannot be used!).
• Setup-1: In the toolbar window, you must select the "i1Pro / i1Pro 2 (XRGA)" driver.
• It is assumed that your i1Pro 2 is properly connected and detected, as discussed in the beginning of this
section, and that the "Calibrate", "Get Ref.", and "Get Sample" buttons are enabled. Please note that some
controls will remain disabled and some data fields will not be available (shown as "N.A.") if the program is not
activated.
• Setup-2: Select an "Observer"; data will be updated if it is changed after a measurement is done.
• Setup-3: Select the "FI formula", a Color difference formula, for the "Fluorescence Index" (FI); data will be
updated if it is changed after a measurement is done. This setting does not affect the "Fluorescence
Metamerism Index" (FMI) value which is always computed using the CIELAB color-difference formula.
• Setup-4: Calibrate the instrument by clicking the "Calibrate" button.
• To erase a measurement, first press the Alt key, in Windows, or the Option key on a Mac. Whenever the
mouse cursor is within the tool window, the "Get Ref." or "Get Sample" buttons will change their caption to
"Clear" (if there is a measurement).
• The Fluorescence Metamerism Index (FMI) is computed when there is a Reference and a Sample. The FMI
is obtained by using the M2 measurements of the two colors, and either the M0 or M1 measurements (a
different FMI is computed relative to M0 and M1). There is no need for a perfect match under one Illuminant.
• Click on "Save to file..." to save a "Fluorescence report".
• It is assumed that your instrument is properly connected and detected, as discussed in the beginning of this
section, and that the "Calibrate" and "Get Sample" buttons are enabled. Please note that some controls will
remain disabled if the program is not activated.
• Setup-1: Select a measurement "Mode" in the "Next sample" group: Emission, Ambient, Reflectance, Flash.
Different modes can be used for each sample. For reflectance measurements, and if you are using an i1Pro
3 with an “i1Pro 3” driver, or an i1Pro 2 with the "i1Pro / i1Pro 2 (XRGA)" driver, you can select the
"Measurement Conditions": M0 (Ill-A), M1 (D50), M2 (UV-cut). In addition, for the i1Pro 3 Plus, the M3 (Pol.,
i.e. Polarized) Measurement Conditions are available. If you are using an i1Pro, or an i1Pro 2 with the "i1Pro
/ i1Pro 2 (non-XRGA)" driver, the program will select the default measurement conditions supported by the
instrument.
• Setup-2: Select the "Illuminant" and "Observer" that will be used to compute the colorimetric data (L*C*h,
xyY, etc.); data will be updated if they are changed after a measurement is done.
• Setup-3: Select the data type (L*C*h, xyY, etc.) and the color difference formula that will be computed with
the acquired data; data will be updated if they are changed after a measurement is done.
• Setup-4: Calibrate the measurement mode shown in the "Next sample" group by clicking the "Calibrate"
button.
2
• When a measurement is made in "Emission", "Ambient" or "Flash" mode, the photometric quantity, cd/m ,
lux, or lux-sec is shown for this sample.
• When a measurement is made in "Ambient" or "Flash" mode, the Correlated Color Temperature (CCT, in
kelvin) and Color Rendering Index (CRI) of the sample are shown. You can compare such spectrums against
an ideal illuminant by selecting the "S1 vs Illum." or "S2 vs Illum." radio button.
• You can see the numerical coordinates of the spectrums by moving the mouse over the graphs.
• To erase a measurement, first press the Alt key, in Windows, or the Option key on a Mac. Whenever the
mouse cursor is within the tool window, the "Get Sample" buttons will change their caption to "Clear" (if there
is a measurement).
• Mathematical operations can be performed with the spectrums. The operations are enabled according to the
measurement modes of both samples.
• Click on "Save to file..." to save the spectral data or on "Save image..." to save an image of the display.
• The ISO 3664+ tools can accept input from a file or from a supported instrument. A CONNECTED
INSTRUMENT IS NOT REQUIRED in order to use these tools.
• Please note that some data entry buttons and controls will remain disabled and some data fields will not be
available (shown as "N.A.") if the program is not activated.
• For instrument input, it is assumed that your instrument is properly connected and detected, as discussed in
the beginning of this section, and that the "Calibrate", "Tune", "Test" and "Take all" buttons are enabled.
• Setup-1: Select the "VIEWING CONDITIONS". If "Color monitors" is selected, the Color Rendering Index
(CRI) and Metamerism Index (MI) tests are not required, and not shown in the dialog.
• Setup-2: Select the chromaticity "Target center"; selecting "Goal" will show the tolerance required by ISO
3664. Data will be updated if the target center is changed after a measurement is done.
• Setup-3: Select the "Ref. Illuminant" for the Color Rendering Index (CRI); D50 is required by ISO 3664.
Selecting "Auto" will compute the CRI based on the measured temperature, in kelvin; a D-series illuminant
will be selected for color temperatures ≥ 5000 K, and a blackbody will be selected for color temperatures
below 5000 K. Data will be updated if the reference illuminant is changed after a measurement is done.
• Setup-4: Select the "Ref. Illum." for the Metamerism Index (MI) determined as per ISO 23603/CIE S 012; D50
is required by ISO 3664. Data will be updated if the reference illuminant is changed after a measurement is
done. This test gives a Quality Grade, from "A" to "E", with "A" being the best grade, to the measured
illumination relative to the selected ideal illuminant.
• Select one of the positions. There are either 9 or 25 positions depending on the selected Viewing Condition
and ISO 12646 version (for color monitors). A complete set of measurements can be taken for each position.
• Setup-5: Calibrate the instrument by clicking the "Calibrate" button.
• File input: At any time, when not tuning, you can use a data file as input in place of a measurement. A file
must contain only one (1) spectrum. Acceptable file formats are described in the input file requirements
section. There are two methods to open/load a file:.
• 1st method: Click on the "Load..." button and select the file to open with the file input dialog.
• 2nd method: Drag-and-drop one (1) file on the "Load..." button.
• A test result will be shown as PASS or FAIL. A green colored PASS indicates that the test meets the
requirements of ISO 3664. A yellow colored PASS indicates that the test meets the selected goal but this
goal is not the one recommended by ISO 3664.
• When a measurement is made in more than one position, the relative brightness of each position is shown in
the "Brightness uniformity" group.
• To rapidly take a measurement at each position, select the "Take all" button. The input position will
automatically change after each click on the "Test" button or press of the instrument button. If the "Color
monitors" viewing condition is selected, the program can automatically draw either White, Grey, or Dark-Grey
targets at the prescribed screen positions.
• Click on "Save to file..." to save the measured data and all derived results.
• Click on "Print report..." to print a well-formatted one-page report which contains information dedicated to
compliance-type reports.
• The Metamerism Index tools can accept input from a file or from a supported instrument. A CONNECTED
INSTRUMENT IS NOT REQUIRED in order to use these tools.
• Please note that some controls will remain disabled and some data fields will not be available (shown as
"N.A.") if the program is not activated.
• For instrument input, it is assumed that your instrument is properly connected and detected, as discussed in
the beginning of this section, and that the "Calibrate", "Get Ref.", and "Get Sample" buttons are enabled.
• Setup-1: Select the "Measurement Conditions": If you are using an i1Pro 2 with the "i1Pro / i1Pro 2 (XRGA)"
driver, an i1Pro 3, or an i1Pro 3 Plus, you can select M0 (Ill-A), M1 (D50), or M2 (UV-cut). If you are using an
i1Pro, or an i1Pro 2 with the "i1Pro / i1Pro 2 (non-XRGA)" driver, the program will select the default
measurement condition supported by the instrument. For file input, select a colorimeter in the toolbar; this will
disable instrument input for all spectral tools but will enable all measurement conditions in this dialog.
• Setup-2: Select an "Observer"; data will be updated if it is changed after a measurement is done.
• Setup-3: Select the "CII/SMI formula", a color difference formula used for the Color Inconstancy Index (CII),
the Special Metamerism Index (SMI), and the CIE15 Metamerism Index (MI). Data will be updated if it is
changed after a measurement is done. This color difference formula does not affect the HunterLab MI value
which is based on the CIELAB color-difference formula.
• Setup-4: If required, click the "Get Ambient-1" or "Get Ambient-2" button to acquire an ambient illumination
(follow the on-screen instructions). Once acquired, you can save the spectrum in a standard CGATS file
format. You can also load an ambient spectrum from file (ambient file requirements).
• Setup-5: In the middle-left of the window, select the Reference illuminant and Test illuminant that will be used
for metamerism evaluation; data will be updated if either is changed after a measurement is done.
• Setup-6: Select the reference illuminant for CII computation ("CII ref. illum."). Recommended illuminant: D65.
• Setup-7: If using an instrument, calibrate it by clicking on the "Calibrate" button.
• File input: At any time, you can use a data file as input in place of a measurement. A file may contain one or
more spectrums. Acceptable file formats are described in the MI input file requirements section.
• To erase an instrument measurement, first press the Alt key, in Windows, or the Option key on a Mac.
Whenever the mouse cursor is within the tool window, the "Get Ref." or "Get Sample" buttons will change
their caption to "Clear" (if there is a measurement).
• A Color Inconstancy Index (CII) is computed independently for both the Reference and the Sample, and for
each selected illuminant. The CII is computed relative to the CII reference illuminant as selected in "Setup-6".
For example, if D65 is selected as the CII reference, the CII will be zero if D65 was also selected in "Setup-5".
• A color difference (DeltaE*) is computed between the Reference and the Sample for both illuminants of
"Setup-5" above. If the Reference and Sample match, or nearly match, under one Illuminant, the color
difference obtained for the Illuminant which does not match is called the Special Metamerism Index (SMI).
• The CIE15 and HunterLab Metamerism Indices (MI) are computed when there is a Reference and a Sample.
There is no need for a perfect match under one Illuminant.
• Click on "Save report..." to save a "Metamerism Index report", with all the results and the measurements data
or on "Save meas..." to save the Reference and Sample patches spectrums in a CGATS format text file.
• The RAL DESIGN tool can accept input from a file or from a supported instrument. A CONNECTED
INSTRUMENT IS NOT REQUIRED in order to use this tool.
• Please note that some data fields will not be available (shown as "N.A. in demo") if the program is not
activated.
• For instrument input, it is assumed that your instrument is properly connected and detected, as discussed in
the beginning of this section, and that all buttons are enabled.
• If you are using an i1Pro 2 with the "i1Pro / i1Pro 2 (XRGA)" driver, an i1Pro 3, or an i1Pro 3 Plus, all
measurements will be taken with the three "Measurement Conditions", M0 (Ill-A), M1 (D50), and M2 (UV-cut).
If you are using an i1Pro, or an i1Pro 2 with the "i1Pro / i1Pro 2 (non-XRGA)" driver, the program will select
the default measurement conditions supported by the instrument and data will not be shown for the other
measurement conditions (Note: RAL DESIGN coordinates are provided only in reflectance mode).
• Setup-1: If using an instrument, calibrate it by clicking on the "Calibrate" button.
• File input: At any time, you can convert spectral data in a file to RAL DESIGN values in place of a
measurement. A file may contain one or more spectrums. Acceptable file formats are described in the RAL
DESIGN input file requirements section. The input data is immediately converted and saved in a CGATS
format text file. There are two methods to open/load a file:
• 1st method: Click on the "Load file..." button and select the file to open with the file input dialog.
• 2nd method: Drag-and-drop the file to open on the "Load file..." button. You can also drag-and-
drop multiple files at a time.
• Click on "Save to file..." to save a "RAL DESIGN report" based on instrument measurements, i.e. not from
file input.
• Important: If using an i1Pro, fluorescence measurements require a thin, transparent, UV filter, which is not
provided and must be purchased separately; in addition, the i1Pro must NOT be UV-cut. If using an i1Pro 2
or i1Pro 3 which supports the M0 and M2 Measurement Conditions, a separate filter is not required. If your
i1Pro 2 only supports the M2 (UV-cut) measurement condition, it cannot be used with this tool. The
whiteness measurements require compliant white or black backings, which are also not provided; however,
you can easily check white and black backings compliance with the provided tools.
• It is assumed that your instrument is properly connected and detected, as discussed in the beginning of this
section, and that the "Calibrate" as well as all the data entry buttons are enabled. Please note that some data
entry buttons and controls will remain disabled and some data fields will not be available (shown as "N.A.") if
the program is not activated.
• Setup-1: If you have an i1Pro 2 or i1Pro 3 which supports the M0 and M2 Measurement Conditions, you can
select to use either an external UV filter or the internal filter associated to M2 measurements.
• Setup-2: Select the "Whiteness" formula; a common choice is "CIE-GANZ 82".
• Setup-3: Calibrate the instrument by clicking the "Calibrate" button.
• For a full measurement sequence when using an external filter, first place a blank sheet of paper on a
compliant white backing and press on the "Paper on Wh" button. This will give you the paper Whiteness and
Tint, and its Brightness. Then place the UV filter on the paper and press on the "Paper w/filter" button. This
will give you the Brightness w/filter, and the Fluorescence. Finally, remove the UV filter and place the paper
on a compliant black backing and press on the "Paper on Bk" button. This will give you the Opacity.
• For a full measurement sequence when using an i1Pro 2 or i1Pro 3 with the M2 mode, first place a blank
sheet of paper on a compliant white backing and press on the "Paper on Wh" button. This will give you the
paper Whiteness and Tint, its Brightness, the Brightness w/filter, and the Fluorescence. Secondly, place the
paper on a compliant black backing and press on the "Paper on Bk" button. This will give you the Opacity.
• To check a backing compliance, place your instrument on the backing and click on the relevant "Check..."
button. A short message with data will be shown against the button.
• When making measurements with an external filter, this tool requires the transmission spectrum of the UV
filter to process the "Paper w/filter" measurement. The program comes with filter data obtained from a
commercial filter which may be different from the filter you use, even if of the same brand. We strongly
recommend that you characterize your own filter. This is done by first measuring a white backing (using the
"Check Wh back." button, and then measuring the transmission of the filter on this same backing with the
"Get new UV filter" button; the two measurements are processed to extract the filter transmission properties.
The measured filter becomes the default filter afterwards, even if you do not save it in a file; you can export
the filter spectrum in a separate file if you wish, or load a filter spectrum from file (this is useful to restore the
default filter if required; the file is provided in the "UV-filters files" folder located within the CT&A application
folder). Please consult the Whiteness tools section for more info on UV filter measurement.
• To see the spectrum of one of the inputs, check the corresponding box in the "Show" group.
• Click on "Save to file..." to save the spectral data and all the derived data, or on "Save image..." to save an
image of the display.
1.2.1 Purchasing
Important:
• You need to purchase a license in order to receive a Product Key which enables all of the program's
features.
• The software will remain in a limited-features mode as long as it is not activated with the Product Key.
If you decide to purchase this program, please go to our Web site and look for the link to our "Store" page. This
page will provide detailed instructions, and a link to our secure third party payment processor.
If you have a problem with the Web purchasing process or if you have special requirements, click on the
following link to send us an e-mail:
info@babelcolor.com .
1.2.2 Upgrades
A Product Key remains valid for fractional changes in the software version. For example, it will be possible to
use the same key for versions 6.0 up to, but not equal to, 7.0. For this reason, you should keep the e-mail
containing your Product Key in a secure place; you will also need this information if you install the program on
another computer. Please note that no other Product Key will be sent if you lose it or if it gets stolen.
You can check the program version and the activation status in the “About CT&A” dialog.
Upgrading from version 6.x to version 7.x may require additional purchasing.
LICENSE GRANT
The BabelColor Company ("BabelColor") grants you a non-exclusive license ("License") to use the Color
Translator & Analyzer software ("CT&A"), and any associated files and documentation, hereby collectively
called "The Software", as indicated herein.
You MAY:
a) install and use the Software in evaluation mode with limited features as long as you wish;
b) after purchasing a License and receiving a Product Key (also called a License Code), activate the
software with the Product Key and use the activated Software, with all features, on a single (one)
computer per purchased License (a single Product Key may correspond to one or more Licenses);
c) for a Product Key valid for one License, activate your Product Key on another computer as long as you
first deactivate the computer on which the program is currently activated;
d) for a Product Key valid for two or more Licenses, activate and deactivate computers from the same
Company as long as the number of activated computers does not exceed the number of purchased
licenses.
RESTRICTIONS
You MAY NOT:
a) sell or resell this Software package;
b) transfer a License;
c) distribute or offer for download the Software without a written agreement with BabelColor;
d) cause or permit reverse engineering, disassembly, decompilation or alteration of this Software;
e) remove any product identification, copyright notices, or other notices or proprietary restrictions from this
Software;
f) copy the documentation accompanying the Software;
g) extract the data contained in the Color Decks database and publicly distribute it, or offer it for resale, or
use it within another product, without a written agreement with BabelColor.
DATA EXCHANGE
In the activation process, the Software generates a "fingerprint" from hardware components to uniquely and
anonymously identify the computer. The Product Key and the “fingerprint” are sent to an activation server which
sends back an activation certificate. The activation server will also record network related data from where the
request comes from.
TERM
This License is effective until terminated. You may terminate it at any time by destroying the Software, together
with all copies thereof. This License will also terminate if you fail to comply with any term or condition of this
Agreement. Upon such termination, you agree to destroy the Software, together with all copies thereof.
COPYRIGHT/OWNERSHIP
This Software and its source code are proprietary products of BabelColor and are protected by copyright and
other intellectual property laws.
DISCLAIMER OF DAMAGES
BabelColor assumes no liability for damages, direct or consequential, which may result from the use of the
Software, even if BabelColor has been advised of the possibility of such damages.
,
as well as "CT&A" and "PatchTool", are trademarks of Danny Pascale and the BabelColor Company.
• "Adobe", "Adobe Gamma" and "Photoshop" are registered trademarks of Adobe Systems Incorporated.
• "Apple", "ColorSync", "Mac", "Mac OS", “macOS” and "Macintosh" are registered trademarks of Apple
Computer Incorporated.
• "ColorMatch" and "Radius" are registered trademarks and "Digital Origin" and "PressView" are trademarks of
Digital Origin. (Note: company status unknown)
• "Fujichrome" is a trademark and "Velvia" is a registered trademark of the Fuji Photo Film Co., Ltd.
• "GretagMacbeth" is a trademark, and "ColorChecker", "Munsell" and "Eye-One" are registered trademarks of
GretagMacbeth. GretagMacbeth is wholly owned by X-Rite Incorporated.
• "Idealliance" is a registered trademark of International Digital Enterprise Alliance, Incorporated.
• "Kodak" and "Ektachrome" are trademarks of the Eastman Kodak Company.
• "Pantone" is a registered trademark of Pantone, Incorporated.
• "RAL" and "RAL DESIGN" are registered trademarks of the RAL German Institute for Quality Assurance and
Certification e.V.
• "SGI" and "Silicon Graphics" are registered trademarks of Silicon Graphics Incorporated.
• "SoLux" is a registered trademark of Tailored Lighting, Incorporated.
• "Sony" and "Trinitron" are registered trademarks of Sony Corporation.
• "SWOP" is a registered trademark of SWOP, Inc. Since 2005, SWOP is a Program within Idealliance.
• "Windows" is a registered trademark of Microsoft Corporation.
• "X-Rite" is a registered trademark of X-Rite Incorporated.
1.2.5 Credits
DEVELOPED BY
• Danny Pascale, programming, documentation, etc.
SPECIAL THANKS TO
• Sylvie, for her support and understanding.
• Marti Maria, for his free lcms (Little Color Management System, or LittleCMS) color software libraries
( https://www.littlecms.com/ ).
• Jordan Russell, for Inno Setup, a free, and really good, installer for Windows applications
( https://www.jrsoftware.org/ ).
• All friends and customers who helped improve this product by their comments, questions, bug reports and
request for enhancements.
Copy/Paste shortcuts:
• Windows: To copy, press the Ctrl + C keys; to paste, press the Ctrl + V keys.
• Mac: To copy, press the Command () + C keys; to paste, press the Command () + V keys.
When you click on the “Activate” button, the following activation agreement dialog opens:
If you know that you DO NOT have an Internet connection, you should still click on the “I agree !” button; the
program will try to communicate with the activation server and will open an offline activation dialog if the
communication fails. Offline activation and deactivation is discussed later in this section.
You can check if your program is properly activated with the “About CT&A…” menu.
Note: If you have an Internet connection and activation fails, you may need to unblock some specific
communications ports used by the program. Activation requires that ports 80 and 443 be open. Please consult
your company’s network specialist for help.
Here are shortcuts to sub-sections discussing specific dialogs used to manage your Product Key:
• Deactivation / Transfer
• Reactivation
• Offline activation
• Offline deactivation
Deactivation / Transfer
If you wish to use the program on another computer, you must first deactivate the computer on which your key
is being used. To deactivate, select the “Help/Deactivate…” menu command; you will get the following dialog.
When deactivating, you have the choice to erase or not the Product Key. As indicated in the dialog, erasing the
key is recommended if you temporarily installed the program on a customer’s computer. You would similarly
erase the key if the program was installed on a computer which will foreseeably not be used with CT&A in the
future. On the other hand, if you intend to reuse CT&A on this computer soon or on a regular basis, you should
just deactivate without erasing the key.
If you know that you DO NOT have an Internet connection, you should still click on either the “Deactivate and
Erase” button or the “Deactivate” button; the program will try to communicate with the activation server and will
open an offline deactivation dialog if the communication fails. Offline activation and deactivation is discussed
later in this section.
Important: If your Product Key is valid for one (1) license, it is your responsibility to deactivate a computer
before activating another one with the same key. BabelColor cannot remotely deactivate a computer, so make
sure your first computer is deactivated before moving to the second computer.
This dialog is the same which appeared when the program was installed and not activated, except that the first
characters of the Product Key are now shown, with the last characters hidden. The last characters are hidden
for theft protection, to prevent a casual user from copying the key. However, you do not need to replace the
interrogation points (?) with the correct values to reactivate; just click on the “Activate” button. As you see, you
can use the same key to activate the program on many computers. Please note that you can only
simultaneously activate a number of computers corresponding to the number of licenses assigned to the key; if
you purchased one license, then you can activate one computer at a time.
Important: If your Product Key is valid for one (1) license, it is your responsibility to deactivate a computer
before reactivating another one with the same key. BabelColor cannot remotely deactivate a computer, so
make sure your first computer is deactivated before moving to the second computer.
As mentioned in the dialog, a service fee is required for each offline activation. This fee covers the time to
manually process the request and set the activation server. The activation fee can be purchased online on the
BabelColor Web Store page. The fee is not required to view the offline dialog, which is shown below and which
appears when you click on the “Show offline dialog” button.
The first step is to save an “Activation request file”. The default location proposed by the program is the
“BabelColor” folder located within your “Documents” folder. The file name will start with “ActivationRequest-
CTA6_” followed by the first characters of your Product Key.
As indicated in STEP-2, you must send the file to BabelColor. We will verify that you purchased the activation
service fee and we will generate an “Activation file” by e-mail. You can now close this dialog; the program will
start in evaluation mode, with limited features. Please allow a few working days to complete the process.
To perform STEP-3, you should redo the activation process from the beginning, either by starting the program
or with the “Help/Activate…” menu command. When you get to the offline activation dialog, load the “Activation
file” by first clicking on the corresponding button. You will get a confirmation message once the “Activation file”
is processed; you can also check if your program is properly activated with the “About CT&A…” menu.
Important: When you receive the “Activation file” you should use it promptly since this file is valid for a few
days only. However, please note that the activated program has no expiry date.
The “Deactivate/Save Deactivation file” button will be enabled when the missing characters of the Product
Key are replaced by their correct values. You will find the complete key in the e-mail you received when you
purchased the software. This procedure insures that a casual user will not deactivate the program by mistake.
Important: In fact, the program gets deactivated when you SAVE the “Deactivation request file” after pressing
the “Deactivate/Save Deactivation file” button; this gives you one last chance to cancel deactivation. However,
even if the program is deactivated, the deactivation process is not completed until you send the “Deactivation
request file” to BabelColor.
The deactivation options are the same as those available when you deactivate with a live Internet connection.
Erasing the key is recommended if you temporarily installed the program on a customer’s computer. You would
similarly erase the key if the program was installed on a computer which will foreseeably not be used with
CT&A in the future. On the other hand, if you intend to reuse CT&A on this computer soon or on a regular
basis, you should just deactivate without erasing the key.
The “Deactivation request file” file name will start with “DeactivationRequest-CTA6_” followed by the first
characters of your Product Key. Once the “Deactivation request file” is saved, you get a message confirming
deactivation; the message will also specifically mention that the Product Key was erased if you selected this
option. You should now send the deactivation request file to BabelColor to complete the offline deactivation
process.
Important: It is mandatory to send the “Deactivation request file” to BabelColor if you intend to ACTIVATE
another computer OFFLINE with the same Product Key. We will not issue a new offline “Activation file” for the
same Product Key if we do not receive first the “Deactivation request file” from the previous computer.
However, nothing prevents you from deactivating ONLINE if you can connect the computer to the Internet; this
is equivalent to a complete offline deactivation procedure.
The dialog also shows the current program version. Clicking on the Web link will launch your default Web
browser and open the BabelColor home page. Clicking on the e-mail address will open your default e-mail
application.
You will notice that only part of the Product Key is shown; its last characters are hidden to prevent a casual
user from steeling your license. However, the remaining numbers are still sufficient to identify who purchased
the product in case you require product support. As discussed in more details in the Activation-Deactivation
section, you can deactivate CT&A on a computer and activate the software on another computer with the same
Product Key. When deactivating, you can decide to erase or not the product key. If the product key is not
erased on a given computer, you can reactivate this computer without entering the Product Key (and assuming
that the Product Key is not activated over its prescribed limit on other computers). If the Product Key is erased,
you will need to re-enter the COMPLETE Product Key in the Activation dialog. It is thus essential to keep a
copy of the e-mail that contains the Product Key, an e-mail which you received when you purchased the
software.
Important: The program automatically records the user-selectable setups of each tool as well as the windows'
positions when the program is closed. Whenever feasible, the windows reopen to the last saved configuration.
The toolbar window also contains controls to select a measuring instrument (purchased separately), and status
lights for the features supported by the connected instrument (measurement modes, measurement conditions,
spectral tools compatibility). Additional information on the supported instruments is presented here.
The following screenshot shows the toolbar window with the "Instrument" menu opened:
A green light beside the instrument selection menu indicates that the instrument is recognized and ready to
use; a red light indicates that it is not available. Clicking on the “Info” button opens the “Instrument info”
dialog which shows information relative to the instrument and enables you to change its settings. If your
instrument is connected but shown as not available, you should first attempt a reconnect by selecting “Try to
connect again…” in the “Instrument” menu. If the instrument is still not connected, clicking on the “Info” button
may provide information on the source of the problem.
Note: If the above fails, physically disconnect and reconnect the instrument, then select “Try to connect
again…” in the “Instrument” menu. If you have an Eye-One Display or i1Pro and the problem persists, read
Note 4 in the Supported instruments section. For instance, we noticed that it is sometimes not possible to
reconnect the instrument just by using the Instrument menu when the instrument was previously recognized but
the computer was put in "Sleep" mode.
You will also notice that the instrument menu does not offer “i1Pro” and “i1Pro 2” as separate menu items.
Instead, “i1Pro / i1Pro 2 (non-XRGA)” and “i1Pro / i1Pro 2 (XRGA)” are shown; these descriptions
correspond respectively to the old i1Pro driver and the new i1Pro 2 driver. Both the i1Pro and i1Pro 2
instruments can be used with either driver. The i1Pro driver is NOT XRGA compliant and the i1Pro 2 driver is
XRGA compliant. You can thus make measurements with your instruments with or without XRGA calibration.
Note: The “Eye One Display” and “i1Pro / i1Pro 2 (non-XRGA)” menu items are NOT available in 64 bit
packages.
Eye-One Display 2
Note: The "Ambient" status light will be OFF for an older Eye-One Display with no ambient adapter.
Note: This instrument is NOT supported in 64 bit packages.
i1Display Pro
Note: The "Ambient" and "Flash" status will be OFF for an i1Pro without ambient measurement capabilities.
Note: An i1Pro 2 can only be used in its default mode (M0 or M2 depending on model) with this driver.
Note: This driver is NOT supported in 64 bit packages.
Note: An i1Pro can only be used in its default mode (M0 or M2 depending on model) with this driver.
I1Pro 3
I1Pro 3 Plus
Note: The only instrument which supports the M0, M1, M2, and M3 Measurement Conditions.
CT&A CT&A-Mac
Instrument 32 bit 64 bit Notes Type Manufacturer
(Windows) (Mac)
Eye-One Display
Eye-One Display 2 1 to 5 colorimeter
Spyder5 9 colorimeter
Datacolor
www.datacolor.com
SpyderX 9 colorimeter
Important: The CT&A 32 bit executable for Windows can run on 32 bit and 64 bit Windows systems. For the
macOS, the program is provided in a 64 bit package. See the System requirements section for OS
compatibility.
Note (64 bit packages): The “i1Pro / i1Pro 2 (non-XRGA)” driver/menu selection is not available.
Important (Windows OS only): If you need USB drivers for an instrument, consult the "CT&A_Readme.txt" file
located within the main CT&A application folder for driver install instructions. The i1Display Pro uses the default
OS USB drivers and no separate driver installation should be required. The SpyderX also uses default OS USB
drivers but they may not be installed if you use Windows 7; please consult the "CT&A_Readme.txt" file for more
information.
Note 1 (Eye-One Display 2): The Eye-One Display 2 offered or bundled with many wide gamut monitors sold by NEC, such as the
PA271W model, can be used with CT&A. The Eye-One Display 2 is often bundled with monitors sold by other companies; it is usually a
standard model which is only “re-branded”, but it can also be a custom version tuned to a company’s product. This special version of the
NEC Eye-One Display 2 is identified as Custom calibrated color sensor (MDSVSENSOR2) and is available in the SVII-PRO-KIT. This
custom instrument is tuned to the primaries of NEC’s wide gamut monitors. For such monitors, it is not recommended to use a standard
Eye-One Display 2 because the filters used in these instruments were optimized for standard gamut monitors, and measurements done on
wide gamut monitors are less accurate. According to NEC, the MDSVSENSOR2 provides accurate colors for both wide gamut and
standard gamut displays; all color corrections are performed internally (in the colorimeter), and the instrument provides color values which
do not require further corrections when read by a program such as CT&A. With BabelColor's PatchTool program, we have performed an
Idealliance certification procedure on an iMac using both a standard Eye-One Display 2 and the special NEC version, and the results are
identical within the inter-instrument tolerance of the instruments.
Note 2 (Eye-One Display 2): If an Eye-One Display 2 is properly recognized after you click on “Info” button, then it should work with CT&A.
If it is not recognized, i.e. if there is a message that the instrument is not connected, then there are good chances that it cannot be used
with CT&A. For instance, CT&A cannot be used with the special version of the Eye-One Display 2 provided with HP DreamColor monitors.
IMPORTANT: Make sure that instrument connection is not blocked by another program such as “X-Rite Device Services” (see Note 4).
Note 3 (Eye-One Display, Eye-One Display 2, i1Pro – All models): CT&A should be used with only one Eye-One/i1Pro/i1Pro 2
connected at a time and only one i1Pro 3 at a time. You can however connect one Eye-One/i1Pro/i1Pro 2 in addition to one i1Pro 3 and
one i1Display Pro since these instruments use different drivers.
Note 4 (Eye-One Display, Eye-One Display 2, i1Pro – All models): If you installed software from X-Rite, such as i1Profiler, which
comprises the “X-Rite Device Services” program, you may receive a message to the effect that the instrument is not connected when you
click on the "Info" button. Assuming that your instrument is indeed connected, first check if the i1Profiler program from X-Rite is opened,
and, if opened, close it, since CT&A cannot be used at the same time. Early versions of i1Profiler provide a control panel named “X-Rite
Device Services”, which is used to assign/unassign instruments to X-Rite software. On a Mac, the “X-Rite Device Services” control panel is
located in the System Preferences dialog. The latest versions of i1Profiler still include “X-Rite Device Services” but do not include a control
panel, and instrument assignment is performed dynamically when opening an X-Rite program. If using an early version of i1Profiler, you
should DESELECT the i1 (Eye-One) in the “X-Rite Device Services” control panel; this will make the instrument available for CT&A. Please
note that changes in the X-Rite control panel can be done while CT&A is opened. You should then be able to connect the instrument by
selecting “Try to connect again…” in the “Instrument” menu. The early versions of i1Profiler may also open one or more dialogs asking if
you want CT&A to take ownership of the i1 peripherals; please answer “Yes” to the question(s). “X-Rite Device Services” is dedicated to X-
Rite programs and is not under CT&A's control; any problem related to its use should be directed to X-Rite.
Note 6 (i1Display Pro): “i1Display Pro” is the name of the package that contains the “i1Display”, the actual device’s name, plus the
i1Profiler software. However, the device is most often referred to as the “i1Display Pro” in the many reviews found on the Web, a name that
differentiates it from the previous Eye-One Display models.
Note 7 (i1Display Pro): The i1Display Pro measurement time is adjustable by software. When making tests with this instrument we verified
that we get less noise when increasing the measurement time, as expected, but the difference is most often not significant (in particular,
the noise is low for dark patches even with short measurement times). We offer two options: a FAST setting which takes a measurement
about every 0,5 second, and a SLOW setting which takes a measurement about every 1,2 seconds. Select the FAST setting to start with;
use the SLOW setting if you see large differences between two series of measurements done back-to-back, or when the display refresh
rate is lower than 50 Hz. Always use the SLOW setting when making measurements on a CRT.
Note 8 (i1Display Pro): In order to make measurements with the i1Display Pro, it is required to stop the “i1ProfilerTray” application that
may be running in the background. The i1ProfilerTray utility is part of the i1Profiler software provided by X-Rite in the i1Display Pro
package; it will automatically launch each time you boot your computer. i1ProfilerTray can show reminders when a calibration is due and
can monitor the ambient lighting conditions to see if the display profile should be tweaked; it can also automatically adjust the display profile
following ambient illumination changes. Stopping this utility will not change your display calibration. CT&A will display a message if
i1ProfilerTray is running when you select the i1Display Pro and can stop it for you.
Note 9 (Spyder5 and SpyderX): In order to make measurements with these instruments, it is required to stop the “SpyderUtility”
application that may be running in the background. SpyderUtility is part of the software provided by Datacolor for these instruments; it will
automatically launch each time you boot your computer. This program checks the display settings and monitors the ambient lighting
conditions to see if they are still within tolerance relative to the settings and conditions present when the display was last calibrated.
Stopping this utility will not change your display calibration. CT&A will display a message if SpyderUtility is running when you select these
instruments.
If your instrument is connected but shown as not connected in this window, first close this dialog, then
physically disconnect and reconnect the instrument, and finally select “Try to connect again…” in the toolbar
“Instrument” menu. If you have an Eye-One Display or i1Pro and the problem persists, read Note 4 in the
Supported instruments section. For instance, we noticed that it is sometimes not possible to reconnect the
instrument just by using the Instrument menu when the instrument was previously recognized but the computer
was put in "Sleep" mode.
The dialog content is customized for each instrument since not all instruments support all features or provide
the same information. Also, it is important to note that CT&A changes instrument settings only when making a
measurement, and not when selecting a different measurement mode. It may thus be preferable to open the
"Instrument info" dialog AFTER making a measurement, unless you want to see the current instrument settings
before doing a measurement.
The following screenshots show a few examples of the dialog with different combinations of instrument,
measurement mode and driver.
i1Display Pro
Note 1: The calibration matrices list could be updated in the future just by replacing the content of the "i1d3
Support Files" folder located in the main CT&A folder.
Note 2: Select the "PLASMA/CRT (Burst mode)" display type and the "Plasma (EDR 17) calibration matrix
when doing measurements with a plasma display.
Note 3: When measuring a CRT, the "PLASMA/CRT (Burst mode)" display type is said to provide more
accurate results than the standard CRT display type, especially for darker colors.
Here are four screenshots obtained with the same i1Pro 2, with either the old i1Pro driver (i1Pro/i1Pro 2 (non-
XRGA)) or the new i1Pro 2 driver (i1Pro/i1Pro 2 (XRGA)). The two top screenshots were obtained after
making reflectance measurements; the two bottom screenshots were obtained after making flash
measurements.
i1Pro 2 (reflectance) with i1Pro/i1Pro 2 (non-XRGA) driver i1Pro 2 (reflectance) with i1Pro/i1Pro 2 (XRGA) driver
Note 4: The i1Pro driver (i1Pro/i1Pro 2 (non-XRGA)) cannot differentiate between the i1Pro and i1Pro2; both
are seen as an i1Pro. The i1Pro 2 driver (i1Pro/i1Pro 2 (XRGA)) can identify the instrument and provide the
Rev. level.
Note 5: The i1Pro 2 driver resets the time since the last measurement and the number of measurements quite
aggressively compared to the i1Pro driver. This information is often not available.
Note 6: In reflectance mode, with the i1Pro driver, the i1Pro 2 used for the above screenshots can support only
the M0 measurement condition (incandescent illumination with no UV filter). With the i1Pro 2 driver, M0, M1,
and M2 are supported.
Note 7: The i1Pro/i1Pro 2 (non-XRGA) driver is NOT supported in 64 bit packages.
Important: Before initiating the lamp restore procedure, please do the following checks:
• Make sure that you are using the correct calibration tile/base for your instrument. The tile is matched to
the instrument and identified with the same serial number.
• Calibrate your instrument before doing a lamp restore check; this is a good indication that your USB
connection is in proper working order. When there is a USB problem, you should get specific error
messages to this effect when calibrating, particularly in reflectance, and typically more often with the
i1Pro 2 than with the i1Pro. A more complete check-list to go through in case of calibration failure is
presented on the next page.
Once the restore check procedure is started, the lamp will be restored automatically if a lamp drift is detected.
Restoring the standard lamp condition takes about 2 minutes and you will get a confirmation message when it
is completed. If you get a message in less than 10 seconds, then restoration was not required.
Warning: Leave the instrument on the calibration plate until you get a confirmation message that the check or
restore is completed.
Note: If lamp restore is required for an i1Pro 2, you will see a series of yellow-green flashes on the instrument
at the beginning and end of the 2 minutes procedure. Because the i1Pro has no such lights, you should simply
wait until you get a confirmation message. For both instruments, you will also see a waiting cursor while the
check and restore is performed; however, please note that this cursor is visible only when the mouse cursor is
over one of CT&A's windows.
Calibration failure more often occurs when calibrating in reflectance mode. This can happen even if the
instrument is properly detected and identified in the "Instrument info" dialog. Here are potential causes to look
for:
1. The instrument is not properly seated on the calibration tile. This may seem obvious but it is worth
checking!
2. The calibration tile is dirty. Clean it gently with a soft tissue lightly dabbed in isopropyl alcohol.
3. You are using the wrong calibration tile for the instrument. The i1Pro calibration tile is matched to the
instrument at the factory. You should be aware that using a tile from another instrument will very likely
provide inaccurate measurements, even if you do not get an error message!
4. There is a bad or degraded contact between the instrument and the USB cable or between the cable and
the computer USB port. If a connection is loose, you can sometimes improve it by pushing, holding, or
reinserting the connector. Try another USB cable or another USB port to see if you get better results. In
some extreme cases your computer USB port or your instrument connector may need to be replaced.
5. The overall USB cable resistance is too high. This can be due to a poor quality cable, a damaged cable,
a cable which is too long, or a cable with dirty connectors.
6. The computer USB port cannot provide enough current for calibration. This is more often a problem with
external USB hubs. Try a USB port which is not used (i.e. connected and disconnected) often.
7. If all of the above is non-conclusive, your instrument may be due for a factory calibration or repair.
The dialog has four tabs: "Color", "Math", and "Instrument", and "RGB vs RGB". The “Math”, “Instrument” and
“RGB vs RGB” tabs have a "Default" button that can be used to reset factory settings for the tab. Also, you can
click on the "Default-All" button, located below the tab zone, to reset the content of all tabs in one click. The
settings are saved when you leave the dialog, and are loaded at the program start.
COLOR TAB
CT&A is color-managed and the display profile is used to compute the appearance of all color patches. The
program uses the profile assigned to the display corresponding to the window position. If the window is moved
to another display, the patches are rendered with the new display profile; there is no need to manually select a
profile in multi-display systems. The tools in which a display profile is used for rendering color patches are:
RGB vs RGB, CRI, Density, FluoCheck, Graph, Metamerism Index, and RAL DESIGN.
This table shows the name This field shows the profile Click on these buttons to
and file path of the profiles assigned to the display on open folders which contain
assigned to each display by which the “Preferences” user and system display
the OS. Use the OS display dialog is located. profiles.
control panel to change this The content is updated
assignment. continuously.
The “Color” tab of the “Preferences” dialog cannot be used to assign or select a profile but is used to check if
the profiles assigned to each display are the correct ones. Please consult the Display calibration section for
short procedures to test display contrast and highlight saturation.
Note: The profile file path is not shown on the Mac OS.
Important: Make sure the LUTs corresponding to the selected profile are loaded. In particular, for Windows
computers, the LUTs are NOT updated when the display profile is changed using the display properties dialog.
A dedicated LUT loading application, or a reboot, is required.
Important: The display profile has NO EFFECT on the accuracy of the computations; it simply affects the
appearance of the color patches.
When this preference is selected, the RGB vs RGB tool will clip “xyY” and “XYZ” values to zero and the
corresponding data point on the chromaticity diagram will stay on the “x” or “y” axis (or stay at zero). “L*”
of L*a*b* and L*C*h will also be clipped to zero instead of being negative.
When this preference is NOT selected, “xyY” and “XYZ” values can go below zero and the corresponding
data point on the chromaticity diagram will go into the negative “x” and “y” regions. “L*” of L*a*b* and
L*C*h are allowed to be negative.
Spectral interpolation
The method used to interpolate spectrums at 5 nm intervals when the original data is available at 10 nm
intervals. The 10 nm bandwidth data may originate from measurements, from an i1Pro series
spectrophotometer for instance, or from files. Interpolated 5 nm data is used for improved accuracy in the
following tools:
• CRI tools: Used for all computations.
• ISO 3664+ tools: Used for the CRI and the Visible Metamerism Index (MI, ISO 23603).
• Graph and MI tools: Used for the CRI of Ambient data.
Note: For the CRI tools, a newly selected interpolation setting will apply only to new measurements and
new files with a 10 nm bandwidth! If you wish to re-interpolate the currently opened spectrums, you should
export them in CGATS format with a 10 nm bandwidth and reopen them with the new setting. You can
thus see the effect of the interpolation method by opening the same file twice and changing the
interpolation setting in between.
Note: Only “Lagrange” interpolation was used prior to V-5.3.0 and is thus the default for this setting.
Note: The “Cubic spline” method used here is also called “Natural Cubic Spline”. It is not constrained and
will typically show undershoot and overshoot where there are sharp transitions. It was found to be the best
interpolation method, when the input data is uniformly sampled, among the following methods: linear, third
order polynomial (Lagrange), cubic spline, fifth order polynomial, and Sprague (Ref. 66).
This configuration facilitates the comparison of similar colors by minimizing the interference caused by the
large colored surface of the diagram.
You can dim the chromaticity diagram to minimize the screen clutter even more:
In addition, the interference caused by other opened windows on the desktop can be removed by
maximizing the RGB vs RGB window so that it fills the screen:
in Windows,
in Mac OS X.
Important: To prevent odd program behavior, a message will appear if you set the sensitivity setting too
close, or higher, than the hue search extent value, and when you set the hue search extent too close, or
lower, than the sensitivity. The program will then assign the nearest valid number to the parameter being
set.
chromaticity patches on
diagram backgrounds
+ WCAG
Space Deck
interface interface
mouse
input
DeltaE*
display
patches on text on
various backgrounds
backgrounds + WCAG
The RGB vs RGB tool window is opened either by clicking on the corresponding icon on the toolbar window,
by selecting the "RGB vs RGB/Show window" menu, or by selecting the "Tools/RGB vs RGB" menu. This tool
window can be resized to show or hide additional text and patch layouts.
Two colors can be selected either within an RGB space or within a catalogue of color chips, herein called
"Color Decks." The two colors can be compared on various backgrounds (white, gray, black), against each
other or superimposed on one another. You can also see how text of the two selected colors will look on white
and black, and on a background of the other color; with an analysis of each color pair Contrast Ratio as defined
by the Web Content Accessibility Guidelines (WCAG).
There are 20 predefined RGB spaces, plus one user-defined space (Custom RGB space dialog). You can thus
compare your custom space against any of the predefined RGB spaces; you can also export the matrix
parameters used for XYZ to RGB conversion and get the Chromatic Adaptation Transform (CAT) matrices,
either Bradford or CIECAT02, between a custom illuminant and many standard illuminants. Input in a given
RGB space is done either by selecting RGB values, by clicking on the chromaticity diagram, or by entering
L*a*b* or L*u*v* values; the L*a*b*/L*u*v* values can be either manually entered or they can be measured
using one of the supported instruments.
First, let's say a few words about "RGB" (in reality R'G'B', i.e. RGB with primes beside each letter), the most
used but least understood of these color languages. For most people, "RGB is RGB" is like "A rose is a rose",
where the same word describes the same "thing." Alas, RGB spaces are most often very different. The graphic
designer is well aware of the difference between the look of an image created on a wide gamut display whose
device space is close to Adobe (1998) RGB and its appearance on a Windows compatible PC (with a default
sRGB space), where both the colors and the brightness (luminance) are affected. Similarly, the serious
amateur or professional photographer will be confronted with a choice of RGB spaces which are all presented
as the best choice for manipulating his images, but which produce vastly different results.
The process, performed in the background, even if controlled by the user, is usually complex and does not
provide direct information on how a specific color was translated: What are the RGB coordinates of a particular
color in the new space? Was that color clipped? By how much? These answers can be found with the RGB vs
RGB tool.
Within CT&A, a color in an RGB space can also be described by multiple other color spaces, which could be
though of as different "color languages." The other color spaces include the principal color characterization and
description standards used in the graphic and colorimetric trades: "xyY", "XYZ", "L*a*b*", "L*u*v*", "Hex #",
"HSB", "Munsell HVC", in various illuminant settings.
The "Hex #" color representation is simply a conversion of RGB values from the decimal base (base-10) to the
hexadecimal base (base-16). Previously used mainly by programmers, it is now often required for assigning
colors when designing Web pages. Both "HSB" (Hue-Saturation-Brightness) and the "Munsell HVC" (Hue-
Value-Chroma) color systems describe color using a code structure which attempts to simplify the relation
between the perceived color and its description. The simpler HSB notation is used by many graphic
applications in color pickers, whereas the Munsell notation, a perceptively uniform system and an International
Standard, is used for accurate and critical color assessment.
Important: When inputting L*a*b* or L*u*v* data in the RGB space interface, you should remember that all
RGB spaces have a limited gamut (i.e.they do not represent all visible colors), and that if you enter a color
value which is outside of the RGB space, this color will be clipped to fit within the space.
Important: Some settings, tools and functions may not be available when the program is not activated.
The three icons are grouped at the left of the toolbar. The "Tables" icon is equivalent to the "Table data" menu
item while the "Graphics" icon is equivalent to the "Graphic data" menu item. The "Tables" icon is always
enabled while the "Graphics" icon is enabled only when the RGB vs RGB tool window is opened.
• Mode: Three modes are available. These modes affect how the data is compared or converted in the RGB
vs RGB window.
• Compare: Sets the program in Compare mode if it was in Convert mode (either Left to Right or Right to
Left). It has no effect if the program is already in Compare mode.
• Convert / Left to Right: Sets the program in Convert mode Left to Right (Space #1 to Space #2). It has
no effect if the program is already in Convert mode Left to Right.
• Convert / Right to Left: Sets the program in Convert mode Right to Left (Space #2 to Space #1). It has
no effect if the program is already in Convert mode Right to Left.
These modes can also be set directly from the tool window. Please consult the RGB vs RGB Mode
Settings section.
• Table data: These menu items are available even when the RGB vs RGB window is closed; they open
stand-alone dialogs.
• CAT matrices...: Opens the CAT matrices dialog which can display the Bradford and CIECAT02
Chromatic Adaptation Transform (CAT) matrices that correspond to user selectable source and
destination illuminants.
• Illuminant data...: Opens the Illuminant data dialog that displays the xyz and XYZ coordinates of a user
selectable illuminant.
• RGB to XYZ matrices...: Opens the RGB to XYZ matrices dialog that displays the "RGB to XYZ" and
"XYZ to RGB" matrices of a user selectable space.
• Space data...: Opens the Space data dialog that displays the illuminant, the primaries, and the gamma
parameters of a user selectable space.
The ColorChecker coordinates for all three illuminants are presented in this section. The CMYK data
corresponds to the C, M, and Y primaries, plus the CM, MY, and YC overprints. The Planckian locus is the
locus of blackbody illuminants between 1,000 K and 25,000 K.
Hint: You can open the saved file in Microsoft Excel as well as other spreadsheet applications. In Excel, first
select to open all files, then select the report file (its default name is BabelData.txt), then use the input
Wizard. Select the "Delimited" and "Space separation" options. Some of the file content will be awkwardly
formatted but, most importantly, the coordinates data and the data columns titles should be aligned. You can
then copy and paste the data to another spreadsheet.
• Print Graphic...: Opens a standard dialog to select a printer, if more than one is available, and prints the
chromaticity diagram. In addition, if enabled in the "RGB vs RGB" tab of the Preferences dialog, all the
corresponding data and mode settings will be printed beside the diagram. The print size is adjusted to fill the
default printable width. An alternate means of opening this dialog is to press the Control + P keys, in
Windows, or the Command () + P keys on a Mac.
Note: The page setup dialog ("File/Page Setup...") will be called before printing for the first time after a
program start. This dialog is used to select the paper size, its orientation, and the print margins and,
depending on the operating system version, you may also be able to change the printer from it.
• Define custom RGB...: Opens the Custom RGB space dialog where you can edit the Illuminant, primaries
and gamma parameters of a custom RGB space; this space can then be selected, in a RGB Space space
selection list. The illuminant of the custom space also defines the Custom illuminant in a Color Deck
illuminant selection list.
Here is a description of the "Tables" and "Graphics" menu items, with links to a description of each dialog and
additional information.
• CMYK spaces: Displays the C, M, and Y primaries and CM, MY, and YC overprints of eight common CMYK
spaces. The coordinates are computed for the D50 illuminant.
Note: Any graphic data selected with these menus will also be visible in the chromaticity diagram of the
Custom RGB space dialog.
This dialog displays the 3 x 3 (Rows x Columns) Bradford or CIECAT02 Chromatic Adaptation Transform
(CAT) matrix that corresponds to user selectable source (From) and destination (To) illuminants. Source data
is XsYsZs and destination data is XdYdZd; both are column vectors.
By default, in Compare mode, the source is the illuminant of the LEFT side (Space #1 or Deck #1), and the
destination is the illuminant of the RIGHT side (Space #2 or Deck #2). By default, in Convert mode, the source
is the illuminant of the Space or Deck being converted "FROM", and the destination is the illuminant of the
Space or Deck being converted "TO".
Additional standard illuminants plus any custom illuminant defined in the Custom RGB space dialog are
provided in the illuminant selection menus:
You can copy matrix data by making a mouse right-click (or ctrl + click on a one-button Mac mouse) on any
data field. When copied, the data is transferred into the clipboard. Please note that matrix values are separated
by Tabs, on three lines; you can then easily paste the values in a spreadsheet or document table, where they
will be distributed in individual cells.
This dialog is called with the "RGB vs RGB/Table data/CAT matrices..." menu or with the "CAT matrices..."
menu of the toolbar "Tables" icon.
This dialog displays the xyz and XYZ coordinates of a user selectable illuminant.
By default, the dialog selects the illuminant of the LEFT side (Space #1 or Deck #1). Any custom illuminant
defined in the Custom RGB space dialog is also provided in the illuminant selection menu.
This dialog is called with the "RGB vs RGB/Table data/Illuminant data..." menu or with the "Illuminant data..."
menu of the toolbar "Tables" icon.
This dialog displays either the 3 x 3 (Rows x Columns) RGB to XYZ matrix, or its inverse, the XYZ to RGB
matrix, of a user selectable space. Input and output data are assumed to be column vectors.
Selecting "RGB to XYZ" or "XYZ to RGB" is done by clicking the corresponding radio button.
By default, the dialog presents the RGB to XYZ matrix of Space #1 if the LEFT side is in Space mode, or when
both sides are in Deck mode.
By default, the dialog will present the RGB to XYZ matrix of Space #2 if the LEFT side is in Deck mode AND
the RIGHT side is in Space mode.
Hint: You can save the two matrices data in a file by using the "Export to file..." button in the Custom RGB
space dialog.
This dialog is called with the "RGB vs RGB/Table data/RGB to XYZ matrices..." menu or with the "RGB to XYZ
matrices..." menu of the toolbar "Tables" icon.
This dialog displays the illuminant, the primaries, and the gamma parameters of a user selectable RGB space.
The primaries coordinates are presented in the xyz form. Only "x" and "y" are shown since, by definition,
z = 1 - x - y.
The "Detailed gamma" parameters are filled with zeros when the space is not defined with a detailed gamma
function. For spaces defined with a detailed gamma function, we also provide a "simple gamma", a single
parameter, which is often used by graphic editing programs.
The "simple gamma" is presented in two equivalent forms, with the second form showing the inverse value of
the first one. However, the second form may look more familiar as it is the number used to characterize gamma
in many programs.
By default, the dialog presents data for Space #1 if the LEFT side is in Space mode, or when both sides are in
Deck mode.
By default, the dialog will present data for Space #2 if the LEFT side is in Deck mode AND the RIGHT side is in
Space mode.
Hint: You can get this data in a file by using the "Export to file..." button in the Custom RGB space dialog.
This dialog is called with the "RGB vs RGB/Table data/Space data..." menu or with the "Space data..." menu of
the toolbar "Tables" icon.
Important: The above image is a simulation of the X-Rite/GretagMacbeth ColorChecker chart produced by
the Munsell Color Lab. The colors are not calibrated and the image should not be used as a reference.
The ColorChecker card is ubiquitous in the photographic and video fields. Its main application is for obtaining a
rapid assessment of an imaging devices' color rendering accuracy, although it can be used for calibration
purposes. The ColorChecker consists of a series of six gray patches, plus typical additive (Red-Green-Blue)
and subtractive (Cyan-Magenta-Yellow) primaries, plus other "natural" colors such as light and dark skin, sky-
blue, foliage, etc. The color pigments were selected for optimum color constancy when comparing pictures of
the chart with pictures of the natural colors... as reproduced on color film! Optimizing the human visual match
was thus not the first priority; still, it was shown, by the chart designers, that the degree of metamerism was
also very small when directly comparing the chart to the natural colors. Expressed otherwise, the perceived
colors of the ColorChecker vary in the same way as the natural colors they represent when the light source
changes, either when imaged on film or compared directly. Please consult Ref. 6 for a detailed description of
the chart by the persons who designed it
Note: The technical term for a change in a single perceived color with various illuminants is Color Inconstancy,
which is related to, but not the same as, metamerism, the term used when two colors matching under one
illuminant do not match under another illuminant.
The coordinates of the patches under the "C", "D50" and "D65" illuminants are shown in the table below; in
relation with the image above, the patch numbers start in the upper left corner and increase from left to right,
and from top to bottom. The table values were derived from the measured spectral data of thirty (30)
ColorChecker or Mini ColorChecker charts. The spectrums were first averaged, then converted to XYZ using
the procedure and the weights of ASTM E308 (Ref. 16), and finally converted to xyY. You will find much more
information and data on the ColorChecker, including "synthetic" images of the chart in numerous color spaces,
on the ColorChecker page of the BabelColor Web site.
The locations of the ColorChecker chart patches for these three illuminants can be viewed on the chromaticity
diagram by selecting one of the three "RGB vs RGB/Graphic data/ColorChecker ( )" menus or one of the three
"ColorChecker ( )" menus of the toolbar "Graphics" icon.
Note: The numbers between parentheses in the neutral patches descriptions are optical densities.
The interface is identical for Space #1 (LEFT side) and Space #2 (RIGHT side).
For more information, use the links in the Table of Contents below.
If the input mode for the Space is L*a*b* / L*u*v* (see L*a*b* / L*u*v* input), and the button (click here
for information on this button) is NOT active at the change request, the system uses the displayed values of
either L*a*b*, L*u*v*, L*a*b* (D50), or L*u*v* (D50), depending on the selected modes, and updates all the
others, including R'G'B'.
If the button is active at the change request, then the following sequence is performed:
1. The L*a*b* / L*u*v* display boxes are reloaded with the last computed values.
2. The "GO !" button is de-activated.
3. Recomputing is performed with the new space parameters.
In Compare mode, the spaces and decks are independent and only the Space for which the space selection
was changed will be updated.
If the change is in a Space which is being converted "TO", then the selection change first triggers an update on
the other side, Space or Deck, which then updates the Space which was changed. If that other side (i.e. being
converted "FROM") is in "L*a*b* / L*u*v* input" mode and the button is active at the change request,
the L*a*b* / L*u*v* display boxes are reloaded and the "GO !" button is de-activated before updating both sides.
R'G'B' SLIDERS
The R, G and B sliders control the R'G'B' inputs. Their minimum value is zero and their maximum is 255; all
values in between are integer numbers. The actual values are shown in the R'G'B' display boxes under the
sliders.
"Y" SLIDER
The Y slider is a luminance control related to the "Y" in the xyY or XYZ color representations. Its minimum
value is zero but its maximum is controlled by a combination of the R'G'B' values and the selected space
characteristics. The "Y" value is not linearly related to the slider position. Moving the Y slider affects the R, G
and B sliders and displays, as well as the "Y" display, but it does not affect the "xy" coordinates, as it can be
verified by looking at the xyY data display or the position of the space's color on the chromaticity diagram.
2
Note: "Y" is proportional to the luminance of the color (measured in cd/m ) as it would be measured with a
photometric detector. Doubling its value doubles the amount of flux emitted by the color patch. However, since
the human eye is not a linear detector, the perceived brightness is less than doubled. The "L*" of the L*a*b*
and L*u*v* color representations are designed to closely mimic the human eye in terms of brightness response
and can, as well, be mentally associated with the Y slider. Please note, however, that increasing or decreasing
the Y slider not only changes "L*" but the "a*" and "b*" coordinates as well.
The R'G'B' values will change by the amounts showed in the above illustration. The "Y" slider will affect the
maximum value of the R'G'B' data set by the amount shown. The actual value change for "Y" is relative to the
maximum emitted flux of each specific color, and is thus different for each color and space.
Note: Starting with "Y" at the top of its slider, clicking repeatedly between the elevator box and the bottom
arrow will give 32 color patches of uniformly decreasing brightness, plus a patch of black at the last click.
Click or double-click in the data display boxes to change the values. Use the Tab key to move between all the
enabled boxes of both spaces, either R'G'B' or L*a*b* / L*u*v*.
The red, green and blue background colors of the RGB data displays shown above indicate that this space
input mode is R'G'B', i.e. color data for this space is entered either directly in these boxes, or via the sliders.
If data in this space was converted from the other space, the RGB display would be seen as follow:
In the display just above, the background color of the R'G'B' display boxes is yellowish and input is disabled.
The sliders are also disabled.
When this display is visible, you will notice, from time to time, the appearance and disappearance of red
exclamation points ( ! ) between the display boxes and the sliders; these clipping indicators which inform
the user that the color from the originating space is out of the converted space gamut, and it had to be
clipped; see the Mode settings section for more information on the Convert mode.
You can copy numerical data by making a mouse right-click (or ctrl + click on a one-button Mac mouse) on
a data field. Shown below is the contextual menu which appears with a right-click on an RGB field or on a
xyY field; selecting the menu will transfer the three coordinates into the clipboard, separated by Tabs. You
can then easily paste the values in a spreadsheet or document table, where they will be distributed in three
columns.
Use the menu located below the "RGB" label to select among the following color spaces: Hex #, HSB,
Munsell HVC, L*C*h, xyY or XYZ.
The Munsell HVC values are not simply the ones corresponding to the closest sample in the Munsell deck
catalogue, but are INTERPOLATED values that closely match the selected Space color.
The L*C*h values are automatically updated, even if there is no color change, when you change the L*a*b* /
L*u*v* display and when you click in the "L*a*b* / L*u*v* in D50" checkbox described below. The displayed
values are:
1. L*C*abhab referenced to the space illuminant when L*a*b* is selected and the "L*a*b* / L*u*v* in D50"
checkbox is NOT selected
2. L*C*uvhuv referenced to the space illuminant when L*u*v* is selected and the "L*a*b* / L*u*v* in D50"
checkbox is NOT selected
3. L*C*abhab referenced to D50 when L*a*b* is selected and the "L*a*b* / L*u*v* in D50" checkbox IS
selected
4. L*C*uvhuv referenced to D50 when L*u*v* is selected and the "L*a*b* / L*u*v* in D50" checkbox IS
selected
Use the bottom menu to select either the L*a*b* or L*u*v* color space.
Checking the "L*a*b* / L*u*v* in D50" checkbox instructs the program to show L*a*b*, L*u*v* and L*C*h
values converted to illuminant D50, irrelevant of the illuminant of the selected space. Of course, if the space
illuminant is D50, no change will be seen in the displays. When the "L*a*b* / L*u*v* in D50" checkbox is
unchecked, the L*a*b*, L*u*v* and L*C*h displays show values corresponding to the illuminant of the
selected space.
Changing the L*a*b* / L*u*v* selection or changing the "L*a*b* / L*u*v* in D50" checkbox status will
automatically update the L*C*h display, whether it is visible or not. Please refer to the additional information
on the L*C*h display above.
When in "L*a*b* / L*u*v* input" mode, and when the button is active, changing the L*a*b* / L*u*v*
selection or the "L*a*b* / L*u*v* in D50" checkbox status will reset the display to the previously calculated
values, and disable the "GO !" button.
Note: Be cautious, the L*a*b* values shown in Adobe Photoshop are always in D50, irrelevant of the
illuminant of the selected space.
For more information on the program modes, go to the Mode Settings section.
The above display is obtained by checking the "L*a*b* / L*u*v* input" checkbox (RGB space: Adobe (1998)).
The light green background color of the L*a*b* data displays indicate that this space input mode is L*a*b*; the
R'G'B' sliders and RGB data boxes are disabled and replaced by controls dedicated to instrument input. Color
data for this space can be entered directly in the light green data fields, either manually or by making a
measurement with one of the supported instruments. There is no setting to select between manual or
instrument input; you just enter data or take a measurement.
Note: We see a blue indicator in the screenshot above. This indicator appears when an i1Pro series
spectrophotometer is connected and recognized by the program (the RGB vs RGB window must also be
selected, i.e. brought to the front). In this case we know it is an i1Pro 2 since the M0, M1, M2 measurement
conditions can be selected.
You will notice, when entering data, that all other displays are NOT automatically updated. To update the other
data displays, you should first enter all L*a*b* or L*u*v* values and then click on the button (alternately,
press the Return or the Enter key).
This manual refresh procedure was devised because the L*a*b* and L*u*v* spaces can describe all the visible
spectrum while the R'G'B' spaces only represent a subset of it. When entering data, it is very likely that the
color described by the input data is outside of the R'G'B' space gamut, and clipping will occur; in such a case,
clipping will be flagged by one or more red exclamation points ( ! ) located below the "R", "G", and "B" labels.
These clipping indicators provide advanced warning; they identify the R'G'B' coordinate(s) that will be clipped
by the data present in the input boxes. The three data input fields can be modified at will, until the "GO !" button
is pressed, to see how and if other data values will be clipped. If you press the "GO!" button when clipping is
flagged, the software will select the closest color corresponding to the input data within the RGB space, as
shown below.
By comparing the display just above with the previous display, we see that the requested L*u*v* (D50) input of
(57.8, 75.0, 48.5) requires an out of bound B' (blue) value (a negative value in this case). The nearest valid
R'G'B' color computed by the software has a B' value of zero, indicative of the clipping process. Also, the
program recomputed the L*u*v* (D50) value (and all other color representations) to match the R'G'B' data.
The clipping indicators disappear once the "GO !" button is pressed.
Hint: If you just want to measure and compare colors in L*a*b*, with no need for this color to be associated
with an RGB space, you can select a very large space, ProPhoto RGB for instance, to perform your
measurements. Selecting a larger space minimizes the chances of measuring a color which will be clipped.
You can also define your own space or edit an existing one; for example you could create a space with
ProPhoto RGB primaries and a D65 illuminant, instead of D50, if D65 is the illuminant for which you want
specific L*a*b* data.
If an instrument is properly connected and detected by the program, as it can be easily confirmed by a green
instrument status light in the toolbar window, the "Calibrate", "Measure", and "Measure-and-GO!" buttons of the
RGB vs RGB window will be enabled; also, the measurement mode menu in the "Next sample" controls group
will offer only the modes supported by the connected instrument. In addition, if using an i1Pro series
spectrophotometer, a large blue indicator will appear above a "Calibrate" button when the RGB vs RGB
window is selected (brought to the front). The blue indicator identifies the space for which a measurement will
be done if you press the instrument button. If both spaces can accept input by measurement, the blue indicator
automatically changes location after making a measurement.
You can click (left-click) on the indicator to move it to the other side if required; this is shown below in the next
two screenshots.
You can also do a right-click on the blue indicator to lock it on a given side; a locked indicator is surrounded by
a red circle , as shown below. If you do a left-click on a locked indicator; the indicator will change side and
the new position will be locked.
The "Illuminant" used to process the measurement will be the one assigned to the RGB space. For reflectance
measurements, and if this illuminant is not one of the standard illuminants supported by the program (A, C,
D50, D65, or E), the measurement will have to be done by first selecting the "L*a*b* /L*u*v* in D50" checkbox;
the measurement will then be converted internally to the illuminant of the RGB space.
Before making your first measurement, you should calibrate the instrument by clicking the "Calibrate" button.
The program will calibrate the instrument in the mode selected in the "Next sample" controls group located just
above the calibration button.
The L* (of L*a*b*) and Y (of XYZ) values of the AMBIENT color coordinates are always maximized relative to
their xy (chromaticity coordinates) position in the selected RGB space (in other words, at least one of the R, G,
or B coordinates will have a value of 255). L* and Y values of 100 can only be assigned to the chromaticity
coordinates of the illuminant. (Note: this is different than what is done in the Graph tools where L* and Y are
100 for all ambient measurements).
Here is a table which describes the difference between the RGB vs RGB tool and the Graph tools relative to
EMISSION and AMBIENT measurements:
Note: Only x and y are absolute coordinates. While the absolute luminance and illuminance are provided in
cd/m2 or lux, Y is normalized when shown in the xyY and XYZ data fields.
Important: Many displays (usually CRTs, but sometimes LCDs) will change their brightness depending on
what is displayed on the rest of the screen. This is why a single small white square over a black background is
used for emission calibration. As a consequence, in some displays, you may find that, thereafter, white is
measured with an L* value of less than 100 in many situations. Also, most displays are not uniform, with the
center portion "usually" at a higher luminance than the rest of the display; however, it is also possible that the
display center is not the area with the highest luminance.
Note: You may be curious to know why a White Level calibration is required in this program and not in X-
Rite/GretagMacbeth MeasureTool? In effect, MeasureTool also uses a White Level reference value, very likely
coming from a screen profile saved on your computer. The only difference is that, with CT&A, you can set the
reference to other displays.
Measured data can be saved by using the "Save data..." and "Print Graphic..." commands of the "RGB vs
RGB" menu. You should also consult the "RGB vs RGB" tab of the Preferences dialog for additional options.
The display appearance is the same whether the input was R'G'B' or "L*a*b*
/ L*u*v* input" before the requested Convert "TO" mode change. The
background color of the R'G'B' display boxes is yellowish and input is
disabled. The sliders are also disabled.
The interface is identical for Deck #1 (LEFT side) and Deck #2 (RIGHT side). Two deck navigating modes are
available, one using the L*C*h pad, and the other a List view. They are selected with the radio buttons located
below the color patches.
The following Color Decks are provided: British Standard 5252F (BS 5252F), the framework for many British
color standards; FEDERAL STANDARD 595 (FED-STD-595), a set of colors used in the United States of
America for government procurement; the Munsell collection, which are samples based on the Munsell color
system and manufactured at uniform Hue, Value, and Chroma intervals; and the RAL CLASSIC colors, a set of
colors used in Europe since 1927. User-defined color lists can also be imported and added as Color Decks.
Click on a specific zone of the interface image for more information, or in the Table of Contents below.
Use the menu below the "Deck #1" or "Deck #2" label to select a Color Deck. The selection list is the same for
Deck #1 and Deck #2.
The default D65 illuminant will automatically be shown below the deck name. Another illuminant can be
assigned using the Illuminant selection menu; click here for more information on illuminant selection.
After a deck selection, the system loads the deck information from the database. The sequence of events is as
follow:
1. The color strip is regenerated according to the Color Deck database content.
2. The data corresponding to the first color chip in the database is computed in relation to the selected
illuminant.
3. The L*C*h pad or the List view is updated.
In Compare mode, the spaces and decks are independent and only the Deck for which the deck selection was
changed will be updated.
If a Deck is being converted "TO", then two new menu items appear at the bottom of the deck selection list:
• "Selected decks (more than one)"
• "Select more than one deck"
Selecting the last item, "Select more than one deck", opens a Deck Select dialog, shown below, that is used to
select one or more decks as destinations for converting "TO":
At least one deck has to be selected when leaving the dialog; if not, a window with a warning message will pop
up. Once the dialog is closed, the color strip is regenerated according to the dialog selection and will show a
snapshot of ALL selected decks. When two or more decks are selected, the next to last menu item, "Selected
decks (more than one)", is displayed instead of a single Deck name.
When making changes to a Deck(s) which is/are being converted "TO", then the selection change first triggers
an update on the other side (i.e. being converted "FROM"), Space or Deck, which then updates the Deck(s)
which was/were changed. If that other side is in "L*a*b* / L*u*v* input" mode and the button (click here
for information on this button) is active at the change request then:
1. The L*a*b* / L*u*v* display boxes are reloaded with the last computed values.
2. The "GO !" button is de-activated.
3. An update is performed for both sides.
PatchTool's "BabelColor CT&A Export" tool is accessible even when PatchTool is not purchased (or not
activated); however, accessing all of PatchTool's features requires purchasing a separate license. Please
consult the PatchTool Help manual in the section dedicated to the "BabelColor CT&A Export" tool for more
information on how to edit the Color Decks database.
IMPORTANT: Starting with CT&A version 3.1, the Color Decks database file name is ColorDecks_R2.bbd; the
database file name in previous versions was ColorDecks.bbd. Users who have customized their Color Decks in
previous versions will need to regenerate them starting with the ColorDecks_R2.bbd file. DO NOT CHANGE
THE OLD DATABASE NAME TO THE NEW NAME! If you do so, the Munsell Deck, as well as conversions to
the Munsell space, will be less precise.
The selection will affect the deck data, the data displays, as well as the chromaticity diagram. The "Custom"
illuminant is the one selected for the custom space; it can be changed by first selecting the "RGB vs
RGB/Define custom RGB..." menu command and editing the illuminant section of the Custom RGB space
dialog.
Important: The data displays will not show any change if the "L*a*b* / L*u*v* / L*C*h in D50" checkbox is
selected when you change a deck illuminant. This checkbox forces the display to show data converted to
illuminant D50, irrelevant of the illuminant of the selected deck. However, if you uncheck this box, you will
notice that the data has indeed changed according to the selected illuminant.
Note: The Munsell HVC values shown in the data displays are, by design, referenced to Illuminant C and will
remain unchanged following a change in the deck illuminant selection.
L*C*h INTERFACE
The center square patch is the selected patch (Munsell 2.5BG 5/4 in the screenshot above) . This patch name
and coordinates are shown in the data displays. The selected patch is also shown in the color patches displays.
The name of the other patches can be seen by resting the mouse cursor over a patch for a moment; a pop-up
tag with the patch name will then appear.
The patches surrounding the center patch show the nearest patches in the deck(s) corresponding to the
following criteria:
• +sat and -sat: These labels respectively identify the patches which display more and less saturated colors
than the center patch while being the closest to the center patch in terms of luminosity and hue.
• +lum and -lum: These labels respectively identify the patches which are more and less luminous than the
center patch while being the closest to the center patch in terms of color saturation and hue. In the
screenshot above, the center square represents the Munsell 2.5BG 5/4 patch. The mouse is over the "+ lum."
patch, and 2.5BG 6/4 is shown in the popup help text; this patch has the same Munsell Hue (2.5BG) and the
same Munsell Chroma (i.e. saturation, =4) as the center patch, but its Munsell Value (i.e. brightness,
luminosity) is higher (6 instead of 5).
• +hue and -hue: These labels respectively identify the patches which have a hue angle which is bigger and
smaller than the center patch hue angle while being the closest to the center patch in terms of saturation and
luminosity.
All computations are based on the chips L*C*h values, as determined with the selected illuminant. The +sat
and -sat patches are based on the chroma (i.e. C*), the +lum and -lum patches are based on the lightness (i.e.
L*), and the +hue and -hue patches are based on the hue angle (i.e. h).
The L*C*h pad search algorithm uses the current DeltaE* formula, as selected in the DeltaE* display, for some
of its calculations; accordingly, changing the DeltaE* formula may result in a different L*C*h pad layout. In
Compare mode, the CIE94 and CMC(l:c) formulas are further impacted by the state of the "CIE94/CMC
When the algorithm cannot find a valid chip, a neutral color is used for the patch (same color as the tool
background) and "N.A." can be seen in the pop-up tag.
Clicking on any patch beside the center one will bring that patch to the center and all other patches will be
recomputed. You can thus navigate within the deck using the three L*, C* and h dimensions. You can also
select a chip by clicking directly in the color strip or on the arrows at both ends of the strip. You can also go
back and forth between the L*C*h pad and the List view.
Repeatedly clicking on +hue will move the selection in an anti-clockwise direction. Similarly, repeatedly clicking
on -hue will move the selection in a clockwise direction.
Important: Not all decks have dense and uniform distributions across the visible spectrum and you may find,
for example, that the nearest chip for increased luminance shows a significant hue and saturation difference.
This is less frequent in large uniformly distributed decks such as Munsell.
Note: The L*C*h space is more uniform than the xyY space. When navigating by clicking on the +hue and -hue
patches, you will follow a somewhat elliptical path around the illuminant, instead of the expected circular path.
This is more obvious when using a large uniformly distributed deck such as Munsell.
Note: The coordinates of all the patches as well as the color differences between the center patch and the
other patches are presented in the report saved using the "RGB vs RGB/Save Data..." menu.
In such instance, the L*C*h pad is disabled (i.e. it cannot be used to select patches).
When converting "TO" a deck, the center patch is the best match relative to the reference on the other side.
THE OTHER PATCHES ARE THEN DETERMINED RELATIVE TO THE REFERENCE, NOT THE CENTER
PATCH. As mentioned in the "L*C*h interface" section above, you can change the DeltaE* formula to see how
it affects the match.
Note: The coordinates of all the patches as well as the color differences between the reference patch and all
the L*C*h patches, including the center one, are presented in the report saved using the "RGB vs RGB/Save
Data..." menu.
• Sensitivity: Because the searching algorithm looks for the closest chip which minimizes the other two
parameters, for example the lightness and the hue when searching for the chroma (saturation), it may find a
chip which is almost the same as the one represented in the center patch. This may happen, for example, if
the deck contains chips of the same hue but with different surface finishes (i.e. mat, glossy, etc.). To filter out
these chips, we impose a threshold, or sensitivity, on the search algorithm. The default sensitivity value is
0,2 units of L*, C*, or h; it can be set between 0 and 10 units with 0,1 units steps.
• Patches outline: By default, the patches are surrounded by a thin black border. This border can be removed
by unselecting the "Decks L*C*h pad view: Draw borders around patches" checkbox.
Important: To prevent odd program behavior, a message will appear if you set the sensitivity setting too
close, or higher, than the hue search extent value, and when you set the hue search extent too close, or
lower, than the sensitivity. The program will then assign the nearest valid number to the parameter being set.
The patches surrounding the center patch show the nearest chips in the order they are catalogued. Although
there is a logic in how the catalogues are built, you may find the chips grouped by hue, saturation, or any other
criteria.
Clicking on any patch beside the center one will bring that patch to the center, and the other patches will shift
accordingly.You can also select a chip by clicking directly in the color strip or on the arrows at both ends of the
strip. You can also go back and forth between the List view and the L*C*h pad.
Note: Only the L*C*h display mode is available when the deck(s) is/are being converted "TO".
Two small black arrows on each side of the strip indicate the position of the selected chip. These chips
are shown as color patches in the L*C*h pad and List view.
When in Compare mode, the color strip can be used to select a chip by clicking either in the color strip itself or
on the arrows at both ends of the strip. Clicking on the arrows will move the selected chip by 6 positions in the
deck database. When in List view, clicking on the "upward" arrows will bring the top patch at the bottom of the
view, as if we were moving towards the top of the strip; similarly, clicking on the "downward" arrows will bring
the bottom patch at the top of the view, as if we were moving towards the bottom of the strip. Clicking on the
arrows in L*C*h pad view also moves the selected chip by 6 positions in the strip, but the overall pad view
change is not as obvious as with the List view.
Chip selection is also possible by clicking the L*C*h pad and List view patches.
In Convert mode, it is possible to select more than one deck as a destination (see Deck selection). In such a
case, the color strip shows a snapshot of ALL selected decks.
Note: The color strip cannot be used to select chips when a deck is being converted "TO".
• Name
The chip name is the usual reference number or name used in the color catalogue. In Convert mode, more
than one deck can be selected as a destination (see Deck selection); to prevent confusion when in this
mode, the deck name is also shown beside the selected chip ID in the name field:
Use the menu located below the "Name" field to select among the following color spaces: Munsell HVC,
L*C*h, xyY or XYZ.
The Munsell HVC values are not simply the ones corresponding to the closest sample in the Munsell deck
catalogue, but are INTERPOLATED values that closely match the selected deck color.
The L*C*h values are automatically updated, even if there is no color change, when you change the L*a*b* /
L*u*v* display and when you click in the "L*a*b* / L*u*v* / L*C*h in D50" checkbox described below. The
displayed values are:
1. L*C*abhab referenced to the space illuminant when L*a*b* is selected and the "L*a*b* / L*u*v* / L*C*h
in D50" checkbox is NOT selected
2. L*C*uvhuv referenced to the space illuminant when L*u*v* is selected and the "L*a*b* / L*u*v* / L*C*h
in D50" checkbox is NOT selected
3. L*C*abhab referenced to D50 when L*a*b* is selected and the "L*a*b* / L*u*v* / L*C*h in D50" checkbox
IS selected
4. L*C*uvhuv referenced to D50 when L*u*v* is selected and the "L*a*b* / L*u*v* / L*C*h in D50" checkbox
IS selected
Use the bottom menu to select either the L*a*b* or L*u*v* color space.
Checking the "L*a*b* / L*u*v* / L*C*h in D50" checkbox instructs the program to show L*a*b*, L*u*v* and
L*C*h values converted to illuminant D50, irrelevant of the illuminant of the selected deck. Of course, if the
space illuminant is D50, no change will be seen in the displays.
When the "L*a*b* / L*u*v* / L*C*h in D50" checkbox is unchecked, the L*a*b*, L*u*v* and L*C*h displays
show values corresponding to the illuminant of the selected space.
Changing the L*a*b* / L*u*v* selection or changing the "L*a*b* / L*u*v* / L*C*h in D50" checkbox status will
automatically update the L*C*h display, whether it is visible or not. Please refer to the additional information
on the L*C*h display above.
Note: Be cautious, the L*a*b* values shown in Adobe Photoshop are always in D50, irrelevant of the
illuminant of the selected space.
This diagram represents the chromaticity coordinates ("xy") of the Space or Deck colors selected on each side
of the RGB vs RGB tool window. This coordinates system was defined by the Commission Internationale de
l'Éclairage (CIE) in a standard published in 1931. It is based on the observation of color patches subtending a 2
degrees Field-of-View. The diagram is often referred to by the simpler "CIE1931, 2 degree" description. Please
see the xyY and XYZ section for a description of how the "xy" data is obtained.
In a nutshell, the "horseshoe" shape represents the gamut of colors perceived by the human eye. On the
contour are located pure (or fully saturated) colors typically generated by lasers. The "reddest" red is located at
the extreme right and the deepest blue at the bottom (x=0.175, y=0). Following the contour, clockwise from the
deepest blue, all other "rainbow" colors will be found (blue, cyan, green (toward the top), yellow, orange and
red). The straight line between red and blue represents a mix of the two colors located at the extremes of the
visible spectrum (red + blue = magenta).
The colors within the horseshoe are less saturated variants of the pure colors. Typical "whitish" illuminants
have colors located towards the center of the horseshoe.
Hint: The BabelColor logo can be used as a reminder of the locations of the red, green and blue zones.
The colors used to draw data in the diagram match the colors used to print the illuminant description in the
space interface and the chip name in the deck interface:
• Light green for Space #1 and Deck #1
• Orange for Space #2 and Deck #2
Additional data such as the chromaticities of the X-Rite/GretagMacbeth ColorChecker patches, the limits of
many standard CMYK spaces, or the locus of blackbody illuminants (i.e. the Planckian locus), can be
superimposed on the diagram by using either the menu from the "Graphics" icon in the toolbar window or the
"RGB vs RGB/Graphic data" menu.
In order to maximize the area of the display dedicated to the visible gamut, the "x" and "y" axis are clipped to
values less than one. Because it is possible to define a space, using the Custom RGB space dialog, which
extends past the displayed limits, a little arrow will appear next to the data point when its location is outside of
the display:
You may not be able to select any coordinates with a precision of 0,001; however, you can always tweak the
input with the R'G'B' and Y sliders afterwards. We suggest you select the xyY data display to see the input
coordinates in the selected space:
Selecting to which space the mouse click will input the data is done by selecting the proper radio button in the
"xy" mouse input display:
A mouse click (a left-click on a multi-buttons mouse) will direct the input to the space selected in the mouse
input control window. A mouse right-click (or ctrl + click on a one-button Mac mouse) will direct the input to the
other space. This mode can be used simultaneously with the R'G'B' input mode.
Note: The mouse input controls must be enabled to enter data via this method.
When clicking outside of a space perimeter, the triangle defined by the space primaries, the software finds the
closest valid color on the perimeter. By default, the program sets the Y coordinate (of XYZ) at the highest
permissible value for the selected "xy" data set (i.e. it sets the maximum value of the R'G'B' triad to 255). xyY
data is then converted in R'G'B', XYZ, L*a*b*, L*u*v*, L*a*b* (D50), L*u*v* (D50), Hex, HSB, and Munsell HVC,
and can also be used as input for the other side.
Mouse input is disabled when in L*a*b* / L*u*v* input mode, when the space is being converted "TO", or when
the side is in Deck mode. The various displays are shown in the Mouse input interface section.
Note: The mouse input controls must be enabled to enter data via this method.
See the chromaticity diagram section for more information on how the data is processed.
INPUT SELECTION
To select the space to which the input will be directed with a mouse click, click on the radio button with the
arrow pointing toward the chosen side:
The arrow of the radio button selected just above points towards the RIGHT side, or Space #2.
DISPLAY VARIATIONS
One or both buttons are automatically disabled when the program is set in specific modes. The various displays
are:
• Display seen in Compare mode when both sides are in RGB Space mode; both buttons are enabled:
When you select the LEFT side, as shown above, a mouse click will enter data in the LEFT side (Space #1),
and a mouse right-click will enter data in the RIGHT side (Space #2). When you select the RIGHT side, a
mouse click will enter data in the RIGHT side (Space #2), and a mouse right-click will enter data in the LEFT
side (Space #1)
• Display seen in Convert mode Right-to-Left (Space #2 to Space #1) OR Compare mode with Space #1 in
L*a*b* / L*u*v* input mode OR Compare mode with Deck #1 selected:
A mouse click will enter data in the RIGHT side and a mouse right-click will do nothing since mouse input is
disabled for the LEFT side.
• Display seen in Convert mode Left-to-Right (Space #1 to Space #2) OR Compare mode with Space #2 in
L*a*b* / L*u*v* input mode OR Compare mode with Deck #2 selected:
A mouse click will enter data in the LEFT side and a mouse right-click will do nothing since mouse input is
disabled for the RIGHT side.
• Display seen in Convert mode with the input space in L*a*b* / L*u*v* input mode OR Compare mode with
both spaces in L*a*b* / L*u*v* input mode OR Compare mode with both decks selected; both buttons are
disabled:
FORMULA SELECTION
Fourteen DeltaE formulas and variants are available:
• ∆E*ab
"CIELAB color-difference", referenced to the selected space or deck illuminant
(shown only if same illuminant for both sides)
• ∆E*uv
"CIELUV color-difference", referenced to the selected space or deck illuminant
(shown only if same illuminant for both sides)
• ∆E*ab D50
"CIELAB color-difference", referenced to D50 illuminant
• ∆E*uv D50
"CIELUV color-difference", referenced to D50 illuminant
• ∆E*94
∆E*94-textile
"CIE94 color-difference", referenced to the selected space or deck illuminant (shown only if same illuminant
for both sides). The ∆E*94-textile version has its kL factor equal to 2; kL equals one for the standard version.
• ∆E*94 D50
∆E*94-textile D50
"CIE94 color-difference", referenced to D50 illuminant
• ∆E*CMC(2:1)
∆E*CMC(1:1)
"CMC(:c) color-difference", referenced to the selected space or deck illuminant (shown only if same
illuminant for both sides). CMC(2:1) is used for acceptability (pass/fail) measurements while CMC(1:1) is
used for perceptibility measurements.
• ∆E*CMC(2:1) D50
∆E*CMC(1:1) D50
"CMC(:c) color-difference", referenced to D50 illuminant
• ∆E00
"CIEDE2000 color-difference", referenced to the selected space or deck illuminant (shown only if same
illuminant for both sides).
• ∆E00 D50
"CIEDE2000 color-difference", referenced to D50 illuminant
The ∆L*, ∆C*, and ∆H* parameters are defined in the CIELAB & CIELUV section; they represent the individual
contributions of lightness, chroma and hue to the global ∆E color difference. ∆h, defined in the L*C*h section, is
also shown because this angular difference is readily associated with a 360 degrees hue circle whereas ∆H* is
an indirectly derived value.
Since ∆L*, ∆C*, and ∆h can be positive OR negative, it is important to identify a reference and a sample. In
Compare mode, the reference is always on the LEFT side and the sample on the RIGHT side. In Convert
mode, the reference is always on the side being converted "FROM" while the sample is the side being
converted "TO".
Important: For the CIEDE2000 formula, the display shows the weigthed ∆L00, ∆C00, and ∆H00 values (and ∆h’),
instead of the unweighted ∆L*, ∆C*, and ∆H* values (and ∆h).
DISPLAY VARIATIONS
As mentioned above, all color-differences referenced to the selected space or deck illuminants are shown only
if the illuminants on both sides are the same (Ex.: Apple RGB and sRGB, where both spaces are defined with
illuminant D65). If not, the following display will be seen (Ex.: Apple RGB, with illuminant D65, and ColorMatch,
with illuminant D50):
You are still able to get a color-difference by selecting the corresponding D50 color-difference formula; for
DeltaE*ab it is DeltaE*ab D50:
where the L*a*b* coordinates of both spaces, translated in D50, are used to compute the numbers. All color-
difference formulas have an equivalent D50 selection.
Hint: If you want to see the L*a*b* D50 values used to compute the D50 color-difference, select the "L*a*b* /
L*u*v* in D50" checkbox appearing under the data displays of the corresponding space, or the "L*a*b* / L*u*v* /
L*C*h in D50" checkbox of the corresponding deck.
Hint: Although the results for only one color difference formula are displayed at a time, all formulas are
computed. The data for all formulas can be seen by saving or printing data.
Important: As per their definition, the CIE94 and CMC(:c) color-differences will be different depending on
which of the two color sides is defined as the reference, or if none of the sides can be considered a reference.
The software will automatically adjust the formula according to the definitions; as a result, variations in the
displayed values will be seen when going from Compare mode to Convert mode, or vice-versa. See the
DeltaE* section for detailed formula information.
There are four zones in which the colors of each Space (or Deck) can be compared. Please refer to the
screenshot above for the zone locations.
• Zone 1 – below the chromaticity diagram: The two selected colors are shown on two superimposed
squares. The larger square corresponds to Space #1 (or the Left side), and the smaller square
corresponds to Space #2 (or the Right side).
Space #1
Space #2
• Zone 2 – bottom-left: This part of the window is dedicated to patches seen side-by-side. Clicking on
these patches will change the size and background of the patches. The Zone 2 layouts are presented
later in this section.
• Zone 3 – upper-right: This zone is dedicated to patches of the selected colors super-imposed on
standard white and black backgrounds, and on a background of the other color. These color
combinations are also used to compute a Contrast Ratio defined by the Web Content Accessibility
Guidelines (WCAG), a ratio helpful in analyzing the legibility of colored text, with corresponding
examples shown in the bottom-right zone (Zone 4). The WCAG requirements are presented in the next
section, which is dedicated to the text layout zone.
• Zone 4 – bottom-right: This zone is dedicated to text of the selected colors shown on white, black, and
the other color backgrounds. Red and green bars indicate if these samples meet the WCAG
requirements; the text layout and the WCAG requirements are further described in the next section.
The next screenshot shows how the patches appear when the display corresponds to the more limited sRGB
space. Because the patches are located outside of the sRGB display profile range (gamut), with one or more
coordinates clipped at either zero or 255, clip indicators (!) are shown in the bottom-left corner of the patches.
The colors used to draw the clip indicators in the patches match the colors used to print the illuminant
description in the space interface and the chip name in the deck interface:
• Light green for Space #1 and Deck #1
• Orange for Space #2 and Deck #2
Important: Please note that the clipping indicators in the color patches displays are NOT indicative of any
clipping resulting from the conversion from one space to the other (ex.: from Space #1 to Space #2), or
between a deck and a space, or from L*a*b* / L*u*v* input. See the L*a*b* / L*u*v* input interface and data
displays sections for more information on these other clipping indicators.
In a multi-monitor setup, the display profile used for display purposes will be automatically updated when you
move the RGB vs RGB window across monitors. You can see the profile assigned to each monitor in the
“Color” tab of the Preferences dialog.
These layouts can be useful when comparing colors which may be displayed on grey, white or black
backgrounds, or when checking if two nearly identical colors will be seen as identical when viewed separated
by a distance.
Of course, you can adjust the window dimension so that the patches become one pixel high lines, as shown
below at full scale. This is useful for judging the visibility and contrast of such lines on black or white
backgrounds, and how they differ.
These two zones can thus be used to rapidly assess how the selected colors visually appear against various
backgrounds in both graphic and text form. You will also notice, in the top zone, labels with text and data, with
a label for each color on background combination. A label example is shown below; it corresponds to the
Space #1 color on white:
The numbers on the first line indicate the Contrast Ratio for the two colors (one selected color on a given
background), as defined in the Web Content Accessibility Guidelines (WCAG). The “AA” and “AAA” symbols of
the first line respectively indicate if this contrast meets or not the Minimum and Enhanced contrast
requirements for Normal text. The symbols of the second line indicate similar compliance for Large text. The
WCAG Contrast Ratio definition and the compliance thresholds are presented later in this section, but even
without this knowledge, the above label tells us that:
• the Contrast Ratio is 3,1 to 1;
• this color pair does not meet the Minimum and Enhanced contrast requirements for Normal text
(“AA” and “AAA” are red);
• this color pair meets the Minimum requirements for Large text (“AA” is green) and fails the Enhanced
requirements for Large text (“AAA” is red).
Note: Depending on the number of vertical pixels on your display, you will be able to see more or less lines of
each text combination. At least one line of each combination should be visible with a display size of 768 pixels
vertically. Also, you may need to hide the tool or task bar in your desktop to see the entire text layout.
Note: The labels with WCAG data will appear only if the window is enlarge wide enough.
The relative luminance is simply the “Y” of the XYZ color space where Y is normalized, for the purpose of this
equation, between zero and one, i.e. 0 and 1. The “0.05” constant added to each luminance is an estimate of
the typical viewing flare (reflection from ambient light) which will affect each color seen on a monitor. From the
Contrast Ratio definition, we see that the ratio can range between 1 and 21, which is commonly written as 1:1
to 21:1.
Please note that we have presented the contrast requirements in the table in the same order as they appear in
the WCAG labels of the RGB vs RGB window, as seen with this example:
When a requirement is met, the symbol is shown in green; when the requirement fails, the symbol is shown in
red. In addition, you will note that the requirement for Normal text/Level AA is the same as for Large
text/Level AAA (the required contrast is 4.5:1 in both cases), which means that when the contrast ratio is 4.5
or larger, the two corresponding symbols (“AA” on the first line, and “AAA” on the second line) become green,
as shown in th example above.
Note: In the additional notes provided to understand WCAG 2.0 (Understanding WCAG 2,0, Understanding
Success Criterion 1.4.3 - Contrast (Minimum)), it is acknowledged that a contrast ratio of 3:1 is the minimum
level recommended by ISO-9241-3 and ANSI-HFES-100-1988 for standard text and vision (i.e. 20/20 vision).
The higher value recommended for Minimum contrast and Normal text (4.5:1) takes into account a lower visual
acuity of 20/40. Similarly, the Enhanced contrast requirement for Normal text (7:1) is designed to account for
users with a 20/80 visual acuity.
Important: While you can select any RGB space, even different spaces for each sample, we recommend that
you use the same color space on each side, and, as well, the color space that you will use in your final
application. If you select a Space and a Deck, make sure you use the same Illuminant.
Hint: EXAMPLE 3 of Tutorial #4 proposes a method on how to optimize two colors to maximize text contrast.
This dialog is called with the "RGB vs RGB/Define custom RGB..." menu or by selecting the last menu item in a
RGB vs RGB window space selection menu.
Any change in a user-modifiable data value — with a white background — will take effect as you enter the data,
updating the other fields, the chromaticity diagram, and the gamma diagram.
SPACE SELECTION
Selecting any of the preset RGB spaces will automatically fill the "Illuminant", "Primaries" and "Gamma" input
fields with the values corresponding to this space. Modifying any field will automatically change the space
selection list to "Custom...", and the Space "name" field will allow user input (default name: "CustomRGB").
MESSAGE WINDOW
This window is used to indicate the various characteristics and limitations of the input fields.
When a new value is assigned by the user to the "x" coordinate, the system makes sure that the "x + y + z"
total remains equal to one. The "z" value will first be adjusted to fill the difference; if "z" reaches zero or one,
then the "y" value is adjusted. Similarly, when the user assigns a new value to "y", the "z" value will first be
adjusted to fill the difference; if "z" reaches zero or one, then the "x" value is adjusted.
Additional pre-calculated illuminants are available by pressing the "More..." button, which opens the Custom
illuminant dialog:
The selection list of this dialog offers additional standard illuminant presets, such as B, F2, F7, and F11, and
will automatically calculate the coordinates of either D-series illuminants or blackbodies as per a user specified
temperature (in kelvin). The equations of the D-series illuminants are presented in the Illuminants section.
A simulated representation of the illuminant "whiteness" relative to D65 is shown in concentric color patches;
these patches are to be used as a guide only.
Pressing "OK" will transfer the coordinates shown in the Custom illuminant dialog into the Custom RGB
space dialog.
The Bradford and CIECAT02 Chromatic Adaptation Transform (CAT) matrices between the Custom illuminant
and many standard illuminants (i.e. A, C, D50, D65, E, etc.) can be seen in the CAT matrices dialog opened
with the "RGB vs RGB/Table data/CAT matrices..." menu or with the "CAT matrices..." menu of the "Tables"
icon in the toolbar window.
Important: The illuminant has to be located within the triangle formed by the primaries. If the illuminant is
outside or on the periphery of this triangle, the program will not accept the Custom space when pressing "OK".
Note: The illuminant defined for the Custom space is also available in the illuminant selection list of a Color
Deck.
Note: The CAT matrix will map all custom illuminants to white in the color patches display (i.e. converted to
D65 for either sRGB or Apple RGB), even if the custom illuminant cannot be adapted (i.e. it has a definite color
tint).
When a new value is assigned by the user to any "x" or “y” chromaticity coordinate, the program makes sure
that the "x + y + z" total remains equal to one (1) by adjusting the "z" value. The coordinates can be either
positive or negative. Please be aware that coordinates which are outside of the chromaticity diagram spectral
locus (the horseshoe) will correspond to non-visible or non-real colors.
The coordinates shown in the input fields are displayed in the "CIE1931" diagram of the dialog. They are
identified by the "Current space" legend.
Note: Assigning negative chromaticity coordinates may result in negative “xyY”, “XYZ”, and “L*” values. In the
past (before CT&A V-5.2), when chromaticity coordinates were always positive, negative XYZ values happened
only because of rounding errors, and they were clipped to zero; this was the default (and only) processing.
Now, in order to get negative (i.e. non-clipped) XYZ values for a space with negative chromaticities, you must
first deselect the
Clip “xyY” and “XYZ” to zero in the “RGB vs RGB” tool
checkbox in the “Math” tab of the Preferences dialog.
Important: The primaries have to be positioned to form a triangle which encompasses the illuminant. If the
illuminant is outside or on the periphery of this triangle, the program will not accept the Custom space when
pressing "OK".
Important: Make sure the primary coordinates you enter are x, y, and z chromaticities, which are always
shown in lowercase. For instance, you cannot use the XYZ coordinates presented by Apple's ColorSync
Utility, as shown below. You first need to derive xyz from XYZ with the following equations (see this section for
more info):
x = X / (X+Y+Z)
y = Y / (X+Y+Z)
z = Z / (X+Y+Z) .
The values shown in the input fields are used to compute the simple and detailed gamma functions shown in
the "Gamma" diagram of the dialog. The functions are identified by the "Current space" legend. The equations
for gamma are shown in the RGB to R'G'B', and gamma section. Here is an example that illustrates how the
detailed gamma parameters affect the function:
To ease the design of the detailed gamma, the software will automatically compute the slope value that
matches the offset, gamma and transition values; the slope characterizes the linear portion of the gamma
function located below the transition. If a change is required to the current slope value, the new value will be
displayed with either a green or a red background. As a design rule, you should not define a detailed gamma
which results in a red (negative) slope. Here is what can happen:
• If the slope field is red or green, editing the field or pressing the "Tab" key while the cursor is in the field will
change the color of the slope background back to white. However, if the edited value is negative, it will be
clipped to zero.
• If the slope field is green and you do not edit it, the program will assign the displayed value as the new
slope.
• If the slope field is red and you do not edit it, a slope of zero will be nonetheless assigned when you click
"OK" in the dialog.
You can always select a different slope than the one suggested, as long as it is positive, and that you do not
further change the offset, gamma or transition; if this is the case, a new slope value will be suggested.
Important: If you set the detailed gamma to zero, the program will reset to zero all other detailed gamma fields
(offset, transition, and slope).
The "Space template" selection menu affects both the "CIE1931" and "Gamma" diagrams. Using this menu,
you can overlay a gray colored template corresponding to any of the preset RGB spaces or to the last saved
Custom space; you can also select to not display any template using the "(none)" selection. These templates
are to be used as design guides. The current space data is always shown in orange.
The "Gamma display" selection menu affects only the "Gamma" diagram. Using the menu enables you to see
either the simple or the detailed gamma function, or both. If the detailed gamma function is not defined for a
given space, a red X will be shown over the legend symbol.
Hint: To see the Planckian locus, or any other graphic data, you should select it using either the "RGB vs
RGB/Graphic data" menu or the menu of the "Graphics" icon in the toolbar window before opening the custom
RGB space dialog.
EXPORT TO FILE
At any time while you are editing the custom RGB space, you can export a file which contains the following
information:
1. the illuminant description and coordinates;
2. the primaries coordinates;
3. the gamma parameters;
4. the RGB to XYZ matrix coefficients;
5. the XYZ to RGB matrix coefficients.
This file can be opened by any text editor. It can also be imported in any spreadsheet that supports space
delimited tables.
Important: No check of the validity of the current RGB space is made before exporting the space data.
Note: A Custom space is not saved for use within the program RGB vs RGB tool until the "OK" button is
pressed.
You can save the profile with either the "*.icc" extension, the standard ICC profile extension, which is standard
on Mac but also common on Windows, or the "*.icm" extension usually found on Windows computers. While
the file extensions are different, the content of "*.icc" and "*.icm" profiles are the same.
Note: If you enter parameters for both a detailed gamma and a simple gamma, the ICC profile's gamma will be
built using the detailed gamma information.
Important: No check of the validity of the current RGB space is made before creating the profile.
Note: A Custom space is not saved for use within the RGB vs RGB tool until the "OK" button is pressed.
To change a side into Deck mode, click on the label identified "Space #1" or "Space #2" and slide the cursor to
the Deck selection:
To change a side back into Space mode, click on the label identified "Deck #1" or "Deck #2" and slide the
cursor to the Space selection:
For more information on the interface of each mode, look in the RGB Space interface and Color Deck interface
sections.
The Compare mode is readily identified by the following three buttons located on top of the chromaticity
diagram:
The buttons have the following appearance if the "Dim the chromaticity..." option is enabled:
To get back to the Compare mode when in either of the Convert modes, simply click on the central Convert
mode button:
For an RGB space in Compare mode, input is done either by assigning R'G'B' values, shown below on the left,
or by entering L*a*b* / L*u*v* data, shown below on the right (L*a*b*/L*u*v* data can be entered manually or
directly with one of the supported instruments).
When in Compare mode, you can go in Convert mode Left to Right by clicking the central Compare mode
button:
By default, clicking the Compare mode button will select the Convert Left-to-Right mode and the button label
will change to "Convert mode". Also, the button color as well as the color of the arrows on each side will
become yellow, as shown in the illustration just below.
To alternate between the Left-to-Right and Right-to-Left modes, simply click on one of the arrows:
OR
OR
use the "RGB vs RGB/Mode/Convert Left to Right" and "RGB vs RGB/Mode/Convert Right to Left" menus.
Note: There is NO action when clicking on the arrows while in Compare mode.
In Convert Left-to-Right mode, you can perform a conversion from (Space #1 or Deck #1) to (Space #2 or
Deck #2):
You will notice in the just-above illustration (Convert Right-to-Left) that all local inputs of the RGB space on the
LEFT, including the sliders and the "xy" mouse input, are disabled, and that the R'G'B' displays' backgrounds
are yellow.
When converting to a RGB space, the converted coordinates are high precision, non-integer, fractional
numbers which are rounded only for R'G'B' display purposes. This is why the color-difference, DeltaE*, when
there is no clipping, is exactly zero. When going back to Compare mode, this RGB space is injected rounded
integer values as R'G'B' inputs, and all other data values are updated. As a result, a small color difference
value may then appear in the DeltaE* display. For more information on integers and rounding, go to the data
integrity section.
Note: L*a*b*/L*u*v* input is not available in a RGB space when a space is being converted "TO".
Note: The Color deck List view is not available when a deck is being converted "TO".
Important: As part of the conversion process, the software determines, using a Chromatic Adaptation
Transform matrix, the coordinates that would be obtained if the color was measured using the illuminant of the
destination space or deck. When converting to a RGB space, colors which fall outside the new space gamut
are clipped to the nearest in-gamut color. This is the method used when converting color profiles with "Relative
Colorimetric" intent in Photoshop and other graphic editing programs that use this terminology. When
converting to a deck, the system finds the best match based on the current DeltaE* formula, as selected in the
DeltaE* display. Accordingly, changing the DeltaE* formula may result in a different match. Please note that the
match is always performed using the deck illuminant even if the D50 version of a DeltaE* formula is selected.
In Compare mode, a Color deck input is performed by clicking in the color strip or by clicking on one of the
L*C*h pad or List view patches. When converting "TO" a Color deck, its input only comes from the other side,
RGB space or Color deck.
Click on one of the input modes listed below for more information:
• R'G'B' space input modes
• R'G'B' data
• R'G'B' sliders
• L*a*b*/L*u*v* data entered manually
• L*a*b*/L*u*v* data entered with one of the supported instruments
• "xy" mouse input in the chromaticity diagram
• From another RGB space or Color deck, in Convert mode
The R'G'B' data and R'G'B' sliders input modes are disabled when the L*a*b* / L*u*v* input mode is active
OR when the input is from another RGB space or Color deck, in Convert mode. To go back to R'G'B' input if
the space is in L*a*b* / L*u*v* input mode, uncheck the L*a*b* / L*u*v* input checkbox. To go back to R'G'B'
input if input is from another RGB space or Color deck, change from Convert to Compare mode.
The L*a*b* / L*u*v* input input mode is disabled when the input is from another RGB space or Color deck
(i.e. when the space is being converted "TO").
The "xy" mouse input mode is disabled when in L*a*b* / L*u*v* input mode OR when the input is from
another RGB space or Color deck.
The Color strip, L*C*h pad, and List view input modes are disabled when the input is from another RGB
space or Color deck (i.e. when the deck is being converted "TO"); if you want to go back to the other deck
input modes, change from Convert to Compare mode.
The single and multiple parameters functions are the most common methods, and the single parameter gamma
is the most common overall. Not all spaces are defined with detailed gamma parameters, but all spaces have a
simple gamma value assigned. A single parameter function (simple gamma) is often used even if the space
has been defined by a multiple parameters function (detailed gamma); however, the detailed gamma will
provide more accurate colorimetric transforms.
By default, CT&A uses a detailed gamma, if defined, but it can be set to use a simple gamma via the
Preferences dialog. Please note that the Custom RGB dialog also supports both types of gamma functions.
To view the gamma parameters for a given space, use the "RGB vs RGB/Table data/Space data..." menu or
the "Space data..." menu of the "Tables" icon in the toolbar window.
In CT&A, a CAT is used to for space conversion in the RGB vs RGB and Metamerism Index (MI) tools, and
used to compute display colors in all tools. The CAT can be set in the Preferences dialog. Please note that it
should be set to "CIECAT02" in order to obtain the prescribed CII values in the Metamerism Index tool.
Note: In older versions of CT&A, before Version 4.x, CIECAT02 was used only to compute the CII in the MI
tool, and all other CAT functions were done with a Bradford CAT. Starting with CT&A Version 4.x, the CAT can
be selected and CIECAT02 is the default.
The Munsell tools window is opened either by clicking on the corresponding icon on the toolbar window, or by
selecting the "Tools/Munsell" menu.
Defined in the
RGB vs RGB tool
Custom RGB space
dialog.
Here is an example where we use the L*a*b* output converted from Munsell as input to the L*a*b* to Munsell
conversion:
The ∆Eoo (CIEDE2000) color difference data field shows the difference computed between the L*a*b* output
from the Munsell to RGB and L*a*b* conversion and the L*a*b* input of the L*a*b* to Munsell converter. Of
course, in this example, we just assigned the output as input and the color difference is zero! More interesting
here is the Munsell output from the L*a*b* to Munsell conversion (= 5.0YR 6.5/12.0) which is exactly the same
In this second example we use the Munsell HVC output from the L*a*b* to Munsell* conversion as input to
the Munsell to RGB and L*a*b* conversion.
Do a mouse right-click
on the color difference
data fields to select the
color difference
formula.
We see a small color difference (CIEDE2000=0,67) in the L*a*b*-to-Munsell-to-L*a*b* roundtrip; this difference
gives us an idea of the overall conversion precision. A similar analysis can be performed using RGB inputs and
outputs.
Hint: As shown on the screenshots of the preceding pages, you can copy input and output data by making a
mouse right-click on a data field. When copied, the data is transferred into the clipboard. Depending on the
selected menu item, the data may or may not be separated by Tabs; Tab separated data can easily be pasted
in a spreadsheet or document table.
For L*a*b* input, there is an additional constraint since there is no precise minimum or maximum limit on the a*
and b* coordinates. Yet, for L*a*b* we can still check if the corresponding chromaticity is within the chromaticity
diagram; in this case, the limits vary depending on the selected illuminant.
In the Munsell tools, chromaticity validity checks are performed on RGB and L*a*b* inputs. For Munsell HVC
inputs, the Chroma is limited by the Munsell Color System data tables. The following screenshot shows a
variety of flags that you will see when colors are off-limit. For the screenshot, we first typed the ProPhoto RGB
coordinates in the RGB to Munsell section. We then assigned the Munsell output (from RGB) as an input to
the Munsell to RGB and L*a*b*. We finally assigned the L*a*b* output of the Munsell to RGB and L*a*b*
conversion as an input to the L*a*b* to Munsell conversion.
The “NaC” flag before the RGB and L*a*b* inputs stands for “Not a Color”, indicating that the corresponding
chromaticity coordinates are outside of the chromaticity diagram. You can verify this with the RGB vs RGB tool.
The “MAX for G” flag indicates that the assigned input, from the RGB to Munsell conversion, is larger than the
maximum Chroma used in the Munsell Color System database; this is a program limitation. Please note that
the maximum Chroma is different for each Hue.
Finally, you will also notice exclamation points ( ! ) in the green color patches. This symbol indicates that the
patch color is outside of the display color profile, i.e. that it is clipped.
Note: In Windows, if the i1Pro/i1Pro 2 or i1Pro3 USB drivers are not installed, please consult the
"CT&A_Readme.txt" file located within the main CT&A application folder. This file can be opened directly with
the "Start menu/BabelColor/CT&A Readme" shortcut.
Instrument button support: When the Munsell tools window is selected, i.e. brought to the front, and
assuming that a compatible instrument is selected and recognized, a large blue indicator appears next to a
"Measure" button. This indicator identifies the data that will be measured if you press the instrument button; of
course, you can also do a mouse click on any data entry button.
SETUP
• There is no user setup for this tool. The program will set itself in reflectance mode and the data will be
computed for illuminant C and the 2 degree Observer. However, it is assumed that your instrument is
properly connected and detected, as discussed above.
Note: If you are using an i1Pro 2 with the "i1Pro / i1Pro 2 (XRGA)" driver, an i1Pro 3, or an i1Pro 3 Plus, all
measurements will be taken with the three "Measurement Conditions", M0 (Ill-A), M1 (D50), and M2 (UV-cut),
as defined in ISO 13655 (Ref. 42). A description of the M0/M1/M2 measurement conditions can also be
found in the FluoCheck tools. If you are using an i1Pro, or an i1Pro 2 with the "i1Pro / i1Pro 2 (non-XRGA)"
driver, the program will select the default measurement conditions supported by the instrument and data will
not be shown for the other measurement conditions.
• If not already done, calibrate the instrument by clicking on the "Calibrate" button and following the on-screen
instructions.
INSTRUMENT MEASUREMENT
To make a measurement, just click on the "Measure" button or press the instrument button. Apart from the
measurement in Munsell Hue Value/Chroma notation, the window can also show the L*a*b* values relative to
Illuminant C.
If you take a measurement of a color patch, with non-florescent inks, printed on a non-fluorescent substrate,
the M0, M1, and M2 values should be identical. However, if the ink or substrate is fluorescent, you will likely
obtain three different values.
Note: A clipping indicator appears in the bottom left corner of the color patch when the color of the sample it
represents is outside of the RGB space gamut of the monitor.
Click on "Save to file..." to save a Munsell report which will also include the user-typed conversions. The report
has tab-delimited data that can be directly imported in a spreadsheet program and opened in many text editing
applications (it is suggested to use a monospace font, such as Courier, in order to facilitate formatting). The
report spectral measurements can also be read by software, such as BabelColor PatchTool, which can open
CGATS compatible files.
The CRI tools window is opened either by clicking on the corresponding icon on the toolbar window, or by
selecting the "Tools/CRI, CQS, CRI2012, TM-30" menu.
The tools comprise the current Color Rendering Index (CRI) method as well as proposed replacement metrics,
and new metrics for gamut area and memory colors. A short description of the metrics is presented below; a
more complete description of each metric is presented in this section.
• CRI (CIE 13.3:1995): The only agreed method for computing the CRI. It comprises 14 individual indices
of which the first 8 are used to compute Ra, the general index usually presented as the "CRI" by lamp
manufacturers. The ninth index (R9), computed from a saturated red sample, is often negative; while it is
not used to compute the general index, R9 is sometimes used in conjunction with Ra when assessing a
light source. The remaining indices are also based on more saturated samples and, except for R14, their
values are generally lower than the first 8 indices.
• CQS (Color Quality Scale, NIST Version 9.0.3): A proposed CRI replacement developed by the USA
National Institute of Standards and Technology (NIST). It addresses specific complaints against the
standard CRI by using 15 saturated samples, by not penalizing chroma increase, and by using RMS
averaging instead of arithmetic mean to compute the general index (Qa). It also includes a color fidelity
metric (Qf), where saturation effects are not applied, and a relative gamut area metric (Qg). Many
versions of this metric were developed; the one used in CT&A is the recommended version to be used at
publication time.
Important: The CRI tools can accept input from a file or from a supported instrument. A CONNECTED
INSTRUMENT IS NOT REQUIRED in order to use these tools. A file may contain one or more spectrums. The
file may be either in CGATS format, or a plain text file; the specific requirements for each file formats are
presented in the CRI input file requirements section. There are two methods to open/load a file:
• 1st method: Click on the "Load..." button and select the file to open with the file input dialog.
• 2nd method: Drag-and-drop the file to open on the "Load..." button OR on the table located beside the
input buttons. You can also drag-and-drop multiple files at a time.
Important: To measure a light source with the CRI tools, you need to have an i1Pro series spectrophotometer
connected to the computer on which CT&A is running. The instrument must also be properly recognized by the
program; this is confirmed by a small green light beside the instrument selection menu in the toolbar window,
and by the "Calibrate", "Get Ambient", and "Tune" buttons of the CRI window being enabled (all selection
menus will be disabled and most data fields will not be available if the program is not activated). If you plug an
instrument in your computer after the program start, you can attempt to connect the instrument by selecting
"Try to connect again..." in the Instrument menu. A status of the selected instrument can always be obtained by
clicking on the "Info" button located in the toolbar window.
Important: Please make sure that your instrument supports the use of an ambient adapter as some versions of
the i1Pro and i1Pro 2 are sold without this capability.
Note: In Windows, if the i1Pro/i1Pro 2 or i1Pro 3 USB drivers are not installed, please consult the
"CT&A_Readme.txt" file located within the main CT&A application folder. This file can be opened directly with
the "Start menu/BabelColor/CT&A Readme" shortcut.
Instrument button support: When the CRI tools window is selected, i.e. brought to the front, and assuming
that a compatible instrument is selected and recognized, a large blue indicator appears above the "Get
Ambient" button. This indicator confirms that the next instrument key press will be assigned to this button; of
course, you can also do a mouse click on the button.
Because the human visual system is very adaptive, it automatically adjust itself to a vast array of light sources
and accept as "white" sources whose dominant wavelength varies from the yellowish to the bluish. Of course, if
the source's tint is too strong, our brain will then consider that the source is "colored" and process all viewed
samples accordingly. The acceptable "white light" zone is defined by a line in the CIE1960 (u, v) coordinates
plane computed with the chromaticity of Planckian radiators (i.e. blackbodies) of varying temperature, between
1000 and 100,000 kelvin in CT&A, to which is added a certain tolerance expressed as a distance (Duv, ±0.05 in
CT&A) from the Planckian locus (Ref. 52). The Color Temperature of the blackbody which corresponds the
most with the Test source is called the Correlated Color Temperature (CCT).
A low temperature blackbody can easily be simulated by a candle, and a tungsten or halogen-tungsten lamp is
very close to a blackbody with a temperature of 2856 K (i.e. Illuminant A). As a blackbody temperature goes
higher, so does the proportion of blue light that it emits, with a corresponding shift in its perceived dominant
wavelength. For temperatures higher than 5000 K it was customary until recently to use a phase of daylight
corresponding to this temperature (CIE 15: 2004, Table T.2; herein called the D-series illuminants) instead of
the blackbody spectrum. The difference between a blackbody and a D-series illuminant is that the D-Series
illuminant, while based on a ubiquitous blackbody, the Sun, also take into consideration atmospheric absorption
and sky illumination, which vary according to time of day, time of year, latitude, cloud cover, etc.
Note: While the computed CCT of a light source is valid if its coordinates are within ±0.05 chromaticity units
from the Planckian locus, acceptable Duv values are usually much lower, with a maximum of ±0.0054 being
specified in the CRI standard (CIE 13.3: 1995), and ±0.006 specified in ANSI C78.377-2008 (Ref. 53).
However, it is important to note that in ANSI C78.377-2008, for CCTs of 4000 K and higher, the center of the
Duv tolerance zone is not on the Planckian locus in order to take into consideration the locus of the D-series
illuminants which is slightly offsetted relative to the Planckian locus.
For the "standard" CRI, the CQS (Color Quality Scale), and CRI2012 methods, the Reference source is:
• a Planckian radiator (i.e. a blackbody) if the CCT is less than 5000 K;
• a D-series (i.e. a phase of CIE Daylight) illuminant if the CCT is equal to or larger than 5000 K.
While the indices of samples 9 to 14 are not taken into consideration when computing the general index, R9 is
a case in itself. Because it is a markedly more saturated red, it is not uncommon to get negative R9 values
which could seriously affect the general index if averaged with the differences of the first eight samples.
Samples 10 to 12, although also more saturated, would similarly affect the average. The potential impact of R9
on a global CRI index, and of the more saturated colors in general, was recognized early on and it was decided
to base the CRI on the first eight samples, while keeping R9 to R14 as special indices only.
Of course, not all light sources are such that R9 is dramatically bad, but since only Ra is typically provided by
lamp manufacturers, it is easy to see how a lamp with an acceptable CRI can give poor results when
illuminating a saturated red. This said, it is generally admitted that a "CRI" number alone is not enough to
guarantee the quality of a light source and other measurements need to be done in parallel. This is why the
Metamerism Index (MI) measurements described in ISO 23603/CIE S 012 was defined (see the ISO 3664+
tools section). By measuring both the CRI and the MI, one can get a very precise evaluation of a light source.
Unfortunately, the MI is specifically targeted to the light sources used in the graphic arts field: D50, D55, D65,
and D75. For other CCTs, one is left only with the CRI, yet, by also considering R9 as an associated metric, as
some lamp manufacturers are said to be contemplating, one could get a better fidelity metric, without the need
to define a new standard.
Ever since the CRI computing method was adopted, there were proposals to improve it but none of them could
be agreed upon as an international standard. It is interesting to note that the method is described in a
Technical Report (CIE 13.3: 1995), and is not presented as a Standard, although it is used as such because
it was at least agreed upon! With the advent of Solid-State Lighting (SSL), there was renewed interest in
revamping the CRI and a new CIE Technical Committee (TC1-69) was formed in 2006. While the CRI was
designed mostly for smooth and continuous light sources with the relatively small number phosphor peaks of
standard fluorescent lamps, the essentially unlimited combinations of narrow bandwidths Light Emitting Diodes
(LED) did not mesh well with the CRI method.
In 2010, the CQS was almost voted by the TC1-69 CIE Technical Committee as the replacement standard for
the CRI. In a dramatic finale, it was rejected and it was suggested that two metrics be recommended, in two
new committees. These committees were formed in 2012:
• TC1-90 Colour Fidelity Index: To evaluate available indices based on colour fidelity for assessing the
colour quality of white-light sources with a goal of recommending a single colour fidelity index for
industrial use.
• TC1-91 New Methods for Evaluating the Colour Quality of White-Light Sources: To evaluate available
new methods for evaluating the colour quality of white-light sources with a goal of recommending
methods for industrial use. (Methods based on colour fidelity shall not be included: see TC1-90.)
The two committees were to write a report to propose the new metrics in 2015 but progress was slower than
expected. The TC1-90 committee issued its report, CIE 224, in 2017. The CIE 2017 Colour Fidelity Index (Rf)
is based on IES TM-30-15 to which a few changes were applied; these changes were simultaneously accepted
by the group responsible for the TM-30 method and incorporated in the TM-30-18 version (now TM-30-20).
Note: According to a CIE Division 1 presentation, the CIE 224:2017 Colour Fidelity Index is not a replacement
for the general color rendering index (Ra of CIE 13.3:1995).
The TC1-91 committee is still working on the Colour Quality methods. However, do not expect a final answer
on this subject since the committee will only evaluate various methods and will not provide a recommendation
on which method to use.
Note: One of the complaints against CRI2012 is that many samples cannot be accurately represented on most
computer displays. In the CRI tool you may notice that some of the CRI2012 patches exhibit an exclamation
point in the bottom-left corner. This is a flag to indicate that the patch color is outside of the display gamut, with
at least one RGB coordinate clipped to zero or 255. The number of clipped colors will be less for displays which
support larger gamut spaces, such as Adobe (1998) RGB. Of course, the computed values are not affected by
the display gamut. Yet, a revised version of CRI2012 (referred to as CRI2014 in some texts) may use different
samples for this reason.
Once we determine the CCT of the Test source and define the Reference source, we can compute the
chromaticity coordinates (J'a'Mb'M) of each CES with both the Test and Reference sources. From this point, the
data is processed in two separate paths:
• We compute the color difference for each CES, which provides the Color Fidelity for each sample
(Rf,ces), and the overall Fidelity Index (Rf). We also compute the average fidelity index for skin
(Rf,skin), which is simply the average of the individual indices (Rf,ces) of samples CES15 and CES18.
• We group the samples in 16 bins covering 22.5 degrees each in the a'Mb'M chromaticity plane (herein
called Hue Angle Bins) and we compute the average chromaticity for each bin. The average
chromaticity data is processed to obtain:
o The so called “Local” data: The color difference, Local Color Fidelity (Rf,h), Local Chroma
Shift (Rcs,h), and Local Hue Shift (Rhs,h) for each Hue Angle Bin.
o The Gamut Area: The areas enclosed by the average chromaticity coordinates of the
Reference and Test sources represent their respective gamut. The area covered by the
Reference source defines the 100% gamut reference; the ratio of the two areas gives us the
Gamut Index (Rg).
o The Color Vector Graphic (CVG): We normalize the Hue Angle Bin chromaticity coordinates
of the Reference source so that they are represented by a perfect circle. The Hue Angle Bin
coordinates of the Test source are then shown in relation with the reference circle; an increase
in saturation (i.e. chroma) is shown as a point outside of the circle and a desaturation as a
point within the circle. Any hue shift is immediately visible if the shift direction is not aligned to a
radius of the reference circle.
Note: While the maximum value for Rf is the same as for the CIE CRI, with a value of 100 meaning that the
Test source is equivalent to the Reference source, there is no official value assigned to a non-acceptable
index. In the TM-30-15 interface, the value of “80” on the fidelity index axis is shown in bold simply as a
reminder of the CIE CRI index threshold.
Note: The CRI2012, TM-30-15, TM-30-18, TM-30-20, and CIE 224 methods all use the CIECAT02 Chromatic
Adaptation Transform (CAT). However, we have noticed that CRI2012 uses a “gamut-fixed” matrix (Ref. 56)
while the others use the “standard” matrix. The differences between the results obtained with the two matrices
are generally small, but we provide the option to select one or the other nonetheless. The option is set in the
"Math" tab of the Preferences dialog (The CIECAT02 matrix is sometimes referred to as MCAT02).
Note: In CT&A, all data is processed at 5nm intervals between 380 nm and 730 nm while the CES spectral
data is provided between 380 and 780 nm. Our tests done with the 300+ spectrums provided with the TM-30-
15 documentation show that the effect of limiting the processing to 730 nm on the Rf and Rg indices is
negligible.
Note: The CES are not distributed uniformly in each Hue Angle Bin and the number of samples per bin will vary
with different test sources. The number of samples per bin is automatically provided in the report file whenever
Hue Angle Bin data is selected for export (Hue Angle Bins data fields: Rf,h, Rcs,h, and Rhs,h).
Note: The Rg vs Rf graph has a dark grey zone in which you should never see a test point. The graph also
has a light grey zone in which you may sometimes see a test point; if this happens, check this test source
position relative to the Planckian locus since it may have a large Duv value.
These guidelines are not associated with a single parameter, Rf for instance, but consider a combination of
parameters. For example, the “Best” fidelity criteria combines a Color Fidelity (Rf) of 76 or higher with a
Chroma Shift of the first Hue Bin (Rcs,h1) between -1% and +9%, and a Gamut Index (Rg) of 100 or higher.
Note: The chroma shift of the first Hue Bin (Rcs,h1), corresponding to red patches, was selected in the
guidelines because it is the strongest single predictor of subjective evaluations (Ref. 64), i.e. it correlates well
with the overall visual assessment of the test subjects. It is interesting to note the similarity in the importance of
Hue Bin #1 and patch R9 of CIE 13.3, with the difference that this Hue Bin is always included when computing
the overall fidelity whereas R9 was often discarded.
Important: Be careful when comparing TM-30-15 results with those of TM-30-20 (or TM-30-18). While most
numbers are the same, the Rf values of TM-30-15 are lower than the ones computed in TM-30-20. This is
particularly important if you intend to use the guidelines of TM-30-20 Annex E for TM-30-15 data, an idea which
we do not recommend.
Once we determine the CCT of the Test source and define the Reference source, we can compute the
chromaticity coordinates (J'a'Mb'M) of each CES with both the Test and Reference sources. From this point, the
data is processed in two separate paths:
• We compute the color difference for each CES, which provides the Color Fidelity for each sample
(Rf,ces), and the overall Fidelity Index (Rf). We also compute the average fidelity index for skin
(Rf,skin), which is simply the average of the individual indices (Rf,ces) of samples CES15 and CES18.
• We group the samples in 16 bins covering 22.5 degrees each in the a'Mb'M chromaticity plane (herein
called Hue Angle Bins) and we compute the average chromaticity for each bin. The average
chromaticity data is processed to obtain:
o The so called “Local” data: The color difference, Local Color Fidelity (Rf,h), Local Chroma
Shift (Rcs,h), and Local Hue Shift (Rhs,h) for each Hue Angle Bin.
o The Gamut Area: The areas enclosed by the average chromaticity coordinates of the
Reference and Test sources represent their respective gamut. The area covered by the
Reference source defines the 100% gamut reference; the ratio of the two areas gives us the
Gamut Index (Rg).
We finally display the Fidelity Index (Rf) and the Gamut Index (Rg) on a graph of Rg vs Rf.
Note: While the maximum value for Rf is the same as for the CIE CRI, with a value of 100 meaning that the
Test source is equivalent to the Reference source, the comparison stops here. The Illuminating Engineering
Society (IES) has published guidelines, TM-30-20 Annex E and F (Ref. 57-67-68), to better relate the metric
data with various color rendition intents, such as “Preference”, “Vividness”, and “Fidelity”. Table E2 from
TM-30-20 Annex E is reproduced on the next page.
Note: The CRI2012, TM-30-15, TM-30-18, and CIE 224 methods all use the CIECAT02 Chromatic Adaptation
Transform (CAT). However, we have noticed that CRI2012 uses a “gamut-fixed” matrix (Ref. 56) while the
others use the “standard” matrix. The differences between the results obtained with the two matrices are
generally small, but we provide the option to select one or the other nonetheless. The option is set in the "Math"
tab of the Preferences dialog (The CIECAT02 matrix is sometimes referred to as MCAT02).
Note: In CT&A, all data is processed at 5nm intervals between 380 nm and 730 nm while the CES spectral
data is provided between 380 and 780 nm. Our tests done with the 300+ spectrums provided with the TM-30-
15 documentation show that the effect of limiting the processing to 730 nm on the Rf and Rg indices is
negligible.
Note: The CES are not distributed uniformly in each Hue Angle Bin and the number of samples per bin will vary
with different test sources. The number of samples per bin is automatically provided in the report file whenever
Hue Angle Bin data is selected for export (Hue Angle Bins data fields: Rf,h, Rcs,h, and Rhs,h).
Note: The Rg vs Rf graph has a dark grey zone in which you should never see a test point. The graph also
has a light grey zone in which you may sometimes see a test point; if this happens, check this test source
position relative to the Planckian locus since it may have a large Duv value.
TM-30-20 vs TM-30-15
The three main differences between TM-30-20 and TM-30-15 are:
i- Some of the 99 Color Evaluation Samples (CES) are not defined outside of the 400 to 700 nm range. In
TM-30-15 the data below and above this range was extrapolated using a derivative method. In
TM-30-20, flat extrapolation using the 400 nm and 700 nm values is used. The effect on the computed
indices is negligible.
ii- For the Reference source, the transition between a Planckian radiator and a D-series illuminant is now
between 4000 K and 5000 K (instead of between 4500 K and 5500 K in TM-3015).
iii- The scaling factor used to compute the Color Fidelity (Rf) index is now 6.73 instead of 7.54. The overall
effect is a noticeable increase in all Color Fidelity values (Rf, Rf,skin, Rf,ces, and Rf,h); there is no
change to the Chroma Shift (Rcs,h) and Hue Shift (Rhs,h) values.
These changes were done to match the TM-30-20 Color Fidelity index (Rf) to the CIE 224:2017 Colour Fidelity
Index (Rf) (Ref. 65) recommended by the CIE TC1-90 committee. Please note that CIE 224 is only concerned
by Rf and not by the other indices derived in TM-30-20 (Rg, Rf,skin, Rf,h, Rcs,h, etc.).
Note: According to the CIE, the CIE 224:2017 Colour Fidelity Index is not a replacement for the general color
rendering index (Ra of CIE 13.3:1995) but only a step in its eventual replacement.
TM-30-20 also includes specifications on how the Color Vector Graphic (CVG) should be formatted in reports
and proposes specific layouts for three report sizes. These reports can be generated using CT&A’s TM-30-20
report selector dialog.
Three Priority Levels are defined for each intent, with “Level 1” being the most stringent. Because of how the
design constraints were defined and how the parameters are computed, it is not possible to find a light source
which reaches a “Level 1” for all three intents. However, a test source which is identical to a reference source
will exhibit a Level 1 for Preference (P1) and Fidelity (F1), and a Level 3 for Vividness (V3). These results are
usually presented in the form “P1 | V3 | F1”.
These parameters were selected because they have low correlation with each other and probe different
aspects of color rendering quality (Ref. 64). In particular, red chroma which characterizes the patches of Hue
Bins 1 and 16 (i.e. h1 and h16), is the strongest single predictor of subjective evaluations i.e. it correlates well
with the overall visual assessment of the test subjects. It is interesting to note the similarity in the importance of
Hue Bin #1 and patch R9 of CIE 13.3, with the difference that this Hue Bin is always included when computing
the overall fidelity whereas R9 was generally discarded.
Important: Be careful when comparing TM-30-20 results with those of TM-30-15. While most numbers are the
same, the Rf values of TM-30-20 are higher than the ones computed in TM-30-15. This is particularly important
if you intend to use the guidelines of TM-30-20 Annex E for TM-30-15 data, an idea which we do not
recommend.
In the CRI tools window, the TM-30-20 Color Rendition Performance can be assessed with the values of the
three parameters used for categorization analysis, Rf, Rg, and Rcs,h1 and with the categorization results
derived from these numbers. Two examples are shown below:
Rf,h1
In the top example of the preceding page, both Rf and Rf,h1 are green. Rf meets the F3 level while Rf,h1
exceeds the F2 level (Rf,h1 is not used to define the F1 level). Overall, this sample meets the requirements of
the F3 level.
Please note that while a parameter may meet the requirements of one Design Intent level, this does not mean
that the minimal level (i.e. 3) is achieved. For instance, in the top example, the gamut index (Rg=106) meets
the V3 level; however, Rcs,h1 is just below the 0% requirement and the Vivid categorization is shown as” V-”.
In the bottom example Rf exceed the P1 level but does not meet the F3 level; it is thus shown in BLUE. Rg
meets the P3 level but not the P2 level. However, Rcs,h1 is -20%, well below the P3 level and is thus shown in
RED. Overall, the minimum Preference level is not met and the Design Intent performance is shown as “P-“.
In separate psychophysical analysis studies, Smet et al. (Ref. 49) have shown a good correlation of the number
obtained by the arithmetic average of the GAI and Ra (= (GAI + Ra) / 2) is well correlated with the perception of
"naturalness" (associated with Color Fidelity). This combined metric is identified as "GAI and Ra" in CT&A.
The GAI is very similar, in terms of computation method, to Qg of CQS. However, whereas the GAI reference
area is a surface computed with Illuminant E, the reference area in Qg is computed with the Reference source
White Point. This choice of the reference area has quite an effect on how these respective metrics are
correlated with perceptual studies. While GAI is associated with "Color Discrimination", Qg is better associated
with "Color Preference" (and "GAI and Ra" with naturalness/Color fidelity).
Note: It is shown in Ref. 51 that the CCT alone is moderately correlated with gamut size and Color
Discrimination, with higher discrimination associated with higher CCTs. There is thus no surprise in GAI being
well correlated with Color Discrimination since the GAI Reference area is associated to a fixed CCT and the
Test area is associated with the measured CCT.
The individual indices (Si) describe the degree of similarity with each object's memory color. A general degree
of similarity (Sa), is obtained with the geometric mean of the ten Si values. A Sa score of 1 means that the
light source renders all familiar objects exactly as we expect them to look. Sa is then rescaled between 0 and
100 with a sigmoid function; the rescaled value is Rm, the general memory quality index. Please note that, in
practice, any Sa with a value of 0,5 or less is rescaled to Rm=0.
In the cluster list above, except for Ra12 which is an older version of Ra,2012, we have indicated only the
metrics which are computed in CT&A. In their analysis, the authors show that Qg is better correlated than Qa
and Qf for discrimination, but not as good as GAI, yet they have found that Qg is more closely associated to the
metrics of the "Preference" cluster than to the ones of the "Discrimination" cluster. They also suggest
simultaneously using two metrics, such as Qa and Qg, which are computed using the same samples, for more
accurate predictions; the reader should consult Ref. 51 for a complete analysis. In another study, Smet et al.
(Ref. 49, Table 2) have categorized 13 metrics in two categories. Here is how the metrics supported by CT&A
are categorized:
• Naturalness: CRI (Ra), CQS (Qa, Qf); "GAI and Ra"
• Preference / Attractiveness: GAI, MCRI (Sa)
You will note that Ra, Qa and Qf are considered better for Fidelity measurements in one study and better for
Naturalness measurements in the other. There is no issue here, the terms “Fidelity”, “Quality” and
“Naturalness” are often used interchangeably when categorizing illumination.
So with all these possibilities you may not be at ease to make a choice. Of course it depends on your design
intent; the illumination requirements for a press room are not the same as those for a candy store. One thing is
sure; we do not recommend using Ra alone for “Fidelity” assessment! You should as a minimum also consider
R9 in combination with Ra but you may find that very few light sources will qualify. This is where a modern
multi-metrics method such as TM-30-20 can be helpful.
Preliminary experiments with TM-30-15 and TM-30-18 (Ref. 64) had shown that simultaneously taking into
consideration Rf, Rg, and the Chroma Shift of the first Hue Bin (Rcs,h1) could provide a good match to
subjective qualities of the sources such as “Preference” and “Naturalness.” Additional experiments with
TM-30-18 have been compiled since and used to define guidelines for the “Preference” “Vividness” and
“Fidelity” intents. These guidelines were published as TM-30-18 Annex E and additional background and
evidence to support the recommendations were published in TM-30-18 Annex F (Ref. 67-68); these annexes
are now integrated in the TM-30-20 main document (Ref. 57). The guidelines are summarized in the TM-30-20
description section.
The CRI data ranges section presents the nominal ranges for the CRI tools metrics (except TM-30-20 numbers
which can be found here), the CCT/Duv acceptability ranges, and some results obtained with standard CIE
illuminants.
The metrics selected in CT&A’s CRI tools hopefully provide an overview of the current state of knowledge.
Time will tell if TM-30-20 will replace the old CRI, i.e. CIE 13.3:1995, or if this is yet another step towards this
goal. Nonetheless, the newer metrics are backed with significant validation experiments which, at the very
least, show that we cannot go back to a single-number-fits-all metric to describe the rendering quality of a light
source.
Data menus
Data table
Metric selection
Spectrum graph
TM-30-15 / TM-30-20
Hue Angle Bin
graphs
Patches
representation
Chromaticity graph
In the screenshot above we see that measurement #26 is selected in the table. Some of the metrics results are
shown in black while others are shown in red or orange. You will find a description of all the supported metrics
in the CRI tools description section; the expected ranges for each metric are discussed in the CRI metrics and
Duv ranges section.
The instrument should be calibrated before making any measurements. Click on the "Calibrate" button of the
CRI window and follow the indications to perform an "Ambient" mode calibration. You will be prompted to
perform the calibration if you attempt to make a measurement without prior calibration.
Note: While the CRI tools accept 5 nm bandwidth data files (see CRI input files requirements) which are
processed with a 5 nm workflow, 10 nm input data from measurements or from files are also processed
internally with a 5 nm workflow. 10 nm data is interpolated to 5 nm with the user-selected spectral interpolation
method (cubic spline / Lagrange).
• 2nd method: Drag-and-drop the file to open on the "Load..." button OR on the table located beside the
input buttons. You can also drag-and-drop multiple files at a time.
When the table contains multiple measurements, select the measurement for which you want to see the
processed data by clicking in one of the first two columns of the selected measurement/row. You can navigate
in the measurement table with the UP and DOWN arrow keys.
To edit a measurement name, first click on the "Name" column; this will select the current name. You can use
the LEFT and RIGHT arrow keys to position the cursor or the UP and DOWN arrow keys to edit the previous or
next measurement name.
In Windows, you can select any number of measurements using the "Ctrl" and "Shift" keys in association with a
mouse click; on a Mac, use the "Option" and "Shift" keys instead. Even if multiple measurements are selected,
only the one with a check mark in the first column will be used for display. The selected measurements can be
deleted using the menu which appears when you do a right-click on the table.
Note: Only the standard CRI data (CIE 13.3: 1995) is shown when the program is not activated.
Chromaticity graph
All three graphs are include in the TM-30-20 “Full” report while only the Chroma Shift and Hue Shift graphs are
included in the TM-30-20 “Intermediate” report.
Note: The CES are not distributed uniformly in each Hue Angle Bin and the number of samples per bin will vary
with different test sources. The number of samples per bin is automatically provided in the report file whenever
Hue Angle Bin data is selected for export (Hue Angle Bins data fields: Rf,h, Rcs,h, and Rhs,h).
Note: According to current research (Ref. 63-64-67-68), the Color Fidelity (Rf,h1) and Chroma Shift (Rcs,h1) of
the first Hue Bin, is of particular importance when assessing the fidelity of a light source. The first Hue Bin (h1,
identified as “Bin 1” in the screenshots) represents the average of samples in the red part of the spectrum.
The second screenshot was obtained with a display which was assigned the sRGB profile (using the OS
control panel). We see that five reference patches and one test patch are clipped. Please note that while the
clipped colors may not be visibly accurate, all computed values remain accurate.
No patch color is
clipped by the display.
A plain text file can easily be created with a word processor or a spreadsheet application, as shown below.
When saving the file, do not use the often complex native application file formats (for ex.: *.xls); instead, select
a tab-delimited or Comma-Separated-Value (CSV) text format.
Note: You will find separate 5 nm and 10 nm data files for several CIE illuminants in the "Illuminants" folder
located within the CT&A application folder. You can use these files as templates for your own CGATS file.
Note: The TM-30-20 metrics data ranges and color codes are presented in the TM-30-20 tool description
section.
The CRI computing method (CIE 13.3: 1995) does not mention specific goals for a test source. It only mentions
that the CRI was scaled so that a standard warm white fluorescent lamp (of the 1990s!) had a General Colour
Rendering Index (Ra) of about 50. However, the ISO 3664:2009 standard (Ref. 32) recommends a goal of 90+
for Ra and a goal of 80+ for the separate Special Colour Rendering Indices (Ri).
While the authors of the CQS and CRI2012 metrics do not mention specific goals, they scaled their
computation so that the average Qa and Ra,2012 would be 50 for the twelve standard fluorescent lamps (FL1
to FL12; data files are provided in the "Illuminants" folder located within the CT&A application folder), therefore
matching the average Ra for the same lamps. We thus extended the ISO 3664 goals for Ra to Qa and
Ra,2012, and Ri to Qi and Ri,2012.
There is no generally approved goals associated with the TM-30-15 Method. You will find guidelines for Fidelity
Index (Rf) and Gamut Index (Rg) ranges in slides from various seminars (see Ref. 63-64 for examples) but you
should be aware that they have a tendency to change slightly because of ongoing experimentation and specific
design intent. CT&A will highlight Rf, and Rf,skin if they are less than 76; Rg will be highlighted if less than 98
and more than 110.
The authors of the GAI metric (Ref. 48) mention that "a minimum CRI (i.e. Ra) of 80 and a GAI between 80 and
100 will provide good color discrimination and make objects in the scene appear both "vivid" and "natural,"
given sufficient illuminance is provided...". In CT&A, the goals of “GAI and Ra,” a metric proposed by Smet et
al. (Ref. 49), are borrowed from those of the GAI metric.
The authors of the MCRI metrics (Ref. 50) have shown a high correlation between Ra and Rm. They have
scaled Rm so that CIE illuminant FL4 and D65 have values of 50 and 90 respectively but they do not
recommend formal goals. We will nonetheless highlight Rm if its value goes below 80, by analogy with the CRI
Ri goal of ISO 3664; we will also highlight the corresponding Sa value (Rm is a rescale of Sa) when Sa is less
than 0.7268.
Rg 0 200
TM-30-20 (Note 8) (Note 8)
Rf,h1 (Note 7) 0 100
Note: Numerical values for Ri, Qi, Ri,2012, Rf,ces and Rf,h are not shown in the CRI window. However, the bar
graphs with the individual indices show "80" in bold in their vertical scale, corresponding to the "Goals" in the
table above.
Duv is the distance in the CIE1960 (u, v) chromaticity plane between the coordinates of the Test source and
the coordinates of the Planckian radiator. The CRI method (CIE 13.3: 1995) mentions that if the chromaticity
difference is greater than ±0.0054 "...the resulting Colour Rendering Indices may be expected to become less
accurate." This threshold is thus used abundantly in all test procedures designed to verify lamp conformance.
In the CRI tools, any Duv larger than ±0.0054 will be shown in ORANGE. Also, any Duv larger than ±0.05, or
about ten times the acceptable threshold, will be shown as OOR (Out-Of-Range).
Note: A maximum Duv of ±0.006 is specified in ANSI C78.377-2008 (Ref. 53). However, it is important to note
that in ANSI C78.377-2008, for CCTs of 4000 K and higher, the center of the Duv tolerance is not on the
Planckian locus. This is simply because the locus of the D-series illuminants has a slight offset relative to the
Planckian locus.
Examples
Here are some results obtained with standard CIE illuminants. Files for these illuminants can be found in the
"Illuminants" folder (5nm-BW) located within the CT&A application folder.
CRI CQS CRI2012 TM-30-15 TM-30-20
Illuminant CCT Duv Ra R9 Qa Qf Qg Ra,2012 Rf Rg Rf Rg
CIE 15-A 2857 0 100 100 100 100 100 100 100 100 100 100
CIE 15-FL4 2938 -0.0008 51 -111 53 54 79 51 52 84 57 84
CIE 15-D50 5003 0.0032 100 100 100 100 100 100 98 99 100 100
CIE 15-E 5457 -0.0044 95 82 97 95 104 97 94 104 95 104
CIE 15-D65 6505 0.0032 100 100 100 100 100 100 100 100 100 100
GAI MCRI
Illuminant CCT Duv GAI GAI and Ra Rm Sa
CIE 15-A 2857 0 53 77 90 0.763
CIE 15-FL4 2938 -0.0008 45 48 50 0.664
CIE 15-D50 5003 0.0032 88 94 90 0.767
CIE 15-E 5457 -0.0044 100 98 92 0.775
CIE 15-D65 6505 0.0032 98 99 90 0.765
The CRI file options dialog is opened by clicking on the "Save to file..." button of the CRI window.
If you specifically selected some measurements rows in the data table of the CRI tools window before opening
the dialog, you can save the data for only these measurements. You can also save the data for all
rows/measurements. When you have multiple measurements, it can be advantageous to save the data in a
single report file; this report corresponds to the "One file" radio button in the "File options" section of the dialog.
This file can be opened in any word processor; because the data is tab-delimited, you can also open the report
in a spreadsheet application, such as Microsoft Excel. The file type can be either "CGATS" or "Plain text"; you
should select the “CGATS” type if you intend to reopen the file in the CRI tool. If you select the “One file” option
you will be proposed a file name, which you can change if you wish.
The data corresponding to each measurement can also be saved in its own file by selecting the “Separate files”
file option, for which the file type can also be either "CGATS" or "Plain text". Again, if you intend to reopen the
file in the CRI tool, select the “CGATS” option. Since the only CRI tools data which is compatible with the base
"CGATS.17" file format is the measured spectral data, we strongly suggest that you at least select the
"Spectrum" data field. All other (derived or computed) data will also be present in the file but it will be included
in the form of commented lines (i.e. lines which start with the "#" character).
The "Plain text" file type results in a file very similar to the CGATS file but without the header and specific tags
required by the CGATS format and without a special character at the beginning of each commented lines. This
file format is more compact and easily readable.
Hint: If you saved your data using the “Plain text” file type, you can still use this file as input in the CRI tool
(Obviously, the file must at least contain spectral data!). You should edit the file in a simple word processor to
just keep the lines containing the wavelength labels and the spectral data. You will find additional information in
the “CRI input file requirements” section.
If you select the "One file + Separate files" option, you will first be asked to confirm the name and location of
the "One file" report (you can change the report name!) and then be asked to select a folder into which the
separate files will be saved. You can accept the proposed folder, define another folder, or save the files
elsewhere.
• Select the 10 nm bandwidth if you intend to export spectral data to be used with other CT&A tools, the
ISO3664+ and MI tools to be more specific, which only accept 10 nm ambient data.
• Select the “Resample” option (available for the 10 nm bandwidth only) if the input data had a 5 nm
bandwidth. When this option is selected, the 5 nm data is down-sampled to 10 nm data using a
triangular function. Resampling affects ALL spectral values.
• Do not select the “Resample” option if your input data had a 10 nm bandwidth (for i1Pro
measurements for instance). In this case, the output file will have the same spectral values as the input
file, i.e. data for all wavelengths ending with a 5 will simply be discarded.
Warning: If your input data had a 10 nm bandwidth and you resample it when you save, this affects all spectral
values and reopening such a file will show different results!
Note: If your input data had a 10 nm bandwidth, there will be no difference when you reopen exported data
saved in either 5 nm or (10 nm bandwidth without resampling) since the 10 nm data will be re-interpolated.
However, you may still want to save with a 5 nm bandwidth in order to get the interpolated values.
Report types
(as per TM-30-20)
The TM-30-20 report selector dialog is opened by clicking on the "TM-30-20 reports..." button of the CRI
window.
Three report types are offered. They are defined according to the TM-30-20 guidelines (Ref. 57).
• Simple: Contains the CVG graph with the numerical values of Rf, Rg, CCT, and Duv. The “Manufacturer”
and “Model” data fields of the report selector dialog are shown. The nominal image size is about 3.25 x
3.6 in (8,25 x 9,2 cm).
• Intermediate: Contains the CVG graph with its additional data as well as the Chroma Shift and Hue Shift
graphs. The “Manufacturer” and “Model” data fields of the report selector dialog are shown. The nominal
image size is about 6.9 x 3.6 in (17,5 x 9,2 cm).
• Full: Contains the CVG graph with its additional data as well as the spectrum graph, the Chroma Shift
graph, the Hue Shift graph, the Local Color Fidelity (Hue Bin) graph, and a graph with the fidelity of each
CES. In addition to the “Manufacturer” and “Model” data fields, the Full report includes the content of the
“Source”, “Date” and “Notes” data fields of the report selector dialog. The report also presents Ra and R9
of CIE 13.3, and the xy and u’v’ coordinates of the Test source. The nominal image size is about 7 x 9 in
(17,8 x 22,9 cm).
All report types can optionally show the Color Rendition performance as defined in Table E2 of TM-30-20
Annex E. The performance is expressed in the form “Px | Vx | Fx” where “P” corresponds to the “Preference”
design intent, “V” corresponds to the “Vividness” design intent, and “F” to the “Fidelity” design intent. “x” is a
placeholder for a number (1, 2, or 3) which indicates the priority level, with “1” being the highest; if level 3 is not
met, a hyphen (-) is written.
Examples of the three report types are shown on the next pages.
The press-proof, either "real" or "soft" (i.e. simulated on a calibrated monitor or printer), should be
representative of the final product. Apart from the printed image, which is a "qualitative" proof, many individual
color patches of the primary inks are added on the printed sheet outside of the main subject area. These
patches are used for "quantitative" assessment of the reproduction quality.
Many different patch designs and patterns have been devised (Plate Control Targets or Color Bars) and their
selection is a matter of preferences, expected print quality, and project cost. For more information, please
consult the Web site and the publications of the Printing Industries of America (PIA) association (PIA joined
forces with the Graphic Arts Technical Foundation (GATF) in 1999):
https://www.printing.org/
PIA Quality and Process Controls Catalog and Guide .
The Density tools window is opened either by clicking on the corresponding icon on the toolbar window, or by
selecting the "Tools/Density" menu.
Important: To use these tools, you need to have an i1Pro series spectrophotometer connected to the
computer on which CT&A is running. The instrument must also be properly recognized by the program; this is
confirmed by a small green light beside the instrument selection menu in the toolbar window, and by the
"Calibrate" and data entry buttons of the Density window being enabled (some data entry buttons and controls
will remain disabled and some data fields will not be available if the program is not activated). If you plug an
instrument in your computer after the program start, you can attempt to connect the instrument by selecting
"Try to connect again..." in the Instrument menu. A status of the selected instrument can always be obtained by
clicking on the "Info" button located in the toolbar window.
Note: In Windows, if the i1Pro/i1Pro 2 or i1Pro 3 USB drivers are not installed, please consult the
"CT&A_Readme.txt" file located within the main CT&A application folder. This file can be opened directly with
the "Start menu/BabelColor/CT&A Readme" shortcut.
Instrument button support: When the Density tools window is selected, i.e. brought to the front, and
assuming that a compatible instrument is selected and recognized, a large blue indicator appears next to a
data entry button ("Get D", "Get Ds", "Get OP", etc.). This indicator identifies the data that will be measured if
you press the instrument button; of course, you can also do a mouse click on any data entry button. If the tool
requires or supports more than one data entry field, the indicator automatically changes location after making a
measurement. You can click (left-click) on the indicator to move it to the previous measurement if required, or
do a right-click to lock it on a given measurement. You can also do a left-click on a locked indicator; the new
position will be locked.
Click on a link in the Table of Contents below for information on the tools' interface and for specific tools
descriptions and equations.
The section describes how to set up the interface and make measurements with the Density tools. For specific
tools descriptions and equations, please select the tool in this Table of Contents.
Note: A clipping indicator will appear in the bottom left corner of a color patch when the color of the sample it
represents is outside of the RGB space gamut of the monitor.
SETUP
• It is assumed that your instrument is properly connected and detected, as discussed in the Density tools
introduction, and that the "Calibrate" and "Get x" buttons are enabled. Please note that some data entry
buttons and controls will remain disabled and some data fields will not be available (shown as "N.A.") if the
program is not activated.
• Select a "Measurement Conditions". If you are using an i1Pro 2 with the "i1Pro / i1Pro 2 (XRGA)" driver or
an i1Pro 3, you can select the "Measurement Conditions": M0 (Ill-A), M1 (D50), M2 (UV-cut). If you are using
an i1Pro 3 Plus, the M3 (Pol.) Measurement Conditions will also be available. If you are using an i1Pro, or an
i1Pro 2 with the "i1Pro / i1Pro 2 (non-XRGA)" driver, the program will select the default measurement
conditions supported by the instrument.
Note: If multiple Measurement Conditions are supported by your instrument, the M0/M1/M2 measurements
will be taken when any one of these conditions is selected. You can thus change this setting at any time.
Note: Because M3 requires an accessory polarizer, and because M0/M1/M2 measurements are performed
separately, the M3 density measurements are processed independently from M0/M1/M2 measurements, with
their own “Measurement control” for instance, and are presented in a distinct report section.
• Select a "Measurement type": Reflection density, Dot Area, Print Contrast, Hue error - Grayness - Saturation.
Data is kept independently for each measurement type.
• If required, select a "Formula" (for Dot Area and Apparent Trap). If required, set the "n Factor" for the Yule-
Nielson formula of the Dot Area measurement. A n factor of 1,70 is shown by default when the Yule-Nielson
formula is first selected; it can then be changed by the user by typing a new value in the field where it
appears. Please consult the Dot Area and Apparent Trap sections for more information on these formulas.
• If not already done, calibrate the instrument by clicking on the "Calibrate" button and following the on-screen
instructions.
WHITE BASE
A "Paper" "White base" is automatically selected and "Absolute" is disabled if "Dot / Tone (Dot Area)" or
"Apparent Trap" is selected. Both options are enabled for "Reflection density", "Print Contrast", and "Hue error -
Grayness - Saturation".
If "Paper" is selected for the "White base", it is strongly suggested to measure the paper first by clicking on the
"Get" button located in the "White base" group.
Important: The same paper data is used for all density measurements types. When "Paper" and "Absolute" are
both available, selecting one or the other will update ALL the measurements sets of ALL measurement types.
FILTER
An "Auto" "Filter" is automatically selected and "Man" (i.e. Manual) is disabled if "Apparent Trap" or "Hue error -
Grayness - Saturation" is selected. Both options are enabled for "Reflection density", "Dot / Tone (Dot Area)",
and "Print Contrast".
If available, selecting the "Man" radio button will enable the individual CMYK filters. Selecting any of these
filters will instruct the program to show only the data — in the data table — corresponding to this filter.
MEASUREMENT CONTROL
Up to five sets of measurements can be done for each density tool. Select the measurement set by clicking on
a radio button in the "Measurement control" group (they are labeled #1, #2, etc.). You should see the
measurement number in the upper-left cell of the data table.
To make a measurement, either click on the "Get x" button under the square patches, where "x" represents the
measured variable (D, Ds, OP, etc.) which changes according to the selected measurement type, or press the
instrument button. A large blue indicator is located beside the "Get x" button that will be selected if you press
the instrument button:
To automatically change/increment the measurement number in the "Measurement control" group, simply
check the "Auto-select" box. Once all inputs for a measurement set are done (i.e. all inputs are green), the
system selects the next measurement set. For example, if "D solid" and "D tint" for "Print Contrast" are
measured for measurement set #3, then #4 is then selected.
The "Show avg." box is enabled when there are at least two complete measurements. To display the average,
check the "Show avg." box. The values will appear in the data table with an Italic font and the word "Avg." will
be displayed in the upper-left cell.
You can clear the selected measurement set or all sets by clicking on either the "Clear meas." or "Clear all"
buttons. The "Clear all" button erases only the data of the current measurement type.
Hint: You can easily measure the same parameter for all measurements by locking the parameter. For
example, in the "Dot / Tone (Dot Area)" tool, first check the "Auto-select" box and then lock the blue indicator
on the "Get Dt" button; each press of the instrument button will then get Dt and assign it to a different
measurement. This is shown in the screenshot below:
Hint: You can grab the average as the reference by first selecting the "Show avg." box and then clicking the
"Grab Ref." button.
Click on "Save to file..." to save a report of the selected "Measurement type". You will be prompted to save only
the current measurement type or all the data acquired in all Density tools. The report has tab-delimited data
that can be directly imported in a spreadsheet program, and opened in many text editing applications (it is
suggested to use a monospace font, such as Courier, in order to facilitate formatting).
You can copy numerical data by making a mouse right-click (or ctrl + click on a one-button Mac mouse) on
any table cell or data field (such as the Apparent Trap and Hue-Grayness-Saturation results). Shown below
is the contextual menu which appears with a right-click on the fourth column of the first row (Cyan, D tint); you
can copy either the cell content, the complete row or column of this cell, or the entire table. When copied, the
data is transferred into the clipboard, separated by Tabs. You can then easily paste the values in a
spreadsheet or document table, where they will be distributed in individual cells.
Note 1: Copy ROW data: When copying a row, the filter label (C, M, Y or K) is also copied.
Note 2: Copy COLUMN data: When copying a column, the header (D paper, etc.) is also copied. The data will
be pasted in a single line (i.e. ROW).
Note 3: Copy ALL data: When copying the entire table, the headers are also copied. The data will be pasted
using the same number of rows and columns as in the copied table.
which is equal to zero (0,0 D) for 100% reflectance, 1,0 D for 10% reflectance, 2,0 D for 1% reflectance, 3,0 D
for 0,1% reflectance, etc. The lower the reflection, the higher is the density. A similar equation can be defined
for transmission, with "T" replacing "R".
Taking the logarithm effectively compresses the tonal difference and assigns the same significance, a 1,0 D
difference, to a change between 1% and 10% compared to a change between 10% and 100%. This is
representative of the non-linear sensitivity of the human eye, and of the similar characteristics of the
photographic films used to make the printing plates.
A density is not a spectral characteristic per se, since it is a measure of reflection — or transmission — only. By
associating the density to a color filter, we are able to characterize the densities of specific color ranges, the
ones corresponding to the various inks of the color printing process for instance.
When an image is photographically reproduced, black and white separation films are exposed through Red,
Green, and Blue filters. These films are negatives, where the brightest areas are recorded as black and the
dimmest areas as white. The white areas of the red filtered image correspond to the complementary color of
red, which is cyan. Similarly, the complementary color of the green filter is magenta and the complementary
color of the blue filter is yellow.
The separation films are then used to expose the printing plates. Ink will be
deposited proportionally to the clear areas of the film. Accordingly, inks of
the complementary colors of the filters, Cyan, Magenta and Yellow (CMY),
have to be used to properly reproduce the colors. Although the separation
plates can be generated directly by software, the final reproduction steps
are the same, and the same filters are assumed when measuring a
hardcopy.
Different filter curves are used. Called "Status X", with "X" a letter such as "A", "E", "I" or "T", they are selected
according to the reproduction process, print or film, and to agreed standards.
As single density measurement always combines the effect of the ink AND the paper on which it is printed; the
measurement is thus an absolute value (Dabs). If you first measure the density of the paper (Dpaper), also
called "White base" or substrate, you can subtract this value from the absolute measurement and obtain a
relative density (Drel) representative of the ink deposition only:
The densities corresponding to the various filters can be combined to provide additional information on the
printing process, such as Dot Area, Apparent Trap, Print Contrast, and Hue error, Grayness, and Saturation.
These are defined in the following sections. Many of the equations used for density characterization use the
relative values instead of the absolute ones.
In CT&A, three formulas can be used to obtain Dot Area values: Murray-Davies, Yule-Nielson, and SCTV
(Spot Color Tone Value). The first two are used to evaluate tone values obtained with the four-color CMYK
printing process; the third formula, SCTV, is a new formula designed specifically to measure the tone of spot
colors (Ref. 59).
Yule-Nielson:
where Dsolid is the solid density, Dtint the tint density, and Dpaper the paper density. The only difference
between the two equations is the presence of the "n Factor" in the Yule/Nielson formula, an empirically
determined value based on the printing substrate. By setting the n factor to one, the Yule-Nielson equation
becomes identical to the Murray-Davies equation.
The n factor is typically set to values between 0,5 and 9,9. Approximate values for various materials are:
• 1,60 to 1,70 for coated paper;
• 2,70 for uncoated paper;
• 2,50 for newsprint.
In this tool, a default value of 1,70 appears for the n factor when the Yule-Nielson formula is first selected; this
value can then be changed by the user.
The Dot Area on the separation film can also be measured; this measurement requires a transmission
densitometer (Note: this measure cannot be done with an i1Pro series spectrophotometer). By comparing the
dot areas of both the film and the print, one can obtain the Dot Gain, which is the increase in dot size between
the film and print. One can also assume that the Dot Area of the film is equal to the percentage tint specified in
the original data file (in Photoshop for example), and measure the Dot Gain as the difference between the Dot
Area of the print and the file value.
Dot Area and Dot Gain are typically measured for 25% (highlights), 50% (mid-tones), and 75% (shadows) tints.
Excessive dot gain in the shadows will result in "plugging" with a loss of contrast and detail. Excessive dot gain
in highlights will make light, "washed-out", colors difficult to reproduce. As well, gray balance will be affected by
inconsistent dot gains across the four printed colors.
In the table above, the Dot Gain is determined relative to a 50% tint, as specified in the original data file. For
example, for Magenta uncoated: Dot Gain = (Dot Area of print) - 50% = 79% - 50% = 29% .
SCTV FORMULA
The Tone Value (TV) is derived from the XYZ values of the spot ink solid, the substrate, and the spot ink tone.
It is NOT derived from densities obtained from predefined Red, Green, and Blue filters. The Tone Value is
normalized between substrate (TV=0%) and spot ink solid (TV=100%).
Below is a screenshot of a typical measurement. In addition to the Tone Value, you also get the paper and solid
densities, and the wavelength corresponding to the lowest reflectance, λ (Rmin). Here we get a TV of 45,4%,
with a Dpaper of 0,14Y and a Dsolid of 1.29Y (both densities Status T), and a minimum reflectance at 470 nm.
Hint: For a given set of measurements, you can switch between the three formulas without having to re-
measure the patches.
The two following formulas can be used to obtain Apparent Trap values:
Preucil (GATF), defined as the ratio of the difference between the density of the over-print and the density
of the first ink printed (first-down ink) to the density of the second ink printed (second-down ink):
Brunner, which evaluates trapping as the apparent dot area of the second color as if it was printed as a tint
instead of solid:
where Dop is the density of the over-print, D1 is the density of the first-down ink, D2 is the density of the
second-down ink, and Dpaper is the density of the paper.
The computation is based on the filter corresponding to the dominant hue, usually from D2, which is the filter
with the highest density. For example, if yellow is printed over cyan, the trap value will be computed using the
"Y" filter values of all the samples (paper, 1st ink and 2nd ink). The trap value is reported in the following
format:
trap% Y/C green
where Yellow is printed over Cyan and green is the color of the over-print.
Typical Apparent Trap values — these are NOT standards — as measured on three coated papers and one
uncoated paper, and using a black backing, are:
where Dsolid is the solid density and Dtint the tint density. The above formula shows only absolute inputs; if
desired, the print contrast can be determined with relative density values, where the contribution of the paper
density, Dpaper, is removed from both Dsolid and Dtint.
Typical Print Contrast values — these are NOT standards — that can apply for coated paper and newspaper:
The measurements are performed on solid patches (100% tint) of either cyan, magenta or yellow. The
individual CMY values are first ranked as Dlow, Dmid, and Dhigh, where Dlow is the lowest density of the CMY
values, Dhigh is the highest density, and Dmid is the middle density.
Hue error is a misnomer; it is not an error per se, but the variation from an ideal cyan, magenta or yellow:
The above example shows that the measured patch is Cyan (the filter with Dhigh) with a tendency towards
Yellow (the Dmid filter). In the example, the hue error is the ratio of the yellow ink density over the cyan ink
density once gray is removed by subtracting Dlow from each of them; the yellow-with-gray-removed density is
22,5% of the cyan-with-gray-removed density.
which you can visualize by the fact that there is at least a value of Dlow in each ink, creating a gray
background.
Saturation is the difference between the highest density filter value and the lowest one:
which can be looked at as Dhigh without the gray. Saturation is expressed in density units, not in percentage.
The above formulas show only absolute inputs; if desired, they can be determined with relative density values,
where the contribution of the paper density, Dpaper, is removed from the absolute values (Dlow, Dmid, and
Dhigh).
Typical Hue error, Grayness, and Saturation values — these are NOT standards — as measured on three
coated papers and one uncoated paper, and using a black backing, are:
INTRODUCTION
The FluoCheck tools are made possible by the capabilities of X-Rite's i1Pro 2 and i1Pro 3 spectrophotometers
which supports the M0, M1, and M2 Measurement Conditions as defined in ISO 13655 (Ref. 42). The
FluoCheck tools were devised by BabelColor to rapidly evaluate if a color sample is susceptible to fluorescence
and if two samples that match without fluorescence still match when fluorescence is taken under consideration.
The FluoCheck window is opened either by clicking on the corresponding icon on the toolbar window, or by
selecting the "Tools/FluoCheck" menu.
Important: An i1Pro 2 or i1Pro 3 which supports the M0 (Ill-A), M1 (D50), and M2 (UV-cut) measurement
conditions is required to use these tools (an i1Pro cannot be used!). Also, for the i1Pro 2, you must select the
"i1Pro / i1Pro 2 (XRGA)" driver in the toolbar window and the instrument must be properly recognized by the
program. Instrument recognition is confirmed by a small green light beside the instrument selection menu in the
toolbar window, and by the "Calibrate", "Get Ref.", and "Get Sample" buttons being enabled in the FluoCheck
window (some controls will remain disabled and some data fields will not be available (shown as "N.A.") if the
program is not activated). If you plug an instrument in your computer after the program start, you can attempt to
Note: In Windows, if the i1Pro 2 USB drivers are not installed, please consult the "CT&A_Readme.txt" file
located within the main CT&A application folder. This file can be opened directly with the "Start
menu/BabelColor/CT&A Readme" shortcut.
Instrument button support: When the FluoCheck tools window is selected, i.e. brought to the front, and
assuming that a compatible instrument is recognized, a large blue indicator appears next to the "Get Ref." or
"Get Sample" button. This indicator identifies the data that will be measured if you press the instrument button;
of course, you can also do a mouse click on any data entry button. The indicator automatically changes
location after making a measurement. You can click (left-click) on the indicator to move it to the previous
measurement if required, or do a right-click to lock it on a given measurement. You can also do a left-click
on a locked indicator; the new position will be locked.
The remainder of this section describes how to set up the interface and make measurements. For additional
information on the FluoCheck FI and FMI indices and for the FMI equation, click here.
SETUP
• It is assumed that your instrument is properly connected and detected, as discussed in the introduction just
above.
• Select a "FI formula"; data will be updated if it is changed after a measurement is done.
The available color difference formulas are:
• CIELAB
• CIE94 (i.e. the common formula, CIE94 (1:1))
• CIE94 tex. (i.e. CIE94 for textile, CIE94 (2:1))
• CIE94 (2:2)
• CMC (2:1)
• CMC (1:1)
• CIEDE2000
Note: CIE94 (2:2), where kL=2 and kC=2, puts more weight on the hue (with kH=1) than on the lightness and
chroma. This formula is recommended by Berns (Ref. 25, p. 129) to determine the CII and is also a very
good choice for the FI.
Note: The FMI values are always computed using CIELAB color differences.
• If not already done, calibrate the instrument by clicking on the "Calibrate" button and following the on-screen
instructions.
This indicator automatically changes location when an input is done at one position. Do a left-click on an
indicator to change its position or a right-click to lock it (a locked indicator has a red border: ). You can also
do a left-click on a locked indicator; the new position will be locked.
To erase a measurement, first press the Alt key, in Windows, or the Option key on a Mac. Whenever the
mouse cursor is within the tool window, the "Get Ref." and "Get Sample" buttons will change their caption to
"Clear" (if there is a measurement). To clear the sample, click the button with the mouse while keeping the Alt
or Option key pressed:
Here is a first example where only the Reference is measured; the measured patch is a skin color from a
glossy magazine (you should enlarge the screenshot and wait a few seconds for your eyes to adapt in order to
better differentiate the color differences):
The Fluorescence Index (FI) for the patch measured under M1 relative to M2 is 4,18, i.e. this is the color
difference between M1 and M2 as computed with the selected FI formula, in this case CIELAB. If we visually
compare the patches, shown enlarged in the next screenshot, we see that the M2 color is more yellow and M1
is more neutral (i.e. bluer).
The effect is similar, but less intense, when we compare M2 and M0 computed for Illuminant A, with a FI of
2,68. The higher FI for M1-vs-M2 is expected since a D50 light source contains more UV than an Illuminant A
light source.
You will notice that the zone where the M2 color is represented can be distinctly separated in two; there is a
black mark "–" outside of the patch layout which identifies where the two colors join:
There are two reasons for this. Firstly, because M2 is UV-cut, there is no predetermined illuminant associated
to this measurement condition. Secondly, in order to better compare M2 with M0 and M2 with M1, we compute
M2 using the illuminant associated respectively to M0 (Ill-A) and M1 (D50). The two M2 colors are thus a
representation of the patch as seen under two illuminants; the color difference is, in effect, color inconstancy, a
phenomenon which can be better quantified using the Metamerism Tool (MI) tools. It is important to note that
not all measured colors will display this inconstancy, and that this effect is distinct from fluorescence.
Note: The MI tool is best used to analyse non-fluorescent colors, or colors as they appear under non-
fluorescent inducing sources, i.e. M2. If you see color inconstancy in the FluoCheck tool, this is merely a
suggestion that further analysis may be required relatively to color inconstancy.
Note: Because the FI and FMI are color differences, the same criteria and thresholds used in evaluating color
differences should apply when assessing these numbers.
In this third example we kept the "Ref." of the previous two examples and measured another "Sample".
The FIs of the sample are not zero, indicating fluorescence, but they are not as high as the FIs of the reference.
The FMI computed relative to M0, FMI(M0), is 1,00 and the FMI computed relative to M1, FMI(M1), is 1,50.
Since the FMI values are lower than the FI, especially when the FI is computed with CIEDE2000 and the FMI
with CIELAB, these results indicate that the two samples will somewhat change in the same fashion when
subject to a fluorescent source. The lower FMI(M0) value (=1,0) also indicates that the color fluctuations for
Illuminant A may well go unnoticed; this is not quite the case for D50, as we see below:
In practice, this measurement could mean that the change between these two colors will be more noticeable
under daylight (D50) than under tungsten illumination (Illuminant A) as the paper's Fluorescent Whitening
Agents (FWA) degrade and there is less fluorescence. This degradation could also happen if looking at the
colors in daylight but behind a window which cuts most of the UV content.
Note: A clipping indicator appears in the bottom left corner of a color patch when the color of the sample it
represents is outside of the RGB space gamut of the monitor.
Click on "Save to file..." to save a Fluorescence report. The report has tab-delimited data that can be directly
imported in a spreadsheet program, and opened in many text editing applications (it is suggested to use a
monospace font, such as Courier, in order to facilitate formatting).
You can copy numerical data by making a mouse right-click (or ctrl + click on a one-button Mac mouse) on
any data field (L*a*b*, FI, FMI)). Shown below is the contextual menus which appear with a right-click in the
reference M0 L*a*b* data field and on the bottom-right FI. When copied, the data is transferred into the
clipboard. Please note that L*a*b* values are separated by Tabs; you can then easily paste the values in a
spreadsheet or document table, where they will be distributed in individual cells.
Note: ISO 13655 also describes the M3 Measurement Conditions which covers instruments fitted with a
polarizing filter; these conditions are not supported by the i1Pro 2 and the standard aperture i1Pro 3. M3 is
supported with the large aperture i1Pro 3 Plus which does have an accessory polarizer head. Please note that
M3 measurements are not required in the FluoCheck tools.
Important: Because the i1Pro 2 uses a separate UV source tuned for the optical brighteners typically found in
paper, this UV source may not create fluorescence in the printing inks. For instance, some fluorescent inks are
also excited by violet, blue, and even green light, with a re-emission in the yellow, orange or red portions of the
spectrum. In such a case, a measurement made with an i1Pro 2, which is based on a M0 lamp, will show less
ink fluorescence than an instrument base on a Xenon lamp which has relatively more violet and blue content.
As for the i1Pro 3 and i1Pro 3 Plus, which use a LED-only based light source, they react the same way as an
i1Pro 2 when measuring a sample printed with fluorescent ink and are likely similarly optimized to measure the
effect of UV light on the substrate. Thus, it is not recommended to use the FluoCheck tool to analyze ink
fluorescence.
The Fluorescence Index (FI) and the Fluorescence Metamerism Index (FMI) described on the next page
were devised by BabelColor. The FI and FMI are not described in a standard but they are based on the
standard-defined M0, M1, and M2 measurement conditions.
Please note that the FI could as well be measured using the Graph tools, by first making a reflectance
measurement in M2, on the left side of the Graph tool, and then a measurement in M0 or M1 on the right side.
The color difference obtained in the Graph tool would be identical to the FI of the FluoCheck tools. The
advantage of using the FluoCheck tools is that you obtain the color difference, i.e. the FI, simultaneously for
M2-vs-M0 and M2-vs-M1 while being able to visualize the patches in all three measurement conditions.
In addition, the FluoCheck tools enable you to compare a "Ref." against a "Sample", or two samples.
and the second one identified as FMI(M1), corresponding to the bottom portion:
where M0, M1, and M2 refer to the measurement conditions, and where
are computed with the data of the measurement condition referred to in the FMI equation. As we can see by
inspecting the equations, the FMI is based on CIELAB.
INTRODUCTION
The Graph tools window is opened either by clicking on the corresponding icon on the toolbar window, or by
selecting the "Tools/Graph" menu.
Important: To use these tools, you need to have an i1Pro series spectrophotometer connected to the
computer on which CT&A is running. The instrument must also be properly recognized by the program; this is
confirmed by a small green light beside the instrument selection menu in the toolbar window, and by the
"Calibrate" and "Get Sample" buttons of the Graph window being enabled (some controls will remain disabled if
the program is not activated). If you plug an instrument in your computer after the program start, you can
attempt to connect the instrument by selecting "Try to connect again..." in the Instrument menu. A status of the
selected instrument can always be obtained by clicking on the "Info" button located in the toolbar window.
Instrument button support: When the Graph tools window is selected, i.e. brought to the front, and assuming
that a compatible instrument is selected and recognized, a large blue indicator appears next to a "Get
Sample" button. This indicator identifies the data that will be measured if you press the instrument button; of
course, you can also do a mouse click on any data entry button. The indicator automatically changes location
after making a measurement. You can click (left-click) on the indicator to move it to the previous measurement
if required, or do a right-click to lock it on a given measurement. You can also do a left-click on a locked
indicator; the new position will be locked.
SETUP
• It is assumed that your instrument is properly connected and detected, as discussed in the introduction just
above.
For reflectance measurements, and if you are using an i1Pro 2 with the "i1Pro / i1Pro 2 (XRGA)" driver or
an i1Pro 3, you can select the "Measurement Conditions" M0 (Ill-A), M1 (D50), or M2 (UV-cut), as defined in
ISO 13655 (Ref. 42). If you are using an i1Pro 3 Plus, the M3 (Pol.) Measurement Conditions will also be
available. A description of the M0/M1/M2 measurement conditions can also be found in the FluoCheck tools.
If you are using an i1Pro, or an i1Pro 2 with the "i1Pro / i1Pro 2 (non-XRGA)" driver, the program will select
the default measurement conditions supported by the instrument.
The photometric and radiometric units for emission, ambient and flash modes are:
photometric photometric radiometric units
Mode
units name units (for spectrums)
2 2
Emission luminance cd / m mW /nm /m /sr
2
Ambient illuminance lux mW /nm /m
integrated 2
Flash lux-sec mJ /nm /m
illuminance
Important: The "Ambient" and "Flash" modes are not available for older i1Pros which were sold without the
diffuser cap accessory. These instruments can be factory refurbished; please contact X-Rite for additional
information.
• Select the "Illuminant" and "Observer" that will be used to compute the tristimulus data.
The available illuminants are:
• A (Tungsten or Incandescent, 2856 K)
• B (Direct sunlight at noon, 4874 K*, obsolete)
• C (North sky daylight, 6774 K*)
• D50 (Daylight, used for color rendering, 5000 K*)
The colorimetric coordinates will be updated if these settings are changed after a measurement is done.
Important: The "Illuminant" and "Observer" settings have no effect on the spectrums' shapes and the
spectrums' data values.
• Select the data type, or color space, that will be computed with the acquired data. L*a*b* is always computed
in addition to the user-selected color space. Data will be updated if the color space is changed after a
measurement is done.
The available color spaces are:
• L*C*h (ab) (i.e. L*C*h from L*a*b*)
• L*u*v*
• L*C*h (uv) (i.e. L*C*h from L*u*v*)
• XYZ
• xyY (recommended for ambient and flash measurements)
• Select the color difference formula that will be used with the acquired L*a*b* data; the difference will be
updated if the formula is changed after a measurement is done.
The available color difference formulas are:
• CIELAB
• CIE94 (i.e. the common formula, CIE94 (1:1))
• CIE94 tex. (i.e. CIE94 for textile, CIE94 (2:1))
• CMC (2:1)
• CMC (1:1)
• CIEDE2000
• If not already done, calibrate the selected measurement mode by clicking on the "Calibrate" button and
following the on-screen instructions.
Note: In CT&A, emission calibration requires the measurement of a white patch, preferably located on the
display or emissive surface on which subsequent measurements will be performed; this procedure sets the
White Point (WP). The WP characteristics (display location, luminance and CCT) are shown in the toolbar
window, as seen in green text in the next screenshot.
Important: The L* and Y values of the EMISSION color coordinates are computed relative to the display
White Point, as discussed above. Accordingly, the display white is assigned L* and Y values of 100. Nothing
prevents you of using another monitor or another emissive surface to set this reference value, and all
subsequent emission measurements will then be referenced to this new white point. However, be aware that
the L*a*b* and "Y" values, as well as the appearance of the patches of all previous emission measurements will
NOT be updated. On the positive side, in emission measurements, the only absolute parameters are the
chromaticity coordinates (xy), and these parameters should not be affected by an emission calibration change.
Here is a table which describes the difference between the RGB vs RGB tool and the Graph tools relative to
EMISSION and AMBIENT measurements:
Note: Only x and y are absolute coordinates. While the absolute luminance and illuminance are provided in
cd/m2 or lux, Y is normalized when shown in the xyY and XYZ data fields.
Important: Many displays (usually CRTs, but sometimes LCDs) will change their brightness depending on
what is displayed on the rest of the screen. This is why a single small white square over a black background is
used for emission calibration. As a consequence, in some displays, you may find that, thereafter, white is
measured with an L* value of less than 100 in many situations. Also, most displays are not uniform, with the
center portion "usually" at a higher luminance than the rest of the display; however, it is also possible that the
display center is not the area with the highest luminance.
To make a measurement, click on one of the "Get Sample" buttons or press the instrument button. A large
blue indicator is located beside the input that will be selected if you press the instrument button:
This indicator automatically changes location when an input is done at one position. Do a left-click on an
indicator to change its position or a right-click to lock it (a locked indicator has a red border: ). You can
also do a left-click on a locked indicator; the new position will be locked.
To erase a measurement, first press the Alt key, in Windows, or the Option key on a Mac. Whenever the
mouse cursor is within the tool window, the "Get Sample" buttons will change their caption to "Clear" (if
there is a measurement). To clear the sample, click the button with the mouse while keeping the Alt or
Option key pressed:
• Flash mode: Before making any measurement, you should calibrate the instrument by clicking on the
"Calibrate" button and following the instructions. Please note that calibrating for the flash mode will also do
the calibration for the ambient mode. If you try to do a measurement and the calibrations was not done, or is
outdated, you will automatically be directed through the calibration sequence before doing the measurement.
Because of the above sequence, where it is required to press and hold the instrument button, it is not
possible to start a flash measurement from the program window; accordingly, the "Get Sample" buttons are
hidden. The sample to which the next instrument key press will be assigned is identified by the "Input: i1
key" text and by the blue indicator. As discussed above in this section, the indicator automatically changes
location when an input is done at one position, and its position can be changed or locked using the mouse.
You will notice that, by default, the coordinates for emission, ambient and flash measurements are absolute
values ("Abs."). If desired, you can normalize a graph by selecting the "Nor." radio button in the scale
adjustment groups, as shown below on the left; this action will set the maximum of a spectrum to one (1). The
normalization is for viewing purposes only; internally, the data is still saved in absolute coordinates. You can
also zoom-in and zoom-out a graph by clicking the small arrows in the scale adjustment zones, as shown
below on the right.
To change the graph grids appearance, use your mouse right-click (or ctrl + click on a one-button Mac mouse)
and select an option.
By first hiding all grids then selecting to show a separate line for R=1, you can easily view the reflectance of a
fluorescent paper, as shown in the example below, which is compared with a very neutral but grayish paper. At
440 nm, corresponding to the mouse cursor position, the reflectance of this fluorescent paper is 114% (R=1,14)
compared to 86% for the more neutral paper.
SPECTRUM S2
OPERATIONS Emission Ambient Flash Reflectance
Here is what the middle section of the dialog looks like when two reflectance samples are measured:
• Multiply: This is always done with a reflectance spectrum and either an ambient, flash, or emission
spectrum.
You should select "b-", and check the "W adapt." box located to the right of the Math spectrum, when the
emission or ambient spectrum is close to "white", and "a-" (which corresponds to "W adapt." unchecked) in all
other cases (the "b-" option has no sense for a deeply colored light source).
In the screenshot shown at the start of this section, Sample #1 (S1) is a reflectance measurement of a purple
color patch done with the M2 measurement condition whereas Sample #2 (S2) is an ambient measurement
of a typical halogen desk lamp, with a color temperature and a spectrum close to Illuminant A. The
illuminance is 958 lux and the color temperature is 2850 K; please note that this light source is represented
as a light-yellow patch because the selected reference illuminant is D50 and a 2850 K source looks yellower
when compared to a D50 source (even though a 2850 K source is perceived as "white" when our eyes are
adapted to it, after a few seconds).
If you assume that you are "illuminant adapted" to the source and that the sample is basically lit by white light
(case "b-" above), the resulting perceived color is closer to the one of the original sample. As mentioned, this
can be simulated by clicking the "W adapt" box (not shown in the screenshot).
• Add: Adding two reflectance spectrums will simulate an additive RGB process. However, adding reflectance
and emission spectrums may result in L* and Y values superior to 100. When adding ambient spectrums, the
resulting coordinates will always be normalized to L* and Y values of 100.
• Average: The resulting spectrum has the same shape as the one obtained with the "Add" function, but its
brightness is half the one of the "Add" function.
• Subtract: You can select to subtract either spectrum from the other. Negative values, while displayed, are
clipped to zero — for all measurements types — when computing tristimulus data, for color patch
representation, and for data export.
• S1 vs Illum. or S2 vs Illum.: These functions appear whenever you measure a sample in "Ambient" or
"Flash" mode. In the screenshot below, "S2: Ambient" is the measurement, in ambient mode, of daylight
measured through a window (in winter, around noon, with a heavy cloud cover and snow on the ground);
accordingly, the "S2 vs Illum." radio button is enabled. When this button is selected, the spectrum of the
sample is reproduced in the bottom graph, in black, along with a spectrum, in green, of an "ideal" reference
illuminant corresponding to a rounded value of the measured sample's CCT. The reference illuminant type, a
blackbody or a D-series Illuminant, is based on the CCT value; in addition, ten commonly used illuminants
can be manually selected (there is more information on CCT selection further down):
You will notice that the color of the patch representing the measured daylight has a slight blue tint. This is
because its CCT, D59, is higher than the selected reference illuminant, D50, and thus corresponds to a bluer
chromaticity. Here is what happens if we select D60 and D93 as the reference illuminant:
When we select D60, the patch color is almost pure white; this is expected since D60 is very close to the
source CTT (=D59). When we select D93, the patch color now has a definite yellow tint; this is because the
chromaticity of D93 is bluer than the one for D59, and the measured source does appear relatively yellower
in comparison. You will also notice that, in all three screenshots, the chromaticity coordinates of the
measured light (0,3239 / 0,3398 / 100,0) remains unchanged but the L*a*b* value, computed using the
reference illuminant, does change (with the most neutral value obtained for a D60 reference illuminant).
Important: When selecting "S1 vs Illum." or "S2 vs Illum.", the reference illuminant is ALWAYS generated for
the SAME ILLUMINANCE/LUMINANCE as the selected sample (868 lux in this example) so that you can
better compare them with an absolute ("Abs.") scale.
You can also manually select other illuminants with the "Ref. Illum." Listbox shown on the
right. The selection comprises a 2856 K blackbody, which is Illuminant A, a 3200 K
blackbody generally used for TV Studio lighting, as well as four blackbodies
corresponding to many SoLux lamps, and four commonly used Daylight series (D-series)
illuminants. Selecting "Auto" will compute the ideal spectrum based on the measured
CCT, in kelvin. A D-series illuminant will be selected for color temperatures over 4000 K,
and a blackbody will be selected for color temperatures below 4000 K. The temperature
is assigned in steps of 100 K for D-series illuminants and 50 K for blackbodies. The
spectral data of the reference illuminant is scaled to match the measured illuminance; it
can be exported to a file (see below).
Click on "Save to file..." to save the spectrums of the measured samples and of the mathematical operations, if
selected. You can use the text entry fields to assign a custom name to each sample. The report has tab-
delimited data that can be directly imported in a spreadsheet program as well as many text editing applications
(it is suggested to use a monospace font, such as Courier, in order to facilitate formatting). The file is also
CGATS compliant and can be opened by many color-management software, including BabelColor's PatchTool
and X-Rite/GretagMacbeth MeasureTool.
Important: Although the ambient, emission, and flash spectrums are saved in a CGATS compatible file format,
these spectrums are not normalized to 1 or 100, like a reflectance spectrum. The appearance of the patch and
the computed color coordinates will thus not be correct in programs that can read these files.
Hint: An ambient spectrum saved in the Graph tools can be loaded in the MI tools as a "Measured illuminant"
using the "Load.." button. Such a spectrum can also be loaded as a measurement in the ISO 3664+ tools (look
for the section on how to load an ambient spectrum from a file). In both cases, it is important to save only one
spectrum in the file, erasing the second spectrum with the method described in the MEASUREMENTS section
above if required.
Click on "Save image..." to save an image of the display. You will be shown a dialog where you are asked to
select a printing scale:
The 1X scale is equivalent to a screenshot. The 2X scale draws everything twice the size; this is the same as
doubling the resolution for the same image size. The 2X scale is recommended if you want to use the image in
a printed report.
You can copy numerical data by making a mouse right-click (or ctrl + click on a one-button Mac mouse) on
any data field. Shown below is the contextual menu which appears with a right-click on the L*a*b* data field of
Sample #1 (S1); selecting the menu will transfer the three coordinates into the clipboard, separated by Tabs.
You can then easily paste the values in a spreadsheet or document table, where they will be distributed in three
columns.
INTRODUCTION
The ISO 3664+ tools help in measuring if a viewing system meets selected requirements of ISO 3664
("Viewing conditions - for Graphic Technology and Photography") and other standards referred by it, with
additional custom goals for increased flexibility in characterizing your environment. The ISO 3664+ window is
opened either by clicking on the corresponding icon on the toolbar window, or by selecting the "Tools/ISO
3664+" menu.
Important: While a measurement may meet a requirement, such as the brightness level, the CRI, the
Metamerism Index (MI), etc., overall compliance to a standard requires that all tests in the standard be passed
as measured by equipment which exactly meets the specified characteristics. For instance, the i1Pro and i1Pro
2 provide spectral data at 10 nm increments between 380 and 730 nm while the data tables of many standards
referred to by ISO 3664, including ISO 23603, CIE S 012, and CIE 13, are defined for wider wavelength ranges
and for 5 nm bandwidth instruments. Obviously, since an i1Pro cannot provide data below 380 nm, the Ultra-
Violet (UV) Metamerism Index of ISO 23603 / CIE S 012 cannot be measured. On the other hand, in the great
majority of cases, with appropriate data processing, the effects of its larger instrumental bandwidth are small or
negligible, and provide results comparable to the ones obtained with a 5 nm bandwidth instrument, with more
apparent differences sometimes seen with light sources which exhibit very narrow spectral peaks. As with any
instrument, you should also take into account the instrument accuracy provided by the manufacturer when
assessing its measurements.
Important: Although it is identified with the same name, the Metamerism Index referenced to in ISO 3664 is
not the same as the MI determined in the MI Tools. The MI test specifically called for in ISO 3664 is ISO 23603.
This is the same test defined in CIE S 012 /E:2004, which is an evolution of the CIE 51 test. The metamers of
CIE S 012 are basically identical to the ones of CIE 51; however, their spectrums are now defined between 380
and 780 nm instead of between 400 and 700 nm in CIE 51. The grade categories for CIE 51 and CIE S 012 are
the same and are computed in the same manner.
Important: To measure a light source with the ISO3664+ tools, you need to have an i1Pro series
spectrophotometer connected to the computer on which CT&A is running. The instrument must also be
properly recognized by the program; this is confirmed by a small green light beside the instrument selection
menu in the toolbar window, and by the "Calibrate", "Tune", "Test" and "Take all" buttons of the ISO3664+
window being enabled (some data entry buttons and controls will remain disabled and some data fields will not
be available (shown as "N.A.") if the program is not activated). If you plug an instrument in your computer after
the program start, you can attempt to connect the instrument by selecting "Try to connect again..." in the
Instrument menu. A status of the selected instrument can always be obtained by clicking on the "Info" button
located in the toolbar window.
Note: In Windows, if the i1Pro/i1Pro 2 or i1Pro 3 USB drivers are not installed, please consult the
"CT&A_Readme.txt" file located within the main CT&A application folder. This file can be opened directly with
the "Start menu/BabelColor/CT&A Readme" shortcut.
Instrument button support: When the ISO 3664+ tools window is selected, i.e. brought to the front, and
assuming that a compatible instrument is selected and recognized, a large blue indicator appears between
the "Tune" and "Test" buttons. This indicator confirms that the next instrument key press will be assigned to this
window's "Test" button; of course, you can also do a mouse click on any data entry button.
See also:
• Tutorial 8: Measure your display characteristics with the ISO 3664+ tools.
See the end of this section, or click on the references numbers, for contact and purchasing information on the
publications and standards mentioned herein.
The CRI is a number between 0 and 100, with 100 being the best value, which defines how well colors are
rendered by a light source in comparison with a reference illuminant, or standard. This standard can be either
a thermal radiator (blackbody) or a D-series (daylight) illuminant.
The first step in obtaining the CRI is to compute the color difference (Ei) of eight pre-defined color patches
whose coordinates are determined using both the test source and the reference illuminant. Subtracting the
scaled color differences to 100 provides eight numbers which are called Special Color Rendering Indices
(Ri):
The reference illuminant is D50 in ISO 3664, but in this tool, you have the choice of using either the
prescribed illuminant, other common illuminants, or let the program automatically select it. In "Auto" mode, a
D-series illuminant will be selected for color temperatures equal to or larger than 5000 K, and a blackbody will
be selected for color temperatures below 5000 K.
The color patches are "real" patches (compared to CIE 51; see below) with the following descriptions and
references:
The CRI, even though relied on by many, and often quoted as a measure of quality by lamp companies in
particular, should not be considered simply at its face value. With the possibility of selecting a reference in a
large array of illuminants, it is not too difficult to find an illuminant for which the computed CRI is over 90. To
prevent any abuse, the reference illuminant should always be given in association with the CRI. Also, even
though the color rendering properties of illuminants as different as a blackbody at 2856 K (Illuminant A) and
D65 (daylight, 6500 K) are not the same, they will both result in a CRI of 100 if the test source matches the
reference.
Note: This index is computed for ambient type illumination only, not for color monitors.
• ISO 23603 / CIE S 012/E: Standard method of assessing the spectral quality of daylight simulators for visual
appraisal and measurement of colour (Ref. 32). This procedure is used to determine a Metamerism Index
(MI) and a Quality Grade. This index is not the same as the one computed in the MI Tool although it is
similarly based on measuring metameric differences using the CIELAB color difference formula.
ISO 23603 and CIE S 012 /E:2004 are identical; they are an evolution of the CIE 51 test:
CIE 51.2-1999: A Method for Assessing the Quality of Daylight Simulators for Colorimetry (Ref .33).
The metamers of ISO 23603 / CIE S 012 are basically identical to the ones of CIE 51; however, their
spectrums are now defined between 380 and 780 nm instead of between 400 and 700 nm in CIE 51 (see
Ref. 31 which contains tabular data on the metamers used for the visual index of CIE S 012). The MI is
computed in the same manner for CIE 51 and ISO 23603 / CIE S 012, and the quality grade categories are
the same.
The computation of this MI is based on the average color difference of five pairs of virtual metamers (i.e.
theoretical, or mathematically defined). These metamers have been defined in such a way that the computed
color difference is zero for all pairs if the illuminant under test has the same spectrum as the ideal illuminants;
computations are done with the 10 degree Observer (CIE1964). This ideal illuminant is D50 for ISO 3664
but ISO 23603 also covers the use of D55, D65, and D75. A different pair of metamers is assigned by the
standard for each reference illuminant. Any of these reference illuminants can be selected within the tool;
click here for information on this interface.
The difference between ISO 23603 and CIE 13, used to compute the CRI, is that CIE 13 compares the same
patches with two illuminants while ISO 23603 compares two metamers with the test illuminant.
The five virtual metamers have the following L*a*b* and L*C*h coordinates:
The coordinates in the "10 degree" table above are the same for both metamers of a given pair, by
definition. The coordinates in the "2 degree" table correspond to the reference metamers of each pair; the
coordinates for the metamers assigned to each illuminant (not shown) are very slightly different, simply
because the metamers were optimized for the 10 degree Observer.
Note: This index is computed for ambient type illumination only, not for color monitors.
Note: ISO 23603 / CIE S 012 and CIE 51 not only describe how to measure a visible metamerism index, but
an Ultra-Violet (UV) index as well. In practice, the i1Pro and i1Pro 2 cannot do measurements in the range
required for the UV index, and thus, only the visible index is computed.
Warning: The chromaticity tolerance called for in ISO 23603, CIE S 012 and CIE 51 is a 0,015 radius
centered on the reference illuminant whereas ISO 3664 specifies a 0,005 tolerance. This tolerance is
expressed in u'v' coordinates determined with the Uniform Chromaticity Scale (UCS, CIE1976), and the 10
degree Observer (CIE1964).
• ISO 12646:2008: Graphic technology -- Displays for colour proofing -- Characteristics and viewing conditions
(Ref. 32). ISO 12646 is referred to but not specified in ISO 3664. To see the interface corresponding to the
2008 version of ISO 12646, first select the "Color monitors" Viewing Condition, then the 3x3 "Monitor grid".
This version contains, among other tests, a Brightness uniformity specification (Section 4.4) which we have
adapted for this tool because of its usefulness. Brightness uniformity is performed on nine positions defined
by a 3 x 3 grid; the grid is non-uniform as it favors the monitor's center area. The test is performed separately
for the White, Grey, and Dark-Grey patches; the brightness of the white patch at the selected position is
shown in the upper-left of the tool window, if measured. The positions can be selected manually or
automatically; see the ISO 3664+ user interface section for more information.
• ISO 12646:2014-Final Draft: Graphic technology -- Displays for colour proofing -- Characteristics (Ref. 32).
ISO 12646 is referred to but not specified in ISO 3664. To see the interface corresponding to the 2014
version of ISO 12646, first select the "Color monitors" Viewing Condition, then the 5x5 "Monitor grid". This
version contains, among other tests, a Tone uniformity specification (Section 4.2.2) which is in effect a Color
uniformity test; this test is selected by the "Color" radio button in the tool interface. The standard also
contains a Tonality Evaluation (Uniformity) specification (Section 4.2.3) which is based on the ratio of the
luminances of the GREY and WHITE patches; this test is selected by the "Tone" radio-button in the tool
interface. Both tests are performed on twenty-five positions defined by a uniform 5 x 5 grid. The positions can
be selected manually or automatically; see the ISO 3664+ user interface section for more information.
Color: The reference white illuminant for Color uniformity is the center patch XYZ coordinates. The "color" of
the other patches is compared with the center using the CIEDE2000 color difference equation. Thus, a color
difference from the center patch is shown for all non-center positions; by definition, when measured, the
center patch shows a color difference of zero. The color difference is performed separately for the White,
Grey, and Dark-Grey patches. Please note that only the color difference is shown in the interface
representing the 5 x 5 grid; the XYZ and L*a*b* coordinates used to compute the color difference are not
required to be shown by the standard.
Tone: The deviation from uniform tonality (Ti) for a non-center position (with index i = 1 to 24) is expressed
by the following equation:
Ti = abs(Ri / Rc - 1)
where Rc is the Grey/White luminance ratio measured in the center, and Ri is the ratio for the non-center
position. The maximum deviation seen when all positions are measured shall be less than 0.1 (or 10%, which
is the number format used in CT&A). By definition, when measured, the center patch shows a tonality
deviation of zero. Please note that only the tonality deviation is shown in the interface representing the 5 x 5
Important: the reference display illuminant for color monitors is D50 in ISO 12646 while it is D65 in ISO
3664. The difference stems from the different target applications. ISO 3664 is dedicated to applications
where the display and the hardcopy are viewed independently, and ISO 12646 is dedicated to applications
where direct comparison is made between the monitor and the hard copy. Either illuminant (or others) can be
selected as the reference in CT&A.
Warning: If you elect to use the specifications of ISO 12646:2008 for your color monitors, you should be
aware that the chromaticity tolerance for the D50 illuminant is 0,010, not 0,025 as in ISO 3664 (both
expressed in u'v' coordinates, UCS, CIE1976 and the 10 degree Observer).
The following table shows a snapshot of the requirements for each condition:
Surround
u'v' luminous
Viewing Ref. Illuminance / CRI MI Illuminance
tolerance refl./
condition Illuminant Luminance (CIE 13) (ISO 23603) uniformity
(note 1) lum./
illumin.
neutral and
dark gray
2 or black
> 80 cd/m
Color D65 0,025 N.A.
(should be N.A. N.A. (should be
monitors (note 2) (note 2) (note 3)
2 ≤ 32 lux)
> 160 cd/m )
(shall be
≤ 64 lux)
Note 1: The chromaticity coordinates, u' and v', are determined using the CIE1976 Uniform Chromaticity
Scale (UCS) equations and a 10 degree Observer (CIE1964); the tolerance is a radius with its center on the
reference illuminant.
Note 2: In ISO 12646:2008, the reference illuminant for the monitor is D50 and the chromaticity tolerance is
a 0,010 radius.
Note 3: There are no specific requirements for luminance uniformity on color monitors in ISO 3664.
Nonetheless, CT&A can perform uniformity measurements based on ISO 12646:2008 (Brightness, 9
positions) and ISO 12646:2014 (Color and Grey/White tone ratio, 25 positions).
Note 4: Projection viewing of TRANSPARENCIES not supported in CT&A.
Purchasing ISO and CIE publications can be done through the following sources:
https://www.iso.org/
http://www.cie.co.at (CIE International headquarter)
http://www.cie-usnc.org (CIE U.S.A. branch)
The Color Rendering Index (CRI) and Metamerism Index (MI) tests are not required when the "Color monitors"
viewing condition is selected, and these tools are not shown for this selection.
Important: The "P1" and "P2" viewing conditions are not available for an i1Pro sold without ambient
measurement capabilities, and thus without the diffuser cap accessory. This can be confirmed by looking at the
Toolbar status lights or by opening the Instrument info dialog. Some of the older models can be factory
refurbished; please contact X-Rite for additional information.
Selecting "Goal" will show the tolerance required by ISO 3664, which varies according to the viewing
conditions. You can also select targets corresponding to many ambient viewing conditions and popular display
color temperatures. Data will be updated if the target center is changed after a measurement is done. Data will
be updated if it is changed after a measurement is done.
• Select the "Ref. Illuminant" for the Color Rendering Index (CRI):
• 2856 K (Illuminant A)
• 3200 K (TV Studio lighting)
• 3500 K (SoLux lamp)
• 4100 K (SoLux lamp)
• 4700 K (SoLux lamp)
• 5000 K (SoLux lamp)
• D50
• D55
• D65
• D75
• Auto
D50 is required by ISO 3664. Selecting "Auto" will compute the CRI based on the measured temperature, in
kelvin. A D-series illuminant will be selected for color temperatures equal to or larger than 5000 K, and a
blackbody will be selected for color temperatures below 5000 K. Data will be updated if the reference illuminant
is changed after a measurement is done.
D50 is required by ISO 3664. Data will be updated if the reference illuminant is changed after a measurement
is done.
• For the P1, P2, and T1 "Viewing Conditions", select a position in the "Brightness uniformity" group by clicking
on one of the nine radio buttons.
• For the Color monitors "Viewing condition", first select the "Monitor grid", either 3x3 corresponding to the
"Brightness uniformity" measurements of ISO 12646:2008, or the 5x5 grid corresponding to the "Color and
Tone uniformity" measurements of ISO 12646:2014. Select the target color and one of the positions. The
target colors and their corresponding RGB 8-bit values are:
• White: R=G=B= 255
• Grey: R=G=B= 127
• Dark-Grey: R=G=B= 63
When the targets are generated and displayed by CT&A, the display profile is NOT used. However, the
displayed color should be the same as if a display profile was used, the reason being that color profiling
programs first correct the display White Point (WP) and the neutral axis by modifying the graphics card Look-
Up-Tables (LUT) before computing an ICC profile. By doing this, the WP and neutral axis are corrected even
when a program is not ICC-aware (Note: CT&A is ICC-aware but displaying the targets with profile correction
is not a requirement here). Yet, if you wish, you could display the targets with an ICC-aware program; for this
task, you need target images, with one image per target color. Such images can be generated with the
provided target creation dialog illustrated later in this section. In your ICC-aware imaging program you should
then associate the display profile to the image data, which should also be displayed using the display profile;
since the input and output profile are the same, this is equivalent to using no ICC profile! What is most
important here is to make sure the proper graphics card's LUTs corresponding to the display profile are
loaded; on Windows this usually happens at reboot and requires a dedicated LUT application provided by the
profiling program manufacturer, while on a Mac simply selecting a profile is usually sufficient.
• If not already done, calibrate the instrument by clicking on the "Calibrate" button and following the on-screen
instructions. Please note that the P1 and P2 viewing conditions require calibrating the instrument in
"Ambient" mode, with the diffuser adapter mounted, while the T1 and Color monitors’ conditions require a
calibration in "Emission" mode, without the diffuser.
Note: In CT&A, emission calibration requires the measurement of a white patch, preferably located on the
display or emissive surface on which subsequent measurements will be performed; this procedure sets the
White Point (WP). The WP characteristics (display location, luminance and CCT) are shown in the toolbar
window, as seen in green text in the next screenshot.
A test result will be shown as PASS or FAIL. A green colored PASS over a black background indicates that the
test meets the requirements of ISO 3664. A yellow colored PASS over a black background indicates that the
test meets the selected goal but this goal is not the one recommended by ISO 3664.
Let's go back to the first screenshot shown in the ISO 3664+ tools introduction, which is reproduced below. The
measured brightness (1991 lux) meets the requirement of the P1 Viewing Condition (for critical comparison of
prints), which is 2000 lux. The location where the measurement was taken, in the bottom-center of the viewing
zone, is shown in the "Brightness uniformity" section (there is not enough data to show a Pass/Fail result). The
green central zone of the chromaticity target represents the maximum acceptable u'v' offset (the vector
obtained by combining the u' and v' offsets). In our example, the target center has been selected as "Goal",
which corresponds to D50 for this viewing condition; the measured offset (illustrated by a yellow dot) is 0,0084,
outside of the acceptable zone (A "passed" chromaticity measurement would be illustrated by a white dot).
The CRI results are presented as an index between 0 and 100, with 100 being the best result. The index of
each sample used in the CRI computation is presented in a data table; these values are called the "Special
indices". The data table can be sorted by clicking on a column heading: "Sample", "SI", or "P/F" (i.e.
"Pass/Fail"). The CRI is the average of these indices. For the above screenshot, the goals for the special
indices as well as the one for the CRI are met. Finally, we see that we meet the MI requirements.
In another example shown in the screenshot below, we see that a 4195 K blackbody was selected to compute
the CRI of a D50 light source. The measured chromaticity, the yellow dot just outside of the target, is shown
with a red circle to indicate it is out-of-range (Note: Measurements located outside of the target are always
shown on the target periphery even if located farther away).
The three colored diamonds around the chromaticity target are used to identify primary colors that need to be
removed or added in order to approach the target center. When a measurement is close to a diamond, then we
should remove this diamond's color. In the above screenshot we see that the measurement is too red, which is
not surprising since the measured dource is at a lower temperature than our goal (D50 target center), and thus
with a more reddish appearance. If the measurement had been midway between the green and red diamonds,
then we would have had too much yellow (green + red, in additive fashion), or not enough blue, as we can use
the opposite diamond to see what color needs to be added.
Note: The "diamonds" are positioned on the target edge at locations which are a projection of the primaries
(R=830 nm, G=515 nm, B=360 nm) relative to the selected target center (i.e. the Illuminant). Because the
Illuminants are not located at the same place in the u'v' chromaticity diagram (CIE1976, 10 degree Observer),
the locations of the primaries' projections are adjusted for each case.
In order to make multiple measurements at a fast rate, just click on the "Tune" button to start the tuning mode;
the tuning mode can be used for all viewing conditions. A small dialog will open, asking you to set the interval
between the measurements which will be done continuously until the tuning mode is stopped. Use the colored
diamonds as a guide when tuning.
Hint: The color differences of the five metamers used to determine the MI Quality Grade, not shown in the tool
interface, is contained in the report generated by clicking the "Save to file..." button. You will also find in this file
all the other data presented in the tool window. In addition, you can print a well-formatted one-page report
which contains information dedicated to compliance-type reports by clicking the "Print report..." button.
We will see next the various uniformity tests which can be performed with the tool.
Brightness uniformity (for ambient measurements, transparency viewer): The two screenshots below
show brightness uniformity results obtained with measurements done for the P1 Viewing Condition (Note: The
P2 interface is identical, and the transparencies interface is nearly identical). The image on the left shows
measurements done at seven of the nine positions; the non-measured positions are shown in yellow. The
positions which meet the requirement of 75%+ relative to the center position are shown in green, and the one
which does not meet it is shown in red; the brightness uniformity thus fails because of this single position where
the brightness is 70% of the center value. The image on the right shows a similar set of measurements where
the brightness uniformity is within requirement, even if we notice a brightness decrease towards the left side of
the monitor. The data from the image on the right can also be seen in the Example-1 screenshot of the printed
reports section; please note that the report includes other measurements not shown here.
All the measurements and results (Brightness, Chromaticity, CCT, uniformity, as well as CRI and MI when
applicable) for a given position, and for a selected target color if applicable, can be erased by first selecting the
position for which you want to erase the data, and then clicking on the "Clear pos." button.
All the data for all positions of a given viewing condition, and for a selected target color if applicable, can be
erased by clicking the "Clear all" button.
If required, you can select any other position and continue the sequence from this point. In the P1, P2, and T1
Viewing Conditions, and when measuring an external monitor, do a mouse click to select the position in the tool
window. When measuring a monitor connected to your computer, use the arrow buttons on the keyboard to
change the target position. Changing the target position while doing a "Take all" sequence is useful if you are
not sure of a measurement or if you pressed on the instrument button inadvertently.
If the "Color monitors" viewing condition is selected, clicking the "Take all" button will open a small dialog which
asks if you want to do the measurements on the display used for White Point calibration; if not, we suggest you
redo the emission calibration. If you select a display attached to the same computer on which the CT&A
program resides, the program can automatically draw the targets at the prescribed screen positions for this
monitor (one or two monitors supported). If you want to perform these measurements manually, or on a third
display, or on the display of another computer, we suggest that you use dedicated target images instead of a
simple large patch that fills the screen.
You can define target images for any monitor size by clicking on the "Targets..." button; this will open the
following dialog:
If you need targets for the computer on which CT&A is running, just position the dialog within the monitor for
which you want the targets and click on the "Assign values for this display" button; this action will fill the
target parameters fields. The target parameters can also be manually set to the values of your choice. Select
the monitor grid for which you want the targets as well as the file type and click the "Save" button when ready.
A file name will be proposed; edit the name if you wish but please note that a suffix identifying the target color
will be added for each of the three image files that will be generated. You can then open the images using the
graphic editing program of your choice; we recommend using a program which offers a "Full screen" viewing
mode.
Note: The 3x3 grid defined in ISO 12646:2008 favors the monitor's center area, and the targets are thus non-
uniformly distributed on the monitor, while the 5x5 grid defined in ISO 12646:2014 is uniform.
Click on "Save to file..." to save an ISO 3664 report. The report has tab-delimited data that can be directly
imported in a spreadsheet program, and opened in many text editing applications (it is suggested to use a
monospace font, such as Courier, in order to facilitate formatting).
The problem with earlier units is related to the polarization of the light emitted from the display. In an LCD
display, the intensity of each pixel is controlled by rotating the light's polarization state between crossed
polarizers, and the light coming out is linearly polarized (often at a 45 degrees angle). To check this, look at
your display using a photographic polarizing filter (or polarizing sunglasses), and rotate it slowly; you should
see maximum and minimum transmission for angular positions separated by 90 degrees. The display light is
not seen differently by the human eye whether it is polarized or not, since we only perceive the light intensity;
however, polarization can affect an instrument reading.
In order to obtain reproducible and valid measurements, we recommend making all measurements with the
instrument placed at the same angle that was used for calibration. If calibration is done with the instrument
suspended in its cradle, as shown in the following illustrations, all subsequent measurements should be done
with the i1Pro placed vertically. It is acceptable to make measurements with the instrument turned 180 degrees
from its calibration position, so that it is still vertical, as shown in the illustration on the left. Accordingly, in such
a case, measurements should not be done with the instrument positioned horizontally, or at an angle, as shown
in the illustration on the right.
Note: "Older" CRT displays do not emit polarized light and are thus not susceptible to errors due to instrument
orientation.
Note: Colorimeters, such as the Eye-One Display or i1Display Pro, are usually not affected by this effect.
A plain text file can easily be created with a word processor or a spreadsheet application, as shown below.
When saving the file, do not use the often complex native application file formats (for ex.: *.xls); instead, select
a tab-delimited or Comma-Separated-Value (CSV) text format.
Important: You should make sure that the file data corresponds to the selected viewing condition, i.e. ambient
measurements for P1 and P2, and emission measurements for T1 and color monitors.
Note: You can load a spectrum in any of the nine (9) positions shown in the “Brightness uniformity” group (P1,
P2, T1, and 3x3 Color monitors viewing conditions) or in any of the twenty-five (25) positions of the “Color and
Tone uniformity” group (5x5 Color monitors). File input is also possible after you click the "Take all" button.
Data entry forms appear in a dialog box when you press the ‘Print report…’ button. These forms are to be used
to fill the data fields which appear in the bottom of the report (highlighted below). Two forms are presented, one
for the P1, P2, and T1 Viewing Conditions, and another for the Color monitors Viewing Condition.
Example 1 (P1): The first screenshot corresponds to the P1 brightness uniformity results shown in the ISO
3664+ tools interface section; while the brightness uniformity passes, as well as the CRI and MI, the absolute
illuminance levels is too high in the center and the chromaticity fails at all positions.
INTRODUCTION
The Metamerism Index tools window is opened either by clicking on the MI icon on the toolbar window, or by
selecting the "Tools/Metamerism Index" menu.
Important: The Metamerism Index tools can accept inputs from a file or from a supported instrument. A
CONNECTED INSTRUMENT IS NOT REQUIRED in order to use these tools. Files for the Reference and
Sample patches may contain one or more reflectance spectrums while files for the Measured illuminants MUST
contain only one ambient spectrum. A file may be either a text file complying with the CGATS format, or a plain
text file. The specific requirements for each file formats are presented in the MI input file requirements
(reflectance) and MI input file requirements (custom illuminant) sections.
Note: In Windows, if the i1Pro 2 USB drivers are not installed, please consult the "CT&A_Readme.txt" file
located within the main CT&A application folder. This file can be opened directly with the "Start
menu/BabelColor/CT&A Readme" shortcut.
Instrument button support: When the MI tools window is selected, i.e. brought to the front, and assuming that
a compatible instrument is selected and recognized, a large blue indicator appears next to the "Get Ref." or
"Get Sample" button. This indicator identifies the data that will be measured if you press the instrument button;
of course, you can also do a mouse click on any data entry button. The indicator automatically changes
location after making a measurement. You can click (left-click) on the indicator to move it to the previous
measurement if required, or do a right-click to lock it on a given measurement. You can also do a left-click
on a locked indicator; the new position will be locked.
Matching inks to textile colors is a similar process. The ink pigments and the textile dyes usually have different
spectrums but a color match can still be obtained. However, because the spectrums are different, the match is
usually dependent on the illuminant. For instance, an ink patch matched with a textile color under a halogen
lamp may not match under daylight or fluorescent illumination.
There are basically two aspects to look at when we want to match two colors under different lights. The first is
how each color will be perceived under these lights, or how "constant" the color is, and the second comes into
play when you compare the two colors simultaneously. For the first aspect, an index which characterizes the
stability of a single color under different light sources has been defined: the Color Inconstancy Index (CII).
Computing the CII requires a Chromatic Adaptation Transform (CAT) matrix, which exists in many variants. The
CAT recommended for the CII is CIECAT02, used in the CIECAM02 color appearance model (Ref. 26-28). The
CIECAT02 matrix is a variant of a simplified Bradford CAT, where some non-linear parameters are omitted, and
which is further optimized in regards to many experimental data sets.
The recommended daylight reference illuminant is D65. This is consistent with the use of L*a*b* as the color
difference space, since it is often considered that the L*a*b* space is most uniform for D65. However, in CT&A,
the user has the option to select any one of 12 preset illuminants, or one of two measured ambient sources.
Now let’s see what happens if we compare two colors simultaneously. If the pigments or dyes are of the same
type and origin, the two patches should remain quite similar under various illuminations. If not, which is quite
common in the real world, the match will generally hold only for a limited set of illumination conditions (if well
done!).
Important: The REFERENCE and TEST illuminants may not be the same for the CII and SMI.
Because the SMI is simply the color difference between two samples under a single illuminant, it can be
determined using any color difference formula (CIELAB, CIE94, CMC, etc.). However, as mentioned above, if
we do not have a perfect match under the Reference illuminant, we cannot use this number as the MI.
Computing a general MI is more complex because each sample spectrum interacts with each illuminant
spectrum, for a total of four sample-illuminant combinations. Many formulas were proposed and tested, some
which use residual differences of a wavelength by wavelength comparison between the two samples (Ex.:
Bridgeman's, and Nimeroff and Yurow's metameric indices), and some which are simply based on the L*a*b*
coordinates of the samples. While the spectral math approach may seem more accurate, it was found that the
L*a*b* based methods, which take into consideration the illuminant, showed better correlation with the
perceived difference (Ref. 29).
MI (CIE15)
When the Reference and Sample patches are not exactly metameric under the Reference illuminant, this
means that:
𝑋𝑋𝑋𝑅𝑅𝑅., 𝑅𝑅𝑅.𝑖𝑖𝑖. ≠ 𝑋𝑋𝑋𝑆𝑆𝑆𝑆𝑆𝑆, 𝑅𝑅𝑅.𝑖𝑖𝑖. .
In such a case, we apply a Multiplicative Correction to the Sample XYZ values obtained with the Test
illuminant. The correction is the ratio of the Reference and Sample XYZ values obtained with the Reference
illuminant:
𝑋𝑋𝑋𝑆𝑆𝑆𝑆𝑆𝑆 𝑐𝑐𝑐𝑐., 𝑇𝑇𝑇𝑇 𝑖𝑖𝑖. = 𝑋𝑋𝑋𝑆𝑆𝑆𝑆𝑆𝑆, 𝑇𝑇𝑇𝑇 𝑖𝑖𝑖. �𝑋𝑋𝑋𝑅𝑅𝑅., 𝑅𝑅𝑅.𝑖𝑖𝑖. / 𝑋𝑋𝑋𝑆𝑆𝑆𝑆𝑆𝑆, 𝑅𝑅𝑅.𝑖𝑖𝑖. � .
In the Metamerism Index tools dialog, the (CIE15 corrected) data field represents the corrected Sample L*a*b*
values derived from the corrected XYZ values.
The color difference between the Reference patch L*a*b* value obtained with the Test illuminant and the
corrected Sample patch L*a*b* is the MI (CIE15) value.
where n1 refers to the first illuminant and n2 refers to the second illuminant, and where
are computed with the data of the illuminant referred to in the MI equation.
Note: In a HunterLab Application Note (Ref. 44), the following guidelines are mentioned in regards to the above
equation when matching textile colors with dyes:
- Acceptable match: MI < 0,5
- Doubtful match: 0,5 ≤ MI < 1,0
- Not acceptable: 1,0 ≤ MI (the application note uses the term "reformulation")
- Be less stringent when matching with a fluorescent-tube illuminant (such as F2, F7, F11, etc.)
Note: You will obtain the same value for the SMI and both MI if the Reference and Sample patches match for
one Illuminant (∆L*, ∆a*, and ∆b* are zero for the matching illuminant), AND if you select CIELAB as the color
difference formula for the SMI.
Note: In addition to the Metamerism Index tools, CAT matrices are used in CT&A for space conversion in the
RGB vs RGB tool, and to compute all display colors. Two CAT matrices are available, "CIECAT02" and
"Bradford"; it can be selected in the "Math" tab of the Preferences dialog.
• Select the Measurement Conditions: If you are using an i1Pro 2 with the "i1Pro / i1Pro 2 (XRGA)" driver, an
I1Pro 3, or an i1Pro 3 Plus, you can select the "Measurement Conditions" M0 (Ill-A), M1 (D50), or M2 (UV-
cut), as defined in ISO 13655 (Ref. 42). A description of the M0/M1/M2 measurement conditions can also be
found in the FluoCheck tools. If you are using an i1Pro, or an i1Pro 2 with the "i1Pro / i1Pro 2 (non-XRGA)"
driver, the program will select the default measurement conditions supported by the instrument.
Hint: For file input, if you want to enter data in all measurement conditions and the instrument is not
compatible, you can either unconnect the instrument or select a colorimeter in the instrument menu.
Important: Although the Metamerism Index tools can provide data when measuring color patches printed on
a fluorescent substrate, the MI tools are better used for non-fluorescent substrates and non-fluorescing inks.
If you have an i1Pro 2 connected using the the "i1Pro / i1Pro 2 (XRGA)" driver, all measurements are made
with the three measurement conditions and you can switch the condition to see if the CII, SMI, and MI indices
are affected. For fluorescent substrates, we recommend using the FluoCheck tools; however, even in such a
case, you can use the MI tools with the M2 measurement condition to evaluate the color stability when there
is no substrate fluorescence (assuming your instrument supports M2). If you have an i1Pro which is not UV-
cut, you can check substrate fluorescence using the Whiteness tools and a UV filter (not provided).
• Select the "CII/SMI formula", a color difference formula, used to compute the CII and SMI values. Data will be
updated if it is changed after a measurement is done. The available color difference formulas are:
• CIELAB
• CIE94 (i.e. the common formula, CIE94 (1:1))
• CIE94 tex. (i.e. CIE94 for textile, CIE94 (2:1))
• CIE94 (2:2)
• CMC (2:1)
• CMC (1:1)
• CIEDE2000
Note: CIE94 (2:2), where kL=2 and kC=2, is recommended by Berns (Ref. 25, p. 129) to determine the CII as
it puts more weight on the hue (with kH=1) than on the lightness and chroma, which is the intent of the CII
measurement.
Note: Because the CII, SMI, and MI are color differences, the same criteria and thresholds used in evaluating
color differences should apply when assessing these numbers.
Note: The HunterLab MI values are always computed using CIELAB color differences.
• Select the reference illuminant for CII computation. D65 is recommended but any other is valid.
• If not already done, calibrate the instrument by clicking on the "Calibrate" button and following the on-screen
instructions.
Note: Computing the CII requires processing the measured data with a Chromatic Adaptation Transform (CAT)
matrix. CT&A supports the "CIECAT02" and "Bradford" matrices but CIECAT02 is recommended for the CII. If
"Bradford" is currently selected, you will see a warning message, in red, in the MI window, as shown below.
You can select the CAT matrix in the Preferences dialog.
The illuminance (lux), the Correlated Color Temperature (CCT, in kelvin), the Color Rendering Index (CRI, see
the CIE 13.3 section in the ISO3664+ tools description), and the CCT used for CRI computation will be shown
at the right of the "Get Ambient" button. Once measured, you can save the spectrum in a file for reference, or
for use at a later time.
Hint: If there is a problem during the ambient calibration procedure, for example, if you forget to place the black
cap on the diffuser, then the calibration should be redone. However, if you click on the "Calibrate" button while
in the MI tools, the default procedure is to calibrate in Reflectance, and not in Ambient mode. To redo a
calibration in Ambient mode, open the Graph tools, select the "Ambient" mode, and then click on the "Calibrate"
button. Once the calibration is completed, you can go back in the MI tools and measure an ambient source.
Hint: We recommend saving your ambient light source measurements since, apart from the spectrum, the file
contains: the illuminance, the CCT, the CRI with the CRI reference CCT, the chromaticity coordinates (xyY),
and the tristimulus values (XYZ). This file can be opened in any word processor or spreadsheet application.
Hint: An ambient spectrum saved in the MI tools can be used as input in the CRI and ISO 3664+ tools.
Important: Although the ambient spectrum is saved is a CGATS compatible file format, which can be opened
by most color processing software, it contains a spectrum which is not normalized to 1 or 100, like a reflectance
spectrum. The appearance of the patch and the computed color coordinates will thus not be correct in such
programs.
You will find files of many standard illuminants in the "Illuminants" folder located within the main CT&A
application folder. In Windows, this folder can be opened directly with the "Start menu/BabelColor/Illuminant
files" shortcut.
If Ambient-1 or Ambient-2 is selected but not already measured, or loaded from file, when measuring the
Reference or Sample, you will get a message asking you to acquire the ambient spectrum. Once a Reference
or Sample is measured, the window data will be updated whenever you change an illuminant.
INSTRUMENT MEASUREMENTS
To make a measurement, either click on the "Get Ref." or "Get Sample" button or press the instrument button.
A large blue indicator is located beside the input that will be selected if you press the instrument button:
This indicator automatically changes location when an input is done at one position. Do a left-click on an
indicator to change its position or a right-click to lock it (a locked indicator has a red border: ). You can also
do a left-click on a locked indicator; the new position will be locked.
To erase a measurement, first press the Alt key, in Windows, or the Option key on a Mac. Whenever the
mouse cursor is within the tool window, the "Get Ref." and "Get Sample" buttons will change their caption to
"Clear" (if there is a measurement). To clear the sample, click the button with the mouse while keeping the Alt
or Option key pressed:
The analysis clearly shows that the Reference and Sample patches are not matched. This is not to say that a
high CII is synonymous with high MI, since the color shift could be in the same direction for the two colors and
could possibly result in a near-zero MI, as we will see with the second example on the next page.
If these were pieces of clothes, their color relationship would be the same under tungsten halogen lamps (i.e.
Illuminant A) in a room, or outside in daylight.
Note: A clipping indicator appears in the bottom left corner of a color patch when the color of the sample it
represents is outside of the RGB space gamut of the monitor.
Click on "Save report..." to save a Metamerism Index report. The report contains:
• The L*a*b* values for the Reference and Sample patches.
• All CII, SMI, and MI data.
• The Reference and Sample patches spectrums.
The report is tab-delimited; it can be directly imported in a spreadsheet program and opened in many text
editing applications (it is suggested to use a monospace font, such as Courier, in order to facilitate formatting).
Data is saved for all applicable Measurement Conditions.
Click on “Save meas…” to save the Reference and Sample patches spectrums in a CGATS format text file,
which can easily be used for file input afterwards.
You can copy numerical data by making a mouse right-click (or ctrl + click on a one-button Mac mouse) on
any data field (L*a*b*, CII, SMI, MI)). Shown below is the contextual menu which appears with a right-click on
the upper-left CII, which quantifies the color inconstancy for the Reference between "D50" and "D65". When
copied, the data is transferred into the clipboard. Please note that L*a*b* values are separated by Tabs; you
can then easily paste the values in a spreadsheet or document table, where they will be distributed in individual
cells.
Note: At any time, you can use a data file as input in place of a measurement; a connected instrument is NOT
required for file input. A file may contain one or more spectrums.
In this dialog, the available Measurement Conditions depend on the connected instrument capabilities. Here
are a few examples:
• An i1Pro may be capable of providing only M0 or M2 data, depending on the instrument model.
• An i1Pro 2 with M0/M1/M2 capabilities will provide only M0 data if connected with the “i1Pro / i1Pro 2
(non-XRGA)” instrument driver.
• An i1Pro 2 with M0/M1/M2 capabilities can provide measurements in all measurement conditions
(M0/M1/M2) if connected with the “i1Pro / i1Pro 2 (XRGA)” instrument driver.
If you want to enter data in all measurement conditions and the instrument is not compatible, you can either
unconnect the instrument or select a colorimeter (an instrument which cannot provide spectral data) in the
instrument menu. This will disable instrument input for all spectral tools but will enable all measurement
conditions in this dialog
The file requirements are described in the MI input file requirements (reflectance) section.
Important: You should make sure that the file data represents reflectance measurements. The reflectance
values shall be defined between zero and one, with one representing full (100%) reflectance or between 0 and
100.
A plain text file can easily be created with a word processor or a spreadsheet application, as shown below.
When saving the file, do not use the often complex native application file formats (for ex.: *.xls); instead, select
a tab-delimited or Comma-Separated-Value (CSV) text format.
A plain text file can easily be created with a word processor or a spreadsheet application, as shown below.
When saving the file, do not use the often complex native application file formats (for ex.: *.xls); instead, select
a tab-delimited or Comma-Separated-Value (CSV) text format.
Hint: If you are not sure of your file format, simply load it and save it under another name; then compare the
two files to see if the data is the same.
INTRODUCTION
The RAL DESIGN tool window is opened either by clicking on the corresponding icon on the toolbar window,
or by selecting the "Tools/RAL DESIGN" menu. The RAL DESIGN tool is a straightforward measurement and
conversion tool that presents the measured data as per the RAL DESIGN HLC convention:
• H: Hue angle (from 0, written as “000”, to 360 degrees)
• L: Lightness (apparent brightness, from 0, written as “00”, to 100)
• C: Chroma (saturation, from 0, written as “00”, to 100)
The RAL DESIGN notation is based on L*C*h data computed from illuminant D65 and the 10 degree Standard
Observer (CIE1964). HLC data is simply a reordering of the L*C*h values, with "h" becoming "H" and being
shifted as the first coordinate. The values are also rounded to the nearest integer. For additional information on
the RAL DESIGN notation, Measurement Conditions, and where you can purchase reference chips, click here.
Important: The RAL DESIGN tool can accept inputs from a file or from a supported instrument. A
CONNECTED INSTRUMENT IS NOT REQUIRED in order to use this tool. A file may contain one or more
spectrums; multiple files can be inputted with drag-and-drop on the "Load file…" button. The input data is
immediately converted and saved in a CGATS format text file. A file may be either a text file complying with the
CGATS format, or a plain text file. The specific requirements for the file formats are presented in the RAL
DESIGN input file requirements section.
Important: To measure a color with the RAL tool, you need to have an i1Pro series spectrophotometer
connected to the computer on which CT&A is running. The instrument must also be properly recognized by the
program; this is confirmed by a small green light beside the instrument selection menu in the toolbar window,
and by the "Calibrate" and "Get RAL" buttons of the RAL DESIGN window being enabled (some data fields will
not be available (shown as "N.A. in demo") if the program is not activated). If you plug an instrument in your
computer after the program start, you can attempt to connect the instrument by selecting "Try to connect
again..." in the Instrument menu. A status of the selected instrument can always be obtained by clicking on the
"Info" button located in the toolbar window.
Note: In Windows, if the i1Pro/i1Pro 2 or i1Pro 3 USB drivers are not installed, please consult the
"CT&A_Readme.txt" file located within the main CT&A application folder. This file can be opened directly with
the "Start menu/BabelColor/CT&A Readme" shortcut.
Instrument button support: When the RAL DESIGN tool window is selected, i.e. brought to the front, and
assuming that a compatible instrument is selected and recognized, a large blue indicator appears beside the
"Get RAL" button. This indicator confirms that the next instrument key press will be assigned to this button; of
course, you can also do a mouse click on the button.
Note: If you are using an i1Pro 2 with the "i1Pro / i1Pro 2 (XRGA)" driver, an i1Pro 3, or an i1Pro 3 Plus, all
measurements will be taken with the three "Measurement Conditions", M0 (Ill-A), M1 (D50), and M2 (UV-cut),
as defined in ISO 13655 (Ref. 42). A description of the M0/M1/M2 measurement conditions can also be
found in the FluoCheck tools. If you are using an i1Pro, or an i1Pro 2 with the "i1Pro / i1Pro 2 (non-XRGA)"
driver, the program will select the default measurement conditions supported by the instrument and data will
not be shown for the other measurement conditions.
• If not already done, calibrate the instrument by clicking on the "Calibrate" button and following the on-screen
instructions.
INSTRUMENT MEASUREMENT
To make a measurement, just click on the "Get RAL" button or press the instrument button. Apart from the
measurement in RAL DESIGN notation, the display also shows the L*a*b* and L*C*h values. If you take a
measurement of a color patch printed on a non-fluorescent substrate, the M0, M1, and M2 values should be
identical, as shown in the screenshot at the beginning of this section. However, if the substrate is fluorescent,
you may obtain three different values, as shown below:
HINT: Even though all colors can be represented in RAL DESIGN notation, not all colors are available in "real"
inked or painted color chips. The standard RAL DESIGN patches are typically offered in increments of five for
each coordinate. For communicating the RAL DESIGN value, we suggest you give the exact measurement as
well as the closest available printed patches.
Note: A clipping indicator appears in the bottom left corner of the color patch when the color of the sample it
represents is outside of the RGB space gamut of the monitor.
The input data is immediately converted and saved in a CGATS format text file. The output data comprises:
• the color in RAL DESIGN notation (defined as the SAMPLE_NAME);
• the individual RAL Hue, Lightness, and Chroma (HLC) components;
• L*a*b* computed with Illuminant D65 and the 10 degree Observer;
• the original file sample ID, if present, or a sequential ID, if not;
• the original sample NAME if detected, and redefined as SAMPLE_REF.
The input file requirements are described in the RAL DESIGN input file requirements section.
Click on "Save to file..." to save a RAL DESIGN report based on instrument measurements, i.e. not from file
input. The report has tab-delimited data that can be directly imported in a spreadsheet program, and opened in
many text editing applications (it is suggested to use a monospace font, such as Courier, in order to facilitate
formatting).
You can copy numerical data by making a mouse right-click (or ctrl + click on a one-button Mac mouse) on a
data field. Shown below is the contextual menu which appears with a right-click on the RAL (HLC) data field of
the M1 measurement condition. Right-clicking in any data field will give you the choice of copying only the field,
or the data of the entire row or column in which the cell is located, or even all measured data. When copied, the
data is transferred into the clipboard. Please note that L*a*b*, L*C*h, and RAL values are separated by Tabs;
you can then easily paste the values in a spreadsheet or document table.
However, apart from its limited size, RAL CLASSIC has a major drawback: it cannot describe "any" color. To
solve that issue, a new RAL system was devised, this time based on modern colorimetric criteria. Called RAL
DESIGN, the system numbering scheme is a simple re-ordering and rounding of the L*C*h color space values
which is presented as HLC, for Hue, Lightness, and Chroma, with the hue being placed as the first coordinate.
While any color can be represented in the RAL DESIGN notation, not all colors can be reproduced physically
on printed patches. In practice, 1625 patches are offered in fixed spaced increments of 5 to 10 units for each
parameter. The nearest physical patch of the above example is:
060 80 10 .
If the match is critical, it may be advisable to identify two or three nearest patches and visually interpolate
between them. For the example above, for which a patch with close enough Lightness is not available, these
would be:
060 70 10 and 060 80 10 .
In order to obtain RAL DESIGN data, the original requirements were as follow:
Note: The required instrument, model DC 3890 from the Datacolor company, is not available anymore and
support has been discontinued in September 2002. Since then, we have seen the Datacolor SF 600X
mentioned as a reference instrument; however, other instruments of the same geometry are easily available
from various manufacturers.
Important: As per RAL DESIGN requirements, CT&A uses the 10 degree Observer (CIE1964) and the D65
illuminant for its calculations. These requirements correspond to the needs of the paint and textile markets.
Unfortunately, this also means that RAL DESIGN data cannot easily be converted to, or compared with, typical
data available in the printing and graphic fields, since these fields are essentially based on the 2 degree
(CIE1931) Observer.
Important: As indicated above, RAL DESIGN data should be derived from a spectrophotometer configured
with a d / 8° geometry, where the color sample is subjected to a diffuse illumination and measurement is done 8
degrees away from the sample normal. Since the i1Pro and i1Pro 2 spectrophotometer are 45° / 0° instrument
with a circular illumination at 45 degrees incidence and measurement at 0 degree (i.e. on the sample normal),
the RAL DESIGN values obtained with these instruments will not be accurate for glossy samples. The reason is
that, for glossy samples, the reflection coefficients are slightly higher with a d / 8° instrument compared to the
values measured with a 45° / 0° instrument. However, good measurement correlation can be obtained with
semi-gloss and matte samples.
Important: You should make sure that the file data represents reflectance measurements. The reflectance
values shall be defined between zero and one, with one representing full (100%) reflectance or between 0 and
100.
A plain text file can easily be created with a word processor or a spreadsheet application, as shown below.
When saving the file, do not use the often complex native application file formats (for ex.: *.xls); instead, select
a tab-delimited or Comma-Separated-Value (CSV) text format.
INTRODUCTION
The Whiteness tools window is opened either by clicking on the corresponding icon on the toolbar window, or
by selecting the "Tools/Whiteness" menu.
Important: To use these tools, you need to have an i1Pro series spectrophotometer connected to the
computer on which CT&A is running. The instrument must also be properly recognized by the program; this is
confirmed by a small green light beside the instrument selection menu in the toolbar window, and by the
"Calibrate"and data entry buttons of the Whiteness window being enabled (some data entry buttons and
controls will remain disabled and some data fields will not be available (shown as "N.A.") if the program is not
activated). If you plug an instrument in your computer after the program start, you can attempt to connect the
instrument by selecting "Try to connect again..." in the Instrument menu. A status of the selected instrument
can always be obtained by clicking on the "Info" button located in the toolbar window.
Note: In Windows, if the i1Pro 2 USB drivers are not installed, please consult the "CT&A_Readme.txt" file
located within the main CT&A application folder. This file can be opened directly with the "Start
menu/BabelColor/CT&A Readme" shortcut.
Instrument button support: When the Whiteness tools window is selected, i.e. brought to the front, and
assuming that a compatible instrument is selected and recognized, a large blue indicator appears next to the
"Paper on Wh", "Paper w/filter", or "Paper on Bk" button. This indicator identifies the data that will be measured
if you press the instrument button; of course, you can also do a mouse click on any data entry button. The
indicator automatically changes location after making a measurement. You can click (left-click) on the indicator
to move it to the previous measurement if required, or do a right-click to lock it on a given measurement.
You can also do a left-click on a locked indicator; the new position will be locked.
The remainder of this section describes how to set up the interface and make measurements. For a description
of the standards and the Measurement Conditions, click here.
SETUP
• It is assumed that your instrument is properly connected and detected, as discussed in the introduction just
above.
• If you have an i1Pro 2 which supports the M0 and M2 measurement conditions, you can select to use either
an external UV filter or the internal filter associated to M2 measurements. When you select the "Use the M2
mode UV filter" radio button, the controls associated with the external filter are disabled, as shown below.
Note: Even if you use an i1Pro 2, the M2 mode UV filter radio button is enabled only when you select the
"i1Pro / i1Pro 2 (XRGA)" driver in the toolbar window.
Note: If you use an external UV filter, you should characterize it before measuring the paper properties. A
filter characterization procedure is presented later in this section. You can also load the filter relative
transmission spectrum from a file (file requirements).
• If not already done, calibrate the instrument by clicking on the "Calibrate" button and following the on-screen
instructions.
MEASUREMENTS
A typical measurement sequence goes as follow:
• Paper on white backing: Place the paper for which you want to determine the characteristics on the
white backing and press on the "Paper on Wh" button.
• Paper with filter on white backing: With the paper still on the white backing, place the UV filter between
the paper and the instrument and press on the "Paper w/filter" button.
Note: If you selected the "Use the M2 mode UV filter" radio button, the "Paper w/filter" button is removed
and this measurement is done automatically each time you do a "Paper on Wh" measurement.
• Paper on black backing: Remove the UV filter between the instrument and the paper. Place the paper
on the black backing and press on the "Paper on Bk" button.
To make a measurement, click on one of the buttons or press the instrument button. A large blue indicator is
located beside the input that will be selected if you press the instrument button:
This indicator automatically changes location when an input is done at one position; in fact you can do the
above measurement sequence simply by pressing the instrument button two or three times in a row. Do a left-
click on an indicator to move it to its previous position or a right-click to lock it (a locked indicator has a red
border: ). You can also do a left-click on a locked indicator; the new position will be locked.
To erase a measurement, first press the Alt key, in Windows, or the Option key on a Mac. Whenever the
mouse cursor is within the tool window, the "Paper on Wh", "Paper w/filter", and "Paper on Bk" buttons will
change their caption to "Clear" (if there is a measurement). To clear the sample, click the button with the
mouse while keeping the Alt or Option key pressed:
This is a paper whose whiteness and brightness comes from fluorescence due to paper additives called Optical
Whitening Agents (OWA), Fluorescent Whitening Agents (FWA), or Optical Brightening Agents (OBA). These
additives convert the invisible ultra-violet wavelength of the light source to blue light, which makes the paper
look whiter compared to the generally yellowish tint of standard paper fibers. We can see the reflectance going
almost up to 1,1 (or 110%) at 440 nm for the measurement on the white backing (red curve), while the same
paper measured with the UV filter (which cuts the UV) shows a maximum reflectance just over 90% at the
same wavelength (blue curve). The red and blue curves essentially are the same for wavelengths over 520 nm.
Precise numerical data can be obtained by moving the mouse over the graph; the wavelength at the location of
the mouse cursor and the corresponding spectral reflectance for all selected spectrums appears in the "Show"
group:
The fluorescence, which is the brightness difference between the measurement without the UV filter (=99,2)
and the measurement with the UV filter (=90,5), on the white backing, is almost 9 (99,2 - 90,5 = 8,7).
Important: Here are essential steps to take in order to insure more accurate and repeatable fluorescence
measurements. For a more detailed procedure, please consult the following Application Note: "AN-8 How to
optimize the accuracy of fluorescence measurements with BabelColor CT&A" available on the BabelColor
Tutorials Web page.
• If using an external filter, make sure you characterize it (characterization procedure) as presented further
down in this section. In the example above, we used a GamColor 1510 filter whose data we saved in a
file named "my filter" (Note: this filter data is also kept within the program's preferences and there is no
need to keep this file, even though we suggest you do so).
• Use the plastic positioning guide, provided for the i1Pro, or the positioning base, provided for the i1Pro2,
which are dedicated to spot measurements. This accessory insures proper spacing between the
instrument and the sample.
• Wait 20 to 30 seconds between each measurement and after calibration. This delay provides time for the
instrument to stabilize.
• Repeat the full measurement sequence a few times, always saving the results. You will be better able to
reject a measurement sequence which contains marginal data (usually the "Paper w/filter" measurement
made with an external filter).
In this second example we took fluorescence measurements of the same paper using an i1Pro 2 with an
external filter, shown in the first screenshot below, then using the internal UV filter of the i1Pro 2 M2 mode,
shown in the second screenshot. The paper is from a glossy magazine; it is not as bright as the paper used for
the first example but does exhibit fluorescence.
Note: In our experience, the fluorescence measured with an external filter can match well within 15% the
fluorescence measured using the M2 mode filter.
Hint: Because a measurement made with a non-UV-cut instrument plus a separate UV-cut filter is equivalent to
making measurements with an instrument fitted with a permanent UV-cut filter, you can use the Whiteness
tools to rapidly make measurements with and without UV-cut. Such measurements can also be done on
colored patches, and are thus not limited to white paper, although you should only look at the L*a*b* values in
this case, and disregard the Whiteness, Brightness, etc. values. For measurements without a UV-cut filter, you
have to use the "Paper on Wh" button, and for UV-cut measurements you need to place the UV filter between
the instrument and the color patch, and press the "Paper w/filter" button.
The message contains a short assessment of the measurement; the text is red when the backing is not
compliant, and black when compliant. You can see the backings' spectrum by selecting the corresponding
check box in the "Show" group. You can also export the backings' spectrums and get the measured reflectance
vs requirements values at the eight control wavelengths for the white backing by clicking on the "Save to file"
button (located in the bottom of the Whiteness window).
In addition to the Chroma and reflectance requirements, the white backing shall not be fluorescent; this is
particularly important when using this backing to characterize a UV filter. Here are three methods to check for
white backing fluorescence:
1. Visual spectral check: Place the instrument directly on the backing and click on the "Paper on Wh"
button. Look for a bump in the spectrum in the blue region between 420 nm and 460 nm. In particular, if
the spectral reflectance exceeds 1,0 (100%) at one wavelength, then you know for sure this backing is
fluorescent.
2. Measured with an external UV filter: This method can be used to characterize an unknown backing
and assumes that the UV filter characteristics were obtained with measurements on another non-
fluorescent backing (Note: When properly characterized, you will never measure backing fluorescence
on the same backing used to characterize the UV filter, even if this backing is fluorescent, and even if
you can see a characteristic spectral bump). To measure a backing fluorescence, take the "Paper on
Wh" and "Paper w/filter" measurements directly on the backing, without paper. In other words, first
measure the backing by placing the instrument on the backing and press the "Paper on Wh" button, then
place the filter between the instrument and the backing and press the "Paper w/filter" button. A
fluorescent backing will result in a positive brightness difference, i.e fluorescence, in a similar manner as
fluorescence in paper.
3. Measured with the FluoCheck tools: This method requires that you use an i1Pro 2. Open the
FluoCheck tools window and measure the Fluorescence Index (FI) obtained when placing the
instrument on the backing. The FI will be zero if the backing is not fluorescent.
To our knowledge, a thin TAPPI T452 UV filter suitable for use under an i1Pro cannot be found off-the-shelf.
The filters we recommend are equivalent to those recommended in the ISO 13655 standard (Ref. 42) for UV-
cut and fluorescence measurements (Wratten 2B and the FujiFilm SC-41). All these filters have a sharper cut-
off slope than the filters required by the TAPPI T452 standard, and their 50% transmission point is at lower
wavelengths, i.e. more towards the violet. However their sharp cut-off effectively blocks the UV as efficiently.
You will find files with the transmission characteristics of these filters in the "UV-filters" folder located within the
main CT&A application folder. In Windows, this folder can be opened directly with the "Start menu/
BabelColor/UV-filters files" shortcut.
Important: In order to obtain more accurate measurements, we strongly recommend that you characterize
your own UV filter, even if you have a sheet of one of the filters for which we provide a transmission
characteristics file. We have noticed that the characteristics of sheet filters vary between batches and even
within a single sheet. We suggest that you draw a 10 mm diameter circle (about half an inch), with a felt pen,
on the filter sheet, identifying a zone that will be used to characterize the filter and make the measurements
afterwards.
Obtaining a filter transmission is a three steps procedure, with the first two requiring a measurement. Firstly,
you measure the reflectance of a reference substrate. Secondly, you measure the filter reflectance on this
substrate. Thirdly, the filter transmittance is derived, by the program, from the two measurements. Two
important requirements of the reference substrate are that it shall be opaque, and that it shall NOT be
fluorescent. The substrate does not need to be perfectly white, and it does not need to be highly reflective (a
light gray substrate could do), and it even does not need to be a compliant white backing. Still, a compliant
white backing is a perfect reference substrate since it has all the required characteristics (see the Checking
white and black backings compliance sub-section above for more information). Here is the procedure:
• Calibrate your instrument.
• Wait 30 seconds and measure the reference substrate, i.e. the white backing, by clicking the "Check Wh
back." button; a compliant white backing is not absolutely required as discussed above.
• Place the filter between the instrument and the reference substrate. Wait 30 seconds and click on the
"Get new UV filter" button. If successful, the new UV filter transmission data will be saved internally and
will be used as the reference thereafter.
Note: There is no need to save filter data to an external file since it is kept internally by the program. However,
you may want to save it separately for reference or comparison purposes. You can change the filter name by
clicking in the text box below the "Load" and "Save" buttons.
Important: There are uncertainties in all measurements. Since the filter transmission is derived from two
measurements, and since the transmission characteristics are applied to a third measurement, you may obtain,
at certain wavelengths, a spectral reflectance of the measured paper with filter ("Paper w/filter") which is higher
than the reflectance of the paper measured with no filter. The increase is typically between zero and two
percent, and does not affect the measured parameters by a significant amount.
Note: You can also load the filter relative transmission spectrum from a file which contains data provided by
a filter supplier or that you derived yourself (UV filter file requirements).
You should obtain two identical spectrums, the same L*a*b* coordinates, the same brightness without the filter
and with the filter, and zero fluorescence. This happens because the filter transmission is compensated when
using the "Paper w/filter" button. In practice, because there are uncertainties in the measurements, and
because the filter characteristics were determined with other measurements which were also imperfect, the
measured L*a*b* and brightness values will not be exactly equal, and the fluorescence will not be zero. Still, a
fluorescence lower than ± 0,5 is expected, i.e. between + 0,5 and -0,5. As we have indicated before, it is
particularly important to wait 30 seconds between each measurement in order to let the instrument stabilize.
Hint: Do not hesitate to redo the procedure if you are not satisfied. If the procedure fails, you can always reload
the default filter from a file provided with the program; this file is located in the "UV-filters" folder located within
the main CT&A application folder. In Windows, this folder can be opened directly with the "Start
menu/BabelColor/UV-filters files" shortcut.
INTERFACE FEATURES
To change the graph grids appearance, use your mouse right-click (or ctrl + click on a one-button Mac mouse)
and select an option.
Click on "Save to file..." to save a Whiteness report. The report has tab-delimited data that can be directly
imported in a spreadsheet program as well as many text editing applications (it is suggested to use a
monospace font, such as Courier, in order to facilitate formatting). The file is also CGATS compliant and can be
opened by many color-management software, including BabelColor's PatchTool and X-Rite/GretagMacbeth
MeasureTool.
This section presents a description of each Whiteness tool. It also describes the requirements for black and
white backings, and information on commercially available UV filters. For a presentation of the Whiteness tools'
interface, go to this section.
Many standards were developed over time and many are still in use. Because whiteness is not just desirable
for paper, similar standards have been developed for textiles, chemical powders and paper pulp. The main
differences between the standards are:
• the instrument measurement geometry;
• the light source used for the measurement;
• the illuminant and Standard Observer used for computation;
• the use or not of wavelength selective filters;
• the backing on which the paper is measured;
• and the equations!
We have selected the standards which correspond to the measurement geometry and light source of the i1Pro
and i1Pro 2, and which are relevant to the photographic and print fields.
Since backings are fundamental to reliable measurements, not only of white paper but also for colored targets,
we provide tools to check the compliance of white and black backings. As well, because the precise
characteristics of the UV filter must be used in the computations related to fluorescence, we provide a tool to
characterize your own filter.
Here is a description of the standards and measurement conditions used in each tool.
Of the three, the CIE-GANZ 82 is the most commonly used. Many more formulas and variants have been
defined over time. We have retained these three because they are either well known or, in the case of
CIELAB-HE 2007, could potentially provide better results. All these formulas are based on, or are compatible
with, the 45 deg./0 deg. illumination/viewing geometry of the i1Pro and i1Pro 2.
Note: The 45 deg./0 deg. illumination/viewing geometry is equivalent to the 0 deg./45 deg. geometry.
Whiteness is measured by placing the paper to be analysed on a compliant white backing; the exact
specifications are presented below in the BLACK AND WHITE BACKINGS sub-section.
The whiteness is expressed with a number relative to a perfect diffuser. The tint characterizes the shift from
neutrality, i.e. how much of a tint is perceived; a perfectly neutral white will have a zero tint. In practice,
perfectly diffusing and neutral papers are never seen. We do find neutral papers which are not perfect
The typical whiteness and tint ranges for which the CIE-GANZ 82 formula is valid are:
40 < Whiteness < (5Y - 280)
and
-3 < Tint < +3
where Y is the measured CIE Y (the luminance, the Y of XYZ). Higher whiteness values correspond to whiter
samples. Positive values of Tint indicate a greenish tint, while negative values of Tint indicate a reddish tint;
the tint is stronger as the absolute value increases. A perfect diffuse reflector will result in a Whiteness = 100
and a Tint = 0. A message is shown in the Whiteness tools window when the Whiteness or Tint are out-of-
range.
These formulas are not linear, and equal differences in Whiteness or Tint may not represent equal perceptual
differences. Also, the upper-limit for the validity of the whiteness range is a hard stop; any sample exceeding
this limit is not considered white, and because of the way the limit is formulated (= 5Y - 280), lower-luminance
samples (i.e. samples of lower Y values) are valid in smaller ranges than higher luminance samples. These
drawbacks are the reasons why the CIE-Uchida equations were developed.
The CIE-Uchida equations are similar in structure to the CIE-GANZ 82 equations but the whiteness and tint
numbers are not the same. Compensation factors are added to the equation parameters, for better linearity
between the numbers and the perceptual differences, and the whiteness is no longer limited by an upper
range (the lower range is still 40 whiteness units according to the CIE-GANZ 82 formula). In practice, the
Whiteness and Tint obtained with the CIE-Uchida formula are close to the CIE-GANZ 82 numbers when the
whiteness is within the limits of CIE-GANZ 82, but differ when the upper limit is exceeded. In fact, the CIE-
Uchida numbers are valid when the upper whiteness limit of CIE-GANZ 82 is exceeded while the CIE-GANZ
82 numbers should be rejected. In addition, there is no limits proposed by Uchida for the tint; accordingly, we
do not test if the measurement is within tint limits when this formula is selected.
The CIELAB-HE 2007 formula takes the same approach as the CIE-Uchida formula to improve the linearity
and extend the whiteness range, but the goal was to improve it even more by selecting the visually uniform
L*a*b* space instead of the XYZ space. Such an approach was looked at previously by Ganz (Ref. 39), but it
lacked the extended range and uniformity that the Uchida formula provides. The CIELAB-HE 2007 was
judged to be well correlated with visual estimation, and the formula's authors concluded that it does
significantly improve the visual uniformity compared to the CIE-GANZ 82 and CIE-Uchida formulas (and other
formulas as well). You will note that the Whiteness and Tint values obtained with this formula are quite
different from the values obtained with the two other formulas (more generally, you cannot directly compare
the numbers between formulas).
• The brightness scale is based on the reflectance of magnesium oxide, which defines a brightness of 100,0;
other reference diffusers are accepted if characterized relative to magnesium oxide.
• Other requirements: The measurement is done essentially in
the blue part of the spectrum, in a band centered around 460
nm. In the context of this standard, Brightness is associated
with blue reflectance. The effective wavelength of 457 nm, used
in the brightness standard title, is obtained by the combination
of illuminant, glass optics, filters, and photodetector for which
the mathematical product of relative spectral power distribution,
spectral transmittance, and spectral response is shown (in %) in
the following graph.
Important: There are sufficient differences between an i1Pro and an instrument designed expressly for the
requirements of TAPPI T452 or ASTM D985 that you should not expect to match the results obtained with
qualified equipment. However, the instrument geometry is close, the lamp source is of the required type, the
blue wavelength band is simulated in software, and the reference white can be derived from the i1Pro
reflectance calibration.
Note: ISO 2470 is a standard often referred to for brightness assessment. While it is also dedicated to the
measurement of blue reflectance (ISO brightness), it requires a Diffuse illumination/0 deg. viewing
geometry instrument which is so different from the 45 deg. illumination/0 deg. viewing geometry of the
i1Pro, that any comparison between the numbers obtained with each standard is not recommended.
The measurement is done by placing the paper on a white backing. The brightness can be measured with or
without a UV-blocking filter; the difference between the computed brightness is a measure of the paper
fluorescence. This is discussed in the Fluorescence sub-section below.
Brightness values over 100 are common. This feat is possible by the use of additives, called Optical
Whitening Agents (OWA), Fluorescent Whitening Agents (FWA), or Optical Brightening Agents (OBA), which
increase the reflection coefficient and improve the neutrality of typically yellowish paper fibers. The increase
in brightness comes from a fluorescence effect; in such an effect, Ultra-Violet (UV) light is absorbed by the
additives and transformed into visible light, typically in the blue wavelengths range. The transformation of
invisible light into visible light improves the brightness while the added blue compensates for the intrinsic
yellowish color to make the paper look more neutral; this is the principle behind adding blue dyes in washing
detergents.
If we compare the spectral distribution with a filter with the one without a filter, presented above in the
Brightness sub-section, we obtain the ideal TAPPI T452 filter transmission, where T = 100 * (F(λ) / E(λ)),
where the maximum transmission is normalized to 100:
wavelength filter T (%)
380 nm 0
400 nm 4
420 nm 22
440 nm 45
460 nm 71
480 nm 90
500 nm 100
The fluorescence is obtained by the brightness difference without and with the UV-blocking filter:
Fluorescence = Brightnesswithout a filter - Brightnessw/filter
While fluorescence can brighten and whiten a paper appearance, the effect is affected by the UV content of
the light source, with halogen lights having much less UV than outdoor daylight. This means that when you
make an ICC profile of a paper which exhibits strong fluorescence, the colors will change depending on the
lights under which the print is seen. Because of this, many printers and photographers favor papers which
exhibit low fluorescence, or even no fluorescence at all.
Another drawback of fluorescent papers is that the additives lose their properties with time and exposure to
light. So even if the print is calibrated properly for viewing under a specific light source, the colors will change
with time.
Note: To our knowledge, a thin TAPPI T452 UV filter suitable for use under an i1Pro cannot be found off-the-
shelf. The filter we recommend, as well as the many equivalents mentioned in the UV FILTER sub-section
below, are available off-the-shelf, and are equivalent to those recommended in the ISO 13655 standard (Ref.
42) for UV-cut and fluorescence measurements. They have a sharp cut-off transmission curve which
effectively blocks the UV as efficiently.
Important: Because the suggested UV filters have transmission characteristics which are not those required
by the standards, you should not expect to reproduce the results obtained with the prescribed filter. However,
you will be able to reliably detect papers which are fluorescent and be able to grade their susceptibility to
fluorescence.
• Opacity
• Standards: Defined in CGATS.5 and ISO 2471
• Instrument geometry: 0 deg./45 deg. or 45 deg./0 deg.
• D50, 2 degree Observer
The opacity is obtained by first measuring the paper on the white backing and then on the black backing. The
opacity is defined by the ratio of CIE Y (the Y of XYZ) on the black backing divided by CIE Y on the white
backing:
Opacity (%) = 100 * (Yblack / Ywhite)
For ISO 13655, a sample is considered opaque if its opacity is not less than 99%.
Note: One difference between CGATS.5 and ISO 2471 is that ISO 2471 calls for self-backing instead of a
white backing. Self-backing, a backing made of a thick pile of the same paper, is obtained when you place
under the paper sheet to be measured as many additional unprinted sheets as are necessary to ensure that
no further change in measurement are seen when more are added.
You can check the backing fluorescence in the same way that you would check paper fluorescence. Please
see the Whiteness tools section for more information on the tools provided to check a white backing
compliance (Chroma, reflectance, fluorescence).
Please see the Whiteness tools section for more information on the tools provided to check a black backing
compliance (optical density, density range).
The least we can say is that the situation is not black or white!. Because the backing used for measurement
can have an impact on the resulting data, especially if the opacity is on the low side, it is recommended to use
the same backing for measurements and visual assessment. There used to be a preference for black backings,
mainly because of ISO 5-4, but many now favor the white backing, because it is closer to self-backing, while
being more stable. Self-backing is a backing made of a thick pile of the same paper, an approximation of what
you find in books and magazines (with not too much ink per page though!).
The purpose of this filter is to cut the Ultra-Violet (UV) from the instrument lamp, so that no fluorescence is
generated. This is equivalent to an i1Pro or i1Pro 2 with a UV-cut filter; however, because the Whiteness tools
also require measurements with an instrument which has NO UV-cut filter, a UV-cut i1Pro is not recommended
for these tools.
Hint: Because a measurement made with a non-UV-cut instrument plus a separate UV-cut filter is equivalent to
making measurements with an instrument fitted with a permanent UV-cut filter, you can use the Whiteness
tools to rapidly make measurements with and without UV-cut. Such measurements can also be done on
colored patches, and are thus not limited to white paper, although you should only look at the L*a*b* values in
this case, and disregard the Whiteness, Brightness, etc. values. For measurements without a UV-cut filter, you
have to use the "Paper on Wh" button, and for UV-cut measurements you need to place the UV filter between
the instrument and the color patch, and press the "Paper w/filter" button.
As we mentioned previously in this section while describing the Fluorescence measurement, the TAPPI T452
UV filter cannot easily be found off-the-shelf. However, we have found two very similar types of plastic sheets
designed to remove UV emissions from lamps (particularly fluorescent lamps) which effectively block UV
wavelengths. The default values used in the program are those of the GamColor 1510; a very similar filter,
Rosco 3114, can also be used. For purchasing information, please consult these web sites:
• GamColor 1510
https://us.rosco.com/en/products/catalog/gamcolor
• Rosco 3114
https://www.rosco.com
According to the ISO 13655 standard, other equivalent filters are the Wratten 2B and the FujiFilm SC-41. All
these filters have a sharper cut-off slope than the filters required by the TAPPI T452 standard, and their 50%
transmission point is at lower wavelengths, i.e. more towards the violet. However their sharp cut-off effectively
blocks the UV as efficiently. You will find files with the transmission characteristics of these filters in the "UV-
filters" folder located within the main CT&A application folder. In Windows, this folder can be opened directly
with the "Start menu/BabelColor CT&A 6/CT&A UV-filters" shortcut.
When you do a measurement with the filter between the instrument and the paper, not only is the UV radiation
prevented from hitting the paper, but the visible radiation (i.e. the white light from the instrument lamp) is also
affected by the filter. In other words, this filter is not perfectly transparent and has a typical transmission of 90%
in the visible. In fact, the filter transmission affects the instrument light twice, once as the light goes from the
instrument to the paper, and another time when, reflected by the paper, it goes back in the instrument. We thus
need to compensate any absorption by the filter in the visible range, as if it was perfectly transparent. This is
why the filter characteristics, its transmission, is absolutely required by the program, and why we provide
default values as well as a method to re-generate the transmission characteristics with your own filter.
Important: We have noticed that the characteristics of sheet filters vary between batches and even within a
single sheet. In order to obtain more accurate measurements, we strongly recommend that you characterize
your own UV filter, even if you have a sheet of one of the filters for which we provide a transmission
characteristics file.
Important: You should make sure that the file data represents relative transmittance measurements. The
transmittance values shall be defined between zero and one, with one representing full (100%) transmittance.
Although such a file can be opened by other software, such as BabelColor PatchTool, it cannot be interpreted
or used as reflectance data.
A plain text file can easily be created with a word processor or a spreadsheet application, as shown below.
When saving the file, do not use the often complex native application file formats (for ex.: *.xls); instead, select
a tab-delimited or Comma-Separated-Value (CSV) text format.
Although the "Definitions and theory" section is not required reading in order to be able to use the program, it
contains a lot of information about RGB spaces and the mathematics of colorimetry. For more information on
colorimetry, the reader can consult our References.
From the input, in green, multiple conversions are performed to obtain the various displayed outputs, in light
blue; the results of the steps with a white background are not displayed but used internally. If in Convert mode,
the input for the other side, which can be either a Space or a Deck, is XYZ data; it is shown in yellow.
Color data within this tool is of two types: integer and real, i.e. with fractional precision. R'G'B' data is most
often seen and used in integer form since this is how it is saved in images; however, nothing prevents
someone of using real values for increased accuracy, especially when converting to higher bit number
representations, such as 16 bit. Hex # data is, by definition, integer based while HSB data is rarely, if ever,
seen in non-integer form. The xyY, XYZ, L*a*b*, L*u*v*, and L*C*h color data representations can have
fractional values and usually benefit greatly from the added precision.
Integer input is in effect when using either the R', G' or B' sliders, or their corresponding data displays boxes.
However, fractional input values for R'G'B' will happen when using the "Y" slider or "xy" mouse input; this is
required in order to provide accurate and consistent results with these input controls.
Please note that all R'G'B' inputs will be rounded after one of the following actions, and when R'G'B' is the input
mode after the change:
• a mode change (Compare to Convert, Convert to Compare, a direction change in Convert),
• an input mode change (L*a*b* / L*u*v* input to R'G'B' input),
• a different RGB space is selected,
If the input mode before and after the change is L*a*b* or L*u*v*, there is no rounding of the input variables.
When converting a color into a RGB space, i.e. in Convert mode, the converted coordinates are high precision,
non-integer, fractional numbers. The R'G'B' values, thus also Hex # and HSB, are rounded to the nearest
integer for display purposes but the other color spaces data correspond to the fractional R'G'B' values. This is
why the color-difference, DeltaE*, when there is no clipping, is exactly zero. When going back to Compare
mode, a small color difference value may appear in the DeltaE* display. What happens is that the space which
was converted "TO" is now independent and in R'G'B' input mode. To be consistent with the integer logic of
R'G'B', the software replaces the fractional R'G'B' values, which were previously rounded for display only, by
their nearest integers, and re-computes all other color data.
This process logic was defined to maintain accuracy for users interested in color conversions not related to
RGB spaces, while not affecting the integer conversion accuracy for users interested in RGB spaces
computations.
The CIE1931 representation was determined from color patches covering a two degrees Field Of View (FOV).
This FOV is well within the angle subtended by the eye's fovea, the region of the retina near the eye's optical
axis where the density of cones is the highest. Cone density falls rapidly to less than ten times the peak value
at plus or minus five degrees from the fovea's center (Ref. 15) and, in practice, color patches subtending FOVs
between one and four degrees can be treated using the CIE1931 data. For larger patches it was found that the
eye has a somewhat different response. This resulted in a new set of measurements, called the CIE1964 data
set, which was done for patches subtending a FOV of ten degrees. Data corresponding to the CIE1964 data
set is often presented as (X10, Y10, Z10) or (x10, y10, Y10) to distinguish it from the 1931 system.
Since most images are made of combinations of small color patches subtending small angles, the CIE1931
system remains a valid choice for many practical applications. In particular, it is the one used to define all RGB
spaces. There is also no need to convert all legacy CIE1931 standards since, in most instances, the users just
want to match a specification, and as long as that specification can be measured, there is no reason to change
it! On the other hand, it can be seen that the 10 degree Observer is specified more often in recent standards,
such as RAL DESIGN and ISO 3664.
For reflected light, the reflectance is measured for each wavelength band and a ratio is computed relative to a
perfect white diffuser. For transmitted light, a ratio is computed relative to a perfect transmitter. In the case of
self-luminous sources, a radiance factor, the ratio between actual output and maximum output, may be
determined.
Then, for each wavelength band, the reflectance, transmittance, or radiance factor is multiplied by the source
SPD and by the spectral tristimulus value of each color-matching function. Results are then added separately
for each function. In other words, the reflected or transmitted spectrum is weighted by the color-matching
functions and integrated to provide a single value, a scalar, also called the tristimulus value, for each function.
The scalar obtained with the red color-matching function is named X. Similarly, the scalars obtained with the
green and blue functions are Y and Z.
The green color-matching function has an interesting characteristic. It was defined in such a way that it
matches the overall Luminance response of the human eye (X and Z have no such easily attributed
correspondence to a physiological phenomenon). All values represented by Y are therefore, by design,
2
photometric quantities (lux, cd/m , etc.). Also, by definition, the color coordinates of the illuminant, the brightest
color, are, when normalized, the ones for which Y equals 100 (i.e. maximum Y is 100 even if X or Z can be
higher).
An excellent source of data, presented in tabular forms, on the SPD of all standard illuminants, such as C, D50,
D65, F6 etc., and for the color-matching functions, is ASTM Standard E308-99 (Ref. 16) which describes a
complete procedure to calculate XYZ with custom illuminants as well as a simplified procedure that can be
used with standard sources.
In the xyz representation, because of the redundancy of the fourth equation above, only two coordinates are
required, usually x and y, to convey the chromatic content of a sample. The representation of color is thus
simplified from 3 dimensions to 2 dimensions. However, the absolute luminance information of Y is lost in the
process. For these reasons, it is a common practice to present color data as xyY.
When the pure monochromatic colors of the spectrum are plotted in the "xy" plane, they form a line, the
spectral locus, which has the shape of a horseshoe, officially named the CIE1931 chromaticity diagram (labels
identify the positions of many specific wavelengths):
The straight line at the base of the horseshoe represents the mixture of red and blue light, two colors at the
opposite of the spectrum. All other "impure", or non-monochromatic, or less saturated colors fall within the
horseshoe. Only the colors inscribed within the horseshoe are possible. The colors outside the horseshoe are
"imaginary" and result from the mathematical treatment behind the color-matching functions. The horse shoe is
inscribed in a larger triangle, defined by the (x,y) = (0,0), (1,0), and (0,1) coordinates, which is called the
Maxwell triangle, from the name of the Scottish physicist, James Clerk Maxwell (1831-1879), who used a
The more one goes away from the edges of the horseshoe, the more the color is de-saturated. The ideal white,
also called the equal energy illuminant since all three reference functions are equal, has x, y and z equal to
0,33333… and is located somewhere in the center of the horseshoe. It is interesting to note that the ideal black
is located at the same spot. This seemingly contradictory result is simply because the diagram does not
represent intensity, thus its name chromaticity diagram, and the importance of the Y information in comparing
measured color data.
A very useful feature of this diagram is that it can be used to determine the color resulting from the mix of two
known emissive colors. The chromaticity of a color resulting from the mixture of two colored lights will simply be
located on the straight line between the two. This is one of the characteristics of additive color mixture, also
called Grassmann's laws. Adjusting the ratio between the two lights will make the resulting color move along
the line. An interesting consequence is that mixing two colors located at such positions on the chromaticity
diagram that a line between them goes through the white point region will result in "white" being perceived for
certain ratios. This last example is just to contradict the often-heard statement that you need at least three
colors to generate white, and is a direct consequence of the overlapping bandwidths of the cones.
We see that the triangle defined by the primaries is fully used for
low luminance colors only. As the luminance is increased, the
color range becomes smaller.
Note: One of this program features is that when you select a color by clicking on its chromaticity diagram (see
also "xy" mouse input), the selected color will always be the highest — i.e. brightest — possible color in the xyY
representation.
One of the challenges in color display design is to select the best primaries to generate the maximum number
of colors. Since it is impossible to generate all colors with three primaries, one can think of using four, five, or
more, different basic colors to define a multi-facet polygon that would encompass most of the horseshoe
shape. However, this is difficult in practice, firstly because of the limited availability of high-brightness long-life
monochromatic phosphors, for CRTs, or the manufacturing cost of high purity filters, for LCDs, and secondly
because of the complexity of controlling sources which are redundant for much of the gamut (many colors can
be created by more than one mix of the basic colors). In short, the technology required to achieve these goals
is not cost-effective and there has been few consumer level products so far (SHARP developed a 4-color LCD
TV technology, named "Quattron Technology", which is sold under the AQUOS brand, and where the addition
of yellow pixels is said to increase the color gamut by 10% and improve color gradation). Historically, the
phosphors of the first color TVs were selected in most part for the two following reasons: they were available,
and three phosphors are enough to get a very good job done.
Chromaticity data for the A, C, D50, D65, E and a user-defined illuminant can be found in the dialog which is
called with the "RGB vs RGB/Table data/Illuminant data..." menu or with the "Illuminant data..." menu of the
toolbar "Tables" icon.
Bradford or CIECAT02 Chromatic Adaptation Transform (CAT) matrices used to convert XYZ data between two
of these illuminants or between one of those illuminants and a user-defined illuminant can be found in the
dialog which is called with the "RGB vs RGB/Table data/CAT matrices..." menu or with the "CAT matrices..."
menu of the toolbar "Tables" icon.
It is common to associate a temperature with an illuminant. This temperature is related to the emission of a
blackbody. A blackbody is by definition a material that has perfect emissivity and absorptivity at all
wavelengths; it will therefore not reflect or scatter light. The light emitted from the blackbody has a spectral
content with a dominant color that shifts from red to blue with increasing material temperature. Temperature is
expressed in the kelvin scale, with zero kelvin defined as the absolute zero (-273 Celsius). The perceived color
of a blackbody, its chromaticity coordinates, can easily be determined using the Custom illuminant dialog which
can be accessed from within the Custom RGB space dialog.
Few illuminants are perfect blackbodies. However, when a source matches the chromaticity of a blackbody, we
refer to the source temperature as the color temperature. If the chromaticity does not match, the blackbody
temperature that most closely matches the spectral properties of the illuminant is given; this temperature is
called the Correlated Color Temperature (CCT). These temperatures are identified with an asterisk in the table
above, as well as in the program's illuminant table data.
The illuminant referred as D65, with a correlated temperature of 6504 K, emits light with a spectrum close to
mid-day daylight illumination and can be considered a good "general use" white. D65 is part of the standard
CIE D-series illuminants which cover the 4000 K to 10000 K plus range where the number following the "D" is
an abbreviation of the correlated temperature—all D-series illuminant have chromaticities slightly different than
same temperature blackbodies.
D50, with a correlated 5000 K temperature, has a spectrum with a strong orange content, typical of tungsten
lights. D50 is the reference illuminant for the print industry and the only illuminant used to compute L*a*b* data
in Adobe Photoshop. D50 is also, presently, the only illuminant in the Profile Connection Space (PCS), a color
space used as the link between devices, in the International Color Consortium (ICC) profile definition (Ref. 17).
.
Like for the blackbodies, the chromaticity coordinates of the D-series illuminants can be obtained with the
Custom illuminant dialog.
For many years, one contender that has withstood critical revue is called the Bradford CAT, or BFD, from the
name of the city, in England, where the researchers who developed it came from. A simplified matrix
representation of the Bradford transform was found to give excellent results during the work performed in the
development of the sRGB standard (Ref. 8). In its simplified version, the only data required to derive a Bradford
matrix, in addition to the predefined Bradford cone response and inverse cone response matrices, are the XYZ
coordinates of the source and destination whites. The source white is the illuminant used to measure the
original data, and the destination white is the illuminant to which the data has to be translated.
Once derived, the Bradford conversion matrix is used in the following way:
where XYZsource is the data derived from the original illuminant, and XYZdestination is the data transformed in the
destination space illuminant.
More recently, another CAT, named CIECAT02, was developed for use with the CIECAM02 color appearance
model (Ref. 26-28). The CIECAT02 transform is a variant of the simplified Bradford CAT, where some non-
linear parameters are omitted, and which is further optimized in regards to many experimental data sets. Like
the simplified Bradford based CAT, a CIECAT02 based CAT is a 3x3 matrix, and it can be used in the same
way as the equation above.
CT&A can use a Bradford or a CIECAT02 CAT; the selection is done in the "Math" tab of the Preferences
dialog. The CAT matrices can be viewed in a dialog which is called with the "RGB vs RGB/Table data/CAT
matrices..." menu or with the "CAT matrices..." menu of the toolbar "Tables" icon.
Although it is clear that more accurate XYZ values are obtained when using spectral data combined with the
color-matching functions (see the Important note below), such spectral data is often not available; a CAT is
then the only choice. The average error obtained in Ref. 8 when converting Pantone color chips from D50 to
D65 using the Bradford transform was 1,4 ∆E*ab with a standard deviation of 0,9. A similar conversion study
from D65 to D50, done by the BabelColor Company with the 611 FED-STD-595 chips (of Rev-B), resulted in a
0,71 ∆E*ab average error with a 0,65 standard deviation. Not surprisingly, the fluorescent samples show larger
errors.
Note: In older versions of CT&A, before Version 4.x, CIECAT02 was used only to compute the Color
Inconstancy Index (CII) in the Metamerism Index tools, and all other chromatic adaptations were done with a
Bradford CAT. Starting with CT&A Version 4.x, the CAT can be selected and CIECAT02 is the default.
However, CIECAT02 remains the recommended CAT when computing the CII.
Important: A chromatic adaptation transform gives us the coordinates of a color as seen under another
illuminant; however, being based on tristimulus data, it cannot take into consideration the spectral content of a
light source interacting with the spectral content of a sample measured in reflectance. In practice, such
interactions do take place and the perceived color of a sample is often different when viewed under two light
sources. The CAT computed color is the exact match for the color seen under the first illuminant, and the color
computed with the spectral data is the color actually perceived; the difference is defined as color inconstancy,
an effect measured with the MI tools.
After this operation, the RGB coordinates of the illuminant are (100, 100, 100) when normalized XYZ data with
Y equal to 100 is used. Results over 100 or below zero are clipped at 100 and zero respectively.
By the combined use of the RGB to XYZ and XYZ to RGB matrices, we can transform RGB data from one
RGB space to another. If the illuminant is not the same for both spaces, we apply a Chromatic Adaptation
Transform (CAT), Bradford or CIECAT02, in mid process. The RGB space-to-space conversion procedure is
represented by the equation:
The computation sequence is performed from right to left. If the illuminant is the same, the CAT transform
(Bradford shown in the equation) is simply omitted. It is important to mention that converting from one space to
another is often done in conjunction with an additional step, called gamut mapping, which is not represented in
the preceding equation. Gamut mapping algorithms attempt to minimize the effects of clipping by distorting the
values of either or both the clipped and non-clipped colors. Variants of the process, still a subject of active
research (Ref. 19), have been devised for different requirements such as maintaining saturated colors in
business graphics or achieving a balanced "realistic" look in pictures, even if none of the resulting colors are
accurate.
Important: When converting colors to other spaces, the software adapts the new coordinates to the destination
space illuminant by using a CAT. Colors which fall outside the new space are clipped to the nearest color. This
is the method used when converting color profiles with "Relative Colorimetric" intent in Photoshop and other
graphic editing programs that use this terminology.
Important: Many RGB to RGB conversion matrices found in the literature are simply the RGB to XYZ and XYZ
to RGB matrices shown above, combined into one, as per ASTM RP 177-93 (also Ref. 18), with no CAT matrix
or gamut mapping.
GAMMA
The eye is more sensitive to variations of luminance in low luminance levels than similar variations in high
luminance levels. Compared to RGB, which is scaled linearly in luminance, R'G'B' values are scaled according
to this non-linear perception of the eye, and more data triads are assigned to the lower luminance levels. As a
result, the R'G'B' scale is close to a perceptively linear scale where doubling the values of a triad will result in a
color whose brightness appears doubled.
The conversion equations shown here describe how two "flavors" of gamma are used to encode data from
RGB to R'G'B' and vice-versa. This is just one aspect of gamma, the software-encoding gamma, amongst the
other gamma parameters that define a complete vision chain.
For more information on the elements of a vision chain, see Ref. 9, Ref. 10, and Ref. 11.
For a detailed presentation on colorimetry and how images are perceived, see Ref. 5.
Important: All computer programs which display R'G'B' data, in color pickers for example, present R'G'B' data
as R, G or B, or RGB, without the prime symbol after the letter. These programs never display linear RGB
values as obtained in converting from XYZ to RGB. Still, this is an "industry standard" representation, and this
is how this program user interface is done. However, in CT&A's documentation, the correct R', G', and B', or
R'G'B' form is used to minimize any confusion in the transformation equations.
Important: You should always verify how gamma is defined before making comparisons with other sources of
information, and you should get used to the fact that any author's gamma value could be the reciprocal (= 1/x)
of another author's definition.
The detailed gamma function is (for simplicity, only R' is shown; G' and B' are similar; R, G, and B are
normalized between zero and one prior to this operation):
The function is defined by two segments: a linear segment at low light levels, below the defined transition level,
which makes the transform less susceptible to noise around zero luminance, and a power segment with a γ
(gamma) exponent. The effect of that exponent is to compress the luminance signal by assigning a larger
signal range to dim colors, where the eye is most sensitive, and a small signal range to bright colors.
The offset is related to what is generally identified in TVs and monitors as the black level, intensity or
brightness control knob. The combination of (1 + offset) is related to the picture, gain or contrast knob. It may
sound surprising to associate brightness to a DC level and contrast to a term which controls the maximum
luminance level, but these terms were defined in relation to what is perceived, not the mathematical
expression. In effect, the eye perceives as a brightness increase a change in the black level more than it does
of a change in the gain.
The four parameters offset, gamma, transition, and slope collectively define the "detailed gamma."
The two above equations can be approximated by a simpler function of the form:
for 0 ≤ R ≤ 1 .
Here, a single parameter, the γ (gamma) exponent, with a value different than the gamma of the detailed
function, defines what we call the "simple encoding gamma," or "simple gamma" for short. Not all spaces are
defined with detailed gamma parameters, but all spaces have a simple gamma value assigned. The simple
gamma is generally used by all graphic editing programs while the detailed gamma provides more accurate
colorimetric transforms.
You can define and compare both simple and detailed gamma functions using the Custom RGB space dialog
which opens with the "RGB vs RGB/Define custom RGB..." menu or with the last menu item in a RGB vs RGB
window space selection menu.
Note: An average difference of 1.3 DeltaE*ab, with a 0.9 DeltaE*ab standard deviation, was measured when
using a simple gamma instead of a detailed one in random sRGB to L*a*b* conversions.
The detailed gamma equations are (R', G', and B' are normalized between zero and one prior to this operation):
for 0 ≤ R' ≤ 1 .
The conversion is not from one color space to another but simply a change in the numerical base of the R', G'
and B' numbers. Instead of being written in standard decimal way (base 10), a base 16 (hexadecimal) is used.
Here is the decimal to hexadecimal conversion table:
For example, the R'G'B' =(255, 0, 16) triad is written as #FF0010, where "FF" is the hexadecimal equivalent of
255 (= (15 x 16) + 15), "00" is zero, and "10" hexadecimal is 16 (= (1 x 16) + 0).
The numbers are presented side by side, with no separating spaces, in the traditional R'G'B' sequence:
#redgreenblue. By convention, a number (#) sign precedes the hexadecimal color. This representation has the
advantage that a single, fixed size, string of six characters can represent all colors.
To view this representation, select Hex # in the Hex # / HSB / xyY / XYZ display.
Hue is a value between zero and 360, in reference with the degrees of a circle where zero degrees is "pure"
red, 120 degrees is "pure" green, and 240 degrees is "pure" blue. By "pure", we mean the maximum purity that
can be obtained with an R'G'B' triad (Ex.: maximum red is R'G'B' = (255, 0, 0)). A simplified representation of
the color variation with the angle is shown below (Note: the actual 3D shape of the HSB space is a six-sided
cone, a hexcone):
The intent of HSB is good, but it has drawbacks. Firstly, its use is not standardized; there are many variants,
such as HSL (Hue-Saturation-Lightness), or HSV (Hue-Saturation-Value). The equations to derive these
representations are similar, but not identical, and you will find various scales for each parameter.
Secondly, the conversion equations are not continuous, which does not make them mathematically, or
computer, "friendly" (and fast!).
More importantly, because of the way it is derived, the HSB representation is NOT a colorimetrically accurate
representation of color. The brightness parameter ("B") has no relation with the actual luminance (Y), or the
relative brightness (i.e. lightness, L*), of the color. In HSB, any hue can have a maximum "B" value of 100. As
illustrated in the xyY and XYZ section, the maximum luminance of an RGB space is a very non-uniform
function, where the maximum luminance is only achieved for pure white.
A more "scientifically correct" alternative is to use the chroma (C*ab) and hue angle (hab) of the L*a*b*
representation, or their equivalent in the L*u*v* representation, but they are not as intuitive. Another more
perceptually correct way of selecting colors is to use the Munsell Color System, which characterizes the
spectrum in uniformly perceived Hue, Value (an indicator of lightness), and Chroma (a counterpart of
saturation) steps. Still another "scientifically correct" way of picking colors is to use the color picker capabilities
of this program, as it is shown in Tutorial 4.
Nonetheless, when used for picking colors, HSB is a good alternative to R'G'B'.
Determine the maximum (MAX) and minimum (MIN) value of the rgb triad (both are values between zero and
one):
Finally, if H is negative:
Attempts to transform the original diagram into a more uniform representation have resulted, after much work
and discussions, in a relatively recent industry wide "agreement" on two standards, the L*a*b* representation,
called either CIE1976 (L*a*b*) or CIELAB, and the L*u*v* space, called either CIE1976 (L*u*v*) or CIELUV.
Since both spaces have their proponents and preferred applications, it is up to the users to select the most
appropriate model, at least until a better "universal" one is defined and accepted.
XYZ to L*a*b*
L*a*b* is derived from XYZ data with the following equations:
L* = 116 f y − 16 a* = 500 ( f x − f y ) b* = 200 ( f y − f z )
where
fx = 3 x x>ε
κ x + 16
fx = x≤ε
116
fy = 3 y y >ε
κ y + 16
fy = y≤ε
116
fz = 3 z z >ε
κ z + 16
fz = z ≤ε
116
with either
ε = 0.008856 and κ = 903.3
which are the values now in use by the CIE, or
Better uniformity is thus obtained with L*a*b* by normalizing the color coordinates with the illuminant
coordinates, and by applying a 1/3 exponent to the ratios, which corresponds to the non-linear perception, i.e.
dynamic range compression, of the eye subjected to increased luminance.
Increases in a* values represent increases mainly in redness, while decreases in a* values represent increases
mainly in greenness. Increases in b* values represent increases mainly in yellowness while decreases in b*
values represent increases mainly in blueness.
Note: In practice, selecting the "in use by the CIE" or "better continuity" ε and κ values will result in essentially
no difference relatively to the precision of 8 bit RGB data.
L*a*b* to XYZ
The XYZ coordinates are derived from L*a*b* data with the following equations, starting with y and fy:
X = xXn Y = yYn Z = zZn
where
x = f x3 f x3 > ε
x = (116 f x − 16 ) / κ f x3 ≤ ε
z = f z3 f z3 > ε
z = (116 f z − 16 ) / κ f z3 ≤ ε
and
a*
fx = + fy
500
L * +16
fy = y >ε
116
κ y + 16
fy = y≤ε
116
b*
fz = fy −
200
where Xn, Yn, and Zn are the illuminant coordinates, and ε and κ are defined as for XYZ to L*a*b*.
Attempts to transform the original diagram into a more uniform representation have resulted, after much work
and discussions, in a relatively recent industry wide "agreement" on two standards, the L*a*b* representation,
called either CIE1976 (L*a*b*) or CIELAB, and the L*u*v* space, called either CIE1976 (L*u*v*) or CIELUV.
Since both spaces have their proponents and preferred applications, it is up to the users to select the most
appropriate model, at least until a better "universal" one is defined and accepted.
XYZ to L*u*v*
L*u*v* is derived from XYZ data with the following equations. We start by computing u'n and v'n once (for a
given illuminant):
where Xn, Yn, and Zn are the illuminant coordinates. An equivalent set of equations using x and y is:
Then, for each data set, we calculate the intermediate variables u' and v':
The u' and v' coordinates are a projective transformation of the xy coordinates plane, and define a more
uniform chromaticity diagram called the Uniform Chromaticity Scale (UCS, CIE1976), which is often used as
a replacement to the CIE1931 xy chromaticity diagram. Straight lines in the xy chromaticity diagram remain
straight in the u'v' diagram.
u'v' chromaticity tolerances are specified in many Standards and Publications, such as ISO 12646, ISO 3664,
CIE 51 and CIE S 012 (click here for more information on these standards). The L*a*b* space does not have
such chromaticity units.
L* = 116 3 y − 16 y >ε
L* = κ y y≤ε
where
Y
y=
Yn
The exact name for L* is lightness, to indicate it is the relative brightness of a color patch when compared to
the brightness of a perfect "white" diffuser in the same illuminating conditions (or when compared to a "white"
patch, with R'G'B' =(255, 255, 255), if the patch is seen on a computer monitor). In effect, the actual brightness
can vary for a given lightness. The difference between u'v' and u*v* is that, as the equations show, the later
form takes into account the variation in perception due to lightness.
L*u*v* to XYZ
The XYZ coordinates are derived from L*u*v* data with the following equations. We start by computing u'n and
v'n once (for a given illuminant):
Then, for each data set, we calculate the intermediate variables u' and v':
where ε and κ are defined as for the XYZ to L*u*v* equations, and
The C* and h variables are shown in relation with L*, a* and b* in the following diagram:
It is important to note that the 3D shapes of the L*a*b* and L*C*h spaces, as well as the position of the data
within them, and the value of L*, are identical; it is simply that the data is represented using cylindrical
coordinates instead of three orthogonal axes.
Chroma can be considered an approximate counterpart of perceived color saturation. The higher the chroma,
the more monochromatic the color tends to be; the lower the chroma, the closer to neutral gray the color tends
to be. A hue angle of zero degree, equivalent to 360 degrees, is red-purple, using the Munsell description lingo,
or magenta-red, if you prefer using descriptions which are closer to the ones used in color printing. Increasing
the hue angle will make you go through red, orange, yellow, green, cyan, blue, and then back to red-purple
(magenta-red). This is very similar to what is seen when increasing the hue, going counter-clockwise, in the
HSB space and the Munsell Color System, although you will notice that these representations are not similar in
terms of the relative importance they allocate to each major hue.
These differences are shown in the DeltaE* interface window. See the CIELAB & CIELUV section for more
information on the difference between ∆H*ab and ∆hab.
Note: The three variables, L*, C*, and h define a space which has the same representation goal as the HSB
space, but is more colorimetrically correct.
One of the few methods left to convert data between the two color systems is interpolation. Traditionally done
manually by using tables and graphics, such as the ones contained in the ASTM D1535 standard (see Ref. 23),
it is now performed by computers. This task is facilitated by the inherent structure of the Munsell Book of
Color which presents samples with uniform Munsell Hue, Munsell Value, and Munsell Chroma (HVC) steps
between them. By measuring the XYZ characteristics of all these samples, we obtain two matching three-
dimensional tables, one with XYZ numbers and the other with HVC numbers, from which we can interpolate the
HVC coordinates of any XYZ sample, or the reverse. A simplified illustration of interpolation is shown below:
The goal is to find the unknown Munsell coordinates (HVC ?) corresponding to the measured XYZ sample. In
this simplified case, two nearest neighbors of the sample, XYZ-1 and XYZ-2, are found from a search within the
known XYZ database. The corresponding, and also known, Munsell coordinates in the HVC table are labeled
HVC-1 and HVC-2. The relative position of the XYZ sample between XYZ-1 and XYZ-2 is then used to deduce
the HVC coordinates of the sample. In practice, this process is performed in three dimensions and the search
routine looks for multiple neighbors located around the sample.
Alternately, the following equations can be used to determine Munsell Value from the CIE Y coordinate (from
Ref. 23):
For Y <= 0,9:
0,9967
Munsell Value = 0,87445 * Y .
Although it is quite an elaborate data fitting formula, implementing it in a conversion program is straightforward.
Alas, there are no similar equations for the other two parameters, hue and chroma, and interpolation is the only
solution.
Two particular problems arise from the interpolation method. The first one is that it is difficult to recognize true
neutral samples (ex: "N 2,3/") and most converters show a "nearest best candidate", which can be of any hue;
this condition is monitored and displayed correctly in CT&A. The second one is that the reference samples, the
ones used for interpolation, for a color located near the illuminant, can be located all around the illuminant. In
such a case, the interpolation routine must contain additional code to prevent large hue shifts; this is also
considered in this program.
Even though the Munsell Book of Color, the original presentation method of the Munsell Color System, contains
samples which cover a large part of the visible gamut, it is not exhaustive since it is impossible to reproduce on
printed or painted chips all the colors humans can perceive. This is the case for high chroma colors, like the
According to ASTM D1535 (again from Ref. 23), the estimated precision with which a color can be
characterized visually is 0,5 hue step, 0,1 value step and 0,4 chroma step.
Important: The data tables built for the Munsell Color System were derived using Illuminant "C". Since the
chromatic adaptation transforms (CAT matrix) do not take into account any potential color inconstancy effect,
the conversion errors for samples subject to this effect may be higher than what is normally expected for these
transforms (click here for typical values).
Note: They were other attempts at devising a formal uniform color system. The best known is the Optical
Society of America (OSA) Uniform Color Scales (UCS) project which development spanned on over three
decades. UCS development was ultimately "officially" abandoned; one of the reason being that it was still not
perfectly uniform, but it could well resurface as it provides an original view into color space and a different
approach in building color palettes (see Ref. 24).
By incorporating the fy terms and the constants in L*, we can simplify the above equations to:
Since y is the normalized luminance (=Y/Yn), and varies between zero and one. We can easily associate y to
linear RGB (i.e. before gamma correction), and assume that R,G, and B are also normalized between zero and
one (y = R/255). We can thus associate R'G'B' values to L*. Because the maximum value of the L* function is
100, we need to multiply the equation by 2,55 in order to obtain the proper R'G'B' maximums. The re-written
equations are:
(
L* = 2.55 (100 + 16) 3 y − 16 ) y > 0.008856
L* = 2.55 (903 .3 y ) y ≤ 0.008856
Now, let's look at the equation we use for the detailed gamma function (for simplicity, only R' is shown; G' and
B' are similar; R, G, and B are normalized between zero and one prior to this operation):
By comparing the equations of L* and R', we can see that they have the same structure or, in other words, that
they are the same equation. We can deduce that the L* offset is 16, that its gamma exponent (γ) is 1/3, and that
the slope is 903,3.
Finally, if we adjust the normalizing factor in the L* equations (=2,55) to the ones used in CT&A (=255), we get
these equivalent equations:
(
L* = 255 (1 + 0.16) 3 y − 0.16 ) y > 0.008856
L* = 255 (9.033 y ) y ≤ 0.008856
To derive a simple encoding gamma for L-star, we have traced the detailed gamma (R'G'B' vs RGB) and fitted
a curve with a single exponent equation; for comparison purposes, we have also traced the response of a
simple 2,2 gamma:
The best fit was obtained for a single exponent (γ) of 2,4346. We see that a simple gamma of 2,4346 provides
a better fit to L* than a generic 2,2 gamma. You will find these values in the Space data dialog. Here is a similar
graph that you can obtain with the "Gamma" tab of the Custom RGB space dialog:
Note: When we write that a simple gamma of 2,4346 provides a better fit to L* than a generic 2,2 gamma, this
does not automatically mean that it is better. It all depends of the end-use for the RGB space which uses L*,
and where this detailed gamma fits in the vision chain.
CT&A computes these differences according to many standards and variants. Although all are computed, only
one is displayed at a time (see DeltaE* interface). However, all are shown when saving or printing data in the
RGB vs RGB tool.
Click on the topic to see the definition and equations of each of the following color-differences:
• CIELAB, ∆E*ab in abridged form
• CIELUV, ∆E*uv in abridged form
• CIE94, ∆E*94 in abridged form
• CMC(l:c), ∆ECMC(:c) in abridged form
• CIEDE2000, ∆E00 in abridged form
There is no "best one" although some are better suited to specific applications. The Commission Internationale
de l'Éclairage (CIE) recommends CIELAB for large color differences (∆E*ab larger than 5). Up until recently,
CIE94 was often the preferred choice for small color differences but CIEDE2000 may displace it if usage
confirms the preliminary — positive — findings of early CIEDE2000 users. CMC will most frequently be used,
especially in the United Kingdom, in the context of the ink and textile industries where the (2:1) variant is found
to be well adapted.
DISCUSSION
An accepted "reference" is that a ∆E=1 corresponds to colors which are barely differentiable by 50% of a group
of observers; the other 50% would see no difference. This threshold is valid for all the color-difference formulas
described herein, even though an exact difference of one will not be obtained by all for the same conditions. As
well, when comparing very different colors, the color-differences obtained with the various formulas can also be
very different, an indication that the formulas are still not perfectly matched to how the human visual system
perceives color.
To place this error in perspective, we should take into consideration the conditions in which the colors will be
seen. One of these conditions is the observation time. According to a review article by Has & al. (Ref. 1), an
inexperienced user will take approximately 5 seconds, when comparing images, to notice a ∆E*ab difference of
15 from an original. The time goes up to 10 seconds for a ∆E*ab of 10, and 15 seconds for a ∆E*ab of 5. Another
study (Ref. 2) has shown that errors of less than 2.5 ∆E*ab are not visible on real world images shown on a
CRT. In essence, the threshold value of ∆E = 1 should be perceived only by prolonged comparative viewing in
a controlled environment.
On the hardware side, it has been shown (Ref. 3) that CRTs require a warm-up time varying between 15
minutes and three hours, depending on models, before achieving a long term stability of 0.15 ∆E*ab on average.
On a given CRT subjected to a large luminance variation, an initial ∆E*ab of 1.0 was seen to exponentially
decrease to about 0.1 ∆E*ab in 60 seconds. As for printed material, errors between 2 and 4 ∆E*ab are
mentioned by Has & al. (Ref. 1) for the offset and rotogravure processes.
,
where
.
k=1 for samples compared in close proximity (k=0,5 or less for samples compared further away from each
other, where the eye is less sensitive to lightness differences). A value of k=1 is used in this software.
An alternate color-difference equation for this space can be expressed in relation to the cylindrical coordinates
of lightness, chroma and hue (see the XYZ to L*a*b* section):
where
The relation between these variables can be seen in the following diagram:
Even though this equation is a workhouse of the plastic, paint and textile industries, its statistical threshold is a
cause of concern, and of possible litigation, in many industrial applications where expert observers' judgments
are confronted. For this reason, better color-difference equations are being sought.
CIELUV (∆E*uv)
Similarly, a color-difference equation is defined for the L*u*v* space (i.e. the "CIELUV color-difference
equation", DeltaE*uv or ∆E*uv in abridged form):
where
where
The main application fields for CIELUV have historically been the television and video display industries.
.
where C*ab ref is determined according to which of the two color patches is considered the Reference (or
Standard), and which one is considered the Sample (or Trial), a terminology borrowed from the Quality Control
(QC) field. The case where none of the patches is a Reference is also treated. This concept of assigning more
importance to one patch, which was not included in the CIELAB and CIELUV formulas, can result in quite
different results depending on the selected configuration. The value assigned to C*ab ref is:
In CT&A, you can select the reference mode in the "Math" tab of the Preferences dialog. The two options are:
• Reference at Left, Sample at Right
To be used when doing a Quality Control (QC) check. Here are the Reference and Sample for the
various tools:
• RGB vs RGB tool: In Compare mode, the LEFT side is the Reference and the RIGHT side is the
Sample. In Convert mode, the side being converted FROM is always the Reference, and the side
being converted TO, the Sample. This setting will also affect the selection of the L*C*h pad
patches.
• FluoCheck tools: For the FI, the Reference is M2 and the Sample either M0 or M1.
• Graph tools: The LEFT side is the Reference and the RIGHT side is the Sample.
• Metamerism Index tools: For the SMI, the Reference and Sample correspond to the button
labels. For the CII, the Reference is the data computed with the illuminant selected in the "CII ref.
illum." menu and the Sample is the data computed with one of the two illuminant menus on the
left of the window.
In most applications, kL=kC=kH=1. The textile industry often uses a variant where kL=2. Setting kL to 2 lowers the
contribution of lightness in the color-difference; in effect, for textiles, lightness differences can be twice the ones
of paint samples, where kL=1 would be used, for the same computed error. In some specialized applications,
such as when measuring a Color Inconstancy Index (CII), it is appropriate to emphasize the contribution of the
hue relative to the lightness and chroma; in this case, kL and kC can both be set to 2.
It is generally assumed that when no other indication is given, the kL, kC, and kH factors of the CIE94 formula
are all equal to 1 (i.e. CIE94(kL:kC) shown as CIE94(1:1) is CIE94; please note that kH is usually not shown as it
is almost always used with a value of 1). The ∆E*94-textile version, with its kL factor equal to 2, can also be
expressed as CIE94(2:1).
In this software, the kL=2 version is identified by CIE94-textile when it is computed relative to the space defined
illuminant, and CIE94-tex D50 when it is computed relative to the D50 illuminant.
CIE94 provides better data consistency and is considered by many a replacement for CIELAB for general
purpose color-difference assessment.
Important: As per its definition, the CIE94 color-difference will be different depending on which of the two color
samples is defined as the reference, or if none of the samples can be considered a reference. The software will
automatically adjust the formula according to the definition; as a result, variations in the color difference
numbers may be seen in the RGB vs RGB tool when going from Compare mode to Convert mode, or vice-
versa, or changing the direction of the conversion.
if L*ref ≥ 16
or
SL=0,511 if L*ref < 16.
Finally, the two control parameters, and c, are selected depending on the application. For perceptibility
measurements, when seeking minimal perception differences, and c should equal one. For acceptability
measurements, where pass or fail judgment is required, as in the ink and textile industries, should be set to 2.
Both versions, identified as CMC(1:1) and CMC(2:1), as well as versions computed relative to the D50
illuminant, can be selected in this software.
In CT&A, you can select the reference mode in the "Math" tab of the Preferences dialog. The two options are:
• Reference at Left, Sample at Right
To be used when doing a Quality Control (QC) check. Here are the Reference and Sample for the
various tools:
• RGB vs RGB tool: In Compare mode, the LEFT side is the Reference and the RIGHT side is the
Sample. In Convert mode, the side being converted FROM is always the Reference, and the side
being converted TO, the Sample. This setting will also affect the selection of the L*C*h pad
patches.
• FluoCheck tools: For the FI, the Reference is M2 and the Sample either M0 or M1.
• Graph tools: The LEFT side is the Reference and the RIGHT side is the Sample.
• Metamerism Index tools: For the SMI, the Reference and Sample correspond to the button
labels. For the CII, the Reference is the data computed with the illuminant selected in the "CII ref.
illum." menu and the Sample is the data computed with one of the two illuminant menus on the
left of the window.
Important: As per its definition, the CMC(:c) color-difference will be different depending on which of the two
color samples is defined as the reference, or if none of the samples can be considered a reference. The
software will automatically adjust the formula according to the definition; as a result, variations in the color
difference numbers may be seen in the RGB vs RGB tool when going from Compare mode to Convert mode,
or vice-versa, or changing the direction of the conversion.
Similarly to CIE94 and CMC(l:c), it includes weighting functions for lightness, chroma, and hue. Among the
differences, it proposes a scaling factor to a* for low chroma colors, to improve the formula performance near
the illuminant. It also comprises a factor, RT, called the rotation term, which is affected by the chroma and hue
differences, with the goal of improving the performance for blue colors (for hue angles around 275 degrees).
The formula is available in two forms. The original form has a fourth term associated to RT. The alternate form
has three terms, where the rotation term effect is integrated in the individual contributions of chroma and hue
differences. More information on the alternate form can be found in this document from the CIE Web site:
CIE R 1-39 Alternative Forms of the CIEDE2000 Colour-Difference Equation
https://files.cie.co.at/524.pdf
This section presents the equations for both forms of the formula.
The two formulas provide the same ∆E00 values and are identical relative to the lightness difference; however,
beside the disappearance of the rotation term, ∆C’ and ∆H’ are respectively replaced by ∆C’’ and ∆H’’, and
kCSC and kHSH are respectively replaced by S’’C and S’’H. The three terms formula can clearly be helpful if we
are interested in specifically minimizing the contributions of chroma or hue to the total error in a given process.
The equations required to derive the CIEDE2000 color difference with the four terms formula are presented in
the next page. The additional equations required for the three terms formula are presented in the last page of
this section.
𝐶′ = (𝑎′2 + 𝑏 ∗2 )1/2
∆𝐶 ′ = 𝐶 ′𝑆 − 𝐶′𝑅
where G is determined from (be careful not to confuse the C* (C-star) and C' (C-prime) variables):
∗
𝐶𝑎𝑎 = (𝑎∗2 + 𝑏 ∗2 )1/2
∗
(𝐶𝑎𝑎 ∗
∗ 𝑅 + 𝐶𝑎𝑎 𝑆 )
𝐶𝑎𝑎 𝑚𝑚𝑚𝑚 =
2
∗7 1⁄2
𝐶𝑎𝑎 𝑚𝑚𝑚𝑚
𝐺 = 0.5 − 0.5 � ∗7 � .
𝐶𝑎𝑎 𝑚𝑚𝑚𝑚 + 257
In order for ∆H' to be of the proper sign—you may recall that it is always positive in older formulas—you should
subtract 360 from ∆h', in the ∆H' formula, if it is larger than 180 degrees:
∆𝐻′ = 2(𝐶 ′ 𝑅 𝐶 ′𝑆 )1⁄2 𝑠𝑠𝑠((∆ℎ′ − 360°)⁄2) if ∆ℎ′ > 180°.
0.015(𝐿∗𝑚𝑚𝑚𝑚 − 50)2
𝑆𝐿 = 1 + .
(20 + (𝐿∗𝑚𝑚𝑚𝑚 − 50)2 )1/2
𝑆𝐶 = 1 + 0.045𝐶′𝑚𝑚𝑚𝑚 .
𝑇 = 1 − 0.17 cos(ℎ′𝑚𝑚𝑚𝑚 − 30°) + 0.24 cos(2ℎ′𝑚𝑚𝑚𝑚 ) + 0.32 cos(3ℎ′𝑚𝑚𝑚𝑚 + 6°) − 0.20 cos(4ℎ′𝑚𝑚𝑚𝑚 − 63°)
𝑆𝐻 = 1 + 0.015𝐶′𝑚𝑚𝑚𝑚 𝑇 .
2
ℎ′𝑚𝑚𝑚𝑚 − 275° + 360°
∆𝜃 = 30 𝑒𝑒𝑒 �− � � � if ℎ′𝑚𝑚𝑚𝑚 < 0;
25
1⁄2
𝐶′7𝑚𝑚𝑚𝑚
𝑅𝐶 = 2 � 7 �
𝐶′𝑚𝑚𝑚𝑚 + 257
𝑅𝑇 = − sin(2∆𝜃) 𝑅𝐶 .
The three control parameters, kL, kC and kH, are, simply enough, equal to one.
The above equations are all you need if you want to compute ∆E00 with the four terms formula. However, if you
are interested in the individual contributions of the lightness, chroma and hue differences, this is where the
additional equations of the three term formula become useful. These equations are shown in the next page.
The next step is to obtain an angle (φ) from the following equation:
(𝑘𝐶 𝑆𝐶 )(𝑘𝐻 𝑆𝐻 )
tan(2∅) = 𝑅𝑇 .
(𝑘𝐻 𝑆𝐻 )2 − (𝑘𝐶 𝑆𝐶 )2
Important: The φ angle is expressed in radians and not in degrees like we did with h’.
We then use φ to derive the remaining parameters of the three terms formula:
∆𝐶′′ = ∆𝐶′ cos(∅) + ∆𝐻′ sin(∅)
2(𝑘𝐻 𝑆𝐻 )
𝑆′′𝐶 = (𝑘𝐶 𝑆𝐶 ) � �
2(𝑘𝐻 𝑆𝐻 ) + 𝑅𝑇 (𝑘𝐶 𝑆𝐶 ) tan(∅)
2(𝑘𝐶 𝑆𝐶 )
𝑆′′𝐻 = (𝑘𝐻 𝑆𝐻 ) � �
2(𝑘𝐶 𝑆𝐶 ) + 𝑅𝑇 (𝑘𝐻 𝑆𝐻 ) tan(∅)
to finally obtain:
∆𝐿′ ∆𝐶′′ ∆𝐻′′
∆𝐿00 = ∆𝐶00 = ∆𝐻00 = .
𝑘𝐿 𝑆𝐿 𝑆′′𝐶 𝑆′′𝐻
Note: The CIE94/CMC reference mode setting in the "Math" tab of the Preferences dialog has no effect on
this formula.
Important: For the CIEDE2000 formula, the DeltaE* display of the RGB vs RGB tool shows the weigthed ∆L00,
∆C00, and ∆H00 values (and ∆h’), instead of the unweighted ∆L*, ∆C*, and ∆H* values (and ∆h).
ACES AP0 is an extremely large gamut RGB space which encompasses ALL visible colors. However, in order
to contain the visible spectrum, the blue primary must be defined with a negative “y” value (CIE 1931
chromaticity). This has the effect that many RGB triads correspond to negative “Y” (of XYZ) values and
negative L* (of L*a*b*) values. While colors with negative coordinates do not correspond to visible or “real”
colors, it is sometimes useful to keep the negative values when converting back and forth between RGB
spaces. Traditionally, negative “xyY” and “XYZ” values are clipped to zero when encountered and the
processing software must be specifically designed to handle these cases; starting with CT&A version 5.2 this is
properly handled with the RGB vs RGB tool and the Custom RGB space dialog.
Note: In order to get negative (i.e. non-clipped) XYZ values, you must first deselect the
Clip “xyY” and “XYZ” to zero in the “RGB vs RGB” tool
checkbox in the “Math” tab of the Preferences dialog.
Note: When referring to the ACES RGB space, the “AP0” suffix is used to identify the primaries which
encompass all visible colors. When you see the “AP1” suffix, this refers to a set of primaries more closely fitted
to the visible colors of the chromaticity diagram; if required, you can define the AP1 version using the Custom
RGB space dialog.
Warning: If you use instrument input in the RGB vs RGB tool with this space, please note that the contribution
of camera flare as defined in SMPTE ST 2065-1 section 4.1.1 is NOT included when computing the XYZ/L*a*b*
values. Similarly, camera flare is not taken into account when converting colors from another RGB space
towards ACES AP0.
The ACES AP0 Illuminant has a Correlated Color Temperature (CCT) of 6000 K (expressed as 6000 K *) and a
simple software-encoding gamma of 1 (i.e. a linear tone response).
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
When reproducing images encoded with this space, you will find that many colors cannot be reproduced with
the ubiquitous CMYK print process, particularly in the green portion of the gamut. Newer six-color or eight-color
printing presses offer the potential for a larger gamut but the extra channels of these presses are most often
used for spot colors and not for additional primaries. On the other hand, ink-jet printers with additional primaries
such as orange and green are more easily found and are commonly used in conjunction with this RGB space.
It is also possible to find wide gamut displays which can show all (or near all) the colors of this space.
A simple software-encoding gamma of 0,455 (=1/2,2 if you define gamma using the reciprocal value) is used in
CT&A. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
In its older OS versions, a Mac user could set the display gamma in a control panel. This display gamma
combined the LUT gamma and the CRT gamma; when a value of 1,8 was entered, the LUT was filled with
numbers corresponding to a exponential function (i.e. curve) with a gamma (i.e. exponent) of 1,8/2,6=0,69
(=1/1,45).
A simple software-encoding gamma of 0,556 (=1/1,8) is used in CT&A for Apple RGB. This gamma is the same
as the one defined for ColorMatch, Generic RGB, eciRGB 1.0, and ProPhoto. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
Here is a short history of Apple RGB and how it was dislodged as the default Mac RGB space. This history is
based on messages posted in the Apple ColorSync forum, where current or ex-insiders give their point of view,
and on Apple technical notes.
Warning: As with many things associated to Apple, and particularly when related to color management,
precise information is hard to get by, and is always subject to change. This is why most of the material is
quoted from people who knew something at some time!
This was in the pre-sRGB days, so Apple RGB was used as a generic RGB profile. It made sense at the
time since much of the color content was artificially generated in FreeHand or Illustrator, thus it was created
in Apple RGB. Adobe eventually put Apple RGB into Photoshop as a working space and it thus it has been
passed on to today's users.
Now that it is the Modern Age, it would be a good idea to drop Apple RGB from system. It outlived its
usefulness. Comparing it to sRGB or any of the current LCD or CRT monitors is like comparing a Conestoga
wagon to a current automobile.
Robin Myers
This also applied to untagged RGB data sent to the display by non-ICC aware applications. In other words, this
meant that “Generic RGB” was assumed to be the source profile for untagged data by ColorSync, which is
Apple's color management technology at the operating system level, which then converted it to whatever
display profile was selected.
(...)
Moving forward, OS X is taking steps to prevent accidental printing without color management. This makes
it unlikely that you can use the standard OS X apps like Preview to print profile targets reliably. Tagging it
with Generic RGB will work today, but not tomorrow when Snow Leopard launches (and switches to a
default profile of sRGB, not Generic RGB). And tagging the target with sRGB tomorrow may not work for
the future (should future versions of OS X switch to another default profile).
(...)
Untagged data is assumed to be in the display color space, it has intentionally behaved that way for quite
some time.
(...)
Conclusion
The Apple RGB space is no longer coupled to the display space. A custom calibrated display profile is always
preferred; however, if you do not have a custom profile and you are using a display integrated with a Mac
computer, select the profile corresponding to factory calibration. If connecting to third party monitor for which
you have no reliable profile, select sRGB as the default space for a standard gamut display.
A simple software-encoding gamma of 0,455 (=1/2,2) is used in CT&A. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
Beta RGB was devised after a careful study and comparative analysis of many RGB spaces. Beta RGB is
designed to:
• have a gamut which enclose various color sets of "possibly important colors" (in the words of the space's
author), such as different film types, color charts and printing gamuts;
• have a gamut which is as small as possible, taking the first criteria into account, in order to minimize
quantization errors;
• maximize the percentage of the visible spectrum that it encompasses;
• maximize the encoding efficiency, i.e. the percentage of valid RGB triads, representing real colors.
The following table presents the percentage of the visible gamut encompassed by each space, the L*a*b*
gamut Efficiency as well as the Encoding Efficiency for most of the RGB spaces supported by CT&A (This
data was derived by Bruce Lindbloom and is used by permission):
L*a*b* gamut Encoding
RGB space
Efficiency (%) Efficiency (%)
Adobe (1998) 50,6 100
Apple RGB 33,5 100
BestRGB 77,6 96.5
Beta RGB 69,3 99.0
Bruce RGB 41,5 100
CIE RGB 64,3 96,1
ColorMatch 35,2 100
DonRGB4 72,1 98,8
eciRGB 55,3 99,7
Ekta Space PS5 65,7 99,5
NTSC 54,2 99,9
PAL / SECAM 35,7 100
ProPhoto 91,2 87,3
SMPTE-C 31,9 100
sRGB 35,0 100
Wide Gamut 77,6 91,9
Beta RGB encompasses 69% of the colors visible by humans; this is to be compared to 34% for Apple RGB,
51% for Adobe (1998), and 91% for ProPhoto. In comparison, the encoding efficiency for Beta RGB is 99%,
compared to 100% for Apple RGB and Adobe (1998), and 87% for ProPhoto.
We see that for smaller spaces, all RGB values are valid (100% encoding efficiency), which is expected, but
that larger spaces are less efficient. While it is easy to see why ProPhoto has invalid triads, because two of its
primaries are outside of the visible spectrum, others, like BestRGB and Wide Gamut, do suffer of the same
problem (to a lesser extent than ProPhoto however). Beta RGB thus offers a very nice compromise.
A simple software-encoding gamma of 0,455 (=1/2,2) is used in CT&A. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
Here is a presentation of Bruce RGB extracted from one of Bruce's numerous articles (Ref. 13):
BruceRGB is essentially a compromise between two spaces shipped with Photoshop 5.x -- ColorMatch RGB
and Adobe RGB (1998). ColorMatch RGB is a high-quality monitor space, but it is a monitor space
nonetheless, designed to accommodate the color range and spectrum of light-emitting RGB devices. Adobe
RGB (1998) is a considerably larger space that grew out of wishful thinking for a future generation of video
monitors.
ColorMatch RGB and Adobe RGB (1998) are in common use in output-centric workflows, but neither was
designed with the idea of color-accurate output as the paramount concern. As a result, both spaces suffer
from something of a mismatch with typical hard copy output, whether from a CMYK press or a photo-realistic
inkjet printer. Both spaces clip (drop out) the saturated yellows and oranges achievable in sheet-fed printing
and on photo printers: You'd have to resort to a very large space such as Adobe's Wide Gamut RGB or
Kodak's ProPhoto RGB to encompass those. But ColorMatch RGB also clips cyan, as well as the blues and
greens that lie adjacent to it, quite significantly. Adobe RGB doesn't clip printable cyan, but it contains a
fairly large number of colors that few if any output devices can reproduce, so it wastes a good number of
those precious 256 data points in each channel.
BruceRGB, in contrast, was designed with output in mind from the start. It clips fully saturated yellows by
about the same amount as Adobe RGB, and quite a bit less than ColorMatch RGB. It may clip cyan slighly
with very high-quality sheet-fed printing, but not by more than a few percent -- much less than ColorMatch
RGB. Equally important, it wastes far fewer bits on unrealizable colors than Adobe RGB.
A simple software-encoding gamma of 0,455 (=1/2,2) is used in CT&A. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
A simple software-encoding gamma of 0,455 (=1/2,2) is used in CT&A. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
The main advantages for its users are a reproducible and well-characterized environment. A calibrated
PressView system takes into account, independently for each RGB channel, the CRT gain, offset and
brightness combined with the display look-up table (LUT), which it uses for calibration purposes. The resulting
display gamma is a "perfect" 1,8 value (=1/0,556) on a 0,33 cd/m2 black pedestal and a white point luminance
of 85 cd/m2.
The primaries used in CT&A, and shown in the RGB Space data dialog, are different than the ones used in
Photoshop. The ones used herein were confirmed by miro displays, which purchased the Radius brands and
technologies from Radius, now renamed Digital Origin (Note: present company status unknown).
A simple software-encoding gamma of 0,556 (=1/1,8) is used in CT&A. This gamma is the same as the one
defined for Apple RGB, Generic RGB, and ProPhoto. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
There are two versions of this space which differ in their Illuminant; the DCI P3 Theater RGB space Illuminant
has a Correlated Color Temperature (CCT) of 6300 K (expressed as 6300 K *) while the DCI P3 D65 RGB
space has a D65 Illuminant. Both spaces are defined with a simple software-encoding gamma of 2,6.
Note: Only the DCI P3 Theater is defined as a preset RGB space in CT&A. However, you can easily define the
DCI P3 D65 using the Custom RGB space dialog.
There is also a variant of this space defined by Apple, called Display P3, which has a D65 Illuminant but with
the gamma of the sRGB space.
14.4.10 Display P3
Defined by Apple, Display P3 has the same primaries as the DCI P3 Theater and DCI P3 D65 RGB spaces. It
is defined with a D65 Illuminant (same as for DCI P3 D65) but its gamma is the detailed gamma defined for
sRGB.
This space has been used by Apple in some of its wide gamut displays. It is interesting to note that Apple
selected the DCI primaries instead of the Adobe (1998) RGB primaries which have been used by other display
manufacturers in order to bring their display closer to the specifications of Digital Cinema. However, because of
its use of the sRGB detailed gamma, some conversion is nonetheless required if DCI P3 values are required.
A simple software-encoding gamma of 0,455 (=1/2,2) is used in CT&A. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
You should also consider the Ekta Space PS5, another space dedicated to the Ektachrome film.
The development and release, in 1999, of eciRGB 1.0 is one of the result of this initiative.
eciRGB 1.0
According to the ECI Web site:
http://www.eci.org/doku.php?id=en:colourstandards:workingcolorspaces
... ECI wanted to see one (ICC profile) that:
• has a gamut that covers all colors that can be printed on today's printing presses—whether sheet fed or
web offset, gravure or newsprint—but not much beyond (in order to not to waste precision for bits that
never really get used);
• produces a neutral gray whenever the values for Red, Green and Blue are equal;
• offers equidistance, i.e. equal difference between two color values in eciRGB mirrors an perceived equal
difference when these colors are seen by the human eye;
• is based on a Gamma of 1,8 and a light source of 5000K.
Older CT&A versions were based on eciRGB 1.0. Starting with CT&A version 3, we switched to the definition of
eciRGB_v2.
If required, you can easily define a custom space matched to the definition of eciRGb 1.0. In the Custom RGB
space dialog, first select "eciRGB_v2" in the "Custom" space menu, then change the space gamma by
selecting "default 1.80" in the gamma menu. This gamma is the same as the one defined for Apple RGB,
ColorMatch, Generic RGB, and ProPhoto. There is no detailed gamma for eciRGB 1.0.
eciRGB_v2
Defined as a technical revision of eciRGB 1.0, eciRGB_v2 has one major change:
• the gamma of 1,8 is replaced by the L* (pronounced L-star) characterization method, which is the L* of
CIELAB.
As we show in the L* (L-star) section, the L* Tone Response Curve is in fact a detailed gamma as defined in
the RGB to R'G'B', and gamma section, where the detailed gamma is defined by:
offset = 0,16
gamma = 1/3 = 0,333333
transition = 0.008856
slope = 9,033
and which can also be approximated by a simple software-encoding gamma of 0,410741 (=1/2,43462 if you
define gamma using the reciprocal value).
The primaries and Illuminant are the same as in the first version. Work is under way to incorporate this space in
the ISO 22028 standard. Again, according to the ECI Web site:
• In general, ECI now recommends to always use the eciRGB_v2 profile for new projects or when creating
new data. This is especially true when converting from RAW data or from 16 bit image data.
• For existing projects and files which are not using eciRGB_v2 it is not recommended to convert them to
eciRGB_v2 in order to avoid unnecessary conversion or – even more dangerous – assigning the wrong
profile to the data. Especially 8 bit data using eciRGB 1.0 should be kept in eciRGB 1.0 (preferably with
the eciRGB 1.0 profile embedded) as any colour space conversion will lead to at least some loss of
quality.
Starting with CT&A version 3, eciRGB_v2 replaced eciRGB 1.0 in the RGB space selection menu. Numerical
data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
Interestingly, the primaries of both versions of eciRGB are those of NTSC.
For conversion of multiple color values in list form, you can use one of the Gamut tools in BabelColor's
PatchTool, which enable you to select any standard ICC profile. You can see a Gamut tools screenshot here:
https://www.babelcolor.com/patchtool_gamut_convert.htm .
As per Mr. Holmes' "readme" file that accompanies the profile (18 pages of recommended reading) which can
be downloaded from his Web site:
"Ekta Space PS 5, J. Holmes" is sometimes referred to as "Joe RGB" or simply "Ekta Space". Like the
profile from which it was derived, it is a special RGB color space profile which I designed for high quality
storage of image data from scans of transparencies such that little or no clamping of out-of-gamut data
would typically occur when the colors are converted from a scanner profile for transparencies into this
profile, even when highly saturated colors are present in the film.
Like all the wider gamut spaces, scanning should be done at 16 bits per channel (48 bits for RGB) whenever
possible. Conversion to 8 bits per channel (24 bits for RGB) should only be done at the final stage.
A simple software-encoding gamma of 0,455 (=1/2,2) is used in CT&A. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
You should also consider the DonRGB4 space, another space dedicated to the Ektachrome film.
This also applied to untagged RGB data sent to the display by non-ICC aware applications. In other words, this
meant that “Generic RGB” was assumed to be the source profile for untagged data by ColorSync, which is
Apple's color management technology at the operating system level, which then converted it to whatever
display profile was selected.
However, in the following years, Apple changed the default space again, this time selecting sRGB as its default
space for untagged images, indirectly acknowledging the use of sRGB as the common space for all platforms.
When this change was done, Apple added that the default space could be expected to change again in the
future, which it did, as we discuss in the Apple RGB section.
Generic RGB, contrary to what its name suggests, is well defined by Apple. It has a gamma of 1,8 and is based
on the D65 Illuminant, like Apple RGB, but the chromaticities of its primaries are very close to the ones of
ColorMatch (Note: ColorMatch is D50 based). With the same gamma and almost identical primaries, you could
think of Generic RGB as a D65 ColorMatch. In any case, the Generic RGB space primaries are, except for the
green, quite close to the original Apple RGB values, and the only “valid” reason for the change is a mention by
Apple that “Apple RGB” is in fact proprietary to Adobe, and thus does not belong to Apple!
A simple software-encoding gamma of 0,556 (=1/1,8) is used in CT&A. This gamma is the same as the one
defined for Apple RGB, ColorMatch, eciRGB 1.0, and ProPhoto. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
With chromaticities not very far from SMPTE-C (and SMPTE-240M), HDTV and sRGB strive to represent the
evolution of our standard TV and its convergence with the PC world, while maintaining compatibility with the
large quantity of recorded media.
A simple software-encoding gamma of 0,513 (=1/1,95) is used in CT&A. The detailed gamma is the one
defined in ITU-R BT.709-3. The same gamma is defined for NTSC, PAL / SECAM and SMPTE-C.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
14.4.16 NTSC
The color space of the first North-American TV sets. It is now an obsolete space that has been replaced by one
defined with more efficient – brighter – phosphors, SMPTE-C, albeit at the expense of the gamut size. In a
strange turn of events, the eciRGB 1.0 and eciRGB_v2 spaces have the same primaries as the NTSC space,
while the primaries of the Adobe (1998) RGB space are very close, a sign of the significant recent progress in
the printing industry which can print larger gamuts than a few years ago.
A simple software-encoding gamma of 0,513 (=1/1,95) is used in CT&A. The detailed gamma is the same as
the one defined for HDTV (HD-CIF), PAL / SECAM and SMPTE-C.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
A simple software-encoding gamma of 0,513 (=1/1,95) is used in CT&A. The detailed gamma is the same as
the one defined for HDTV (HD-CIF), NTSC and SMPTE-C.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
14.4.18 ProPhoto
A very large gamut designed by Kodak which is getting attention from digital camera users as an archiving and
working space for RAW — unprocessed camera — data.
Formerly called ROMM RGB while being developed, it was renamed to ProPhoto to make it more noticeable to
its intended users.
While it covers most of the visible spectrum, it also extends outside of it. As a result, about 13% of the RGB
triads represent non-existent colors. Working at 16 bits per channel (48 bits for RGB) is a minimum with this
space, and there are some concerns that even this bit depth is not enough. Some users are also puzzled by
the decision to use a 1,8 gamma when the industry is slowly moving towards a standard 2,2 value. In any case,
when used with caution for images that DO contain colors outside of the range of medium size working spaces,
like Adobe (1998) RGB, it can provide improved color rendering when used in conjunction with modern wide
gamut inkjet printers.
A simple software-encoding gamma of 0,556 (=1/1,8) is used in CT&A. This gamma is the same as the one
defined for Apple RGB, ColorMatch, eciRGB 1.0, and Generic RGB. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
It is defined with a detailed gamma which is essentially the same as the one for NTSC and PAL / SECAM. The
difference is that the gamma parameters have higher precision to better match 10 or 12 bit RGB components.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
14.4.20 SGI
The chromaticities of a Sony Trinitron CRT are used in CT&A, but other displays by Hitachi and Mitsubishi, with
different chromaticities, are also found in the SGI product line. The relatively low CRT gamma of 0,35 (=1/2,86),
quoted by the tube's manufacturer, is common for Sony's GDM series of displays from which the SGI-Sony
displays are derived.
When a gamma number is entered by the user in an SGI system, the look-up table (LUT) is filled with values
corresponding to a γLUT = 1/gamma_number. A typical LUT gamma is 0,588 (=1/1,7)
A simple software-encoding gamma of 0,68 (=1/1,47) is used in CT&A. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
14.4.21 SMPTE-240M
SMPTE-240M is a standard for 1125-Line High-Definition analog video. Its primaries are the same as for
SMPTE-C.
However, the software-encoding gamma of SMPTE-240M is slightly different than the one defined for SMPTE-
C. Even so, a simple generic gamma of 2,2 (=1/0,455) is often used in computer software for both spaces. The
simple software-encoding gamma values used in this program for these spaces were obtained by doing a best
fit on the detailed gamma functions; they are different for SMPTE-C and SMPTE-240M, and more precise than
the generic value.
A simple software-encoding gamma of 0,521 (=1/1,92) is used in CT&A. The detailed gamma is the one
defined in SMPTE 240M-1995.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
14.4.22 SMPTE-C
SMPTE-C defines the primaries for the current North American and Japanese composite analog video
standard, SMPTE 170M-1999. You should note that, for compatibility with existing studio equipment, the
primaries of NTSC are also accepted in SMPTE 170M-1999.
Even if the software-encoding gamma of SMPTE-C is slightly different than the one defined for SMPTE-240M,
a simple generic gamma of 2,2 (=1/0,455) is often used in computer software for both spaces. The simple
gamma values used in this program for these spaces were obtained by doing a best fit on the detailed gamma
functions; they are different for SMPTE-C and SMPTE-240M, and more precise than the generic value.
A simple software-encoding gamma of 0,513 (=1/1,95) is used in CT&A. The detailed gamma is the one
defined in SMPTE 170M-1999. The same gamma is defined for HDTV (HD-CIF), NTSC, and PAL / SECAM.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
With chromaticities not very far from SMPTE-C (and SMPTE-240M), HDTV and sRGB strive to represent the
evolution of our standard TV and its convergence with the PC world, while maintaining compatibility with the
large quantity of recorded media.
Advertised as a general-purpose space for consumer use, sRGB is proposed for applications where
embedding the space profile (ex: ICC profile) may not be convenient for file size or compatibility purposes. By
having all elements in a system sRGB compliant, no time is lost in conversions. The World Wide Web is
obviously a target of choice for this space but it should not be discounted for other "scanner-to-printer"
applications. An extended gamut color encoding standard has been proposed for sRGB (Ref. 45); it supports
multiple levels of precision while being compatible with the base standard.
sRGB is the default space for Windows and a good choice for Mac (see the Apple RGB section for more info).
All untagged RGB data sent to the display by non-ICC aware applications is thus assumed to be sRGB. In
other words, this means that sRGB is assumed to be the source profile for untagged data by the operating
system color-management system, which then converts it through whatever display profile is selected.
A simple software-encoding gamma of 0,455 (=1/2,2) is used in CT&A. The detailed gamma is the one defined
in IEC 61966-2-1.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
A simple software-encoding gamma of 0,455 (=1/2,2) is used in CT&A. There is no detailed gamma.
Numerical data pertaining to this space can be viewed in the RGB Space data and RGB to XYZ data dialogs.
IMPORTANT WARNING
Even if catalogues of color chips and swatches can be measured and presented in electronic form, the ultimate
reference traditionally remains a physical sample. There are many reasons why this is often true:
• A physical sample properly represents the effect of the stock (the paper on which the chip is painted or
printed).as well as the chip's surface finish, that can go from matte to glossy, with all steps in between. While
it is feasible to take into account the stock color in an electronic representation, all surface effects are
impossible to display.
• It is impossible to reproduce all the "printable" or "paintable" colors on a standard computer monitor, not to
mention fluorescent colors and metallic finishes.
The goal of this tool is to facilitate the task of comparing, matching and converting colors to and from color
catalogues and RGB spaces, even colors that cannot be reproduced on a computer display. Once a color chip
is identified, we recommend that the user gets a physical sample to confirm that the color and finish match the
rendering intent.
The color matching fan is to be used for matching the colors in the BS 5252 standard which are referred to in
derived color standards. Please note that a color is only a British Standard color when it appears in a standard
derived from BS 5252 for a particular product or function; in other words, a derived standard may not refer to all
237 colors of BS 5252.
A BS 5252F patch code has three parts. For example, a bright yellow patch can be found with the following
code:
10 E 55
where the number "10" describes the color in terms of its hue, the letter "E" identifies its grayness group, and
"55" describes its weight.
The hues are numbered from "02" to "24", corresponding to a hue circle going from red, to orange, to yellow, to
green, to blue, and purple. Neutral shades are identified with a "00" hue number. The grayness groups go from
"A", high grayness (i.e. colors with low saturation), to "E", very low grayness (i.e. saturated colors). The weights
go from "01" to "58", with the weight numbers steadily increasing from one grayness group to the other, with the
lower weights located in group "A", and the higher weights in group "E". Also note that patches with a given
weight number will be found only within a single grayness group.
In the BS 5252F fan deck, the patches are sorted first in terms of grayness, then weight, and finally hue. In this
software, the patches are sorted first in terms of hue, then grayness, and finally weight.
While not exhaustive, it has found many uses outside of its "mandatory" field. For example, many hobbyists use
the standard to exchange color information in order to accurately reproduce scaled models.
Chips are identified using a 5 digits numbering system ("12345"). The first digit describes the surface finish.
Please note that not all colors are presented with the three finishes; many have only one. The second digit
indicates an arbitrarily selected color classification grouping. The "misc." group comprises whites, blacks, and
others. The last three digits ("__345") are assigned in an approximate order of increasing luminance. The
numbers are not closely packed sequential numbers; large "holes" between chips are frequent.
Warning: Group No. 8, "fluorescent", is included in the deck but the user should be aware that these colors
cannot be displayed on a computer with the same accuracy as the other non-florescent chips. The "fluorescent"
group comprises only six chips.
In the FED-STD-595 loose sheet Color Book, chips are first separated by color group; then they are presented
by increasing luminance (last 3 digits). Each page is separated in three columns, one per finish, and the chips
of a given color appear side by side. For example, in the green color group, you will find the 14516, 24516, and
34516 chips on the same row. You will also find additional chips in change notices that are delivered on
separate sheets.
The overall grouping of the chips, and the separate location for the change notices make this standard hard to
navigate in printed form. For example, you will find chips of all hues in the gray section. You should find that
navigation is easier with the L*C*h pad mode.
Important: As per the FED-STD-595, if this standard is called in USA government procurement, it is mandatory
to match a color by visual comparison with a physical chip; therefore, you should purchase the selected chip for
final approval.
Tel.: +1-202-619-8925
Fax: +1-202-619-8985
The Munsell Hue is separated in 10 hue ranges (please refer to the illustration below). For each hue range,
there is a major hue located at the range center. The major hues are Red, Yellow, Green, Blue and Purple, as
well as the five hues located between them and named by combining the names of the hues on each side. For
example, the hue located between Yellow and Red is called Yellow-Red, instead or Orange; this naming
convention minimizes the number of color names one has to deal with.
Each hue range is further divided in 10 sub-zones defined by 11 radii labeled from zero to 10. The major hues
are labeled 5R, 5YR, 5Y, 5GY, 5G, 5BG, 5B, 5PB, 5P, 5RP. The color circle is, in effect, separated in 100 hue
segments where each hue separation is perceptually uniform. A zero to 100 number can be used to describe
the Munsell Hue but it is seldom seen (the zero is at 10RP, the numbers increase when going counter-
clockwise, up to 100, also at 10RP).
The radius labeled "10" in one zone corresponds to the "0" radius of the next zone (the 10Y hue is the same as
0GY); in practice, the 10Y notation is the preferred one.
The Munsell Book of Color has samples with hues located at every 2,5 hue steps. For example: 10RP / 2,5R /
5R / 7,5R and 10R for the red hue range.
The Munsell Chroma, like the C* of the L*C*h representation, can be considered an approximate counterpart of
perceived color saturation, while the Munsell Value is associated to the lightness (L*) of the color. The
perceived chroma and value increase uniformly with each unity step. For example, the perceived difference
between a Chroma 1 and a Chroma 2 sample is the same as the one perceived between Chroma 4 and
Chroma 5 samples; similarly, the perceived difference between a Chroma 1 and a Chroma 3 sample is the
same as the one perceived between Chroma 4 and Chroma 6 samples.
In CT&A, bidirectional conversions FROM and TO the Munsell notation can be performed in many ways:
• Munsell tools: A dedicated tool for bidirectional high precision conversion between Munsell and L*a*b*/RGB.
• RGB vs RGB tool RGB to Munsell: Convert RGB data to high precision Munsell notation.
• RGB vs RGB tool Color Deck: A digital catalogue equivalent of the Munsell Book of Color. Used to convert
samples presented in fixed uniformly distributed steps to XYZ/L*a*b*/RGB coordinates.
• Convert TO Munsell Color Deck: Find the nearest Munsell (digital catalogue) sample for a given RGB/L*a*b*
input or for a sample from another Color Deck.
First devised as a color description teaching aid, the Munsell Color System was quantitatively formalized in the
1940s. The analysis led to small adjustments in the samples color in order to improve the spacing uniformity
between them. This "renotated" system is the one we now use. The Munsell Color System is an international
reference, defined in ASTM D1535 and other standards, that is used in many fields of work, from archaeology,
when describing the colors of artifacts, to medical studies, when comparing the color of skin affections, to
hobby activities such as accurately depicting the colors of scaled vintage airplanes.
A great tool to learn and practice the Munsell system is The New Munsell Student Color Set, which combines a
color-primer book with color chips and a three-ring binder to store the chips; this tool is produced by Jim Long
and Joy Turner Like (see Ref. 34).
See the XYZ to Munsell section for more information on the conversion process. Additional information and
data on the Munsell Color System can be found on the Munsell Color Science Laboratory (MCSL) Web site:
https://www.rit.edu/science/munsell-color-lab . This laboratory is part of the Rochester Institute of Technology.
Please note that MCSL is not the same entity as the Munsell Color Services Division of GretagMacbeth, which
is itself now part of X-Rite.
Note: RAL stands for Reichsausschuss für Lieferbedingungen, which translates as Committee of the German
Reich for Terms and Conditions of Sale; it was founded in Berlin in 1925.
Through time, colors were added to the original set of 40 colors, and a few were removed. This color set is now
known as RAL CLASSIC, which comprises 213 colors, of which 210 can be found in the CT&A RAL CLASSIC
deck. This is still a very limited set, pastel colors being obviously absent, and a more modern and complete
color system, called RAL DESIGN, has been defined to replace it. However, RAL DESIGN has far from
displaced RAL CLASSIC, which is well entrenched in many companies' specifications.
RAL CLASSIC chips are described by a four digits number ("1234"), where the first one describes a broad color
group, and the last three have no particular signification. The color groups are:
Important: While RAL CLASSIC chips are available in both semi-gloss and glossy finishes, the colors found in
the program deck are representative of the semi-gloss finish.
Warning: RAL 9006 and 9007 were defined in relation to the appearance of corrosion protection coatings. The
RAL 9006 coating is essentially made of aluminum particles, while RAL 9007 is made of layers of iron oxide
and aluminum powder. According to RAL, these patches cannot be reproduced with high precision from one
edition to the other. In addition, using them for decorative purposes requires an additional transparent layer,
which can also affect the perceived color. For these reasons, these two colors are recommended only for
corrosion protection applications.
Ref. 1 Michael Has, Todd Newman, "Color Management: Current Practice and the Adoption of a New
Standard," available on the Internet on the ICC Web site at https://www.color.org/wpaper1.html.
Ref. 2 Michael Stokes, M.D. Fairchild, Roy S. Berns, "Colorimetric quantified visual tolerances for pictorial
images," Comparison of Color Images Presented in Different Media, Proceedings 1992, Vol. 2, M.
Pearson ed., Tech. Assoc. Graphic Arts and Inter-Soc. Color Council, pp. 757-777.
Ref. 3 Roy S. Berns, Mark E. Gorzynski, Ricardo J. Motta, "CRT Colorimetry, Part II: Metrology," COLOR
research and application, Vol. 18, No. 5, Oct. 1993, pp. 315-325.
Ref. 4 J. R. Jiménez, J. F. Reche, J. A. Díaz, L. Jiménez del Barco, E. Hita, "Optimization of Color
Reproduction on CRT-Color Monitors," COLOR research and application 24 (3), 207-213 (1999)
Ref. 5 R.W.G. Hunt, The reproduction of Colour, 5th ed., Fountain Press (1995), ISBN 0-86343-381-2.
Ref. 6 C.S. McCamy, H. Marcus, J.G. Davidson, "A Color-Rendition Chart," J. Appl. Phot. Eng., Vol. 2, No. 3,
Summer 1976, pp. 95-99, Society of Photographic Scientists and Engineers (now called "The Society
for Imaging Science and Technology"; https://www.imaging.org ).
Ref. 7 M.R. Luo, R.W.G. Hunt, B. Rigg, K.J. Smith, "Recommended colour-inconstancy index," Journal of the
Society of Dyers and Colourist, Vol. 115, May/June 1999, pp. 183-188.
Ref. 8 Mary Nielsen, Michael Stokes, "The Creation of the sRGB ICC Profile," Proceedings of IS&T Sixth
Color Imaging Conference: Color Science Systems and Applications 1998, Scottsdale, Arizona, ISBN
0-89208-213-5.
Ref. 9 PNG (Portable Network Graphics) Specification, Version 1.0, World Wide Web Consortium (W3C)
Recommendation 01-October-1996, available on the Internet on the site https://www.w3.org.
Ref. 10 Roy S. Berns, Ricardo J. Motta, Mark E. Gorzynski, "CRT Colorimetry, Part I: Theory and Practice,"
COLOR research and application, Vol. 18, No. 5, Oct. 1993, pp. 299-314.
Ref. 11 Charles A. Poynton, A Technical Introduction to Digital Video, John Wiley & Sons (1996), ISBN 0-471-
12253-X. From the same author, on the Internet, on the site http://www.poynton.com/Poynton-color.html:
"Frequently Asked Questions About Gamma," available as "GammaFAQ.pdf;"
"The rehabilitation of gamma," available as "Rehabilitation_of_gamma.pdf;"
"Frequently Asked Questions About Color," available as "ColorFAQ.pdf."
Ref. 12 David L. MacAdam, "Visual sensitivities to color differences in daylight," J. Opt. Soc. Am., Vol. 32,
1942, pp. 247-273.
Ref. 13 Bruce Fraser, "Out of Gamut: Finessing Photoshop Color," available on the Internet at
https://creativepro.com/out-of-gamut-finessing-photoshop-color.
Ref. 14 The Science of Color, Committee on Colorimetry, Optical Society of America, Washington (1973),
ISBN 0-96003-801-9.
Ref. 16 ASTM E308-99: "Standard Practice for Computing the Colors of Objects by Using the CIE System,"
available from their Web site: https://www.astm.org.
Ref. 17 ICC Specification ICC.1:1998-09: "File Format for Color Profiles," available on the Internet at
https://www.color.org.
Ref. 19 Ján Morovic, To develop a Universal Gamut Mapping Algorithm, Ph.D. thesis, University of Derby,
October 1998.
Ref. 20 W. Thornton, "Matching lights, visual response, and the painfully sub-human CIE Standard
Observers," Perceiving, Measuring and Using Color, Vol. 26, 1990, p. 1250.
Ref. 22 Society of Dyers and Colourists (SDC): https://www.sdc.org.uk. American Association of Textile
Chemists and Colorists (AATCC): https://www.aatcc.org. British Standards: https://www.bsigroup.com.
ISO standards: https://www.iso.org.
Ref. 23 ASTM D1535: "Standard Test Method for Specifying Color by the Munsell System," available from
their Web site: https://www.astm.org.
Ref. 24 Joy Turner Luke, "Uniform Color Scales," Optics and Photonics News, September 1999, p. 28.
Ref. 25 Roy S. Berns, Billmeyer and Saltzman's "Principles of Color Technology," 3rd ed., John-Wiley & Sons
(2000), ISBN 0-471-19459-X.
Ref. 26 N. Moroney, M.D. Fairchild, R.W.G. Hunt, C. Li, M.R. Luo, and T. Newman, "The CIECAM02 Color
Appearance Model," Proceedings of the IS&T/SID Tenth Color Imaging Conference, Nov. 2002, pp.
23-27.
Ref. 27 R.W.G. Hunt, C. Li, M.R. Luo, and T. Newman, "Chromatic Adaptation Transforms," COLOR research
and application, Vol. 30, No. 1, Feb. 2005, pp. 69-71.
Ref. 28 M.D. Fairchild, "A Revision of CIECAM97s for Practical Applications," COLOR research and
application, Vol. 26, No. 6, Dec. 2001, pp. 418-427.
Ref. 29 A.K.Roy Choudhury, S.M. Chatterjee, "Evaluation of the Performance of Metameric Indices," COLOR
research and application, Vol. 21, No. 1, Feb. 1996, pp. 26-34.
Ref. 30 Y.-M. Lam, J.H. Xin, "Evaluation of the Quality of Different D65 Simulators for Visual Assessment,"
COLOR research and application, Vol. 27, No. 4, Aug. 2002, pp. 243-251.
Ref. 31 C.S. McCamy, "New Metamers for Assessing the Visible Spectra of Daylight Simulators and a Method
of Evaluating Them," COLOR research and application, Vol. 24, No. 5, Oct. 1999, pp. 322-330.
Ref. 33 CIE 13.3-1995: "Method of Measuring and Specifying Colour Rendering Properties of Light Sources;"
CIE 51.2-1999: "A Method for Assessing the Quality of Daylight Simulators for Colorimetry;"
CIE S 012 /E:2004: "Standard Method of Assessing the Spectral Quality of Daylight Simulators for
Visual Appraisal and Measurement of Colour;"
Commission Internationale de l'Éclairage (CIE): International headquarter - http://www.cie.co.at;
U.S.A. branch - http://www.cie-usnc.org.
Ref. 34 Jim Long, Joy Turner Luke, The New Munsell Student Color Set, 2nd Ring ed., Fairchild Books and
Visuals (2001), ISBN 1563672006.
Ref. 36 ASTM E313-05: "Standard Practice for Calculating Yellowness and Whiteness Indices from
Instrumentally Measured Color Coordinates," available from their Web site: https://www.astm.org.
Ref. 37 Hiroko Uchida, "A New Whiteness Formula," COLOR research and application, Vol. 23, No. 4, August
1998, pp. 202-209.
Ref. 38 Guoxin He, Mingxun Zhou, "Whiteness formula in CIELAB uniform color space," CHINESE OPTICS
LETTERS, Vol. 5, No. 7, July 10 2007, pp. 432-434.
Ref. 39 Ernst Ganz, Hartmut Kurt Andreas Pauli, "Whiteness and tint formulas of the Commission
Internationale de l’Eclairage: approximations in the L*a*b* color space," APPLIED OPTICS, Vol. 34,
No. 16, 1 June 1995, pp. 2998-2999.
Ref. 40 TAPPI T452 om-08: "Brightness of pulp, paper, and paperboard (directional reflectance at 457 nm),"
available from their Web site: https://www.tappi.org.
Ref. 41 ASTM D985-97 (Reapproved 2007): "Standard Test Method for Brightness of Pulp, Paper, and
Paperboard (Directional Reflectance at 457 nm)," available from their Web site: https://www.astm.org.
Ref. 42 ISO 13655:2009: "Graphic technology — Spectral measurement and colorimetric computation for
graphic arts images," available from their Web site: https://www.iso.org.
Ref. 43 ISO 5-4:2009: "Photography and graphic technology -- Density measurements -- Part 4: Geometric
conditions for reflection density," available from their Web site: https://www.iso.org.
Ref. 45 PIMA 7667:2001: “Photography – Electronic still picture imaging – Extended sRGB color encoding –
e-sRGB” (PIMA: Photographic and Imaging Manufacturers Association. In 2001 PIMA merged with
the Digital Imaging Group to form the International Imaging Industry Association (I3A); I3A
apparently disbanded in 2013). Similar to the method presented in Amendment 1 of
IEC 61966-2-1:1999 (Wikipedia, International Color Consortium).
Ref. 46 Wendy Davis, Yoshi Ohno, "Color quality scale," Optical Engineering 49(3), March 2010, 033602-1 to -16.
Ref. 47 KAG SMET, J Schanda, L Whitehead, RM Luo, "CRI2012: A proposal for updating the CIE colour
rendering index," Lighting Res. Technol. 2013; 45: 689-709.
Ref. 48 Mark S. Rea, Jean P. Freyssinier-Nova, "Color Rendering: A Tale of Two Metrics," COLOR research
and application, Vol. 33, No. 3, June 2008, 192-202.
Ref. 49 Kevin Smet, Wouter R. Ryckaert, Michael R. Pointer, Geert Deconinck, and Peter Hanselaer,
"Correlation between color quality metric predictions and visual appreciation of light sources,"
OPTICS EXPRESS, Vol. 19, No. 9, 25 April 2011, 8151-8166.
Ref. 50 K.A.G. Smet, W.R. Ryckaert, M.R. Pointer, G. Deconinck, P. Hanselaer, "A memory colour quality
metric for white light sources," Energy and Buildings 49 (2012) 216-225.
Ref. 51 Kevin W. Houser, Minchen Wei, Aurélien David, Michael R. Krames, and Xiangyou Sharon Shen,
"Review of measures for light-sources color rendition and considerations for a two-measure system
for characterizing color rendition," OPTICS EXPRESS, Vol. 21, No. 8, 22 April 2013, 10393-10411.
Ref. 52 Yoshi Ohno (2014), "Practical use and Calculation of CCT and Duv," LEUKOS: The Journal of the
Illuminating Engineering Society of North America, 10:1, 47-55. DOI:
10.1080/15502724.2014.839020.
Ref. 54 IES TM-30-15 (2015), "IES Method for Evaluating Light Source Color Rendition," available from the
Illuminating Engineering Society (IES) Web site: https://www.ies.org
Ref. 55 Aurélien David, Paul T. Fini, Kevin W. Houser, Yoshi Ohno, Michael P. Royer, Kevin A.G. Smet,
Minchen Wei, and Lorne Whitehead, "Development of the IES method for evaluating the color
rendition of light sources," OPTICS EXPRESS, Vol. 23, No. 12, 15 June 2015, 15888-15906.
Ref. 56 Michael H. Brill, Sabine Susstrunk, "Repairing Gamut Problems in CIECAM02: A Progress Report,"
COLOR research and application, Vol. 33, No. 5, October 2008, 424-426.
Ref. 57 ANSI/IES TM-30-20 (2020), "IES Method for Evaluating Light Source Color Rendition," available from
the Illuminating Engineering Society (IES) Web site: https://www.ies.org (download link)
Ref. 59 ISO 20654:2018, “Graphic technology — Measurement and calculation of spot colour tone value,"
available from their Web site: https://www.iso.org.
Ref. 61 SMPTE EG 432-1:2010, “Digital Source Processing - Color Processing for D-Cinema.”
SMPTE Web site: https://www.smpte.org. Support documents are available on this Web page:
https://dcimovies.com/specification/index.html.
Ref. 62 Recommendation ITU-R BT.2020-2, “Parameter values for ultra-high definition television systems for
production and international programme exchange.”
ITU Web site: https://www.itu.int. The English version of the document is available with this link:
https://www.itu.int/dms_pubrec/itu-r/rec/bt/R-REC-BT.2020-2-201510-I!!PDF-E.pdf
Ref. 63 Michael Royer, "What’s Next for LED Color Rendering?," Lightfair 2018, Chicago, 10 May 2018.
https://www.energy.gov/sites/prod/files/2018/05/f51/lfi2018_royer.pdf
Ref. 64 Tony Esposito, Kevin Houser, Jason Livingston, Michael Royer, "Specifying Color Quality with IES
TM-30," IES 2018 Annual Conference, Boston, 9-11 August 2018.
Ref. 65 CIE 224:2017: "Colour Fidelity Index for accurate scientific use,"
Commission Internationale de l'Éclairage (CIE): International headquarter - http://www.cie.co.at;
U.S.A. branch - http://www.cie-usnc.org.
Ref. 66 Zhifeng Wang, Binghao Zhao,Jiqiang Li, Ming Ronnier Luo, Michael R. Pointer, Manuel Melgosa,
Changjun Li, " Interpolation, Extrapolation, and Truncation in Computations of CIE Tristimulus
Values," COLOR research and application, Vol. 42, No. 1, February 2017, pp. 10-18.
Ref. 67 ANSI/IES TM-30-18 ADDENDUM #1, Part 1 Annex E (2019), "RECOMMENDATIONS FOR
SPECIFYING LIGHT SOURCE COLOR RENDITION," available from the Illuminating Engineering
Society (IES) Web site: https://www.ies.org (download link)
Ref. 68 ANSI/IES TM-30-18 ADDENDUM #1, Part 2 Annex F (2019), "EVIDENCE SUPPORTING
RECOMMENDED CRITERIA FOR SPECIFYING LIGHT SOURCE COLOR RENDITION," available
from the Illuminating Engineering Society (IES) Web site: https://www.ies.org (download link)
• General features:
• Compare two RGB spaces amongst twenty-four (24) pre-defined spaces and one custom space.
• Translate (Convert) from one RGB space to any other.
• Compare and Convert RGB spaces to industry standard color catalogues (Color Decks).
• Input RGB space data in six different formats.
• Acquire a L*a*b* or L*u*v* input from a colorimeter or spectrophotometer.
• Obtain output data in up to 11 different formats for RGB spaces and 9 formats for Color Decks.
• Calculate the color-difference (DeltaE) in up to fourteen formats.
• Get the individual contributions of ∆L*, ∆C*, ∆H* in the DeltaE* color-difference, as well as ∆h.
• See the "xy" chromaticity coordinates in graphical form (chromaticity diagram).
• Display the chromaticity data of the X-Rite/GretagMacbeth ColorChecker card, the primaries and
secondaries of 8 standard CMYK spaces, and the Planckian locus.
• Print the chromaticity diagram with or without the numerical colorimetric data.
• The colors are displayed using the assigned ICC display profile.
• Get clipping information (an Out-Of-Gamut flag) when converting to a RGB space and when data is
entered using the L*a*b* / L*u*v* input mode.
• Get tabular data on spaces, illuminants, Bradford matrices, and XYZ to RGB and RGB to XYZ matrices.
• Save a report with exhaustive comparative data for the selected colors.
• Color Decks
• British Standard 5252F (i.e. BS 5252F, which comprises the colors referred to by BS 4800, BS 4900, BS
4901, BS 4902, BS 4903, BS 4904, and BS 6770)
• Federal Standard 595B (FED-STD-595B)
• Munsell Color System (with over 4000 color chips; Munsell Color System description)
• RAL CLASSIC
• User-defined list imported using the "BabelColor CT&A Export" dialog of the PatchTool program, which
converts color lists saved in Adobe Swatch Exchange (ASE), CGATS, CXF or plain text formats to the
Color Decks database format.
• ∆ECMC(2:1) D50
∆ECMC(1:1) D50
"CMC(:c) color-difference", referenced to D50 illuminant
• ∆E00
"CIEDE2000 color-difference", referenced to the selected space or deck illuminant
• ∆E00 D50
"CIEDE2000 color-difference", referenced to D50 illuminant
The color-differences are computed for the illuminant of the spaces or decks being compared, only if both sides
have the same illuminant, and for illuminant D50, in all cases. In addition, the individual contributions of
• ∆L*, the lightness difference,
• ∆C*, the chroma difference, and
• ∆H*, the hue difference,
to the DeltaE* value, as well as
• ∆h, the hue angle difference,
are shown for each selected format.
• Input requirements: The Munsell tools do not require a color measurement instrument although data can be
inputted using such an instrument.
• Supported instruments:
• i1Pro (X-Rite, spectrophotometer): Rev A-D.
• i1Pro 2 (X-Rite, spectrophotometer): i1Pro 2 M0/M1/M2 and i1Pro 2 M2-only.
• i1Pro 3 (X-Rite, spectrophotometer): i1Pro 3 M0/M1/M2 and i1Pro 3 Plus M0/M1/M2 (M3 not-supported).
• If you are using an i1Pro 2 with the “i1Pro / i1Pro 2 (XRGA)” driver, an i1Pro 3, or an i1Pro 3 Plus, all
measurements will be taken with the three Measurement Conditions, M0 (Ill-A), M1 (D50), and M2 (UV-
cut), as defined in ISO 13655-2009. If you are using an i1Pro, or an i1Pro 2 with the “i1Pro / i1Pro 2
(non-XRGA)” driver, the program will select the default measurement conditions supported by the
instrument.
• Note (64 bit packages): The “i1Pro / i1Pro 2 (non-XRGA)” driver/menu selection is not available.
• General features:
• Convert from Munsell to RGB and L*a*b*.
• Convert from RGB to Munsell..
• RGB spaces: The (24) predefined spaces plus the Custom space defined in the RGB vs RGB tool.
• Convert from L*a*b* to Munsell.
• L*a*b* illuminants: 15 predefined illuminants plus a Custom illuminant defined in the RGB vs RGB tool.
• Measure spectral data and convert to Munsell.
• Export a report with tab-delimited data that can be directly imported in a spreadsheet program and
opened in many text editing applications. The report spectral measurements can also be read by
software, such as BabelColor PatchTool, which can open CGATS compatible files.
• Supported instruments:
• i1Pro (X-Rite, spectrophotometer): Rev A-D.
• i1Pro 2 (X-Rite, spectrophotometer): i1Pro 2 M0/M1/M2 and i1Pro 2 M2-only.
• i1Pro 3 (X-Rite, spectrophotometer): i1Pro 3 M0/M1/M2 and i1Pro 3 Plus M0/M1/M2/M3.
The M3 Measurement Conditions are supported only in the Density and Graph tools.
• Supported measuring modes: reflectance, emission, ambient illumination, flash. These measuring
modes may not be available in all instrument models.
• You can select between an “XRGA” compliant driver and a “non-XRGA”/legacy driver
• If you are using an i1Pro, or an i1Pro 2 with the “i1Pro / i1Pro 2 (non-XRGA)” driver, the program will
select the default measurement conditions supported by the instrument (M0 or M2).
• Note (64 bit packages): The “i1Pro / i1Pro 2 (non-XRGA)” driver/menu selection is not available.
• Text reports formats:
• All text reports are Tab-Delimited and can be opened in a spreadsheet application or a word processor.
• The CGATS compliant text files can also be opened by many color-management software, including
BabelColor's CT&A and PatchTool (Note: A CGATS compliant file does not guarantee that the data can
be used by a program!).
• Test source data: CCT (kelvin); Duv (CIE1960); brightness (lux); LER (Light Efficiency Ratio, in lm/W); the
Reference source (a blackbody or a D-Series illuminant).
• CRI (CIE 13.3: 1995): A graph of the 14 individual indices and Ra; numerical values of Ra (a general score
based on the first 8 indices and better known as the current CRI), R9, R(9-14) (for indices 9 to 14) and R(1-
14) for indices 1 to 14; a graph of the samples (a*, b*) coordinates; a representation of the samples
illuminated by the Reference and Test sources; the CIELAB color difference between the patches (Ref. 33).
• CQS (Color Quality Scale, NIST Version 9.0.3): A graph of the 15 individual indices and Qa; numerical values
of Qa (general score based on the 15 indices), Qf (fidelity index) and Qg (relative gamut area); a graph of the
samples (a*, b*) coordinates; a representation of the samples illuminated by the Reference and Test sources;
the CIELAB color difference between the patches (Ref. 46).
• CRI2012 (nCRI Version 2012): A graph of the 17 individual indices and Ra,2012; numerical value of Ra,2012
(based on the 17 indices); a graph of the samples (a'M, b'M) coordinates; a representation of the samples
illuminated by the Reference and Test sources; the color difference between the patches (Ref. 47).
• TM-30-15 and TM-30-20 / CIE 224: Numerical values of the Fidelity Index (Rf), the Gamut Index (Rg); the
fidelity index for skin (Rf,skin), the color fidelity (Rf,ces) for each of the 99 Color Evaluation Sample (CES),
and the color difference (DeltaE’) for each set of CES patches. Numerical values of the Local Color Fidelity
(Rf,h), Local Chroma Shift (Rcs,h) and Local Hue Shift (Rhs,h) for each of the 16 Hue Angle Bins. A graph of
the reference source, which is different from the source used in other color rendering metrics when the CCT
is between 4500 K and 5500 K, for TM-30-15, and between 4000 K and 5000 K, for TM-30-20; a bar graph
of the color fidelity by sample (Rf,ces); a bar graph of the color fidelity by Hue Angle Bin (Rf,h); a bar graph of
the chroma shift by Hue Angle Bin (Rcs,h); a bar graph of the hue shift by Hue Angle Bin (Rhs,h); a graph of
the average chromaticity (a'M, b'M) of the reference and test data of the Hue Angle Bins, which is used to
compute the gamut area; a Color Vector Graphic (CVG) used to evaluate color saturation and desaturation; a
plot of Rg versus Rf; and a visual representation of the 99 CES reference and test patches. TM-30-20 only:
Color Rendition Categories (Preference, Vividness, Fidelity) in three Priority Levels as defined in TM-30-20
Annex E. (Ref. 54-57-65).
• GAI (Gamut Area Index): Ref. 48.
• GAI and Ra: The arithmetic mean of GAI and Ra (the current CRI)) (Ref. 49).
• MCRI (Memory Color Rendering Index): Rm (general memory color quality index); Sa (degree of similarity);
Si (special color quality indicators of the ten objects) (Ref. 50).
• Data input:
• Instrument or file input; a connected instrument is NOT required for file input.
• Input file formats: CGATS or Plain text files; 380-400 nm to 700-730 nm spectral ranges; 5 nm or 10 nm
bandwidth. The file may contain one or more spectrums; you can drag-and-drop one or more files on the
"Load…" button or on the data table.
• Supported instruments: Any i1Pro series spectrophotometer with ambient adapter (the adapter is an
option in some models).
• Input is processed internally with a 5 nm bandwidth; 10 nm data is interpolated to 5 nm with the user-
selected spectral interpolation method (cubic spline / Lagrange).
• Data output:
• Custom export dialog: Select amongst the data used for the graphs, the general and specific metrics
indices, and the Test source data.
• Export all measurements or only selected measurements.
• Export in a single file report or in a batch of individual files (one file per measurement), or both options.
• The single file report or the individual files can be exported in either CGATS format, which can easily be
used for file input afterwards, or in Plain text format.
• TM-30-20 graphic reports: Generate graphic reports as per the TM-30-20 method guidelines (Ref. 57).
Three report types are available: Simple, Intermediate, and Full. These reports are saved as images in
PNG, TIF, BMP, or JPG format. The image resolution is selectable at 96, 150, 300, or 600 DPI.
• Measurement Conditions: M0, M1, M2, or M3; as defined in ISO 13655-2009 (as permitted by instrument).
• Reflection Density, with Absolute or Paper White base.
• Dot / Tone (Dot Area): Formulas:
• Murray-Davies
• Yule-Nielson with user-adjustable n Factor
• Spot Color Tone Value (SCTV) as per ISO 20654:2018
• Apparent Trap: Preucil (GATF) or Brunner formulas.
• Print Contrast, with Absolute or Paper White base.
• Hue error - Grayness - Saturation with Absolute or Paper White base.
• Density standards (as defined in ISO 5-3):
• ANSI Status A: Recommended for measuring densities of photographic color prints.
• ANSI Status E: Used mostly in Europe to measure printed material. It has a wide-band color response.
Equivalent to the DIN status.
• ANSI Status I: Has a narrow-band interference-type filter response. Equivalent to the DIN NB and SPI
statuses.
• ANSI Status T: The equivalent of ANSI Status E in North America. The difference with Status E is how
the yellow filter is weighted.
• Manual or Automatic CMYK filter selection
• Up to five measurements per tool; get the average; select one measurement, or the average, as a reference.
• Export a report formatted for a spreadsheet and a word processor.
• Important: An i1Pro 2 or i1Pro 3 which supports the M0 (Ill-A), M1 (D50), and M2 (UV-cut) Measurement
Conditions as defined in ISO 13655-2009 is required to use these tools (an i1Pro cannot be used!).
• Fluorescence Index (FI): This index requires only one printed sample; the index is obtained by computing the
color difference between a measurement made with the M2 (UV-cut) measurement condition and a
measurement made with either M0 (Illuminant A) or M1 (D50). The formula used to compute the color
difference can be any of the standard color difference equations listed below.
• Fluorescence Metamerism Index (FMI): This index evaluates if the combined appearance of two printed
samples varies between a reference Measurement Condition (M2, UV-cut) and a UV-inducing illuminant
(either M0 or M1); it is based on the HunterLab Metamerism Index. The FMI is identified as either FMI(M0) or
FMI(M1).
• Standard Observer: 2 degree (CIE1931) or 10 degree (CIE 1964).
• Fluorescence Index Color difference formula:
• CIELAB
• CIE94, i.e CIE94(1:1)
• CIE94 textile, i.e. CIE94(2:1)
• CIE94(2:2) (recommended by Berns for metamerism analysis)
• CMC(2:1)
• CMC(1:1)
• CIEDE2000
• Save all results in a report formatted for a spreadsheet and a word processor.
• Based on selected requirements of ISO 3664:2009, ISO 12646:2008 and ISO 12646:2014-Final Draft to
which are added user-selectable conditions.
• Data input: Instrument or file input; a connected instrument is NOT required for file input. For CRI and MI, 10
nm input is interpolated to 5 nm with a user-selected spectral interpolation method (cubic spline / Lagrange).
• ISO 3664 Viewing Conditions:
• P1: Prints: Critical comparison (requires an i1Pro with an ambient diffuser adapter)
• P2: Prints: Practical appraisal (requires an i1Pro with an ambient diffuser adapter)
• T1: Transparencies (direct viewing)
• Color monitors (the uniformity measurements can be done using the requirements of ISO 12646: 2008 or
ISO 12646:2014-Final Draft; see more details below)
• Measurements:
• Brightness: ambient illuminance (lux); monitor luminance (cd/m2).
• Chromaticity: u'v' Uniform Chromaticity Scale (UCS, CIE1976), 10 degree Observer (CIE1964)
• Correlated Color Temperature (CCT), in kelvin, of a monitor or ambient source.
• Color Rendering Index (CRI): CIE 13; also provides the index of each sample
• Daylight simulator Metamerism Index (MI) and Quality Grade: ISO 23603 / CIE S 012 (visible-range-only)
• Brightness uniformity (for P1, P2, and T1 Viewing Conditions): Measure the brightness, the CCT, the
chromaticity, the CRI and the MI for up to nine positions.
• Brightness uniformity as per ISO 12646:2008, Section 4.4 (for color monitors): The relative brightness of
WHITE, GREY, and DARK-GREY targets can be measured on a non-uniform 3 x 3 grid which favors the
monitor's center area. For the white targets, the CCT and chromaticity are measured as well.
• Tone uniformity, i.e. Color uniformity, as per ISO 12646:2014-Final Draft, Section 4.2.2 (for color
monitors): Measurements can be done on WHITE, GREY, and DARK-GREY targets positioned on a
uniform 5 x 5 grid. The color difference between the center and the other positions is computed using
CIEDE2000. For the white targets, the CCT and the chromaticity are measured as well.
• Tonality Evaluation, i.e. Grey/White Tone ratio uniformity, as per ISO 12646:2014-Final Draft, Section
4.2.3 (for color monitors): Measurements can be performed for up to twenty-five positions located on a
uniform 5 x 5 grid. Measurements need to be done with both WHITE and GREY patches for a given
position. The deviation of the Grey/White ratio is shown relative to the center position. For the white
targets, the CCT and the chromaticity are measured as well.
• Chromaticity "Target center":
• D50 for "P1", "P2" and "T1" (ISO 3664)
• D65 for "Color monitors" (ISO 3664)
• 2856 K, 3200 K, 3500 K, 4100 K, 4700, 5000 K (non ISO 3664)
• D55, D60, D75, D93 (non ISO 3664)
• CRI "Reference Illuminant":
• D50 for "P1", "P2" and "T1" (ISO 3664)
• 2856 K, 3200 K, 3500 K, 4100 K, 4700, 5000 K (non ISO 3664)
• D55, D65, D75 (non ISO 3664)
• Automatically assigned from the measured color temperature (CCT)
• MI and Quality Grade "Reference Illuminant":
• D50 for "P1", "P2" and "T1" (ISO 3664)
• D55, D65, D75 (non ISO 3664)
• Input file formats: CGATS or Plain text files; 380-400 nm to 700-730 nm spectral ranges; 10 nm bandwidth.
The file must contain one spectrum; you can drag-and-drop a file on the "Load…" button.
• Supported instruments: Any i1Pro series spectrophotometer. An ambient adapter is required for ISO 3664 P1
and P2 viewing conditions (the adapter is an option in some models).
• Save all results in a text report.
• Print a well-formatted one-page report which contains information dedicated to compliance-type reports.
• Get the RAL DESIGN Hue-Lightness-Chroma (HLC) coordinates of a color patch. L*a*b* and L*C*h (D65, 10
degree Observer) are also displayed.
• Data input: Instrument or file input; a connected instrument is NOT required for file input.
• Input file formats: CGATS or Plain text files; 380-400 nm to 700-730 nm spectral ranges; 10 nm bandwidth.
The reflectance values shall be defined between zero and one, with one representing full (100%) reflectance
or between 0 and 100. The file may contain one or more spectrums; multiple files can be inputted with drag-
and-drop on the "Load file…" button. The input data is immediately converted and saved in a CGATS text file.
• If you are using an i1Pro 2 with the “i1Pro / i1Pro 2 (XRGA)” driver, an i1Pro 3, or an i1Pro 3 Plus, all
measurements will be taken with the three Measurement Conditions, M0 (Ill-A), M1 (D50), and M2 (UV-cut),
as defined in ISO 13655-2009. If you are using an i1Pro, or an i1Pro 2 with the “i1Pro / i1Pro 2 (non-XRGA)”
driver, the program will select the default measurement conditions supported by the instrument.
• Save all results from an instrument measurement in a text report. The report includes the spectral data for all
applicable Measurement Conditions.
• Measure the whiteness, tint, brightness, fluorescence, and opacity of white papers.
• Whiteness and Tint formulas: CIE-GANZ 82, CIE-Uchida, CIELAB-HE 2007.
• Brightness and Fluorescence: Based on TAPPI T452 / ASTM D985.
• Note: There are sufficient differences between an i1Pro series spectrophotometer and an instrument
designed expressly for the requirements of TAPPI T452 or ASTM D985, that you should not expect to
match the results obtained with qualified equipment. However, the instrument geometry is close, the
lamp source is of the required type, the blue wavelength band is simulated in software, and the reference
white can be derived from the standard instrument calibration in reflectance.
• Opacity: As per CGATS.5 / ISO 2471.
• Data input: Instrument input only (except UV filter). An i1Pro M0 or an i1Pro 2 M0/M1/M2 must be used.
• Input file formats (UV filter): CGATS or Plain text files; 380-400 nm to 700-730 nm spectral ranges; 10 nm
bandwidth. The transmittance values shall be defined between zero and one, with one representing full
(100%) transmittance. The file must contain one spectrum.
• Important: Fluorescence measurements with an i1Pro also require a thin, transparent, UV filter, which is not
provided. You can use the default UV filter spectrum, load a filter spectrum from a file, or measure your own
filter and assigned it as the program default.
• Note: Whiteness, Tint, Brightness, and Fluorescence measurements require a compliant white backing.
Opacity measurements require a compliant black backing. Backing are not provided but compliance checking
tools are included (see below).
• White backing compliance: Check the compliance of a white backing as per ISO 13655.
• Black backing compliance: Check the compliance of a black backing as per ISO 5-4.
• Derive a UV filter spectrum : Derive the spectral characteristics of an unknown UV filter to be used for
fluorescence measurements
• Export the results and the measurements in a CGATS compliant text file.
• Export an image of the spectrums in PNG, BMP, or JPG format. You can select to generate the image at a
1X or 2X scale (double resolution and size).
Windows
Minimum:
• Windows 7
• 1.0 GHz
• 2 GB RAM
• 1024 x 768, 32 bit color (the tool bar should be hidden to maximize the display area)
Recommended:
• Compatible with Windows 7 / Windows 8.1 / Windows 10.
• 1.0+ GHz
• 2+ GB RAM
• 1280 x 1024, 32 bit color
• Calibrated display
Mac OS
Minimum:
• Intel Mac: Mac OS X 10.10.5 (Yosemite)
• 1.0 GHz
• 2 GB RAM
• 1024 x 768, 32 bit color (the task bar should be hidden to maximize the display area)
Recommended:
• Compatible from Mac OS X 10.10.5 (Yosemite) to macOS 10.15.5 (Catalina)
• 1.0+ GHz
• 2+ GB RAM
• 1280 x 1024, 32 bit color.
• Calibrated display
Note: Acrobat Reader is now available in two distribution modes, called “tracks”: “Continuous track” and
“Classic track”. The Continuous track, offered by default, is a “cloud” version which gets updated as
required, without user control. The Classic track is similar to the older program version which gets updated
at fixed intervals. If you prefer the older version, you can locate the download file by searching for “DC
Classic Track Release” with your favorite search engine. This link contains more information:
https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/whatsnewdc.html
In order to maximize the usefulness of the color patches displayed in CT&A, a calibrated display is thus
strongly recommended; however, a lack of calibration will not affect the numerical values or the conversion
accuracy. If you do not have access to dedicated display calibration hardware and software tools, we suggest
you use the following contrast adjustment procedure to optimize the display contrast and its dynamic range. If
you have access to calibration instruments, then you most likely already measured and assigned a custom ICC
profile for your display and no further calibration should be required; in this case, we suggest that you only
check your display, without making hardware adjustments (go over Steps 8 and 9).
Note: Monitors’ On-Screen-Displays (OSD) sometimes offer presets such as sRGB or Adobe (1998) RGB
which, when selected, disable the monitor contrast and brightness controls. In the absence of any calibration
equipment, you should select such settings and use the following procedures for checking purposes only.
Note: The following procedures were originally written for CRT (Cathode Ray Tube) displays. Since many LCD
(Liquid Crystal Displays) flat panels do not have individual contrast and brightness adjustments, you can only
use the procedures for evaluation. In addition, some LCD display technologies are more susceptible to exhibit
rapidly changing luminance, color and contrast characteristics with different view angles; if this is the case with
your monitor, it is important to maintain the same horizontal and vertical view angles relative to the display.
Important: Since displays can represent only a subset of the colors humans can see, a selected or measured
color in CT&A may well be out of the display profile range (gamut). When this happens, clip indicators are
shown in the bottom-left or bottom-right corner of the corresponding patch. Please note that no clip indicator
should appear while doing the following procedures.
Contrast Adjustment/Check
This procedure is based on Ref. 4.
1. Open the computer and let the display stabilize for at least 30 minutes (60 minutes plus recommended),
making sure that the screen saver does NOT start during this period.
2. Dim the room lights, and make sure no direct light comes through the room windows.
3. Start CT&A.
4. Open the Preferences dialog. This dialog is called with the "Edit/Preferences..." menu command in
Windows or the "CT&A/Preferences..." menu command in Mac OS X. Verify that the proper profile is
assigned to each display. If this is not the case, use your OS display control panel to change the
assignment (the CT&A dialog can remain open). In the “Math” tab, uncheck “Always use a single
parameter gamma”. Close the Preferences dialog when done.
5. Open the RGB vs RGB tool window and close all other tool windows. Set both sides to R'G'B' space
mode and R'G'B' data input (i.e. the “L*a*b*/L*u*v* input” checkbox should NOT be checked!). Select a
space whose gamma corresponds to your display; this will often be sRGB for a standard gamut display
and Adobe (1998) RGB for a wide gamut display, but it can also be eci_RGB_v2 with a L-star gamma.
You can also define a custom RGB space with a gamma of your liking. Assign the same space on both
sides.
6. Bring the "Y" sliders of both spaces to zero (i.e. pure black with R’, G’ and B’ = 0).
7. Raise the "Y" slider of Space #2 to 16 (i.e. R’G’B’=16). This very dark gray is displayed in the smaller
center patch.
8. (Do NOT perform if checking) Set the display contrast control, usually represented by a circle with two
contrasting halves, to its highest setting.
9. (Do NOT perform if checking) Adjust the brightness control, usually represented by a "sun" logo
(circle with rays), to make the center patch as dark as possible, but not black.
10. If you have problems distinguishing the contrast between the two patches, simultaneously raise all the
sliders of Space #2 by increasing the "Y" slider by steps of 1 or 2 and readjust the display brightness
control. On the other hand, you can try lowering the Space # 2 values and further increase the display
brightness until it is no longer possible to do Step 9. It is not unusual to be able to see the center patch
when Space #2 is as low as 12 (i.e. R’G’B’=12), or even lower.
Highlight Check
This procedure enables you to verify that your display is not saturated when displaying pure white, i.e., that it
can show details in the highlights. The contrast adjustment/check procedure should be done prior to this check.
1. Open the Preferences dialog. This dialog is called with the "Edit/Preferences..." menu command in
Windows or the "CT&A/Preferences..." menu command in Mac OS X. Verify that the proper profile is
assigned to each display. If this is not the case, use your OS display control panel to change the
assignment (the CT&A dialog can remain open) and redo the Contrast Adjustment/Check procedure
described above. In the “Math” tab, uncheck “Always use a single parameter gamma”. Close the
Preferences dialog when done.
2. Open the RGB vs RGB tool window and close all other tool windows. Set both sides to R'G'B' space
mode and R'G'B' data input (i.e. the “L*a*b*/L*u*v* input” checkbox should NOT be checked!). Select a
space whose gamma corresponds to your display; this will often be sRGB for a standard gamut display
and Adobe (1998) RGB for a wide gamut display, but it can also be eci_RGB_v2 with a L-star gamma.
You can also define a custom RGB space with a gamma of your liking. Assign the same space on both
sides.
3. Set all Space #1 RGB values to 255 and all Space #2 RGB values to 251.
4. You should be able to see the lower intensity center patch; these settings correspond to a 1,57
DeltaE*ab color difference in eci_RGB_v2, 1,38 in sRGB, and 1,34 in Adobe (1998) RGB. If the patches
look the same, lower the Space #2 values until you see a difference. You could try lowering the display
brightness to see if it affects saturation but this may also affect your contrast adjustment and ability to
distinguish shadows, so we do not recommend that you change any setting when checking highlights.
Improvement:
• Spectral data in CGATS and TEXT files (see “Input file formats” in Specifications - Spectral tools):
In the past, if 380 nm data was detected, 730 nm data was required; also, if spectral data started at
400 nm, the program looked only for 700 nm data. Now, data is required between 400 and 700 nm.
Any valid data between 380 and 730 nm will be used. Missing data will be extrapolated to complete the
380 to 730 nm range necessary for processing. Spectral data lower than 380 nm and higher than 730
nm is discarded.
o This improvement affects the following tools:
CRI, ISO 3664+, Metamerism Index (color patches, illuminant), RAL DESIGN, Whiteness.
Bug fixes:
• CRI tools: Now will not round the data on the chroma shift graph of TM-30-20 reports and will show a
decimal for values between -10 and +10.
• Density tools:
o The “Show (Ref.)” checkbox is now unselected and disabled when first opening the tool.
o SCTV is computed even if another formula (Murray-Davies or Yule-Nielson) is selected in the
“Dot / Tone (Dot Area)” tool. The problem was noticeable when saving the measurements.
o Now properly displays the measurement conditions in the dialog and file name when saving
Density measurements for instruments which do not support multiple measurement conditions.
• RGB vs RGB tool: Now updates the RGB vs RGB chromaticity diagram to the mouse-down event
position when rapidly dragging the mouse afterwards with the mouse button down. Before the fix the
canvas was updated only when not moving, moving slowly, or bringing the mouse outside the
chromaticity graph.
Other:
• CRI tools: Replaced TM-30-18 references by TM-30-20 (Ref. 57). The TM-30-20 version integrates
Annex E and Annex F (Ref. 67-68) which were published separately after TM-30-18 was issued and it
has a new page layout. The computation methods and the technical content are the same in both
versions.
• New compiler version version with revised APIs. This compiler improves compatibility with recent OSs.
Bug fix:
• TIFF images from CT&A can now be opened in Photoshop CC 23: TIFF images from CRI / TM-30-18
reports and ISO 3664+ / ISO 12646 Targets now include the specific data required by CC 23. Adobe
may also have fixed the issue so that TIFF images from previous CT&A versions will also open.
Other:
• i1Pro 2 and i1Pro 3 instruments (from X-Rite): The libraries/DLL (Windows) and Frameworks (macOS)
have been updated to their latest versions.
Bug fix:
• (macOS Big Sur 11) RGB vs RGB tool: Improved program stability when resizing the window.
New feature:
• ISO3664+ tools: Now shows the MI value as well as the MI Quality Grade on the screen.
Improvement:
• CRI tools: The TM-30 Color Vector Graphic (CVG) graph is now smoothed (screen and reports).
Bug fix:
• (Mac 64 bit only) Display profile recognition: Now properly identifies the profile of additional displays
connected to a given computer instead of assigning the main display profile. This bug affected the
rendering of patches on secondary displays.
New features:
• Added support for the X-Rite i1Pro 3 and i1Pro 3 Plus spectrophotometers:
o These instruments are available in all tools.
o Supported measuring modes: reflectance, emission, ambient illumination. These modes are
not available in all tools.
o M0/M1/M2 Measurement Conditions: available in all tools with reflectance input.
o M3 Measurement Conditions (i1Pro 3 Plus): available in the Density and Graph tools.
• Munsell tools: A bidirectional set of tools to convert FROM and TO Munsell Hue Value/Chroma (HVC).
o Convert from Munsell to RGB and L*a*b*.
o Convert from RGB to Munsell.
o RGB spaces: The 24 standard spaces plus the Custom space defined in the RGB vs RGB tool.
o Convert from L*a*b* to Munsell.
o L*a*b* illuminants: 15 predefined illuminants plus a Custom illuminant defined in the RGB vs
RGB tool.
o Measure spectral data and convert to Munsell.
o Supported instruments: X-Rite i1Pro series spectrophotometer. Measurements Conditions: M0,
M1, M2 (when supported by the instrument).
o Instruments supported in 32 bit and 64 bit packages.
o Export a report with tab-delimited data that can be directly imported in a spreadsheet program
and opened in many text editing applications. The report spectral measurements can also be
read by software, such as BabelColor PatchTool, which can open CGATS compatible files.
• Density tools: Added support for the M3 (Pol.) Measurement Conditions. Requires an i1Pro 3 Plus.
• Graph tools: Added support for the M3 (Pol.) Measurement Conditions. Requires an i1Pro 3 Plus.
• CRI tools: Added computation and display of TM-30-18 Color Rendition Categories (Preference,
Vividness, Fidelity) in three Priority Levels as defined in TM-30-18 Annex E. The Color Rendition
performance can be included in text file and graphics reports.
Other:
• (Mac 64 bit only) The provided 64 bit install files are compliant with current Apple notarization
requirements. Notarization is required for some software in macOS 10.14.5 and is mandatory for all
software starting with macOS 10.15. Please note that any software meeting notarization requirements
may not be fully compatible with a given OS version; see the CT&A system requirements for more
information.
• (Mac) The program is now released in a 64 bit package only. This change main effect is to drop
support of legacy instruments for which 64 bit DLLs/Frameworks are not available. Please consult the
Toolbar “Supported instruments” section for more information.
Improvements:
• Whiteness tools: Now check if there is a measurement with a filter before changing the filter setting.
• (Mac) Now assigns more noticeable background colors to many data fields for “non-English” systems.
Bug fixes:
• Density tools:
o Now recomputes the Dot / Tone (Dot Area) and Apparent Trap when remeasuring the paper.
o The paper status stays green if new paper measurements fail. Old measurements remain valid.
o Now recomputes the SCTV paper data when changing the Measurement Conditions.
o Now exports the correct “Average D_sol” when saving SCTV data.
• CRI tools: The program will now correctly reselect a previously selected row when a non-selected row
is deleted or when many rows without the selected row are deleted.
• Spyder5 and SpyderX: The program now properly detaches these instrument libraries when the
instrument is deselected.
• RGB vs RGB Custom space: Now shows the proper primaries when the default Custom space is
shown the first time the Custom space dialog is opened.
Improvements:
• NTSC RGB space (RGB vs RGB tool): Tweaked the RGB to XYZ and XYZ to RGB matrices of the
NTSC RGB space in order to better match the space illuminant coordinates.
Bug fix:
• (Mac 64 bit only) Fixed a bug affecting all windows showing color-corrected patches. The bug
generated a NilObjectException error message before shutting down the program. The problem
affected the most recent macOS versions (Yosemite, Catalina).
Other:
• macOS 10.15 Catalina support: At the time of writing this manual no issues were found while using this
version of CT&A with macOS 10.15.1 Catalina. Please see the CT&A system requirements for other
OS requirements.
New features:
• Added support for the Datacolor SpyderX colorimeter:
o This instrument is currently used in the "RGB vs RGB" tool (and not in the spectral tools).
o Supported models: SpyderX Elite, SpyderX Pro.
o Select any of the four Datacolor-provided calibration matrices: Any monitor, Standard gamut
LED, Wide gamut LED, GB LED.
o Instrument supported in 32 bit and 64 bit packages.
• Added support for the Datacolor Spyder5 colorimeter:
o This instrument is used in the "RGB vs RGB" tool (and not in the spectral tools).
o Supported models: Spyder5ELITE, Spyder5PRO, Spyder5EXPRESS.
o Select any of the four Datacolor-provided calibration matrices: Any monitor, Wide gamut LCD
w/CCFL backlight, Wide gamut LCD w/RGB LED backlight, Wide gamut LCD w/CCFL2
backlight.
o Select between two measurement speeds.
o Instrument supported in 32 bit and 64 bit packages.
Bug fixes:
• CRI tools:
o The program will not crash when generating a TM-30-18 report that contains non-valid
numbers derived from severely non-compliant light sources (such as red only).
o A Duv too big is now shown as “OOR” (Out-Of-Range) instead of “1000” (an extremely high
Duv value) in TM-30-18 reports.
o The CRI tool and CRI reports now show “OOR” (Out-Of-Range) instead of “999 K” for values
too low and “100001 K” for values too high.
o (Mac) Changed the tool shortcut letter from “command+shift+Q” (a log-out shortcut) to
“command+shift+T”. While this was not a problem in Windows, we changed the tool shortcut
letter from “Ctrl+shift+Q” to “Ctrl+shift+T” in Windows.
• RGB vs RGB tool: Now properly refreshes the DeltaE formula menu and the Delta labels when the tool
window is first opened.
• (Mac 64 bit only) Selecting "Try to connect again..." in the Instrument menu now correctly selects the
previous instrument.
Other:
• Instrument calibration is now required before the next measurement whenever the instrument is
changed.
• A “Forced deactivation…” menu item is added to the Help menu. This procedure may be helpful when
the status of the Product Key activation is ambiguous (i.e. when the “Activate” menu is available even if
the program was known to be activated on this specific computer).
• (Mac 64 bit only) The provided 64 bit install files are compliant with current Apple notarization
requirements. Notarization is required for some software in macOS 10.14.5 and will be mandatory for
all software starting with macOS 10.15. Please note that any software meeting notarization
requirements may not be fully compatible with a given OS version; see the CT&A system requirements
for more information.
New features:
• IES TM-30-18 / CIE 224:2017 (CRI tools): Added the 2018 version of the IES Method for Evaluating
Light Source Color Rendition to the CRI tools ( https://www.ies.org/ ).
o TM-30-18 is an update of TM-30-15 required in order to harmonize it with CIE 224:2017 (which
is only concerned by the Color Fidelity Index (Rf)). The Rf of TM-30-18 and CIE 224:2017 are
identical.
o In addition to the text file report which is available to all metrics, it is possible to generate
graphic reports as per the TM-30-18 method guidelines. Three report types are available:
Simple, Intermediate, and Full. These reports are saved as images in PNG, TIF, BMP, or
JPG format. The image resolution is selectable at 96, 150, 300, or 600 DPI.
• TM-30-15 and TM-30-18 (CRI tools): We now compute the Local Chroma Shift (Rcs,h) and Local Hue
Shift (Rhs,h) for all Hue Angle Bins in addition to the previously available Local Color Fidelity (Rf,h).
o It is now possible to display the Local Chroma Shift or Local Hue Shift graph in the CRI tool
window.
o It is now possible to export the Local Chroma Shift and Local Hue Shift data in text reports
(You can also export Local Chroma Shift and Local Hue Shift data in graphic reports for
TM-30-18).
• Spectral interpolation (“Math” tab of the Preferences dialog):
o In previous versions, when required, interpolation of 5 nm values from 10 nm spectrums was
performed with the “Lagrange” method. You can now select between the “Cubic spline” and the
“Lagrange” methods.
o Used for all computations in the CRI tools.
o Used for the CRI and the Visible Metamerism Index (MI, ISO 23603) in the ISO 3664+ tool.
o Used to compute the CRI in the Graph and MI tools.
Bug fix:
• RGB vs RGB tool (Windows version only): Fixed the issue where the RGB vs RGB window minimal
size was not properly assigned. This problem could be seen in systems with high resolution displays
where the display magnification is higher than 100%.
Other:
• TM-30-15 and TM-30-18 (CRI tools):
o Moved the CIECAT02 gamut fix option to the “Math” tab of the Preferences dialog.
• CRI export data dialog TM-30 data fields:
o Added the Local Chroma Shift (Rcs,h) and Local Hue Shift (Rhs,h) data fields.
o Removed the less pertinent chromaticity and CVG data fields (J’a’b’, a’b’(avg), CVG data).
o You can export either TM-30-15 or TM-30-18 data, or both.
• CRI tools: Tweaked the Out-Of-Range colors and thresholds of the CRI metrics results.
New features:
• Density tool: Added the SCTV formula for “Dot / Tone (Dot area)” measurements (SCTV: Spot Color
Tone Value, as defined in ISO 20654:2018 “Graphic technology — Measurement and calculation of
spot colour tone value”).
• RGB vs RGB tool:
o It is now possible to define an RGB space with negative chromaticity coordinates when using
the Custom RGB space dialog. As before, the Custom RGB space settings can be used to
generate an ICC profile.
o Because negative chromaticities may result in negative xyY and XYZ values, an option to clip
or not the xyY and XYZ data values to zero was added to the “Math” tab of the Preferences
dialog.
o Four (4) new standard RGB spaces were added to the RGB space selection menu: ACES
AP0; DCI P3 Theater; Display P3 (used on Macs by Apple); Rec. 2020 (UHDTV).
Improvements:
• RGB vs RGB tool: The following control settings are now saved and reassigned when the program
reopens: RGB space selection menu; RGB input values; L*a*b*/L*u*v* menu; L*a*b* / L*u*v* in D50
checkbox; L*a*b*/L*u*v* input values; DeltaE* formula selection menu.
Bug fixes:
• Activation: Fixed an issue where an OutOfBoundsException message was shown if attempting
activation when the computer Ethernet cable was not connected to a router. The OFFLINE activation
dialog is now shown.
• RGB vs RGB tool (macOS): Fixed the issue where the text within some buttons was clipped in high
resolution displays.
Other:
• This version was compiled in 32 bit executable files (Mac and Windows) and a 64 bit executable
package is also available for Mac.
• (Mac 64 bit only) Instrument support changes:
o The following instruments/drivers are no longer available:
Eye One Display, i1Pro / i1Pro 2 (non-XRGA).
o The following instruments/drivers remain available:
i1Display Pro, i1Pro / i1Pro 2 (XRGA).
• (Mac) The minimum system requirement is now Mac OS X 10.9.5 (Mavericks).
New features:
• Metamerism Index (MI) tools:
o Added the Metameric Index (MI) computed according to CIE15:2004, Section 9.2.2.3. This
index is computed when the Special Metamerism Index (SMI) obtained with the Reference
illuminant is NOT zero. The MI is derived with a Multiplicative Correction applied to the data of
the Sample patch obtained with the Test illuminant.
o Note: The MI computed in previous versions, based on the HunterLab formula, is still available.
It is now identified as “MI (HunterLab)”.
o File input: It is now possible to enter spectral data from a file in addition to measurement from
an instrument. A connected instrument is NOT required for file input. Input can be assigned to
any of the supported Measurement Conditions (M0, M1, or M2).
o Input file formats: CGATS or Plain text files; 380-730 nm or 400-700 nm spectrum ranges; 10
nm bandwidth. The file may contain one or more spectrums; multiple files can be inputted with
drag-and-drop.
o In addition to the MI report, you can now save the Reference and Sample patches spectrums
in a CGATS format text file, which can easily be used for file input afterwards.
• RAL DESIGN tool:
o File input: It is now possible to convert spectral data from a file. A connected instrument is NOT
required for file input. The input data is immediately converted and saved in a CGATS format
text file.
o Input file formats: CGATS or Plain text files; 380-730 nm or 400-700 nm spectrum ranges; 10
nm bandwidth. The file may contain one or more spectrums; multiple files can be inputted with
drag-and-drop.
o Output data: L*a*b* computed with Illuminant D65 and the 10 degree Observer; the color in
RAL DESIGN notation; the individual RAL Hue, Lightness, and Chroma (HLC) components.
Improvements:
• CRI tools: Data table interface improvements.
o Now updates the CRI window when browsing in the data table with the up-down arrows; there
is no need to do a carriage return.
o Will now select all ambient sources added by drag-and-drop in the data table.
o The last input is always selected for display purposes and the data table is automatically
scrolled to the bottom.
o When measuring a light source with an instrument, the sample name is selected and you can
edit it immediately.
• FluoCheck tools: When saving the report from an instrument measurement, the report now includes the
spectral data for all Measurement Conditions.
• RAL DESIGN tool: When saving the report from an instrument measurement, the report now includes
the spectral data for all applicable Measurement Conditions.
• RGB vs RGB tool: The CIEDE2000 color difference is now computed with the alternate three terms
form equation in which the fourth term associated with rotation (RT) is now integrated with the chroma
and hue differences. The DeltaE* display of the RGB vs RGB tool now shows the weighted ∆L00, ∆C00,
and ∆H00 values (and ∆h’), instead of the unweighted ∆L*, ∆C*, and ∆H* values (and ∆h).
• Preferences – Color tab: The dialog now includes buttons which open various folders where user and
system display profiles are stored.
Other:
• Preferences – Color tab (Mac): Because Apple ColorSync is deprecated, it is no longer possible to
provide the path of a display profile. The name of the profile assigned to a monitor is still available.
• Windows OS: Windows Vista is no longer supported.
• i1Pro DLL (Windows): Version 4.2.3 of the library (i1Pro.dll) is now provided with the program.
New features:
• IES TM-30-15 (CRI tools): Added the IES Method for Evaluating Light Source Color Rendition to the
CRI tools ( https://www.ies.org/ ).
o Data output: The Fidelity Index (Rf); the Gamut Index (Rg); the fidelity index for skin (Rf,skin);
the color fidelity (Rf,ces) for each of the 99 Color Evaluation Sample (CES); the color fidelity
(Rf,h) for each of the 16 Hue Angle Bins; the chromaticity coordinates (J’a’b’) of all CES
reference and test patches; the color difference (DeltaE’) for each set of CES patches; the
average chromaticity coordinates (a'M, b'M) of the Hue Angle Bins; and the normalized
chromaticity data used to draw the Color Vector Graphic (CVG).
o Graph displays: A graph of the reference source, which is different from the source used in
other color rendering metrics when the CCT is between 4500 K and 5500 K; a bar graph of the
color fidelity by sample (Rf,ces); a bar graph of the color fidelity by Hue Angle Bin (Rf,h); a
graph of the average chromaticity (a'M, b'M) of the reference and test data of the Hue Angle
Bins, which is used to compute the gamut area; a Color Vector Graphic (CVG) used to
evaluate color saturation and desaturation; a plot of Rg versus Rf; and a visual representation
of the 99 CES reference and test patches.
o Data input: Instrument or file input; a connected instrument is NOT required for file input.
o Input file formats: CGATS or Plain text files; 380-730 nm or 400-700 nm spectrum ranges; 5
nm or 10 nm bandwidth. The file may contain one or more spectrums; multiple files can be
inputted with drag-and-drop.
o Supported instruments: Any i1Pro or i1Pro 2 with ambient adapter (the adapter is an option in
some models).
o Input is processed internally with a 5 nm bandwidth; 10 nm data is interpolated to 5 nm.
o Custom export dialog: Select amongst the data used for the graphs, the general and specific
metrics indices, and the Test source data.
o Export all measurements or only selected measurements.
o Export in a single file report or in a batch of individual files (one file per measurement), or both
options.
o The single file report or the individual files can be exported in either CGATS format, which can
easily be used for file input afterwards, or in Plain text format.
• ISO 3664+ tools: Data entry forms were added to fill the reports description data fields. The forms
appear when you press the ‘Print report…’ button. Two forms are presented, one for the P1, P2, and
T1 Viewing Conditions, and another for the Color monitors Viewing Condition.
Improvements:
• CRI tools:
o You can now select one or two of the available metrics, in any order, for better display use.
o A separate button was added to load a file from an input menu; this is useful if an instrument is
not connected when you use the CRI tools. You can also drag and drop one or more files on
the button (you can still drag and drop files on the data table!).
o You can now open files with more than one spectrum.
o You can now also select the CGATS file type for ‘One file’ reports; this is useful if you want to
open all your measurements from one file afterwards.
o A ‘Resample’ option was added to the ‘Spectrum bandwidth’ section of the CRI export dialog.
This option is recommended when you export measurements made with a 5 nm bandwidth to a
10 nm bandwidth.
• ISO 3664+ tools:
o A separate button was added to load a file (with one spectrum) from an input menu. You can
also drag and drop one (1) file on the button.
o Because of this new button, you can now load a file even if an instrument is NOT connected!
Other:
• New licensing system:
o Licensing is now based on a ‘Product Key’ which is used to activate a specific computer.
o You can transfer a Product Key to another computer by deactivating the first computer and
activating the second one. If you are connected to the Internet, this process is free and you
can repeat it as you require. If the computer is not connected to the Internet, offline activation
and deactivation is possible but a service fee is required for each activation; this fee can be
paid from the BabelColor Web site.
o The same key can be used for the Mac and Windows versions (one OS at a time!).
o Once a Product Key is activated on a computer, an Internet connection is not required.
New feature:
• RGB vs RGB tool: Added computation and display of the Web Content Accessibility Guidelines
(WCAG) Contrast Ratio for text content ( https://www.w3.org/TR/2008/REC-WCAG20-20081211/ ).
o Get the Contrast Ratio as well as Go/No-Go flags for the Minimal contrast requirements (Level
AA) and for Enhanced contrast (Level AAA), for both Normal text and Large text.
o Get the Contrast Ratio and contrast acceptance data for either one of the selected colors
against a white or black background, and for one color against the other.
o The WCAG results can be printed in a text-based report.
Improvements:
• Display profile:
o When rendering a color patch, the program uses the profile assigned to the display
corresponding to the window position. If the window is moved to another display, the patches
are rendered with the new display profile; there is no need to manually select a profile in multi-
display systems.
o The Preferences dialog now shows the names and file locations of the profiles assigned to all
connected displays. It also shows the profile corresponding to its location.
• (Mac) The program is now compiled using the ‘Cocoa’ Framework instead of the ‘Carbon’ Framework,
which was made possible by dropping support for PowerPC. Some of the effects of this change are:
o GUI appearance; for instance, the windows can now be resized by dragging any edge.
o More accurate color rendition with wide gamut displays, and, for all displays, a better match
with the numbers shown by the Mac ‘Digital Color Meter’ Utility.
Bug fixes:
• CRI: The patches displays are now erased when all measurements are deleted.
• Whiteness tools: Now shows the percentage sign for opacity in the saved image.
Bug fixes:
• Graph and Whiteness tools: Solved an issue where in some OS configurations the saved image was
incomplete and was not generated with a 2X scale.
• RGB vs RGB tool: Illuminance (ambient) measurements with the i1Display Pro are now provided with the
correct scaling.
Other:
• (Windows) The Help manual is no longer available in a self-contained compiled HTML application; it is now
provided as a PDF file.
New features:
• ISO 3664+ tools / Color monitors: Added support for measuring the Tone uniformity (i.e. Color uniformity,
Section 4.2.2) and Tonality Evaluation (i.e. Grey/White Tone ratio uniformity, Section 4.2.3) requirements of
ISO 12646:2014-Final Draft.
• Measurements are performed on targets located on a 5 x 5 uniform grid.
• Measurements can be performed with White, Grey, and Dark-Grey targets.
• Export a spreadsheet savvy text report or print a well formatted one-page report which presents the
overall characterization information.
• Built-in dialog to create image files of targets for any display size. Separate files are generated for the
White, Grey, and Dark-Grey target patches. File formats: PNG or TIFF; RGB; 8-bit.
Improvements:
• ISO 3664+ tools / Color monitors: Improved the ISO 12646:2008 Brightness uniformity measurements
interface (3 x 3 non-uniform grid).
• Measurements can now be performed with White, Grey, and Dark-Grey targets instead of just White.
• Built-in dialog to create image files of targets for any display size. Separate files are generated for the
White, Grey, and Dark-Grey target patches. File formats: PNG or TIFF; RGB; 8-bit.
• When doing measurements with the 'Take all' sequence, you can now change the target position at
anytime (if you want to go back to redo a bad measurement for instance).
Other:
• Complete revision of Tutorial 8 of the Help manual (Measure your display characteristics with the ISO 3664+
tools).
• (Windows) The minimal system requirement is now Windows Vista. As previously announced, CT&A Version
4.2.1 was the last version to support Windows XP.
• (Mac) The minimum system requirement is now Mac OS X 10.6 10.7. As previously announced, CT&A
Version 4.2 was the last version to support PowerPC. Future CT&A versions may require Mac OS X 10.7
(Lion) or newer.
Bug fix:
• For Windows XP ONLY: The 'i1Pro / i1Pro 2 (XRGA)' instrument selection can make CT&A 4.2 b316 close
unexpectedly on Windows XP computers. The problem was fixed by replacing the software libraries of the
i1Pro Software Development Kit (SDK) Version 4.2.0 by those of an older SDK; as a consequence, the menu
to check i1Pro / i1 Pro 2 lamp restore, introduced in CT&A 4.2, is not available in the software package
dedicated to Windows XP.
New features:
• CRI (Color Rendering Index) tools: Added a set of tools to evaluate the color rendering properties of white-
light sources. The tools comprise the current CRI standard as well as proposed replacement metrics, and
new metrics for gamut area and memory colors.
• Test source data: CCT (kelvin); Duv (CIE1960); brightness (lux); LER (Light Efficiency Ratio, in lm/W);
the Reference source (a blackbody or a D-Series illuminant).
• CRI (Color Rendering Index): A graph of the 14 individual indices and Ra; numerical values of Ra (a
general score based on the first 8 indices and better known as the current CRI), R9, R(9-14) (for indices
9 to 14) and R(1-14) for indices 1 to 14; a graph of the samples (a*, b*) coordinates; a representation of
the samples illuminated by the Reference and Test sources; the CIELAB color difference between the
patches. Ref.: CIE 13.3: 1995.
• CQS (Color Quality Scale, NIST Version 9.0.3): A graph of the 15 individual indices and Qa; numerical
values of Qa (general score based on the 15 indices), Qf (fidelity index) and Qg (relative gamut area); a
graph of the samples (a*, b*) coordinates; a representation of the samples illuminated by the Reference
and Test sources; the CIELAB color difference between the patches. Ref.: Wendy Davis, Yoshi Ohno,
"Color quality scale," Optical Engineering 49(3), March 2010, 033602-1 to -16.
• CRI2012 (nCRI Version 12.0): A graph of the 17 individual indices and Ra,2012; numerical value of
Ra,2012 (based on the 17 indices); a graph of the samples (a'M, b'M) coordinates; a representation of the
samples illuminated by the Reference and Test sources; the color difference between the patches. Ref.:
KAG SMET, J Schanda, L Whitehead, RM Luo, "CRI2012: A proposal for updating the CIE colour
rendering index," Lighting Res. Technol. 2013; 45: 689-709.
• GAI (Gamut Area Index): Ref.: Mark S. Rea, Jean P. Freyssinier-Nova, "Color Rendering: A Tale of Two
Metrics," COLOR research and application, Vol. 33, No. 3, June 2008, 192-202.
• GAI and Ra: The arithmetic mean of GAI and Ra (the current CRI). Ref.: Kevin Smet, Wouter R.
Ryckaert, Michael R. Pointer, Geert Deconinck, and Peter Hanselaer, "Correlation between color quality
metric predictions and visual appreciation of light sources," OPTICS EXPRESS, Vol. 19, No. 9, 25 April
2011, 8151-8166.
• MCRI (Memory Color Rendering Index): Rm (general memory color quality index); Sa (degree of
similarity); Si (special color quality indicators of the ten objects). Ref.: K.A.G. Smet, W.R. Ryckaert, M.R.
Pointer, G. Deconinck, P. Hanselaer, "A memory colour quality metric for white light sources," Energy
and Buildings 49 (2012) 216-225.
• Data input: Instrument or file input; a connected instrument is NOT required for file input.
• Input file formats: CGATS or Plain text files; 380-730 nm or 400-700 nm spectrum ranges; 5 nm or 10 nm
bandwidth. The file must contain only one spectrum; multiple files can be inputted with drag-and-drop.
• Supported instruments: Any i1Pro or i1Pro 2 with ambient adapter (the adapter is an option in some
models).
• Input is processed internally with a 5 nm bandwidth; 10 nm data is interpolated to 5 nm.
• Custom export dialog: Select amongst the data used for the graphs, the general and specific metrics
indices, and the Test source data.
• Export a single file report with all measurements or only the selected measurements.
• Export one file per measurement in either CGATS format, which can be used as file input, or in Plain text
format. All measurements or only the selected measurements can be exported in batch.
• Color Management Module (CMM) changed from LCMS 1.19 to LCMS 2.5.
• Full support of ICC v2 and ICC v4 profiles (LCMS 1.x had partial support of ICC v4 profiles).
Improvements:
• i1Pro and i1Pro 2:
• Now supports the i1Pro SDK Version 4.2.0.
• Added a menu to check i1Pro / i1 Pro 2 lamp restore. Lamp restoration is performed, if required, when
the menu is called.
• Improved algorithm to compute the CCT. The algorithm is now more accurate over a larger chromaticity area.
The acceptable isotemperature zone is between 1000 K and 100,000 K, with Duv (CIE1960) between +0.05
and -0.05.
• Tools which benefit from the improvement: RGB vs RGB, CRI, Graph, ISO 3554+, Metamerism Index.
New features:
• Toolbar window: The tools can now be accessed with new a top-level window which contains: a toolbar,
controls to select a measuring instrument, and status lights for the features supported by the connected
instrument (measurement modes, measurement conditions, spectral tools compatibility).
• Separate tools windows.
• One or more tool can be opened and used at any given time.
• Simply click on a window and make a measurement by pressing the i1Pro or i1Pro 2 button, even if
different measurement modes are selected in each window.
• The Main screen of previous CT&A versions is now called the "RGB vs RGB" tool. This tool opens in a
separate window, like the other spectral tools.
• Added support for the X-Rite i1Pro 2 spectrophotometer.
• This instrument is used in the "RGB vs RGB" tool and in all spectral tools.
• Supported models: i1Pro 2 M0/M1/M2 and i1Pro 2 M2-only.
• Supports the M0, M1, and M2 measurements mode for reflectance measurements.
• Supports X-Rite’s XRGA calibration standard for reflectance measurements.
• The i1Pro 2 can be used in CT&A on a PowerPC Mac with the older i1Pro driver; in this configuration,
the i1Pro 2 behaves as an i1Pro. The new i1Pro 2 features are available only in conjunction with the new
i1Pro 2 driver, which requires an Intel Mac with OS X 10.5.8+.
• i1Pro and i1Pro 2:
• Both the older i1Pro and the new i1Pro 2 drivers are provided. The i1Pro2 driver is XRGA compliant and
the older driver is NOT XRGA compliant. The new driver is referred to in CT&A as ‘i1Pro / i1Pro 2
(XRGA)’; the older diver is referred to as ‘i1Pro / i1Pro 2 (non-XRGA).’ You can thus make
measurements with your instruments with or without XRGA calibration.
• Calibration with the ‘i1Pro / i1Pro 2 (XRGA)’ driver always require that the instrument be positioned on its
white calibration tile, even for measurement modes other than reflectance.
• Added support for the X-Rite i1Display Pro colorimeter.
• This instrument is used in the "RGB vs RGB" tool (and not in the spectral tools).
• Supported models: i1Display Pro hardware sold by X-Rite (i.e. the retail version, part #EODIS3-XR).
Generic models sold by other companies (third parties, or OEM, part #EODIS-OEM) should also be
compatible. At this time we cannot say if we will support or not custom models sold by other companies
since separate agreements with these parties may be required. More specific info will be provided as
new models are released.
• CT&A can load and assign calibration matrices (contained in X-Rite Emissive Display Reference (EDR)
files) specifically designed for various display technologies, and which provide improved measurement
accuracy. Eight EDR files are supplied, including ones for OLED and Plasma displays; additional files
could be added in the future without a need to reinstall CT&A.
• Select between two measurement speeds.
• Note: On Mac, OS X 10.5+ is required (Mac Intel tested, PowerPC TBD).
• FluoCheck tools: Added a set of tools to measure the effect of substrate fluorescence on measured colors.
FluoCheck tools provide numerical data on the stability of a color under the M0, M1, and M2 Measurement
Conditions as defined in ISO 13655. A Fluorescence Index (FI) is obtained by measuring a color using either
M0 (i.e. Ill-A) or M1 (i.e. D50), and M2 (i.e. UV-cut), and computing the color difference between the two
measurements. When two colors are compared, a Fluorescence Metamerism Index (FMI) is obtained by
using the M2 measurements of the two colors, and either the M0 or M1 measurements (a different FMI is
computed relative to M0 and M1).
• An i1Pro 2 which supports the M0/M1/M2 measurement conditions is required to be able to use the
FluoCheck tools.
• Density, Graph, and Metamerism Index tools: In reflectance mode, and if using an i1Pro 2 which support the
M0/M1/M2 measurement conditions, you can now select the measurement condition.
• RAL DESIGN tool: In reflectance mode, and if using an i1Pro 2 which support the M0/M1/M2 measurement
conditions, you will now obtain the RAL DESIGN measurement for all these measurement conditions.
• Whiteness tools: If using an i1Pro 2 which support the M0/M1/M2 measurement conditions, you can now
obtain the fluorescence value by using the measurements corresponding to the M0 and M2 measurement
conditions, without the need for an external UV filter.
• Preferences: You can now select between Bradford or CIECAT02 as the Chromatic Adaptation Transform
(CAT) to be used for space conversion in the "RGB vs RGB" and "MI" tools, and to compute display colors.
New features:
• Spectral Tools - ISO 3664+: Added a tuning mode where measurements are automatically taken at user-
specified time intervals. This mode is particularly useful to tweak the chromaticity of a display.
• Custom RGB space dialog: Added the capability to save the RGB space as an ICC profile; save the profile
with an ICC or ICM extension.
Improvements:
• Spectral Tools - Graph: Added text entry fields for user-assigned Sample names.
• Spectral Tools - Graph: Added 3200 K (TV Studio lighting) in the Reference Illuminant menu when selecting
"S1 vs Illum." or "S2 vs Illum."
• Spectral Tools - ISO 3664+: The chromaticity target interface has been enhanced. The target layout indicates
if the measured color is too Red, too Green, or too Blue, and the relative position of out-of-range
measurements is now shown around the target.
• Spectral Tools - ISO 3664+: Added 3200 K (TV Studio lighting) to the Chromaticity and CRI menus.
• Munsell Color Deck: New higher accuracy Munsell database; this database also improves the conversion
accuracy towards the Munsell space.
Bug fixes:
• Main screen: The scrollbars' mouse wheel action will not change the Y, R, G, or B value when the scrollbars
are disabled. The scrollbars are now hidden when disabled.
• (Mac OS X 10.7-Intel) Due to a compiler bug, the scrollbars' elevator position remains visible when the
scrollbars are disabled. To fix the issue, the scrollbars are now hidden when disabled.
Other:
• Changed the Color Decks database file name to accommodate the new Munsell database. Users who have
customized their Color Decks will need to regenerate them.
New features:
• The program is now color-managed. The patches color in the main screen and in Spectral Tools are
corrected using the default, or user-selected, ICC display profile.
• Spectral Tools - Whiteness: Added a set of tools to measure paper whiteness, brightness, fluorescence, and
opacity. There are also tools to check if white and black backings are compliant. Some accessories are
required; see the Specifications for more information.
• Spectral Tools - Whiteness: Use this tool to measure color patches with and without UV-cut with only a non-
UV-cut Eye-One. A UV-blocking filter is required; see the Specifications for more information.
• Spectral Tools - Metamerism Index: There are now two custom Ambient inputs instead of one.
• Spectral Tools - Metamerism Index: You can save a measured Ambient illuminant to a file and load the
illuminant from a file.
• Spectral Tools - ISO 3664+: You can print well formatted one-page reports which contains information
dedicated to compliance-type reports.
• Spectral Tools - ISO 3664+: You can load an Ambient spectrum from a file instead of having to measure it.
• Custom RGB space: added the L* (L-star) tone response curve in the preset gamma list.
• Main screen: Additional patch layouts are available when increasing the screen dimensions. Compare color
patches on various backgrounds and see how text of each color looks like on black and white backgrounds,
as well as on a background of the other color.
• Main screen: The chromaticity diagram is now represented in color to help select a colors with a mouse-click,
and the coordinates are shown while moving the mouse over the diagram.
• Main screen: You can select a color on the chromaticity diagram with a mouse left-click or a mouse right-click
(ctrl + click on a one-button Mac mouse) and assign the input respectively to one space or the other.
• Main screen: Added the option to show the Planckian locus in the chromaticity diagram.
• Added a Page Setup menu to set the margins, paper size, and paper orientation prior to printing.
Improvements:
• Spectral Tools - Graph: You can save an image at twice the screen resolution for improved quality when
printing.
• Spectral Tools - ISO 3664+: Updated the requirements to those of ISO 3664:2009(E) (essentially, the
expected display Luminance is now 160 cd/m2 instead of 100 cd/m2)
• Main screen: The eciRGB 1.0 space has been updated to eciRGB_v2, with a L* (L-star) tone response curve.
• Main screen: You can change the instrument measurement mode with the mouse popup menu.
• The measuring instrument serial number and UV filter information is included in saved files and reports.
• The saved files and reports have been reviewed for presentation uniformity.
Bug fixes:
• Will show a warning message and not an error message when trying to save a file which is opened by
another application, or locked.
• (Mac OS X-Intel) The main screen gray background is uniform on program start; before the fix, it was
required to resize the display to refresh the background.
New feature:
• Spectral Tools - Graph: Added the capability to measure FLASH light sources (Flash mode).
Improvements:
• Spectral Tools - Graph: The CRI (Color Rendering Index) and the reference illuminant used to compute it are
now shown in the Graph tools for Ambient and Flash modes.
Bug fix:
• Fixed the problem where the program would go into an infinite loop with imported Color Decks of less than 20
chips (Note: Custom Color Decks are imported via BabelColor's PatchTool).
New features:
• Spectral Tools - Graph: A contextual menu was added to configure the horizontal and vertical graph grids.
• Spectral Tools - Metamerism Index: The reference illuminant for the Color Inconstancy Index (CII) used to be
fixed at D65. It is now possible to select among a list of 12 preset illuminants, or select a locally measured
ambient illuminant.
Improvements:
• Spectral Tools - ISO 3664+: The brightness uniformity can now be done on up to nine points as per ISO
12646 and the uniformity tool interface has also been improved. Target images for monitor brightness
uniformity measurements have been redone; they are included as individual files.
• Spectral Tools - Graph: Finer scaling steps for the graph display.
Bug fix:
• Fixed a computation problem when measuring reflectance samples (with an Eye-One Pro) with an RGB
space based on Illuminant E, in the main screen. The problem did not affect Emission or Ambient
measurements in the main screen, or any measurement type, including Reflectance, in the spectral tools.
Other:
• New tutorial: Measuring color patches on a display.
• (Windows) The Color Decks database is now located in the user "Documents" folder, where it can be more
easily accessed. As an additional benefit, there is no more a requirement to be a system administrator in
Windows XP; this change also makes the program better compliant to Windows Vista security requirements.
• Windows 98 is no longer supported; the last compatible version for this OS is 2.7.1.
Improvements:
• (Windows Vista) The drivers and system libraries (DLL) are now fully approved for this OS.
• (Mac) The program is now offered in Universal binaries and Intel packages.
Bug fix:
• Fixed the reload of the custom RGB space data when starting the program. This bug was introduced in
version 2.7.0.
• (Windows Vista) Windows Vista incorporates a Data Execution Prevention (DEP) feature which monitors how
applications access memory. In most Vista Home systems, the DEP setting is set, by default, to check only
the system programs and services; in this case, even before the fix, BabelColor CT&A started correctly.
However, the DEP setting can be changed by the user, either globally or on a program by program basis,
and its default setting may also vary for other OS configurations. BabelColor CT&A did not start when the
DEP was assigned to all applications, or to BabelColor CT&A only; this has been fixed.
New features:
• A contextual menu was added to most data fields, enabling a copy of all coordinates in a single mouse click.
The copied data, in Tab-delimited format, can be pasted in multiple columns within spreadsheets and
document tables.
• Because many LCD displays have a natural D60 white point, the D60 Illuminant was added in the selection
menus of the Graph Tools and the ISO 3664 Chromaticity measurement.
• The Generic RGB space (ColorSync default space on Mac OS X) was added to the RGB space list.
• Additional selections were added to the display space Options/Preferences setting, and the Generic RGB
space is now the proposed default selection for Mac OS X.
Improvements:
• Faster program startup.
• Faster loading of the Color Decks.
Bug fix:
• Fixed a data corruption problem when measuring emission data in the main screen after opening the ISO
3664 tools tab and coming back to the main screen (Note: there was no corruption when staying in the main
screen or using the other Spectral Tools).
Other:
• Changed the Color Decks database format.
Bug fix:
• Corrected a bug which made the program crash in certain operations when not registered.
Other:
• (Mac) The downloadable file is now compressed in a zip type archive.
Bug fix:
• Fixed a crash problem on Windows OS when using the program from account names defined with letters
having accented characters (Ex: Frãnz, János, etc.).
Other:
• The program name was changed to "BabelColor Color Translator and Analyzer", or "BabelColor CT&A" in
short form, to better differentiate it from other BabelColor products.
New features:
• Added the British Standard 5252F (BS 5252F) and RAL CLASSIC Color Decks.
Bug fix:
• The Eye-One Display and Eye-One Display 2 colorimeters are now properly recognized (Note: the Eye-One
Pro instruments were not affected by the problem).
New features:
TM
• Can input data from the Eye-One colorimeters and spectrometers
• Spectral tools which include:
1. Density tools: Reflection Density; Dot Area; Print Contrast; Apparent Trap; Hue error - Grayness -
Saturation;
2. Metamerism Index tools: HunterLab Metamerism Index (MI); Special Metamerism Index (SMI); Color
Inconstancy Index (CII); virtual light booth with ambient illumination input;
3. RAL tool: get the RAL DESIGN coordinates of a color patch;
4. Graph tools: analyze reflectance, ambient or emission spectrums; get ambient illuminance (lux), monitor
2
luminance (cd/m ), ambient Correlated Color Temperature (CCT, in kelvin); spectral math operations
(Add, Subtract, Average, Multiply); compare an ambient spectrum to ideal blackbodies or D-series
illuminants spectrums;
5. ISO 3664+ tools: viewing conditions assessment, with Color Rendering Index (CRI; CIE Publication 13),
ambient illuminance, monitor luminance, CCT, chromaticity, and illumination uniformity, light booth and
daylight simulators evaluation (CIE Standard 12, an updated version of CIE Publication 51).
• Export a spreadsheet savvy text report for most spectral tools (Density, Metamerism Index, Graph, ISO
3664+) and export an image of the spectral graphs.
Bug fix:
• Fixed a registration issue associated with operating systems set in languages using double-bytes font
encoding (Unicode), languages such as Japanese, Chinese, etc.
New features:
• A custom RGB space can now be defined by the user (RGB vs RGB menu).
• A custom D-series or blackbody illuminant can be defined using the source temperature (in kelvin).
• Export a spreadsheet savvy text report that contains all the parameters required to define and compute the
custom RGB space coordinates.
• Get the Bradford chromatic adaptation matrix between the custom Illuminant and many standard Illuminants.
New feature:
• Addition of the DeltaE2000 (CIEDE2000) color difference formula.
Bug fixes:
• Solved the issue where it was not possible to precisely select colors near the blue primary of large RGB
spaces, such as ProPhoto, by clicking in the "xy" chromaticity diagram.
• Fixed the problem of unstable interface for users in regions of the world where a period is used as a
separator for thousands (ex.: 6.123,43). Editing the regional preferences to assign a space to the thousands
separator is no longer necessary. Affected regions included: Belgium, German speaking countries, Italy, the
Nederlands, Portuguese speaking countries, and some Spanish speaking countries.
Bug fix:
• Solved the issue where the program crashed when entering particular combinations of RGB values (out-of-
range parameters were sometimes generated when converting to other color notations).
New features:
• First release with the "Color Deck" viewing mode where the user can browse and convert colors from and to
catalogues of color chips.
• Now provides the individual contributions of ∆L*, ∆C*, ∆H* in the DeltaE* color-difference, as well as ∆h.
• Six RGB spaces have been added: BestRGB, Beta RGB, DonRGB4, eciRGB, Ekta Space PS5, and
ProPhoto.
• Two color spaces have been added: Munsell HVC (interpolated) and L*C*h.
• User selected Options (Windows) / Preferences (Mac) are now saved, when changed, and loaded when the
program starts.
Improvements:
• The data tables in the saved report are easier to read (and import in a spreadsheet).
• The input boxes parsing routine has been redone.
• The tutorials were reviewed for better cross-platform use. A tutorial was added for the new "Color Deck"
mode.
Bug fixes:
• Solved the issue where entering negative numbers in the L*a*b*/L*u*v* input boxes resulted in odd data entry
point behavior.
• Solved a bug in the CMC DeltaE* computation which introduced a small error for small color differences, but
which increased with large color differences.
New features:
• First release of the Mac version with support for OS 8 and 9 (Mac Classic), and OS X.
Improvements:
• Windows version significantly faster than version 1.1.
• Better Print routine which supports more printers and page widths.
• Improved parsing in input boxes.
• Improved GUI uniformity with various display Appearance settings (Windows).
Bug fixes:
• No more printing limitations when using the program in a 800 x 600 display.
Other:
• Windows 95 not supported anymore.
Note: All the images in this help manual are heavily compressed in JPEG format. Because of this, the color
patches shown in the tutorials are not made of single solid colors; adjacent pixels of a given patch may be of
slightly different colors. This is not the case with the patches produced by CT&A.
Additional tutorials and application notes are available on the BabelColor Web site:
https://www.babelcolor.com/tutorials.htm .
Important: For more accurate visual results, your display(s) should be calibrated with a custom ICC profile.
You can check that the proper color profile is recognized for each active monitor by looking at the “Color” tab of
the Preferences dialog. You can also verify your display settings with the procedures described in the Display
calibration section. Please note that the display profile has NO EFFECT on the accuracy of the computations; it
simply affects the appearance of the color patches.
The tutorial is separated in two parts. The first part shows how identical RGB coordinates in Apple RGB and
sRGB really look quite different. Apple RGB was the de facto color space in older Mac computers and many
legacy images were created in this space. sRGB has been the standard RGB space for Windows based
computers for a long time and a good choice for a recent Mac (see the Apple RGB section for more info). This
tutorial will help you understand what happens when you open legacy images generated in Apple RGB, which
were most likely not tagged with an ICC profile, in a new computer where the default space is sRGB. The
difference between these two spaces is mostly (and not totally!) in the spaces' gamma, which is 1,8 for Apple
RGB, and 2,2 (if we use the simple gamma) in sRGB.
The second part compares the same coordinates selected in the sRGB and Adobe (1998) spaces. These two
spaces have very similar gammas; the simple software-encoding gamma is the same (=2,2), but sRGB's
gamma is more accurately defined a multiple segments detailed gamma. However, they have quite different
gamuts, with Adobe (1998) being much larger and capable of representing more colors.
Important: Before starting a tutorial, please take time to complete the SETUP section; this will make sure that
the tutorial's screenshots and results match your own. Within each steps you will find links to specific help
sections which provide more details if required.
Note: The Apple RGB vs sRGB tutorial cannot be done if CT&A is not activated).
• Open the RGB vs RGB tool window either by clicking on the corresponding icon on the toolbar window, by
selecting the "RGB vs RGB/Show window" menu, or by selecting the "Tools/RGB vs RGB" menu.
• Make sure the tool is in Compare mode, which can be confirmed by looking at the Mode settings buttons
located on top of the chromaticity diagram:
The middle button should be labeled "Compare mode" on a white background, as shown above. If this is
not the case, select the compare mode with the "RGB vs RGB/Mode/Compare" menu, or click on the
yellow "Convert" button which will change into the white "Compare mode" button.
• Uncheck any "L*a*b* / L*u*v* input" checkbox located at the bottom of each space.
Note: The R'G'B' coordinates are selected randomly each time the program is launched.
STEP 1
Set Space #1 to Apple RGB and Space #2 to sRGB:
You can verify in the chromaticity diagram that the spaces' illuminants are at the same location (x=0.313 and
y=0.329, the coordinates of illuminant D65). The diagram also shows the triangles defined by the primaries of
each space; they are of similar size but slightly offset from one another:
Note: A single click may be sufficient to select the displayed value, depending on the platform, Windows or
Mac, and the Operating System (Windows 2000, XP, Vista, Windows 7, Mac OS X).
Double click in the data display of Space #1 which has a green background and type 140; alternately, press the
Tab key to move from one data box to the other. Double click in the data display of Space #1 which has a blue
background and type 116. The R'G'B' displays should look like:
STEP 3
Type the same values in the data displays of Space #2. The color patches display should look like:
The first thing we notice is that the color looks much darker in the sRGB space even though the R'G'B'
coordinates are identical. A similar effect will be seen for all colors in an image, with the resulting image much
too dark.
DISCUSSION
The main effect behind this color difference is the spaces respective gammas. The gamma of 1,8 for the Apple
RGB space tends to be more linear than the gamma of 2,2 of sRGB. A space with a linear gamma (gamma=1)
will have its zero to 255 R'G'B' values uniformly distributed with light and dark colors. As the gamma increases,
there are more and more R'G'B' numbers used to represent darker colors; this is consistent with how the
human visual system works. Thus, the 2,2 gamma of sRGB will result in more integer values dedicated to
darker colors than the 1,8 gamma of Apple RGB. This is why the numbers used to represent a color in Apple
RGB actually correspond to darker colors in sRGB. This said, if you look at the chromaticity diagram, you will
also notice a color shift. In the cut-out of the chromaticity diagram shown below, the green square,
corresponding to Space #1, is closer to the illuminant, meaning that the Apple RGB color is less saturated, i.e.
more grayish:
The DeltaE* display also shows the individual contributions of lightness difference (∆L*), chroma difference
(∆C*) and hue difference (∆H*) in the total ∆E difference. ∆L* and ∆C* also correspond to the differences
between the L* and C* coordinates shown for each space in their L*C*h displays. While ∆H* is what is left
when you remove the ∆L* and ∆C* contributions in ∆E, ∆h, the hue angle difference is directly related to the h
shown in the L*C*h displays. See the L*a*b* or L*u*v* to L*C*h and DeltaE* sections for the mathematical
definition of these parameters.
We see that most of the difference comes from the lightness (-6,48, i.e. darker by 6,48%), with a smaller but
noticeable contribution from chroma (2,68), which expresses color saturation, as we also inferred by looking at
the chromaticity diagram.
In practical terms, these simple steps show that legacy images created without embedded profiles in Apple
RGB, very likely on a Mac a few years ago, will look darker on a Windows based computer, or on a Mac
running Mac OS X 10.4+, if no compensation is done. On a Mac running Mac OS X with a version prior to 10.4,
the image would look quite similar to the original intent since these previous versions of Mac OS X used
Generic RGB as their default RGB space, a space which has the same gamma as Apple RGB (to confirm,
simply select Generic RGB in Space #2).
If the image has an embedded ICC profile and the software used to open it supports color management, then it
will be viewed with correct colors. If the image has no ICC profile but its Mac origin is known, you can manually
assign the Apple RGB profile to the image, with Photoshop for example, and again obtain a proper image.
Note: Older, pre-Mac OS X, images originating from a Mac platform should be assumed to be encoded in
Apple RGB. More recent images with no ICC profile could be encoded either in Generic RGB or sRGB; If the
image looks darker when opened as sRGB, then try Generic RGB.
This concludes the first part of this tutorial; click here to go to the second part. Click here to go back to the
tutorials' Table of Contents.
• Open the RGB vs RGB tool window either by clicking on the corresponding icon on the toolbar window, by
selecting the "RGB vs RGB/Show window" menu, or by selecting the "Tools/RGB vs RGB" menu.
• Make sure the tool is in Compare mode, which can be confirmed by looking at the Mode settings buttons
located on top of the chromaticity diagram:
The middle button should be labeled "Compare mode" on a white background, as shown above. If this is
not the case, select the compare mode with the "RGB vs RGB/Mode/Compare" menu, or click on the
yellow "Convert" button which will change into the white "Compare mode" button.
• Uncheck any "L*a*b* / L*u*v* input" checkbox located at the bottom of each space.
Note: The R'G'B' coordinates are selected randomly each time the program is launched.
STEP 1
Set Space #1 to sRGB and Space #2 to Adobe (1998):
You can verify in the chromaticity diagram that the spaces' illuminants are at the same location (x=0.313 and
y=0.329, the coordinates of illuminant D65). The diagram also shows the triangles defined by the primaries of
each space. The Adobe (1998) is the larger one, mostly due to its more saturated green primary:
Note: A single click may be sufficient to select the displayed value, depending on the platform, Windows or
Mac, and the Operating System (Windows 2000, XP, Vista, Windows 7, Mac OS X).
Double click in the data display of Space #1 which has a green background and type 140; alternately, press the
Tab key to move from one data box to the other. Double click in the data display of Space #1 which has a blue
background and type 116. The R'G'B' displays should look like:
STEP 3
Type the same values in the data displays of Space #2. The color patches display should look like:
Because these two spaces have very similar gammas, we would expect that the two patches exhibit the same
level of lightness, and this is almost the case here, although the Adobe (1998) is slightly brighter (compare the
patches L* value). But what we clearly see is that the sRGB color, the larger square, is much less saturated,
i.e. less pure or muddy, than the Adobe (1998) color.
DISCUSSION
The main effect behind this color difference is the spaces' respective gamut size. The Adobe (1998) space can
represent more colors, and these additional colors are essentially all more saturated than the colors of the
sRGB space. If we assume that their gamma is the same, then the darker and lighter colors should be
represented by the same numbers. However, because the Adobe (1998) space also contains more saturated
colors, all R'G'B' coordinates of this space are more saturated. If you look at the chromaticity diagram, you will
notice this saturation shift. In the cut-out of the chromaticity diagram shown below, the green square,
corresponding to Space #1, is closer to the illuminant, meaning a less saturated color. Also, the orange square,
corresponding to Space #2, is shifted towards the red primary:
The DeltaE* display also shows the individual contributions of lightness difference (∆L*), chroma difference
(∆C*) and hue difference (∆H*) in the total ∆E difference. ∆L* and ∆C* also correspond to the differences
between the L* and C* coordinates shown for each space in their L*C*h displays. While ∆H* is what is left
when you remove the ∆L* and ∆C* contributions in ∆E, ∆h, the hue angle difference is directly related to the h
shown in the L*C*h displays. See the L*a*b* or L*u*v* to L*C*h and DeltaE* sections for the mathematical
definition of these parameters.
We see that most of the difference comes from the chroma (6,53), with smaller contributions by the hue (2,37)
and the lightness (2,15). The hue angle shift, at -4,84 degrees, indicates that we have a slight red shift for the
Adobe (1998) color relative to the sRGB color.
In practical terms, these simple steps show that images created without embedded profiles in sRGB will look
saturated if an Adobe (1998) profile is assumed. Conversely, an image created in the Adobe (1998) space will
look muddy when opened in a program which assumes that the image space is sRGB.
If the image has an embedded ICC profile and the software used to open it supports color management, then it
will be viewed with correct colors. If the image has no ICC profile but its origin is known, you can manually
assign the sRGB or Adobe (1998) profile to the image, with Photoshop for example, and again obtain a proper
image.
However, still, there are many applications which do not support sophisticated color management, Web-
browsers coming to mind. In some cases, where color is critical, the fashion business for example, the designer
may insist to have its garments viewed in the same way with different computer platforms. To be able to
convert color coordinates between two color spaces then becomes useful. This is the subject of the second
tutorial: Converting between RGB spaces.
CT&A should still be opened, with the settings and input values obtained in this tutorial. In particular, check that
the DeltaE*ab values are the same as the ones shown in the screenshot above. Now go back in the
Preferences dialog we opened at the beginning of this tutorial, and select the "Math" tab. Select the "Always
use a single parameter gamma (simple gamma)" checkbox:
With the most significant change in the lightness difference which went from 2,15% to 1,68%. The overall color
difference is just a tad smaller, 7,04 instead of 7,27, but the difference in chroma is still very high. You will also
see a small change in the visual appearance of sRGB patch and its L*a*b* coordinates, but no change in its
R'G'B' values:
This concludes the tutorial. Click here to go back to the tutorials' Table of Contents.
For this second tutorial we look at how to convert R'G'B' color coordinates from Apple RGB to sRGB, and then
from sRGB to Adobe (1998), so that the colors represented by the RGB coordinates are the same. Please note
that we have selected a color in Apple RGB which is not clipped when converted to sRGB and Adobe (1998);
clipping is the subject of Tutorial 3 (Understanding clipping).
Note: If you are using an non-activated copy of CT&A, you can only convert between sRGB and Adobe (1998)
and you should do the shorter version of this tutorial which looks at the sRGB to Adobe (1998) conversion only.
SETUP
Set the program as follow:
• Open the RGB vs RGB tool window and close all other tool windows.
• Set the RGB vs RGB window in Compare mode with both sides set in RGB space mode.
• Space #1 selection: Apple RGB
• Space #1 input mode: R'G'B'
• Space #2 selection: sRGB
• Space #2 input mode: R'G'B'
• Gamma mode: detailed gamma; leave
Always use a single parameter gamma (simple gamma)
unchecked in the Preferences dialog.
• DeltaE* display: DeltaE*ab
STEP 1
Click and drag the elevator box of Space #1 Y slider to its lowest position:
All R'G'B' displays of Space #1 should be zero. Click and drag the elevator box of Space #1 G (green) slider
until the display shows 135; click between the elevator box and the extremities for coarse adjustments (+/- 10)
or on the slider's arrows for fine (+/- 1) adjustments (Note: Sliders in the latest Mac OS X versions do not have
Click and slowly drag the elevator box of Space #1 R (red) slider up to the top (R' = 255); as you move, follow
the green box on the chromaticity diagram as it slides along the line between the red and green primaries of
Space #1. You will also notice how the Y slider follows the red slider once it goes beyond the green slider's
position.
Finally, click and drag the elevator box of Space #1 Y slider until the R display shows 200 (if you have difficulty
adjusting Y to 200, move it until you are close and adjust by clicking on the Y slider arrows for fine adjustments
of +/- 1); notice how all the RGB sliders move while the green square on the chromaticity diagram does not.
This last adjustment affects only the color luminance. The R'G'B' displays should now show:
STEP 2
To convert this color in the sRGB space, simply click on the Compare button located on top of the chromaticity
diagram:
After the click, the three buttons' content and color will change to:
and the overall display will look like (RGB vs RGB window shown without the extra patches layouts):
STEP 3
We will now convert these sRGB coordinates in Adobe (1998) RGB. There are many ways to do this but since
we already have Space #2 set in sRGB with the correct values, we will simply change the convert direction to
be from Right-to-Left. To change the convert direction, click on either one of the yellow arrows on top of the
chromaticity diagram:
After the click, the direction arrows color will change to orange:
You will notice that the R'G'B' boxes backgrounds have changed, with the ones with a yellow background now
seen on the Space #1 side. You can now change Space #1 from Apple RGB to Adobe (1998):
The color patches have not changed, just the R'G'B' coordinates of Space #1, which are now shown relative to
Adobe (1998) RGB. In other words:
Adobe (1998) (194, 128, 174)
= sRGB (215, 129, 177)
= Apple RGB (200, 106, 163) .
which means that there is no clipping resulting from the conversion (i.e. the Adobe (1998) space can reproduce
this sRGB color exactly).
In Convert mode, the program does an exact color conversion, determining the R'G'B' coordinates of the
converted space with fractional precision (they are rounded for display purposes only). To see how integer
values of R'G'B' in both spaces would compare, simply click on the Convert mode button to go back to
Compare mode (you may see changes in the xyY, XYZ, L*a*b* and L*u*v* values):
Following the click, the software replaces the fractional R'G'B' values of Space #2 with the closest integers. The
DeltaE* display now shows:
the "real" difference between the Adobe (1998) and sRGB spaces for these R'G'B' data sets.
For more information on how the software treats integer variables, see the data integrity section.
This concludes the tutorial. Click here to go back to the tutorials' Table of Contents.
In Tutorial 1 we have seen that if we use identical R'G'B' values in Apple RGB, sRGB, or Adobe (1998), we are
in fact describing colors of different lightnesses (intensity), chromas (saturation) and even hues.
For this second tutorial we look at how to convert R'G'B' color coordinates from sRGB to Adobe (1998), so that
the colors represented by the RGB coordinates are the same. Please note that we have selected a color in
sRGB which is not clipped when converted to Adobe (1998); clipping is the subject of Tutorial 3 (Understanding
clipping).
SETUP
Set the program as follow:
• Open the RGB vs RGB tool window and close all other tool windows.
• Set the RGB vs RGB window in Compare mode with both sides set in RGB space mode.
• Space #1 selection: Adobe (1998)
• Space #1 input mode: R'G'B'
• Space #2 selection: sRGB
• Space #2 input mode: R'G'B'
• Gamma mode: detailed gamma; leave
Always use a single parameter gamma (simple gamma)
unchecked in the Preferences dialog.
• DeltaE* display: DeltaE*ab
STEP 1
Click and drag the elevator box of Space #2 Y slider (on the RIGHT side of the RGB vs RGB window) to its
lowest position:
All R'G'B' displays of Space #2 should be zero. Click and drag the elevator box of Space #2 G (green) slider
until the display shows 154; click between the elevator box and the extremities for coarse adjustments (+/- 10)
Click and slowly drag the elevator box of Space #2 R (red) slider up to the top (R' = 255); as you move, follow
the orange box on the chromaticity diagram as it slides along the line between the red and green primaries of
Space #2. You will also notice how the Y slider follows the red slider once it goes beyond the green slider's
position.
Finally, click and drag the elevator box of Space #2 Y slider until the R display shows 215 (if you have difficulty
adjusting Y to 215, drag the slider until you are close and do fine adjustments by sliding your finger on the
mouse surface); notice how all the RGB sliders move while the green square on the chromaticity diagram does
not. This last adjustment affects only the color luminance. The R'G'B' displays should now show:
STEP 2
To convert this color in the sRGB space, select the "RGB vs RGB/Mode/Convert Right to Left" menu. After the
selection, the three buttons button located on top of the chromaticity diagram will change to:
and the overall display will look like (RGB vs RGB window shown without the extra patches layouts):
ADDITIONAL INFORMATION
If you look at the DeltaE* display, you will see that the color-difference between the two coordinates data sets is
zero:
which means that there is no clipping resulting from the conversion (i.e. the Adobe (1998) space can reproduce
this sRGB color exactly).
In Convert mode, the program does an exact color conversion, determining the R'G'B' coordinates of the
converted space with fractional precision (they are rounded for display purposes only). To see how integer
values of R'G'B' in both spaces would compare, simply click on the Convert mode button to go back to
Compare mode (you may see changes in the xyY, XYZ, L*a*b* and L*u*v* values):
Following the click, the software replaces the fractional R'G'B' values of Space #2 with the closest integers. The
DeltaE* display now shows:
the "real" difference between the Adobe (1998) and sRGB spaces for these R'G'B' data sets.
For more information on how the software treats integer variables, see the data integrity section.
This concludes the tutorial. Click here to go back to the tutorials' Table of Contents.
Note: Even if clipping indicators may be seen in all tools' patches, this tutorial is done using the RGB vs RGB
tool which enables us to have fine control on the input color.
When converting color data from one RGB space to another, it is often found that a given color or, more
generally, a range of colors, cannot be displayed in the destination space. These colors are said to be out of
gamut. There are basically two choices when this occurs: either clip the color on the edge of the destination
space, or "compress" the distance between all colors and maintain the color relations. In addition, some
conversion is required to compensate for the "color" of different illuminants which vary from yellowish to bluish.
These two requirements are the basis of the "intent" choices offered in high end image editing programs when
converting data using ICC profiles.
For most color translation/conversion applications, it is important to maintain the perceived color as uniformly
as possible. An often recommended option is Relative Colorimetric intent. When selecting this intent, the
system first adapts the color of the sample to the color of the destination illuminant. The chromaticity
coordinates of the original and translated colors are different, but when they are viewed under their respective
illuminants, they are seen as being the same. However, once shifted to match the destination illuminant, the
color may still be out of gamut; in this case, it is usually clipped on the gamut's edge.
For proofing applications, it is advisable to keep the same chromaticity coordinates, whenever possible, and
clip to the nearest gamut edge if not; this is usually called Absolute Colorimetric intent. This type of
conversion does not try to make the colors look identical under various illuminant. A white patch under D50, a
yellowish white, will look yellowish when seen under D65, and a white patch under D65, a bluish white, will look
bluish when seen under D50. This intent is not recommended for general imaging applications.
If the perception of colors, when seen together, is more important than their individual accuracy, then the
program can modify the colors for the purpose; this is called Perceptual intent. With this option, none of the
converted colors are accurate. Another choice is Saturation intent, which is suggested for applications where
the vividness of the colors is more important than their hue, in business graphics for example. Obviously, color
accuracy is not a goal here. Variants of the above intents, such as Black Point Compensation (BPC), are
offered in some programs, the user should consult their respective documentation.
CT&A emphasizes perceived accuracy; accordingly, colors are converted internally using Relative
Colorimetric intent, with no BPC, and adapted to the other space illuminant using a Chromatic Adaptation
Transform (CAT) matrix.
Whenever clipping happens between the color coordinates shown in a tool and the RGB coordinates used for
display purposes, clipping indicators are shown in the bottom of the color patch. Similarly, in the RGB vs RGB
tool, when clipping arises in a conversion between the two sides of the tool, clipping indicators appear above
the converted space's R'G'B' data displays.
Another type of clipping indicator can be seen when in L*a*b* or L*u*v* input mode. This is discussed in
Tutorial 5.
Note: We do not care if the graphics card LUTs are not loaded or incorrect for the selected profile since we
are only interested in the numbers and their effect on the clipping display.
Important: After you have completed this tutorial, do not forget to set your display profile back to what it
was when you started it.
The coordinates are converted to Space #2 / sRGB, with R'G'B' = (52, 23, 1).
There is no clipping and DeltaE*ab=0. On the chromaticity diagram, the small orange square representing
Space #2 is positioned on top of the green square representing Space #1. Since this is a very dark brown, we
suggest you increase the window to show the extra patches in the bottom of the display, and click on the
patches until they are surrounded by a black background; this background will make the brown more
noticeable.
If you bring the mouse cursor over the patches and stop for a second, you will get a Help Tag which indicates
the display profile assigned to the window. It should correspond to the profile assigned in the Setup (where we
selected sRGB).
This indicator tells us that one or more RGB coordinate of the color patch is clipped when displayed, i.e.
this Adobe (1998) RGB color cannot be accurately represented. We remind you that we have selected
sRGB as the display profile.
• A clipping indicator has also appeared on top of the B coordinate for Space #2:
Since we are converting to sRGB, the same RGB space used for the display profile, clipping should be
expected. However, here we see that it is only the Blue coordinate which is clipped, an information which
we do not have in the clipping indicator located below the patches..
• We can see that the orange square of Space #2 is no more over the green square:
However, in this case, the color difference is quite small and likely not noticeable by most persons.
We now see that the sRGB patch representing Space #1 (Adobe (1998)) has both its red and blue
coordinates clipped. To match the Adobe (1998) color we would need to add more red than the nominal
255 maximum value for 8 bit encoding, and assign a negative value to the blue coordinate. This is indeed
one method to extend the gamut of RGB spaces; see for instance:
PIMA 7667:2001 Standard: “Photography – Electronic still picture imaging – Extended sRGB color
encoding – e-sRGB” (PIMA: Photographic and Imaging Manufacturers Association).
While not very common, this method is used in some PatchTool conversions, another BabelColor product
( https://www.babelcolor.com ) .
• From this point on we can see that the orange square of Space #2 moves away from the green square and
the color difference goes up as we increase Y. Below on the left we see the RGB coordinates of Space #1
with Y at its maximum position, where R of Space #1 is now 255 but R of Space #2 is still clipped at 255:
Note: It is hazardous to judge a color difference visually when one or both colors are clipped by the display
profile, since clipped colors are not accurate by definition!
Important: Do not forget to reset the display profile, using your OS monitor control panel, to what it was when
you started the tutorial.
Almost every "xy" coordinates within the triangle defined by the space primaries has a different maximum "Y"
value, and the 3D shape of a space's xyY coordinates is far from the uniform cube representation of R'G'B'.
Moreover, the 3D shape is different from one space to the other and the maximum Y will likely be different,
resulting in clipping in the Y dimension. It is thus risky to only use only the periphery, or area, of the "xy"
representation to compare color spaces; the third dimension, "Y", must also be taken into consideration.
This concludes the tutorial. Click here to go back to the tutorials' Table of Contents.
Any software which manipulates color images or color objects usually has a color picker. It is often the
operating system's default picker but various schemes are proposed. Sometimes, the color picker is made only
of R'G'B' sliders and input boxes, but you can also find L*a*b* and HSB (Hue-Saturation-Brightness) input
controls. You usually have a color patch showing the current selection and, sometimes, another patch showing
the previous selection.
SETUP
Set the program as follow:
• Open the RGB vs RGB tool window and close all other tool windows.
• Set the RGB vs RGB window in Compare mode with both sides in RGB space mode.
• Space selection: sRGB for both spaces
• Input modes: R'G'B' for both spaces
• Hex # / HSB / HVC / L*C*h / xyY / XYZ display: xyY in both spaces
• L*a*b* / L*u*v* display: L*a*b* in both spaces
• L*a*b* / L*u*v* in D50 checkbox: unchecked in both spaces
• Gamma mode: detailed gamma
Its "Y" value is 37,4 compared to 15,1 for Space #1. The "L*" values (of L*a*b*), more representative of the
perceived brightness, are 67,6 for Space #2 and 45,8 for Space #1.
To match their brightness, you have three choices, all done using the "Y" slider:
• increase the brightness of Space #1,
• decrease the brightness of Space $2, or
• increase or decrease the brightness of both spaces!
There is a caveat: You cannot arbitrarily increase the luminance ("Y") or brightness ("L*") of a given color; there
is a different maximum value for each "xy" data set (see the xyY and XYZ section for more information).
For the purpose of the example, we will simply decrease Space #2 brightness. Click and drag the elevator box
of the "Y" slider until its "Y" coordinate approximately matches the value seen in Space #1; you can also do the
adjustment using "L*" as a reference.
where Y=15,1 for both spaces (note that L*=45,8 also in both spaces), and the color patches display now
shows:
You will find that the perceived brightness is better matched using "Y" or "L*" as references compared to
making adjustments using the "B" of the HSB. To visualize this, set the Hex # / HSB / HVC / L*C*h / xyY / XYZ
display to HSB in both spaces.
Verify, in the "xy" mouse input display, that the Space #1 radio button is selected and that both buttons are
enabled:
Click (mouse left-click) in the chromaticity diagram window around the x = y = 0.250 location (plus or minus
0.010). A small display with the x and y coordinates will appear as you move the mouse on the chromaticity
diagram; these coordinates will appear in the xyY display of Space #1 when you do a mouse click:
and click (mouse left-click) in the chromaticity diagram at a location, relative to the illuminant, approximately
opposite from Space #1 color (x ≈ 0.37, y ≈ 0.42).
Both methods achieve the same result but Method 1 is faster when you need to switch sides repeatedly.
Enlarge the window until you see the extra patches on the bottom of the display and the ones on its right:
If required, click on the bottom patches until you obtain the layout where the patches are side-by-side.
Have a look at the DeltaE* display shown below, which was obtained by adjusting the position of Space #2 with
the goal of minimizing the lightness (L*) and chroma (C*) differences while obtaining an almost exact 180
degrees shift in hue.
While R'G'B' inputs are natural when working in RGB spaces, many applications call for the use of more
standard colorimetric data such as XYZ, L*a*b* or L*u*v*. For example, specifying a reference color for a
company logo will often be done using L*a*b* coordinates determined with a D50 illuminant.
When incorporating a logo in a publicity brochure, there is a need to use the best (should we say exact!) color
information. A conversion of the L*a*b* data into the RGB space of the image rendering tools is often required.
You may also have a need to convert L*a*b* to L*u*v* data, or convert L*a*b* or L*u*v* data from one
illuminant to another, or determine the equivalent xyY and XYZ coordinates. These are all transforms which are
independent of the RGB space environment but which are nonetheless possible to do within this window.
SETUP
Set the program as follow:
• Open the RGB vs RGB tool window and close all other tool windows.
• Set the RGB vs RGB window in Convert mode Left-to-Right with both sides in RGB space mode.
• Space selection: sRGB for both spaces
The next three steps are only done to insure that the tutorial's illustrations match the user screen.
• Select "Bradford" as the Chromatic Adaptation Transform in the "Math" tab of the Preferences dialog, then
close the dialog.
• Space #1 input mode: R'G'B' (not L*a*b* / L*u*v* input yet)
• Click and drag the "Y" slider of Space #1 to the bottom: R'G'B' = (0, 0, 0)
Continue with these settings:
• Now set Space #1 input mode to: L*a*b* / L*u*v* input
• Hex # / HSB / HVC / L*C*h / xyY / XYZ display: xyY in both spaces
• L*a*b* / L*u*v* display: L*a*b* in both spaces
• L*a*b* / L*u*v* in D50 checkbox: checked in both spaces
• DeltaE* display: DeltaE*ab
Make sure that the L*a*b* / L*u*v* in D50 checkbox is checked since the sRGB space illuminant is D65. If the
box was left unchecked, the program would assume that the L*a*b* input is in D65.
Click the mouse in the L* box, the first box on the left with a green background. Write 48,2 in the box and then
press tab on your keyboard to go the next box on the right. Write -49,4 for a*, then another tab to go to the third
box, and write 23,3 for b*.
The color we just entered is L*a*b* (D50) = (48,2, -49,4, 23,3), a mid-green.
The display will not be updated until the "GO !" button is clicked. The R'G'B' and xyY displays still show the
previous data. The clipping indicator ( ! ) above the R' display box is an advanced warning that the typed L*a*b*
input represents a color which cannot be exactly represented in the sRGB space; it will be clipped. The clipping
indicator will disappear when we click the "GO !" button and the closest valid color will be determined. If you
now click the "GO !" button (you can also press the Return key), the display becomes:
All three L*a*b* coordinates have changed to the closest matching color. The R' display now shows zero, as a
result of clipping. In such a situation, there are a few choices:
• clipping is deemed reasonable and the clipped R'G'B' coordinates are used as is (the clipping error will be
evaluated next),
• another target space with a larger gamut can be selected,
• a custom spot color could be used for printing, if this is the desired output media.
where none of the L*a*b* coordinates have changed relative to the input values. Since we are in Convert mode,
and since Space #2 is set in sRGB, Space #2 will show the same R’G’B’ values we had when Space #1 was
clipped to sRGB (Space #2 sRGB = 0, 134, 72). In addition, the DeltaE*ab display shows a 5,59 color-
difference value between the non-clipped and clipped colors.
Note: For those who think the above color-difference value overestimates the perceived difference, you can
change the color-difference formula to DE2000. You will get a number (=2,12) which better matches what we
see.
Looking at the chromaticity diagram, we see that the green square of Space #1, representing the non-clipped
color, is slightly out of the sRGB triangle:
With the above procedure, we learned that the original L*a*b* color is not clipped in Adobe (1998) RGB and we
got the corresponding R'G'B' coordinates; we also determined the exact color-difference value resulting from
the use of sRGB.
First, if not already set, select the Adobe (1998) space for Space #1, then check the L*a*b* / L*u*v* in D50
checkbox, and finally, enter the following L*a*b* (D50) values = (92,7, -40,2, 94,1).
Once the values are entered, you must click on the "GO !" button; only then will you be able to get the data for
the other representations. Here is a screenshot of the L*a*b* (D50) values:
As well, Hex #, HSB, Munsell HVC, L*C*h, xyY and XYZ can be displayed for this given L*a*b* (D50) input.
However, all of these representations, except L*C*h, are shown relative to the illuminant of the selected space,
D65 in this case (for Adobe (1998)). L*C*h is the exception; it will always correspond to the L*a*b* / L*u*v* and
L*a*b* / L*u*v* in D50 checkbox selections (click here for more info).
For conversions using this method, you should use the largest space available for a given illuminant:
• for illuminant C: NTSC,
• for illuminant D50: ProPhoto,
• for illuminant D65: Adobe (1998),
• for illuminant E: CIE RGB,
• or you can define a large space with any illuminant using the Custom RGB space dialog.
Important: If the L*a*b* or L*u*v* input data falls outside of the gamut of the selected RGB space, the
conversion will be clipped and the results will not be valid.
As indicated in this example title, we want to convert L*a*b* (D65) data into illuminant E values. One possible
method is to select CIE RGB space for Space #2. We could also design a custom RGB space with Illuminant E
for Space #2, but this is not the purpose of this tutorial! After selection the CIE RGB space, you will see that the
DeltaE*ab display shows "N.A.", for "Not Applicable", since a color-difference cannot be directly computed from
L*a*b* values determined for different illuminants (D65 and E).
To compute this color-difference, the XYZ values of Space #1 are first converted from D65 (the illuminant of
Adobe (1998)) to D50, and those of Space #2 from E (the illuminant of CIE RGB) to D50; the color-difference
is then determined using L*a*b* (D50). In this case, a zero color-difference is obtained, meaning no clipping.
The patch color may be clipped for display purposes, but this has no effect on the conversion.
We thus converted:
L*a*b* (D65) = (92,4, -46,6, 96)
to
L*a*b* (E) = (92,4, -42,1, 95,7)
Important: The conversion is valid as long as there is no clipping shown over the RGB coordinates of Space
#2. If there is clipping, you will need to define a larger custom RGB space for Space #2.
This concludes the tutorial. Click here to go back to the tutorials' Table of Contents.
Note: Of course, if you have the L*a*b* coordinates of the patches, you can always select the L*a*b* / L*u*v*
input mode, and enter the coordinates directly, but make sure they are of the proper illuminant.
This procedure uses chromaticity coordinates referenced to illuminant D65; the data is presented in the table
below. Similar data for illuminants C and D50 is provided, as well as additional information, in the ColorChecker
data section.
D65
# description x y Y
1 dark skin 0,398 0,360 10,1
2 light skin 0,383 0,356 34,6
3 blue sky 0,249 0,266 18,9
4 foliage 0,343 0,432 13,3
5 blue flower 0,269 0,254 23,5
6 bluish green 0,261 0,360 42,7
7 orange 0,508 0,406 29,7
8 purplish blue 0,212 0,184 11,8
9 moderate red 0,462 0,312 18,7
10 purple 0,292 0,222 6,37
11 yellow green 0,377 0,496 44,2
12 orange yellow 0,476 0,442 42,1
13 blue 0,188 0,144 6,11
14 green 0,306 0,489 23,4
15 red 0,539 0,322 11,7
16 yellow 0,449 0,476 59,4
17 magenta 0,369 0,241 19,2
18 cyan 0,198 0,270 20,0
19 white (0.05 D) 0,316 0,334 91,2
20 neutral (0.23 D) 0,312 0,330 58,9
21 neutral (0.44 D) 0,312 0,330 36,0
22 neutral (0.70 D) 0,311 0,329 19,1
23 neutral (1.05 D) 0,310 0,328 8,94
24 black (1.5 D) 0,311 0,327 3,20
PROCEDURE
1. Click on any red dot; compare the "xy" coordinates in Space #1 display boxes with the ones in the table
shown at the end of this tutorial. Use the data window in the chromaticity diagram as a guide, shown
here for patch #1:
The red dot should be in the green square's center, but an exact value/position match may be difficult to
achieve for some patches due to the limited screen resolution; you should tweak the location with the
RGB and Y sliders if required and place emphasis on matching the numerical values instead of the red
dot and green square relative positions.
2. Using Space #1 "Y" slider, bring the "Y" of the xyY display as close as you can to the table value.
3. Set the program in Convert mode Left-to-Right by clicking on the "Compare mode" button on top of the
chromaticity diagram. You now have a large color patch corresponding to one of the ColorChecker
chart's patches (assuming you use a calibrated display!). You can also enlarge the window to show the
patch layout in the bottom of the display:
This concludes the tutorial. Click here to go back to the tutorials' Table of Contents.
SETUP
Set the program as follow:
• Open the RGB vs RGB tool window and close all other tool windows.
• Set the RGB vs RGB window in Compare mode with both sides in RGB space mode.
• Space #1 selection and input mode: anything
• Space #2 selection: eciRGB_v2
• Space #2 input mode: R'G'B' (i.e. uncheck L*a*b* / L*u*v* input)
• DeltaE* display: DeltaE*ab
• Go to the "RGB vs RGB" tab of the Preferences dialog and click on the tab's "Default" button. The dialog
should appear as shown below:
In particular, please note the default settings for these two parameters which affect the appearance of the
patches layout:
Decks List view: Draw borders around patches
Decks L*C*h pad view: Draw borders around patches
The deck mode will appear. The selected deck will depend on which deck was last used. If not already
selected, select the Munsell deck:
Note: The deck labeled "Pantone+ Coated" in the above screenshot is not provided with CT&A; however, you
can easily add such a deck if you have Photoshop, or if you have color data saved in CxF format. In this case,
the data was from a Photoshop color library first exported in Adobe Swatch Exchange (ASE) format and then
opened with PatchTool. Once opened in PatchTool, adding a deck to CT&A can be done using PatchTool
CT&A Export tool (This function can be done with PatchTool in demo mode, and no purchase is required).
STEP 2
Change the selected chip, located in the center of the L*C*h pad, by clicking either on the color strip, the
arrows at each end of the color strip, or on the L*C*h pad patches surrounding the center patch:
Try clicking on the patches labeled with + sat., + lum. and + hue and see how they respectively select a chip
with more saturation, more luminance, and a hue characterized by a larger h angle. Similarly, click on the
patches labeled with - sat., - lum. and - hue to respectively select a chip with less saturation, less luminance,
and a hue characterized by a smaller h angle.
The name of the chip represented by the center patch is shown below the pad. For the names of the chips
around the center, simply rest the mouse cursor over the patch and a tag with the chip name will appear. For
more information on the features of the L*C*h pad, as well as its interaction with the DeltaE* setting, see the
L*C*h pad section.
The deck display now has the following appearance (Note: the selected chip may be different):
The largest patch in the center is the same as the one in the center of the L*C*h pad. However, the other
patches over and under the central patch are shown according to their position relative to that chip in the deck
database, a snapshot of which is shown in the color strip. You can click on any patch in the list to bring it to the
central position; as well, like for the L*C*h pad, you can click in the color strip and on the arrows at each end.
STEP 4
In the RGB vs RGB menu, select the "Mode/Convert Right to Left" menu item:
Select "eciRGB_v2" in Space #2 and write the following values in the R'G'B' display boxes: (195, 116, 117).
The program automatically selects the L*C*h pad mode when you convert TO a deck; the List view is not
available. The center patch of the L*C*h pad shows the best match to the R'G'B' coordinates we just entered. It
is the 5R 6/10 chip, where 5R means the middle of the Red Hue zone in the Munsell notation, while 6/ is the
Munsell Value and /10 is the Munsell Chroma. The match is not exact since there is a visual difference in the
patches display in the bottom of the window:
If we want the Munsell HVC equivalent to the eciRGB_v2 R'G'B' coordinates, we simply select the Munsell
HVC display in Space #2:
The 4,5R 5,7/10,4 value is obtained by interpolating between known Munsell chips manufactured at fixed hue,
value and chroma intervals. The interpolation process is discussed in the XYZ to Munsell section; for more
information on the Munsell notation, please see the Munsell Color System section.
With the same illuminant on both sides, values are now shown for DeltaE*ab, and we see that we have a ∆E
difference of 3,78.
STEP 5
On the other hand, if we want to find the exact eciRGB_v2 equivalent to the Munsell 5R 6/10 chip, we just need
to click on one of the conversion direction arrows:
to change the conversion direction from Right to Left to Left to Right, and we obtain the following eciRGB_v2
R'G'B' coordinates:
under which we see that the interpolated Munsell HVC values are now equal to the Munsell values of the
selected chip in Deck #1.
This concludes the tutorial. Click here to go back to the tutorials' Table of Contents.
These tools are called ISO 3664 with a "+" since they can not only help in making many measurements
required by the ISO 3664 standard, but can also be adjusted to meet your own requirements and also include
tools to measure monitor uniformity according to ISO 12646:2008 and ISO 12646:2014. For instance, ISO 3664
specifies D65 as the chromaticity of the monitor while many would prefer using D50, as specified in ISO 12646.
This is possible in this tool by simply selecting another reference illuminant. The same flexibility in setting the
reference conditions is available for the Color Rendering Index (CRI) and the Metamerism Index (MI), which
can be measured when selecting the other viewing conditions (Prints and Transparencies) defined by ISO
3664.
SETUP
Note: When calibrating or checking a display, and before doing any measurements, you should wait at least
one hour after powering up the monitor, to give time for the electronic components and the LCD back lights to
settle. This is certainly a minimal demand as the ISO 12646:2014 standard mentions that a display to be tested
shall be operated in calibration mode for 12 hours in a room where the temperature is between 18 to 28
Celsius, and stable within 0.5 degree, before making the tests. Such stringent demands may make sense in a
certification laboratory but are not representative of most working environment we have seen.
Note: It is interesting to see that, for luminance and chromaticity, the 2014 version of ISO 12646 places more
emphasis on the stability than on absolute requirements. For instance, the luminance shall stay within 2% of
the average measured during 9 hours, and the white point shall not deviate by more than 0.005 in CIE x and y
from the calibration values. Of course, these variations are applicable for an environment where the
temperature is controlled as stated in the previous note. This tutorial does not address these specific
measurements but uses the luminance and chromaticity requirements defined in ISO 3664:2009.
The window content will change to show only the tools required by the selected viewing condition. In the
"Monitor grid" control group, select the "5x5 (ISO 12646:2014)" radio button. The display should look as follow:
The minimal ISO goal of 80 cd/m2 is considered insufficient by many but may well happen in real life for
monitors which are a few years old. However, going overboard on the plus side is not good either. Recent
LCD displays can often be adjusted to a brightness of well over 300 cd/m2 which is considered too bright,
also by many, for accurate color work, as it emphasizes the darker shades which will be printed much darker
than what is seen on the screen. You should be aware that certain manufacturers of high-end monitors will
not honor their warranty if their monitor is set at a luminance higher than 100 cd/m2.
• Chromaticity: Expressed in u' and v' units of the Uniform Chromaticity Scale (UCS, CIE1976), these are
often specified instead of xy (CIE1931) units because they are more uniform; i.e. the perceived difference
between two sets of chromaticity coordinates better matches the numeric distance between the two sets.
Also, the 10 degree Observer (CIE1964) is used for this measurement.
In ISO 3664, the maximum offset for color monitors is a 0,025 u'v' radius. The
radius of the green circle in the illustrated target corresponds to this value. The
offset value cannot be changed for a given viewing condition but the provided
numerical value will enable you to compare it against other requirements you may
have, such as the more stringent 0,010 radius called for in ISO 12646:2008.
The "Meas. Temp." is the White Point temperature of your display. Technically, it
is the Correlated Color Temperature (CCT), in kelvin, corresponding to the
measured chromaticity. Expressed otherwise, this is the temperature to which you
would set a blackbody in order for it to emit a white of the same chromaticity.
Note: The reference illuminant for the CRI tool will also be based on the "Meas.
Temp." (CCT) shown here if "Auto" is selected as the reference CRI illuminant. As
mentioned previously, the CRI tool is available only for the Prints and
Transparencies viewing conditions.
• Color and Tone uniformity: These two tests are not part of ISO 3664, which specifies a brightness
uniformity for the Prints and Transparencies viewing conditions only, but are those specified in ISO
12646:2014. They are selected with the radio buttons labeled "Color" and "Tone". The measurements need
to be performed with White, Grey, and Dark-Grey color targets.
The test selected by the "Color" radio button is called "Evaluation of tone uniformity" in the standard but what
is described is really a measure of the difference between the color measured at each position and the color
measured in the center position. The color difference is computed using the CIEDE2000 color difference
formula. The Color test is performed independently for the three target colors; you can measure only the
white targets if this is what you need.
The test selected by the "Tone" radio button is called "Tonality Evaluation (Uniformity)" in the standard and it
consists of the deviation between the Grey/White luminance ratio measured at each position relative to the
luminance ratio measured in the center position. The equation for computing the deviation is presented in the
ISO 3664+ tools description section.
When making measurement, you should first select a position by clicking on the corresponding grid cell; this
is confirmed by a red border around the cell. You should then select the target color you wish to measure; the
grid background will change to represent the selected color. You will notice two or three small squares for
each position; three squares are shown when doing the Color test and two squares are shown when doing
the Tone test.
Color test with the Dark-Grey target selected. Tone test with the White target selected.
The color in the center of each small square corresponds to the target colors that can be measured for a test;
this is why the Tone test cell only shows Grey and White squares (and a slash that indicates a ratio will be
computed). The border color of a small square indicates if a target was measured or not, with a yellow border
It it your responsibility to make sure that the proper target color is used for a measurement, but the program
can help you in this regard. First, if you measure the characteristics of a color monitor connected to the
computer on which CT&A is running, you simply need to click on the "Take all" button and the proper target
color will be shown for all positions; this is discussed further more in STEP 3 below. If the color monitor is not
connected to the computer on which CT&A is running, or if you want to make manual measurements, you will
need to manually display the target. Fortunately, you can easily generate custom target images by clicking on
the "Targets..." button; this will open the following dialog:
If you need targets for the computer on which CT&A is running, just position the above dialog within the
monitor for which you want the targets and click on the "Assign values for this display" button; this action
will fill the target parameters fields. The target parameters can also be manually set to the values of your
choice. Select the monitor grid for which you want the targets as well as the file type and click the "Save"
button when ready. A file name will be proposed; edit the name if you wish but please note that a suffix
identifying the target color will be added for each of the three image files that will be generated. You can then
open the images using the graphic editing program of your choice; we recommend using a program which
offers a "Full screen" viewing mode (the photo viewer application in Windows and "Preview" on Mac will do).
Note: The 3x3 grid defined in ISO 12646:2008 favors the monitor's center area, and the targets are thus non-
uniformly distributed on the monitor, while the 5x5 grid defined in ISO 12646:2014 is uniform.
Hint: You should keep your monitor resolution settings as fixed as you can, the reason being that the screen
brightness, its uniformity and chromaticity, and thus its profile, will be affected by a resolution change. If a
change is required, we suggest using different display profiles for each setting.
When calibrating in emission, CT&A presents a dialog which asks you to specify the calibration display. When
two or more monitors are detected, the following dialog is shown:
Once the WP is measured, its characteristics (display location, luminance and CCT) are shown in the toolbar
window, as seen in green text in the next screenshot (for the screenshot below we measured the WP on the
main display of an iMac computer, with no other monitor connected). The display had just been calibrated with
a profiling application with a target luminance of 120 cd/m2 and a D65 WP; this computer (iMac, 21.5 in., Mid
2010) was used for all the measurements shown in this tutorial.
STEP 3
We will now measure the targets at ALL positions and for ALL target colors. You can measure the targets
colors in any order but for the purpose of this tutorial, please reselect the "White" target radio button and select
the "Color" radio button as well. To start the measurements, click the "Take all" button located in the bottom of
the "Color and Tone uniformity" group. Assuming that calibration is done, that you did your calibration on a
monitor connected to computer on which CT&A is running, and that there is only one monitor connected to the
computer, the following dialog will appear:
Note: Different messages will be shown depending on where calibration was done and the number of monitors
connected to the computer. To better follow this tutorial, please select a monitor connected to the computer on
which CT&A is running.
By clicking "Continue", the selected monitor should show a white target in its center. Position the instrument
over the white circle and press the instrument button. The target will then move to the upper-left position.
Important: We do not recommend making measurements with CT&A when MeasureTool or any other program
which may wait for an instrument input is active. None of the programs will crash, but the input may be either
assigned sequentially to the various programs or not assigned at all.
You can also print a one-page report by clicking on the "Print report" button. The printed document presents the
measured data in a visual format ideal for compliance-type reports:
The luminance, CCT and chromaticity results of the above report are presented in a larger format on the next
page.
This concludes the tutorial. Click here to go back to the tutorials' Table of Contents.
In this tutorial, we select the emission mode to measure the luminance of black and white areas of a saved
image, and from these measurements we evaluate the monitor contrast ratio. You may have noticed that high
contrast values of 800:1 plus are advertised for many LCD displays, much higher than the contrast we could
obtain on CRTs. However, a higher contrast is not always better. For press use, the contrast should, in theory,
be adjusted to the contrast of the final support medium. Contrast values can range from 500:1 for fine art prints,
done with high-end ink jets printers and high quality papers, to 300:1 for standard presses with ink on coated
paper, to 200:1 for newspaper images. Because you cannot adjust the black level, and thus the contrast, of
most LCD displays, some profiling software will use the display card or monitor Look-Up-Tables to adjust it.
SETUP
Note: For optimal results, your display should be calibrated prior to this tutorial. Also, the calibration, and this
tutorial, should be done at least one hour after powering up the monitor, to give time for the electronic
components and the LCD back lights, or the CRT tube, to settle.
• Select the Illuminant and Observer in the "Illuminant / Observer" group box. These settings are used to
compute the colorimetric data shown in the bottom section of the "Graph" window (L*a*b* plus a user-
selected color space); they have no effect on the measured and displayed spectrums. We suggest you
select the illuminant which corresponds, or is closest, to the White Point selected when you calibrated your
display; here we have selected D65 and the 2 degree Standard Observer:
STEP 2
Calibrate the instrument by clicking on the "Calibrate" button and following the on-screen instructions. The
calibration in emission mode is done in two steps. The first step requires that the instrument be placed on its
base, to measure the noise floor of the black level, and the second is used to measure the display White Point
(WP). The WP is measured on a white patch, preferably located on the display or emissive surface on which
subsequent measurements will be performed.
When calibrating in emission, CT&A presents a dialog which asks you to specify the calibration display. When
two or more monitors are detected, the following dialog is shown:
Once the WP is measured, its characteristics (display location, luminance and CCT) are shown in the toolbar
window, as seen in green text in the next screenshot (for this screenshot we measured the WP on the LEFT
display of a 2 monitor computer).
STEP 3
To perform this test we need an image with a white target on a black background. You could devise such an
image with any imaging program but you can also use an ISO12646 test image generated within CT&A. To
generate the image, open the ISO 3664+ tools window, select the "Color monitors" Viewing Condition, and
click on the "Targets..." button located near the center of the window. This will open a target creation dialog.
Shown below is a reduced sized screenshot of such an image for a 3x3 grid.
For the purpose of the test, open the image using any graphics editing or viewing program, and size it so that it
fills the screen (which should be at 100% size or zoom if the image resolution corresponds to your monitor
resolution). There is a thin white border around the images to help match their size to the monitor's viewing
area.
Hint: In Windows, you can open the photo viewer application, then select the slide show (F11), and pause at
the selected image; press Alt + Tab to switch between opened applications.
Hint: In Mac OS X, open the image using "Preview", select the slide show, and click on the icon assigned to fill
the screen with the image.
Note: The ISO 12646 target images are normally used in conjunction with the ISO 3664+ tools (see also the
previous tutorial). Yet, they have what we need to measure the contrast ratio. It is not suggested to use small
black and white patches over a crowded and colorful desktop. Many displays will change their brightness
depending on what is displayed on the rest of the screen. In particular, if there are large zones of high
luminosity, the light will leech through the monitor face-plate and influence the black reading. Similarly, ambient
(i.e. room) illumination will affect the readings. Just for the fun of it, if you are using a CRT, place a small
opaque disk—a piece of cardboard will do—over one of the patches, and see the whitish halo around it, which
Hint: You should keep your monitor resolution settings as fixed as you can, the reason being that the screen
brightness, its uniformity and chromaticity, and thus its profile, will be affected by a resolution change. If a
change is required, we suggest using different display profiles for each setting.
STEP 4
At this point, you should have a test image that fills the monitor screen. You do not need to see the other
program windows to proceed with this step, but the Graph tools window should be opened and set as
described previously.
Important: For the purpose of this test, make sure your ambient illumination is less than 10 lux. To achieve
such a low level, you will need to close the main room lights and pull the blinds; if needed, an indirect desk
lamp many feet/meters away should be enough. In particular, when you calibrate the instrument on its base,
make sure the instrument is well seated and that no light from the monitor illuminates the base from the side
(place your hand as a shield if required).
Important: We do not recommend making measurements with CT&A when MeasureTool or any other program
which may wait for an instrument input is active. None of the programs will crash, but the input may be either
assigned sequentially to the various programs or not assigned at all.
Simply position the instrument on the screen, over the white circle located in the test image center, and press
the instrument button. You should hear a "beep". Position the instrument over a black area, between the four
patches in the lower-right section for example, and press its button again:
You can now go back to the "Spectral tools' dialog. Do not close the test image as you may want to do more
measurements with it.
The white center patch has a 137 cd/m2 luminance while the black area has a 0,19 cd/m2 luminance. The
contrast ratio is 721 (= 137 / 0,19), a typical value for a LCD which was not calibrated with a prescribed black
level.
Hint: By leaving the blue indicator unlocked ( ), the input changes sides each time we press the instrument
button. However, if you want to measure the black point at multiple positions while keeping your white
measurement, just lock ( ) the indicator to the sample (with a combination of left and right mouse clicks on
the indicator). In the screenshot shown below, pressing on the instrument button will assign the measurement
only to the right sample from now on:
Hint: The chromaticity of the white patch, the monitor White Point, can be seen by selecting the "xyY" color
space coordinates in the bottom-left list box (which is also useful to verify the coordinates of your monitor
primaries):
You can also compare the two spectrums with their maximum output normalized to one. Simply click on the
"Nor." radio button on each side:
This concludes the tutorial. Click here to go back to the tutorials' Table of Contents.
The RGB vs RGB tool is dedicated to the comparison and conversion of RGB spaces and Color Decks. For a
given RGB space, color coordinates can be entered directly in RGB, as L*a*b* or L*u*v* values, or converted
from another RGB space or Color Deck. In this tutorial, we will use the L*a*b* / L*u*v* input mode which can
accept direct measurements from any of the supported instruments.
The general purpose "Graph" tools enable you to observe, compare and analyze two spectrums and their
corresponding colorimetric data. The spectrums can be from reflectance, emission, ambient or flash
measurements, and basic mathematical operations can be performed between them. Because the Graph tools
require spectral data, they can only accept data from an i1Pro series spectrophotometer.
The tutorial is separated in two parts. PART 1 comprises three steps, which are performed in the RGB vs RGB
tool, and which can be done with all supported instruments. PART 2 has one step which is performed in the
Graph tools window, and which requires an i1Pro series spectrophotometer.
Important: Since these measurements may take some time, you should also temperature stabilize your
instrument by leaving it on the display, in its cradle, while the display heats up.
While the display and the instrument stabilize, prepare and save two small images which will be used to
perform the measurements of this tutorial. The images characteristics should be as follow:
• Size: 200 x 200 pixels per patch minimum
• Color properties: RGB, 8 bit color
• Color: 1 image filled with white (RGB=255, 255, 255)
1 image filled with light grey (RGB=196, 196, 196)
• File format: Bitmap (*.bmp) or PNG (*.png), with no attached profile
Hint: Here is an alternate method to generate color patches using a text file and PatchTool as a viewer
(in the free demo mode!). Simply write the following three lines, where all values are separated by tabs
(tabulation spaces), and save them in a text file (*.txt):
R G B
255 255 255
196 196 196
Open the text file in PatchTool; when asked to assign a profile, select the sRGB space, 8 bit encoding.
Select the "Emission" mode for both spaces. The screenshot below on the left shows the menu for an i1Pro 2,
and the screenshot on the right is the menu for an i1Display Pro. The RGB vs RGB window should look like the
screenshot at the bottom of this page.
Note: In the above screenshot the color patches will likely be different from yours, and the blue indicator will
not be present if an i1Pro series spectrophotometer is not the selected instrument. Also the screenshot shows
the RGB vs RGB window reduced to its minimum layout, without any extra patches.
Calibrate the instrument by clicking on the "Calibrate" button (on either side of the RGB vs RGB window) and
following the on-screen instructions. The calibration in emission mode is done in two steps. The first step
requires that the instrument be placed on its base, to measure the noise floor of the black level, and the second
is used to measure the display White Point (WP). The WP is measured on a white patch, preferably located on
the display or emissive surface on which subsequent measurements will be performed.
When calibrating in emission, CT&A presents a dialog which asks you to specify the calibration display. When
two or more monitors are detected, the following dialog is shown:
Once the WP is measured, its characteristics (display location, luminance and Correlated Color Temperature
(CCT)) are shown in the toolbar window, as seen in green text in the next screenshot (for this screenshot we
measured the WP on an "Other display", not necessarily connected to the computer on which CT&A is
running).
Note: You may ask why a White Level calibration is required in CT&A and not in X-Rite/GretagMacbeth
MeasureTool? In effect, MeasureTool also uses a White Level reference value, very likely coming from a
screen profile saved on your computer. The only difference is that, with CT&A, you can set this reference to
any display. You could for instance use a white patch on your TV screen or even a white patch from a
projector.
Note: Your monitor may or may not be calibrated but, in any case, this is the white to which you will adapt your
vision and relative to which all other colors will be perceived. For example, if your monitor was calibrated to
D65 but is, in effect, at D62 (or, more precisely, 6243 K), like the one we measured, you will adapt to D62 and
never see the difference. The difference will become apparent if you compare the display white with a perfect
D65 white; in this case, our monitor would look yellowish.
Assuming you just calibrated the instrument as described in STEP 2, your instrument should still be located on
the display. Center the white patch under your instrument and make one measurement in Space #1, then
Space #2. Here we have two or three choices, depending on your instrument:
i- Click on the "Measure" button of each space.
ii- Click on the "Measure-and-GO!" button of each space.
iii- If you use an i1Pro series spectrophotometer, click twice on the instrument's button.
Note: Using the window buttons instead of the i1Pro button minimizes the pressure applied by the instrument
on the display, which could possibly affect the measurements, especially on thin LCD screens.
Here is a screenshot of what we obtained after measuring the white patch by clicking on the “Measure” button
of each space:
Because we pressed the “Measure” button, the measured data was entered in the L*a*b* data fields but the
xyY and RGB data fields, as well as the patch color, were NOT updated. We also see clipping indicators ( ! ) for
the red coordinate of Space #1 and for the green and blue coordinates of Space #2. As described in the section
on L*a*b*/L*u*v* input, this means that the measured color is outside the gamut of the respective spaces. If we
now click on the red “GO !” buttons, the input will be clipped and the xyY and RGB values will be computed.
The result is shown on the next screenshot.
Important: If we had pressed on the “Measure-and-GO !” buttons, or on the instrument key, we would have
seen only the results as shown on the next screenshot, and missed the fact that the input values were clipped
by the spaces.
The color temperature (CCT) is essentially the same on each side, 6215 K vs 6236 K, and to the CCT obtained
during emission calibration (6243 K). Here the match is excellent but the CCT is very sensitive to measurement
noise and we could easily see differences of ±100 K if we did many measurements within a few minutes,
differences for which we should not be seriously concerned anyway.
So far so good, but we do note that the measured chromaticity coordinates ("x" and "y") are different, even if
the measured color temperatures are the same. Since emission measurements are measured in absolute
chromaticity, the measurements should be at the same location for both spaces, and more specifically at a
location which corresponds to the 6243 K temperature of the display (slightly towards the yellow side relative to
D65). However, the measurements, illustrated by the green and orange squares, are located on, or near, each
space illuminant, D65 and D50 respectively. What happened?
Firstly, the xyY coordinates are scaled to the absolute value of Y for the White Point (WP) calibration, so our
white patch has a Y of 100, by definition. Secondly, you should keep in mind the three-dimensional shape of an
RGB space when represented in xyY coordinates, as shown on the next page. This illustration shows that there
is a maximum luminance (Y) for each pair of xy coordinates, and only the White Point (WP), i.e. the illuminant,
can have a Y value of 100. Now, unless the white patch has the same chromaticity as the space illuminant, any
other chromaticity with Y=100 will be clipped to fit into the space.
The first method is to make the measurements using the "Measure" button instead of the "Measure-and-GO!"
button, which we effectively did in the beginning of this step, and we indeed saw that the input values would be
clipped. The second method is to measure a gray patch. The rationale is that a lower luminance (i.e. lower Y)
should prevent clipping when we convert the L*a*b*/xyY input to RGB. Open the grey patch image, with
R=G=B=196, and assign a measurement to each space with the "Measure-and-GO!" button (you can also try
with the "Measure" button to confirm that there is no clipping!). Here is a typical result:
If you intend to do PART 2 of this tutorial, you should leave your instrument on the display.
Hint: To get the chromaticity values with more precision, just do a right-click (ctrl + click on a single-button
Mac mouse) with the mouse cursor over a xyY data field. A popup menu will enable you to copy the values.
You can then paste the values in a text file or a spreadsheet.
Important: Measurements on a display may be processed in different ways depending on what we want to
achieve. Here we measured the absolute coordinates of a display patches, without any attempt to compensate
for white point adaptation. It would also be possible to compensate for the actual white point, measured during
emission calibration, and shift the coordinates of all measured colors as if the white point was the RGB space
white point, doing in fact a Relative Colorimetric correction. Such a method is part of the recommended
procedure to certify monitors as specified by Idealliance ( https://www.idealliance.org ) and is the method used
by BabelColor's PatchTool. You will find an Application Note on the BabelColor Tutorials Web page that
explains how to perform the Idealliance procedure using PatchTool: AN-4a Using PatchTool for IDEAlliance
MONITOR proofing certification.
For this tutorial, the indicator can be left either locked or unlocked since we will click on the "Get sample"
buttons.
PART 2 / STEP 1
• In the "Next sample" group box, select the "Emission" mode.
• Select the Illuminant and Observer in the "Illuminant / Observer" group box. These settings are used to
compute the colorimetric data shown in the bottom section of the "Graph" window (L*a*b* plus a user-
selected color space); they have no effect on the measured and displayed spectrums. We suggest you
select the illuminant which corresponds, or is closest, to the White Point selected when you calibrated your
display. For this tutorial we selected D65 and the 2 degree Standard Observer.
• Select the chromaticity coordinates ("xyY") in the bottom-left list box.
• If you just completed PART 1 of this tutorial, you should not need to do a calibration. If you need to, the
calibration procedure is the same as the one described in PART 1 / STEP 2 (you should use the "Calibrate"
button of the Graph tools since this window is already selected and the measurement mode is set to
"Emission").
The luminance levels are the same as the ones obtained in the RGB vs RGB tool window; the CCT can also be
considered to be the same, when taking into account the typical variation seen when measuring this parameter.
You will notice that the grey patch spectrum, drawn in red, looks very close to the white patch spectrum, drawn
in black, even if the luminance is significantly lower. This can easily be explained by looking at the scales,
shown on each side of the graph, which are different.The spectral curves have a similar shape and we can
have a better idea of this match by looking at normalized spectrums; this is done by clicking on the "Nor." radio
buttons on each side of the graph. The resulting graphs are shown on the next page.
You will also note that the "Y" value of the white patch (on the left) is 99,88. Ideally it should be 100 (i.e. 100%)
since we calibrated our display using the same white point. However, a display's brightness is not uniform
across its surface, this brightness may change in time, and there is always an intrinsic error in each
measurement.
Note: L*a*b* values are always computed relative to an Illuminant and Observer. For Reflectance
measurements, changing the Illuminant or the Observer affects the computed values of all color spaces
(L*a*b*, XYZ, etc.). However, in Emission and Ambient modes, you will notice that for a change in Illuminant,
the xyY and XYZ coordinates remain the same while the L*a*b* values change. Because the chromaticity
values of an emitted light is fixed, the perceived color (relative to adapted white), and thus the L*a*b*
coordinates, will vary according to the reference Illuminant used to compute the L*a*b* coordinates.
DISCUSSION
We have seen that the RGB vs RGB tool and the Graph tools will provide the same chromaticities when
measuring a display color as long as the input is not clipped by the selected RGB space in the RGB vs RGB
tool. We thus have to be careful when inputting data into the RGB vs RGB tool due to the fixed size of RGB
spaces. With the Graph tools, you just make measurements without any concern for fitting into an RGB space.
Important: Even if an input is clipped in the RGB vs RGB tool, the luminance or illuminance, and the CCT are
always correct, as they correspond to the measured XYZ values before they may be clipped by the RGB
space.
Here is a table which describes the difference between the RGB vs RGB tool and the Graph tools relative to
EMISSION and AMBIENT measurements:
Note: Only x and y are absolute coordinates. While the absolute luminance and illuminance are provided in
cd/m2 or lux, Y is normalized when shown in the xyY and XYZ data fields.
This concludes the tutorial. Click here to go back to the tutorials' Table of Contents.
If you still do not find an answer to a problem, or if you want to send us your comments and suggestions, click
on the link to send an e-mail:
info@babelcolor.com .
TO REPORT A PROBLEM
Please send us any information that could help in solving the issue, including:
• Screenshots: Take a screenshot of any message, dialog, or tool window which illustrates the problem, then
attach the image or a file containing the image to your e-mail. Here are suggestions on how to take
screenshots:
Windows:
1. Activate the window you want to grab by clicking on it.
2. Press simultaneously on Alt + Print-Screen on the keyboard to copy an image of the selected
window to the clipboard (Note: If the program is frozen, just press Print-Screen to copy the entire
desktop).
3. Paste the window image (usually the "Edit/Paste" menu command) in a graphic edition program or
word processor.
Mac OS X:
1. Press simultaneously on + shift + 3 on the keyboard to create a picture file of the entire desktop,
or press simultaneously on + shift + 4 to create a picture file of a screen area (after pressing and
releasing the key combination, click and drag the mouse over the screen area you want to take a
picture of, or press the space bar and then select an individual window).
2. The file will be saved on the Desktop in the PNG image format.
OR
1. Launch the "Grab" application located in the "Applications/Utilities" folder.
2. Capture the entire screen or a portion of it and save as a "tiff" file.
• Data reports: If the problem is data related and the program still operates when the problem is seen, save
the current data using the "RGB vs RGB/Save Data..." menu, or any report from the spectral tools, and
attach a copy to your e-mail.
• CT&A related information: If possible, describe the sequence of events that resulted in the problem and
include:
For the RGB vs RGB tool:
Operating mode: Compare or Convert (and conversion direction)
Space description (Adobe, Apple, sRGB, Custom, etc.)
Input mode: R'G'B', "xy" Mouse input, "L*a*b*/ L*u*v* input", instrument model and measurement mode
Display mode: Hex #, HSB, Munsell HVC, L*C*h, xyY, or XYZ
Display mode: L*a*b*, or L*u*v*
State of "L*a*b*/ L*u*v* in D50" checkbox
Gamma mode: simple or detailed