Yes it's more than a shame the 'e' parameter doesn't work. The other thing that may help in this situation is to bake out Transform nodes for individual tracks and string them together. I try to get out of the Tracker node as soon as possible. For baked Transform nodes, the transform data needs to be zero'd out on the start frame for the track taking over, and retransformed to the correct relative frame. This is a 2d coordinate system transform.
Judicious use of reference frames and baked still frames of the last frame of the previous track, parented above the "takeover" track, can get you there. It helps to have a one frame "track handle" at the start of the next track, to have as the zero frame to be parented under the last good frame of the previous track. Cheers, Michael On 19 April 2017 at 12:39, Ned Wilson <nedwil...@gmail.com> wrote: > Sigh. Thanks for validating Daniel, > > I’ll submit this to The Foundry as a bug. > > -n > > > On Apr 19, 2017, at 9:37 AM, Daniel Hartlehnert <dah...@gmx.de> wrote: > > > > Afaik, the e parameter is completely bugged. > > If you want to create your matchmove, you have to use trackers that are > valid throughout the whole sequence i am afraid. > > > > Cheers, > > Daniel > > > >> Am 19.04.2017 um 02:55 schrieb Ned Wilson <nedwil...@gmail.com>: > >> > >> I have a shot that I’m tracking which is quite complex, and has a whip > pan in it. I’m trying to do a basic 2D track to get the background image > in. I have 14 tracking points, but not all of them are valid throughout the > entire sequence. Much to my chagrin, I found out that when you set the > tracker to matchmove, it is taking an average of every tracker, regardless > of if it has a tracked keyframe or not. I tried going through and manually > animating the “e” parameter, but to no avail. > >> > >> Am I missing something here? Or, I’m on Nuke 9.0v7, has this been fixed > in a later version? > >> > >> Thanks! > >> > >> -n > >> > >> _______________________________________________ > >> Nuke-users mailing list > >> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > > > _______________________________________________ > > Nuke-users mailing list > > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > _______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
