Revise the Whole Episode: One Request, Every Segment
This is the same engine as AI edit on a single segment, run across many segments at once: same request box, same checks, same price per segment, same History. What changes is how many segments ride on one request, and how you review the outcome. Reach for the whole-episode run when the note applies from the first segment to the last — a way of speaking, a word someone keeps using, a sound that should sit under a whole scene, a pace that drags. Reach for single-segment AI edit when one segment is off and the rest are fine.
What it does
You give it one request. It revises each selected segment against that segment’s own text — the same request, applied wherever you ticked it. Every segment comes back as one of three things: revised, needing no change, or failed; the list tells you which, and you decide what to keep. It never rewrites the episode as one block, and it never touches a segment you did not pick.
Where to find it
- Open the project, go to step 3 Episode Videos, and press Start Editing on the episode’s card. The whole-episode run lives in the editor, not in step 3 itself.
- In the editor, every segment’s card carries an AI edit button (the wand). It opens the panel where a single segment is revised.
- Type your request in the box. When the episode has more than one segment to revise, an Apply to the whole episode… button appears beside Revise. It stays grey until the box has something in it.
- On a phone, the AI edit button on the Script tab opens the same panel as a sheet over the script.
The whole-episode button only appears for revising. If the segment on screen is blank, or written as plain prose instead of shots, the panel is in AI write mode and there is no whole-episode button — writing a segment from nothing is a one-segment job. To revise the episode instead, open any segment that already has shots.
Step by step
- Open the episode in the editor. Project → step 3 → Start Editing on the episode’s card.
- Open AI edit on any segment’s card and write the request. The small chips above the box (lines, action, mood, time and weather, camera, keep someone out, voice-over, another scene) are sentence starters, not a menu.
- Press Apply to the whole episode…. A dialog opens with your request quoted at the top.
- Pick the segments. Everything it can revise is listed and ticked to begin with; the count sits above the list, with Select all and Clear. Untick whatever should stay as it is. The Start button carries Up to ✦ N — the most this run can cost.
- Press Start. A progress line counts the segments as they are revised (Revising 3 of 12…), and each row shows its state as it arrives: waiting, revising, Changes: 2, No change needed, Couldn’t revise.
- Stop whenever you like. The segments already revised stay in the list; the ones that had not started are dropped, and nothing is charged for them.
- Review each row. View opens the line-by-line diff — removed lines struck through, added lines in green. If the request changed the segment’s shots or seconds, the row also says the length is going from Xs to Ys and whether regenerating that segment’s video costs more than before.
- Save what you keep. Save all (N) writes every revised segment into the script as a normal edit, or press Save on a single row to keep only that one. Discard results throws the unsaved ones away — and warns that the credits already charged for them are not refunded. Close leaves them for later.
Saving changes the storyboard text only. The segment still plays the old take until you regenerate it — the same as any edit to the text. The summary line under the list keeps the count honest as you go: revised, no change needed, could not revise, and what the run has been charged.
If you refresh, close the page, or come back later
Revised results that are not saved yet are kept on this device — this browser, on this computer — until you save or discard them, and for a day. Reopen any segment’s AI edit panel in that episode and there is a line: You have unsaved results from an earlier run. Press View to open the list again and save from there. The panel says it plainly: results are kept on this device until you save or discard them.
Each result is tied to the exact text it was made from. If a segment’s text changed in the meantime — a hand edit, a restored version — that segment’s old result is dropped from the list, so an earlier revision never lands on newer text. If every revised segment has changed, there is nothing left to resume. Another browser or another computer will not see the results at all.
One run at a time: starting a new run replaces the list. Save or discard what you want to keep before running another request.
What it can change
Whatever single-segment AI edit can do, it can do to each picked segment:
- Lines — reword a line, cut it short, change its tone, stop one character calling another “boss”.
- Action and mood — what the characters do in a shot, how a scene feels.
- Time, weather, camera — the hour of day, the rain, what a shot is showing.
- Sound — the ambient line under a shot, an added voice-over line.
- The shots themselves — add, remove or merge shots and change their seconds. A segment can only hold so much: its total length stays within the segment’s limit, so a very long addition comes back shorter, or fails with a reason. When a change moves the timing, the row shows the new length before you save.
Examples that work
| Request | What comes back |
|---|---|
| “Make every line colder and shorter.” | Each picked segment comes back with tighter, colder lines; shot counts and timing stay as they were. |
| “Add rain sound under the whole scene.” | Each segment’s sound line carries the rain; regenerate a segment and the rain is in the clip’s audio. |
| “Split the argument into more shots — closer angles.” | Shots are added inside the segments you picked; each row shows the segment’s new length, and whether its regeneration price changed. |
Examples that come back as “No change needed”
| Request | Why, and where it does live |
|---|---|
| “Give the villain a black coat.” | A character’s face, hair, build and outfit come from the character image and its states, not from the storyboard text. The note points at the character; change the image or add a state. |
| “Use a different voice for her.” | Voices are picked on the character, not written in the segment. |
| “Turn the background music off.” | Music is not part of the storyboard text; the Music switch by the player turns it off. |
Two more that read the same way: the spoken language of a project is a project setting, not a line in a segment; and anything that appeared in a finished clip that the storyboard never wrote — an extra passer-by, a stray line — came out of generation, so a revision has nothing to remove. Regenerating that segment is what usually clears it.
What it costs
Every segment that comes back revised is charged once, at the same per-segment price as a single AI edit (the price is on the pricing page). The number on the Start button — Up to ✦ N — is the ceiling for the segments you ticked, not a bill: segments that need no change are free, failed revisions cost nothing, and a segment is charged at most once per run.
Two things stop a run part-way. In both cases everything already revised stays in the list and can still be saved, and the segments that never ran are not charged:
- The balance runs out. The run stops at the segment where the credits ended, and the top-up window opens. The segments that never ran drop out of the list, uncharged.
- Too many revisions in one hour. AI edit has an hourly ceiling per account. Single-segment edits and whole-episode runs count against the same ceiling; the run stops where it is, and you can pick it up again later.
Stopping the run yourself, discarding results, or leaving them unsaved does not refund revisions that were already charged — the charge happens when a segment is revised, not when it is saved.
When a row does not come back changed
No change needed means the segment was read and left as it was. The note under the row usually says why: either there was nothing worth changing, or the request is aimed at something the text does not hold (the table above). Nothing is charged.
Couldn’t revise means the revision did not come home: a hiccup on the way, a reply that could not be used, or a request that would push this segment past what it can hold. The reason sits under the row, and nothing is charged. To retry, save or discard the results you have, then run the request again over just those segments.
Writing a request that lands
- Say what to change, where, and to what: “in shot 2, make her line colder” lands; “improve the dialogue” wanders.
- One kind of change per run. Asking for a new shot and turning the music off in the same sentence usually gets half the job done.
- When a row comes back with a note, read the note — it is usually telling you the request belongs somewhere else.
- If a revision fails because the segment would grow too long, ask for less in that one segment and run the rest as they are.
Whole episode, or one segment?
Same engine, same price per segment either way. The difference is how many segments ride on one request, and how you review them.
| You want | Use |
|---|---|
| One segment is off; the rest are fine | AI edit on that segment: preview the change, then Revise again, Edit by hand, or save |
| The same note applies from the first segment to the last | The whole-episode run: tick the segments, review the list, save in one pass |
| To test a wording before rolling it out | Run it on one segment first; when it lands, run the same request across the episode |
| A blank or hand-written segment needs writing | AI write on that segment — writing from scratch is not part of the whole-episode run |
FAQ
Does the whole-episode run rewrite my script at once?
No. Each segment is revised on its own text and listed for review; only the rows you save are written into the script.
Which segments appear in the list?
The ones whose text is a storyboard with recognizable shots. Blank segments and segments written as plain prose are left out; open one of those and use AI write.
Can I leave some segments alone?
Yes. Every segment it can revise starts ticked; untick any of them, or press Clear and pick. Segments you leave out are not revised and not charged.
Am I charged for segments that need no change?
No. Only segments that come back revised are charged, and a failed revision costs nothing. The number on the button is the maximum for the segments you picked, so a run usually costs less.
What happens if I refresh or close the page mid-run?
Results that were already revised are kept on this device for a day. Reopen the AI edit panel on any segment of the episode and a line offers to open them. Segments whose text changed in the meantime are dropped from the list.
Can I stop a run?
Yes, press Stop. The segments already revised stay in the list and can be saved; the ones that had not started are dropped and are not charged.
Can it add or remove shots, or change a segment’s seconds?
Yes, within what a segment can hold. When a request changes the timing, the row shows the length before and after, and whether regenerating that segment’s video costs more.
Does saving regenerate the videos?
No. Saving changes the storyboard text only. Regenerate a segment when you want a clip made from the new text.
Can I undo a saved revision?
Yes, one segment at a time: open that segment’s History and restore the version from before the change.
Does it work on a phone?
Yes. The same dialog opens as a sheet from the AI edit button on the Script tab.
Run one request across the episode
Write the note, tick the segments, look at every change before it lands.
Updated October 10, 2026
Pricing·Novel to Video·Guides·Samples·Support·Privacy·Terms·Legal·Contact·Affiliate program·© 2026 SceneMixer