Skip to main content
At some point the story is finished and you need a file people can watch. This page covers the review that should come first, the render itself, and what you can do with the result.

​
Watch it end to end, once, before you judge it

This is a business video story, not a social clip. Pacing, argument and the way scenes hand over to each other only become visible when you watch the whole thing. Reviewing scene by scene tells you whether each scene is good and nothing at all about whether the story works.
Watch it once without stopping. Then go back for the details.

​
Before you render

  • Clear any failed background. A scene whose video background failed keeps a placeholder, and a placeholder renders into the finished file. Regenerate it, or replace it with a still.
  • Check the presenter is animated where you want them animated. Scenes still on the still image are cheaper and perfectly usable, but it should be a decision.
  • Read the on-screen text. Anything marked for timing review after a script change should be looked at and cleared.
  • Set your AI markers. See below.

​
AI markers

Every video LatentCast produces carries an invisible fingerprint and signed provenance data, always, whatever you choose here. AI markers control the visible part: the disclosure badge drawn into the picture. Open AI markers above the preview and you can set the badge’s style, light or dark tone, its corner, its size and its opacity, with a live view of how it will look on your own video.
Videos shared outside your organization must carry the visible badge under Article 50 of the EU AI Act. If you start a render without markers set, LatentCast warns you once and lets you continue, because the decision is yours. Read AI transparency for what is marked and how anyone can verify a file.

​
Two things called “generate video”

The Generate video button is a menu with two entries, and they do very different jobs. Proxy videos produce nothing you can send. They are the ingredient that makes the presenter move in the preview. Render them for the current scene, a selection of scenes, or all of them. A scene with no audio yet cannot be rendered and is listed as skipped.

​
Rendering the real thing

Choose Full video for sharing and you are taken to the Videos page, where a card tracks the work through its stages:
  1. Rendering — the picture is composed.
  2. Marking & signing — the invisible fingerprint and provenance signature are applied.
  3. Publishing and Encoding — the file is handed to streaming and prepared for every device.
  4. Finalizing, then Ready.
You can leave the page. A long video spends a noticeable while in marking and signing; the bar there is an estimate rather than measured progress, so a pause near the end is normal.
Signing off is not the same as rendering. Sign-off freezes the story so it can be personalized. Rendering makes a file. You can do either first, and personalization does not need a rendered video.

​
What you get

On the video’s page you can download the MP4, copy an embed code for your own site, and create a viewing page, which is the shareable page with a proper player and a link you can send. Two library-level features are worth knowing:
  • Tags. Free-form labels on a video, used to organise and filter a growing library.
  • Make public. A normal embed link is signed and expires. Making a video public creates a permanent, unsigned embed for pages where a signed link will not do.

​
If a render fails

The card shows the reason. There is no retry on the card: go back to the story and start the render again. Cancelling a render yourself also ends up shown as failed, which is expected rather than a problem. If the preview itself will not load, the placeholder usually names the reason, and Refresh preview is the first thing to try. You will also want it after a proxy render finishes while you were on another page.

​
Next

Preparing your recipient list

The next stage: who gets a version of this story.

Video stories and videos

Sign-off, and why the distinction matters.