Will my clip fit Runway Enhance Frame Rate? Probe it first
Runway lists 4K and 5 minutes as Enhance Frame Rate limits. Sume's Video inspect probe returns duration, size and fps for free, so you can check before you.

Run a Sume Video inspect probe on the clip, with frames set to false, and compare duration_seconds, width, height and fps against Runway's stated Enhance Frame Rate limits of up to 4K and up to 5 minutes. The probe is unbilled and returns in one call, so you find a too-long clip before you spend a plan's time uploading it.
What does the probe return?
With frames set to false, Video inspect returns only the probe. The fields that matter for this check are listed below. The source must be a media.sume.com clip of up to 1800 seconds, and the default mode is sync with a 30 second wait.
| Field | Use |
|---|---|
| duration_seconds | Compare with 5 minutes (300 s) |
| width, height | Compare with 4K |
| fps | Know the starting rate |
| rotation | Portrait clips can report a rotation |
| has_audio | Know if there is a track to keep |
How do I call it?
Send the hosted clip URL with frames set to false. Python is shown, and the call needs SUME_API_KEY set.
import os, requests
r = requests.post(
"https://api.sume.com/v1/video-inspect",
headers={"Authorization": "Bearer " + os.environ["SUME_API_KEY"]},
json={"video_url": "https://media.sume.com/artifacts/artf_demo/talk.mp4", "frames": False},
timeout=60,
)
r.raise_for_status()
probe = r.json()
print(probe)What counts as a pass?
Under Runway's stated limits, a pass is a duration of 300 seconds or less and dimensions within 4K. Runway's entry says the feature targets 25, 30, 48, 60, 120 or 59.94 fps. A clip that is already at your target rate needs no conversion.
What if the clip is too long?
Cut it with Video trim, which is $0.02 per job and keeps up to 900 seconds of output, then process the parts. Trim with precision exact if you want a frame-accurate cut. Rejoining the parts in Timeline needs matching rates, or Sume will repeat or drop frames to meet the output rate.
What does the probe not tell me?
It does not tell you whether your Runway plan includes Enhance Frame Rate. Runway's changelog lists it for Max+ plans, so check your own plan in Runway.
How do I automate the check?
Loop over your clips, call the probe for each, and write down duration_seconds, width, height and fps in a sheet. Flag any clip over 300 seconds or above 4K. A batch of fifty clips costs nothing to probe, so the check can run before every upload. Keep each call under the 30 second sync wait, or switch to an async call for long sources.
Sources
Related posts
More in Developers
- YouTube API audit and quota extension forms: which one to file
YouTube lists four forms for API audits and quota: extension, appeal, periodic audit and change of control. When each applies, and the private-upload rule.
- YouTube API quota reset time: midnight Pacific, errors cost 1
YouTube's quota page says daily quota resets at midnight Pacific Time and even invalid requests cost a point. What that means for Shorts upload batches.
- YouTube captions.insert: 100 MB, 400 quota units, and an SRT build
YouTube captions.insert costs 400 quota units and takes a 100 MB file. Sume returns words and segments, not SRT, so here is the 20-line conversion to upload.
- YouTube notifySubscribers=false: uploading a Shorts backlog quietly
videos.insert takes a notifySubscribers parameter that defaults to true. Why to set it false when you upload a batch of Sume-made Shorts in one sitting.
Written by Sume