Change the camera angle of an existing video: Sume edit options

ByteDance Seed lists camera perspective change among the editing features of Seedance 2.5 (read 2026-10-05). If you want to change the camera angle of an existing clip on Sume, the documented edit route is gemini-omni-flash-1.1 with a video_url and a prompt. The Sume docs do not promise that any given instruction, a camera move included, will work, so the right plan is to run one short test, compare frames, and keep a regeneration fallback.

The documented edit call

Gemini Omni Flash 1.1 is one catalog id, and Sume routes it by request shape. Send video_url and the prompt gives the edit instructions. resolution is optional and defaults to 720p. Do not send aspect_ratio or duration; the edit keeps the source's framing. video_url is the edit source, not a reference, so it cannot be combined with image_url, end_image_url or reference_*_urls.

curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: angle-edit-001" \
  -d '{
    "model": "gemini-omni-flash-1.1",
    "prompt": "Show the same scene from a lower camera angle. Keep the subject and lighting the same.",
    "video_url": "https://example.com/clip.mp4",
    "resolution": "720p",
    "mode": "async"
  }'

Verify the angle changed

Pull stills from the source and the result at matching times with video frames, which takes explicit at[] seconds (1 to 24 per call) and returns image artifacts at source size. Put the pairs next to each other. If the subject, lighting or text changed, the edit did more than you asked.

• Source: at: [1, 4, 7].
• Result: the same three timestamps.
• Judge horizon line, subject position and background parallax, not only the subject.

Writing the edit prompt

A good edit prompt names what to change and what to keep. The Sume docs example is of this shape: change one thing and say "Keep everything else the same." For a camera change, state the new viewpoint in plain terms (lower angle, from the left, higher and further back) and then pin the subject, lighting and setting. Avoid stacking several changes in one edit; do one at a time and re-check.

Because the edit keeps the source's framing and ignores duration and aspect ratio, a big viewpoint change may be partial. Do not promise a client a full re-shoot from a prompt.

• One change per edit.
• State what must stay the same.
• Check stills before and after, at the same timestamps.

Region and length limits

Check the current limits for Omni edits before you plan a batch. The edit job takes the source length as it is: the docs say duration is ignored by the provider on edit. A long source therefore stays long, so trim to the part you need first, which costs $0.02 per trim.

If the edit does not hold

The crop row is worth stating plainly: a crop changes framing, not viewpoint. It is cheap, though, at $0.02 per encode job per the docs, and sometimes a tighter frame is what a client meant by a different angle.