Finding Spikes Before Solving

< Previous | Contents | Manuals Home | Boris FX | Next >

‌Finding Spikes Before Solving

Learn to recognize these velocity spikes directly. There are double spikes when a tracker jumps off course and returns, single spikes when it jumps off course to a similar feature and stays there, large sawtooth areas where it is chattering between near- identical features (or needs a new position key for reference), or big takeoff ramps where it gets lost and heads off into featureless territory.

To help find these issues, the graph editor features the Isolate mode . Left- click it to turn it on, then right-click it to select all the trackers (it does not have to be on for right-clicking to work).

With all the trackers selected, you will usually see a common pattern for most of the trackers, plus a few spots where things stick out. If you click the mouse over the spikes that stick out, that tracker will be selected for further investigation. You can push the left button and keep it down and move around investigating different curves, before releasing it to select a particular one. It can be quicker to delete extra automatic trackers, rather than repairing them.

After repairing each tracker, you can right-click the isolate button again, and look for more. With two monitors, you can put the graph editor on one, and the camera view on another. With only one monitor, it may be easiest to operate the graph editor from the Camera & Graphs viewport configuration. Once you are done, do a refine-mode solving cycle.

Hint: You can stay in Deglitch mode , and temporarily isolate by holding down the control key. This gives a quick workflow for finding and repairing glitches.

< Previous | Contents | Manuals Home | Boris FX | Next >