How to get an editable project as well as the finished video
Tell Vizard Agent that the on-screen text has to stay editable and name the application it will be opened in. It builds those captions and prompts as native text layers rather than rendered images, then copies the project to a fresh folder and opens it there — because a project that works where it was made proves nothing about the machine it is being sent to.
What is the short version?
Rendered text is final text. If the words on screen are clinical terminology, prices, names or dates, then sooner or later somebody will want to correct one of them, and correcting a rendered graphic means coming back to you and waiting for another render.
- Tell Vizard Agent which text must stay editable.
- Name the application whoever edits it will use.
- Ask for the project tested from a fresh folder.
What do you need before you start?
The video, and a clear idea of who edits it next. Vizard Agent builds the project for a named application, so "editable" on its own is not enough — the format has to match what the person on the other end actually opens.
- The source material. As usual.
- Which text is editable. Prompts, captions, cards.
- Which application. The one they have, not the one you have.
- Who is checking it. A clinician, a lawyer, a client.
- Whether the render is final. Both are delivered.
What do you type into Vizard Agent?
Name the application to Vizard Agent, not the idea. The word "editable" covers half a dozen mutually incompatible things, and the only one that actually helps anybody is a project file that opens in the software already sitting on somebody else's computer.
Prompt
Variants worth knowing:
- "Editable text rather than baked-in graphics." The distinction.
- "A project that opens in [the application]." Names the format.
- "Test it from a fresh folder." The check that matters.
What does Vizard Agent actually do?
Here is the Vizard Agent sequence on a real teaching video delivered with an editable text layer alongside it. Notice how much of the list is verification rather than construction: building the project is straightforward, and proving that it opens somewhere else is where the work actually goes.
- Reviews the source and identifies the terms that need checking.
- Plans the edit with editable prompts and separate captions.
- Verifies the editable-project format before committing to it.
- Validates that the text actually renders in the target application.
- Resolves a missing dependency rather than handing over an untested file.
- Checks how the native editable text looks in the finished video.
- Renders the master and builds the project alongside it.
- Opens the project from a fresh folder to catch missing files.
- Confirms the relocated project reproduces the layout.
- Packages the editable files and checks the timings still match.
Step eight is the whole discipline. A project opened where it was built finds every asset by accident, and the first thing the recipient discovers is a timeline of offline clips.
Step five is a habit worth naming. Handing over a project you could not open yourself is worse than handing over nothing, because the recipient assumes the problem is at their end.
Step ten catches the quiet mismatch. If the master is re-rendered after an adjustment and the project is not rebuilt, the editable version now describes a different video, and the captions line up with neither.
What does the result look like?
Two deliverables that agree with each other. A finished master somebody can publish, and a project they can open, retype a term in, and export again — and Vizard Agent confirms it opened cleanly somewhere other than where it was built.
When does this not work well?
Not everything survives as an editable layer. Complex motion graphics, generated shots and anything built by a tool the recipient does not have will arrive as flat video whatever the project format, and pretending otherwise just moves the disappointment later.
- Complex animation. It flattens on the way out.
- An application they do not have. The format has to match.
- Generated footage. It is video, not a layer.
- Fonts they lack. The text will reflow on their machine.
- Very large projects. Linked media becomes a delivery problem.
How do you fix a result that came back wrong?
Say what happened when they opened it. "Offline media" and "the text is not editable" are two quite different failures as far as Vizard Agent is concerned — one is a packaging problem, the other is a decision about how the text was built in the first place.
- "The clips are offline." The media is packaged with the project.
- "The text is a picture." Those layers are rebuilt as native text.
- "The font is wrong on my machine." Fonts are supplied or substituted.
- "It does not match the video." The project is rebuilt from the final render.
How does Vizard Agent compare to doing it yourself?
By hand you export the project, it opens fine on your machine, and you send it. The recipient opens a timeline of missing files, cannot tell whether that is your fault or theirs, and asks you to make the change after all.
| By hand | Vizard Agent | |
|---|---|---|
| Text on screen | Rendered into the picture | Native editable layers |
| The format | Whatever you use | The one they open |
| Testing | On the machine that built it | From a fresh folder |
| Missing assets | Found by the recipient | Found before delivery |
| Master and project | Can drift apart | Checked against each other |
Common questions
Which application should I name? Whichever the person editing has. Vizard Agent builds for that one.
Can it deliver more than one format? Yes, though Vizard Agent has to test each one. Say which ones matter.
What if they do not have my fonts? Vizard Agent supplies them or substitutes one that holds the layout.
Will complex graphics stay editable? Usually not. Vizard Agent will tell you which parts flatten.
Why test from another folder? Because a project opened where it was built finds its media by accident.
Can I get the captions separately too? Yes. A subtitle file alongside the project is usually worth having.
What if they change the timing? Then the render and the project diverge. Vizard Agent notes what is safe to change.
Does this cost more? Somewhat, mostly in verification. Far less than a round trip for one word.
Can it package the media as well? Yes. Ask Vizard Agent for a self-contained package rather than linked files.
Will the editable version look identical? Vizard Agent checks that it reproduces the layout, and reports anything that differs.
What about a second version of the video? Vizard Agent can build a separate project for it without touching the first.
Can I edit it and send it back? Yes, and Vizard Agent can pick the changed project up from there.
Is a subtitle file enough on its own? For captions, often. For on-screen prompts and cards, ask Vizard Agent for the project.
What if I do not know what they use? Ask them before the build. It is the one detail that cannot be worked around.