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 <[email protected]> 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 <[email protected]>:
>> 
>> 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
>> [email protected], http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
> 
> _______________________________________________
> Nuke-users mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Reply via email to