Randy was spot on - average the tracks and use the average for each corner.
So if you had 16 trackers 4 for each corner you would average each group and
then apply the result of the tracks to the 'cornerpin to'
with an expression linked to a knob to offset the result should it drift
slightly
Hey,
I put the script to create the directory that doesn't exist before a render
in init.py. I found it here :
http://docs.thefoundry.co.uk/nuke/63/pythondevguide/callbacks.html#beforerender
def createWriteDir():
import nuke, os
file = nuke.filename(nuke.thisNode())
dir = os.path.dirname(
You can put a check in to see if the directory already exists:
if not os.path.isdir(dir):
os.makedirs( osdir )
Cheer,
Andy
- Original Message -
From: Julien Chandelle julienchande...@gmail.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk
Sent: Monday, 12
thanks it's works
perhaps the foundry have to add this in the Python dev guide
On Mon, Dec 12, 2011 at 11:48 AM, Andy Walker andy.wal...@framestore.comwrote:
You can put a check in to see if the directory already exists:
if not os.path.isdir(dir):
os.makedirs( osdir )
Cheer,
FWIW, if you have several tracks you want to average onto one cornerpin (or
anything else for that matter), check the T (use to calculate transform)
next to each tracker, then in the Transform tab, set the transform mode to
stabilize and the centre knob will be the average of the 4 trackers,
So it is! - though works on none as well
Howard
From: Colin Alway colin.al...@gmail.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk
Sent: Monday, 12 December 2011, 11:23
Subject: Re: [Nuke-users] Consolidate/use more then one tracker node
I guess they haven't put it in as os is a generic python module rather than
something specific to Nuke. I'm not a great fan of Nuke's python docs
generally, they are very hard to read... Although perhaps I should have read
the dev guide you're using, I must've missed that when I first wrote
The dev guide I use, come from the foundry it should be specific to nuke.
On Mon, Dec 12, 2011 at 1:50 PM, Andy Walker andy.wal...@framestore.comwrote:
I guess they haven't put it in as os is a generic python module rather
than something specific to Nuke. I'm not a great fan of Nuke's python
The Python Developer’s Guide is new documentation release with 6.3vSomething,
and is a monumental leap forward in documenting the Nuke Python API
From: nuke-users-boun...@support.thefoundry.co.uk
[mailto:nuke-users-boun...@support.thefoundry.co.uk] On Behalf Of Andy Walker
Sent: Monday,
Hi Julien,
That sounds like a useful addition, so I've logged it as bug 23681.
Cheers,
Eija
On 12/12/2011 11:04, Julien Chandelle wrote:
thanks it's works
perhaps the foundry have to add this in the Python dev guide
On Mon, Dec 12,
Thanks for the tip, the new docs look much better... Thanks foundry...
Cheers,
Andy
- Original Message -
From: John Vanderbeck john.vanderb...@in-three.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk
Sent: Monday, 12 December, 2011 2:13:30 PM
Subject: RE:
I should have sent this earlier but we are having a Christmas Open House
tonight(Monday) at the office in the Venice, CA office (1 block from DD). We
will have snacks, beer and wine. So if you can make it here through the
rain and want to pop by and pick our brains about anything(nuke, mari,
12 matches
Mail list logo
