Runway Enhance Frame Rate on a Sume clip: get the MP4 first

Yes in principle: Runway's changelog says Enhance Frame Rate works on any video, whether or not Runway made it. A clip from Sume is an MP4 behind a URL, so the practical step is to download the file from the finished job's content endpoint. This post does not describe Runway's upload screens, because the changelog entry does not, and Sume is not integrated with Runway.

Where do I get the file from Sume?

Sume generation is asynchronous. You submit a job, poll its status, then read the result. A completed video job exposes its file at GET /v1/videos/{jobId}/content. Download it before you rely on it for a long edit chain, and keep your own copy, since the file is your deliverable.

The jobs and results guide describes the status calls and the Idempotency-Key header, which stops a retry from creating a second paid job.

import os, requests

BASE = "https://api.sume.com"
H = {"Authorization": "Bearer " + os.environ["SUME_API_KEY"]}

def download(job_id: str, path: str) -> None:
    url = f"{BASE}/v1/videos/{job_id}/content?index=0"
    with requests.get(url, headers=H, stream=True, timeout=120) as s:
        s.raise_for_status()
        with open(path, "wb") as f:
            for chunk in s.iter_content(1 << 20):
                f.write(chunk)

if __name__ == "__main__":
    download("job_REPLACE_ME", "clip.mp4")

What should I check before sending it to Runway?

Runway's entry names limits: Max+ plans, up to 4K, up to 5 minutes. Read your clip's duration, width and height with Video inspect first. It is unbilled for a probe. The table maps each limit to the field that answers it.

Does the rate change come back into Sume?

The return trip is a plain upload. Sume's Timeline, trim and captions steps want a media.sume.com source, so a file made elsewhere needs to be added to your media library before those steps can use it. The MCP asset flow does that: request an upload URL, PUT the file, then complete the asset.

Does this change how the clip looks?

Changing the frame rate changes motion smoothness, not content. Whether Runway's result looks better for your clip is something to judge on your own footage. Sume makes no claim about it.

What should I keep from the Sume job?

Keep the job id and the Idempotency-Key you used, plus the downloaded MP4 and its probe output. If you need to regenerate a clip later, the id lets you find the original job, and the probe tells you what rate and size the file had before any conversion. Store both next to the file.