If delivery depends on preserving lightness, do not rely on Hue Saturation Intensity’s Preserve lightness switch: Kdenlive’s manual says lightness processing is not yet implemented and marks the effect as having known bugs. Choose a correction path whose behavior you can verify for the requirement, or arrange a manual review of the relevant frames. If lightness preservation is not essential, you can consider the effect, but treat it as a candidate for a local comparison, not as an assured result.
Decide whether the requirement is a blocker
Translate the brief into a visible acceptance condition before adjusting anything. “Keep the logo’s color” and “change greens without making the image appear brighter or darker” are different requirements. The second depends directly on lightness preservation; the first may not, though the manual’s general known-bug warning still calls for review.
Kdenlive documents this effect as operating in RGB. Its controls include a color-range selection, Hue shift, Saturation shift, Intensity shift, Strength, RGB weights, and Preserve lightness. The manual specifically notes that hue adjustments can change lightness, while also warning that lightness processing is not implemented. See the effect documentation for the listed controls and caveat. A control being visible in the interface is not evidence that its stated aim is fulfilled.
Use this decision rule:
- Identify which image areas and frames must meet the brief, and write down whether their apparent lightness must remain stable.
- If stable lightness is a delivery requirement, exclude Preserve lightness as a dependable safeguard. Pick another correction approach that can be judged against the requirement, or set a review gate before delivery.
- If it is not a requirement, select the intended color range and make a restrained trial. Record the chosen values for Hue, Saturation, Intensity, and Strength; do not infer that any setting will produce a particular visual result.
- Compare the trial with the untreated frame at the same display conditions. Check the target area and nearby areas that should not change.
- Accept only if the observed result meets the written brief on the frames that matter. A favorable single frame does not establish that every relevant frame passes.
The comparison procedure is editorial guidance, not a Kdenlive guarantee or a report of software testing.
Record a frame-level acceptance check
The following is a hypothetical delivery review for a short clip with a green product label. The client requires the label hue to change but has not specified stable lightness. These observations are sample entries to show how to record a decision; they are not predicted effect behavior.
| Review item | Hypothetical observation | Decision to record |
|---|---|---|
| Requirement | Change the green label; no explicit lightness-preservation requirement | Trial may proceed, subject to the known-bug review gate |
| Reference frame | At 00:08, the label is visible beside a neutral gray panel | Use this frame as a side-by-side comparison point |
| Untreated comparison | Label appears green; gray panel is the visual reference | Keep the frame and display conditions consistent for review |
| Trial result | In this hypothetical observation, the label shifts, while the reviewer notices the gray panel also looks different | Do not assume the change is limited to the intended subject; inspect other relevant frames |
| Acceptance | A second reviewer must judge the label and the gray reference against the brief | Accept only if both meet the stated requirement; otherwise reject or revise the correction path |
Note whether the effect was used and whether the check was a manual visual review. Do not describe a hypothetical observation as a reproduced bug.
Limits and next steps if it fails
The manual’s “known bugs” status does not describe a specific failure mode, so do not attribute an observed change to a particular defect without evidence. Likewise, the note that lightness processing is not implemented does not establish what every other control will do on your footage. The effect’s color-range options are selections among listed primary and complementary colors, not a documented guarantee of object-level isolation.
If a frame fails the acceptance check, first decide whether the unmet requirement is lightness stability, color accuracy, or unwanted changes elsewhere. If it is lightness stability, do not try to solve it by treating the Preserve lightness switch as effective. Try a different correction route that offers a checkable result, or send the affected frames for manual review. If the problem is unwanted spill, reassess whether the selected range is suitable; the manual does not promise a spatial mask or a particular isolation method. Retest only against the relevant acceptance criteria, and record the outcome as a review, not as proof that the effect is generally reliable.
Common questions
Does Preserve lightness guarantee unchanged lightness? No. The manual says lightness processing is not yet implemented.
Does “known bugs” identify the defect I will encounter? The cited page flags known bugs but does not specify their manifestations.
Can I still use the effect if lightness is not critical? You can evaluate it for that task, but review the relevant frames and avoid claiming an unverified result.
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 film workspace. The external software controls discussed above belong to their respective products.