solved - the bug is Nuke might add a dodgy keyframe at frame 0 for B-Splines when you copy and paste a roto node. Delete that keyframe at frame 0 after you copy paste and all is good.
On 7 February 2013 11:49, Marten Blumen <[email protected]> wrote: > got some errors; in Roto_BODY BSpline3 corrupts once you use Undo > > > On 7 February 2013 10:07, Marten Blumen <[email protected]> wrote: > >> can you upload the roto_body node after you copy paste it. >> >> maybe there is a bug where a keyframe is set at 0 to 0,0 >> >> >> On 7 February 2013 09:31, Philippe Roberge <[email protected]>wrote: >> >>> Thanks Marten! I didn't noticed that keyframe at 0 and you're right, >>> it's fixed if remove it. >>> >>> But if I work on the "legs" in "Roto_BODY". I still get the misplaced >>> shapes after closing and reopening or by simply copying the node… very >>> weird! >>> >>> On 2013-02-06, at 3:24 PM, Marten Blumen wrote: >>> >>> here the fixed one >>> >>> >>> On 7 February 2013 09:20, Marten Blumen <[email protected]> wrote: >>> >>>> easy fix - somehow you've got dodgy keyframes set around frame 0- load >>>> all the points into the Curve Editor and delete those keyframes. I only >>>> tested it briefly - hope it works >>>> >>>> >>>> On 7 February 2013 09:06, Philippe Roberge <[email protected]>wrote: >>>> >>>>> OK, I saved a script without the plate. Here's the link: >>>>> >>>>> https://dl.dropbox.com/u/73257592/roto_problem.nk >>>>> >>>>> My main problem was with the "Roto_BODY" node. But i just tested >>>>> something and got another problem with the "Roto_HEAD" node. >>>>> >>>>> Just to test… if you load my script, go to frame 91 watch the shape of >>>>> "Roto_HEAD" (it should look like a roundish shape with 2 "ears" at the top >>>>> of it), then copy+paste the "Roto_HEAD" node... do you get a weird shape >>>>> that makes no sense? >>>>> >>>>> >>>>> On 2013-02-06, at 2:45 PM, Marten Blumen wrote: >>>>> >>>>> Can you post the roto node/spline that causes it? there are 2 bugs in >>>>> the release notes that appear related; >>>>> >>>>> • BUG ID 32459 - RotoPaint: Undoing a point move that created a >>>>> keyframe doesn't currently undo the keyframe creation. >>>>> >>>>> • BUG ID 32083 - SplineWarp: Deleting all but one point on a curve >>>>> resets >>>>> its correspondence points to 0,0, which cannot be undone. >>>>> >>>>> >>>>> On 7 February 2013 08:25, Philippe Roberge <[email protected]>wrote: >>>>> >>>>>> LOL Thanks Marty but the versioning is really not the issue here! :) >>>>>> >>>>>> Even if I save hundreds of different versions the problem is still >>>>>> there. Just by copying the roto node I'm getting the keyframes problem >>>>>> I've described earlier. A workaround that seems to be working so far >>>>>> would be to convert the bsplines into bezier curves. >>>>>> >>>>>> On 2013-02-06, at 2:09 PM, Marty Blumen wrote: >>>>>> >>>>>> the classic work around is always version up when saving. Use _v001 >>>>>> in your file name, that uses the in-built versioning system; It's in the >>>>>> file menu as 'save a new version' >>>>>> >>>>>> Sent from iEarth >>>>>> >>>>>> >>>>>> On 7/02/2013, at 3:08, Philippe Roberge <[email protected]> >>>>>> wrote: >>>>>> >>>>>> I spent a whole day rotoscoping a running wolf and I encountered >>>>>> several bugs with the "Roto" node… >>>>>> >>>>>> - Sometimes, after your roto is all done, some points decide to go to >>>>>> the 0,0 position >>>>>> - When you do a "ctrl-z", the "undo" is applied BUT random keyframes >>>>>> are adde throughout the shot. >>>>>> - NOW THE MOST FRUSTRATING… I was all done, everything was working, >>>>>> I saved, sent it to render farm and left. When I came back this morning >>>>>> and >>>>>> loaded the same script, several shapes were out of place and/or had >>>>>> different keyframes!!! Now, I have to completely redo these shapes! >>>>>> >>>>>> Anybody got these *&#?$ bugs and/or have a workaround?! >>>>>> >>>>>> -- >>>>>> Philippe Roberge >>>>>> >>>>>> Senior Compositor >>>>>> Mokko Studio >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>>> >>>> >>>> >>> <fixroto.nk.zip>_______________________________________________ >>> >>> 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
