Vidu S2-Editing: live stream edits vs a Sume Omni clip edit

Vidu S2-Editing works on a live feed; Sume's edit works on a file. With Sume you send one finished clip and a prompt describing the change to gemini-omni-flash-1.1, and you get a new clip back from an async job, not a stream.

Vidu facts are from its update log; Sume facts are from Video Router and Webhooks, read 2026-09-30.

What does Vidu S2-Editing do?

The September 15, 2026 entry describes "Vidu S2-Editing: Real-Time Editing Model", which uses style, clothing, character and background reference images to edit an incoming video stream in real time. The page gives no request schema, so any integration detail has to come from Vidu.

How does a Sume edit work?

The video_to_video (edit) capability takes a video_url. The prompt describes the edit, resolution is optional (default 720p), and there is no aspect_ratio or duration. video_url is the edit source, not a reference, so it cannot be combined with image_url, end_image_url or reference_*_urls.

Native audio is always on; generate_audio: false is rejected. Send the request to POST /v1/video-router/generate with an Idempotency-Key.

Which parts of the Vidu feature have no Sume equivalent?

How do I know when the edit finished?

Poll the job or take a webhook. The docs list job.completed as "The job completed and a public result is available", plus job.failed and job.canceled. Nothing is sent while the edit is still running.

What should I check before editing a clip?

Uploaded-video edits have an availability limit covered in Gemini Omni edit of an uploaded video: EEA, UK and Switzerland; read it first. For prompt wording, see Gemini Omni video edit prompts.