Dylan Penhale wrote:
> Thanks Greg
>
> [2048] is good, but we will opt for splitting over multiple lines as suggested.
> Basically we just want to render out the 1st, middle and last frames, then
> the middle of those, then sort of fill in the gaps. We can create a small
> code to formulate that string when we submit.
Right, every so often the 'binary tree' ordering comes up.
Your approach is correct; to create 'frames' commands
with the frames in the order you want them.
I should probably make a '-btree' option flag for the 'frames'
submit command, so that it will automatically generate a
'binary tree' frame ordering for frame ranges. That way you
could just do:
frames -btree 1-100
..and it would generate the "1 50 100 25 75 .." frame ordering.
I'll add it to ol' todo list for the upcoming major release.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|