|
|
523.
|
|
|
AdobeRGB is frequently used as an <em>editing space</em>. It can encode more colors than sRGB, which means you can change colors in a photograph without worrying too much that the most vivid colors are being clipped or the blacks crushed.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-whatisspace.page:62
|
|
|
525.
|
|
|
Now, if ProPhoto is clearly better, why don't we use it for everything? The answer is to do with <em>quantization</em>. If you only have 8 bits (256 levels) to encode each channel, then a larger range is going to have bigger steps between each value.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-whatisspace.page:75
|
|
|
526.
|
|
|
Bigger steps mean a larger error between the captured color and the stored color, and for some colors this is a big problem. It turns out that key colors, like skin colors are very important, and even small errors will make untrained viewers notice that something in a photograph looks wrong.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-whatisspace.page:81
|
|
|
527.
|
|
|
Of course, using a 16 bit image is going to leave many more steps and a much smaller quantization error, but this doubles the size of each image file. Most content in existence today is 8bpp, i.e. 8 bits-per-pixel.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-whatisspace.page:88
|
|
|
528.
|
|
|
Color management is a process for converting from one color space to another, where a color space can be a well known defined space like sRGB, or a custom space such as your monitor or printer profile.
|
|
|
(itstool) path: page/p
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/color-whatisspace.page:94
|
|
|
529.
|
|
|
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
|
|
|
531.
|
|
|
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
|
|
|
532.
|
|
|
external ref='figures/color-average.png' md5='9189963fdd14f11f0685a9ef2196279b'
|
| Context: |
|
_
|
|
|
(itstool) path: page/media
This is a reference to an external file such as an image or video. When
the file changes, the md5 hash will change to let you know you need to
update your localized copy. The msgstr is not used at all. Set it to
whatever you like once you have updated your copy of the file.
|
|
|
|
|
(no translation yet)
|
| In Ubuntu: |
|
(not translated yet)
|
|
|
|
Located in
C/color-why-calibrate.page:25
|
|
|
534.
|
|
|
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
|
|
|
535.
|
|
|
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
|
