Id probably set up some python to iterate through the read nodes. in the
beginning of the function it hooks up the read with the top most node,
and at the end it executes the write.
On 11/21/2011 2:35 PM, michael vorberg wrote:
try something like:
in the before render field of your write2:
nuke.toNode(Switch1)["which"].setValue(2)
this will work if you hit the render on each write seperate, for my
quick test it didnt work if i render all nodes
Am 21.11.2011 14:08, schrieb Thomas Volkmann:
Some interesting stuff so far, but not yet exactly what we are after
(though it definitely is an improvement).
Is there any documentation on that python-tab in the write node? I
didn't find anything on this, but maybe I'm not searching properly,
because I didn't find the former mentioned 'topnode'-expression either.
If we could something like "if write2 -> use switch 2" to work that
would be perfect!
Thanks for your input!
-------- Original-Nachricht --------
Datum: Mon, 21 Nov 2011 12:49:33 +0100
Von: michael vorberg<pingkin...@googlemail.com>
An: Nuke user discussion<nuke-users@support.thefoundry.co.uk>
Betreff: Re: [Nuke-users] Same operation on multiple inputs
two things come into my mind:
a) you can build a temp script with the read node and all the things
you want to do. and the end put in a write node
in the read node file knob write: [argv 0]
and in the write node put an expression to build the name from the
write
node or put in [argv 1]
then start nuke from a commandline with: nuke tempscript.nk
"path/to/read/images.ext" "path/to/write/images.exr" (you can get
rid of
the second argument if you build the write node filenames by
expression)
this will start nuke and put the first argument
("path/to/read/images.ext") into the read nodes file knob
b) the switch method isnt that bad, i would make an expression on the
disable knob of the write node which makes it only active if the right
switchinput is selected.
something like: "switch1.which==3?0:1"
Am 20.11.2011 21:22, schrieb Thomas Volkmann:
Hey,
is it possible to setup some sort of batch-processing in Nuke? E.g.
having multiple Read nodes that need all the same treatment, and then
write them out to different places.
First idea was to put the compositing tree into a group and clone that
one...that was when I found out that you can't clone groups. Another
approach a co-worker came up with, was to connect all the Reads to a
Switch-node and have multiple Write nodes in the end, of which
everyone has a 'before render -> change switch'-expression, but
somehow that didn't work.
Probably I am just missing the obvious... I there a common workflow
for that?
Thanks,
Thomas
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
