Verified short control · public R&D showcase

Animate one character from another performer's motion

A static ivory android adopts the dance of a visually unrelated mechanical performer. The three panels keep the input, driver, and generated result visible so the motion transfer can be judged rather than merely claimed.

Reference

Motion driver

Generated output

Output: 77 frames · 4.8125 sec
Quality gate: Short control passed
Measured run: About $0.06 GPU time
Long-form status: Separate validation gate

Inspect the advanced deployment Check your own workflow

Advanced deployment is available for technical evaluation, but it is not presented as a guaranteed one-click result. Review the current GPU rate before launching; running deployments are billed until stopped.

What this run verifies

A reproducible short motion-transfer proof

The output follows the unrelated driver’s full-body dance instead of inventing arbitrary motion.
The target’s ivory ceramic identity, bald mechanical head, fitted costume, hands, and feet remain recognizable.
No human skin, hair, duplicate performer, cropped feet, or black padding appeared in the reviewed output.
The exact reference, preprocessed driver, workflow config, output, and hashes are retained for reproduction.

What it does not verify

Long-form and self-serve remain open gates

This 4.8-second control does not prove the same visual quality across a 20–60 second render.
SAM2 first-frame mask points still need visual validation and may need manual tuning for a new subject or driver.
Driver and target silhouette compatibility materially affects costume and anatomy stability.
Rear-angle hip understructure shifts slightly, so this is a strong public proof—not a flawless production result.

The useful workflow lesson

Validate the mask before paying for diffusion

Prompt changes alone did not fix earlier identity leakage. The reliable improvement came from matching the target and driver silhouettes, then previewing the SAM2 removal mask across the full driver before starting the paid generation step.

1
Prepare the target
Use a full-body character with clear limbs and framing compatible with the driver.
2
Normalize the driver
Pin crop, resolution, frame rate, duration, and the licensed source interval.
3
Inspect SAM2
Preview the entire removal mask and tune first-frame points before generation.
4
Render and validate
Check identity, anatomy, framing, motion fidelity, continuity, media metadata, and cost.

Current product status

The short proof is ready to share. The hosted environment and direct deployment route exist, but each new input can still require mask tuning and visual QA. A clean V4 long-form render is the next technical quality gate; audience actions on this page are the distribution gate.

Inspect deployment details View licensed driver source