< Previous | Contents | Manuals Home | Boris FX | Next >
If you are solving a lengthier shot where trackers come and go, and where there may be some tracking issues, you can monitor the quality of the solving from the messages displayed.
As it solves, SynthEyes is continually adjusting its tentative solution to become better and better (“iterating”). As it iterates, SynthEyes displays the field of view and total error on the main (longest) shot. You can monitor this information to determine if success is likely, or if you should stop the iterations and look for problems.
If the scene starts to solve with a very large error, especially for 360VR shots, you may need to adjust the Begin/End frames, see Special 360VR Solving Considerations.
SynthEyes will also display the range of frames it is adding to the solution as it goes along. This is invaluable when you are working on longer shots: if you see the error suddenly increase when a range of frames is added, you can stop the solve and check the tracking in that range of frames, then resume.
Note : More specifically, you can check the most-recently-added trackers, which are selected when the solve stops before completing. The camera view's right-click/View/Only selected trackers option, tracker radar, your ability
to group the trackers by assigning colors, and the timing bar's right-click menu can all be helpful. (Selecting trackers after solving is subject to a preference, on by default.)
You can monitor the field of view to see if it is comparable to what you think it should be — either an eyeballed guess, or if you have some data from an on-set supervisor. If it does not seem good to start, you can turn on Slow but sure and try again.
Also, you can watch for a common situation where the field of view starts to decrease more and more until it gets down to one or two degrees. This can happen if there are some very distant trackers which should be labeled Far or if there are trackers on moving features, such as a highlight, actor, or automobile.
If the error suddenly increases, this usually indicates that the solver has just begun solving a new range of frames that is problematic.
Your processor utilization is another source of information. When the tracking data is ambiguous, usually only on long shots, you will see the message “Warning: not a crisp solution, using safer algorithm” appear in the solving window. When this happens, the processor utilization on multi-core machines will drop, because the secondary algorithm is necessarily single-threaded. If you haven’t already, you should check for trackers that should be “far” or for moving trackers.
©2024 Boris FX, Inc. — UNOFFICIAL — Converted from original PDF.