Video control surfaces: Runway Act-Two vs Pika Pikaframes — motion-capture vs keyframe-directorial

3 sources

Runway Act-Two (motion-capture upgrade for actor-driven motion in Runway Gen-4.5) and Pika Pikaframes (keyframe-to-keyframe interpolation that lets creators specify start and end frames and lets the model fill the gap) are two complementary control surfaces for video generation that shipped in the same week. They take different bets on creator control: Runway Act-Two on motion-capture (actor wears mocap, model translates motion into the generated video); Pika Pikaframes on keyframe-directorial (creator specifies start and end frames, model fills the gap). The two are not equivalent: Act-Two is best for motion-driven content (choreography, performance); Pikaframes is best for shot-transition-driven content (storyboards with planned shot flow).

Why now

Both shipped in the same week — creators can now pick the control surface that matches their workflow.

Why it is worth publishing

Demo potential: side-by-side of the same choreography / storyboard scene built with Act-Two vs Pikaframes.

Evidence basis

Two independent vendor primary sources + The Decoder weekly roundup

“Runway Act-Two and Pika Pikaframes both shipped this week — and they take different bets on creator control: motion-capture for motion-driven content, keyframe-directorial for shot-transition-driven content.”

Angle

Frame the two as 'motion-capture vs keyframe-directorial' control surfaces — Act-Two for motion-driven content, Pikaframes for shot-transition-driven content.

Format

Short talking-head video

Demo idea

Record a 6-minute explainer: 1 min intro on 'motion vs keyframe' framing, 2 min on Act-Two (mocap-driven workflow), 2 min on Pikaframes (keyframe workflow), 1 min on which content fits which surface.

Platform notes

Specific mocap rig requirements, keyframe schema details, and per-tier pricing beyond the captured summary are not extracted.

Usable claims

Runway Gen-4.5 video generation model reached GA — improved motion coherence over 5+ second shots, character / object consistency across scenes, Act-Two motion-capture upgrade.
Pika 2.2 — Pikaframes keyframe-to-keyframe interpolation (specify start and end frames), improved scene consistency, Pika Additions API for in-painting.

Evidence pipeline

From the news

Breakdown

Runway Act-Two bets on motion-capture control; Pika Pikaframes bets on keyframe-directorial control. This explainer uses the motion-vs-keyframe framing as the lens for picking a control surface based on content type (motion-driven vs shot-transition-driven).

Sources

Risks

Use The Decoder and IT之家 as media-type corroboration, but read the underlying vendor docs for any specific capability or pricing claim before stating it on the record. Verify specific capability claim against the underlying vendor docs and the actual license / pricing matrix before stating it on the record; do not paraphrase per-platform pricing or license terms into specific dollar figures or commercial-use clauses.
Vendor docs confirm feature existence but specific pricing beyond the captured summary is not in this pass. Verify specific capability claim against the underlying vendor docs and the actual license / pricing matrix before stating it on the record; do not paraphrase per-platform pricing or license terms into specific dollar figures or commercial-use clauses.

Demo ideas

Side-by-side: same choreography on Act-Two (mocap-driven) vs Pikaframes (keyframe-driven).
Content-type decision matrix: choreography / performance → Act-Two, storyboard / shot flow → Pikaframes.
Workflow story: 'migrate a mocap-driven workflow to keyframe-directorial' or vice versa, measure porting work.