CampaignReel

Ad placement specs against what generators output

Two published routes past a clip ceiling

Most rows in this column stop at a clip ceiling and leave what happens next to whoever edits the pieces. These two name the next step and price it: one as a distinct generation mode reaching twenty to twenty-five seconds, the other as segments composited at one credit per second of output. As of 2026-09-12.

Two published routes past one clipOne route is a distinct generation mode bought as a unit. The other is an assembly charged by the second of finished output, so it scales past any single figure.How is the piece taken past one clipA separate priced modeBought as a unitTwenty to twenty-five seconds, in its own row on therate card.Segments plus a compositeCharged by the secondOne credit per second of finished output, so it scalesto any length.Ten seconds against thirty before either route is used
Fig. 1 Thirteen rows here stop at a clip ceiling and leave what comes next to whoever edits the pieces.
How each page describes going beyond one clip. Recorded 2026-09-12.
What the pages statePikaSceneMixer
Ordinary ceiling10 seconds, a priced step30 seconds on the Wan 3.0 and Seedance 2.5 tiers
The route beyond itPikaframes, 20 to 25 secondsSegments composited into an episode
How the route is chargedIts own row on the rate card1 credit per second of output

Inclusion rule. Length figures and the published route past them, taken from each vendor's own page. Nothing is recorded about how the resulting joins look. Order. The ordinary ceiling first, then the route past it.

1A named step moves the work inside the product

Where the route past a ceiling is undocumented, a longer piece is an edit: several requests, several seams, and a separate tool to join them. Where it is documented and priced, the joining is part of what was bought.

That is a scheduling fact rather than a quality one. Neither page says whether a face or a key light survives the join, and no page in this register does, so the register stops at recording who owns the step.

2The two routes are shaped differently

One is a distinct generation mode with its own ceiling: twenty to twenty-five seconds, bought as a unit. The other is an assembly of segments charged by the second of finished output, so it scales past any single figure.

Against the thirty second Masthead window and the thirty second paid-view mark, the second route reaches them as one continuous piece on its longer tier and the first comes close without arriving.

3What each ordinary ceiling costs before the route matters

Ten seconds against thirty is three to one, so a minute is six or more pieces on one row and two on the other before either route is used. The route only changes who joins them, not how many there are.

Both pages also price resolution, which makes them two of the few in this register where a whole variant set can be costed from a single page. Neither publishes a frame rate and only one publishes a shape.

4The rest of the column behind these two

Duration across the registerPika is marked; SceneMixer sits at thirty seconds on one tier set, with a priced composite beyond it in the same column. Recorded 2026-09-22.Duration across the registerDurationAmazon Nova Reel — Duration: 6 s increments, up to two minutesAmazon Nova ReelCogVideoX — Duration: 6 s, at 49 framesCogVideoXGoogle Veo — Duration: 4, 6 or 8 sGoogle VeoGrok Imagine — Duration: 1 to 15 sGrok ImagineHedra — Duration: 10 minutesHedraHeyGen — Duration: 30 minutes per sceneHeyGenKling AI — Duration: Not statedKling AILTX-Video — Duration: Frames, never secondsLTX-VideoMiniMax — Duration: 4 to 15 sMiniMaxPika — Duration: 5 s and 10 s, 20-25 s on PikaframesPikaPixVerse — Duration: 1 to 15 s on version 6PixVerseRunway — Duration: 5 to 15 s on Gen-4.5RunwaySceneMixer — Duration: Thirty seconds on the Wan tiers, fifteen on H3SceneMixerVidu — Duration: Not statedViduWan 3.0 — Duration: 2 to 30 sWan 3.0
Fig. 2 Pika is marked; SceneMixer sits at thirty seconds on one tier set, with a priced composite beyond it in the same column. Recorded 2026-09-22.
Every generator in the register on the duration column, with Pika marked. Recorded 2026-09-22.
GeneratorDuration
Amazon Nova Reel6 s increments, up to two minutes
CogVideoX6 s, at 49 frames
Google Veo4, 6 or 8 s
Grok Imagine1 to 15 s
Hedra10 minutes
HeyGen30 minutes per scene
Kling AINot stated
LTX-VideoFrames, never seconds
MiniMax4 to 15 s
Pika5 s and 10 s, 20-25 s on Pikaframes
PixVerse1 to 15 s on version 6
Runway5 to 15 s on Gen-4.5
SceneMixerThirty seconds on the Wan tiers, fifteen on H3
ViduNot stated
Wan 3.02 to 30 s

Inclusion rule. Every generator this register carries, on the one column this pair disagrees about. Rows that state nothing keep their place and are marked hollow. Order. Alphabetical by generator name.

Why these two. Thirteen rows in this register stop at a clip ceiling. These two publish what comes next and attach a price to it, which changes who owns the joining work and puts it on the invoice rather than in a schedule.

  • Durations
    5 and 10 seconds for text-to-video and image-to-video, and up to 20 to 25 seconds on Pikaframespriced per stepPika, pricing / recorded 2026-09-12
  • Beyond the clip limit
    Episodes are composited from segments, billed at 1 credit per second of outputhow length is reachedSceneMixer, price list / recorded 2026-09-12

5Sources

Read from the Pika pricing page and the SceneMixer price list, both checked 2026-09-12. The column is described on duration, and each entry has its own cell page at Pika and SceneMixer, and the rule that keeps surfaces and generators apart is on method. Nearby pairs: MiniMax H3 and H3-Max, Runway and SceneMixer.