Slide deck title loop: a 10-second Omni clip for $1.88

Make a looping 16:9 title background for a presentation: Omni Flash, the same image as first and last frame, 10 seconds at 1080p for $1.875 on Sume.

5 min readSume
All posts

For a presentation title slide, generate a 10-second 16:9 clip with Gemini Omni Flash 1.1, using the same still as the first frame and the last frame so the end meets the start. On Sume that is image_url plus end_image_url, and 1080p costs $0.1875 per second, $1.875 for the 10 seconds. Google's Omni page, read 2026-10-08, lists interpolation between a first and last frame as a supported mode and 10 seconds as the top of the 3 to 10 second range.

Google's Omni page labels its 1080p and 4K outputs as upscaled, so for a slide behind text, 1080p is the sensible ceiling.

The request

Pick a still with open space for the title. Describe a slow, repeating motion: drifting particles, a light sweep or a gentle camera drift. Avoid anything with a clear beginning and end, since the loop has to close on the same frame.

curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: deck-title-loop-01" \
  -d '{
    "model": "gemini-omni-flash-1.1",
    "prompt": "Slow drifting light particles over a dark blue gradient, locked camera, returns to the first frame, no dialogue",
    "image_url": "https://example.com/title-still.png",
    "end_image_url": "https://example.com/title-still.png",
    "duration": 10,
    "resolution": "1080p",
    "aspect_ratio": "16:9",
    "mode": "async"
  }'

Price by resolution for a 10-second loop

Sume bills Google's list rate times 1.25 for each output second.

10-second Omni loop, Sume rates read 2026-10-08 against Google direct
ResolutionSume per secondSume 10 secondsGoogle direct note
360p$0.0375$0.375Draft check
720p$0.125$1.25About $0.10 per second on Google's pricing page
1080p$0.1875$1.875Upscaled
4K$0.375$3.75Upscaled

Two things that catch people out

Omni always generates a sound track, and the API rejects generate_audio: false. A slide loop usually wants silence, so plan to mute the track in your slide software or strip it in a later step; see the related post on removing the audio.

The loop is only as seamless as the model's last frame is close to the first. Check the join by playing the clip twice end to end. If there is a visible jump, re-run with a calmer prompt, or fix it in an editor with a short cross-fade; the same file at 360p costs $0.375 per try, so test the motion there first.

Checking the loop and the slide

Play the clip on repeat in the slide program before you present. A small jump at the loop point is common; trim two frames at the end if needed, and note that Sume's video trim returns a new MP4. Keep the area where the title sits visually quiet, because slide text needs contrast.

Presenters often run a laptop with sound on. Omni always generates audio, so add No dialogue, silent room tone to the prompt and set the clip to mute in the slide app.

Submit with an Idempotency-Key header so a retry after a dropped connection returns the original job instead of a second charge; the same key with a different payload returns 409. Then poll GET /v1/jobs/:id/status and fetch GET /v1/jobs/:id/result when it finishes.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume