Swap the seasonal dish in a restaurant clip with Omni Flash edit

To change the dish in a restaurant clip you already have, send the clip to Gemini Omni Flash 1.1 in edit mode with an instruction such as 'replace the pasta with a roast turkey plate, keep everything else the same'. On Sume that is video_to_video through the Video Router, billed per output second at the 720p rate of $0.125 by default.

One strong source clip becomes a set of seasonal specials: pumpkin soup this week, a roast next week, a dessert for the holiday party.

How the edit call works

The Video Router docs list video_to_video (edit) for gemini-omni-flash-1.1: send video_url, put the instructions in the prompt, and resolution is optional with a default of 720p. There is no aspect_ratio or duration field in edit mode, and video_url is the edit source, not a reference. You cannot send it together with image_url, end_image_url or reference_*_urls. The docs example replaces a bottle with an apple and tells the model to keep everything else the same.

Google's launch post (read 2026-10-05) describes scene extension, first and last frame control and a draft mode for Omni 1.1 Flash. It lists the product in AI Studio, the Gemini API, Flow and the Gemini app. Check the Sume catalog for what Sume exposes, as the Sume docs are the ones that apply to your call.

What a weekly special costs

Edit billing is per output second, and the output follows the source length. Sume bills the provider list times 1.25 as a function of the resolution.

Weekly arithmetic

A weekly special for one location at 8 seconds and 720p is $1.00, so a month of four specials is $4.00. For a group with ten locations running one special each week, that is $10 a week for the edits. Draft at 360p, then finish at 720p.

I estimate those from the rate and the source length. The edit endpoint does not take a duration, so the length you pay for is the length of the source you send. Trim the source before you edit if it has dead air at the end.

Write the edit as a swap

Write the instruction as a swap with a preservation clause. 'Replace the bowl of soup with a slice of pumpkin pie on the same plate. Keep the table, the hand and the lighting unchanged.' Then look at the first and the last second, where an edit model is likeliest to wander.

Native audio is always on for this model. If the source clip had a kitchen sound bed, check that the edited clip still has one that matches the new dish, or replace it with a licensed track. The docs for the model reject generate_audio: false, so you cannot turn it off at the request level.

Do not put a price on the plate by prompt. If the special has a price or a booking line, add it as a caption or an overlay after the edit, since the text of a price should come from your system and not from a model.

Where not to use it

This works for a promo with food as the hero. It does not change your menu photos for delivery platforms, which often have their own rules about edited images. Check the platform's own requirements before you upload an edited photo or clip as a menu image.

A repeatable weekly plan

A short plan for a restaurant owner. Film one clean 8-second clip of a plate on the pass, steady camera, good light, no text. Keep it as the master. Each week, write one edit instruction, run it at 360p, look at it, and then run it at 720p for the post. The master never changes, so the clips share a look, and the dish is the only news.

The same master also works for a group. Ten locations can each have their own special while the clip, the camera move and the plate stay the same. Put the location name and the price in a caption or in the post text, not in the model's output.

Keep a record of each instruction next to the output URL. After the holidays you will know which swap wording produced a clean result and which one needed a retake, and next year's batch starts from the good ones.