Multimaster output sizes: repeat video trim with new width and height
For several deliverable sizes from one master, run Sume video trim once per size with output width and height 256 to 2160, fps 24/25/30/60, precision exact.

To get several sizes from one master, call POST /v1/video-trim once per deliverable with the same start and duration and a different output of width, height and fps. Width and height run 256 to 2160, and output works only with precision: "exact". Each call is a separate job and a separate new MP4.
Blackmagic's 21.1 announcement says the color page's multimaster trim feature can now override output sizing for each trim, for independent framing per aspect ratio. Sume does not drive that feature; the sizing rules here are from Video trim, read 2026-10-01. See also Resolve highlight edits driven by Claude.
What does the Resolve announcement say?
The announcement says that on the color page the multimaster trim feature now supports individual trim passes for Dolby Vision, HDR10+ and HDR Vivid, and that "output sizing can now be overridden for each trim, allowing independent framing for different aspect ratios." Separately, it says Resolve 21.1 supports integration with AI assistants such as Claude, Claude Code and ChatGPT Codex to "analyze projects, organize media, adjust settings and batch render". Sume video trim is not HDR trim passes; it only covers the per-size cut.
What does one deliverable request look like?
Only output changes between calls. Use a distinct Idempotency-Key per size, since each size is its own request.
for size in "1920 1080" "1080 1920" "1080 1080"; do
set -- $size
curl -X POST https://api.sume.com/v1/video-trim \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: master-cut-$1x$2" \
-d "{\"video_url\": \"https://media.sume.com/artifacts/artf_demo/master.mp4\",
\"start\": 0, \"duration\": 30,
\"output\": {\"width\": $1, \"height\": $2, \"fps\": 30}}"
doneWhat are the limits per size?
| Field | Value |
|---|---|
output.width / height | 256 to 2160 |
output.fps | 24, 25, 30 or 60; omit to inherit the source |
precision | exact (libx264, yuv420p); keyframe refuses output |
| Output length | 0.2 to 900 s |
Does it crop to the new aspect ratio?
The docs describe output as a conform and do not say how a different aspect ratio is fitted, so test one size and look at it. If you need explicit framing, crop first with video filter or place the clip on a Timeline with a fit mode; see one source, three aspect ratios.
What does it cost?
The docs list a public rate of $0.02 per job, so three sizes are three jobs. Confirm the live figure in GET /v1/catalog.
Sources
Related posts
More in Use cases
- Resolve 21.1 source viewer aspect ratio: check clips first
Resolve 21.1's source viewer keeps each clip's original aspect ratio. To check clips before conforming, Sume video inspect returns stills with width and height.
- Reuse one winning ad across a catalog: one edit job per SKU
To reuse a proven video ad for many products on Sume, send one edit job per SKU with its own Idempotency-Key, and submit in waves so queue_full never hits.
- Runway Ad Localization recipe vs a Sume image edit prompt
Runway localizes an ad image from a targetLanguage code like ja. On Sume, send the ad as a reference image and name the language in the edit prompt.
- Runway Product Ad recipe vs Sume reference-to-video
Runway's Product Ad Recipe turns product photos into an ad video. On Sume, send photos as reference images and put the concept in one prompt.
Written by Sume