Vidu 540p has no Sume value: map Vidu resolution names
Vidu Q4 Preview offers 540p, 720p, 1080p, 2K and 4K. Sume's documented values are 480p, 720p, 768p, 1080p, 1K, 2K and 4K, per model. A lookup that fails loudly.

Vidu Q4 Preview lists 540p, 720p, 1080p, 2K and 4K, with 720p as the default. Sume's documented resolution values are 480p, 720p, 768p, 1080p, 1K, 2K and 4K, and each model accepts only a subset. 540p is not in the Sume list, so a request that sends it fails. Look up the supported values per model and choose on purpose.
Which names overlap?
Only some Vidu names exist on Sume.
| Vidu name | In the Sume list? | Note |
|---|---|---|
| 540p | no | nearest documented values are 480p and 720p |
| 720p | yes | Vidu default; Sume wan-3.0 and seedance-2.5 accept it |
| 1080p | yes | Sume wan-3.0 and seedance-2.5 accept it |
| 2K | yes, per model | check supported_resolutions |
| 4K | yes, per model | check supported_resolutions |
How do you pick the replacement for 540p?
Choose by purpose. For a cheap draft take 480p; for a keeper take 720p. On wan-3.0 fal's page lists $0.05 a second at 480p and $0.10 at 720p (fal, read 2026-10-09), which Sume bills at 1.25 times, $0.0625 and $0.125. A 5-second draft is $0.3125, a 5-second keeper $0.625.
What does the guard look like?
Fill supported from supported_resolutions in GET /v1/videos/models at run time so the guard follows catalog changes.
def resolution_for(name: str, supported) -> str:
if name in supported:
return name
raise ValueError(f"{name} not supported; choose from {sorted(supported)}")
wan = ["480p", "720p", "1080p"]
print(resolution_for("720p", wan))
try:
resolution_for("540p", wan)
except ValueError as e:
print(e)Sources
Related posts
More in Developers
- Vidu 'Authorization: Token' vs Sume 'Bearer': one HTTP client
Vidu wants 'Authorization: Token <key>'; Alibaba Model Studio and Sume want 'Bearer <key>'. A small header helper for a ported client.
- Vidu is_rec and Wan prompt_extend: prompt rewrite vs Sume
Vidu's is_rec and Alibaba's prompt_extend can rewrite your prompt. Sume's documented video fields have no such switch. How to drop them and compare results.
- Vidu's payload pass-through vs Sume: where to keep your order id
Vidu lets you send a payload string that comes back untouched. Sume's video request has no such field; use an Idempotency-Key and your own job table instead.
- Vidu Q4 base64 images and a 20 MB body vs Sume's HTTPS URLs
Vidu accepts base64 images with a 20 MB request body cap. Sume wants a public HTTPS URL. Base64 math, and a small check before you submit.
Written by Sume