So here is a Bug/Feature request. If you submit a bunch of write nodes with “Frame Range, Limit to Range” checked it’ll error if the write node is asked to write a frame sequence with no frames within the Limit To Range range. This isn’t normally a problem on a GUI render but when you chunk up the frames into groups it errors since you can’t have it just skip the chunks of each write node that aren’t enabled. It would be nice if when you submitted write nodes as separate jobs if it would look at the frame range if the limit to range is checked and change the job’s frame range automatically.
Makes sense. We’ll add it to the wishlist.
Thanks!
Ryan
I just checked the Nuke submitter code, and it appears that we already support this. If you enable the option to submit each write node as a separate job, you just need to enable the “Use Node’s Frame List” option, and we will pull the frame list from the write node if the “limit to range” option is enabled.
Cheers,
Ryan