+1
From: helmsie nuke-users-re...@thefoundry.co.uk
To: nuke-users@support.thefoundry.co.uk
Sent: Wednesday, October 3, 2012 12:06 PM
Subject: [Nuke-users] new comp stack node survey
Hello all!
I'd like to see the interest in the Nuke community for a comp
N.
Shake had one of those and it was a nightmare to sort compers scripts out.
Howard
On 3 Oct 2012, at 20:10, Bill Gilman billgil...@yahoo.com wrote:
+1
From: helmsie nuke-users-re...@thefoundry.co.uk
To: nuke-users@support.thefoundry.co.uk
Sent: Wednesday, October 3, 2012
Yes this node exist and it's called if I remember well Multilayer.
On Wed, Oct 3, 2012 at 9:36 PM, helmsie
nuke-users-re...@thefoundry.co.ukwrote:
**
Thank you for your input Howard.
To my knowledge Shake didn't have anything like this. I'm happy to be
corrected here.
Helmsie
Bad idea to have a node like this in Nuke.
Creates bad habits.
The whole point of node based compositing is the ease of access. When you
have things happening inside of a node it is very difficult to make
variations. You can't insert a node in the middle. Breaks the magic.
Ron Ganbar
email:
I totally agree with Howard.
It somewhat contradicts a node based environment and in Shake it
certainly seemed to bring on a dark age for me when having to debug
people's scripts.
On 10/4/12 8:21 AM, Howard Jones wrote:
N.
Shake had one of those and it was a nightmare to sort
Have to agree with Howard as well. It undoes so much of the logical clarity
inherent to a node-based compositor.
-Nathan
From: Howard Jones
Sent: Wednesday, October 03, 2012 12:21 PM
To: Bill Gilman ; Nuke user discussion
Subject: Re: [Nuke-users] new comp stack node survey
N.
I would love something like this if it was for time. E.G. like Combustion's
'Edit' Node which let you take in multiple plates and then use a lightweight
NLE for retiming, cutting back and forth and fades.But as a weird layer
based system I pass. I'm not vehemently against something like
I'm indifferent. The main functionality is to give a clear stacking order
of layers, the 'L' key sort-of does this already with multiple Merge nodes.
Re-ordering nodes is easily done with command up/down arrow.
On 4 October 2012 08:06, helmsie nuke-users-re...@thefoundry.co.uk wrote:
**
On 10/4/12 at 10:40 PM, (Frank Rueter) wrote:
It somewhat contradicts a node based environment and in
Shake it certainly seemed to bring on a dark age for me
when having to debug people's scripts.
hell, i even got totally lost when i had to debug my own scripts
whenever i was foolish enough
Can you mock-up how that would look with the new node?
On 4 October 2012 10:13, helmsie nuke-users-re...@thefoundry.co.uk wrote:
**
Thanks Howard. I stand corrected.
Having the ability to quickly walk through and reorder a stack can add
speed and organization to the workflow. I'm
+1 against, I've been to hell and back debugging scripts with
MultiLayer and banned its use back in the day.
The screenshot you posted looks like a poorly planned comp, you're
trying to solve a problem by adding a layer based workflow into a node
based one. Now you have two problems.
./sam
Whoever produced this node graph needs a good telling off.
I've always been of the opinion that, unless you're a one-man-band, the
script is as important as the final pixels you're delivering (if not
more so), and working within a team, a compositor should be responsible
and take care that
wow sack 'em
Howard
From: helmsie nuke-users-re...@thefoundry.co.uk
To: nuke-users@support.thefoundry.co.uk
Sent: Wednesday, 3 October 2012, 22:13
Subject: [Nuke-users] Re: new comp stack node survey
Thanks Howard. I stand corrected.
Having the
Ha!
I always teach people that they have the right to be run over by a bus, and
the rest of the team pick up where they left off without constantly ringing the
hospital!
Howard
From: Frank Rueter fr...@beingfrank.info
To:
wow, sounds like me sermon too, especially the bus part
On 10/4/12 10:54 AM, Howard Jones wrote:
Ha!
I always teach people that they have the right to be run over by a
bus, and the rest of the team pick up where they left off without
constantly ringing the hospital!
Howard
I've only been using Nuke for about 7 years and I didn't know you could do
that! (alt+cmd+up/down arrow on a mac)
Howard
From: Marten Blumen mar...@gmail.com
To: nuke-users@support.thefoundry.co.uk
Sent: Wednesday, 3 October 2012, 22:03
Subject: Re:
Test
Sent from my iPad
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
wouldn't that compete with the multi channel philosophy?
On 10/4/12 10:56 AM, Steve K wrote:
Hey Helmsie,
What about multi-output gizmo functionality like in Katana. I haven't used
katana in a couple years, but I long for the ability to be able to have
multiple outputs in Nuke...
Where one
Hey Helmsie,
What about multi-output gizmo functionality like in Katana. I haven't used
katana in a couple years, but I long for the ability to be able to have
multiple outputs in Nuke...
Where one could build a multi purpose node like you mentionedAND have the
ability to edit the inner
Test ok :)
Luddnel Spider Magne | Director - Lead Motion Compositor
555Lab – Alchemy between you and us
104 rue de la Folie Méricourt 75011 Paris
Office (+33)148 075 055
Mobile (+33)699 434 555 | 555lab.com
-Original Message-
From: Steve K charhar...@gmail.com
Sender:
it'd be also rad to be able to cmd drag a node 'through' the tree to
rearrange the node order, just like using the arrows. might feature request
it!
On 4 October 2012 11:20, Howard Jones mrhowardjo...@yahoo.com wrote:
I've only been using Nuke for about 7 years and I didn't know you could do
A little competition is a good thing :)
How so?
After some thought, I guess it would/could be an issue for a multichannel
workflow...but wouldn't the existing gizmo workflow have the same issues?
Frank, Could you elaborate?
Sent from my iPad
On 2012-10-03, at 6:24 PM, Frank Rueter
well, the current philosophy is that you can stuff as many channels into
one pipe as you like (more or less), and retrieve them via the channel
knobs.
a multi output feature would basically be like a shuffle node, shuffling
the respective layers into rgba. Or am I misunderstanding?
If you
I'd like multi outputs from a gizmo but what you describe with internal
workings seems to be a gizmo rather than a 'black box ' multilayer node, which
deals with the internals in a hidden manner.
Somewhat digressing though from Helmsie's poll though.
Howard
Though reading Frank's reply - multichannels is the Nuke way
Howard
From: Howard Jones mrhowardjo...@yahoo.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk
Sent: Wednesday, 3 October 2012, 23:37
Subject: Re: [Nuke-users] new comp stack node
here's my 1st tip- set /preferences/ Node Graph-Arrows/ Up Arrow to bright
red - it visually warns up 'you're noodling the wrong way'
green for down, and, muted for left and right.
On 4 October 2012 10:36, Frank Rueter fr...@beingfrank.info wrote:
yeah. I'd love to see some sort of educational
I always use red and green like that.
my favorite - label the dots. And have one just before inputs so you can easily
see where each input came from.
Howard
From: Marten Blumen mar...@gmail.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk
. an annoying screeching sound and monitor flickering when nodes are
dragged into nasty positions
On 10/4/12 12:17 PM, Marten Blumen wrote:
to help the fight against 'wrong way' noodling we could use;
. a new node-graph-gravity-feature that literally makes it harder to
move nodes up ;)
Another nice tip Howard.
[quote=mrhowardjones]my favorite - label the dots. And have one just before
inputs so you can easily see where each input came from.
Howard
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk,
Tutorial title? 'The Halcyon days of Laissez Faire Node Graphs are over!'
by your frustrated Comp Supervisor
On 4 October 2012 12:21, Frank Rueter fr...@beingfrank.info wrote:
• an annoying screeching sound and monitor flickering when nodes are
dragged into nasty positions
On 10/4/12
we could also come up with a little electroshock device that can be
hooked up to nuke's python api
On 10/4/12 12:44 PM, Marten Blumen wrote:
Tutorial title? 'The Halcyon days of Laissez Faire Node Graphs are
over!' by your frustrated Comp Supervisor
On 4 October 2012 12:21, Frank Rueter
On 4 okt. 2012, at 00:57, Howard Jones mrhowardjo...@yahoo.com wrote:
I always use red and green like that.
my favorite - label the dots. And have one just before inputs so you can
easily see where each input came from.
Well there certainly is a grain of wisdom to this node suggestion -
Looking at a node layout might give an indication of a compers recreational
usage! ie the spider web test:
http://www.trinity.edu/jdunn/spiderdrugs.htm
On 4 October 2012 13:10, Julik Tarkhanov ju...@hecticelectric.nl wrote:
On 4 okt. 2012, at 00:57, Howard Jones mrhowardjo...@yahoo.com wrote:
Perhaps a new tool in the recruitment process? ;)
http://chrisbenjaminsen.com/games/#untangle
direct:
http://nonoba.com/chris/untangle
On Wed, Oct 3, 2012 at 5:20 PM, Marten Blumen mar...@gmail.com wrote:
Looking at a node layout might give an indication of a compers
recreational usage! ie
Node Layout Technician - (NLT)
On 4 October 2012 13:25, Tony Tsai tony...@gmail.com wrote:
Perhaps a new tool in the recruitment process? ;)
http://chrisbenjaminsen.com/games/#untangle
direct:
http://nonoba.com/chris/untangle
On Wed, Oct 3, 2012 at 5:20 PM, Marten Blumen
what we need is a node graph like the Fusion had 10 years ago. Cells
that nodes fit into and that re-arranges the layout every time you move
a node around.
JUST KIDDING!!
On 10/4/12 1:35 PM, Marten Blumen wrote:
Node Layout Technician - (NLT)
On 4 October 2012 13:25, Tony Tsai
On 10/3/12 at 12:57 AM, (Howard Jones) wrote:
my favorite - label the dots. And have one just before inputs
so you can easily see where each input came from.
i like that one a lot! just added this to my menu.py
nuke.knobDefault('Dot.label', ' [value input0.name]')
might be worth thinking
bugger tcl.
def getParentNode(node):
parentNode = node.input(0)
if parentNode.Class() == 'Dot':
return getParentNode(parentNode)
else:
return parentNode.name()
nuke.knobDefault('Dot.label', [python getParentNode(nuke.toNode('Dot1'))])
On 10/4/12 1:46 PM, chris wrote:
On 10/3/12 at
38 matches
Mail list logo
