It would be great if we could have tasks with framelists, instead of frame ranges.
We render qts on the farm, and sometimes the quicktimes have ‘every Nth’ frame type lists, or retimes requiring skipping frames. SInce the quicktimes have to be rendered in a single session by a single machine, the only way we can currently do this is by modifying the nuke.py plugin and hacking in some range override property - and making the job a single task job.
Hey Laszlo,
We’ve had a handful of requests that essentially ask to make the Frames associated with a Task more flexible. And this request is very much in line with those requests. I’ve referenced your request in our design doc and opened a topic for internal discussion.
I definitely back this idea.
To take it a step further, it would be useful if tasks didn’t have to be associated with frames at all, but rather used a more flexible set of metadata that may or may not contain frames. That’s obviously for a separate (long) future discussion, but I figured I’d throw it out there in case that basic idea could inform some future design decisions.