When we make an image in Krita, and print that out with a printer, the image tends to look different. The colours are darker, or less dark than expected, maybe the reds are more aggressive, maybe contrast is lost. For simple documents, this isn’t much of a problem, but for professional prints, this can be very sad, as it can change the look and feel of an image drastically.
The reason this happens is simply because the printer uses a different color model(CMYK) and it has often access to a lower range of colors(called a gamut).
A naive person would suggest the following solution: do your work within the CMYK color model! But there are three problems with that:
- Painting in a CMYK space doesn’t guarantee that the colors will be the same on your printer. For each combination of Ink, Paper and Printing device, the resulting gamut of colors you can use is different. Which means that each of these could have a different profile associated with them.
- Furthermore, even if you have the profile and are working in the exact color space that your printer can output, the CMYK color space is very irregular, meaning that the color maths isn’t as nice as in other spaces. Blending modes are different in CMYK as well.
- Finally, working in that specific CMYK space means that the image is stuck to that space. If you are preparing your work for different a CMYK profile, due the paper, printer or ink being different, you might have a bigger gamut with more bright colors that you would like to take advantage of.
So ideally, you would do the image in RGB, and use all your favorite RGB tools, and let the computer do a conversion to a given CMYK space on the fly, just for preview. This is possible, and is what we call ‘’Soft Proofing’‘.
You can toggle soft proofing on any image using Ctrl + Y. Unlike other programs, this is per-view, so that you can look at your image non-proofed and proofed, side by side. The settings are also per image, and saved into the .kra file. You can set the proofing options in.
There you can set the following options:
- Profile, Depth, Space
- Of these, only the profile is really important. This will serve as the profile you are proofing to. In a professional print workflow, this profile should be determined by the printing house.
Set the proofing Intent. It uses the same intents as the intents mentioned in the color managed workflow.
- Adaptation State
- A feature which allows you to set whether Absolute Colorimetric will make the white in the image screen-white during proofing(The slider set to max), or whether it will use the white point of the profile(The slider set to minimum). Often CMYK profiles have a different white as the screen, or amongst one another due to the paper color being different.
- Black Point Compensation
- Set the black point compensation. Turning this off will crunch the shadow values to the minimum the screen and the proofing profile can handle, while turning this on will scale the black to the screen-range, showing you the full range of grays in the image.
- Gamut Warning
- Set the color of the out-of-gamut warning.
You can set the defaults that Krita uses in
To configure this properly, it’s recommended to make a test image to print(and that is printed by a properly set-up printer) and compare against, and then approximate in the proofing options how the image looks compared to the real-life copy you have made.
Out of Gamut Warning¶
The out of gamut warning, or gamut alarm, is an extra option on top of Soft-Proofing: It allows you to see which colors are being clipped, by replacing the resulting color with the set alarm color.
This can be useful to determine where certain contrasts are being lost, and to allow you to change it slowly to a less contrasted image.
You can activate Gamut Warnings with Ctrl + Shift + Y, but it needs soft proofing activated to work fully.
Soft Proofing doesn’t work properly in floating-point spaces, and attempting to force it will cause incorrect gamut alarms. It is therefore disabled.
Gamut Warnings sometimes give odd warnings for linear profiles in the shadows. This is a bug in LCMS, see here for more info.