P-Video-Animate

P-Video-Animate is the node for when you have an image of something and want it to move - really move, not just drift. Its required inputs tell the story: referenceImages and referenceVideos, because this model animates a subject with reference guidance from both a still and a motion source. Character animation, product shots that come alive, a character whose look is locked but whose motion comes from a second clip - that's the territory. It runs on Runware's cloud and returns a native VIDEO.

The pairing of image + video reference is what separates this from a plain image-to-video node. One reference gives the model the subject's look; the other gives it the motion to copy. That's why you'd reach for it over, say, P-Video with a single frame image.

What you actually set

• referenceImages - required, IMAGE socket. The subject - the character, product, or scene you're animating.
• referenceVideos - required, RUNWARE_REFERENCEVIDEOS builder socket. The motion source. Wire in a clip whose movement you want applied to the reference image.
• positivePrompt - optional. Use it to steer the action when the reference video isn't the whole story.
• resolution - 720p or 1080p (default 720p); matches input aspect ratio automatically.
• fps - model default, 24, or 48.
• settings.preserveAudio - default True: keep the source video's audio track in the output. If your reference clip has sound you want to carry over, this is the switch; turn it off for silent output.
• seed, numberResults - the usuals.

Output: one video socket, type VIDEO.

Install

One-time pack install: ComfyUI Manager → search Runware → install → restart, or

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

API key into ComfyUI Settings → Runware API key or RUNWARE_API_KEY. Nothing heavy installs; the model is cloud-side.

Where people get burned

• The reference video drives everything. A jumpy, noisy reference clip produces jumpy, noisy animation. Your motion quality is capped by the clip you feed it.
• Both references have to be reachable. referenceVideos is a builder socket feeding the cloud - a local file path won't cut it; the clip needs to be uploadable/URL-reachable.
• safety.mode defaults to none. Opt into fast/full if you want a guardrail.
• It's a premium video run. Two references plus motion means a meatier request and a bigger per-run cost. Check the title bar before batching.

The verdict: if your workflow is "this exact character, doing this exact motion," nothing else in the pack does it as directly. If you just want prompt-to-video, the simpler P-Video node is cheaper and faster.