Scenario Seedance

Scenario Seedance Video

Overview

Seedance, ByteDance's video family on Scenario, folds every mode below into one model that infers which from your inputs, so the conditioning you pass decides more than prompt wording. Discover it with search and treat model_schema_get as the contract: members ship side by side, agreeing on the shape and disagreeing on every number.

Connection and the core loop: see the scenario skill in this repo; model-agnostic video work: the scenario-video skill; choreography held across cuts from a storyboard: the scenario-seedance-storyboard skill. If a sibling skill named here is missing from your available skills, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.

Quick reference

Mode follows from the inputs (names from the live schema):

image and the reference arrays are mutually exclusive. referenceVideos (motion conditioning) and referenceAudio (timing and energy, or a speaker's voice) combine with referenceImages; on the 2.0 line reference audio also requires one image or video reference, where 2.5 takes it alone. Reference parameters are arrays even for one asset. Prompt tags bind by array order: @image1 is referenceImages[0], likewise @video1 and @audio1, and the prompt says what each tag governs and what it leaves alone ("@image1 defines the bottle and label, nothing of the set"), for video and audio tags as much as for images. No seed, mask, or camera parameter exists: camera moves live in the prompt, one dominant move and one action per shot. Several actions go as timecoded beats ("0-2s ... 2-4s ..."), one per beat, the last ending inside duration, the shot named as one continuous take.

A reference track the prompt does not claim is easily ignored, a generated voice line most of all, so bind it to a role in words: "@audio1 is her own voice; she speaks it to camera, lips in sync" for speech, "the camera move and each action land on the beats of @audio1" for music.

duration defaults to Auto, which on 2.5 at authoring time priced a text-to-video job as the full 30 second cap (the same 480p prompt quoted about four times its 8 second price). Set the seconds the shot needs on every run; with referenceVideos, Auto follows the longest reference clip instead.

Caps are per member, so read them off model_schema_get. At authoring time 2.5 took 30 reference images, 10 videos, 10 audio, 4 to 30 seconds, up to 1080p; the 2.0, Fast, and Mini hits took 9, 3, 3, and 4 to 15, with 4k on 2.0 alone and no lastFrameImage on Mini. Price moves further than the caps do, six times across the family for one 4 second 480p job, so dry_run the same job on two members before a batch.

The conditioning rule

In reference mode, frame one anchors to the base state of the reference world, and no prompt wording overrides it. If the shot must open in a specific state, render a still of it and pass it as image; use referenceImages when only identity, world, and palette matter. Deciding this per shot before generating is worth more than any prompt tuning.

Sound from the shot, music from elsewhere

generateAudio (default true) is one switch over the whole track: it scores the shot as well as sounding it. A score written inside a shot survives no cut, since each shot invents its own key and tempo and the next one restarts them.

So run the lanes apart. Keep generateAudio: true for what the picture makes, footsteps, impacts, room tone, dialogue, each landing on frame, and name only those sounds ("diegetic sound only: heels on tile, room tone"). Never name what to leave out: "no music" is what the audio filter reads, and a track blocked with OutputAudioSensitiveContentDetected usually traces to such an exclusion, so re-run on the same model with the sound named positively before any provider switch: the filter read the wording, not the provider (see the scenario-moderation skill). Spoken lines go in quotes, sized to the clip's seconds, with the speaker named and the delivery in two or three words. Score the sequence once with a music model (see the scenario-audio skill) and lay that track over the assembled cut (see the scenario-video-assembly skill, or scenario-seedance-music-video when the song comes first): re-scoring then costs one audio run, not every shot again.

The prompt is the only lever, so listen to what comes back: when music leaks in, re-run that shot with generateAudio: false and add sound from a sound-effects or video-to-audio model.