Thanks guys - I was adjusting the clip via the dopesheet as an easy workaround, but I was looking for a solution that could provide an obvious visual in the node graph that the clip was being affected. Retime node it is!
On Sep 1, 2011, at 12:24 PM, Diogo Girondi wrote: > Use a Retime node instead if you want to really cut it. The FrameRange is > most useful when you need to change the first_frame and last_frame values for > downstream nodes that will make use of those. > > > Cheers, > Diogo > > On 01/09/2011, at 15:55, Craig Tozzi <[email protected]> wrote: > >> I don't use this node that often, but I'm trying to use it today, and it >> doesn't seem to be doing anything. >> >> I've tried a simple test outside of my comp, with just a read node to a >> Frame Range node to the viewer, and setting values seems to have no visible >> effect - frames are not cut from the beginning or end. I've not had any luck >> applying it to .movs or to image sequences. >> >> Am I missing something really simple or is this not doing what it's supposed >> to? >> >> Running NukeX 6.2v2 on OSX. >> >> Thanks! >> >> >> _ >> Craig Tozzi >> twothousandstrong >> venice, california >> _______________________________________________ >> 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 _ Craig Tozzi twothousandstrong venice, california
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
