How to tell whether a faster render preset actually cost you quality
Ask Vizard Agent for a 1:1 crop of the render beside the same crop of the source, one render pixel to one screen pixel. Watching the video full-frame cannot show you compression loss because your screen is already scaling it down, and the crop has to come from the hardest footage in the job rather than an easy shot.
What do you type into Vizard Agent?
Ask Vizard Agent for the comparison rather than a verdict. Whether the quality is acceptable is a judgement you should make on evidence of your own, and the evidence is two crops side by side. Name the hardest sequence if you know it, the rain, the crowd or the foliage, because that's the shot the decision rests on.
Prompt
What does Vizard Agent actually do?
Most of it is diagnosis rather than encoding. A preset that looks identical on a talking head can visibly smear a field of grass, so the test runs on the densest footage. And the preset change comes late, after every other explanation for the slowness has been ruled out. In the session behind this article it:
- Paused an hour-long render that was running far too slowly, and benchmarked the encoder settings on the dense field footage specifically.
- Tested the storage speed and looked for local scratch space.
- Compared a 1:1 crop of the render against the source, side by side, and made a tighter crop where the first wasn't decisive.
- Isolated whether storage or the processor was the bottleneck, restarted with thread limits so the encoders stopped competing, and checked the machine's actual processor quota.
- Compared the two presets' quality directly before committing.
When does this not work well?
A crop comparison only tells you about the shot it came from. Compression artefacts depend on content, so a clean result on one sequence guarantees nothing for another, and grain, rain and confetti each fail differently, which Vizard Agent has to test for separately. Platforms re-encode your master anyway, and a machine under other load gives benchmarks you can't repeat.
Common questions
Why is watching it back not enough? Because your screen scales the picture. Vizard Agent compares at actual pixels.
What if both look the same? Then take the faster preset. Vizard Agent treats that as a real result, not a failure.
Could the slowness be something else? Often. Vizard Agent checks storage and processor load before blaming the encoder.