A blogger redid a 30-second clip in Seedance 2.5 as one piece and spent 21 generations at $25 each — $525. Every attempt broke something different: wrong weapon, zombies not running at the hero, no grenade.
Slicing solves this differently: the clip is cut into scenes, the first frame of each is restyled as an image, and the generator gets short pieces and repeats the motion of the source in the new look. Scenes that need no changes never go to the generator, a failed piece is redone on its own, and in the end everything is stitched back together with the original sound. This can save money when not every scene needs changes: you pay only for the scenes you change, and in the method author's experience slicing works in about 9 cases out of 10.

In a long shot with no cuts, start a new piece on the first frame where the new object is already visible, so it is on the first frame of its piece. Do not send scenes where nothing changes to the generator.
Ask it to keep the composition, pose, light and background and change only what you need. If the same person or object appears in many scenes, make a reference first and attach it to every restyle. Check the pose and angle against the source frame before generating video: redoing an image is cheaper.
Upload a piece of 4–30 seconds and the restyled frame as a photo, and in the prompt say what changes and what stays. The length and format of the result come from the source piece. Slow down a scene shorter than 4 seconds, remember the factor, and restore the speed after generation.
It costs less, and a good draft can be completed to 1080p within 7 days without a new generation. Redo a failed piece on its own, changing one thing at a time: the prompt, the restyled frame or the cut point.
Restore the speed of slowed scenes, match the size and frame rate to the source, and lay the original audio track over it. The Narezka skill ("slicing") at the bottom of the page does the slicing, frames and stitching itself. From you it needs the video, what to replace, the restyled frames (or a "yes" to generate them) and a "yes" for each video generation.
The first prompt is for restyling a frame in GPT Image 2.6, the others are for Seedance 2.5 in Video editor mode. Fill in your own text in square brackets.
Keep this frame as is: composition, angle, pose, light, background and all people. Change only: the hero's light hoodie → a dirty torn ivory t-shirt, and in his hand a golden revolver with a white grip. No new objects and no text. Photorealistic, like a frame from the same video.
@video1 is the source video: repeat the motion, camera, pace and timing exactly. @image1 is the first frame in the new look: this is how [object] looks in the whole scene. Change only: [object] → [new look, as in @image1]. The replacement follows the path, scale, overlaps and contacts of the original object. Keep from @video1: [people, background, light, clothes, everything we do not change]. Camera: trajectory, framing and focus as in @video1.
@video1 is the source video, repeat the motion and camera exactly. @image1 is the first frame of the scene. At the moment of the finger snap, the TV behind the girl explodes: a flash, screen shards, smoke. The girl, her movements, the light and the camera as in @video1. Before the snap the TV does not change.
The author of the video "Seedance 2.5 Tutorial: Full AI Video-to-Video Workflow" filmed a take in a yard with a friend and a bat, and wanted the AI to turn it into a zombie apocalypse scene: an abandoned mall, a zombie crowd, a golden revolver, a grenade and an explosion.
His preparation was serious: a location frame and character and prop sheets in an image model, and a shot-by-shot prompt written in Claude. But he generated the whole 30-second video in one piece, and every failure had to be redone from scratch.

Every generation gave a new error. The blogger fixed the prompt in the same Claude chat and ran the whole clip again.





Each generation of the 30-second clip cost the blogger about $25. In total, 21 attempts — $525. He compares this to a shoot with makeup artists, extras and graphics for tens of thousands, and that is indeed cheaper. But most of the money went on repeats where one detail broke, and he had to pay for all 30 seconds.

The generator knows about the replacement only what is visible on the restyled first frame and in the prompt. Everything that appears later — a new shot, a second person, an object that enters the frame — it has not seen in the new look, and it often returns it as in the source or invents its own version.
The longer the piece and the more events in it, the more places where something goes wrong. And a mistake in one detail at the end of the clip costs a new generation of the whole clip.
| The whole clip in one generation | Slicing into scenes | |
|---|---|---|
| What goes to the generator | All seconds of the clip, even without edits | Only scenes where something changes |
| If it did not work | A new generation of the whole clip | A new generation of one piece |
| Objects that appear later | Often come back as in the source | Visible on the first frame of their piece and get replaced |
| Check before paying | Only the prompt | The restyled frame of every scene |
| Draft | The whole clip in 480p | Every piece in 480p, in 1080p only the good ones |
Example: a 30-second clip of six 5-second scenes, with edits needed in four. 20 seconds go to the generator, not 30, and redoing a failed scene is 5 seconds, not the whole clip.
If the clip was filmed as one shot, cut not by time but by the appearance of objects.
The method is packed into a skill — a file with instructions for an AI assistant. The assistant finds the shot changes and checks them frame by frame, cuts the clip, extracts the first frames, writes the tasks for restyling and for Seedance 2.5, lays out the project and stitches the finished pieces with the original sound. From you it needs the video, what to replace, the restyled frames (or a "yes" to generate them) and a "yes" for each paid generation.
Claude Code: put the file at ~/.claude/skills/narezka/SKILL.md. Codex, Cursor, ChatGPT and any other assistant: attach the file to the chat and write "follow this file". The file is in Russian, but the assistant follows it in any language and answers in yours. For slicing, the assistant needs access to your computer and the free program ffmpeg — the skill checks this and offers to install it.
Original video: "Seedance 2.5 Tutorial: Full AI Video-to-Video Workflow" by Rourke on YouTube
It is redoing a finished clip: the AI takes the motion, camera and timing from the source and changes the look based on a prompt and an image. In Mixer AI this is Seedance 2.5 in Video editor mode.
The generator knows about the replacement what is visible on the restyled first frame. What appears later it has not seen in the new look, and it often returns it as in the source. That is why the clip is cut so that every replaced object is visible on the first frame of its piece.
Do not send scenes without edits to the generator, check the restyled frame before generating, start with a 480p draft, and redo only the failed piece, not the whole clip. The price of each generation in Mixer AI is visible before you start.
In Video editor mode, from 4 to 30 seconds, and the result is as long as the piece. A scene shorter than 4 seconds is slowed down before generation and sped back up afterwards.
Download it on this page. It works in Claude Code, Codex, Cursor and ChatGPT: the file goes into the skills folder or is attached to the chat.