Vimeo pixel aspect ratio 1:1: setsar in a video filter
Vimeo recommends square pixels (1:1). Sume's video filter allowlist includes setsar, setdar and scale, so a filtergraph can set the sample aspect ratio.
Vimeo recommends a pixel aspect ratio of 1:1, or square pixels. On Sume you can send a filtergraph to POST /v1/video-filter containing setsar, which is on the server's allowlist alongside setdar and scale. Check the graph first with the free /v1/video-filter/check route.
Vimeo's guidance is from its compression guidelines. The Sume limits come from Video filter and the allowlist in packages/timeline-compiler/src/filter.ts, read 2026-10-01.
What does Vimeo say about pixel shape?
Under resolution, the page recommends compressing with a pixel aspect ratio of 1:1, then lists common sizes such as 1280 x 720 and 1920 x 1080. Square pixels mean the stored width and height already describe the picture shape, with no display stretch.
Which filters on the allowlist matter here?
| Filter | On the allowlist | Use for 1:1 |
|---|---|---|
setsar | Yes | Set the sample aspect ratio |
setdar | Yes | Set the display aspect ratio |
scale | Yes | Change the pixel dimensions |
crop | Yes | Cut the frame to a shape |
How do I send it?
The filtergraph is filters-only, max 2048 characters and 32 named filters, with no inputs or stream specifiers. The server wraps it for you. The clip must already be a media.sume.com file and the source cap is 300 seconds. Replace /v1/video-filter/check with /v1/video-filter (and add an Idempotency-Key) to encode.
curl -X POST https://api.sume.com/v1/video-filter/check \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"video_url": "https://media.sume.com/artifacts/artf_demo/anamorphic.mp4",
"filtergraph": "scale=1920:1080,setsar=1"
}'What will this not fix?
Scaling to a new width and height changes the picture's shape if the source ratio differs, so choose dimensions that keep the intended display shape. The docs do not describe how a clip's existing pixel aspect ratio is reported back, so check the result in a probe tool. Fields like vf, codec or crf are rejected; see ffmpeg fields rejected.
Sources
Related posts
More in Developers
- VS Code extension icon: 128x128 minimum, 256x256 for retina
VS Code wants an extension icon of at least 128x128, with 256x256 for retina displays. Generate 1024x1024 with GPT Image 2.5 on Sume and downscale to 256.
- Wan 3.0 at 30 fps, HappyHorse at 24: set Timeline output.fps
Alibaba lists Wan 3.0 at 30 fps and HappyHorse 1.1 at 24 fps. Joined in Sume's Timeline, a differing output.fps resamples sources and warns; omit it to match.
- Wan 3.0 smart duration and adaptive ratio vs Sume's explicit fields
QwenCloud lists smart duration and adaptive aspect ratio for Wan 3.0. On Sume you send an integer duration and an aspect_ratio the model supports.
- Wan 3.0 sound toggle vs Sume generate_audio for Wan
Wan 3.0 lists a sound toggle at QwenCloud. On Sume, generate_audio defaults to the model's audio capability and some models reject false.
Written by Sume