Omni 1.1 Flash start and end frame API on Sume

On Sume, give gemini-omni-flash-1.1 a start frame as image_url and an end frame as end_image_url through the Video Router. Google says Omni 1.1 generates continuous video between two keyframes, which suits camera orbits, zoom transitions and seamless loops; to loop, use the same image for both.

Google's claim is from its Omni 1.1 Flash developer post. Sume's request shapes are from Video Router and Video generation, read 2026-10-01.

What does Google say about start and end frames?

The post says you can specify the starting and ending frames of a shot to get smooth transitions and camera movements, and names complex orbits, zoom transitions and seamless looping clips as use cases. Its examples ask for "one continuous shot, no jump cuts", and one ends on a frame that matches the scene from the beginning.

Which Sume fields carry the two frames?

Two surfaces exist, and they differ. In the Video Router, the image_to_video capability takes image_url plus an optional end_image_url. In the generic Videos API, frame_images entries each carry a frame_type of first_frame or last_frame, and each model advertises what it accepts in supported_frame_images. For Omni, follow the Video Router row and check the catalog before assuming a field.

If you send both frame_images and input_references to the Videos API, frame_images takes precedence and the request is image-to-video.

What limits apply to the clip itself?

How do I make a looping clip?

Send the same image as both the start and end frame, describe a motion that returns to its starting pose in the prompt, and keep the duration inside 3–10 seconds. Whether the loop looks seamless depends on the prompt and image; Sume's docs make no promise about it. For the neighboring interpolation topic see Gemini Omni first and last frame interpolation.