Luma Ray3.2 length by frame rate (24/30/60 fps) and Sume's fps

Luma's Ray3.2 page says Modify Video can take up to 20 seconds, depending on frame rate: up to 20 seconds at 24 fps, 15 seconds at 30 fps and 7 seconds at 60 fps. Sume does not offer a Luma id, so the practical question is how to choose an output frame rate for clips you do make on Sume. The video trim and timeline tools can conform an output to 24, 25, 30 or 60 fps.

The Luma figures are from Luma's Ray page, read on 2026-10-03. Sume's conform options are in the video trim docs and timeline compose docs.

The frame-rate-to-length rule

The three Luma figures follow one pattern: the budget is a total frame count. 24 fps times 20 seconds is 480 frames; 30 fps times 15 seconds is 450; 60 fps times 7 seconds is 420. They are not exactly equal, so treat the page's figures as stated limits, not a formula.

On Sume the equivalent decision belongs to the delivery platform, not the model. Pick 24 for cinematic, 25 for PAL regions, 30 for most social, 60 for fast motion.

Conforming a Sume clip

Frame rate is set on the way out. In video trim, the output object takes width, height and fps of 24, 25, 30 or 60, and works on exact trims only. In a timeline, output.fps sets the render rate; if it differs from a clip's own rate, the render warns output_fps_resamples_sources, meaning clips are resampled rather than rejected.

Resampling does not add real frames: going from 24 to 60 repeats or blends frames, so motion does not look smoother. If 60 fps matters, it has to come from the source.

A note on edits

Luma's Modify Video is an edit of existing footage. On Sume the edit route is Gemini Omni Flash 1.1 with a video_url, which takes a prompt for the change and has its own length limits in the docs. Compare those on the model's page before you plan a long edit, rather than assuming Luma's 20 seconds carries across.

For long sequences, cut the source at the scene boundary, edit each piece, and join them with the timeline tool.