Edit a 20-second AI video: Luma, Aleph 2 or Omni's 10-second input?

Google's Omni page limits uploaded videos for editing to 10 seconds or less (Google Omni docs, read 2026-10-09). Runway's Aleph 2.0 edits videos of 2 to 30 seconds with up to 5 keyframe images (Runway changelog, read 2026-10-09), and Luma's pricing mentions video-to-video at 10, 15 or 20 seconds (Luma pricing, read 2026-10-09). On Sume, Omni edits go through video_url, so a 20-second clip is cut into windows first.

How do you cut a 20-second clip for Omni?

Use video trim to make two 10-second pieces: start: 0, duration: 10 and start: 10, duration: 10. The docs set the rate at $0.02 per job. Trim only reads Sume-hosted clips, so import the file first with POST /v1/media-imports. Use precision: "exact" (the default) so the cuts are frame-accurate.

{"video_url": "https://media.sume.com/artifacts/artf_demo/talk.mp4", "start": 10, "duration": 10}

What does the edit pass cost?

Edits are billed per output second at the provider list times 1.25; other resolutions follow the price chart linked below.

What can go wrong at the seam?

The Video Router docs say the prompt gives the edit instructions and the output keeps the geometry. Join the halves on a timeline after you check them.

• Colour or lighting can drift between the two edited halves, so check the last frame of the first against the first of the second with video frames.
• Native audio is regenerated per clip, so listen across the join.
• Edits keep the source framing, so the aspect ratio cannot change in this step.

When is a longer-edit tool the better choice?

If the change must be consistent across one 20 to 30 second take, a tool that accepts the whole clip avoids the seam. Sume's catalog lists no Runway or Luma ids (catalog read 2026-10-09), so that route sits outside Sume.