ImagePlane v1.2
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Frank Rueter
Use a camera to match or stabilise a shot
Requirements:
6.0 or later
Linux, Mac, Windows
6.0 or later
Linux, Mac, Windows


The ImagePlane gizmo can be used like the Tracker node for matching or stabilising, except it will use a match move camera to provide the required animation:

Technically, the imagePlane gizmo turns the incoming image into an image plane of a snapshot of the used camera at the given reference frame.

Technically, the imagePlane gizmo turns the incoming image into an image plane of a snapshot of the used camera at the given reference frame.
import chan file | use to import a chan file for using an internal camera (instead of connecting one). When this is used the imported values will live in the CameraKnobs tab. |
use input | if checked, the connected camera will be used, otherwise the values from the CameraKnobs tab will be used (imported chan file) |
output | chose to match or stabilise the incoming image based on the camera |
refFrame | frame to keep unmodified |
distance | distance of the internal 3D card to the camera. Use to control the amount of parallax applied to the image |
output | parameters to control the output format |
Please login in order to download these files.
Comments
Obsolete_knob import_chan call is wrong, probably a missing NULL for script argument
But it works... and I like it!
Thanks!
D
thanks Frank
I have this set up :
Original plate -> Image Plane1 set to "stabilize", Camera1 as input, ref frame 1 -> Image Plane2 set to "match", Camera1 as input, ref frame 1
Original plate and output of Image Plane2 match at the ref frame, but do not match anymore at frame 100. Am I doing something wrong here ?
Thanks,
Salvador
Salvador
Also, lens distortion can be a factor for mismatch.
One solution would be to generate a corner pin with the ImagePlane node, so I can reverse it.
Thanks anyway, I find you gizmo very useful.
Maybe is it because I've tried on non nodal camera movements, but am I wrong in thinking that shouldn't be a problem ?
Thanks.
set cut_paste_input [stack 0]
version 6.2 v2
push $cut_paste_input
Camera2 {
translate {{curve x1 -252.1427307 x100 -256.1075745} {curve x1 118.1848984 x100 118.5657959} {curve x1 116.8148804 x100 108.8629684}}
rotate {{curve x1 8.585992813 x100 8.783430099} {curve x1 158.0074463 x100 171.6047974} {curve x1 -0.8503982425 x100 1.075308681}}
focal {{curve x1 12.60000038 x100 12.60000038}}
haperture 11.25220013
vaperture 6.324599743
near 0.009999999776
far 600000
file /jobs/pt/users/ rebeccam/bs_077 _0010/published /trackCamera/bs _077_0010_rm_tr ackcamera_right _v001.fbx
fbx_take_name {{1} Default "Take 001"}
fbx_node_name {{7} "Producer Perspective" "Producer Top" "Producer Bottom" "Producer Front" "Producer Back" "Producer Right" "Producer Left" bs_077_0010_pl0 1_v01_right_1_2 }
name Camera2
selected true
xpos -1785
ypos -198
}
set N77b7aa0 [stack 0]
push $N77b7aa0
CheckerBoard2 {
inputs 0
name CheckerBoard2
selected true
xpos -1600
ypos -298
}
ImagePlane {
inputs 2
name ImagePlane6
selected true
xpos -1600
ypos -197
knob ""
output stabilize
format 0
crop false
focal 12.6
haperture 11.2522001
vaperture 6.32459974
label_1 ""
}
ImagePlane {
inputs 2
name ImagePlane7
selected true
xpos -1600
ypos -77
knob ""
format 0
crop false
focal {{parent.parent .ImagePlane6.CA M_ANIM.focal.ri ght i}}
haperture {{parent.parent .ImagePlane6.CA M_ANIM.hapertur e.right i}}
vaperture {{parent.parent .ImagePlane6.CA M_ANIM.vapertur e.right i}}
label_1 ""
}
Thanks
-Nic
Well done! How difficult would it be to add some sort of "Remove Jitter" function?
http://www.nukepedia.com/expressions/smoothing-animation-curves/
Though I would assume it's preferable to dejitter your incoming camera in case you need to use it for other setups as well.
http://www.nukepedia.com/gizmos/creating-a-new-menu-for-custom-gizmos
nuke.addOnUserCreate(lambda:nuke.thisNode()['ref'].setValue(nuke.frame()), nodeClass='Imag ePlane')
RSS feed for comments to this post