Job Types

Every job in the queue has a type that determines which MetaHuman Animator pipeline it runs and what it requires. Use this page to pick the right one — then follow its workflow guide for the full detail. Types are usually assigned automatically from the take, and you can change a row's type at any time.

Mono A single color camera — head-mounted or any single-lens setup. The fastest type and the right default for most takes. Capture Data only Performance + face AnimSequence; optional body animation (UE 5.8) Stereo A multi-camera head-mounted rig. Highest fidelity — the depth-constrained solve resolves geometry mono footage cannot. Capture Data + Identity + Camera Calibration Performance + face AnimSequence (depth-constrained) Depth A single camera that recorded its own depth and shipped a calibration with the take - a mobile device running Live Link Face. Depth-constrained, with nothing to calibrate. Capture Data (color + depth + linked calibration) + Identity Performance + face AnimSequence (depth-constrained) Other The same as Depth, but the take carries no calibration - a generic depth camera. The calibration is found under the actor folder or linked by hand. Capture Data (color + depth) + Identity + a Camera Calibration Performance + face AnimSequence (depth-constrained) Audio A voice track with no footage. Generates lip-sync and expression from dialogue alone. A voice track — SoundWave, WAV on disk, or Wwise sound (UE 5.8) Performance + face AnimSequence (full-face or mouth-only) Calibration A stereo checkerboard take. Preflight step that produces the calibration every stereo take needs. Checkerboard Capture Data (2 image sequences) CameraCalibration asset (+ optional calib.json) Identity An identity take from a stereo rig or a depth camera. Preflight step that builds and rigs the MetaHuman Identity every depth-family take needs. Identity Capture Data + Camera Calibration Rigged, prepared MetaHumanIdentity (MHID_<Actor>)

Stereo, Depth and Other are the depth family: one solve branch and one options template between them. They differ only in where the depth and the calibration come from. A Calibration job can only ever serve a Stereo take, because one camera cannot solve a pair.

Calibration and Identity Create are not performance solves — they are the two preflight jobs that produce the assets every Stereo take depends on. They run first in the queue automatically. See the Stereo Workflow for how the chain fits together.

Guide Mono Workflow Guide Stereo Workflow Guide Audio Workflow