isn't that just a retime set to none for filter?
Howard
set cut_paste_input [stack 0]
version 6.2 v2
push $cut_paste_input
add_layer {rgba rgba.beta}
Text {
font /usr/share/fonts/truetype/Vera.ttf
yjustify center
box {528 218 1584 654}
center {1056 436}
name Text1
selected true
xpos 4566
ypos 5006
}
Retime {
input.first_lock true
input.last_lock true
output.last 300
speed 0.3333333333
filter none
name Retime1
selected true
xpos 4566
ypos 5047
}
>________________________________
>From: Olivier Jezequel <[email protected]>
>To: Nuke Python discussion <[email protected]>
>Sent: Friday, 19 August 2011, 9:56
>Subject: Re: [Nuke-python] freezing frames for certain time then increment
>
>for a second you gave me the horrible feeling i asked a beginner
>question when the answer is just underneath :)
>but the increment, unless i have missed something is jumping to the real
>frame after freezing and so, pass some frames, with is definitely not
>what i want.
>increment 3 : 1 1 1 4 4 4 7 7 7....
>my expression : 1 1 1 2 2 2 3 3 3 4 4 4 ....
>
>my expression is fitting the job, i need that way so all my sequences
>are forsen the time for my switch to pass on each before reviewing the
>next frame
>
>thanks anyway :)
>Olivier
>
>
>Frank Rueter wrote:
>> 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
>>
>
>_______________________________________________
>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
