How to direct a text animation beat by beat
Describe the animation as a sequence of arrivals and exits to Vizard Agent — what comes in, from where, when, and how it goes. It builds each version and renders a contact strip of that version's key phases, so you judge the movement on frames instead of trying to remember what happened, and it rebuilds an effect more simply when the elaborate construction turns out unstable.
What is the short version?
An animation is a list of events and almost nobody writes it as one. "Make it dynamic" produces something, and then you spend four rounds discovering that what you actually meant was a specific order of arrivals with a specific exit.
- Go to Vizard Agent with the words and the logo.
- Say what arrives, from where, and in what order.
- Say how long the whole thing runs.
What do you need before you start?
The text, the assets and a rough choreography. It does not need to be technical — "the first line comes in from a distance, the second follows a moment later, then both blow away to the right while the web address arrives from behind" is a complete brief.
- The words. Exactly, and in order.
- Your logo, and where it ends up.
- The order of arrivals. What is on screen when.
- How things leave. Cut, fade, blown away.
- The total length. Including the held ending.
What do you type into Vizard Agent?
Describe motion in terms of position and time. "Dynamic" and "smooth" are the two words that get used and neither says anything a build can be checked against; "starts small and comes towards the camera over two seconds" does.
Prompt
Variants worth knowing:
- "Arrives a moment later." An order, not a feeling.
- "Blow them away to the right." An exit with a direction.
- "Eight seconds including the hold." Where the time goes.
What does Vizard Agent actually do?
Here is the order Vizard Agent worked in on a real transparent overlay that went through eight separate versions before it was right. Every one of those versions gets previewed the same way, which is what makes eight rounds affordable to sit through rather than exhausting.
- Checks the available assets and the graphics options.
- Renders the first version as a transparent overlay.
- Builds a contact preview of the animation's key moments.
- Checks the pacing and legibility across the whole overlay.
- Re-renders with a larger title and the extra text removed.
- Verifies the entrances, the wording and the space for the logo.
- Renders a longer, more dynamic version with a growing element.
- Removes that element and slows the zoom so it reads.
- Rebuilds in a plain bold face at the requested length.
- Enlarges the type substantially and re-previews.
- Adds the exit — the first lines flying off into the distance.
- Loads a verified recipe for the wind scatter.
- Checks which break-up effects are actually available.
- Rebuilds the scatter more simply when the first construction proves unstable.
- Verifies the order, the exit and the final held state.
Step three is what makes this workable. An animation watched at speed leaves you with an impression; a strip of its phases laid out as frames lets you see that the second line arrives too early, which is the kind of note that actually moves a build forward.
Step fourteen is the judgement worth copying. An elaborate particle effect that renders differently each time is worse than a simpler one that behaves, and swapping construction rather than adding fixes is usually the shorter path to something you can ship.
What does the result look like?
An overlay that does what you described in the order you described it: each line arriving where you said from where you said, the exit going the way you asked, and the logo holding at the end for the time you allowed.
Because it is transparent, it drops over any footage you like.
When does this not work well?
Complex effects are the least predictable part of any of this. Particle scatters, physical simulations and anything with randomness built into it will vary between renders, so a choreography that depends on exactly where one fragment lands is asking Vizard Agent for trouble.
- Randomised effects. They differ every render.
- Very short animations. No room for a sequence of beats.
- Too many arrivals. Nothing gets read.
- Tiny type in motion. Movement costs legibility.
- An exact reference. Matching a specific effect frame for frame is harder.
How do you fix a result that came back wrong?
Talk about timing and position rather than about mood. Vizard Agent keeps every version it built and the phase preview that went with it, so a note like "the second line should come in earlier" changes a single number rather than restarting the whole animation.
- "The second line is too late." Its entrance moved earlier.
- "I cannot see the zoom happening." Slowed so the movement reads.
- "The scatter looks different every time." Rebuilt more simply.
- "The text is too small." Enlarged and re-previewed.
How does Vizard Agent compare to doing it yourself?
By hand each version is watched, which is slow and imprecise, and the notes that come back are about feel rather than about frames. It is also normal to keep patching a misbehaving effect rather than replacing it, because the patches feel like progress.
| By hand | Vizard Agent | |
|---|---|---|
| Reviewing a version | Watching it | A contact strip of its phases |
| Notes | "More dynamic" | "The second line, half a second earlier" |
| An unstable effect | Patched | Rebuilt more simply |
| Iterations | Expensive | Cheap enough to do eight |
| The ending | Whatever is left | Held for a stated time |
Common questions
Can I get it as a transparent overlay? Yes. Vizard Agent renders it with alpha so it drops over footage.
How many rounds is normal? Several, and Vizard Agent makes each one cheap to review.
Can I specify the font? Yes. Name it and Vizard Agent uses it.
Can text leave rather than just fade? Yes. Say the direction and Vizard Agent builds the exit.
Will a particle effect look the same each time? Not exactly. Vizard Agent will suggest a stabler build if it matters.
Can two things happen at once? Yes. Say what overlaps and Vizard Agent times them together.
How do I judge the pacing? On the phase strip. Vizard Agent renders it with every version.
Can it match an animation I have seen? Approximately. Vizard Agent studies its mechanics.
Does the length include the hold? Say so either way; Vizard Agent works to what you state.
Can it leave room for my logo? Yes. Vizard Agent verifies the space before delivering.
What about vertical? Yes. Vizard Agent builds the choreography for the format.
Can I change one beat only? Yes. That is what the versions are kept for.
Will it work over any footage? If it is transparent, yes. Check contrast against dark shots.
Why review frames rather than watch it? Because eight seconds at speed gives you a feeling, and a strip of its phases gives you the note that fixes it.