reconcile3DPro v1.2
This location is for Registered Users Only.
Perhaps you need to login or register.
13.1, 13.0, 11.3 or later
Linux, Mac, Windows


This small node uses a script to take multiple axis nodes and a camera and converts them to 2D tracks in a tracker node.
It skips the previous technique of having to connect an axis point to a reconcile3D, track and copy the animation data over to a tracker, for every single axis.
Now connect all axis points up to this one node and track them all in one click, then simply export the tracker node with the tracks.
Very useful for getting tracks and cornerpins in complex scenes with camera moves.
Please let me know if you find any issues or bugs and enjoy!
Know Issues
- Having an axis connected to the camera breaks it.
- When creating axis points having anything else selected causes issues.
1.1 Changes - 25 March 2021
You can now select points in the 3D viewer and create connected axis points with the 3D position set to the selected point. Saving time manually creating axis points, snapping them to vertex points and linking them up.
1.2 Changes - 23 June 2022
Thank you for all the feedback!
- Now works with Nuke 13 and Camera 3 (Thanks @Henry Wilkinson)
- Extra Info tab with version and links
- Now pulic on Github and open to comments and pull requests for bug fixes and new features!
- https://github.com/Innders/Nuke-Tools-and-Scripts
- I'm more likely to see comments on Github :)
Comments
I noticed that the tool throws an error message, when the camera has an axis input. Camera evaluation in gizmos is an issue, but maybe you can use DummyCam (http://www.nukepedia.com/gizmos/3d/dummycam) to make this a little bit more robust :)
I also just updated the tool with a pretty cool new feature!
For now I would suggest using AnimatedSnap3D.
http://www.nukepedia.com/python/3d/animatedsnap3d
You can then use that to create your animated axis points and then use Reconcile3DPro to convert those to 2D tracker points.
Is there a Resolution size or Pixel Aspect ratio limitation to the algorithm ? I have some footage that is pixel aspect ratio 2.0 and the reconcile is coming out off.
That's really weird but can't say I have ever tested it with pixel aspect ratio 2.0.
I know that if your window "downres" ISN'T on 1:1 it will come out wrong.
If you find a fix please let me know and comment/pull on Github linked above.
Updated for Nuke 13 here, I also added support for the Camera3 node because it seems to work fine with it and will throw errors otherwise: https://gist.github.com/Shrinks99/796340ab0efc80eb8d791f8a69e73cbd
If you find anymore bugs and want to fix them please comment/pull request on the linked Github repo above!
RSS feed for comments to this post