Inside an episode: who controls transitions
19 of the 28 editors say something about who controls transitions. Among those, the reading given most often is “Applied by the tool”, for 8. Each row carries the first statement logged; the full wording is on each editor's page. As of 2026-09-25.
| Editor | Reading | What the pages say |
|---|---|---|
| Character App | Joined in order | Kept Clips are assembled into the Episode in order; no transition is named |
| Crreo AI | User picks | Transitions are set to None, Auto (chosen by the system) or All Same |
| DirectStudio AI | Applied by the tool | Transitions are added by asking the AI in plain language, which applies the edit |
| DomoAI | In another editor | Clips are cut together in the writer's own editor |
| Filmora | Applied by the tool | The AI handles scene transitions across the scenes |
| Frameo | None said | None said |
| Genra | Applied by the tool | The agent adds transitions while building the video; the user can take over |
| Google Flow | First and last frames | Transitions are made with start and end frames |
| HeyGen | None said | None said |
| Higgsfield | Applied by the tool | The user picks a rhythm, and the scene arrives with cuts already built in |
| ImagineArt | User picks | Scene Jump and Time Jump transitions carry continuity between locations and moments |
| LTX Studio | None said | None said |
| M Studio | None said | None said |
| MagicLight | Applied by the tool | Scenes are connected with intelligent transitions |
| Novi AI | Applied by the tool | The drama is generated with scene transitions included |
| OiiOii | First and last frames | Shots are guided by first-frame and last-frame references |
| Pexo | Applied by the tool | Pexo brings the scenes together and handles transitions and pacing |
| Pippit | User picks | Smooth transitions are added by the user along with music and captions |
| PopShort AI | Applied by the tool | On the top plan, an Editing Agent stitches the final cut |
| Revid AI | None said | None said |
| SceneMixer | Joined in order | The composite joins the active version of every segment, without re-encoding where it can; no transition is named |
| Scenes AI | None said | None said |
| Story.com | Suggested, user decides | The Movie Agent suggests transitions, and the user accepts or ignores them |
| StoryShort | None said | None said |
| Toonkit | None said | None said |
| Topview Drama Studio | First and last frames | Continuation is offered in the beat workspace |
| TrendShort | User picks | The export step offers hard cut, soft transition or dip-to-black before the episode is assembled |
| Vivideo | None said | None said |
Inclusion rule. All 28 editors on the register; an editor whose pages skip this behaviour shows not said. Order. Alphabetical by tool name.
1About this behaviour
Transitions records who decides how two units meet. Four editors let the user pick, eight apply transitions themselves, three build joins from first and last frames, two join units in order without naming a transition, one suggests and lets the user decide, and one leaves the join to another editor.
Nine say nothing. For drama, where most joins are straight cuts, the useful question is less which effects exist than whether the tool will leave a cut alone.
2Readings on this behaviour
- User picks: 4 editors
- Applied by the tool: 8 editors
- First and last frames: 3 editors
- Joined in order: 2 editors
- Suggested, user decides: 1 editor
- In another editor: 1 editor
- None said: 9 editors
3Per-editor readings
- DirectStudio AI — Applied by the tool
- DomoAI — In another editor
- Filmora — Applied by the tool
- Genra — Applied by the tool
- Google Flow — First and last frames
- Novi AI — Applied by the tool
- Pexo — Applied by the tool
- Pippit — User picks
- PopShort AI — Applied by the tool
- TrendShort — User picks
4The other behaviours
How an episode is built · Whether a redo is charged again · How many versions are kept · Whether a single shot can be redone · Whether a finished cut can be partly replaced