Omni Flash edit or regenerate: when video_url beats a new prompt
Edit with video_url to change one thing; regenerate when the motion is wrong. A 6-second edit costs $0.75 at 720p on Sume.

Edit with video_url when the shot is right and one thing is wrong: an object, a colour, a background detail. Regenerate with a new prompt when the motion, framing or pacing is wrong, because an edit keeps the source clip's timing and framing.
On Sume the edit runs on gemini-omni-flash-1.1 through the Video Router. A 6-second edit costs $0.75 at 720p and $1.13 at 1080p.
What an edit does
The edit request sends a prompt and the source video_url. The source clip sets the output, so the API sends no aspect_ratio and no duration to the provider, and a 400 comes back if you give an aspect ratio. If you send a duration with video_url, it is only the reserve-estimate hint, which defaults to 8 seconds.
Google's Gemini API video page describes Omni Flash as a model for video generation and conversational video editing with multi-turn edits (read 2026-10-07). Sume does not expose the multi-turn or extend interaction id; each edit is a single job.
{
"model": "gemini-omni-flash-1.1",
"prompt": "Change the red jacket to dark green. Keep everything else the same.",
"video_url": "https://example.com/street.mp4",
"resolution": "720p"
}Edit or regenerate
Use the table to decide before you spend. Both paths are billed at the same per-second rate for the resolution you choose.
| Situation | Better path | Why |
|---|---|---|
| One object or colour is wrong | Edit | Keeps motion, camera and timing |
| Camera move is wrong | Regenerate | The source camera is kept by an edit |
| Need a different length | Regenerate | Edit length follows the source |
| Need a different aspect ratio | Regenerate | Edit takes no aspect_ratio |
| Subject must change entirely | Regenerate | Edits keep the original scene |
Cost of a try
Because there is no seed, every run is a new take, edit or not. Budget for two or three tries. Prices are provider list per second times 1.25, rounded up to whole cents, on the length of the source clip.
| Source length | 720p | 1080p |
|---|---|---|
| 4 seconds | $0.50 | $0.75 |
| 6 seconds | $0.75 | $1.13 |
| 8 seconds | $1.00 | $1.50 |
| 10 seconds | $1.25 | $1.88 |
Limits
The edit path always produces synced audio, so generate_audio: false and bitrate_mode are 400s, and reference_audio_urls is also rejected. The source clip cannot be combined with image_url, end_image_url or reference_*_urls. To use a clip as conditioning for a new generation instead, send it in reference_video_urls, which accepts up to three clips of at most three seconds each on this model.
- Edit is a Video Router field, not part of the
/v1/videosbody. - Default edit resolution is 720p; ask for 1080p when you need it.
- Trim long sources first; the output length follows the source.
Sources
Related posts
More in Use cases
- Character still first, then Kling 3.0 motion control
Kling 3.0 motion control on Sume needs a still and a motion video. Make and approve the still first, then spend the $0.1575-a-second job on it.
- Why a vertical-only YouTube ad may not serve, and the 16:9 fix
Google says campaigns with only vertical videos may not serve in YouTube in-feed. Render a 16:9 twin of your 9:16 ad from one audio spine with Sume Timeline.
- Does vertical video lift YouTube Shorts ads? Google's 2024 figures
Google's help page cites 35%, 40% and 45% gains for 9:16 video on Shorts. Read what each figure measures, then render the vertical cut with Sume Timeline.
- Business Profile video takes 24-48 hours to show: plan the clip early
Google says Business Profile photos and videos can take 24 to 48 hours to appear; clips run up to 30 seconds and 75 MB at 720p or higher. A restaurant plan.
Written by Sume