CampaignReel

Ad placement specs against what generators output

Where a length is published in frames

Every ad slot in this register is written in seconds. Two entries publish their length in frames: one states six seconds at forty-nine frames, and one states a ceiling below 257 frames and never prints a second at all. As of 2026-09-22.

Plan in frames, convert at the endA shot list written in seconds lands on values one of these entries refuses, because legal frame counts divide by eight plus one and nothing in the error says so.Frames and seconds printedFrames onlyThe published length49 frames, 6 secondsBelow 257 framesThe rate8 a second30 a secondLegal valuesOne249, 241, 233, and downwards in eightsEvery ad slot here is written in seconds
Fig. 1 One card performs the conversion for the reader and the other leaves it, which is why only one seconds figure is recorded.
How each frame-based entry states its length. Recorded 2026-09-22.
ItemWhat is publishedDetail
Frames and seconds both printed49 frames, 6 secondsThe card performs the conversion
Frames onlyBelow 257 frames, at 30 FPSThe card leaves the conversion to the reader
The filter on legal valuesDivisible by 8, plus 1249, 241, 233 and downwards in eights

Inclusion rule. Entries whose own page expresses a length as a frame count. A seconds figure is recorded only where the page itself prints one. Order. The entry that converts first, then the one that does not.

1A conversion the register declines to publish

Frames below 257 at thirty a second is a little over eight seconds. The arithmetic is trivial and the result would sit in the table looking exactly like a figure somebody published, carrying a check date it did not earn.

There is a substantive reason as well. Legal counts divide by eight plus one, so the available lengths are a sparse set rather than a range. A seconds figure implies a range and the unit carries the constraint.

2Why the length is a frame count in the first place

Both entries are open-weight releases described for someone running inference, where frames are the quantity budgeted against memory. Seconds are a derived convenience, and one card offers it while the other does not.

On the card that does, the conversion also explains the number: forty-nine frames at eight a second is the six seconds it prints. The three cells only make sense read together.

3What a buyer has to do with these two rows

Plan in frames and convert at the end, rather than the other way round. A shot list written in seconds will land on values one of these entries refuses, and nothing in the error will mention divisibility.

Against a thirty second window that means four requests on one row and five on the other, with the last piece on each sized by what the model accepts rather than by what the edit wanted.

  • Where the card says quality holds; length is published in frames
    Works best on resolutions under 720 x 1280 and number of frames below 257not secondsLightricks LTX-Video model card / recorded 2026-09-22
  • Shapes and lengths the model accepts
    Resolutions that are divisible by 32 and number of frames that are divisible by 8 + 1Lightricks LTX-Video model card / recorded 2026-09-22
  • Video length
    6 seconds, at 49 framesfrom the model card tableCogVideoX-5B model card / recorded 2026-09-22

4From brief to placement

For ad work around “Length in frames”, SceneMixer's pages explain how its ad projects are produced:

Paste a scene or a short script and SceneMixer gives you a storyboard — numbered shots with framing and seconds — and then a moving version of each segment, which you can join into a rough cut of the scene.

SceneMixer, Using SceneMixer for Previs and Animatics Before a Live-Action Shoot (read 2026-10-13)

Video is 16:9 landscape by default, with 9:16 vertical available; you set it once per project. Segments are typically 4 to 15 seconds, and some model tiers go to 30.

SceneMixer, AI Short Drama Generator — “What length and aspect ratio does it output?” (read 2026-10-13)

5Sources

Format requirements come from Google Ads Help, read 2026-09-12, and tool limits from each vendor page listed on published limits, read 2026-09-22. The rule against mixing the two is on method. Nearby: Single values, Published defaults, A minute in one call.