User Manual

Table Of Contents
To solve a camera’s motion:
1 Click the Solve button to run the solver.
2 Filter out and delete poor tracks.
3 Rerun the solver.
The Solver tab after it has run and produced an average
solve error of 0.4367 pixels.
How Do You Know When to Stop?
At the end of the solve process, an Average Solve Error (sometimes called a reprojection error)
appears at the top of the Inspector. This is the crucial value that tells you how well the
calculation has gone. A good Average Solve Error for HD content is below 1.0.
You can interpret a value of 1.0 as a pixel offset; at any given time, the track could be offset by 1
pixel. The higher the resolution, the lower the solve error should be. If you are working with 4K
material, your goal should be to achieve a solve error below 0.5.
Tips for Solving Camera Motion
When solving camera movement, it’s important to provide accurate live-action camera
information, such as focal length and film gate size, which can significantly improve the
accuracy of the camera solve. For example, if the provided focal length is too far away
from the correct physical value, the solver can fail to converge, resulting in a
useless solution.
Additionally, for the solver to accurately triangulate and reconstruct the camera and
point cloud, it is important to have:
A good balance of tracks across objects at different depths, with not too many tracks
in the distant background or sky (these do not provide any additional perspective
information to the solver).
Tracks distributed evenly over the image and not highly clustered on a few objects or one
side of the image.
The track starts and ends staggered over time, with not too many tracks ending on the
same frame.
1597Chapter – 77 3D Camera Tracking