Skip to content

Octane denoise companion renders

AlexPearce3D Studio can denoise a motion-blurred hero Beauty while using a separate sharp Beauty and Motion Vector AOV for temporal correspondence.

Companion recipe

  1. Duplicate the hero render job. Preserve the camera, frame range, resolution, scene state, shutter percentage, and shutter alignment.
  2. Add Render AOVs → Auxiliary/Info → Motion Vector AOV.
  3. Export Motion Vector as its own scene-linear EXR sequence. Use lossless ZIP or PIZ rather than DWAA for numerical vector data.
  4. Export a sharp Beauty from the same companion job. Assign it as Motion Guide Beauty in AlexPearce3D Studio.
  5. Keep companion and hero frame numbers exactly aligned.
  6. Run Check Render Readiness, Benchmark Guide, and Benchmark Motion before denoising the complete sequence.

Octane stores horizontal screen-space motion in red and vertical motion in green, measured in pixels. Enabling its Motion Vector AOV disables rendered motion blur, which is why the motion-blurred hero and sharp/vector companion must be separate renders.

The Render AOV Group's Info Sampling Mode affects motion blur, depth of field, and filtering for Info AOVs. Validate the chosen mode with AlexPearce3D Studio's five-frame comparison rather than assuming a vector interpretation.

Preflight expectations

Preflight checks:

  • Complete sequence coverage
  • 2:1 source shape when 360° handling is enabled
  • Matching Beauty, guide, and vector dimensions
  • Finite motion values and useful moving-pixel coverage
  • Magnitude percentiles and suspicious seam-length vectors
  • Octane render identity/header metadata where available

The benchmark tests direction, offsets −1/0/+1, and pixel scale against full-resolution-scaled Vision flow. It records and applies accepted offset/direction/scale corrections in settings, manifests, Metal processing, and EXR provenance.

Failure behavior

Optional AOV problems should warn and fall back rather than fail the RGB denoise. Final output uses an atomic manifest with a source/settings fingerprint, completed/resumed/failed frames, and per-frame fallbacks. Incompatible resumes are rejected.

Preview renders live in a separate cache and cannot be mistaken for completed final frames.

References