For a hue correction, start with color equalizer when you need to work in darktable’s scene-referred, RGB pipeline or when noise and abrupt color boundaries are prominent concerns. Consider color zones when its Lab LCh curve workflow suits the image and you can inspect or isolate the affected range. Neither module guarantees clean separation: the choice depends on the image and the amount of correction.
Decide and make the adjustment
- Identify the intended color and the areas next to it. Note whether the target shares similar hues with skin, clouds, foliage, or another subject. If those neighbors must remain unchanged, plan for a mask rather than relying on hue selection alone.
- Choose the processing approach. Color zones processes in non-linear Lab and lets you select pixels by hue, lightness, or chroma, then change lightness, chroma, and hue with separate curves. Color equalizer works in the scene-referred RGB part of the pipeline and adjusts hue, saturation, or brightness according to current hue.
- Make a restrained first correction. In color zones, use the picker to locate the target range on the curve; where the target overlaps important neighboring colors, add a drawn and/or parametric mask. Compare its default smooth mode with strong only if the adjustment needs more force: the manual says smooth is less likely to produce artifacts. In color equalizer, use the picker to locate the color on its curve. Its nodes have fixed, even spacing; the node-placement control shifts the whole set when the hue you want falls between nodes. Node colors are only cues: check the actual hue/saturation/brightness tab and picked position.
- Inspect the target, nearby colors, and boundaries at both fit-to-view and close zoom. If the adjustment causes noisy patches, an abrupt edge, or an unwanted neighboring-color shift, reduce its strength or revise the selection before judging the result.
Hypothetical acceptance worksheet
This example is a decision aid, not a promised software result. Suppose a blue sky borders a person’s skin, and the intended edit is a modest hue shift while keeping the face visually stable. Record what you observe in your own image; the manual does not specify a pixel-count threshold for choosing a module.
| Check | Hypothetical observation | Decision or next inspection |
|---|---|---|
| Processing context | The editor needs the scene-referred RGB workflow | Start with color equalizer; this matches its documented processing context |
| Target selection | Picked sky hue appears close to hues on the face | Do not assume hue alone separates sky from skin; test a mask with color zones, or assess the equalizer’s affected output visually |
| Boundary | A narrow band where sky meets hair or skin changes conspicuously | Reduce the correction and inspect the edge; with color zones, refine the drawn or parametric mask if needed |
| Noise and transition | Close inspection shows colored speckles or a hard-looking transition | Treat the edit as unsuccessful at that strength; reduce it and compare the modules or selection strategy |
| Final comparison | Sky changes, while skin and the boundary remain acceptable at the intended viewing size | Keep the less intrusive version, even if its hue shift is smaller |
Limits and next steps
Color zones can produce ungraceful transitions and can increase chroma or luma noise; its documentation recommends care and notes that masks may be needed to isolate practical edits. A mask is not a guarantee of a clean edge, so inspect where the target meets the face. If the required separation is too complex for the available mask, reduce the correction or use a more suitable masking workflow.
Color equalizer’s fixed nodes do not allow changing the spacing between individual nodes. The guided filter is intended to mitigate noise and harsh transitions, but the manual warns that it may not remove them entirely. Large corrections can still create artifacts. If noise remains, try a smaller correction and inspect the guided-filter controls: a larger hue-analysis radius may smooth introduced noise but can cause halos at edges; a larger effect radius can smooth the change but may bleed across boundaries. These are tradeoffs to evaluate, not guaranteed fixes. If neither approach preserves the neighboring skin, prioritize separation over a stronger hue shift.
Common questions
Does color equalizer always avoid artifacts? No. Its filter is a mitigation, not a guarantee. The manual advises care and cautions against very large changes.
When should I add a mask to color zones? When the selected color range also affects important neighboring areas, or when the transition is not acceptable. Use the mask to isolate the intended region, then inspect the edge.
Is this based on a local test? No. This guide interprets the supplied [darktable 5.6 color zones documentation](https://docs.darktable.org/usermanual/5.6/en/module-reference/processing-modules/color-zones/) and [color equalizer documentation](https://docs.darktable.org/usermanual/5.6/en/module-reference/processing-modules/color-equalizer/). No local software test or image comparison was performed.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.