Vizard Agent

How to make a short story video about a renovation from nothing but a description

Last updated 2026-08-16 · 6 min read

Describe the story to Vizard Agent — a man clears the ground around an old house, then starts the work — and it builds the whole thing: a reference sheet so the man and the house stay the same, five generated scenes, narration, music and subtitles checked against the fonts actually installed.

What is the short version?

A process story is one of the most watched shapes on any feed: something neglected, someone starting work, the result. You do not need footage of a real renovation to tell it, but you do need every shot to show the same house and the same person.

  1. Go to Vizard Agent and describe what happens, in order.
  2. Say the length, the shape and the language.
  3. Say whether you want narration, subtitles or both.

What do you need before you start?

The story, in sequence. Vizard Agent generates everything else, and what it cannot invent for you is the order of events — which is the whole appeal of this format, since the satisfaction comes from watching things happen in the right sequence.

What do you type into Vizard Agent?

Write the story in plain sentences in your own language. Vizard Agent works out the scenes, the characters and the shot order from that, so a couple of lines describing what happens beats a formal brief or a shot list.

Prompt

Make a video showing how a man renovates an old house. He should first clean up around it and then start the work. Around [40] seconds, vertical.

Variants worth knowing:

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real generated story. The interesting stretch is the end — it did not accept its own subtitles, and chased the problem down to which font file was actually being loaded.

  1. Checks the generation and music tools and their options.
  2. Creates the reference sheet, the music and the first narration line in one pass.
  3. Listens back to the voice before recording the rest.
  4. Generates all five scenes and the remaining narration lines, checking the scene logs.
  5. Reviews every scene as a contact sheet and looks at the frames.
  6. Checks a scene's audio track, resolution and frame rate, then assembles the cut.
  7. Generates word timestamps and builds the subtitles from them.
  8. Renders, looks at the result, and is not satisfied with how the subtitles read.
  9. Checks which font is actually being used, tests two width corrections side by side, compares them, and re-renders with the one that works.

Steps 8 and 9 are the difference between finished and delivered. A subtitle that is technically present but hard to read is the most common way a good video is spoiled, and Vizard Agent looked at its own output and went back.

What does the result look like?

From the run this page is written from, probed on the delivered file: 1080x1920, H.264, 24fps, 38.62 seconds, AAC audio. Vertical, under forty seconds, five generated scenes with narration, music and burned-in subtitles in the language of the brief.

Vizard Agent watches and listens to the finished film once more before delivering it, which is how the subtitle problem was caught in the first place.

Timing was not measured separately for this kind of job. The closest measured work runs a median of 28 to 38 minutes end to end, with the middle half spread considerably wider. Across all projects the median cost by tier is Flash 47, Pro 55, Max 242, Ultra 263 credits.

When does this not work well?

Everything here is generated, so the story is only as convincing as generated video allows. Vizard Agent anchors the house and the man to one reference sheet, and physical work is among the harder things to generate believably.

How do you fix a result that came back wrong?

Name the scene or the element. Vizard Agent keeps the reference sheet, each generated scene, the narration and the subtitle file separately, so a re-styled subtitle or one regenerated shot leaves the rest of the film exactly as it was.

How does Vizard Agent compare to doing it yourself?

By hand this is a generation tool with no memory between shots, a text-to-speech pass, a music track and a subtitle file you have to time yourself — and at the end of it, a house that looks subtly different in all five scenes, which is the one thing the format cannot survive.

By hand Vizard Agent
Keeping the house the same Re-prompt each shot One reference sheet
Narration Generate and hope it fits Auditioned, then measured
Subtitles Type and time them Built from word timings
Bad subtitle rendering Ship it Font checked, corrections compared

Common questions

Do I need any footage? No. Vizard Agent generates every scene from your description, and your own photographs make it better if you have them.

Can it work in my language? Yes. Write the brief in it and Vizard Agent narrates and subtitles in the same language.

How many scenes fit in forty seconds? About five. Each holds for roughly eight seconds, which suits a process story.

Can it end on a before-and-after? Yes, and it is the strongest ending for this format. Ask for it explicitly.

Will the subtitles be readable? Vizard Agent checks the rendered result rather than trusting the file, and you can ask for larger text.

Can I use my own house photos? Yes. Upload them and Vizard Agent builds the story around your real building.

Can it add music? Yes. Vizard Agent searches for a track and mixes it under the narration rather than over it, and you can ask for a different one without touching the scenes.

Can I get a wide version? Yes, though vertical suits this format. Vizard Agent re-frames each scene rather than cropping.

Can it show a specific kind of building? Yes. Name it — a stone cottage, a terraced house — and the reference sheet is built to that.