Remake a viral clip with my product: edit it or rebuild it?
Sume has two remake routes: models that keep the source footage, and reference remix that rebuilds shot by shot. How the agent decides and when to override.
Two families
A remake of someone's clip with your product or your people splits in two. The first family keeps the source footage and changes what is in it: Seedance 2.5 video-to-video, Genjutsu and H3 Max Recast. The second, reference remix, rebuilds the piece shot for shot with a new subject, a new voice and new captions.
Sume's agent instructions in the repository state the rule. When the piece is video-primary and reads as one take, with almost all of it being the source video and the ask keeping that take while changing the clothes, the product, the look or the people, with no new script, the source-footage family fits. Otherwise the rebuild is the answer.
The decision, in questions
- Does the clip have camera cuts? Several cuts point to a rebuild, because Recast needs no single shot over 15 seconds and the Genjutsu and Seedance rows have their own limits.
- Do you want a new script or new voice? A recast keeps the source's soundtrack. fal's page, read 2026-10-03, says Recast preserves the source motion, camera, cuts and audio. A new script means a rebuild.
- Is it the people that change, or the product? People: Recast. Product or clothes: Seedance 2.5 video-to-video or Genjutsu. A product swap inside a rebuilt shot uses Seedance 2.5 reference-to-video.
- Is the length over 30 seconds? Source-footage rows end at 30 seconds, so trim first or rebuild.
Which source-footage row leads
The instructions say Seedance 2.5 video-to-video tends to hold a one-take shape best, so the agent leads with it: the source as the one video_url in the references, image references for the new look, 720p unless asked, audio off and a new music bed. Genjutsu and Recast stay fair picks when the ask leans that way, such as a person swap where the original soundtrack must remain.
The agent is told to say the route and why in one line before the first paid call, and to dry-run to quote the price. You can disagree at that point and name the row you want.
What neither family does
Neither family makes a remake that stays faithful to a reference while changing everything in it. If the result drifts into a different video, the instructions call that a miss even when it looks good. Download rights are separate: use clips you own or have permission to adapt.
Sources
Related posts
More in Agents
- Scheduled run missing from /v1/jobs? Read /v1/action-runs instead
A Sume scheduled agent run is not a generation job. It never appears in /v1/jobs and has its own statuses, so poll /v1/action-runs/{run_id}.
- Scheduled run body: unknown fields are silently dropped, not a 400
A typo in a Sume scheduled run body is dropped without an error, unlike a Format run. Check names, then read the receipt to see what applied.
- Scheduled AI runs in Q4 2026: ceiling by cadence at $1 a run
At the $1.00 default cap, weekly runs top out at $13 for Q4, daily at $90 and hourly at $2,160. How the schedule cap works and what null changes.
- Scheduled run receipt shows less than the wallet debit: which number
usage.billable_amount_usd_micros on a run receipt is generation spend only. GET /v1/usage?run_id= debited_usd_micros also counts the Agent's own turns.
Written by Sume