When a camera won't match cleanly

If a clip resists matching, it is usually the display LUT or the grouping, not the camera. What to check, and how to send a useful sample.

Most "MOVON cannot match my camera" reports turn out to be one of two upstream issues, both fixable in Premiere before the match runs. This page is the short checklist, followed by what to send if the match still misses after the checklist passes.

Before reporting: two upstream checks

1. The display LUT on the source clip

MOVON matches displayable signal, not raw LOG. A clip without the correct Input LUT in Lumetri Color shows up to the match as a flat, low-contrast file that does not look like any other camera, and the match pulls it in a direction the rest of the timeline does not want.

In Premiere, the right slot is Lumetri Color → Basic Correction → Input LUT on the source clip. Sony S-Log3 → Rec.709, Canon C-Log3 → Rec.709, DJI D-Log → Rec.709, and so on. Use the camera manufacturer's own conversion LUT; Premiere ships the common ones, and the rest live on each camera maker's support site.

Get the Input LUT right and the match usually snaps into place without anything else changing. The longer story is at Log to display.

2. The grouping

Open the MOVON panel after Analyze finishes. Each clip is marked with the group it landed in. Two things to confirm:

• Every clip from the same physical camera is in the same group. Mixed-profile clips (a camera that recorded part of the day in LOG and part in a baked profile) sometimes split. Move them into one group manually.
• No clip from a different camera was pulled into a group. A heavily-processed in-camera look can occasionally read as a separate camera to MOVON. Move it to its own group, or treat that clip outside the automated match.

Regroup and re-analyze. The fix rate after a regrouping pass is high enough that most "bad match" reports never make it past this step.

When the match still misses

If the Input LUT is correct and the grouping is clean and the match is still off, the next stop is Match looks wrong, which walks the three in-product fixes (intensity pull-back, hero reselection, scene isolation) in order. Try those before sending a report.

What to send

If the match still misses after the checklist and the three in-product fixes, the homepage Contact form reaches MOVON Labs directly. A useful report contains:

• The two source clips that disagree: one short hero clip (5-10 seconds) and one short mismatched clip from the same scene. Original camera files if possible, otherwise H.264 transcodes that preserve the LOG color space. Anything that was already rendered to Rec.709 has the original signal baked in and is less useful for diagnosis.
• A screenshot of the MOVON panel showing the grouping plan and the hero pick.
• The Input LUT applied in Lumetri (or "none" if the clip was already in display space).
• Camera models of the two clips, if known. Not because MOVON needs them, but because the team uses them to build the training corpus over time.
• Mac model and macOS version (Apple menu → About This Mac).
• One sentence on what "off" means here. Skin too warm? Whites pulled green? Saturation drop? The team triages reports faster when the symptom is named.

A report with the two clips, the screenshot, and one sentence on the symptom is usually enough. Long write-ups are welcome but not necessary.

What happens to the report

The clips and the screenshot stay with MOVON Labs. They feed two things:

• Diagnosis on the specific report. Most reports get a same-week reply with either a workaround or a flag for the next build.
• The model's training set. Anonymized examples of mismatches feed the next training cycle so the same case improves on a later build. Sending a report is the most direct way to make the next match better, including for the camera that triggered this one.

Anything submitted via the Contact form is private to MOVON Labs and is not shared, resold, or used for anything other than improving the match.