It just sets the underlying framerange info for that part of the tree, but doesn't change any in/out points you may have in your read nodes. For example, you could have a FrameRange node after a series of merges, or even retimes, and then it wouldn't be obvious what it's actually doing with Read nodes above.
I find it useful mostly to set a framerange at a certain section of the tree so the Viewer will pick that up when the timeline range is set to "Input", or for flipbooks to take the specified framerange by default. >From the node's help, it looks like AppendClip also reads it. On Thu, Sep 1, 2011 at 11:55 AM, 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
