Cost and Render Time Estimation

🔧 How the Estimator Works

Before submitting a project, we recommend evaluating its render time and cost using our Cost Estimator tool.

1. Select your software, its version, and the render engine used.
2. Enter your machine’s CB R15 score (for CPU) or OctaneBench score (for GPU).
3. Input the number of frames in your animation.
4. Enter the render time per frame on your machine.
5. Click « Estimate Time/Cost ».

Important Considerations

The displayed time and cost correspond only to the pure render time. However, the total processing time of a project also includes:

• Distribution of the scene and assets across the RANCH.
• Scene loading time.
• Pure render time.

🎯 Estimator Accuracy

For a reliable estimate, ensure that:

• The average render time per frame is representative of your entire project. (Avoid using the render time of a single random frame, which may be significantly lower than the average.)

Factors Affecting Accuracy

The accuracy of the estimate depends on:

1. Render Time Consistency:
   • If all frames require the same render time, the estimate will be very close to reality.
2. CPU/GPU Load:
   • If all processor cores or graphics cards are utilized at 100% during rendering, the estimate will be more accurate.

📊 Tips for Accurate Estimation

For Animations (2+ Frames)

1. Submit a test with a few representative frames:
   • The number of test frames depends on the size of your animation.
   • Recommendation: Between 3 and 15 frames.
2. Concrete Example:
   • If your animation has 500 frames with varying render times:
     • 2 minutes at the beginning,
     • 15 minutes at two-thirds,
     • 10 minutes at the end.
   • Recommended test frames: 1, 165, 250, 333, and 500.

For Still Images

There are 2 methods to estimate cost and render time:

Method 1: Use the Cost Estimator

• Base your estimate on your render engine’s time prediction.
• ⚠️ Warning:
  • The estimated time may vary as rendering progresses.
  • Example:
    • You start a 10-minute render, and your software estimates a total time of 23 hours.
    • If you stop the render and use this estimate in our tool, it may be inaccurate.
    • In reality, after 30 minutes of rendering, the software might reassess the total time to 30 hours based on encountered difficulties.

Method 2: Render a Low-Resolution Image

• ⚠️ Conditions:
  • Maintain the length/width ratio of the final image.
  • This method loses accuracy if the size difference is too large.
  • The render time includes the scene loading time.
• Calculating Time for Final Resolution:
  • If you test with an image at ¼ of the final resolution, do not multiply the obtained time by 4, but by 16 (since the final resolution is divided by 4 in both length and width: 4² = 16).
• For Greater Accuracy:
  • Render your image in 3 different resolutions.
  • Observe the time progression curve based on resolution (linear, exponential, etc.).
  • Deduce the time and cost for the image at final resolution.

⚠️ Note : For unbiased renderers (such as Maxwell Render or Indigo), refer to the specific sections dedicated to them.

For distributed rendering (MultiBand with 3ds Max, C4D), the RANCH is approximately 50 times faster than your local machine (depending on its power).