Re: [Nuke-users] Same operation on multiple inputs
Thanks Holger, exactly what we've been looking for... Original-Nachricht Datum: Mon, 21 Nov 2011 20:22:31 +0100 Von: Holger Hummel|Celluloid VFX hol...@celluloid-vfx.com An: Nuke user discussion nuke-users@support.thefoundry.co.uk Betreff: Re: [Nuke-users] Same operation on multiple inputs i stumbled upon this a few days ago: http://www.creatogether.com/foreach-nk haven't tested it myself yet but looks like it's doing at least some of the stuff you're looking for. cheers, Holger Thomas Volkmann wrote: 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 -- Holger Hummel - hol...@celluloid-vfx.com Celluloid Visual Effects, Paul-Lincke-Ufer 39/40, 10999 Berlin phone +49 (0)30 / 54 735 220 - m...@celluloid-vfx.com ___ 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 -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone ___ 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
Re: [Nuke-users] Same operation on multiple inputs
I saw that but couldn't see the difference between copy cloning some nodes and using a multipaste tool (mines from Diogo). Seemed a long way around to do the same thing. I'll let Diogo share this code if he wants. Howard From: Thomas Volkmann t.volkm...@gmx.net To: Nuke user discussion nuke-users@support.thefoundry.co.uk Sent: Tuesday, 22 November 2011, 8:40 Subject: Re: [Nuke-users] Same operation on multiple inputs Thanks Holger, exactly what we've been looking for... Original-Nachricht Datum: Mon, 21 Nov 2011 20:22:31 +0100 Von: Holger Hummel|Celluloid VFX hol...@celluloid-vfx.com An: Nuke user discussion nuke-users@support.thefoundry.co.uk Betreff: Re: [Nuke-users] Same operation on multiple inputs i stumbled upon this a few days ago: http://www.creatogether.com/foreach-nk haven't tested it myself yet but looks like it's doing at least some of the stuff you're looking for. cheers, Holger Thomas Volkmann wrote: 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 -- Holger Hummel - hol...@celluloid-vfx.com Celluloid Visual Effects, Paul-Lincke-Ufer 39/40, 10999 Berlin phone +49 (0)30 / 54 735 220 - m...@celluloid-vfx.com ___ 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 -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone ___ 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
Re: [Nuke-users] Same operation on multiple inputs
Hi Howard,
I don't know which code you're talking about but feel free to share as you
please :)
cheers,
diogo
On Tue, Nov 22, 2011 at 8:01 AM, Howard Jones mrhowardjo...@yahoo.comwrote:
I saw that but couldn't see the difference between copy cloning some nodes
and using a multipaste tool (mines from Diogo).
Seemed a long way around to do the same thing.
I'll let Diogo share this code if he wants.
Howard
--
*From:* Thomas Volkmann t.volkm...@gmx.net
*To:* Nuke user discussion nuke-users@support.thefoundry.co.uk
*Sent:* Tuesday, 22 November 2011, 8:40
*Subject:* Re: [Nuke-users] Same operation on multiple inputs
Thanks Holger,
exactly what we've been looking for...
Original-Nachricht
Datum: Mon, 21 Nov 2011 20:22:31 +0100
Von: Holger Hummel|Celluloid VFX hol...@celluloid-vfx.com
An: Nuke user discussion nuke-users@support.thefoundry.co.uk
Betreff: Re: [Nuke-users] Same operation on multiple inputs
i stumbled upon this a few days ago:
http://www.creatogether.com/foreach-nk
haven't tested it myself yet but looks like it's doing at least some of
the stuff you're looking for.
cheers,
Holger
Thomas Volkmann wrote:
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
--
Holger Hummel - hol...@celluloid-vfx.com
Celluloid Visual Effects, Paul-Lincke-Ufer 39/40, 10999 Berlin
phone +49 (0)30 / 54 735 220 - m...@celluloid-vfx.com
___
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
--
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone
___
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
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
Re: [Nuke-users] Same operation on multiple inputs
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 -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone ___ 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
Re: [Nuke-users] Same operation on multiple inputs
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 vorbergpingkin...@googlemail.com An: Nuke user discussionnuke-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
Re: [Nuke-users] Same operation on multiple inputs
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 vorbergpingkin...@googlemail.com An: Nuke user discussionnuke-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
Re: [Nuke-users] Same operation on multiple inputs
i stumbled upon this a few days ago: http://www.creatogether.com/foreach-nk haven't tested it myself yet but looks like it's doing at least some of the stuff you're looking for. cheers, Holger Thomas Volkmann wrote: 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 -- Holger Hummel - hol...@celluloid-vfx.com Celluloid Visual Effects, Paul-Lincke-Ufer 39/40, 10999 Berlin phone +49 (0)30 / 54 735 220 - m...@celluloid-vfx.com ___ 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
Re: [Nuke-users] Same operation on multiple inputs
This would be cool. You have a reader that just reads in multiple files then writes out the file in the same manner as how BATCH works in Photoshop. I am sure it can be done with python but it would be awesome to have it built in. The write would just need to know to add something to the names after the original name and what directory you want to save to and whether to create a new folder for each sequence in the Batch set up.Fusion sort of does this but I can't remember how it handles the writing part. Randy S. Little http://www.rslittle.com On Sun, Nov 20, 2011 at 15:22, Thomas Volkmann t.volkm...@gmx.net wrote: 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
Re: [Nuke-users] Same operation on multiple inputs
A write node trick I use a lot for things like making proxy sizes or just
conversion putting something like this:
[ string map {.exr _p2.exr} [value [topnode].file] ]
in the file parameter in the write node.
It looks at the topnode (hopefully a read) and gets the value of the file
parameter from it and then does a string substitution so it doesn't write over
it and you can rename. This just saves writing a python function to change the
string, but is fairly simplistic.
On 21/11/2011, at 9:45 AM, Randy Little wrote:
This would be cool. You have a reader that just reads in multiple
files then writes out the file in the same manner as how BATCH works
in Photoshop. I am sure it can be done with python but it would be
awesome to have it built in. The write would just need to know to
add something to the names after the original name and what directory
you want to save to and whether to create a new folder for each
sequence in the Batch set up.Fusion sort of does this but I can't
remember how it handles the writing part.
Randy S. Little
http://www.rslittle.com
On Sun, Nov 20, 2011 at 15:22, Thomas Volkmann t.volkm...@gmx.net wrote:
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
