What does a working result look like?

A working point-tracker overlay has three visible signs. The track follows the feature during playback, the foreground element moves with it, and the final composition includes that moving element. If only the first sign is present, you have a tracking result but not a completed match move.

Try the test with a plain Text+ element or a simple shape before adding glow, masks, transforms, or other effects. This isolates the tracking path. If the plain graphic follows correctly, the tracker is working and another part of the composite is responsible for the failure.

Do not judge the result only on the frame where you set the tracker. A graphic placed at the right position on one frame can look “attached” while remaining unanimated. Move the playhead. If the graphic does not travel with the tracked feature, inspect the operation or the data connection.

Why is my tracker data visible, but the text stays still?

Visible tracking data does not prove that Text+ is receiving the motion. For a straightforward overlay, feed Text+ into the Tracker node as the foreground; if Text+ is elsewhere in the tree, connect the tracked position to its relevant control.

A common arrangement is:

MediaIn1 (tracked footage) -> Tracker1 background
Text1 (graphic)            -> Tracker1 foreground
Tracker1 output             -> MediaOut1

The exact node names in your project may differ. The important relationship is the job of each connection, not whether it is called Tracker1 or Text1. Blackmagic's Fusion page describes connecting the clip to the tracker, switching the operation to Match Move, and connecting the graphic to the green foreground input. The resulting node output then carries the composite.

If your Text+ node already feeds a Transform node, Merge node, or a larger title branch, the simple arrangement may not describe your setup. Find the point at which the text branch meets the footage branch. Then determine which node should receive the tracked movement. Applying a Tracker operation to one branch does not guarantee that a separate branch will move.

Use this quick test:

• Select the node that contains the text or graphic.
• View that node so you can tell whether the text exists before tracking.
• View the tracking node after it, and scrub the timeline.
• If the text appears in the tracking node but does not move, check its operation or connection.
• If the text moves in that node but disappears later, follow the branch downstream.
• If the text is missing even before the tracking node, the problem is upstream of tracking.

If the overlay moves but is hidden by the footage, the tracking data may be applying correctly. Check the foreground/background order instead. A graphic that is present but behind an opaque background can look like a failed track, even though the motion is working.

For a clean beginner node setup, the site's Fusion page tutorial for beginners can help you identify the flow, viewers, and node connections before you rebuild a more complex composite.

Why does the graphic move in the wrong direction or appear behind the clip?

A graphic that moves but appears behind the footage usually has an input or composite-order problem, not missing tracking data. Check which input receives the footage and which receives the graphic, then verify that the output composites foreground over background.

The word “foreground” is literal here: it means the element intended to appear in front of the background image. If you swap those inputs, or choose a merge order that puts the background over the graphic, the composite may hide the element. The tracking path could be valid and still look broken.

A useful distinction:

Do not change the tracked point's position to solve a layer-order problem. That can make the graphic line up on one frame while leaving it hidden on the others. First verify that the graphic is visible without tracking, then verify its composite order, and only then diagnose the movement.

A good isolation test is to temporarily view the Tracker node's output. If the element is visible and follows the target there, the Tracker is doing its part. If the final output is wrong, keep following the flow downstream. If it is not visible at the Tracker output, inspect the inputs and operation.

How do I connect tracker data to a mask or another node control?

A Tracker node can provide motion data to other node controls, but the control must be linked to the tracked value. A mask sitting in the same composition does not automatically inherit a nearby track.

This is a different workflow from using the Tracker node itself as a match-move compositor. For example, you might want a mask center to follow a point while the original image remains on a separate branch. In that case, the question is not “Which merge mode applies this?” but “Which mask parameter receives the track?”

The exact connection method depends on the node and the parameter. In Fusion, identify the control that represents the position you want to animate, then use the control's connection or modifier workflow to link it to the tracking data. Blackmagic's official Fusion overview confirms that tracking can be used to animate mask shapes, while the Fusion Visual Effects manual describes using tracking data as a source for other parts of a composition. For the exact controls in Resolve 21.1, consult the current manual listed in the Support Center.

When the mask fails to follow, check four things:

1. Is the intended tracker publishing usable data? Scrub the analyzed range and watch the tracking point or path.
2. Is the right parameter connected? A mask's center, shape, and other controls are not interchangeable. Connect motion to the control that should move.
3. Does another node override the value? A downstream transform or an additional animation can change the final position after the tracked value is applied.
4. Does the mask itself have a separate job? If it defines a region on the original footage, moving the whole image and moving the mask are different operations. Decide whether the mask should follow the footage, follow a subject, or remain fixed in frame.

If the connection is unclear, disconnect or bypass other effects temporarily and build the smallest possible test: source image, tracker, mask, output. Once that works, restore the other nodes one at a time. This is more reliable than dragging a mask until it looks close on a single frame.

A mask follows tracking only when its own position or shape control receives the motion data.

How can I tell whether the tracker itself failed or the data is simply unapplied?

A track that slips, jumps, or stops following the target is a tracking-quality problem; a stable path with a stationary graphic is an application problem. Separate those diagnoses before you adjust the node tree.

Scrub the analyzed interval while viewing the tracker. If the tracking point remains on the intended feature, the track may be adequate and the failure is likely in the operation, connection, or output path. If the point drifts away, the resulting data will faithfully describe the wrong motion. Applying it correctly will not make the graphic follow the intended object.

Check these conditions before retracking:

• The feature changes appearance. A point tracker needs a recognizable image pattern. A feature that becomes occluded, blurred, or indistinct may no longer be trackable across the full interval.
• The track crosses an obstruction. If the tracked feature passes behind another object, inspect the section where it disappears. The track may need correction or a different tracking approach.
• The shot contains little texture. A plain surface or repeating pattern gives the tracker less distinctive information than a clear feature.
• The tracking range is too short. If the analysis ends before the graphic's needed duration, the remaining frames cannot show a complete applied move.
• The point is on the wrong feature. A path can look smooth while following a background detail instead of the subject you meant to attach the graphic to.
• The viewer is showing a different node. A visible path belongs to the node loaded in the viewer; it does not establish that the final composite uses that node.

Improve the source decision before adding more nodes. Pick a feature with enough contrast and a distinct shape, and place the tracking pattern so it describes that feature rather than surrounding detail. If the tracker loses the target, analyze from an appropriate frame or correct the track using the controls available to that tracking tool. Then inspect the result again before applying it.

Resolve includes different tracker tools for different motion problems. Blackmagic describes 2D tracking as useful for following moving objects, planar tracking for image planes such as signs and screens, and 3D camera tracking for reconstructing camera motion in 3D space on its Fusion page. Choosing a tool that matches the shot matters as much as pressing the analyze button.

Is a point Tracker, Planar Tracker, or Camera Tracker the right tool?

Use a point Tracker for a distinct feature you want to follow, a Planar Tracker for a flat surface whose perspective changes, and a Camera Tracker when you need to reconstruct camera movement in 3D. Their data is not interchangeable as a single “apply” command.

These are working distinctions, not a complete feature specification. Check the Resolve 21.1 manual for the exact controls available in your version and node. If a tutorial says “apply the track” but shows a different tracking tool from yours, pause and identify the tool before following the steps.

For a flat screen replacement, the point Tracker may follow one corner, but it does not describe all the perspective changes across the screen. The Planar Tracker is designed to follow image planes; Blackmagic describes its ability to create a tracking path containing position, rotation, scaling, and perspective changes. For a 3D object placed into a moving shot, a Camera Tracker addresses a different problem: reconstructing the camera's motion in 3D.

If you are working specifically with Fusion's camera solve and need help distinguishing that task from a 2D overlay, see the site's Fusion camera tracker tutorial. For this issue, though, start with the tool already in your node tree. Rebuilding the shot around another tracker before confirming the current node's operation can add complexity without fixing a simple connection mistake.

Why does tracking work in the viewer but not in the final output?

A tracking node can display the correct result in its viewer while the final output follows another branch of the node tree. Trace the image path from the tracked composite to MediaOut and verify that each required node is connected along that path.

Fusion is a node-based compositor: the node tree shows how image-processing tools connect and affect one another. Blackmagic's Fusion overview describes the node tree as a flow chart in which connected tools form the image-processing chain. That means a correct preview is not enough; the final output must also receive the correct chain.

Walk the wires, not just the labels:

1. View the node you believe contains the finished tracked composite.
2. Identify its image output connection.
3. Follow that connection through any Merge, Transform, mask, or effect nodes.
4. Find the final output node for the composition.
5. Check for a parallel branch that still connects the untracked footage directly to the output.
6. View the final output and scrub again.

A common conceptual mistake is to build a working tracking branch, then keep the original footage connected to the final output. The preview looks correct when the tracking node is selected, but the rendered or displayed output may bypass it. Another is to connect the graphic into a node that is not on the output path. It exists in the flow, but it has no effect on the final image.

Also check whether you are viewing the footage, the Tracker node, a Merge node, or the final output. Each viewer can show a different stage of the composition. If the tracked graphic appears in one and not another, the difference tells you where to look next.

Why does the tracker work on one frame but fail through the shot?

A graphic that lines up on one frame but drifts later usually points to an incomplete or inaccurate track, or to a graphic position that was adjusted manually without applying motion across the full range. Test the start, middle, and end of the analyzed interval before refining the appearance.

Three useful checkpoints:

• Start: Does the graphic begin attached to the intended feature?
• Middle: Does it stay with the feature as the subject or camera moves?
• End: Does it remain attached through the last frame you need?

If the first frame is wrong, check the initial placement and the relationship between the tracked feature and the graphic's anchor point. A label often needs its own designed offset from the point it follows. That offset should keep the label readable without changing which feature the tracker follows.

If the middle or end slips, watch the tracker path itself. A graphic that follows a bad path is not a match-move setup failure. Consider whether the feature becomes hidden, changes shape, crosses a low-contrast area, or leaves the frame. Correct or replace the track as needed, then test again.

If tracking stops before the shot ends, confirm the analyzed range and the clip's timing. The tracker cannot apply motion data for frames that were not analyzed. A short test range can therefore produce a valid result that simply does not cover the full shot.

Do not compensate for drift by repeatedly moving Text+ in the viewer while the playhead sits on one frame. That changes the placement at the current time, not necessarily the underlying track. First establish a track that follows the target, then set the graphic's deliberate offset from it.

Why does my screen replacement track but still look wrong?

A screen replacement can follow a surface's general movement yet still look detached if the setup does not account for the surface's changing perspective. For a planar surface, use a workflow built around planar tracking rather than expecting one point to control all four corners.

A single tracked point can tell you where a feature moves. It cannot, by itself, describe how an entire rectangular screen tilts or changes shape in perspective. A phone display moving in the frame may need position, rotation, scale, and perspective changes to keep a replacement aligned. Blackmagic describes the Planar Tracker as producing motion information for position, rotation, scaling, and perspective, and notes that it can be used to replace screens and signs on its Fusion page.

Check these parts of the screen-replacement setup separately:

• Surface selection: Did you define the area of the plane you want to track, rather than a nearby object?
• Track range: Does the plane remain visible and sufficiently clear through the range?
• Replacement image: Is the new screen or sign connected to the node or transform that uses the planar data?
• Corner alignment: Do the replacement's corners match the plane at the reference frame?
• Occlusion: Does a hand, reflection, or foreground object need to appear over the replacement?
• Output path: Does the final composite include the replacement branch and the original footage?

This matters because “the track applied” and “the replacement looks believable” are different standards. A planar track can carry motion while the replacement remains badly positioned at its reference frame, has the wrong aspect ratio, or lacks the original shot's reflections and occlusions.

For a general moving infographic attached to a feature, a point tracker may be enough. For a rectangular screen, decide whether the shot calls for planar tracking. For an object that should occupy real 3D space as the camera moves, decide whether camera tracking is needed. Pick the simplest tool that represents the movement you need.

What should I check when copying a Fusion tracking tutorial?

When a tutorial's result does not match yours, compare its tracking tool, node connections, operation, and Resolve version before repeating its clicks. A tutorial for a point Tracker does not automatically map to a Planar Tracker or Camera Tracker.

Use this comparison checklist:

A tutorial can be perfectly correct and still appear wrong if you follow its steps on a different node or try to use its result for a different goal. The node graph is the source of truth. Identify the role of each node and follow the wires.

Blackmagic's Support Center is the first place to check for the current Resolve 21.1 manual and release-specific documentation. The official Fusion overview also provides a concise account of the standard graphic-overlay sequence: track the clip, choose Match Move, connect the graphic to the foreground input, and inspect the composite. Use that as a baseline, then adapt only when your task requires a different tracker or a separate parameter connection.

When should I retrack instead of changing the node setup?

Retrack when the tracker itself stops following the intended feature; change the node setup when the track is good but the element does not use it. This decision prevents you from trying to repair a connection problem by making the tracker analyze the same footage again.

Use the decision table:

The words matter. If the track is wrong, say “the tracker is not following the feature.” If the track is right but the graphic stays still, say “the track is not connected to the graphic.” Those are different failures, and they need different fixes.

Retrack only when the tracking path is wrong; a correct path needs an application or connection fix.

What does a real-world tracking diagnosis look like?

A worked example can clarify the difference between a tracking failure and an application failure without claiming to report a tested result. Suppose you have a moving shot and want a small title to follow a subject's jacket.

First, identify the intended target. Choose a distinctive feature on the jacket that remains visible during the shot, rather than a nearby background detail. Analyze the range you need and scrub through it. If the tracker follows the jacket, the path is usable for the next diagnosis. If it wanders onto the background, improve the track before working on the title.

Next, set up a simple composite: footage as the background, title as the foreground, and the Tracker node configured to use Match Move. Check the node output. If the title now moves with the jacket, the original issue was that the track was not being used by the Tracker operation or the graphic was not connected to it.

If the title moves but disappears, check the foreground/background relationship and output branch. If it follows the jacket only until the jacket passes behind an arm, the issue is likely the track's continuity at that obstruction. If the title follows correctly but sits directly on the tracked point and covers the subject, change its designed offset from the point; do not place the tracker on a different feature just to move the title away.

Now change the task. Say you want to replace a phone screen. A point on the phone may follow the camera movement, but the four corners of the display can still drift because the surface changes perspective. That is a sign to evaluate a planar tracking workflow, not proof that the point tracker failed to analyze motion.

These examples are diagnostic illustrations, not claims of hands-on testing. The useful habit is to isolate one variable: quality of track, method of applying it, composite visibility, or choice of tracker. Then change the part that matches the observed failure.

What if the track is good but the final composite still looks wrong?

A valid track can still produce a poor-looking shot when the graphic's anchor, scale, perspective, or visibility does not suit the scene. Separate motion matching from visual integration.

Once the graphic follows the target, inspect the composition for:

• Anchor point: Does the text or graphic attach by the point you intended, or is its center being aligned in a way that looks offset?
• Scale: Does it stay at a plausible size as the subject or camera changes distance?
• Rotation: Should the element rotate with the target, or remain upright for readability?
• Perspective: Is the target a flat plane that changes shape in perspective?
• Occlusion: Should foreground objects cover the graphic at some moments?
• Lighting and contrast: Does the inserted element need adjustments to remain legible without looking pasted on?
• Frame edges: Does the element leave the visible frame, or get cropped by a mask or transform?
• Motion range: Does the match continue for every frame in the intended shot?

These checks occur after the track applies. They should not be confused with whether data is reaching the node. If the graphic moves with the target but looks wrong, the next fix may be design or compositing rather than tracking.

For an on-screen explanation while you inspect which control is connected to which node, TryUncle is available for DaVinci Resolve on Mac and Windows; it can guide you through the visible interface while you remain in control of the changes.

A successful track is not the same as a finished composite; motion, visibility, and integration are separate checks.

Which checks should I run before rebuilding the composition?

Before rebuilding a Fusion composition, confirm the tracker type, data quality, operation, input roles, parameter connections, and final output. A short checklist can isolate the fault without deleting a working node tree.

Use this sequence:

• I know which tracking tool the setup uses.
• I scrubbed the analyzed range and confirmed that the track follows the intended feature or plane.
• I chose an operation that uses the data for my goal.
• I connected the footage and graphic to the intended roles.
• I connected masks or other controls to the tracked data when they need independent motion.
• I checked whether the graphic is hidden by merge order, alpha, or a mask.
• I followed the output path through the final node.
• I checked the start, middle, and end of the range.
• I changed one diagnosed issue at a time.
• I checked the current Resolve 21.1 manual if the tutorial's control labels differ.

If these checks do not isolate the problem, save a copy of the project before making broad changes. Then simplify the node graph in a duplicate composition or on a test clip. Keep the source track and the failing composite separate so you can compare them without losing work.

The core repair is usually straightforward: confirm the data, tell Fusion what should use it, and make sure that result reaches the output. If the motion itself is wrong, improve the track or choose a better-suited tracker. If it is right, stop retracking and follow the connections.

What is the next step if Fusion tracker data still will not apply?

If the tracker follows the target but the element stays still, inspect the operation and data connection first. If the track slips, fix the track; if the graphic is hidden, inspect compositing order and the output path.

Keep that diagnosis narrow. A point Tracker match move, a Planar Tracker screen replacement, and a mask linked to tracked data are different setups, even though all of them involve tracking. Identify the tool, state what should move, and follow the node connections until you find the first place where the expected result disappears.

“There were several shots where we removed distractions in the background, and the Fusion paint, tracking and roto tools were excellent for this,” said colorist, VFX artist, and producer Joe Pavlo. He described creating a clean plate, tracking it, and using polygons or Magic Mask for elements in front. The quote is from a published account of the documentary workflow.

Use the immediate check that matches your symptom: set Match Move for a simple point-tracker overlay, connect a mask or other control to the data it needs, or choose planar tracking when one point cannot describe the surface. Then scrub the range and confirm the result at the final output.