I usually end up running this:
def renderByInputRange( all=False ):
"""
renderByInputRange( all )
Render all or the selected nodes by their input ranges.
"""
if all:
nodes = [(n['render_order'].value(), n) for n in nuke.allNodes(
'Write' )]
else:
nodes = [(n['render_order'].value(), n) for n in
nuke.selectedNodes( 'Write' )]
nodes.sort()
if nodes:
for n in nodes:
n = n[-1]
first = n.firstFrame()
last = n.lastFrame()
nuke.render( n.name(), first, last, 1 )
On Wed, Jun 20, 2012 at 7:46 PM, Frank Rueter <[email protected]> wrote:
> The Input frame range usually only works if the node in question is also
> hooked up to a viewer - a very annoying bug in my eyes, but possibly a
> feature in others'. Input is meant to take the selected node's frame range
> which can be modified with the FrameRange node if required.
>
> The global range will always take what the script is set to and the
> "custom" range becomes active if you manually punch in a range (no need to
> select it, it's more of an indicator that you are rendering a custom range).
>
> Then you also have the Viewer ranges which of course take whatever the
> respective viewer is set to.
>
> When rendering multiple Write nodes with different ranges, you will still
> have to figure out the correct frame range to render yourself (and use one
> of the above methods to do so)
>
>
>
>
> On 21/06/12 4:59 AM, Rich Bobo wrote:
>
> I would also love to know the answer to this question... I have multiple
> write nodes and they have all different end times. Even if I set "Custom"
> ranges, they *all* get changed when I edit the next Write node...
>
> Rich
>
> Rich Bobo
> Senior VFX Compositor
>
> Mobile: (248) 840-2665
> Web: http://richbobo.com/
>
>
> On Jun 20, 2012, at 11:18 AM, morgn wrote:
>
> Hi,
>
> Ive specified in each write node the correct frame range. Each write node
> has a different sequence length. When i hit render all, it gives me a drop
> down box for Input/Global/Custom/Viewer. The default value is 1-1, and so
> when i hit render i only get the first frame of each rendered.
>
> Whats the magic trick so Nuke behaves itself and renders the correct frame
> ranges?
>
> Thanks,
>
> Morgn.
> _______________________________________________
> Nuke-users mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>
>
>
> _______________________________________________
> Nuke-users mailing [email protected],
> http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>
>
>
> _______________________________________________
> Nuke-users mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
