Try the increment knob in the FrameHold node (I.e. Set it to 3)
On Aug 18, 2011, at 7:48 AM, Olivier Jezequel <[email protected]> wrote: > well, i managed to sort it : > (frame-parent.startseq)/parent.Inputsnum+parent.startseq > > lucky for me the frame hold parameter remove the decimal to keep only the > integer, so 2.999 is still 2 which is perfect for me on that case. > > > Olivier Jezequel wrote: >> Hiya, >> >> I have a gizmo i made to stitch together some sequences to compare each >> frame together >> for expl 1 wireframe seq, 1 render sequ and 1 ref photo seq (can be more...) >> >> all was working with a retime node that would slowdown the anim of each seq >> to have (on this case with 3 inputs) all the seq frozen for 3 frames, then >> increment and freeze again... >> the problem is coming from the retime node that has a bug referenced #20545, >> so it sometime don't refresh and do its job. and the other retime method are >> not giving the same result. >> So I am trying to find a way to do that otherwise using expressions in a >> framehold, but i can't figure out the expression. >> >> so it should do : freeze for n frames, go to next frame freeze again for n >> frames.... on that case the starting frame of the sequence has to be know i >> think or it will create trouble.. >> >> any ideas ? >> cheers >> Olivier >> >> _______________________________________________ >> Nuke-python mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > _______________________________________________ > Nuke-python mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python _______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
