I’m trying to get something like the following line to work, for a range of images starting at frame 800 through 824. I cannot figure out how to get Natron not to freak out about the Reader syntax:
This assumes that my frame range exclusively lies between 100-999 though, right? If I have a frame range that goes from 1-2000, and my frames are NOT zero-padded, what is the correct way to run a natron script with command-line-provided inputs and outputs?
In Aftereffects or Nuke, “#” signifies “nonzero-padded images”, and “#” will happily work with frame 1, 100, or 1000. Natron seems to be saying that “#” means a single-digit frame (so, only valid from 1-9), is that true?
This problem seems to exist when I have a natron script with “un-initialized” Read nodes. If I pre-point the read nodes to an image sequence, they seem to behave a bit better (though my “number of hashes” question above still stands). It seems there are some sort of callbacks built into the Read node that need to be triggered before the script can be used from the command line.
For example, if I have a Read node pointed to “imagesA.###.exr”, then do this: