VidBudget

Пока эта страница доступна только на английском.

Fix Seedance 2.5 “ratio must be adaptive” and “duration must be -1”

Seedance 2.5 decided your request is a video edit or a video extension, not a new video. Those two task types only accept ratio: "adaptive", and an edit also needs duration: -1, because the output takes its shape and length from the source video. Either send those values, or word the prompt so the model treats the video as a reference.

Данные проверены 2026-11-18 · VidBudget

Short answer

  • The model reads your prompt. Words like replace, add, remove, change or edit the video make it a video edit; extend or continue make it a video extension.
  • For an edit, send "ratio": "adaptive" and "duration": -1, with a source video of 4–30 seconds. For an extension, send "ratio": "adaptive".
  • If you wanted a new video that only borrows motion, style or a character from the clip, describe it as a reference (for example, “Use @Video1 as the motion reference”) and avoid edit words.
  • Set omni_reference_task_type to edit, extend or reference so a wrong request fails at submission instead of after the queue.

The error text

Depending on how the task was submitted, it comes back either as a 400 on submission or as a task that is accepted, waits in the queue, and then fails with this code:

InvalidParameter.TaskTypeConstraint
The parameters `ratio` and `duration` specified in the request are not valid.
Seedance identified your task as video editing based on your prompt.
Issues: [0] `ratio` must be `adaptive`. [1] `duration` must be -1.

For an extension the message names only ratio. Web apps built on the API often show it in other words, such as “r2v error” or “video reference failed”, and some of them have no adaptive option to pick.

Why Seedance says “ratio must be adaptive”: the model picks the task type

Seedance 2.5 and 2.5 Flash look at your references and your prompt and sort every request with references into one of three subtasks. Two of them have fixed rules for ratio and duration:

Task typeWhen the model picks itRequired
Reference-to-videoAt least one reference image, video or audio, and the prompt asks for a new videoNothing special: any supported ratio, 4–30 s
Video editAt least one reference video, and the prompt asks to change itratio: "adaptive", duration: -1; the source video 4–30 s. The output keeps the source's shape and length
Video extensionAt least one reference video, and the prompt asks to continue it forward or backwardratio: "adaptive"; duration 4–30 s or -1
First / last frameAn image sent with the role first_frame (and last_frame)ratio: "adaptive"; the output follows the first frame's shape

With omni_reference_task_type left at its default, auto, the classification happens after the task starts, so the request is accepted and only fails later. That is why people report waiting up to a quarter of an hour for an error that a submission check could have caught. These rules are specific to the 2.5 series, so requests that worked on Seedance 2.0 can start failing after a switch to 2.5.

Prompt words that trigger edit or extend

BytePlus's guide says an edit prompt contains at least one of edit the video, add, delete / remove or modify / replace / change, and an extension prompt contains extend forward / backward, continue or continue the story. The model judges intent, not exact words, so treat these as warning signs, not a complete list:

Read as an editRead as an extension
replace the man in @Video1 with …, swap, add a hat, remove the logo, change the sky to …, edit the video, keep everything else unchanged, restore, enhance extend @Video1, continue the shot, continue the story, make it 5 seconds longer, what happens next, before @Video1 …

Fix 1: you wanted a new video

This is the common case: you attached a clip for its motion, camera move or character, and the model took it as a request to edit that clip. Describe the clip as a reference and describe the new video you want:

Reads as an editReads as a reference
Replace the dancer in @Video1 with the girl in @Image1.The girl in @Image1 dances on a rooftop at sunset. Use @Video1 as the motion reference: copy the exact movement and timing of the dance.
Change the background of @Video1 to a beach.A new shot on a beach at noon. Follow the camera movement of @Video1.

On the official API you can also send "omni_reference_task_type": "reference". That lifts the ratio and duration rules, but the model still checks the prompt: if it reads an edit anyway, you get TaskTypeMismatch.

Fix 2: you wanted an edit or an extension

Send the values the task type requires and declare it, so a wrong request is rejected at once and not after the queue. A video edit on BytePlus ModelArk:

JSON · video edit
{
  "model": "dreamina-seedance-2-5-260628",
  "content": [
    {"type": "text", "text": "Replace the jacket of the man in @Video1 with a red raincoat."},
    {"type": "video_url", "video_url": {"url": "https://example.com/source-8s.mp4"}, "role": "reference_video"}
  ],
  "omni_reference_task_type": "edit",
  "ratio": "adaptive",
  "duration": -1
}

A video extension (the output length is yours to choose, 4–30 s, or -1 to let the model decide):

JSON · video extension
{
  "model": "dreamina-seedance-2-5-260628",
  "content": [
    {"type": "text", "text": "Extend @Video1 forward by 5 seconds: the camera keeps rising above the city."},
    {"type": "video_url", "video_url": {"url": "https://example.com/source-10s.mp4"}, "role": "reference_video"}
  ],
  "omni_reference_task_type": "extend",
  "ratio": "adaptive",
  "duration": 5
}

If you do not know in advance which type a request is, BytePlus recommends auto with "ratio": "adaptive" and "duration": -1, which satisfies every subtask. The trade-off: you no longer choose the shape and length of a new video yourself.

Some unified video APIs and web apps cannot send adaptive or -1 at all (one SDK's issue tracker has a report of exactly this). There, rewording the prompt (Fix 1) is the only fix that works.

TaskTypeMismatch

InvalidParameter.TaskTypeMismatch is the opposite problem: you declared edit, extend or reference, but the prompt reads as another type. The parameters are fine; the prompt is not. Make the prompt say what you declared (an edit names what to change in @Video1; an extension says extend or continue), or go back to auto.

Handle it in code

Expect both forms: a 400 when you submit, and a task that fails later. One retry with the required values covers a misread edit; do not retry the same request unchanged.

Python
TASK_TYPE_ERRORS = ("TaskTypeConstraint", "must be `adaptive`", "must be -1")

def needs_edit_values(error_text: str) -> bool:
    return any(marker in error_text for marker in TASK_TYPE_ERRORS)

def resubmit_as_edit(request: dict) -> dict:
    """The model read this request as a video edit: send the values an edit requires."""
    return {**request, "omni_reference_task_type": "edit", "ratio": "adaptive", "duration": -1}

# On a 400 at submission, or on a failed task whose error matches, submit
# resubmit_as_edit(request) once. If the message names only `ratio`, it was
# read as an extension: set ratio to "adaptive" and keep your duration.

On VidBudget

VidBudget's API takes a fixed aspect_ratio (16:9, 9:16, 1:1, 4:3 or 3:4) and a fixed duration; it does not accept adaptive or -1 yet. In practice this means reference-to-video works, and a prompt that Seedance reads as an edit or an extension is likely to fail. When it does, the task is refunded in full automatically, including the amount held for it.

Sources

FAQ

What does "Seedance identified your task as video editing based on your prompt" mean?

Seedance 2.5 sorted your request into the video-edit task type because it has a reference video and the prompt asks to change it. Edits need ratio: "adaptive" and duration: -1, because the output keeps the source video's shape and length.

How do I stop Seedance 2.5 from treating my reference video as an edit?

Describe the clip as a reference ("Use @Video1 as the motion reference") and the new video you want, and leave out edit words such as replace, add, remove or change. On the official API, omni_reference_task_type: "reference" declares it; the prompt still has to match.

What is the difference between TaskTypeConstraint and TaskTypeMismatch?

TaskTypeConstraint: your ratio or duration does not fit the task type the model chose; change the parameters. TaskTypeMismatch: you declared a task type and the prompt reads as another one; change the prompt or set the type back to auto.

Am I charged for a request that fails with TaskTypeConstraint?

A request rejected with a 400 at submission creates no task. On VidBudget, a task that fails later is refunded in full to your balance automatically.

Вход в VidBudget

В аккаунте доступны баланс, ключи API и история генераций.

или
Войти через Google

Ещё нет аккаунта?Зарегистрироваться бесплатно

Связаться с нами

Поможем с аккаунтом, пополнением баланса, результатами и API.

По вопросам платежа укажите номер заказа, по вопросам генерации — ID задачи. Так мы сможем сразу её проверить.

Правила возврата средств →Документация API →