reconcile3DPro v1.3


 
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Innders
Convert multiple 3D points to 2D tracker points really fast!
Requirements:
13.1, 13.0, 11.3 or later
Linux, Mac, Windows
25 Aug 2022
785

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!

reconcile3DPro Example

Know Issues

  • Having an axis connected to the camera breaks it.
  • When creating axis points having anything else selected causes issues.

Change Log

1.3 Changes - 25 August 2022

  • Fixed a bug where only the scripts settings format was used (Thanks @Alesja Surubkina)
  • Make sure to plug in Img input to ensure you calculate to the correct format! This also better aligns with the original Reconcile3D node.

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 :) 

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.

Reconcile3DPro Demo v2

 

Please login in order to download these files.

Comments   

 
+1 # Nikolai Wüstemann 2021-03-25 08:05
This is handy and save a lot of time, thanks!
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 :)
 
 
-1 # Luke Inderwick 2021-03-25 16:29
Thanks for trying it out Nikoloai and bringing this error to my attention. It's because the camera input will be looking for the top node, which will usually be the camera, unless an axis is connected. So it thinks the axis is the plugged in camera and causes the error. I will take a look at a fix.

I also just updated the tool with a pretty cool new feature! :D
 
 
0 # Josh Barham 2021-09-27 14:11
Would it be possible to have an option to create animated axis? Currently it only snaps to a static 3D point and would be useful to have that functionality built in to this. Great tool though. Cheers
 
 
0 # Luke Inderwick 2021-10-15 07:50
Hi Josh, thanks for the feedback, I will take a look into implementing this 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.
 
 
-1 # M Frank 2022-03-19 02:37
Hey Luke -- this is pretty sweet! I was thinking of making something similar.

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.
 
 
0 # Luke Inderwick 2022-06-23 08:13
Hi M Frank!

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.
 
 
+2 # Henry Wilkinson 2022-05-11 20:33
Thanks for writing this script!

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
 
 
+3 # Luke Inderwick 2022-06-23 08:15
Thanks Henry, I have updated the script with your changes.

If you find anymore bugs and want to fix them please comment/pull request on the linked Github repo above!
 
 
0 # Thomas Vu 2024-09-05 06:49
thanks for the fix bro, it work for me nuke 13
 
 
0 # Alesja Surubkina 2022-08-25 10:14
Great tool, noticed one issue though. It does not seem to recognise the resolution of plate plugged in and takes data from project settings.

Cause I'm trying to use it on undistorted plate that is then Reformated to 1.2 scale, but it keeps insisting that my footage is in default resolution.

The only solution I found is to change project resolution while tracking and then change it back. Tad clunky. Would be good to have control somewhere inside the node.

Otherwise very speedy, thanks.
 
 
+2 # Luke Inderwick 2022-08-25 19:50
Thanks for discovering this bug. I have now fixed it, make sure you plug your plate into the Img input. This now works the same as the original Reconcile3D does.
 
 
0 # Markus Eiken 2022-11-21 10:12
Love the tool! Doesn't seem to be working in nuke13.2?
I'm getting a lot of SyntaxErrors. "missing parentheses". When adding parentheses to the lines nuke is complaining about I still cant make it work.
This is when I try to use the "Track Axis Points" button. Any help would be appreciated, thanks!
 
 
0 # Luke Inderwick 2022-11-21 10:18
Hi Markus,

Thanks for letting me know, I will look into this and try and get a fix ASAP.

If you find a fix in the meantime then either post on here or maike a comment on then github here: https://github.com/Innders/Nuke-Tools-and-Scripts/issues/3
 
 
0 # Daniel Müri 2023-01-26 14:37
Oh that would be a nice tool, but i can't get it to work because of the "missing parentheses". Hope you can fix it.
 
 
0 # Luke Inderwick 2023-01-26 17:00
I've just spent the last hour trying it but unfortunately I don't own Nuke13.2 and therefore it's very hard to actually export my changes.

The bugs are:
All prints need () around the text.
Anywhere you see a check for === "Axis" add another check for "Axis3"
Anywhere you see a check for === "Camera" add another check for === "Camera3"

If you do fix it please make a PR/comment on the github repo.
 

You have no rights to post comments

We have 6264 guests and 124 members online