MagicLight and TrendShort, episode by episode
MagicLight and TrendShort read differently on five of the six behaviours: unit, redo charge, versions, transitions and replace in cut. They read the same on one-unit redo. From 5 source pages, read 2026-09-25; no maker pays to be listed.
| Behaviour | MagicLight | TrendShort |
|---|---|---|
| Unit | Scenes | Shots |
| Redo charge | Charged again | Failed runs refunded |
| Versions | Pick from a set | None said |
| One-unit redo | One unit at a time | One unit at a time |
| Transitions | Applied by the tool | User picks |
| Replace in cut | None said | Recomposite |
Inclusion rule. The six behaviours every editor is read on. Order. Register order of the behaviours.
1How the two differ
Both describe charges. MagicLight uses credits from the start of processing without refunds; TrendShort charges on success and refunds failures automatically. MagicLight applies transitions itself; TrendShort lets the user choose hard cut, soft transition or dip to black.
How an episode is built
Review every individual scene in the Storyboard editor.
MagicLight, AI Drama Generator page
Each shot should describe one focused action and a clear result, not several unrelated events.
TrendShort, Studio workflow guide
Whether a redo is charged again
Credits are consumed when processing begins
MagicLight, FAQ
After a task fails, the system attempts an automatic refund.
TrendShort, support
How many versions are kept
Generate multiple versions - Choose the best result from several attempts
MagicLight, FAQ
TrendShort: none said.
Who controls transitions
Connect your scenes with intelligent transitions that maintain visual coherence.
MagicLight, home page
The final export step exposes hard cut, soft transition, and dip-to-black choices before assembling the whole episode.
TrendShort, Studio workflow guide
Whether a finished cut can be partly replaced
MagicLight: none said.
Composition combines prepared video and audio per shot, with an audio strategy control before batch composition.
TrendShort, Studio workflow guide
2Statements on file
- Step 3, adjust each sceneScenes are adjusted one by one in a storyboard editor; scripts of up to 12,000 characters give about 50 minutes
- Step 3, storyboardThe storyboard is a list of shots, each one focused action; shots are composed with their audio before export
- FAQ, credits and refundsCredits are consumed when processing begins and are not refunded once used; estimates are shown first
- How credits are charged and refundedEstimated credits are authorised, charged when a task succeeds, and refunded automatically when it fails
- FAQ, inconsistent resultsGenerating several versions and choosing the best is the suggested fix for inconsistency
- Seamless scene transitionsScenes are connected with intelligent transitions
- ExportThe export step offers hard cut, soft transition or dip-to-black before the episode is assembled
- Compose shotsComposition is a review step that combines video and audio per shot before the whole episode is assembled
3How a segment-based editor handles what splits MagicLight and TrendShort
| Point | SceneMixer | Source |
|---|---|---|
| How an episode is built | An episode holds segments, and a segment holds every take generated of it | SceneMixer, what is inside a project |
| How many versions are kept | Every generation of a segment is kept, and the history control switches between them | SceneMixer, fixing one shot without redoing everything |
| Whether a finished cut can be partly replaced | After a segment changes, the episode is composited again; the earlier file stays until the new one replaces it | SceneMixer, compositing and sharing an episode |
Inclusion rule. Points on which the two editors differ and SceneMixer's guides describe its own handling. Order. The order points take on every editor page.