A short runtime does not establish that a montage is an eligible AI editing input. Runway's current Edit Studio guide lists a maximum of ten cuts or shot changes; eleven or more produces an error. Count the transitions inside the actual uploaded file, alongside its duration and media specifications, before treating rejection as a prompt-writing problem.
Count what is inside the one attachment
One MP4 can contain a long unbroken shot or dozens of brief images. An attachment-count limit and a cut-count limit therefore measure different things. Review the source from beginning to end and mark visible shot boundaries. Keep uncertain transitions identified instead of claiming that a dissolve or rapid flash always counts one particular way in the service.
The same guide currently specifies source duration, resolution and frame-rate conditions. Check its live details and the active interface together; another Runway model or an Imagild input route may use a different contract. Do not extrapolate these limits into a universal rule for all video-to-video tools.
Make an editorial split before a technical split
When the montage exceeds the supported complexity, divide it into groups that can be edited and reviewed independently. A product close-up and a completely different venue may deserve separate treatment even if their combined duration is small. Keep the original assembly intact and write each derivative's original in and out positions.
Avoid splitting in the middle of a word, a hand contact or a meaningful transition merely to satisfy a numerical count. Decide whether that boundary belongs to the edit. If a dissolve must be rebuilt later, retain the clean shot material or document the limitation before generation. Extra handles are useful only when they actually exist in the source.
A hypothetical eighteen-shot teaser
Imagine a teaser made from eighteen very short shots. It is a proposed planning example, not an executed Edit Studio upload. Record the shots in story order, then group them by location and intended edit. A service's cut definition still needs checking; do not automatically equate eighteen shots with the same number of cuts.
| Derivative | What to record | Assembly evidence |
|---|---|---|
| Opening group | Source interval and internal boundaries | Original first and last frames |
| Product group | Intended object change | Stable identity reference and joins |
| Closing group | End-card content and timing | Approved final frame and sound tail |
For every group, inspect the file actually exported for upload. A filename saying short version does not prove its cut count, dimensions or frame rate. Preserve a matching original so the transformed output can be reviewed on the same interval.
Reassemble without concealing scope changes
After processing, align each returned group to its documented source interval and inspect every rebuilt join. Check object continuity, exposure, missing frames and the soundtrack separately. If a service changes duration or returns only a selected range, resolve that mapping before replacing the corresponding group in the master.
The approved deliverable is the reconstructed teaser, not simply several successful job statuses. Keep a group manifest linking input derivatives, outputs and final placement. These constraints describe the Runway Edit Studio documentation checked for this guide; Imagild does not thereby promise the same editor, cut detector or preservation behavior. No upload or paid generation was performed for this example.