I'd have to dig into it myself to see find out, but I don't see a reason
why the tracker node would do this when you extract a track. Mayb a bug?
Assuming that the resulting animation/value is correct, just keep it as
is or add the respective value on each frame (if you are creating a new
animation curve)
On 05/03/14 12:29, Julik Tarkhanov wrote:
Good guess, also seen that by now ;-) this comes from a Tracker node
that I'm extracting a "track" knob value from. Don't know whether it's
been introduced
by deliberate curve manipulation or the Tracker node itself though.
On 05 Mar 2014, at 00:26, Frank Rueter <[email protected]
<mailto:[email protected]>> wrote:
where does this come from? Looks like a user expression to add the
value 5 to the animation curves value per frame (you shoudl see this
as a vertical offset in the curve editor).
--
Julik Tarkhanov | HecticElectric | Keizersgracht 736 1017 EX
Amsterdam | The Netherlands | tel. +31 20 330 8250
cel. +31 61 145 06 36 | http://hecticelectric.nl
_______________________________________________
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
