Luma Ray3.2 makes 5 or 10 second clips; which Sume ids accept both

Luma's Ray3.2 page lists text-to-video and image-to-video at 5 or 10 seconds native. Both durations are valid on every pinned Sume video id that produces text or image clips: seedance-2.5 (4-30 s), wan-3.0 (2-30 s), kling-3 (4-15 s), minimax-h3 and minimax-h3-max (5-15 s) and gemini-omni-flash-1.1 (3-10 s). Luma itself is not in the Sume catalog.

The Luma figures are from Luma's Ray page, read on 2026-10-03, and the Sume ranges from the Video Router docs and Video generation docs.

A fair comparison clip

If you are comparing a Luma clip with a Sume model, matching the duration first removes one variable. Use 5 seconds for a fast, cheap read on motion and 10 seconds to see whether the model holds identity and lighting over time.

Keep the other settings equal too: same prompt, same first frame, same aspect ratio. The side-by-side workflow is covered in same prompt, three models.

Cost grows with seconds

Every Video Router model bills list times 1.25 and most bill per output second, so a 10 second clip costs about twice a 5 second one on the same model and resolution. Generate the 5 second version first; commit to 10 only when the shorter clip is right.

Seedance is billed on video tokens rather than seconds, so use the pricing block from the models list for it and compute a total from that.

Edge cases

Whole seconds only: the docs define duration as an integer and list supported_durations in whole seconds, so ask for 5 or 10, not 7.5.

If a model changes its range, supported_durations changes with it. Read the list when your service starts instead of copying numbers from a blog.