RESOLVE 21 · TRANSFORM · TRACKER-DRIVEN WORKFLOW

Match Move.

Track the surface.
Place the insert. Confirm in motion.

Match Move on the Color page is a patch-based tracker and compositing tool. Route the external foreground through an Ext. Matte into the FX node’s second RGB input, choose Zoom/Rotation before analysis, then track, repair weak patches, fit the Positioning canvas and finish in Compositing. The live viewer here is a teaching proxy, not Resolve’s solver.

01 / WIRE

Clip + Ext. Matte · RGB 2

02 / TRACK

Model before solve · patches

03 / FINISH

Canvas · Composite · QC

Patch Size adjusts enlarged patch previews, not solve accuracy. Pick Zoom/Rotation before analysis, and do not use Global Blend to conceal a drifting track.

MATCH MOVE / REGISTRATION STUDY · EDUCATIONAL MODEL
SYNTHETIC SHOT / NOT OFXActive patches: 4 · PLANAR · frame 48/100
1234PAN / POSITIONING REFERENCEMODEL RESIDUAL 1.1 PX · STRESS 0.1 · PATCH DISPLAY 2.0
◉ REFERENCE VIEW
NO RESOLVE FRAMES
Estimated overlayIdeal surface (study)Occlusion

Model-only residual: 1.1 px. Compare the dashed target with the estimated insert as you scrub. Four or more points are relevant for perspective in the real filter, but this demonstration models only 2D translation, scale and rotation.

Patch Size changes drawn patch windows only: it never enters the toy solver. In real Resolve, set Enable Zoom/Rotation before tracking, and edit inner/outer boxes in the Viewer. Global Blend is available here only in the Composite stage.

COLOR / RESOLVE FX TRANSFORM

Six native Tracking-state views + a clearly labeled registration teaching proxy

6 original screenshots · 4 panel modes · 4 exercises

01WHAT MATCH MOVE ACTUALLY SEPARATES

Solve quality, motion model and output stage are separate decisions.

The effect stops feeling mysterious when tracking data is debugged before positioning/compositing.

Match Move is a pipeline, not a one-click transform

First obtain a stable motion solve, then verify how it is interpreted for positioning, and only after that commit the composite. `Show Controls For` exists because these jobs are separate. Judging only the final composite often hides the original cause of drift.

An unnecessary degree of freedom can make the solve worse

Enable Zoom and Enable Rotation are useful when the shot genuinely contains scale change and rotation. If the motion is mostly X/Y translation, extra degrees of freedom can make the tracker interpret noise or local deformation as real motion.

Patch cleanup beats blind re-analysis

Activate None/All, Clear past/future, Delete, and Refresh Tracks exist for selective maintenance of tracking patches. When one region fails on glare, occlusion, or blur, isolate and repair the problem rather than repeatedly re-running the entire range without diagnosing the cause.

Show Trackers, Show Center, Show Paths, and Show Active patches are diagnostic tools, not viewer decoration. They reveal which patches participate, how paths behave, and what the patch windows display. Global Blend should be a final integration choice, never a way to hide a poor solve.

02COLOR PAGE · TWO REAL INPUTS

Without a second RGB input, there is nothing to match-move.

Match Move on Color is not a self-contained graphic generator. The foreground arrives as a Timeline Matte/Ext. Matte; the background comes from the current clip’s node tree. The diagram is a learning aid, not a screenshot.

COLOR NODE EDITOR / ROUTINGRGB 1 + RGB 2
Two RGB sources converge on a Match Move FX nodeBackground clip passes through a primary correction to input one. The external foreground clip is exposed via Ext. Matte and connected to input two. Match Move sends the resulting composite to output.BACKGROUNDCurrent Color clipCORRECTIONPrimary balanceFOREGROUNDAdded as MatteEXT. MATTERGB → Input 2MATCHMOVE FX1 + 2OUTRGB 1RGB 2
Background → Input 1Ext. Matte RGB → Input 2

Important: The external clip is not attached to the key/mask connector. The workflow documented in Resolve 21 uses the foreground as Timeline Matte, with its RGB routed into the FX node’s second image input.

CONNECT ONCE, THEN TRACK01 — 04
  1. Expose the source clip

    Edit → Media Pool → right-click foreground → Add as Matte For Color Page Clip.

  2. Prepare a stand-alone FX node

    On Color, add Match Move on the connection from the final correction node to the output.

  3. Route Ext. Matte as RGB

    Add Matte → Timeline Mattes creates the Ext. Matte node. Disconnect its automatic link, then attach its RGB output to the second RGB input on Match Move.

  4. Track → Position → Composite

    Set the tracking model before running analysis, align the Positioning canvas in the Viewer, then choose Composite Type and Output = Composite.

Native evidence: Tracking onlyLater modes: manual verified

Reference manual: Resolve 21 · Chapter 168 · A Match Move Workflow ↗

03SIX NATIVE TRACKING-STATE VIEWS

Read Match Move as a staged tracking interface, not one long list of knobs.

Six original captures show only the Tracking state. Additional Positioning, Compositing and Stabilising controls are documented from Chapter 168; no screenshots have been fabricated.

ROUTING · MODE / OUTPUT

Separate editing tracking data from using the result

Show Controls For

Selects the interface block: Tracking, Positioning, Compositing, or Stabilising. This is stage navigation, not an effect-strength control.

CheckThis changes which control panel is edited; it is distinct from Output. Inspect both dropdowns separately.

Output

Disabled keeps the work in tracking/setup, Positioning Reference provides an intermediate positioning check, and Composite commits the result as the final composite output.

CheckIf Composite drifts, return to Disabled/Positioning Reference and separate solve failure from placement failure.

TRACKING CONTROLS · ANALYSIS / MOTION MODEL

Build the smallest motion model that fits the shot

Tracking transport

The transport buttons start/stop analysis passes in the required direction and let you manage the tracking range.

CheckInspect difficult intervals during analysis, not only the first and last frame.

Prev track end

Moves to the previous tracking-segment boundary so you can quickly locate where a solve starts, ends, or needs maintenance.

CheckUse it with patch cleanup for local diagnosis, not as a substitute for reviewing the path.

Next track end

Moves to the next tracking-segment boundary. Useful when a track contains several repaired or restarted sections.

CheckCheck neighboring frames after jumping; a visually clean boundary can still hide a speed discontinuity.

Enable Zoom

Enables scale change in the tracked motion. Decide BEFORE running analysis; if changed after a solve, retrack.

CheckCheck whether the surface really changes scale from the start to the end, select Zoom, then track.

Enable Rotation

Enables rotation in the tracked motion. Set it BEFORE tracking; turning it on after analysis does not repair the existing solve.

CheckStable rotation needs at least two distinct patches on the same rigid surface.

PATCH GEOMETRY · IN VIEWER

Four parts of a patch and how many points matter

Center point

The tracked feature center that defines the path anchor.

CheckUse Show Center and inspect the anchor throughout the shot.

Inner patch box

The inner rectangle defines the image pattern used for matching. Resize it in the Viewer, not with the Patch Size display slider.

CheckChoose a sharp, contrasty corner; avoid an independently moving shadow or object.

Patch window

A magnified preview of the tracking pattern; adjust its window dimensions with Display Options → Patch Size.

CheckDo not confuse display dimensions with pattern/search geometry.

1 / 2 / 4 / 6+ patches

1 patch tracks XY position, 2+ support rotation, 4+ support perspective and 6+ let the effect select from a larger pool. More trackers do not help when their features belong to different moving surfaces.

CheckFirst choose a coherent rigid surface; then add enough well-separated features.

Option-click tracker

Option-click a tracker control to remove an unwanted tracker rather than temporarily disable its contribution.

CheckBefore deleting, verify that the feature and its tracked history are no longer needed.

MANAGE TRACKING PATCHES · REPAIR THE SOLVE

Maintain patches locally instead of endlessly retracking everything

Activate None

Temporarily deactivates all tracking patches so you can selectively restore what you need or inspect solve state.

CheckDo not confuse inactive with deleted; this manages participation rather than necessarily destroying data.

Activate All

Re-enables participation of all available patches.

CheckAfter Activate All, re-check weak regions; a single bad patch can contaminate the motion model.

Clear past

Clears tracking history before the current frame for the selected patch context.

CheckPlace the playhead on a meaningful repair point or you may erase a valid part of the solve.

Delete

Deletes the selected tracking patch when it consistently follows the wrong feature.

CheckDelete only after checking overlays; a weak patch may still be useful elsewhere in the range.

Clear future

Clears tracking history after the current frame so the continuation can be rebuilt from a known-good point.

CheckEspecially useful after an occlusion: preserve the good past and rebuild the future.

Refresh Tracks

Refreshes the tracking result using the current active-patch set and repairs.

CheckAfter refresh, play the difficult interval; do not trust a single still frame.

DISPLAY OPTIONS · MAKE THE SOLVE VISIBLE

Diagnose paths and active patches directly in the Viewer

Show Trackers

Shows tracker overlays in the Viewer.

CheckEnable while diagnosing drift; hide only after the solve is approved.

Show Center

Shows the tracking/transform reference center.

CheckA sudden center jump is a quick warning of solve trouble or an active-patch change.

Show Paths

Displays the solved motion paths over time.

CheckLook for both positional outliers and unnatural bends in speed/direction.

Show Active patches

Highlights the patches that are actually participating in the current solve.

CheckIf the track drifts, first confirm the active patch belongs to the intended physical surface.

Patch Size

Adjusts the magnified patch preview windows in the Viewer. It is a display setting, not the tracker search-area size or a tracking-quality control. The inner on-screen box defines the pattern and the outer box the search region.

CheckChange Patch Size and observe the enlarged preview window; the track should not re-solve. Resize the on-screen inner rectangle when you need a different pattern region.

POSITIONING · DOCUMENTED / NO CAPTURE

Canvas, corner pin and checking insert geometry

MANUAL VERIFIED · ORIGINAL PANEL SCREENSHOT NOT PROVIDED

Canvas Controls

In Positioning, Canvas Controls select the on-screen canvas interaction. You can move, resize and corner-pin the inserted foreground.

CheckFor a sign replacement align all four corners with the real surface in the reference frame.

Positioning canvas / corner pin

The Viewer canvas positions and corner-pins the external input; scrub after placement to verify the inserted image stays attached.

CheckCompare not just the center but all four corners at start, middle and end.

Reset Corners

Resets the corner-pin canvas to full frame; use it to recover placement, not to fix an incorrect motion solve.

CheckSave the working placement before resetting if you might need to restore it.

Show Comp Result

Toggles preview of the foreground/background composite while checking placement; it does not connect the second FX input for you.

CheckIf the insert is missing, confirm Ext. Matte → second RGB input of the FX node.

COMPOSITING · DOCUMENTED / NO CAPTURE

How the foreground is composited onto the plate

MANUAL VERIFIED · ORIGINAL PANEL SCREENSHOT NOT PROVIDED

Composite Type

In Compositing this determines whether the external foreground overlays the background or only the background plate is output. Do not confuse it with the separate top-level Output menu.

CheckWith Output = Composite but no insert, check Composite Type and the Ext. Matte connection.

Plate Cropping · Left

Crops unwanted material from the left edge of the inserted plate.

CheckStart at zero; adjust only if unwanted source edges remain on the left.

Plate Cropping · Right

Crops the unwanted right edge of the external plate.

CheckReview the right edge during motion, particularly with perspective transform.

Plate Cropping · Top

Crops the top edge of the external plate before compositing.

CheckDo not cut off the intended logo or interface frame.

Plate Cropping · Bottom

Crops the bottom edge of the external plate.

CheckReview motion and seam quality at final frame resolution.

STABILISING · DOCUMENTED / NO CAPTURE

Stabilizing is a separate use of the tracked motion

MANUAL VERIFIED · ORIGINAL PANEL SCREENSHOT NOT PROVIDED

Edge Behavior

Determines what happens to empty borders created when Stabilising compensates for background movement. This is not the insert compositing mode.

CheckSwitch to Stabilising on the same shot; inspect frame edges and cropping throughout the clip.

GLOBAL BLEND · FINAL INTEGRATION

Blend doses the finished result; it does not cure tracking drift

Global Blend

Mixes the processed Match Move result with the node input. Use it only after tracking/positioning/compositing QC.

CheckIf you must reduce Blend heavily because the graphic slides, return to tracking patches and the motion model.

Native captures show exact visible labels in the archived Resolve build. Later panel states can expose different controls; verify those in the Resolve 21/21.1 build you are using.

04A REPEATABLE TRACK / REPAIR / COMPOSITE WORKFLOW

Connect → choose model → track → repair → position → composite → QC.

The external input and Zoom/Rotation are prepared before running analysis; placement is checked separately from the track.

EXTERNAL MATTE → MOTION SOLVE → POSITION → COMPOSITESELECT A STAGE
Seven steps: connect source, choose model, track, repair, place, composite and reviewCONNECTExt. Matte → RGB 2MODELBefore trackingTRACKForward / BackwardREPAIRClear / RefreshPLACEPositioning canvasCOMPOSITEComposite Type / CropREVIEWPlayback / Blend
01 / 07

Wire the foreground correctly

Use Add as Matte For Color Page Clip, expose the asset as Ext. Matte in Color, and feed its RGB into the FX node’s second input. The background remains on the first input.

This is a teaching workflow, not Resolve’s internal graph. Connecting the external matte and choosing the motion model happen BEFORE analysis. The Positioning and Compositing states are documented from the reference manual, not invented screenshot panels.

Related reference: Surface Tracker ↗ · Transform ↗ · Picture In Picture ↗

05FOUR REAL MATCH-MOVE DECISIONS

Overlay registration, push-ins, occlusions and stabilization need different repair strategies.

These are decision procedures, not presets. The correct patch set and motion model depend on what remains rigid and visible in the actual shot.

01

Graphic on a moving object

Transfer surface motion to a label/graphic without visible sliding.

  1. 01

    In Edit → Media Pool choose Add as Matte For Color Page Clip on the foreground asset; in Color add Match Move as its own FX node before Output.

  2. 02

    Use Add Matte → Timeline Mattes to expose an Ext. Matte, then connect its RGB output to the SECOND RGB input of the FX node (not its key input).

  3. 03

    On a good reference frame choose Zoom/Rotation BEFORE analysis, place 4+ patches on one plane, then Track Forward/Backward.

  4. 04

    In Positioning fit the four canvas corners and check motion; in Compositing select Composite Type and, if needed, Plate Cropping; set top-level Output = Composite.

  5. 05

    Check start/middle/end and final Blend; repair drifting tracks in Tracking rather than with opacity.

02

Push-in with visible scale change

Keep an overlay registered during a camera push-in.

  1. 01

    Before analysis evaluate scale change from start to end and ENABLE Zoom if needed.

  2. 02

    Choose 2+ stable features on one rigid plane; for significant planar perspective changes use 4+ patches.

  3. 03

    Retrack after changing Zoom/Rotation; toggling the switch does not retrospectively rebuild stored tracking data.

  4. 04

    Inspect positioning corners and the insert boundaries in playback; Patch Size does not improve the solve.

03

Repair after a short occlusion

Preserve the good past and rebuild only the section after the occlusion.

  1. 01

    Find the last clean frame before occlusion; stop analysis and identify the patches that have failed.

  2. 02

    Enable the affected patches, clear their incorrect future track from the current frame (Clear future), preserving good earlier sections.

  3. 03

    Temporarily disable weak patches, place new patches on another visible part of the same rigid surface and continue Track Forward.

  4. 04

    Re-enable repaired patches when their data is valid, and verify overlay/path continuity throughout the clip.

04

Diagnosis before Stabilising

Avoid feeding a defective solve into stabilization.

  1. 01

    In Tracking, clean patches until trajectories are coherent.

  2. 02

    Check Center/Paths for jumps when active regions change.

  3. 03

    Only after solve QC switch Show Controls For → Stabilising.

  4. 04

    Judge not only jitter removal but also crop/edge behavior and the natural character of the original motion.

06CHOOSE THE RIGHT TRANSFORM TOOL

Match Move fits tracked motion transfer; not every geometry task needs a tracker.

Choose by the geometry problem before choosing by familiarity.

Transform-related Resolve FX
FXWhen it fits
Match MoveUse when you need a tracking-driven transform with tracking, positioning/compositing, or stabilising stages.
PanoMap ↗Use for panoramic-layout conversion/rotation rather than object-motion tracking.
Picture In Picture ↗Use for a static/animated inset-card layout without automatic motion solving.
Surface Tracker ↗Use when a deforming surface/region cannot be described well enough by a simpler patch-driven transform.
Transform ↗Use when the transform is known and can be set manually without tracking analysis.

07READ THE TRACKING FAILURE BEFORE MOVING BLEND

Drift, scale breathing, rotation jitter and occlusion jumps have different causes.

Use overlays and stage isolation before changing the final mix.

01The graphic gradually slides off the object

Likely cause: A weak patch, wrong physical surface, or an unnecessary Zoom/Rotation component.
Fix: Enable Show Paths/Active patches, disable unnecessary degrees of freedom, remove/deactivate the weak patch, and Refresh Tracks.

02After an occlusion the track jumps to a neighboring object

Likely cause: The patch reacquired similar texture after losing the intended target.
Fix: Preserve the good past, Clear future from the repair point, fix the patch context, and rebuild the continuation.

03Scale breathes even though the object barely changes size

Likely cause: Enable Zoom is active without enough geometry, or patches do not move coherently.
Fix: Disable Zoom for a translation-only shot or rebuild patches on one rigid surface.

04Graphic rotation jitters

Likely cause: Enable Rotation is interpreting patch jitter as real rotation.
Fix: Check the spacing/stability of active patches; if rotation is not required, disable it.

05Positioning Reference looks correct but Composite does not

Likely cause: The tracking solve is probably sound; the problem is later in the compositing/placement stage.
Fix: Do not blindly retrack. Compare panel modes and troubleshoot the Compositing controls separately.

06Lowering Global Blend seems to hide the problem, but the overlay becomes weak

Likely cause: Blend is hiding a tracking/compositing error instead of fixing it.
Fix: Restore Blend, expose the drift with overlays, and fix the upstream stage.

07The inserted foreground never appears

Likely cause: The external source is disconnected, Plate Only is selected, Composite is disabled, or no Timeline Matte is available.
Fix: Check Add as Matte For Color Page Clip → Ext. Matte RGB → the FX node’s second RGB input, then Compositing → Composite Type and top-level Output.

08Tracking still slips after changing Enable Rotation/Zoom

Likely cause: The motion model checkboxes were changed after analysis; existing tracked data was not rebuilt.
Fix: Set Zoom/Rotation BEFORE a new analysis pass, clear the invalid sections, and retrack.

09Patch Size changed but the solve did not improve

Likely cause: Patch Size on this panel is a preview-window display setting, not the pattern or search box.
Fix: Resize the inner pattern box and outer search box in the Viewer, place patches on stable details and rerun the track.

08BEFORE DELIVERY

Approve the solve first, then approve registration in motion.

A match move that looks correct on a still can still slide, rotate or breathe during playback.

SELF-CHECK0 / 10

Your marks apply to this visit; nothing is sent to a server.

09FAQ

Practical Match Move questions.

Where should I start with Match Move?

Start with Tracking and Output = Disabled. Build and verify the solve, then check Positioning Reference, and only then switch to Composite.

Should Enable Zoom and Enable Rotation always be on?

No. Enable only motion components that genuinely exist and are supported by stable patches. Extra degrees of freedom can amplify jitter/drift.

Why use Clear past and Clear future?

They let you repair one side of the tracking history from a known-good frame while preserving the valid part of the solve.

Why use Positioning Reference before Composite?

It separates motion/placement verification from the final composite, making it easier to identify which stage is wrong.

Can Global Blend fix a bad track?

No. Blend only mixes the result. Fix drift in Tracking/patch management and placement errors in the appropriate later stage.

Where does the inserted foreground come from on the Color page?

The documented classic workflow uses Add as Matte For Color Page Clip; on the Color page route Ext. Matte RGB into the separate Match Move FX node’s second RGB input. Without that connected source there is nothing to insert.

Why use 1, 2, 4 or 6 tracking patches?

The manual describes one patch for translation, two or more for rotation, four or more for perspective, and six or more to let the filter choose the best data from multiple patches. All patches should track the same surface.

Can Patch Size fix a poor track?

No. It changes the magnified patch display window, not the actual pattern or search regions. The inner and outer boxes are adjusted in the Viewer.

Where are Canvas Controls, Composite Type and Plate Cropping?

Switch Show Controls For to Positioning or Compositing. The archive contains no native screenshots of those states, so the guide documents them from the Resolve 21 manual rather than pretending it has photographed panels.

Why consider Fusion for a more complex match move?

The manual explicitly notes that modern complex match moves are generally more effectively handled on the Fusion page. The Color Match Move FX remains useful for guided study and straightforward inserts, but its source routing differs from Fusion Tracker/Planar Tracker.

Sources and boundaries

Six original captures show the Tracking state and its menus only. Routing the Ext. Matte, tracker-count capabilities, Positioning, Compositing and Stabilising are supported by Resolve 21 Chapter 168; those missing panel screenshots were NOT generated. The interactive preview is synthetic, not the Blackmagic solver or compositor.

Match Move is listed as Studio Version Only in the Resolve 21 reference manual. Verify availability and the exact panel UI in your installed build; the learning model neither estimates real tracking accuracy nor reproduces perspective warp.