Color Management is The Key to Reproduce Consistent Colors

Color gamut is usually described as a 2D diagram, shown in Figure 2(a). The horseshoe shape represents all the colors that humans can perceive, and the enclosed area inside the horseshoe shape represents all the colors that a device or medium can reproduce. But in fact, colors should be described in 3D since we need to use XYZ values to describe a particular color. The comprehensive color gamut should be drawn in 3D, like the one shown in Figure 2(b). However, due to the fact that drawing in 3D is not easy, even with the latest computer tools at our disposal, the 2D color gamut diagram is still widely used. The unfortunate result is that the lightness information of the color is missing in the 2D diagram. So, if there are two colors shown on the same location, it may not necessarily be the same color: it could be the same shade of color, but one may be lighter, and one may be darker.

For two devices to have the same color output, it is necessary to accurately map or transform the two color gamut types. Failure to do so, can result in the situation illustrated in Figure 3, which is a very commonly seen scenario of unmanaged colors. There are many algorithms out there to map or transform color gamut types, but we are not going to discuss these in depth here. What we will discuss is the concept of color management and its general workflow. More importantly, what tool can help us manage colors.

When transforming or mapping two color gamut types (or devices), it is simple; just setup one transformation between the two devices, and we are done. But what happens when there are more than two devices? We could still setup separate transformations between each pair of devices, but this will result in a very messy web of transformations; like the one shown in Figure 4. In order to reduce this complexity, it is much easier if each device knows how to transform to a standard color space, and transform back from the standard color space (Figure 5). Using this concept, we could transform from one device to any other devices by utilizing two transformations only.

But what should the standard color space look like? And who should setup the specification of the standard color space? Fortunately, ICC has this covered. ICC stands for International Color Consortium, and was established in 1993 by eight industry vendors. The purpose of ICC is to create, promote and encourage the standardization and evolution of an open, vendor-neutral, cross-platform color management system architecture and components. And the outcome is the ICC profile specification. ICC profile is the key to achieve open source color management workflow. It contains information related to the device characteristic, and both forward and backward transformations from device to the standard color space, which is called PCS (Profile Connection Space) in ICC color transformation. ICC color transformation is illustrated in Figure 6.

But how can ICC color transformation be utilized in practice? Let’s look at the example in Figure 7. When a user scans a color from a scanner, it reads (R, G, B) = (42, 82, 171). If the user would like to print out the same color as the scanned color, ICC workflow will first transform the scanned color to (L*, a*, b*) = (61, 11, 43) in PCS by using scanner ICC profile. Then by using the printer ICC profile, (L*, a*, b*) = (61, 11, 43) is determined to be (C, M, Y, K) = (57, 20, 0, 0) for the printer. By comparing (R, G, B) = (42, 82, 171) from the scanner and (C, M, Y, K) = (57, 20, 0, 0) from the printer, the user will find the colors are very similar. This illustrates the overall ICC workflow.

In this article, we have discussed the concept of color management and its goal to have a consistent color appearance across different devices. We also talked about color gamut and how to setup transformations between two or more devices. Lastly, we introduced ICC and ICC profile, and how ICC workflow is utilized in practice. In our next article, we will talk about who should really utilize ICC workflow and how it should be done.