Models
The models behind Sume's video, image, speech, and music endpoints: ids, clip lengths, resolutions, aspect ratios, audio, references, and migration.

FLUX 3 vs FLUX 2: which one you can call on Sume today
FLUX 3 vs FLUX 2 for image work: BFL's notes start FLUX 3 with video, and Sume's image catalog serves FLUX.2 Pro and Flex. What that means for stills.

FLUX 3 video 20-second clips: what Sume's video API offers
FLUX 3 Video makes up to 20 s clips at 1920x1088. Sume does not list it, but seedance-2.5 and wan-3.0 accept 20 s requests. Durations by model.

Gap or click when joining audio files: use wav, not mp3
Sume's Timeline audio joins up to 20 Sume-hosted parts with no silence at the seams. Its docs say to keep wav, because mp3 adds padding at every edge.

Gemini Live Avatar vs a video avatar API: live or rendered?
Gemini 3.8 Live Avatar streams a lip-synced face in a conversation. Sume's avatar video renders a finished clip from a script. Which job needs which.

Gemini Live Avatar: 97 languages and SynthID, explained
Google says Gemini 3.8 Live Avatar covers 97 languages and adds SynthID to audio and video. What each claim covers, and what it says about other avatar tools.

Gemini Omni 1.1 Flash 360p drafts: what a cheap preview costs
Gemini Omni Flash 1.1 can render 360p previews. On Sume a 360p second is billed at 30% of a 720p second, so drafts cost less than finals.

Gemini Omni Flash 4K: clip length, upscaling and price
Gemini Omni Flash 1.1 renders 4K clips of 3 to 10 seconds on Sume, and Google labels its 4K output upscaled. Length versus Veo 3.1, plus cost.

Gemini Omni Flash prompt guide: one shot, audio, text
Google's Omni Flash prompt tips: ask for a single continuous shot, put negatives in the prompt, describe the audio, spell out on-screen text. Plus a Sume call.

Gemini Omni Flash vs Veo 3.1: which does Google recommend when
Google's video page names Gemini Omni Flash the default, Veo 3.1 for scene extension, last-frame control or legacy pipelines. Facts side by side, plus Sume ids.

Gemini Omni prompt timecodes: [0-3s] and scene cuts
Gemini Omni Flash takes timing in plain words or a [0-3s] timecode syntax, so you can script cuts inside one clip. Google's examples and a 10-second Sume call.

Gemini Omni video edit prompts that keep everything else the same
Google says short prompts work best when you edit a video with Gemini Omni Flash, and to add Keep everything else the same. Examples, limits and a Sume call.

Gemini Omni reference video: is the audio used? No
Gemini Omni Flash accepts video references but not audio: Google says audio in a reference clip is ignored. Limits, Sume's fields, and models that take audio.

Does Gemini Omni video have a SynthID watermark?
Google says all Gemini Omni Flash videos include an invisible SynthID watermark. What that means for API clips, YouTube disclosure, and what Sume's docs say.

Google Flow video length: 4 to 10 seconds by model
Google Flow makes 4, 6 and 8 second clips with Veo 3.1 and 4 to 10 seconds with Gemini Omni Flash 1.1. Length by model and mode, from Google's help page.

GPT Image 2.5 Flare vs Sunburst: what each model page says
OpenAI calls Flare its model for everyday image generation and Sunburst its most capable for generation and editing. What each page lists, and both ids on Sume.

GPT Image 2.5 quality levels: low, medium, high, xhigh, max and auto
GPT Image 2.5 has six quality values: auto, low, medium, high, xhigh and max. What each does to price on Sume and which one runs when you send nothing.

GPT Image 2.5 release date and model ids: Flare and Sunburst
OpenAI's GPT-Image-2.5 Flare and Sunburst carry the snapshot date 2026-09-08. The model ids, dated snapshots, and how Sume names the same two models.

GPT Image 2.5 resolution: the size rules and the 4K ceiling
GPT Image 2.5 takes custom sizes: both edges a multiple of 16, longest edge 3840, 655,360 to 8,294,400 pixels. What that means for 1080p, 1440p and 4K.

Grok Imagine image API: the x-ai/grok-image id on Sume
Sume lists Grok Imagine as x-ai/grok-image on its image API: thirteen aspect ratios (no 4:5), one reference image for edits, and a $0.025 price line per image.

Grok Imagine aspect ratio: 21:9 and 5:2 on xAI vs Sume
xAI added 21:9 and 5:2 to Grok Imagine image on Aug 28. Which ratios Sume's grok-image accepts, what the 400 looks like, and a call that works.

Grok Imagine Video 1.5 reference images API: xAI vs Sume
xAI's API takes up to seven reference images, text-to-video and 1080p for Grok Imagine Video 1.5. Sume's API reference lists it as first-frame image-to-video.

How much VRAM for AI video generation? Numbers from model cards
From 14 GB to 80 GB: the VRAM figures Tencent, Wan-AI and Genmo publish for their open video models, and what each number was measured with.

HunyuanImage 3.0 API: open weights, no listed Sume model
HunyuanImage 3.0 is an 80B-parameter open-weights image model from Tencent. Sume's image docs do not list it; here is what the card says and the hosted route.

HunyuanVideo 1.5 low VRAM: 14 GB with offloading
Tencent's HunyuanVideo-1.5 card lists 14 GB as the minimum GPU memory with offloading on. The OOM settings and step-distilled option it names.

HunyuanVideo API: is there a hosted one, or only weights?
HunyuanVideo is published as downloadable weights. Sume's docs list no HunyuanVideo API, so here is what running it takes and the listed video ids.

Ideogram 4.0 API: request shape and what Sume lists
Ideogram 4.0 has its own endpoint with text_prompt or json_prompt. Sume's image catalog lists Ideogram V3 only; here is how the two differ.

Imagen 4 API shut down in the Gemini API: what Sume's catalog lists
Google says Imagen is shut down in the Gemini API and points to Nano Banana. Sume's image catalog lists google/imagen-4-fast, imagen-4-ultra and Nano Banana ids

Kling 3 4K API: Kling's own tier and what Sume lists
Kling 3.0 lists 4K on Kling's own capability map, but Sume's kling-3 lists 720p and 1080p and prices no resolution tier. Sume's 4K route: gemini-omni-flash-1.1.

Kling 3 duration and aspect ratio limits: Kling's own vs Sume's
Kling's own map lists 3 to 15 seconds for Kling 3.0; Sume's kling-3 takes 4 to 15 seconds at 16:9, 9:16 or 1:1. Values outside the list are refused.

Kling 3 first and last frame API: request, limits and a gotcha
On Sume, kling-3 takes a first and optional last frame via frame_images, for 4-15 seconds. Send frame one in the shape you want; aspect_ratio is text-only.

Kling 3 lip sync with your own audio: what each API does
Kling lists lip sync driven by text or audio. Sume's kling-3 takes no audio input, only a generate_audio switch; models with audio references are listed.

Kling 3 native audio: what the on and off price difference is
On Sume, kling-3 costs $0.14 a second silent and $0.21 with audio. Audio is on unless you send generate_audio false, so the default is the higher price.

Kling 4.0 API: what Sume lists and what to use today
Kling 4.0 API availability could not be confirmed from Kling's own pages on 2026-09-29. Here is what Sume's docs list today for video, and where Kling appears.

Kling motion control API in Python: submit, poll, fetch
Call Kling 3.0 motion control from Python with requests: submit with an Idempotency-Key, poll the status URL until terminal, then fetch the result when ready.

Kling motion control camera movement and orientation
In Kling motion control, character orientation decides whether the camera follows the video or the image. What Kling says, and Sume's character_orientation.

Kling motion control face consistency: element binding
Kling 3.0 Motion Control keeps a face steady by binding a facial element to the character image. How it works, and what Sume's endpoint takes instead.

Kling motion control with multiple people in the video
Kling motion control animates one character. With two or more people in the reference, it uses the one with the largest share of the frame.

Kling motion control not working: causes and fixes
A short, cut-off or wrong-person Kling motion control result usually traces to the reference video. Kling's causes, and the errors Sume's endpoint returns.

Kling motion control prompt: what it can change
In Kling motion control the video supplies the movement and the prompt covers background and looks. Kling's examples, and Sume's 2,000-character prompt.

Kling motion control reference video requirements
Kling asks for one character in one continuous shot, 3 to 30 seconds, short edge 340 px or more. Which limits Sume's endpoint also enforces.

LTX 2 open source: what Lightricks released, and the license
LTX-2 is an audio-video model with open weights under the LTX-2 community license. What the Hugging Face cards list, and why Sume's catalog has no LTX.

Luma Ray 3.2 20 seconds 1080p: how Sume's catalog limits read
Luma says Ray3.2 makes up to 20 seconds at 1080p. In Sume's video docs, seedance-2.5 is the one model stated to accept 20 seconds at 1080p.

Luma Ray 3.2 API: 16 keyframes, and Sume's two-frame route
Luma says Ray3.2 takes up to 16 keyframes per clip. Sume lists no Luma model; chain its first and last frames to cover more key images.

Luma Ray3.2 modify: what is confirmed, and Sume's edit route
Luma's Ray3.2 notes list keyframes, 1080p, HDR and reframe but no quotable modify details. Sume's video edit route is gemini-omni-flash-1.1 with video_url.

Lyria 3 Pro or Lyria 3.5: which model id do I send?
Sume's Music Router accepts sume/music-auto, lyria-3.5 and lyria-3-pro. What each id does, how to pin one, and what Google lists for the models.

Lyria 3.5 API: model id, request and how to call it
Lyria 3.5 is in the Gemini API as lyria-3.5. Here is what Google's page says about it and how to call it from Sume with one music request.

AI music generator with vocals: Lyria 3.5 lyrics by API
Lyria 3.5 can sing. How to ask for vocals or an instrumental, steer lyrics with section tags, and read the lyrics back from a Sume music job.

Lyria 3.5 release date: where it is available
Google announced Lyria 3.5 in the Gemini app on 2026-09-04. Where Google says you can use it, and where Sume lists it.