1. Qube
2. _InclusionsLibrary
3. _SimpleCMD_QubeFrameRangeWithChunk

_SimpleCMD_QubeFrameRangeWithChunk

Most jobs require a frame range

to execute on the

workers. You can set this range in a few different ways :

• "1-100" will just render the range between 1 and 100
• "1-100x3" will render the range 1 to 100, every third frame, so 1, 4, 7, etc.
• "1,3,7,10" will only render the selected frames 1,3,7,10

Execution
Tooltip - How to break up frame range to be executed. Use QB_START_FRAME, QB_END_FRAME and QB_FRAME_NUMBER

When submitting a job to the farm it may be more efficient to "chunk" your job. This means that when the job is sent to the worker it tells the worker to render

N consecutive frames before requesting more work. You would do this to keep from reopening the scene file for each frame. Large scene files can take substantial time to open, which is wasteful across dozens or hundreds of frames.

The drop down options are below:

• "Individual frames" this tells the worker to render 1 frame at a time.
• "Chunks with n frames" this tells the worker to render consecutively the number of frames specified in the

• field.
• "Split into n partitions" this tells the worker to render consecutively the total frames in the range divided by the number in the

• field.

Examples:

• range 1-100 with "individual frames" set will render 1 frame at a time
• range 1-100 with "Chunks with n frames" and the

• field set to

• 5 will send

• 20 frames to each

• instance
• range 1-100 with "Split into n partitions" and the

• field set to 4 will send 25 frames to each

• instance

rangeOrdering
Tooltip - Order to render the items. (Ascending=1,2,3,4,5...,Descending=10,9,8...,Binary=first,middle,last...)

You can set the order in which your frames are rendered. The drop down options are:

• "Ascending" - this will render the frames counting upwards from your start frame
• "Decending" - this will render the frames counting backwards from your end frame
• "Binary"