Should a Shorts season use sume/auto or a pinned video model?
Pin one model per season so episodes look alike. Use sume/auto for pilots and one-offs where a consistent look is not required.

Pin one model for a season. sume/auto lets Sume select the model for each request, which is convenient and not a promise that episode 5 looks like episode 4.
Use auto for pilots, tests and one-off promos, and a named model for anything a viewer will watch in order.
What the docs say
The Videos docs list model as either a model id such as seedance-2.5 or sume/auto. Limits differ by model: Wan 3.0 takes 2 to 30 seconds, Seedance 2.5 takes 4 to 30, Omni Flash takes 3 to 10. A request that works on one model can be rejected on another, which is a second reason to pin.
The catalog route GET /v1/catalog lists the supported resolutions, aspect ratios and durations for each model before you submit.
| Case | Use | Why |
|---|---|---|
| Pilot or test | sume/auto | Fast, no commitment |
| Season with a fixed look | Pinned model | Same model every episode |
| Duration over 10 s | Wan 3.0 or Seedance 2.5 | Omni Flash stops at 10 s |
| Native stereo audio | Check the catalog | generate_audio per model |
A pin that stays pinned
Write the model id in one config file for the whole season and read it from there in every request. When a new model arrives, start a new season on it instead of swapping mid-way.
Pinning also makes costs predictable: one rate, one duration range. See references for what carries the look and no seed for why a model swap cannot be undone by a number.
- One model id per season.
- Test a new model on a spin-off first.
- Record the model id on every episode record.
Recording the pin
Add the model id to the filename or the metadata of every episode. A year from now, you will want to know which episodes came from which model, especially if one is retired from the catalog.
If a pinned model is retired, finish the season on the replacement and note the break; do not pretend the look is continuous.
Sources
Related posts
More in Models
- Sume TTS Router: send sonic-3.6, sonic-latest or sonic-preview?
The Sume TTS Router has five Sonic ids. sonic-3.6 is stable, sonic-latest resolves to it, and sonic-preview is a beta that rejects pro voice clones.
- Swap the lead in a finished AI episode: H3 Max Recast for 20 s
H3 Max Recast replaces the people in a 5-30 s source with 1-4 photos, keeping motion and sound. A 20 s source is $7.50 at 768p and $11.25 at 1080p on Sume.
- MiniMax H3 Max on Sume: video, lip-sync and recast, which id to call
Three Sume ids carry the MiniMax H3 Max name: minimax-h3-max for video, a lip-sync route and h3-max-recast. What each takes, its window and its rate.
- Two reference images, one clip: Omni's cat-and-yarn pattern on Sume
Google's docs show two images, a cat and yarn, producing one video. Here is the Sume request with IMAGE_REF tokens and what changes with a brand product.
Written by Sume