hi

i've found that Oflow doesn't modify the [metadata input/frame] the way
that re-time does.  this is making burn ins in nuke studio pretty bad for
our current project because alot of the footage is being re-timed.

Nuke studio only uses an Oflow node so there is no fix for this right now,
in that workflow.

example : make a retime node on footage, set speed to .5 and filter to
nearest. notice the [input/frame] is correct
make an Oflow node and set the method to frame, the timing to frame and
stretch your keys out so its 2x as long. Notice the [input/frame] is not
correct.

doug
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Reply via email to