It's the mean hypot of the deviation in X and Y that exists between the actual
2D track in screen space and the reprojected 3D feature.
As an aside, if I want my point cloud to be accurate I usually go over to
dedicated 3D tracking packages and forego the Camera Tracker entirelly. You can
move
Add this to you menu.py or init.pynuke.knobDefault("Tracker.label", '[knob transform]')Does anyone know how you would get the tracker node to display the value of the transform knob in the label so it's default?I usually do it by typing [knob transform] in the label section in the node tab. But
Great, works a treat. Thank You.
Darren Coombes - VFX Compositor
Check out some of my work…
www.vimeo.com/53990514
Mob: +61 418 631 079
Skype: darrencoombes
Twitter: @durwood81
On 28/01/2013, at 10:45 PM, Magno Borgo li...@borgo.tv wrote:
Add this to you menu.py or init.py
I like to have the ref frame also:
nuke.knobDefault(Tracker.label, MODE = [value transform]\nREF FRAME
= [value reference_frame])
cheers,
Misho
On 28.01.2013 11:50, Darren Coombes wrote:
Great, works a treat. Thank You.
DARREN COOMBES - VFX COMPOSITOR
Check out some of my work…
I think it's because you are passing a dict of node knob values and they are
applied in an undefined order, so once you change the format or such
the transfer gets overridden (even though you've set it to something
previously). Your best bet would be to set them one by one to make sure that
This is due to an issue with the dpxWriter’s knobs. Specifically, the
'transfer' knob that is returned by the node’s .knob() method or __getitem__
lookup is actually an Obsolete_Knob, so it just eats any value you try to set
on it (logged with The Foundry as bug 28372).
In order to grab the
Thank you Nathan I will try it :)
Miquel Campos
SHED
Character Pipeline TD
2013/1/28 Nathan Rusch nathan_ru...@hotmail.com
This is due to an issue with the dpxWriter’s knobs. Specifically, the
'transfer' knob that is returned by the node’s .knob() method or
__getitem__ lookup is
To clarify some more, the Obsolete_Knob named 'transfer' actually exists on a
base Write node before any FileWriter plugin is loaded, so it ends up masking
the one the dpxWriter creates for the purposes of .knob() and __getitem__
lookups.
However, this oddity is also masking an issue similar
Thanks again for the explanation. Now is fixed :)
2013/1/28 Nathan Rusch nathan_ru...@hotmail.com
To clarify some more, the Obsolete_Knob named 'transfer' actually
exists on a base Write node before any FileWriter plugin is loaded, so it
ends up masking the one the dpxWriter creates for
I don’t think there is currently a way besides manually parsing
node['tracks'].toScript(). I’ve submitted a feature request ticket in case I
missed something obvious, so I’ll let you know what comes out of that.
-Nathan
From: John Mangia
Sent: Saturday, January 26, 2013 12:34 PM
To: Nuke
Ahh thats the one - thanks Julik
I agree on the dedicated front - my money is on 3D Equaliser.
Neil Scholes
+44(0) 7977 456 197
www.uvfilms.co.uk
On 28 Jan 2013, at 09:12, Julik Tarkhanov wrote:
It's the mean hypot of the deviation in X and Y that exists between the
actual 2D track
Hi All,
I am trying to attach a tracker to the destination curve of a spline warper
and can't seem to get it to attach to just the destination. It applies to
both the source and destination which then gives no warping...
Has anyone figured out how to do this...?
Many thanks!
-Oliver
--
US:
Ah yes, great catch Ben. Seems there's still no way to correlate track names
with tracks, or even determine how many tracks exist in the knob, but you
can at least get access to all the data by indexing into the knob.
-Nathan
-Original Message-
From: Ben Dickson
Sent: Monday,
Hi all,
does anybody know if ffmpeg can be used to generate blackmagic codec
quicktimes on Windows?
Thanks,
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
+972 (0)54 255 9765 [Israel]
url: http://ronganbar.wordpress.com/
___
14 matches
Mail list logo
