|
|
505.
|
|
|
Calibrating is important if you care about the colors you display or print.
|
|
|
(itstool) path: info/desc
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-why-calibrate.page:7
|
|
|
507.
|
|
|
Generic profiles are usually bad. When a manufacturer creates a new model, they just take a few items from the production line and average them together:
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-why-calibrate.page:19
|
|
|
509.
|
|
|
Display panels differ quite a lot from unit to unit and change substantially as the display ages. It is also more difficult for printers, as just changing the type or weight of paper can invalidate the characterization state and make the profile inaccurate.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-why-calibrate.page:29
|
|
|
510.
|
|
|
The best way of ensuring the profile you have is accurate is by doing the calibration yourself, or by letting an external company supply you with a profile based on your exact characterization state.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-why-calibrate.page:37
|
|
|
520.
|
|
|
This is what the user sees on a typical business laptop screen
|
|
|
(itstool) path: figure/desc
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-whyimportant.page:40
|
|
|
523.
|
|
|
The basic problem we have here is that each device is capable of handling a different range of colors. So while you might be able to take a photo of electric blue, most printers are not going to be able to reproduce it.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-whyimportant.page:54
|
|
|
524.
|
|
|
Most image devices capture in RGB (Red, Green, Blue) and have to convert to CMYK (Cyan, Magenta, Yellow, and Black) to print. Another problem is that you can't have <em>white</em> ink, and so the whiteness can only be as good as the paper color.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-whyimportant.page:60
|
|
|
525.
|
|
|
Another problem is units. Without specifying the scale on which a color is measured, we don't know if 100% red is near infrared or just the deepest red ink in the printer. What is 50% red on one display is probably something like 62% on another display. It's like telling a person that you've just driven 7 units of distance, without the unit you don't know if that's 7 kilometers or 7 meters.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-whyimportant.page:67
|
|
|
526.
|
|
|
In color, we refer to the units as gamut. Gamut is essentially the range of colors that can be reproduced. A device like a DSLR camera might have a very large gamut, being able to capture all the colors in a sunset, but a projector has a very small gamut and all the colors are going to look "washed out".
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-whyimportant.page:77
|
|
|
527.
|
|
|
In some cases we can <em>correct</em> the device output by altering the data we send to it, but in other cases where that's not possible (you can't print electric blue) we need to show the user what the result is going to look like.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-whyimportant.page:85
|
