I was just playing with that today and had all the same thoughts as you. -E
On Tue, Aug 2, 2011 at 6:22 PM, Bill Gilman <[email protected]> wrote: > hear hear > > On Aug 2, 2011, at 10:16 AM, J Bills wrote: > > > just trying it for the first time. having a hard time trying to get it > to do what I want and several things seem counterintuitive. anyone else out > there having success with it? am I missing something? > > > > I've got gobs of roto for this shot I'm on, and all I want to do is warp > a clean plate for a few frames to remove a rig. simple enough - seems like > a textbook case. > > > > should be as easy as: > > -copy roto already done of the area I want into splinewarp node > > -delete source keyframes on roto except for key on clean plate frame > (reference frame) - so if clean plate was painted on frame 45 I'd delete all > keys except for 45 on the source. > > -leave destination keys alone so that the source warps from frame 45 > position to current frame using original roto > > -then I just play with correspondance points, pinning, warp settings and > boundaries until it looks good. > > > > nope, can't seem to get the roto in there and working. > > > > I can copy and paste it in but beyond that the shapes are very hard to > work with. instead of independant source and destination shapes, they > appear to be the same shape! I can't seem to get access to one set of keys > without manipulating the other. If I try to delete out all of the keyframes > on my 'source' shape, it just deletes the destination keys as well. > > > > I thought the whole point of redesigning it was to make it play nice with > the new roto tools and make everything interchangable like it was in shake > (and ER before it), where you could easily shuffle roto in and out. > imperative for good warping, because eventually those same shapes become > your matte to help blend the warped area with the original plate. > > > > as it is, unless I'm missing something (which I hope I am!) it seems like > we're expected to originate all of the roto within the node and are unable > to edit it much after the fact independently between source/destiantion. > I'm not quite sure what that type of workflow is good for, but apparently > it will warp the face of a lion from the manual nicely. will have to > remember that next time that comes up. :-/ > > > > > > _______________________________________________ > > 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
