How to cut around a transition that is already baked into your source clip
Tell Vizard Agent that the source already has transitions in it. It finds where each one starts and ends, pins clean entry and exit frames either side, trims the awkward boundary frames out, and will replace the built-in effects with plain crossfades if they are fighting the edit you are making.
What is the short version?
A clip exported from a phone editor is not raw footage — it is a finished edit, complete with wipes, flashes and speed changes baked into the picture. Cut it by timing and your shot begins on the tail of somebody else's transition.
- Go to Vizard Agent with the source.
- Say it has transitions already burnt in.
- Ask for clean frames either side of each one.
What do you need before you start?
The source and a decision about the existing effects. Vizard Agent can work around them or take them out, and those lead to different edits — keeping them means cutting to their rhythm, while replacing them means the new cut sets its own.
- The source clip. As exported.
- Whether the transitions stay. Keep, or replace.
- What you are cutting for. A short, usually.
- Whether the pace should change. Built-in effects fix it.
- Any speed changes. Those are baked in too.
What do you type into Vizard Agent?
Say the transitions are in the source, not in your edit. It is the sort of thing that is obvious watching the clip and invisible in an instruction, and without it a trim will be placed on timing alone.
Prompt
Variants worth knowing:
- "Burnt into the picture." Says it is not your effect.
- "Either side of each one." Two frames per transition.
- "Worth keeping or replaced." Asks for the judgement.
What does Vizard Agent actually do?
Here is the sequence on a real portrait cut made from a clip that had already been edited once. Notice that the first render happens before the transitions are dealt with, which is what makes them visible as a problem.
- Builds a dense timeline review sheet of the source.
- Finds the strongest spans for the short.
- Renders a first tighter cut.
- Pins clean entry and exit frames around the built-in transitions.
- Reviews the opening boundary frames.
- Reviews each transition group in turn.
- Reviews the ending boundary frames.
- Trims the awkward boundary frames and re-renders.
- Checks the corrected cut and its waveform.
- Replaces the distracting source transitions with clean crossfades.
- Verifies the result on a final watch-through.
Step three is worth doing before any of this rather than after. Rendering a first tighter cut is what makes the inherited transitions visible as a problem, because in the original clip they look like part of the material and only in your own edit do they start landing in the wrong places.
Step four is the difference between a clean cut and a puzzling one. A wipe occupies a range of frames rather than a moment, so the usable material begins after it finishes, and the only reliable way to find that is to look.
Step ten is the option people do not realise they have. Built-in transitions were chosen for a different edit at a different pace, and once they are identified they can be removed and replaced rather than worked around — which often makes the new cut noticeably calmer.
Step six exists because there is usually more than one. Reviewing them as separate groups rather than as a single sheet keeps each one's before-and-after together, which is how you tell a wipe from a flash from a speed change.
What does the result look like?
A short whose cuts land on actual picture rather than in the middle of somebody else's effect. If the built-in transitions were replaced as well, the whole thing also stops flashing at moments that had nothing to do with the edit you were making.
Vizard Agent tells you where each source transition sat, which is worth keeping for the next time you cut from the same file.
When does this not work well?
Some baked-in effects cannot be undone. A speed change, a heavy flash frame or a transition that covers the only usable moment leaves nothing behind to recover, and the honest answer is to cut elsewhere or ask for the original.
- Speed changes. The original frames are gone.
- Effects over the key moment. Nothing left underneath.
- Very short clips. Every second contains one.
- Full-frame flashes. They destroy the frames they cover.
- Heavy compression. The boundary frames are mush.
How do you fix a result that came back wrong?
Say which boundary and what you see there. Because Vizard Agent knows where each source transition sits, "there is still a flash at the second cut" points at a specific range rather than at the edit in general.
- "A flash survived." The boundary moves past it.
- "It cuts too late now." Trimmed back towards the transition.
- "Keep the original wipes." They stay; the cuts avoid them.
- "Can we get the raw file?" Always the better answer.
How does Vizard Agent compare to doing it yourself?
By hand the source is treated as footage and cut on timing, and the inherited half-transitions get blamed on the new edit. The usual response is to add a crossfade over the top, which layers one effect on another.
| By hand | Vizard Agent | |
|---|---|---|
| The source | Assumed to be raw | Recognised as an edit |
| Cut points | Placed on timing | Pinned to clean frames |
| A leftover wipe | Covered with a crossfade | Trimmed past, or replaced |
| Finding them | On the finished cut | Before the trim |
| The option to replace | Rarely considered | Offered |
Common questions
How do I know my source has them? If it was exported from an editing app it probably does, and Vizard Agent will confirm on the frames.
Can it remove a transition entirely? It can replace one, but Vizard Agent cannot recover frames it covered.
What about speed changes? Those are permanent. Vizard Agent will tell you where they are.
Should I keep the original effects? Only if your cut runs at the same pace. Vizard Agent will advise.
Will a crossfade hide it? It layers two effects. Vizard Agent will suggest trimming instead.
Can it find them automatically? Yes, and Vizard Agent shows you the boundary frames so you can confirm.
What if a transition covers the best moment? Then it is lost, and Vizard Agent will say so. Ask whoever exported it for the original.
Does this apply to stock footage? Sometimes. Vizard Agent finds them in compilation clips fairly often.
Can it list where they are? Yes. Vizard Agent reports each one, which helps if you cut from the file again.
Does it affect the audio? Audio transitions are separate; Vizard Agent checks the waveform too.
Will the cut get shorter? Slightly, since Vizard Agent trims the boundary frames out.
Can I keep some and replace others? Yes. Vizard Agent handles them individually.
Is the original always better? For editing, yes. An export has somebody else's decisions baked into it.
Why did my cut look glitchy? Because it started partway through an effect you did not add.