Gemini Omni Flash 1.1 generate_audio false: why the API refuses
gemini-omni-flash-1.1 on Sume always makes native synced audio, so generate_audio: false is rejected. Replace the sound in a Timeline instead.
Gemini Omni Flash 1.1 on Sume has native synced audio that is always on, and the API rejects generate_audio: false. If you need a silent clip, generate it and remove the sound afterwards instead of asking for no audio.
Both facts are stated in the Video Router docs and video generation docs, read 2026-10-06. Other models differ: Kling 3 Pro lists a lower rate with audio off.
Which catalog models let me turn audio off?
Read generate_audio for each model from GET /v1/videos/models; it says whether the model can produce audio. Kling v3 Pro is the one whose price depends on it, per Sume's rate card:
| Audio | 10-second clip |
|---|---|
| On | $2.10 |
| Off | $1.40 |
How do I get a silent version?
Render the clip through a Timeline that does not include the clip's audio, or add your own voiceover or music bed, which replaces the generated sound.
Sources
Related posts
More in Models
- Gemini Omni Flash 1.1 reference-to-video: IMAGE_REF tags
Use up to 10 reference images and 3 short reference videos in one Gemini Omni Flash 1.1 request on Sume, and point at them with <IMAGE_REF_0> and <VIDEO_REF_0>.
- Edit an existing video with Gemini Omni Flash 1.1 over an API
Send video_url and an instruction to gemini-omni-flash-1.1 on Sume to edit a clip: no duration or aspect ratio, resolution optional, native audio on.
- Gemini Omni scene extension: app, Flow, API or Sume?
Google's launch post lists four places Omni 1.1 Flash runs. Scene extension is not in all of them, and Sume's router does not expose it. Where to go instead.
- gpt-image-1 retires December 1: scan your repo, move to gpt-image-2.5
OpenAI's deprecations page lists gpt-image-1, 1.5 and 1-mini for December 1, 2026. A Python scan finds the ids, and Sume serves openai/gpt-image-2.5.
Written by Sume