Real World Adobe® Photoshop® CS2 [Electronic resources] : Industrial-Strength Production Techniques نسخه متنی

This is a Digital Library

With over 100,000 free electronic resource in Persian, Arabic and English

Real World Adobe® Photoshop® CS2 [Electronic resources] : Industrial-Strength Production Techniques - نسخه متنی

Bruce Fraser, David Blatner

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
توضیحات
افزودن یادداشت جدید












Color Management Systems Explained


A color management system (CMS) is a set of software tools that attempts to maintain the appearance of colors as they're reproduced by different devices. We stress the word "appearance" because it's simply impossible to reproduce many of the colors found in the world in print, or even on a color monitor.

Color management often gets dressed up in much fancier clothing, but it really does only two things.

It lets you assign a specific color appearance to RGB or CMYK numbers that would otherwise be ambiguous.

Within the physical limitations of the devices involved, it lets you keep that specific color appearance as you send your images to different displays and output devices.


The options may sometimes appear more complex, but if you break them down, you'll find that they always do some combination of the above two tasks.


CMS Components


All CMSs employ three basic components:

The reference color space (also known as the profile connection space, or PCS) is a device-independent, perceptually based color space. Most current CMSs use a CIE-defined color space, such as CIE Lab or CIE XYZ. You never have to worry about the reference color space; it's the theory behind how the software works.

The color-matching engine (sometimes known as the color matching method, or CMM) is the software that does the conversion between different device-specific color spaces. Photoshop CS supports other color matching engines besides the Adobe-branded one (ACE) that it shares with the other Adobe Creative Suite applications, but the only reason we can see for using a different engine is if you absolutely must obtain exactly the same conversions from non-Adobe products. In general, the differences between the various CMMs are slight.

Profiles usually describe the behavior of a device like a scanner, monitor, or printer. For instance, a profile can tell the CMS "This is the reddest red that this device can output." A profile can also define a "virtual color space" that's unrelated to any particular device (the Adobe RGB space is an example of this; we'll see how it's useful later on). Profiles are the key to color management. Without a profile, 100-percent Red has no specific meaning; with a profile, the color management system can say "Oh, that color red!" Thanks to the ICC (International Color Consortium), device profiles conform to a standard format that lets them work with all CMSs on all platforms. ColorSync profiles on the Mac and .icm or .icc profiles on Windows both follow the ICC spec and are interchangeable between platforms.


The key point is that profiles define the actual color appearancethe color that we seethat any given set of RGB or CMYK numbers produce on the device (a monitor, a desktop printer, a proofing system, a printing press) whose behavior the profile describes.


Conveying Color Meaning


The key concept in using a CMS is conveying color meaningmaking those ambiguous RGB and CMYK values unambiguous. If the system is going to keep the color consistent among different devices, it needs to know what color appearance each device in the process represents using RGB or CMYK numbers. If a CMS knows what RGB values a scanner produces when it scans specific colors, and knows what colors a display produces when we send it specific RGB numbers, it can calculate the new RGB numbers it needs to send to the display to make it reproduce the colors represented by the scanner RGB numbers.


Profile embedding


When you embed a profile in an image, you aren't changing the image. You're simply providing a definition of what the numbers in the file mean in terms of actual colors you can seeyou're assigning a specific color appearance to the RGB or CMYK numbers. If you don't embed profiles in your images, the numbers in the file are ambiguous and open to many different interpretations. Embedding a profile simply tells color-management-savvy applications which interpretation you want to place on the numbers. Profile embedding is the easiest way to convey the color meaningthe intended color appearanceof the numbers in the digital image.


Source and target profiles


When you ask the color management system to make a conversionto change the numbers in the filethe CMS needs to know where the RGB or CMYK color values came from and where you want to send them. Whenever you open or create an image, you have to give the CMS this information by specifying a source profile and a target profile.

The source profile (which is sometimes already embedded in the file) says, "This RGB data is from such-and-such a scanner," or "This RGB data is from such-and-such a monitor." This tells the CMS what actual colors RGB or CMYK numbers represent. The target profile tells the CMS where the image is going, so that it can calculate the new RGB or CMYK numbers that will maintain the color in the image on the target device.

For example, imagine that color management systems work with words rather than colors. The purpose of the word-CMS is to translate words from one language to another. If you just feed it a bunch of words, it can't do anything. But if you give it the words and tell it that they were written by a French person (the source), it all of a sudden can understand what the words are saying. If you then tell it that you speak German (the target), it can translate the meaning faithfully for you.


The process


Back to pictures: When you scan some artwork, you end up with a lot of RGB data. But for Photoshop to know what specific colors those RGB values are meant to represent, you have to tell it that the RGB data came from this particular scanner. When you choose your scanner's device profile as the source profile, you're telling Photoshop that this isn't just any old RGB data; it's the RGB data carefully defined by the scanner's device profile.

To make the image on your printer match the original, you choose your printer profile as the target profile. The CMS takes the RGB values in the image and uses the scanner profile as the secret decoder ring that tells it what colors (in the reference color space) the RGB values represent. Then it calculates new RGB or CMYK values based on the printer profile, to produce the same colors when they're printed on your printer.

This is really the only thing CMSs do. They convert color data from one device's color space (one "language") to another. Pretty much everything you do with a CMS involves asking it to make the colors match between a source and a target profile, and this same two-step is integral to the way Photoshop CS handles color.


Rendering intents


There's one more wrinkle. Each device has a fixed range of color that it can reproduce, dictated by the laws of physics. Your monitor can't reproduce a more saturated red than the red produced by the monitor's red phosphor. Your printer can't reproduce a cyan more saturated than the printer's cyan ink, or a white brighter than the white Soft-Proofing Controls," later in this chapter.

Relative Colorimetric. The Relative Colorimetric intent maps white in the source to white in the target, so that white on your output is the white of the paper rather than the white of the source space, which may be different. It then reproduces all the in-gamut colors exactly, clipping out-of-gamut colors to the closest reproducible hue. For images that don't contain significant out-of-gamut colors, it's often a better choice than Perceptual because it preserves more of the original colors.

Absolute Colorimetric. The Absolute Colorimetric intent is the same as Relative Colorimetric, except that it doesn't scale source white to target white. If your source space has a bluish white, and your output is on a yellowish-white paper, Absolute Colorimetric rendering makes the printer lay down some cyan ink in the white areas to simulate the white of the original. It's generally only used for proofing (see "Soft-Proofing Controls" later in this chapter).


When you use a CMS to convert data from one color space to another, you need to tell it three pieces of information: the source profile, the target profile, and the rendering intent. You can think of these three elements as where the color comes from, where the color is going, and how you want the color to get there. But before you go hog-wild, converting images willy-nilly from one space to another, a cautionary note is needed.


Space conversions and data loss


Bear in mind that even the best CMS degrades your image when you convert it from one color space to another. Even though the conversions may be very accurate, you still want to limit their number (any color space conversion involves some loss, due to rounding and quantization errors). That's why Photoshop has taken a somewhat different approach to color management than most other applications. Rather than make you transform images continually from one device's color space to another's, thus degrading the image, Photoshop offers a reasonable place for images to live: a device-independent RGB working space.


/ 219