How to be sure a graphic actually rendered into the video
Ask Vizard Agent to confirm the label is in the picture rather than in the build. A graphic can be generated correctly, composited by a command that reports success, and still be invisible in the output — so the check that means anything is whether those pixels exist in a rendered frame.
What is the short version?
Your video has a missing label. Everything in the build insists it is there: the file exists, the overlay step ran, nothing errored anywhere. The frame disagrees, and the frame is what ships, so that is what Vizard Agent checks.
- Ask Vizard Agent to verify each graphic on a rendered frame.
- If one is missing, ask which step lost it.
- Expect the fix to be a different compositing route, not a bigger label.
What do you need before you start?
The video and the list of what should be on screen. Vizard Agent can compare a frame against what the build intended, and a written list of the labels — with their moments — makes that comparison exact rather than impressionistic.
- The video. The rendered output, not a preview.
- What should appear. Each label and when.
- The source graphics. So they can be compared.
- The frame size. Labels are often placed off-frame.
- What you have already checked. It saves repeating it.
What do you type into Vizard Agent?
Ask for evidence rather than a status. "Is the label there?" invites a check of the build log; "show me the frame at 7.5 seconds with the label on it" can only be answered by looking at the picture.
Prompt
Variants worth knowing:
- "Whether its pixels actually landed." The real test.
- "Which stage lost it." Asks for a diagnosis.
- "Show me the frame." Evidence, not assurance.
What does Vizard Agent actually do?
Here is a stretch of the Vizard Agent sequence on an explainer whose animated labels were missing from the output. The diagnosis narrows steadily from the video as a whole down to a single compositing call that was dropping the layer.
- Animates the scene labels as a transparent overlay.
- Reviews the label overlay frames on their own.
- Rebuilds a chart with only the permitted labels.
- Animates the remaining labels for the later scenes.
- Composites the labels onto scene stills to check for collisions.
- Checks the placement across all three scenes.
- Probes the overlay's alpha channel and locates the text inside it.
- Measures the bounding boxes of the labels and the illustrations.
- Composites the labels at full resolution onto each scene.
- Checks whether the label pixels actually landed on the composites.
- Compares two different compositing routes so the labels actually show.
- Overlays the extracted label image with the other route to isolate the bug.
Step ten is the one worth adopting as a habit. It does not ask whether the overlay was applied; it asks whether the pixels are present in the result, which is a different question with a different answer surprisingly often.
Step seven is the first place to look. A transparent overlay with an empty or inverted alpha channel composites perfectly and shows nothing, and the file looks correct in every listing.
Step eleven is the fix. When one compositing route drops the layer, the answer is to use another and compare the outputs, rather than to make the label bigger and hope.
What does the result look like?
A video in which every label you asked for is visibly present at the moment it belongs, confirmed by Vizard Agent on rendered frames rather than in the build log, with the stage that was dropping them identified and replaced.
When does this not work well?
Some missing graphics are not a bug. A label placed outside the frame, one drawn in the same colour as the background, or one hidden behind another layer is present and invisible, and the fix is layout rather than compositing.
- Placed off-frame. Present in the file, outside the picture.
- Same colour as the background. Technically rendered.
- Behind another layer. Order, not compositing.
- Zero opacity. A setting rather than a fault.
- Only in the preview. The preview and the export differ.
How do you fix a result that came back wrong?
Say which label it is and at which second it should appear. Vizard Agent re-checks that exact frame, and the answer is nearly always one of three things: the label is outside the frame, it is behind something else, or the layer never made it into the render at all.
- "It is still missing at 7.5s." That frame is inspected and the route changed.
- "It appears but late." The overlay's timing is corrected.
- "It is behind the illustration." The layer order is changed.
- "It is cut off at the edge." The bounding box is measured and moved inside.
How does Vizard Agent compare to doing it yourself?
By hand you trust the editor's viewer, which is the one place a layer is guaranteed to appear. Exports are where layers go missing — a flattened alpha, an unsupported blend mode, a filter chain that drops an input — and the viewer will not tell you.
| By hand | Vizard Agent | |
|---|---|---|
| The check | The preview window | Pixels in a rendered frame |
| Missing layers | Made bigger, or re-added | Traced to the stage that dropped them |
| Alpha | Assumed | Probed directly |
| Placement | Eyeballed | Bounding boxes measured |
| Confidence | "It should be there" | A frame you can look at |
Common questions
Why would a label render in preview and not in the export? They are different paths, so Vizard Agent checks the export rather than the preview.
Can it check every graphic in a video? Yes. Give Vizard Agent the list and it verifies each one on a frame.
What is an alpha problem? Transparency that is empty or inverted, so the layer composites to nothing.
Can it tell me which step lost it? Yes. Vizard Agent isolates the stages one at a time until the layer disappears.
Is a bigger label a fix? Only if the problem was size, which it rarely is.
Does this apply to captions too? Yes, and Vizard Agent checks them the same way.
What about layers behind others? Vizard Agent measures the bounding boxes and reorders rather than resizing.
Can it prove a graphic tracked correctly? Yes, and that is a related check worth asking for on moving overlays.
How long does the verification take? Seconds per label, against minutes for a re-render.
Should I check every render? Check any render where a graphic was added or changed.
Can it compare two renders? Yes. Vizard Agent can show the same frame from both.
What if the graphic file itself is empty? Vizard Agent inspects the source before blaming the composite.
Does this happen with text as well as images? Yes, particularly with fonts that fail to load silently.
How do I check it myself? Export a frame at that timestamp and look at it at full size.
Can Vizard Agent check a batch of videos? Yes. Give it the list of labels and it verifies each video's frames in turn.
What if the label flickers rather than vanishing? That is a timing or tracking fault, and Vizard Agent inspects the frames either side of it.