Warning, /documentation/digikam-doc/setup_application/cm_settings.rst is written in an unsupported language. File is not indexed.
0001 .. meta:: 0002 :description: digiKam Color Management Settings 0003 :keywords: digiKam, documentation, user manual, photo management, open source, free, learn, easy, configure, setup, color management, icc, profile 0004 0005 .. metadata-placeholder 0006 0007 :authors: - digiKam Team 0008 0009 :license: see Credits and License page for details (https://docs.digikam.org/en/credits_license.html) 0010 0011 .. _cm_settings: 0012 0013 Color Management Settings 0014 ========================= 0015 0016 .. contents:: 0017 0018 Overview 0019 -------- 0020 0021 digiKam is color-management enabled application. RAW files - as they come - are not color managed at all. Your camera provides the data it has captured in a raw format and will let you manage all the processing. Every camera has its specifics as to how it captures color information, therefore you will need to apply a specific profile to the images you want to process. Please refer to the section :ref:`ICC color profile management <color_management>` for more details an explanations. 0022 0023 Basically, a profile *maps* the color information and gives information on how one should render them. It gives also information to Lcms backend and digiKam on how to translate the color information from one color space to an other in order to keep the colors as accurate as possible across all rendering media. 0024 0025 Behavior Settings 0026 ----------------- 0027 0028 The **Behavior** view ask when opening an image in Image Editor or when you use the Color Management tool with RAW files. 0029 0030 .. figure:: images/setup_cm_behavior.webp 0031 :alt: 0032 :align: center 0033 0034 The Color Management Behavior Configuration Page 0035 0036 **Enable Color Management** is the lead option to turn on/off this feature. 0037 0038 You have to provide a **Working Color Space** profile (linear profiles such as sRGB, ECI-RGB, LStar-RGB, Adobe-RGB or CIE-RGB). If you want to print your images, you may want to opt for Adobe RGB, if it is only for web publishing, sRGB is better (Adobe RGB will be displayed slightly dull in non color managed enabled software such as browsers). However you may change this later of course (by attributing another profile), therefore Adobe RGB can be a good choice for storing and image handling as you can always change it to sRGB before releasing an image for your blog. Note: Do not use non-linear profiles as they will change the color-balance. 0039 0040 The three next sections from this view set the rules for different use cases: 0041 0042 - **When the profile of an image does not match the working color space**: this condition provides two options listed below. 0043 0044 - **Ask when opening the image**: If an image has an embedded color profile not matching the working space profile, digiKam will ask if you want to convert to the working space, keep the embedded profile or discard the embedded profile and assign a different one. 0045 0046 - **Convert the image to the working color space**: If an image has an embedded color profile not matching the working space profile, digiKam will convert the image's color information to the working color space. This changes the pixel data, but not the appearance of the image. 0047 0048 - **When an image has no color profile information**: this condition provides four options listed below. 0049 0050 - **Ask when opening the image**: If an image has no embedded color profile, digiKam will ask which color space shall be used to interpret the image and to which color space it shall be transformed for editing. 0051 0052 - **Assume it is using the sRGB color space**: in this case, the image is target for an Internet usage. The **and convert it to the working color space** allows to force conversion to the **Working Color Space** previously defined. 0053 0054 - **Assume it is using the working color space**: in this case, the image is not target for a specific usage, and **Working Color Space** is used for the conversion. 0055 0056 - **Convert it from default input color space to working space**: in this case, the conversion to the **Working Color Space** will be done to include the **Default input color profile** defined in the next settings view. 0057 0058 - **When loading a RAW file with uncalibrated colors**: this condition provides three options listed below. 0059 0060 - **Ask for the input profile**: digiKam prompts a question to the user to select right **Input color profile** to use. 0061 0062 - **Automatic color correction**: digiKam will perform an automatic colors auto-correction based of image historgram analysis. 0063 0064 - **Convert it from the default input profile**: digiKam will use the **Default input color profile** defined in the next settings view. 0065 0066 Profiles Settings 0067 ----------------- 0068 0069 The ICC **Profiles Settings**: here you are given the ability to provide *default* choices for your profiles. Everything is adaptable later-on at the opening of a RAW file. 0070 0071 .. figure:: images/setup_cm_profiles.webp 0072 :alt: 0073 :align: center 0074 0075 The Color Management Profiles Configuration Page 0076 0077 The **Monitor profile** option allows to select the color profile for your screen. 0078 0079 The **Use color managed view** is an alternative to using desktop color management. Only your image in editor will be color managed, not your entire screen. You can at any time toggle this option everywhere in digiKam. This can slow down rendering of the image, depending on the speed of your computer. 0080 0081 **Use color managed view for previews and thumbnails**: with this option, you can also use the color management to render previews and thumbnails in Icon-View, Light-Table, and Import Tool. 0082 0083 The **Default Input color profile** should match the camera maker and model you are using. *Not all profiles are created equal*, there are some that have no tone mapping/gamma correction included (For example Canon camera). In some conditions gamma can be not corrected for 16 bit depth conversion, which means that you have to do the tone mapping yourself. 0084 0085 The **Output device profile** should match the profile for your output device, usually your printer. This profile will be used to do a :ref:`soft proof <soft_proof>`, so you will be able to preview how an image will be rendered via an output device. It enables you to emulate, granted that you have a profile for it, how your image will render for a particular device. It is useful before printing for instance because your printer has a smaller gamut than your camera and some colors might look saturated. You may want to fix this manually instead of relying on the "blind" algorithm of your printer. 0086 0087 The **Color Profiles Repository**: digiKam looks for ICC profiles in a number of default locations e.g. :file:`/usr/share/color/icc`. Set this to the folder where you store extra profiles e.g. :file:`/home/user/.color/icc`. digiKam will scan these folders when starting up. 0088 0089 Advanced Settings 0090 ----------------- 0091 0092 **Use black point compensation**: this setting is a way to make adjustments between the maximum black levels of digital files and the black capabilities of various digital devices. 0093 0094 **Rendering Intents**: this setting provides four options listed below. 0095 0096 - **Perceptual**: causes the full gamut of the image to be compressed or expanded to fill the gamut of the destination device, so that gray balance is preserved but colorimetric accuracy may not be preserved. In other words, if certain colors in an image fall outside of the range of colors that the output device can render, the image intent will cause all the colors in the image to be adjusted so that the every color in the image falls within the range that can be rendered and so that the relationship between colors is preserved as much as possible. This intent is most suitable for display of photographs and images, and is the default intent. 0097 0098 - **Relative Colorimetric**: is defined such that any colors that fall outside the range that the output device can render are adjusted to the closest color that can be rendered, while all other colors are left unchanged. Proof intent does not preserve the white point. 0099 0100 - **Absolute Colorimetric**: causes any colors that fall outside the range that the output device can render to be adjusted to the closest color that can be rendered, while all other colors are left unchanged. This intent preserves the white point and is most suitable for spot colors (Pantone, TruMatch, logo colors, etc.). 0101 0102 - **Saturation**: preserves the saturation of colors in the image at the possible expense of hue and lightness. Implementation of this intent remains somewhat problematic, and the ICC is still working on methods to achieve the desired effects. This intent is most suitable for business graphics such as charts, where it is more important that the colors be vivid and contrast well with each other rather than a specific color. 0103 0104 .. figure:: images/setup_cm_advanced.webp 0105 :alt: 0106 :align: center 0107 0108 The Color Management Advanced Configuration Page 0109 0110 .. note:: 0111 0112 For most cameras it is pretty obvious what color profile they propose for the type at hand, not so for the Canon's. Here is a table of camera/profiles matches, it is non-authoritative of course: 0113 0114 ================== ============== 0115 Camera Profile series 0116 ================== ============== 0117 Canon 1D mark II 6051 0118 Canon 1D mark II 6111 0119 Canon 1Ds 6021 0120 Canon 1Ds mark II 6081 0121 Canon 5D 6091 0122 Canon 10D 6031 0123 Canon 20D 6061 0124 Canon 30D 6112 0125 Canon 40D 6101 0126 Canon 300D 6031 0127 Canon 350D 6111 or 6071 0128 Canon 400D 6131 0129 ================== ============== 0130 0131 The Canon profile extension betray the target style: F for Faithful Style, L for Landscape Style, N for Neutral Style, P for Portrait Style, S for Standard Style. 0132 0133 Here you find a typical :ref:`RAW workflow <rawprocessing_workflow>` scenario with Image Editor.