If two shots look warm and cool, compare the same scene area in the waveform and RGB Parade before changing either shot. When the waveform’s luma patterns sit in similar positions but a credible neutral area separates into different RGB levels, investigate a color cast. When the RGB contours are roughly aligned but the luma pattern is shifted, investigate brightness first. These scopes provide evidence, not an automatic diagnosis: confirm that you are comparing the same material under comparable conditions.
A practical decision sequence
- Choose one visible region present in both shots, such as a matte gray wall. Keep the viewer framing and the selected moment consistent. Avoid glare, deep shadow, clipped highlights, or a patch whose neutrality is uncertain.
- Set Components to Y in the Video Waveform Monitor to inspect luma; All is the documented default and displays YUV, so do not treat an All-components trace as a luma-only waveform. Kdenlive describes the waveform as plotting component intensity, with each graph column corresponding to a column of source pixels. Compare the selected region’s pattern and its relationship to highlights and shadows. A broadly similar position is evidence that overall brightness may already be close; a shifted pattern suggests a brightness difference to investigate. Do not treat a trace touching a guide as a fault by itself.
- Inspect RGB Parade on that same region. The Kdenlive manual says neutral whites, grays, and blacks should have roughly equal RGB waveform dimensions. If the region appears neutral in the scene but the channels separate, record which channel differs and whether the separation appears in highlights, shadows, or both. A single separated channel is a clue, not proof: the object may not be neutral, or the two shots may have different lighting.
- Choose the smallest correction supported by both observations. Similar luma with separated neutral-area channels points toward color correction; similar RGB contours with shifted luma points toward brightness. If both differ, address them as separate problems and reassess after each change. Kdenlive’s Color Temperature effect is one available control; its manual describes Kelvin adjustment and a lightness-preservation parameter, but does not guarantee a particular result for a given shot.
- Return to the same frame region and compare both scopes again. Record whether the diagnosed difference narrowed without introducing an unwanted shift elsewhere in the image.
Kdenlive’s waveform display offers luminance and component display modes, while Parade separates color-component graphs. See the Video Waveform Monitor documentation. For the temperature control and its parameters, see Color Temperature documentation. The comparison procedure above is an editorial workflow, not a documented automatic matching feature.
Hypothetical comparison worksheet
The readings below are hypothetical teaching values, not Kdenlive measurements or a promise about how a scope will display a sample. They illustrate how to keep the brightness and channel questions separate.
| Check | Shot A | Shot B | Observation and decision |
|---|---|---|---|
| Comparison area | Matte gray wall, mid-frame | Same wall, matched moment | Use only if the patch receives comparable light and is plausibly neutral |
| RGB Parade levels, normalized example | R 0.58, G 0.58, B 0.57 | R 0.62, G 0.54, B 0.49 | Shot B has more channel separation in the assumed neutral patch; investigate color before changing overall brightness |
| Luma waveform pattern | Main wall trace near the same level | Main wall trace near the same level | Similar placement does not support brightness as the first correction target |
| After correction | Recheck the same wall and nearby highlights | Recheck the same wall and nearby shadows | Record whether channel separation narrowed and whether luma placement stayed acceptably similar |
The example does not identify a correct temperature value. The final observation should describe the image and scope evidence, not just the control you moved.
Limits and what to try next
A wall that looks gray on screen is not necessarily neutral; colored paint, reflected light, mixed lighting, or a lighting change between takes can explain channel differences. If no trustworthy neutral patch is shared, compare a second plausible neutral object and label the conclusion uncertain. Do not force RGB equality across the whole frame when the scene contains intentional colored light.
Waveform guide lines are not, on their own, evidence of a defect. Kdenlive documents graticules for legal broadcast ranges, but choosing delivery limits and deciding whether image detail is acceptable require context beyond the trace alone. If both scopes differ, determine whether the common area is lit differently before treating the discrepancy as a camera-setting error. If the scopes look aligned but the shots still feel different, inspect other shared objects and the surrounding scene; a single patch may not represent the whole image. The documentation describes scope modes and effect parameters, not a guarantee that a particular adjustment restores clipped or unrecorded detail.
Three quick questions
Does RGB separation always mean white-balance error? No. First verify that the sampled-looking region is a credible neutral and that lighting is comparable. The parade reveals channel relationships; it cannot establish what the object’s true color should be.
What if luma and RGB both differ? Treat them as two observations, not one combined diagnosis. Make a restrained correction for one diagnosed difference, then revisit the same region and reassess the other.
Can Color Temperature alone match two shots? Not necessarily. Kdenlive documents temperature, mix, saturation, and lightness-preservation controls, but the appropriate correction depends on the footage and the intended look. Compare the scopes and image after adjustment rather than assuming a setting will match the shots.
Sources and next step
- Video Waveform Monitor — Kdenlive 26.08 Manual 26.08 documentation
- Color Temperature — Kdenlive 26.08 Manual 26.08 documentation
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.