Luma Ray3.2 or Kling 3 for a start-and-end-frame shot? Sume's option

If your shot only needs a start image and an end image, you do not need Luma Ray3.2's 16 keyframes. On Sume, kling-3 takes a first frame and a last frame for 4 to 15 seconds at 720p or 1080p, and wan-3.0, seedance-2.5, minimax-h3-max and gemini-omni-flash-1.1 do the same.

Luma Ray3.2 itself is not in the Sume catalog, so you cannot call it through Sume. This post compares what Luma documents with what Sume rows accept, so you can decide whether a two-frame shot is enough.

What Luma says

Luma's Ray3.2 announcement lists up to 16 keyframes per clip, clips up to 20 seconds at 1080p, native HDR generation, 16-bit EXR export, and an API for developers (read 2026-10-07). The page gives no price, and this post does not quote one.

Prices for a two-frame, ten-second shot

Sume sells at the provider list per second times 1.25, rounded up to whole cents.

Doing a multi-keyframe shot anyway

If the shot needs a middle beat, chain two jobs: generate A to B, take the last frame of the clip as the first frame of B to C, and join the clips on a timeline. That costs two jobs and may show a seam at the cut. Hold B fixed by using the same image as the end of the first job and the start of the second.

Sume does not offer keyframe curves, HDR output or EXR export, so a pipeline that needs those should call Luma directly.

• Two frames, 4 to 15 seconds, optional silence: Kling 3.
• Two frames, 2 to 30 seconds: Wan 3.0.
• More than two frames, HDR or EXR: not on Sume.

Request

A Kling job with both frames:

{
  "model": "kling-3",
  "prompt": "The product rotates from front to back under soft light",
  "duration": 8,
  "resolution": "1080p",
  "frame_images": [
    {"type": "image_url", "image_url": {"url": "https://example.com/front.png"}, "frame_type": "first_frame"},
    {"type": "image_url", "image_url": {"url": "https://example.com/back.png"}, "frame_type": "last_frame"}
  ]
}