Joined: 09 Jul 2009
Location: Atlanta, GA
|Posted: Mon Nov 22, 2010 3:04 pm Post subject: Solve only giving solution for limited # of frames
|Good afternoon all.
Here is my problem:
I have a scene where I set up a number of supervised trackers, 60 in fact.
I removed all the auto generated trackers and wanted to redo them using only the Green channel of my jpg sequence footage.
I set the supervised trackers to zero weight, removed the coordinate constraints from 3 of them and changed their color.
Made sure the camera lens was not keyed at a certain value and no distortion is being applied.
Ran the "Run Auto-Tracker" button. Got a nice number of auto trackers.
Solved with a .8896 hpix value, good for me.
Found that the 3D trackers only existed for certain frames, namely near the end. These frames coincide with the frames SynthEyes chose for it's starting point (the #s listed next to Begin: and End: in the Solve panel).
I've tried manually setting the Begin and End frames earlier but get the error "all the trackers are at the same position, size constraint hasn't been set up".
While reading the forum and checking on the scene again the camera only gets a keyed path up to the End: frame chosen by Syntheyes during the solve. So if SE chose 196-230 as the Begin/End frame the camera is only keyed up to 230 and won't go beyond that.
Any thoughts? I can delete my supervised trackers, clear the 3d solve and run the autotracker/solve 'go' button. I then get a solve with a high hpix error which I fix by setting the Begin: and End: frames manually to frames that show more trackers on screen at once. I assume this is the right thing to do as I get a lower hpix value (going from 4.3 to 1.2).
I'm not sure why the presence of manual trackers with a weight of 0 are leading to the auto trackers not generating a 3D solution except between the Begin: and End: frames.
I'd like to be able to keep the 60 supervised trackers I've created and still get new auto trackers into the scene. Perhaps I'm going about it wrong but I'd also like to know (for curiosity sake) why the solver is only generating 3D points for part of the scene now.