CampaignReel

Ad placement specs against what generators output

The two rows that charge by the second of output

Two entries in this register publish a per-second basis. One charges every generation that way, at a stated rate per second for two model names. The other charges the compositing step that way, at one credit per second of finished output. On both rows length is money. As of 2026-09-22.

Why the cheap order of work differsWhere every second is charged, framing is settled short and the length raised once. Where a request has a flat rate, a short test costs the same as a long one.Settle the frameAt the shortest usablelength on a per-second rowA compositionRaise the lengthOnce, when the framing isalready rightA finished pieceOn a flat-rate rowIterate at full length; ashort test saves nothing
Fig. 1 No general rule about drafting can be written for this register, which is what this pair shows.
What each page charges by the second. Recorded 2026-09-22.
What the pages stateRunwaySceneMixer
What is billed per secondEvery generationThe composite past the clip ceiling
Clip ceiling15 seconds on Gen-4.530 seconds on the Wan 3.0 and Seedance 2.5 tiers
Cheapest way to iterateAt the bottom of the rangeInside one clip, before compositing

Inclusion rule. Billing statements from each vendor's own page, with the clip figure from the same page. No rates are quoted and no currencies are converted. Order. What is billed first, then the length it applies to.

1Per-second billing changes the order of work

Where every second is charged, framing and lighting should be settled at the shortest usable length and the length raised once. Discovering at fifteen seconds that the framing was wrong costs three times discovering it at five.

On a row with a flat rate per request the opposite is true: iterate at full length, because a short test costs the same as a long one. This pair is the reason a general rule about drafting cannot be written for the whole register.

2The two pages charge for different parts of the job

One charges the generation. The other charges the assembly that happens once the clip ceiling is passed, so requests inside thirty seconds are priced by the tier and only the longer pieces meet a per-second line.

For a sixty second non-skippable that matters. On the first row the whole minute is four per-second charges; on the second it is two tier charges plus a per-second composite, and the arithmetic has a different shape.

3What neither basis tells anyone

Neither publishes how many attempts a usable take costs, and that is the number that decides a budget. A rate per second multiplied by a length gives a floor, not a forecast.

These sheets record the basis because it changes the shape of the estimate, not because it produces one. The attempt count is the figure no page in this register publishes, and it is the reason a media plan carries a contingency.

4The rest of the column behind these two

Duration across the registerRunway is marked; SceneMixer sits at thirty seconds a clip, with the composite priced by the second 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 Runway is marked; SceneMixer sits at thirty seconds a clip, with the composite priced by the second in the same column. Recorded 2026-09-22.
Every generator in the register on the duration column, with Runway 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. Everywhere else in this register length is a parameter and cost is a separate question. On these two rows the duration field is the invoice, which changes the order the work should be done in.

  • How generation is billed
    Charged per second of output, with gen4_turbo at 5 credits per second and gen4.5 at 12Runway API, pricing and costs / recorded 2026-09-22
  • 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 Runway pricing guide and input reference, and the SceneMixer price list, checked 2026-09-22 and 2026-09-12 respectively. The column is described on duration, and each entry has its own cell page at Runway and SceneMixer, and the rule that keeps surfaces and generators apart is on method. Nearby pairs: Veo and Wan 3.0 on retention, Nova Reel and CogVideoX.