<style>[data-reveal] > *,[data-reveal] [data-reveal-child]{opacity:1!important;transform:none!important;filter:none!important}</style>
DocsTroubleshootingMatch looks too aggressive or off
TS°01·Troubleshooting·4 min read

Match looks too aggressive or off

Intensity control, reference reselection, scene isolation. Three things to try, in order.

Last updated May 24, 2026

A bad match is almost never a model bug. It is almost always one of three things: the intensity, the reference, or a scene that wanted to be matched on its own. This page walks the three in the order they are worth trying.

Before any of this, check that display LUTs are applied on the source clips via Lumetri Color → Basic Correction → Input LUT. MOVON matches displayable signal; raw LOG on the timeline produces a match that looks dramatically wrong because the source itself is not viewable. Log to display covers why.

1. Pull the intensity back

The match is calibrated to err toward over-matching, on purpose. Dialing back is faster than chasing missing color, and the easiest knob is at the apply step.

In Lumetri Color, the matched .cube lives in Creative → Look by default. The slider directly below the Look picker is the intensity. Pull it to 70-80%.

This single change fixes most "the match is fighting me" complaints. Skin tones especially benefit from a touch of dial-back; the eye reads skin more critically than scopes do.

NOTE
Once MOVON's own effect ships (in active development), the same intensity control will live on the effect itself, so this step gets shorter.

2. Reselect the reference

If the timeline still looks wrong with intensity pulled back, the reference is probably wrong for this project.

The reference is the target every selected clip is pulled toward, so its flaws become everyone's flaws. A good reference has:

  • Clean whites in a representative scene.
  • Honest exposure (not crushed, not blown).
  • The skin tones the project wants to keep.

Open the panel, pick a reference that fits the description above, and re-run. MOVON re-computes the match against the new reference. The LUTs change to point at the new target.

A common case: an A-cam clip was picked as the reference because that camera carried the most footage, but a B-cam clip in better light was the one that nailed the look. Pick the B-cam clip. The match tightens.

3. Match a scene on its own

Sometimes the timeline has one scene that just refuses to play with the rest, usually for a real reason: a different lighting setup, a sunset, an interior on a different day. The whole-timeline match averages across all of it, and the outlier scene drags the LUT in a direction nothing else wants.

Two options:

  • Lift the outlier scene to a sub-timeline (nested sequence) and run MOVON against just that sequence. A separate reference, a separate match. Stitch back into the main edit. This is the cleanest fix when the scene is large enough to deserve its own match.
  • Override the offending clips by hand with Lumetri Curves and HSL on top of the matched .cube. MOVON's job is to get the cameras roughly agreeing; per-shot taste tweaks are part of the grade.

When none of the three work

If intensity is dialed back, the reference is right, and scene isolation does not change much, the issue is usually upstream of MOVON. Two checks:

  • Wrong display LUT on a clip. Sony S-Log3 footage with a V-Log Input LUT looks wrong from the start; matching that against a correctly-converted reference amplifies the problem. Confirm the Input LUT on each source clip.
  • Mixed in-camera looks. A clip that was already heavily processed in-camera (a strong creative profile, a baked LUT) behaves differently under the match. Leave it out of the selection and match it in its own pass, or treat that clip separately.

Send a sample

If the match still misses, the report path is Report a bad match. A short clip pair (one reference frame, one mismatched frame) and a panel screenshot of the selection is usually enough to diagnose.

Was this helpful?