That's great advice, Nathan.
On Friday, 11 September 2015, Nathan Rusch wrote:
> Update frequency aside, it's worth keeping in mind that the overhead on
> Python expressions is always non-trivial with Nuke's current design; they
> are evaluated via a TCL command, and
Hi Nico,
I reported that declone bug in Jan 2013 (Bug #33635). I got tired of
waiting and just fixed it myself here at my studio. Even sent the code to
The Foundry but I guess it was just ignored or forgotten.
Here's the original gist link I sent to them way back then...
Make sure you've added it to nuke.menu(Nodes) and it will show up. My
guess is you've added it to the menubar; those don't show up in the DAG tab
hotbox. -E
On Thu, Apr 16, 2015 at 6:57 PM, Jordan O jorxs...@gmail.com wrote:
Seems like a silly question, but at what point do plugins get added to
Haven't used it in a while, but check out:
http://tracksperanto.guerilla-di.org/
ā-Eā
On Thu, Aug 28, 2014 at 8:24 PM, Gary Jaeger g...@corestudio.com wrote:
Does anybody have a way of translating nuke corner pins/tracks into after
effects?
Gary Jaeger // Core Studio
249 Princeton Avenue
Unfortunately, companies often do not value experience because it seems
expensive on paper, when all they do is compare the hourly/daily rate for
juniors and seniors; particularly when those companies are managed by
accountant type people that don't understand or want to understand the
- alt+up/down arrow will change version numbers in Read nodes' file paths
- many text-related knobs will accept basic HTML, e.g. in a node's label
knob: bbold text/b iitalics/i
- there's a Nuke IRC chat room on footnetic.com, channel is #nuke
On Sun, Jun 9, 2013 at 8:24 AM, Frank
And since more than one knob will not be changed at a time, I usually use
if/elif/elif/elif structure (since there's no switch in python), ensuring
when the right knob is found, the flow stops. Not sure how much difference
that makes in practice, but, hey, why not.
On Tue, May 7, 2013 at 6:18
...
Are you looking through a particular node?
Happens in a clean/minimal script?
Any evil expressions?
Have you tried rebooting several times and upgraded your mousepad?
On Wed, May 1, 2013 at 8:21 AM, Ean Carr eanc...@gmail.com wrote:
Hey,
Anyone ever get an insta-crash when double clicking
Hey,
Anyone ever get an insta-crash when double clicking an Axis node to get its
properties? This also happened with a Camera2 in the same script, but not
every time. I have a few Axis nodes which cause the crash every time (with
nothing output to the shell).
My current workaround is
Yes, rather unhelpfully, that func doesn't return the node object. Just
change the last line to return nuke.nodePaste... and you should be good to
go. -E
def node_copypaste():
nuke.nodeCopy(cut_paste_file())
nodes = nuke.allNodes();
for i in nodes:
i.knob(selected).setValue(False)
return
Put something like this expression in the message knob of the Text node...
[value BackdropNode1.label]
Is that what you mean?
-Ean
On Sun, Apr 14, 2013 at 5:04 PM, Gary Jaeger g...@corestudio.com wrote:
Can the label of a backdrop node be expression linked to a text node? so
the text
rolling it
back to its original design. I remember giving a few stabs my self at that
time and all I could do was to make it a bit fancier/prettier.
On Wed, Apr 10, 2013 at 9:29 AM, Ean Carr eanc...@gmail.com wrote:
Hey Martin, how would you prefer it then? IMO, the color picker
hasn't
...and if you use a Card3D, make sure to crop it (and 'intersect')
downstream or you're in for some show-stopping bbox issues sooner or later.
On Wed, Apr 10, 2013 at 10:52 AM, Santiago Svirsky
santiag...@moving-picture.com wrote:
Also, if you're rendering planes (and they don't intersect
Hey Martin, how would you prefer it then? IMO, the color picker hasn't
changed much over the years because it functions like the majority of users
want it to, me included. But I'm all ears if you can dream up something
better :) -Ean
On Wed, Apr 10, 2013 at 9:35 AM, Martin Constabe
Connect a Multiply node upstream of your Project3D and animate its 'value'
knob. You should make sure the A side has an alpha if you're doing a
MergeMat 'over', for example, and that the Multiply is set to affect the
right channels (e.g. 'rgba' or 'all').
I do wish MergeMat had a mix knob,
Hey Mark,
If the light node's named 'my_light_node', you would do something like:
nuke.toNode('my_light_node')['name'].setValue(new)
Not in front of Nuke at the moment, but that should work (once you change
focus away from the lightName knob, probably).
Cheers,
Ean
On Sat, Aug 11, 2012 at
...or even better, use the setName method which I believe helps you avoid
naming conflicts:
nuke.toNode('my_light_node').setName(new)
Hope all's well with you, btw!
Ean
On Sat, Aug 11, 2012 at 8:16 AM, Ean Carr eanc...@gmail.com wrote:
Hey Mark,
If the light node's named 'my_light_node
'my_light_node' has been
renamed, the toNode('my_light_node') is no longer valid, and fails if you
try to rename the node a second time.
Mark
Ean Carr wrote:
...or even better, use the setName method which I believe helps you avoid
naming conflicts:
nuke.toNode('my_light_node').setName(new
Hey Ben,
Sounds like it's related to Bug 21461. Multiline_Eval_String knob isn't the
only not serialising correctly; there's MultiView_Knob and some others. The
workarounds have been kind of painful, to be honest.
Cheers,
Ean
On Fri, Nov 25, 2011 at 10:34 AM, Ben Dickson
I like your ideas, Chris. Along those lines, a while ago I made a custom
nuke.Layer function here that disallows adding any channels to built-in
layers. -Ean
On Fri, Nov 25, 2011 at 12:27 PM, chris ze.m...@gmx.net wrote:
hmm, i can see that is kinda hard to solve this issue without crippling
Just subtract the input image from the result...
set cut_paste_input [stack 0]
version 6.3 v5
ColorBars {
inputs 0
name ColorBars1
selected true
xpos 1143
ypos 5446
}
set Nd6e07200 [stack 0]
push $Nd6e07200
Sparkles {
name Sparkles1
selected true
xpos 1029
ypos 5577
}
Merge2 {
inputs 2
Our little virus layer is rgba.beta. Can't seem to get rid of the little
rascal. -Ean
On Sat, Nov 19, 2011 at 11:56 AM, Howard Jones mrhowardjo...@yahoo.comwrote:
I've sent this to support - but it could be a legacy thing, I'm on 6.2v2
here so maybe 6.3 has the cure?
Howard
Well, what a coincidence. I just found a script at our facility with this:
add_layer {rgba rgba.beta redguard1.glow}
Fun times.
-Ean
On Sat, Nov 19, 2011 at 12:12 PM, Ean Carr eanc...@gmail.com wrote:
Our little virus layer is rgba.beta. Can't seem to get rid of the little
rascal. -Ean
I figure this is requested so often that the Foundry should prioritize it.
Pretty please?
On Fri, Oct 21, 2011 at 8:37 AM, Jerry Huxtable je...@thefoundry.co.ukwrote:
Another hacky way to do this is to write an Op which does nothing, and
implement its draw_handles method. In that method you
I've often wanted this, too. There must be a feature request already, I bet.
You should email supp...@thefoundry.co.uk. -Ean
P.S. 'Feather/falloff' are different but also useful and should remain.
On Wed, Sep 28, 2011 at 11:15 AM, Daniel Silwerfeldt dan...@frankvfx.comwrote:
Super thanks
...and for ScannedGrain you could just feed it one grain image instead of a
sequence. -E
On Thu, Sep 15, 2011 at 3:22 PM, to...@elitevfx.com to...@elitevfx.comwrote:
Hey,
If you copy to group, the grain node (Assuming you're using nuke standard),
you have animated values inside there (Noise
There's a hidden node: DeepWrite. Get to it through the Other All Plugins
menu or do this in the script editor:
nuke.createNode('DeepWrite')
Haven't used it yet so not sure if it works. I suspect if it was ready for
primetime, it wouldn't be hidden, though. -E
On Wed, Sep 14, 2011 at 9:57 AM,
Yup, already wrote some python that adds a tab to camera nodes with options
to freeze and choose frame. What I really want are all the time nodes to
accept 3D nodes as valid inputs.
On Fri, Sep 2, 2011 at 9:21 AM, Julik Tarkhanov ju...@hecticelectric.nlwrote:
On 1 sep 2011, at 22:12, Ned
Not exactly... I guess you'd have to loop through dependent nodes and hide
their inputs. First, select the node whose outputs you want hidden, then:
for n in nuke.selectedNode().dependent():
n['hide_input'].setValue(True)
-Ean
On Wed, Aug 10, 2011 at 5:35 PM, mathieu arce
I was just playing with that today and had all the same thoughts as you. -E
On Tue, Aug 2, 2011 at 6:22 PM, Bill Gilman billgil...@yahoo.com wrote:
hear hear
On Aug 2, 2011, at 10:16 AM, J Bills wrote:
just trying it for the first time. having a hard time trying to get it
to do what I
This feature request is s 2008 :D
On Fri, Jul 1, 2011 at 1:30 PM, Ben Dickson ben.dick...@rsp.com.au wrote:
I don't think this is possible, but it would definitely be a good feature
to request to supp...@thefoundry.co.uk
I've been meaning to request (or try and write) a wireframe shader
are listed after
4:3 video formats. Simply cut the 16:9 formats and paste them before the 4:3
ones. Then, Nuke will default to the 16:9 version for both NTSC and PAL.
On 6/23/2011 8:42 AM, Ean Carr wrote:
Hey Donat,
Just edit the built-in PAL format to a different pixel aspect and Read
Hey Donat,
Just edit the built-in PAL format to a different pixel aspect and Read nodes
will match images that match the PAL resolution to that format.
Edit Project Settings...
Change PAL from 1.09 to whatever you want.
-E
On Thu, Jun 23, 2011 at 2:35 PM, Donat Van Bellinghen
Works for me in 6.2v4 64 linux -E
On Thu, Jun 16, 2011 at 12:00 AM, Ned Wilson nedwil...@gmail.com wrote:
Hey Anthony,
I may have spoken too soon earlier. I'm on XP 64 over here and I tested
this a moment ago, it would appear that the eraser does not work either. I'm
running 6.1v3.
You
Hi all,
(Sorry for the cross-post but this old nuke-users thread is probably best
asked in nuke-python...)
Was there ever a method added for setting metadata? Just about to go the
fromScript() way but thought I'd check, first.
Thanks,
-E
On Thu, Sep 23, 2010 at 11:16 PM, Nathan Rusch
Hi,
Just want to add my vote to feature request #1377 please. There are a lot of
new Nuke users coming in and this would help them out.
Thanks,
Ean
attachment: shk_concat.gif___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk,
Hey Pat, looks like you (sort of) already have a latlong map... it just
needs to be 2:1 aspect ratio to map onto the sphere properly. Try
reformatting. -E
set cut_paste_input [stack 0]
version 6.2 v4
push $cut_paste_input
Reformat {
type to box
box_width {{input.width i}}
box_height {{width/2
Done: #18247
On Wed, May 4, 2011 at 2:27 PM, Deke Kincaid dekekinc...@gmail.com wrote:
It never hurts to submit it again as a feature request since votes count.
-deke
On Wed, May 4, 2011 at 04:25, Ean Carr eanc...@gmail.com wrote:
Is Bill's idea an official feature request? I really like
Same here. use input.bbox and see what that does. Works for me in Nuke
6.2v3. As a side note, you use ! instead of a conditional to get the
inverse:
! (xinput.bbox.x || xinput.bbox.r-1 || yinput.bbox.y || yinput.bbox.t-1)
-Ean
On Wed, Apr 20, 2011 at 2:57 PM, Brad Friedman b...@fie.us wrote:
I've tried to link pulldown knobs before in nodes like CheckerBoard using
setExpression() without success.The only way I have ever figured out how to
make this work is through a knobChanged callback. The approach is similar
whether it's a group or gizmo. Here are some examples to try in your
AFAIK, you can't expression link certain types of pulldown knobs in Nuke.
Some work, some don't.
This doesn't work:
checkerboard_linked['format'].setExpression('checkerboard_master.format')
But this does:
nuke.toNode('Blur_linked')['filter'].setExpression('Blur_master.filter')
-E
set
. were fine.
Pre 6.2, a knobChanged callback was the best (only?) way to make a format
knob drive changes to another format knob.
In 6.2, though, you can set an expression link between format knobs, both
through python and manually in the UI.
On Tue, Mar 22, 2011 at 9:42 AM, Ean Carr eanc
fine.
Pre 6.2, a knobChanged callback was the best (only?) way to make a format
knob drive changes to another format knob.
In 6.2, though, you can set an expression link between format knobs, both
through python and manually in the UI.
On Tue, Mar 22, 2011 at 9:42 AM, Ean Carr eanc
by export_chan_file.tcl)
seems to be operating in single-precision float. Easiest way around this
that I can see is to roll your own in Python.
-Nathan
*From:* Ean Carr eanc...@gmail.com
*Sent:* Friday, February 25, 2011 4:20 AM
*To:* Ron Ganbar ron...@gmail.com
*Cc:* Nuke user discussion nuke-users
44 matches
Mail list logo