Edit an old Sora download with Gemini Omni: trim to 10 s first

A Sora clip you saved before the shutdown can be edited with Gemini Omni Flash 1.1, but Google documents a 10 second limit on uploaded edit sources, and Sora clips can be 16 or 20 seconds long. Cut the clip to 10 seconds or less first, then send it as video_url on a Sume Video Router request with a short instruction ending in "Keep everything else the same."

OpenAI's guide says the Sora 2 models and Videos API were shut down on September 24, 2026, so the Sora-side remix and edit endpoints no longer exist; an edit now has to be a new request elsewhere. Google's Omni documentation (read 2026-10-03) says input video for editing and extending should be 10 seconds or less.

Step 1: get the clip onto Sume-hosted media

Sume's trim surface only reads a clip already on media.sume.com, and the docs say there is no open-internet fetch: import first with POST /v1/media-imports. The same is true for Timeline 1.0 and Video inspect. The Video Router itself takes a public HTTPS video_url, but you need the Sume-hosted copy to trim.

Step 2: trim to the part you want to change

Video trim takes video_url, a start, and exactly one of end or duration, and returns a new MP4 artifact holding only that range. The source is untouched. Its public price in the docs is $0.02 per job, and it runs on ffmpeg in the worker, so it does no model inference. The default precision is exact, a frame-accurate re-encode, and audio defaults to keep.

Pick the 10 second window that contains the thing you want to change. If the change runs the length of a 20 second clip, trim two windows and edit each separately; the pieces can be joined again with the timeline.

curl -X POST https://api.sume.com/v1/video-trim \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: sora-trim-001" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/artf_demo/sora-saved.mp4",
    "start": 4,
    "duration": 10
  }'

Step 3: send the trimmed clip as the edit source

Omni's edit mode on Sume is selected by the shape of the request: video_url plus a prompt that describes the edit. It cannot be combined with image_url, end_image_url or any reference_*_urls, and it takes no aspect_ratio or duration, because the output keeps the source framing. resolution is optional and defaults to 720p. Native audio is always on.

Google's guide says simple prompts work best for edits and that overly descriptive prompts can cause unintended changes. Name one change and then say what to keep.

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: sora-edit-001" \
  -d '{
    "model": "gemini-omni-flash-1.1",
    "prompt": "Change the red jacket to a yellow raincoat. Keep everything else the same.",
    "video_url": "https://media.sume.com/artifacts/artf_demo/trimmed.mp4",
    "resolution": "720p",
    "mode": "async"
  }'

Things to know before you spend

Google lists uploaded-video editing as unavailable in the EEA, Switzerland and the United Kingdom, and Omni outputs carry a SynthID watermark. The edit result is a fresh render, so it will not be pixel-identical to the Sora source outside the edited region; compare stills before you replace a published file. Sume bills edits as list times 1.25 per output second by resolution, and the Video Router docs describe the edit mode in full.