Here's an excerpt from the Using Qube manual that should help:
Frame-based Jobs Normally, if you submit a qbsub job to multiple CPUs, Qube will execute the exact same task on each CPU. This would prove redundant if you would like to render a different frame on each CPU, so qbsub has the built-in capability to submit a job to run on multiple CPUs, but send different frames to each running subjob. All that is needed is the range of frames to run, and the command line to submit with the QB_FRAME_NUMBER macro used to determine where the frame number should be inserted into the command line when the command is run.
The standard frame range format for Qube follows this convention:
start-
endx
stepYou may also list frames as well as combine frames and ranges with commas:
frame,?
frame, [
frame|
range,?]
Examples1-100 | Frames 1 to 100 |
1-100x10 | Every 10th frame from 1 to 100 |
1,2,3,4,5 | Frames 1, 2, 3, 4 and 5 |
1-10,20-30 | Frames 1 to 10 and 20 to 30 |
-100-100 | Frames -100 to 100 |
-10- -1 | Frames -10 to -1 |
10-20, 30-40x2 | Frames 10 to 20 and every second Frame from 30 to 40 |
Example % qbsub --range 1-100 Render ?s QB_FRAME_NUMBER ?e QB_FRAME_NUMBER myscenefile.ma Frame-based jobs may also be done based upon frame partitions as well. This is also accomplished in combination with a different set of macro strings. QB_FRAME_START is used to denote the first frame in the range, QB_FRAME_END is used to denote the last frame in the range. QB_FRAME_STEP is used if the frame range contains a step value. This is useful for applications which are more efficient when handling more frames than one at
a time.
Example Render frames from 1 to 100 in partitions of 10 each:
% qbsub --range 1-100 --chunk 10 Render ?s QB_FRAME_START ?e QB_FRAME_END myscenefile.ma Example Render frames from 1 to 100 in 2 partitions of 50 each:
% qbsub --range 1-100 --partition 2 Render ?s QB_FRAME_START ?e QB_FRAME_END myscenefile.ma