Inspect old Sora mp4s before mixing them with new clips

Before you cut saved Sora files together with new Sume clips, probe each file. Sume's video inspect returns probe facts, sampled stills and optional transcript for one clip, without re-encoding it. It reads clips on media.sume.com owned by your workspace, so import the file first. The probe tells you duration, size and codec facts; the stills let you eyeball cuts. Then decide which old shots to keep and which to regenerate on a current model.

What the endpoint needs

The docs set a few firm rules that shape the workflow.

A short audit loop

For a folder of saved Sora exports: import each file, call inspect with frames: { at: [0, 2] }-style explicit timestamps or the default, and store the probe record next to the file name. Group by what the probe reports, then compare with the model you plan to use for new shots. Mismatches in aspect ratio or duration are the common reason a mixed edit looks wrong.

Decide per clip

A clip that matches your target can go straight into an edit. A clip that is close may need a trim or reframe with the other media tools. A clip that is wrong in a way tools cannot fix gets re-rendered. Because a re-render on a current model is a different clip, not the same shot, check the stills against the new output before approving the swap.

• Keep the original file; probe results are records, not replacements.
• Use fast seek for skimming and precise when a timestamp must match.
• Do not transcribe unless you need the audio text.

Honest limits

Inspect does not judge quality or content semantically; the docs describe it as probe facts, stills and optional speech-to-text. It bills the probe by compute, so check your usage after a large audit. For the wider job lifecycle, see the jobs guide.