EasyAnimateV5 Sampler for Video to Video
V2V with camera, trajectory, and control — where EasyAnimate V5.1 gets interesting
- easyanimate_model
- prompt
- negative_prompt
- validation_video
- control_video
- ref_image
- images
EasyAnimateV5_V2VSampler is the most capable node in the EasyAnimate pack, and the one that justifies loading a -Control or -Control-Camera checkpoint at all. It's video-to-video, sure, but the interesting part is the optional inputs: control video, a reference image, and camera conditions. Wire all of them up and you're doing controlled, camera-directed video generation - the V5.1 headline features - in a single sampler.
It inherits the V2V flow from the legacy sampler but adds the V5 layer: Flow scheduler as the default, TeaCache on, and four optional inputs that unlock the control pipeline. This node only behaves like the demos if your loaded model matches what you're asking it to do, so the model wiring matters more here than anywhere else in the pack.
The inputs that matter
easyanimate_model- from the loader. This is the node wheremodel_typereally counts.Inpaintweights usevalidation_videofor restyling;Controlweights usecontrol_video(plus the extras below). LoadEasyAnimateV5.1-12b-zh-Controlor the-Control-Cameravariant and setmodel_typetoControl.validation_video(optional) - your source clip, forInpaintmodels.control_video(optional) - a conditioning video (Canny, pose, depth) forControlmodels. This is also where a trajectory video fromCreateTrajectoryBasedOnKJNodesgoes.camera_conditions(optional) - a STRING, force-input. This is the wire that the camera stack feeds:CameraTrajectoryFromChaoJie'scamera_trajectoryoutput plugs straight in here. Requires the-Control-Cameraweights.ref_image(optional) - a reference first frame forControlmodels (trajectory and camera workflows use this to anchor the shot).denoise_strength- 0.05–1.0, default 0.7. How much source structure survives.video_length- 1–49, step 4, default 49.scheduler- defaults toFlow.teacache_threshold0.1 andenable_teacachetrue round out the V5 trio.
The output
images - the generated IMAGE frame batch, straight to VideoHelperSuite for saving.
How the workflows stack
CameraTrajectoryFromChaoJie (camera_trajectory) ─┐
├─► EasyAnimateV5_V2VSampler
CreateTrajectoryBasedOnKJNodes (image) ─┘ (camera_conditions + control_video + ref_image)
The official V5.1 control-camera and control-trajectory workflow JSONs live in the pack's comfyui/v5.1/ folder if you want the whole graph without wiring it by hand.
Notes
This node is simultaneously the pack's high point and its most brittle corner. When everything matches - -Control-Camera weights, Control model type, trajectory length equal to video_length - the camera control is genuinely fun. When it doesn't, you get drift, ignored conditions, or the model refusing to move at all. The community enthusiasm around these features peaked at V5.1's launch in early 2025, and the pack's momentum faded as Wan and Hunyuan took over - so treat this as a capable, somewhat experimental control surface rather than a polished flagship. The 12B is also VRAM-hungry, so keep the qfloat8 offload mode and the 7B in mind for your first passes.
Inputs (16)
| Name | Type | Default | Description |
|---|---|---|---|
| easyanimate_model | EASYANIMATESMODEL | — | |
| prompt | STRING_PROMPT | — | |
| negative_prompt | STRING_PROMPT | — | |
| video_length | INT | 491–49 | — |
| base_resolution | COMBO | 768 | 4 options: 512, 768, 960, 1024 |
| seed | INT | 430–18446744073709550000 | — |
| steps | INT | 251–200 | — |
| cfg | FLOAT | 7.001–20 | — |
| denoise_strength | FLOAT | 0.700.05–1 | — |
| scheduler | COMBO | Flow | 6 options: Euler, Euler A, DPM++, PNDM, DDIM, Flow |
| teacache_threshold | FLOAT | 0.1000–1 | — |
| enable_teacache | COMBO | true | 2 options: false, true |
| validation_videoopt | IMAGE | — | |
| control_videoopt | IMAGE | — | |
| camera_conditionsopt | STRING | — | |
| ref_imageopt | IMAGE | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| images | IMAGE | — |