MULTIRENDER
Blender logo
For Blender Users

HoloMARI MultiRender for Blender

MultiRender is designed to make large Blender render jobs practical by using all available GPU resources in parallel while staying compatible with HoloMARI output workflows.

WHAT IS MULTIRENDER?

MultiRender is a Blender add-on that launches multiple headless Blender workers, typically one or more per GPU, to render frames or HoloMARI camera jobs in parallel. It combines stable GPU pinning (UUID/Bus), lightweight scheduling, per-worker logs, and clean cancellation so your machine stays productive from start to finish.

WHY USE THIS ADD-ON?

Why creators choose MultiRender:

  • Finish sooner by splitting frame ranges or MARI camera jobs across parallel workers.
  • Keep GPU binding stable with UUID/Bus mapping and avoid ghost-device mismatches.
  • Recover from interruptions with retries and requeue behavior for failed work units.
  • Track every worker with per-process logs and fast troubleshooting visibility.
  • Stay HoloMARI-native with FRAME/CIRCLE dispatch and .mari3d export on completion.
Built for multi-GPU workstations and creators who value time.
DOWNLOAD MULTIRENDER
Get the Blender add-on to render across multiple GPUs and instances in parallel.
DOWNLOAD MULTIRENDER ADD-ON

WHO IS IT FOR?

  • Blender artists pushing animation or heavy image-sequence renders.
  • HoloMARI creators exporting FRAME or CIRCLE camera jobs.
  • Studios with multi-GPU rigs that need predictable pinning and high throughput.

RENDER MODES

  • FRAMES: Distribute frame numbers across workers. Use image sequences; video formats are intentionally blocked.
  • MARI: Dispatch per-camera H/V index jobs (FRAME or CIRCLE) and export one final .mari3d file.

HOW IT WORKS

  1. Manager: In your Blender session, select GPUs and instances-per-GPU, then launch workers.
  2. Workers: Each headless process pins to a device, requests work, renders, and reports status.
  3. Completion: Logs are written and MARI mode outputs the final .mari3d into your project folder.

FEATURE HIGHLIGHTS

  • Multi-GPU and multi-instance dispatch with DYNAMIC and STRIDE scheduling options.
  • Deterministic device selection (UUID/Bus) with optional ghost-device filtering.
  • Per-worker log folders with a direct Open Logs workflow.
  • Clean cancel and graceful teardown using ESC.
  • Consistent output paths rebased to the source .blend location.
  • Headless execution support for workstation and render-node setups.

COMPATIBILITY & REQUIREMENTS

  • Blender: 3.x or newer.
  • GPU: NVIDIA is recommended for CUDA and UUID pinning reliability.
  • OS: Windows and Linux are supported for headless workflows. macOS behavior varies by hardware.
  • HoloMARI: Needed for MARI mode only. Not required for plain FRAMES mode.
  • Output: Use image sequences for FRAMES mode.

QUICK START

  1. Install via Edit > Preferences > Add-ons > Install, choose HoloMARI_MultiRender.py, then enable it.
  2. For FRAMES mode, set output to an image format such as PNG or EXR.
  3. For MARI mode, configure your HoloMARI cameras (FRAME or CIRCLE).
  4. Open Render Properties > Multi-GPU Frames / Multi-Instance MARI and choose GPUs plus instances.
  5. Start with Render (Multi-GPU Frames) or Render (Multi-Instance MARI).
  6. Use Open Logs for diagnostics. Press ESC for clean cancellation when needed.
FAQ

MultiRender FAQ

Q:Does this replace Blender's built-in queue?
A: It complements it. MultiRender runs parallel headless instances with stable device pinning and HoloMARI job dispatch for maximum throughput.
Q:Can I run multiple instances on a single GPU?
A: Yes. Use instances-per-GPU settings for latency-hidden workloads, then tune based on your scene.
Q:Why block video formats in FRAMES mode?
A: Parallel workers can contend for encoders and file handles. Image sequences are safer and more robust across processes.
Q:What if a worker crashes?
A: The scheduler retries and requeues failed units. Check the worker-specific log folder to identify the cause quickly.