blender-manual/manual/movie_clip/tracking/clip/toolbar/solve.rst

4.0 KiB
Raw Permalink Blame History

Sphinx Warnings

9: WARNING: undefined label: 'bpy.ops.clip.create_plane_track'
73: WARNING: undefined label: 'bpy.ops.clip.solve_camera'
99: WARNING: undefined label: 'bpy.ops.clip.clean_tracks'
101: WARNING: undefined label: 'bpy.ops.clip.filter_tracks'
108: WARNING: undefined label: 'bpy.ops.clip.bundles_to_mesh'
110: WARNING: undefined label: 'bpy.ops.clip.track_to_empty'
119: WARNING: undefined label: 'bpy.ops.clip.set_origin'
121: WARNING: undefined label: 'bpy.ops.clip.set_plane'
123: WARNING: undefined label: 'bpy.ops.clip.set_plane'
125: WARNING: undefined label: 'bpy.ops.clip.set_axis'
127: WARNING: undefined label: 'bpy.ops.clip.set_scale'
129: WARNING: undefined label: 'bpy.ops.clip.apply_solution_scale'
139: WARNING: undefined label: 'bpy.ops.clip.set_viewport_background'
141: WARNING: undefined label: 'bpy.ops.clip.setup_tracking_scene'

Note the preview is not accurate and warnings may not indicate real issues.

Solve

Plane Track

See bpy.ops.clip.create_plane_track.

Solve

Tripod

Tripod Motion can be used for footage where the camera does not move and only rotates. Such footage cant be tracked with a generic solver approach, and it is impossible to determine the actual feature points in space due to a lack of information. So this solver will solve only the relative camera rotation and then reproject the feature points into a sphere, with the same distance between feature and camera for all feature points.

Note

This is special type of camera solver and it behaves different from regular solver. It means using more tracks doesnt imply more accurate solution. Having 5-10 tracks on frame is likely what shall be commonly used for this kind of solver.

Keyframe

Automatically select keyframes for initial reconstruction. This option enables complex algorithms which tries to find a keyframe pair with minimal reconstruction error and best scene scale guess.

Keyframe A/B

Start (A) and End (B) frame of the range used for reconstruction.

Refine

Specifies which parameters should be refined during solve. Such refining is useful when you are not sure about some camera intrinsics, and solver should try to find the best parameter for those intrinsics. But you still have to know approximate initial values it will fail to find correct values if they were set completely incorrectly initially.

Focal Length

Refine the cameras Focal Length.

Optical Center

Refine the cameras Optical Center.

Radial Distortion

Refine the cameras Radial Distortion Parameters.

Tangential Distortion

Refine the cameras Tangential Distortion Parameters.

Solve Camera/Object Motion

See bpy.ops.clip.solve_camera.

Cleanup

This panel contains operators and their settings which are needed to clean up bad tracks: tracks which are not tracked long enough or which failed to reconstruct accurately.

Frames

Tracks or tracked segments shorter than this number of frames will be removed.

Error

Tracks which has reprojection error higher than this value will be removed.

Type

Several actions can be performed for bad tracks:

Select

They can simply be selected.

Delete Track

The whole track can be deleted.

Delete Segments

Bad segments of tracked sequence can be removed.

Clean Tracks

See bpy.ops.clip.clean_tracks.

Filter Tracks

See bpy.ops.clip.filter_tracks.

Geometry

3D Markers to Mesh

See bpy.ops.clip.bundles_to_mesh.

Link Empty to Track

See bpy.ops.clip.track_to_empty.

Orientation

Scene orientation tools can be used for orienting object to bundles.

Floor

See bpy.ops.clip.set_origin.

Wall

See bpy.ops.clip.set_plane.

Set Origin

See bpy.ops.clip.set_plane.

Set X, Y Axis

See bpy.ops.clip.set_axis.

Set Scale

See bpy.ops.clip.set_scale.

Apply Scale

See bpy.ops.clip.apply_solution_scale.

Distance

Distance in active scene units which is used by Set/Apply scale.

Scene Setup

Set as Background

See bpy.ops.clip.set_viewport_background.

Setup Tracking Scene

See bpy.ops.clip.setup_tracking_scene.