Luma Ray 3.2 video-to-video: 20 s, 64 keyframes, vs Omni edit on Sume

Luma's Ray 3.2 video-to-video page says the output keeps the source clip's duration, up to 20 seconds, at 360p, 540p, 720p or 1080p, and accepts up to 64 keyframes. Sume does not list a Luma model, so the nearest Sume route for editing an existing clip is gemini-omni-flash-1.1 through the Video Router video_url field, priced at $0.125 per second at 720p.

Luma's published limits

These come from Luma's own pages. Ray 3.2 was introduced on 2026-06-09 and lists clips up to 20 seconds at 1080p and up to 16 keyframes for generation.

What Sume's edit route does

Sume's Video Router documents one edit model. You send video_url and a prompt; resolution is optional and defaults to 720p; aspect_ratio and duration are not accepted for the edit. The source is the edit source, not a reference, so it cannot be combined with image_url, end_image_url or reference_*_urls. Native audio is always on.

Where they differ

Luma accepts a source up to 20 seconds and up to 64 keyframes to steer the result. The Sume page does not state a maximum source length for the edit, and it has no keyframe input: you steer with the prompt alone. If your job needs per-keyframe control over a long clip, Sume's edit route does not replace Luma's.

If your job is a plain instruction edit, such as swapping a product or changing a background, the Omni route fits and the price is simple to compute: seconds of source times the per-second rate. The Omni edit price page shows where that model ranks on the editing board.

A cost example

A 12 second source clip edited at 720p through the Omni route costs 12 x $0.125 = $1.50. At 1080p it is 12 x $0.1875 = $2.25. Sume reserves the amount at submit using the length you give, and the final charge follows the source length.

If the clip is longer than the ten seconds Omni generates elsewhere, check the edit limits in the API reference before you send it, since this page does not state a source-length maximum for the edit. Where Luma's 64 keyframes are the point, buy that job from Luma.

What to send

Keep the source clip under the limit you have checked, host it at a public https URL, and write the instruction as a single change. If you need many changes, run them as separate edits so you can see which one broke the result.