Skip to content

Practice

VFX & Animation Pipeline

Generative-AI tooling that integrates cleanly with existing VFX and animation pipelines — Nuke, Houdini, Maya, Blender — without disrupting the production.

AI-generated image of a VFX compositing suite — multi-monitor workstation showing a node graph, timeline, and rendered frame preview.

How it works

VFX pipeline integration DCC tools on the left (Nuke, Houdini, Maya, Blender) connect bidirectionally to a central ComfyUI workflow runtime, which in turn drives the render farm, exchanges assets with a USD library, and reads versioned per-show config. An ACES / OpenColorIO band runs across the entire diagram to indicate end-to-end colour management. DCC TOOLS WORKFLOW RUNTIME PIPELINE INFRASTRUCTURE Nuke Houdini Maya Blender ComfyUI Workflow Runtime Per-show LoRAs Diffusion pipelines Custom nodes Versioned · reproducible · headless Render Farm Deadline · OpenCue · Tractor USD Asset Library shared scene description Per-show Config versioned in git ACES COLOUR PIPELINE · OpenColorIO end-to-end colour management across every stage Solid line = primary data flow · Dashed line = asset exchange or config
Generative tooling integrated into the existing pipeline. No new system to babysit. Colour-correct end to end.

What this practice is.

We design for VFX supervisors and pipeline technical directors. The brief is consistent: generative-AI tooling that integrates with the DCCs, render farms, and colour pipelines already in production. ComfyUI workflows orchestrated on Deadline / OpenCue render farms. Seeded, deterministic generation with locked model versions per show. USD-native asset exchange. ACES colour management throughout.

What we build.

Frame-level generative tools

Inpainting, outpainting, rotoscoping assistance, plate prep, beauty pass cleanup, sky and crowd replacement. Run as Nuke gizmos, Houdini HDAs, or batch jobs on the render farm.

Motion-aware video generation

Custom diffusion pipelines with motion-vector conditioning, depth and optical-flow priors, and reference-image fidelity. For element gen, look-dev shortcuts, and previz that doesn't fight the supervisor's notes.

Pipeline tooling and orchestration

ComfyUI workflow registries, render-farm integration (Deadline, OpenCue, Tractor), USD-aware asset libraries, versioned-asset review tooling, and per-show config management.

Custom model training and adaptation

LoRA training on a show's reference library, style-locked adapters for series consistency, and per-asset fine-tuning so generative outputs stay on-model across thousands of frames.

How we engineer in this practice.

01

Pipeline-first by design

Generative tooling that does not integrate cleanly with the show's pipeline — versioning, colour management, review, archival — is not delivered. We engineer to the requirements of the pipeline, not to the demonstration.

02

ACES-aware and colour-correct

Diffusion models live in sRGB; production lives in ACES. We engineer the colour transforms end-to-end so generative outputs sit correctly in scene-referred space, not the supervisor's inbox.

03

Deterministic where the show needs it

Seeded generation, locked prompts, frozen model versions per show, and per-shot config files in the production repo. Reproducibility is a delivery requirement, not a feature request.

04

Render farm as the substrate

Generative jobs queue on Deadline / OpenCue / Tractor like any other render task. No bespoke infra to babysit. No separate cost-tracking system.

05

IP and likeness governance built-in

Model training data and asset provenance tracked from day one. No "trust us" on what went into the model.

Stack in this practice.

  • ComfyUI workflow runtime with custom node libraries
  • Stable Diffusion XL, Flux, Wan 2.x, Stable Video Diffusion — model-by-model evaluated per show
  • Custom Nuke gizmos, Houdini HDAs, Blender add-ons, Maya plugins
  • NVIDIA RTX 6000 Ada / L40S render-farm nodes for diffusion workloads
  • Pixar USD for asset interchange; OpenColorIO for ACES
  • Deadline / OpenCue / Tractor for job orchestration
  • S3-compatible object stores (MinIO on-prem, AWS S3 in cloud-bursting workflows)

See the firm-wide stack →

What we won't build in this practice.

Training on assets without provenance

If we can't verify what went into a model, the studio can't ship outputs from it without legal exposure. Provenance is engineered in from the start.

Likeness replication without talent consent

Recreating a specific performer's likeness requires their written consent and a per-use contract. We won't build the pipeline that lets a studio skip that.

Black-box "AI shot" pitches with no eval

Every generative tool we ship comes with an eval suite for the show — pass rate, supervisor accept rate, rework rate. If we can't measure it, the show shouldn't bet on it.

Run a vfx pipeline scoping conversation.

Tell us what you've already tried, what you've ruled out, and what success looks like. We come back within one working day.