Choose a preview start position that contains the scene, motion, or transition relevant to the setting you want to check, then set a duration long enough to observe that issue. HandBrake lets you choose both the preview position and duration, but the result is an encoded portion of the source, not a full-film check. Treat each preview as evidence about that sample only.
Match the sample to the question
First state the question in observable terms: for example, “Can I see detail in this fast pan?” or “Does the change in lighting reveal banding?” Locate a part of the source where that condition occurs. A calm shot cannot answer a question about fast motion, and a preview that ends before a transition cannot show what happens across it.
Choose duration by the event you need to see, not by a universal number. Include enough time before and after a change to judge its context; for a steady scene, include enough continuous material to observe the feature. These are sampling recommendations, not HandBrake rules. Its documented controls let you set a start position and a duration in seconds, then run Live Preview and use playback controls when it is ready. See HandBrake’s preview workflow.
Build a small acceptance worksheet
Use a separate row for each question you want the preview to answer. The following timeline and observations are hypothetical, not a software test or a guarantee of what any setting will produce. Assume a 12-minute source with a quick pan near 02:10, a dissolve near 06:00, and dark foliage near 09:20. The times and durations are example choices; choose actual positions from your own source.
| Question and sample | Start | Duration | Hypothetical observation | Still not covered |
|---|---|---|---|---|
| Fine detail during the pan | 02:06 | 8 sec | Edges look softer during movement than in the preceding frames | Other motion, later scenes, whole-film consistency |
| Change across the dissolve | 05:56 | 10 sec | The transition is visible; inspect both sides at playback speed | Other transitions and scene changes |
| Noise in dark foliage | 09:16 | 12 sec | Shadows look noisy in this sample | Other dark scenes, highlights, full-duration playback |
Record the setting or preset used alongside each row so you know what the observation applies to. If the sample does not contain the relevant event, mark it inconclusive and select another position instead of treating an unrelated image as a pass.
Interpret results and choose the next step
Generate the preview, wait for it to finish, and play the sample. Compare the result with the specific question in your worksheet. If it looks poor or otherwise unexpected, HandBrake’s documentation suggests adjusting quality or selecting a different preset, then creating another preview. For quality changes, the guide recommends small adjustments and explains that the quality control’s direction increases or decreases quality; encoder scales and values are not interchangeable. See HandBrake’s quality guidance.
A passing sample supports only a narrow statement: the observed output looked acceptable in that sampled material for the setting being examined. It does not establish that every scene, transition, audio passage, or the complete encode will meet the delivery requirement. When a finding may depend on different content, add a preview at another relevant position. For full-film acceptance, encode the complete output and review that output against your requirements.
Common questions
Is a longer preview automatically more useful? No. Length helps only if it includes material relevant to the question. A longer sample from the wrong kind of scene may still miss the issue.
Should I use the same duration for every check? Not necessarily. Choose enough time to see the relevant event and its context. A brief static detail check and a scene transition may need different sample lengths.
Does a good preview prove the full encode is correct? No. It is a test run on a small source portion. Use it to screen settings, then judge the complete encoded output separately.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.