Motion Control vs Recast vs Motion Transfer: Which Keeps the Dance
Kling motion control, H3 Max Recast and Genjutsu all reuse motion from a source clip. See inputs, limits and per-second Sume prices side by side.
Three Sume routes reuse the movement in a source video and change who or what performs it. They look similar and are priced differently, so it is worth knowing which input each wants.
What each one takes
Kling motion control, POST /v1/kling/3.0/motion-control, takes a still or avatar image plus a motion video of up to 30 seconds. It has keep_original_sound, a character_orientation of video or image, and an optional prompt of up to 2,000 characters. Kling's own feature page lists Motion Control as a separate feature from video generation.
h3-max-recast takes one source video plus 1 to 4 person photos and keeps motion, camera, cuts and the soundtrack. higgsfield-genjutsu takes one source video plus 1 to 8 reference images and has no text-only mode.
| Route | Source | Identity input | Sume per second |
|---|---|---|---|
| Kling motion control | Up to 30 s | One still or avatar | $0.1575 (list $0.126) |
| h3-max-recast | 5 to 30 s, no shot over 15 s | 1 to 4 person photos | $0.375 at 768p, $0.5625 at 1080p |
| higgsfield-genjutsu | 4 to 30 s | 1 to 8 images | $0.3975 at 480p, $0.85125 at 720p |
Choosing
If one character performs the whole clip and you want the cheapest route, motion control is less than half the Recast rate at 768p. If the clip has several people and several cuts that must survive, Recast preserves the camera and cuts and swaps each person. Genjutsu is the most expensive and is listed only when its provider is configured, so check GET /v1/video-router/models before designing around it.
Runway's pricing page lists Act-Two, its own performance-transfer model, at 5 credits. It is not part of Sume's catalog.
Test cheaply first
Cut a 5-second slice of the source with Sume's video trim route ($0.02) and run the three routes on it before you commit a 30-second render.
Sources
Related posts
More in Models
- Sume Music Router: job.model vs routed_model, which engine ran
On Sume Music Router, job.model echoes the id you sent and request.routed_model names the engine that ran. Ids, price and the Music 1.0 route.
- Music Router routed_model: log which engine made each track
With sume/music-auto, job.request.routed_model names the engine that ran, such as lyria-3.5. Why to store it per track and how to read it from a job.
- Nano Banana Pro interleaved text and images vs Sume image output
Google documents Nano Banana Pro returning text blocks with illustrations in one answer. Sume's Image API documents image results only; here is the workaround.
- NVIDIA VideoFDB: what Griffin Lite's 3.73 means for avatar buyers
VideoFDB scores perception on 237 call clips across 11 nonverbal dynamics. Griffin Lite led full-duplex systems at 3.73 against a human 4.20.
Written by Sume