Why a frame count is not a run time
Where a length is published as a frame count, the seconds figure is one division away and the register still does not print it. The reason is not pedantry: frame-based pages usually carry a rule about which counts are accepted, and seconds cannot express it. As of 2026-09-12.
| What the frame figure carries | Survives conversion | Why it matters |
|---|---|---|
| An approximate run time | Yes | It is what the slot is written in |
| Which values are legal | No | Counts often have to divide by a fixed number |
| Whether the bound is hard | Sometimes | A quality note is weaker than a refusal |
Inclusion rule. Properties a published frame count can carry. A frame rate assumed rather than stated on the same page is not used for a conversion. Order. The property a conversion keeps first.
1A lattice and a continuum look the same in a table
A range of whole seconds allows every value between its ends. A frame ceiling with a divisibility rule allows a sparse set: a handful of counts spaced evenly apart, with everything between them refused.
Printed as seconds both become a single upper bound and the sparseness disappears. A shot list built from that figure will ask for lengths the model rejects, and the error message will not mention frames.
2Frame pages are written for a different reader
Someone running weights budgets frames against memory, so the frame count is the quantity that matters and seconds are a convenience. Some pages do the conversion for the reader and some leave it, and that choice tells you who the page is for.
A buyer planning a placement works the other way round. The honest procedure is to plan in frames on those rows, convert at the end, and treat the seconds figure as an output of the plan rather than an input to it.
3Two kinds of frame bound
Some pages refuse counts above a figure. Others say quality holds below it, which is weaker than a refusal and stronger than a suggestion: a request above it may return something and the page declines to say what.
Those are different planning facts. A refusal can be designed around; a degradation is a risk that has to be tested, and a register that recorded both as one ceiling would be hiding the difference between a wall and a slope.
A craft note, not a spec. Nothing here is taken from a platform or a vendor, and nothing here should be quoted as a requirement. The sourced material is on published limits. Related: Why a ladder exists, Planning a join.
4A generator's ad pipeline
For ad work around “Frames and seconds”, 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)