From 3c15f8e4cdd0164ebe1abd2b02e1c14b0c0f979d Mon Sep 17 00:00:00 2001 From: Chris Elston Date: Sat, 8 Jun 2024 00:20:54 +0100 Subject: [PATCH] color-calibration: Minor tweaks --- .../module-reference/processing-modules/color-calibration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/module-reference/processing-modules/color-calibration.md b/content/module-reference/processing-modules/color-calibration.md index 244ecbf5cd..3979f155d6 100644 --- a/content/module-reference/processing-modules/color-calibration.md +++ b/content/module-reference/processing-modules/color-calibration.md @@ -2,7 +2,7 @@ title: color calibration id: color-calibration weight: 10 -applicable-version: 4.6 +applicable-version: 4.8 tags: working-color-space: RGB view: darkroom @@ -289,7 +289,7 @@ This operation can be repeated as many times as you have images in your series w ## step 3: deactivate color mapping -The settings you configured in *step 1* are sticky -- they will stay active until you manually turn them off by resetting *lightness* to 50 and *chroma* to 0. Until then, *every* time you use this module (even after closing and restarting darktable), those settings will affect the results of an auto-whitebalance operation. To remind you that color mapping is active, especially while the section is collapsed, the heading will change from "area color mapping" to "area color mapping (active)" whenever *chroma* is nonzero or *lightness* is other than 50. +The settings you configured in _step 1_ are sticky -- they will stay active until you manually turn them off by resetting _lightness_ to 50 and _chroma_ to 0. Until then, _every_ time you use this module (even after closing and restarting darktable), those settings will affect the results of an auto-whitebalance operation. To remind you that color mapping is active, especially while the section is collapsed, the heading will change from "area color mapping" to "area color mapping (active)" whenever _chroma_ is nonzero or _lightness_ is other than 50. ---