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.

In DaVinci Resolve 21.1 the source viewer shows a clip at its original aspect ratio, whether the timeline is vertical or horizontal. If you also need to know that ratio before an edit, Sume's video inspect returns probe facts and stills whose entries carry width and height, and it is unbilled for probe and stills.
Resolve claims come from Blackmagic's 21.1 announcement; Sume claims from Video inspect and Video frames, both read 2026-10-01.
What changed in the Resolve 21.1 source viewer?
Blackmagic's announcement says the source viewer now preserves the source media's original aspect ratio independent of the timeline being vertical or horizontal, so customers working with both formats see their media correctly without manual adjustment.
That is a viewing change inside Resolve. It does not tell a script or an agent what shape a file is, which matters when you plan crops or reframes outside the editor.
How do I read a clip's shape with Sume?
Import the clip first (POST /v1/media-imports), then call POST /v1/video-inspect with its media.sume.com URL and an Idempotency-Key. The result carries probe and frames[{t,url,width,height}] as durable image artifacts.
Stills default to a max_edge of 768, so their width and height are the clamped size. When you want source size, pass the source edge in frames.max_edge (the docs allow up to 2160) or use POST /v1/video-frames, which omits the clamp.
curl -X POST https://api.sume.com/v1/video-inspect \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: aspect-check-001" \
-d '{
"video_url": "https://media.sume.com/artifacts/artf_demo/talk.mp4",
"frames": { "at": [0], "max_edge": 2160 }
}'Which Sume call fits which question?
Both routes are for one clip already in your workspace; neither re-encodes it.
| Route | Use it for | Billing |
|---|---|---|
POST /v1/video-inspect | Probe, sampled stills, optional transcript | Probe and stills unbilled |
POST /v1/video-frames | Stills at named times, source size unless max_edge is set | Unbilled |
frames: false on inspect | Probe only, no stills | Unbilled |
Does inspect change my clip?
No. The docs say video inspect never re-encodes the source and never produces an MP4. If you then need a different shape, that is a separate step such as reframing after generation.
What should I do before conforming a batch?
Run inspect with frames: false on each clip, read the probe, and group clips by shape before you decide on crops. Use video-frames when you want one source-size still per clip for a visual check. Transcription is the only billed half of inspect, and it stays off unless you set transcribe: true; see extract video frames for the stills route.
Sources
Related posts
More in Use cases
- 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.
- Runway product swap vs a Sume prompted video edit
Runway's Product Swap Recipe takes a video plus product images. Sume's closest route is one edit call: a video_url and a prompt that names the swap.
Written by Sume