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
