Assets & tasks / PRACTICAL CHECK
Is the product clip broken, or is playback stuttering?
Start with the completed file before requesting another generation. A pause in a browser player can reflect delivery or playback trouble; a warped product at the same source frames is a content problem. Check retrieval, repeatability and another suitable viewing route, then record the evidence for the appropriate next action.
Confirm that you are reviewing a completed result
Check the task state and selected result first. A pending task is not a finished defective clip. For a completed result, download the original through the available account workflow and confirm that the transfer finishes. Keep its filename and the task or result reference so you know which file is being reviewed.
In an illustrative speaker campaign, a browser preview stops during a slow camera slide. The merchant assumes the model froze the image. Before spending credits again, they retrieve the completed source and play it from the beginning locally. This comparison tests whether the symptom follows the footage rather than the particular streaming session.
Observe where and how the fault repeats
Play the same source more than once and note the approximate timestamp of the symptom. A pause at changing times is a different observation from a duplicated frame or product distortion at a repeatable position. Timing alone is not a diagnosis, but it helps choose the next check. Describe what happens rather than calling every interruption a failed generation.
Where available, compare a second suitable player or an external editor. Use the same unmodified source, not a re-encoded copy that introduces another variable. Step through the suspicious area to see whether the image content is coherent. A player unable to decode the file and a clearly decoded but inaccurate product require different investigation paths.
Route the symptom before choosing a remedy
| Observation | Next check | Avoid assuming |
|---|---|---|
| Download is incomplete or cannot open | Retrieve the same completed result again | That new generation is required |
| Browser pauses but local source plays smoothly | Delivery and player behavior | That the model encoded a pause |
| Same wrong product frames recur | Source content against real reference | That buffering caused the distortion |
| One editor drops frames during playback | Preview load and playback diagnostics | That dropped preview frames are missing from the file |
If no suitable route plays the file, record that as an unresolved delivery or decoding issue. Do not declare its product content approved or rejected before it can be inspected.
Separate playback load from encoded content
An editor can struggle to play a sequence in real time even when its source frames are present. Adobe’s dropped-frame indicator reports frames dropped during playback. That is a useful diagnostic observation, not proof that the source file contains missing images or that the generated product is accurate.
For the speaker, a smooth local view with a stable product points the team toward preview delivery. A repeated change to the grille pattern in the same frames points toward content review. If an export introduces the stutter while the clean source remains smooth, inspect that edit and export separately. Preserve the source to keep the comparison meaningful.
Report the result without unnecessary paid reproduction
Record the selected result, complete filename, viewing route, observed timestamp and whether another suitable route reproduced the symptom. Include a short description or appropriately scoped evidence if support needs it. Keep private account access and unrelated customer material out of the handoff; provide only what is needed to investigate the completed result.
Choose the next action from that record: resolve retrieval, investigate playback, repair an external export or review an actual generated-content defect. A new generation is justified only when it addresses a production problem that the current checks identify. Itemlume task status, source content and the publication player are separate parts of that decision.
Sources and further reading
Sources for this page were checked on . Platform rules can change; verify the current source before publishing. Prompt examples and workflow recommendations are Itemlume editorial guidance, not independently measured results.
Frequently asked questions
Does a stuttering preview prove the clip is broken?
No. Compare the completed downloaded source and record whether the symptom repeats.
Does the same timestamp guarantee a content defect?
No. It is a useful clue; inspect the source frames and another suitable playback route.
Should I regenerate before contacting support?
Not simply to reproduce playback trouble. First record the existing result and the checks that distinguish delivery, playback and content.
BUILD FROM A PRODUCT YOU KNOW
Put this workflow into practice with your own product.
Explore the relevant tool first. AI copy and concept planning are free after sign-in. Image and video generation require available credits and the applicable account access.
Open Assets & tasks Check pricing and credits