ingiParent3D v1.8

The child is the main object, and will follow the movement of the parent.

What's the point? If you have carefully positioned a card at frame 1023, for example, and want to parent it to an animated axis, you don't want your card jumping in another position when parenting. It can also be a cam or a geo, whether it is the parent or the child.

This node runs live but it will allow you to bake it and also export a baked axis soon. 

Having a live parenting tool can be useful if you are constantly modifying the animation of the parent or child and don't want to rebake everytime. However the fact that it is live is also heavier and less stable, so at the moment this node is overkill for very simple parenting. It is useful for complex animations that are constantly being changed by layout for example, requiring regular updates in large quantities.

What is live? The animation curves in both the parent and child can be changed without re-baking anything, the rest requires baking. 

Keep in mind that nothing will happen at the ref frame, which is the whole point. So, if you move your parent without setting any anim key, the child will not follow it. That's because if there is no animation, it is as if every frame was a ref frame.

It is also possible to invert the movement of the parent, and in effect 'stabilize'. Which can be useful when dealing with complex camera projections.

It searches the values all the way upstream, so keep the parent node disconnected! The parent should have only one node as an input.