Nodes/ComfyUI-WanVideoWrapper/ReCamMaster Pose Visualizer
ComfyUI Node Runs on cloud

ReCamMaster Pose Visualizer

See your camera path before you render it

By kijai·Created about a year ago·Updated 2 months ago· 6,650
ReCamMaster Pose Visualizer
  • camera_poses
  • IMAGE
base_xval0.20
zval0.30
scale1.00
arrow_length1.00

Camera trajectories are abstract until you look at them. A list of poses, or a .txt of camera coordinates, tells you nothing about whether your shot arcs left gently or whips around the subject like a drone with a grudge. This node draws the path in a 3D plot so you can see the move before you spend minutes of GPU time rendering it and finding out it was wrong.

That's the entire job, and it's a good one. Video generation is slow - the KB has plenty of "5 minutes for a 5-second clip" reports - so anything that lets you catch a mistake before sampling is worth having. Wire this in, run the graph, and you get an image of little camera frustums stepping along the trajectory, arrows showing where the lens points.

What it visualizes

It takes camera poses and renders them as a 3D diagram: each camera position as a small pyramid (the classic "camera frustum" glyph) with a direction arrow, laid out along the path. You read it like a storyboard for the lens - does it orbit, dolly in, tilt up? It accepts poses from the ReCamMaster path, including ones built by WanVideoReCamMasterDefaultCamera, an Animatediff-Evolved CameraCtrl pose, or a RealEstate-style camera intrinsics file, per the node's own description.

The inputs and output

One required input carries the data; the rest are cosmetic controls for the plot:

  • camera_poses (CAMERAPOSES) - the trajectory to draw. This is the only input that matters for what you see.
  • base_xval (default 0.2) and zval (default 0.3) - the width and depth of each drawn camera frustum. Purely how big the glyphs are.
  • scale (default 1.0) - overall size of the plot.
  • arrow_length (default 1.0) - how long the direction arrows are drawn.

If the diagram is cluttered or the cameras overlap, these four just make it more legible - they don't touch your actual render.

The single output is IMAGE - the plot, which you can preview, save, or ignore once you've eyeballed it.

How to install it

Part of Kijai's WanVideoWrapper. ComfyUI Manager: search ComfyUI-WanVideoWrapper, install, restart. By hand:

cd ComfyUI/custom_nodes
git clone https://github.com/kijai/ComfyUI-WanVideoWrapper
pip install -r ComfyUI-WanVideoWrapper/requirements.txt

then restart. No model download for this one - it's a plotting utility. It relies on the wrapper's Python plotting dependencies (matplotlib-style 3D rendering), which come in with the pack's requirements, so if the pack installed cleanly this node works.

Common issues & troubleshooting

Blank or empty plot. Almost always means the camera_poses are empty or didn't get generated. Check the node feeding it - if you're using WanVideoReCamMasterDefaultCamera, make sure it got a valid latent to derive the frame count from.

The path looks nothing like your clip's motion. Remember this shows the camera trajectory, not object motion in the scene. A static camera on a busy scene draws as a single point - that's correct, not a bug.

Cameras are a tangled ball. Turn down scale or arrow_length, or shrink base_xval/zval. On a long trajectory the frustums pile up; the cosmetic knobs exist precisely for this. It changes the picture, never the render.

CategoryWanVideoWrapper

Inputs (5)

NameTypeDefaultDescription
camera_posesCAMERAPOSES
base_xvalFLOAT0.200–100
zvalFLOAT0.300–100
scaleFLOAT1.000.01–10
arrow_lengthFLOAT1.000–100

Outputs (1)

NameTypeDescription
IMAGEIMAGE