Veo 3.1 lists 4, 6 or 8 seconds; Omni on Sume runs 3 to 10

Google's Veo 3.1 page lists lengths of 4, 6 and 8 seconds and resolutions of 720p, 1080p and 4K (read 2026-10-09). A 5-second clip is not one of those lengths. On Sume, gemini-omni-flash-1.1 takes 3 to 10 seconds at 360p, 720p, 1080p and 4K, billed per output second.

What does Google list for Veo 3.1 at 1080p?

Rates come from Google's pricing page. Lite offers 720p and 1080p only, according to the Veo page.

What does the same shot cost on Sume at 1080p?

Sume bills Omni at the provider list price times 1.25 per output second. At 1080p that is $0.1875 a second, so you pay for the seconds you ask for.

When is the fixed 8 seconds a problem?

Ad cut-downs, 5-second hooks and product loops rarely want 8 seconds. With Veo's listed lengths you would generate 6 or 8 and trim. With Omni on Sume you ask for 5, pay for 5, and stay inside the 9:16 or 16:9 frame the model supports. Google also lists 4K for Omni on its own page (read 2026-10-09), and Sume bills 4K at $0.375 a second, so a 5-second 4K clip is $1.875.

What should you check first?

• Run GET /v1/videos/models and read supported_durations for the model you pin.
• Send resolution explicitly. Omni defaults to 720p.
• Remember Sume does not list a Veo id, so this is a comparison, not a swap you can run in the same API.