Load CameraCtrl Poses (File) 🎭🅐🅓②

The Create CameraCtrl Poses nodes build a camera trajectory procedurally, one motion at a time. This one skips that entirely and loads a pre-authored pose file straight off disk - the option if you already have a trajectory you want to reuse, whether that's one of CameraCtrl's own example paths or something you've saved from a previous session.

What it does

pose_filename is a dropdown, the same pattern as a checkpoint or LoRA loader - it lists pose files ComfyUI finds in the expected location and lets you pick one. The node reads it and produces the same CAMERACTRL_POSES type the procedural Basic and Advanced nodes output, so it's a drop-in alternative wherever those would go: feed it straight into the Gen2 CameraCtrl application node, or into Replace Camera Parameters first if you need to adjust the intrinsics for your target framing.

Loading a file is the natural move if you want a specific, known-good trajectory (the CameraCtrl project's own reference paths follow this pattern) rather than hand-tuning motion types and strengths from scratch every time.

The one input that matters

• pose_filename - which pose file to load, selected from what's available in your setup.

Output is CAMERACTRL_POSES.

How to install it

Same CameraCtrl setup as the rest of this family.

• ComfyUI Manager - search AnimateDiff Evolved by Kosinkadink, install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/Kosinkadink/ComfyUI-AnimateDiff-Evolved, restart.
• Model - CameraCtrl_pruned.safetensors.
• Motion module - v3 SD1.5 (v3_sd15_mm), per the README's note that CameraCtrl "was specifically trained for" it.
• Gen2 only.

Common issues & troubleshooting

The dropdown is empty, or your file doesn't show up. This is the most common friction point with any file-dropdown node in ComfyUI - restart after adding a new pose file rather than expecting it to hot-reload, and confirm it landed in the location the node actually scans.

CameraCtrl is niche enough that troubleshooting help is thin on the ground. It's one of the least-discussed features in an already large pack, so if a loaded pose doesn't produce the motion you expected, you're mostly working from the README and direct experimentation rather than a stack of community threads to check against.

Loaded a pose but want to tweak the framing without rebuilding the trajectory. That's what Replace Camera Parameters is for - it overrides the camera intrinsics (focal length, optical center) on a loaded or generated CAMERACTRL_POSES object without touching the actual motion path.