When an animated character looks wrong, another video generation is only one possible next step. The wrong detail may already be in the reference image. It may appear in the scene still before animation begins. Or two acceptable clips may look inconsistent only when placed together.
Find the earliest visible mismatch against the approved design, then repair that stage and recheck the work that depends on it. This gives you a concrete decision: revise the design reference, replace one scene image, regenerate one motion shot, or change the edit. It also prevents a familiar mistake—spending credits to animate an image that already contains the problem.
Dreamina can support both the still-image and video parts of the process. Keep their outputs separate while diagnosing the issue, so a new candidate does not overwrite the evidence you need to compare.
- Make the symptom specific enough to investigate
- Gather the exact files that produced the shot
- A real example: a repeated mistake in the master
- Use the first mismatch to choose the repair
- Inspect frames without losing the evidence
- Carry out a bounded retry in Dreamina
- Close the issue with an actual decision
Make the symptom specific enough to investigate
“The character changed” is a useful reaction, but a poor revision brief. Name the feature, the expected state and the first place you noticed the discrepancy. For example: “The scarf knot belongs on the character's left; it appears on the other side when the character faces the camera in the second shot.”
Then distinguish a design discrepancy from a change the shot was supposed to create. A face in profile has a different outline from a face seen straight on. Warm light can change the apparent color of orange fur. A sleeve can cover a wrist marking. None of those observations alone establishes that the character's identity has been regenerated incorrectly.
Use these questions to narrow the symptom:
Do not classify an obscured detail as correct or incorrect. Mark it as unknown, then inspect another frame or a reference that reveals it. If the only usable view never shows the disputed feature, you may need a clearer shot before making a reliable judgment.
Gather the exact files that produced the shot
For one affected shot, collect the approved design description, the accepted master image, the actual scene still supplied to the video model, and the downloaded clip. Add the shot immediately before and after it if the discrepancy appears at a cut. Keep the prompt and model settings with the files.
The word actual matters. A corrected still saved later is not evidence that the video used it. Compare the uploaded file or saved input record with the image on your desk. When several candidates look almost identical, a clear version name and recorded input relationship can prevent you from troubleshooting the wrong branch.
Arrange the material in production order:
Approved design → master → scene still → generated motion → edited sequence.
Inspect from left to right until you find the first stage where the visible result conflicts with the approved requirement. A downstream clip may contain several other imperfections, but first identify whether the disputed detail was inherited or newly introduced.
If you do not have an accepted design, pause the diagnosis long enough to decide what the character is supposed to be. The character reference preparation guide explains how to establish a master, required views and visible acceptance criteria. A missing design decision cannot be solved merely by choosing whichever later image looks most appealing.
A real example: a repeated mistake in the master
In a saved Dreamina browser case from October 14, 2026, an orange fox mascot with a teal scarf was generated. The written prompts requested three dark tail bands. The first still visibly contained two. Two subsequent stills—one pointing toward a blank sign and one raising a foot beside a box—also showed two bands.
Both later stills used the original waving fox as their image reference. They were separate branches from the same source, not a chain in which the third image inherited the second. The saved prompts, output files and reference records establish that relationship.
The pointing pose retained two visible tail bands from the original reference, although the written requirement asked for three. This is an unchanged original still from the case, not a corrected example.
The diagnosis starts at the master. Repeating two bands can look consistent with that image while still violating the brief. Calling this “the video lost a stripe” would put the error at the wrong stage. A later video retry cannot, by itself, establish that the reference design has been fixed.
The corrective choice is explicit: approve a two-band design and update the brief, or create and approve a three-band master before replacing the affected scene images. The case does not contain a validated three-band repair. That repair remains a proposed next action, and each resulting image would need inspection before being used.
This example supplies a diagnostic method, not a failure rate for Dreamina or a claim that every feature in the outputs was identical. The three-shot mascot case follows the complete reference and clip relationships; here, the useful finding is the earliest known mismatch.
Use the first mismatch to choose the repair
The table identifies where to start. It does not imply that every problem has one cause or that the first repair will succeed. Use the branches below to make the next attempt informative.
When the master is wrong
Return to the still-image stage. Keep a list of the feature that must change and the accepted features that should remain. For the fox example, the target is the tail-band count, while the face, scarf, pose and general illustration style should be checked for unintended changes.
A proposed revision prompt could read:
Revise this fox reference so the tail shows exactly three separate dark bands, with orange fur between them. Retain the existing face, teal scarf, body proportions, pose and plain background. Keep the whole tail visible for inspection. Do not add a second character or additional panels.
This prompt has not been executed as a repair in the saved case. Treat its preservation instructions as requests. Inspect the entire result after checking the tail: a corrected band count accompanied by an unfamiliar face is not an accepted replacement master.
If repeated revisions solve one feature while damaging another, change the preparation route. Simplify the pose to expose the feature, prepare a clearer reference, or use an editing method that gives the required direct control. Decide which result becomes the new master before regenerating derived scenes. Keep the previous version identifiable so you can see which clips still depend on it.
When only the scene still is wrong
Preserve the accepted master and revise the affected scene. A scene image adds pose, environment, lighting and framing; it can introduce a discrepancy even when the identity reference is correct. Replacing the master to match that one bad scene would spread the change to otherwise acceptable work.
Make the scene request more specific about the failed relationship. If a scarf appears on the wrong side, describe the character's own left or right and check whether the view has changed. If the face becomes unfamiliar in an extreme angle, prepare an approved view for that angle or choose a less demanding composition that still serves the story.
Keep scene intent in the revision. A technically accurate neutral portrait cannot replace a pointing scene if the story depends on the point. The useful replacement must satisfy both identity and action preparation. Approve that still, then use the exact new file as the input to the affected video shot.
When the change begins during motion
First verify that the initial video frame is close enough to the intended starting image for the shot's requirements. Then inspect the action, especially turns, occlusion and the point where a hand or prop crosses the disputed feature. Do not infer a precise failure time from only a first and last frame.
Make one meaningful change to the motion request. Suppose a proposed shot combines a full turn, a jump and a moving camera, and the face changes during the turn. A useful diagnostic retry might keep the camera fixed and reduce the turn while preserving the story's essential action. It can help isolate a simpler usable shot; it does not prove which internal model mechanism caused the earlier failure.
For an illustrative fixed-camera wave, a proposed prompt is:
Use the supplied scene image as the visual reference. The fox makes one small welcoming wave while its body remains in place. Keep the camera fixed and the face clearly visible. Preserve the accepted face shape, scarf placement, colors and tail markings. Avoid a body turn, jump or additional character.
Judge the whole replacement clip, including what happens before and after the wave. If the action itself requires an occluded turn or precise repeated poses that the available route cannot deliver acceptably, reduce the shot's demands or move that shot to a more directly controlled animation process. There is no useful universal retry count; stop when another attempt lacks a specific reason to improve the result within your project's remaining budget.
When the problem is at the cut
Place the final usable moment of one shot beside the first usable moment of the next. Compare facing direction, pose, screen position, lighting and action state. Two recognizable versions of the same fox can still make an awkward sequence if the first shot ends facing right and the next unexpectedly starts facing left.
If the clips contain better matching moments, adjust the selected ranges. If a meaningful intermediate action is missing, a transition effect cannot supply it automatically. You may need a different opening pose, a replacement shot, or a story-motivated cutaway. Do not flip a clip casually: it can reverse asymmetric costume details as well as screen direction.
A dissolve can be an intentional stylistic choice, but overlapping two different faces can also make a discrepancy more visible. Review the actual transition before deciding that it helps. The animation assembly guide covers the broader edit, pacing and sound decisions once the individual shots are available.
Inspect frames without losing the evidence
Watch the downloaded clip at normal speed first to understand the action. Then pause around the suspected change, inspect nearby frames, and note the earliest frame where the feature is clearly wrong. Keep “first observed wrong frame” separate from “the exact frame where it began” unless you have checked the intervening frames.
Create a compact comparison with the approved reference, the exact scene input, a frame before the discrepancy, and a frame showing it. For a cut problem, use the actual outgoing and incoming frames. Do not stretch one image to force its proportions to match another. Similar display size helps comparison, but cropping and angle differences must remain apparent.
If you use Premiere, Adobe documents an Export Frame operation: position the playhead, select the camera-shaped Export Frame control in the Source or Program Monitor, then choose a name, format and destination. Add the control through the Monitor's Button Editor if it is absent. Save the selected frames with their shot identity and time so the comparison can be repeated.
Frame inspection answers a different question from complete playback. A few clear images can establish a visible mismatch, but they cannot prove that the rest of the clip is stable. After a repair, watch the complete replacement and inspect its high-risk moments. If audio or dialogue is part of the scene, review that separately; a correct face in still frames does not establish synchronization or usable sound.
Carry out a bounded retry in Dreamina
For an image-level repair, open AI Image, upload the relevant reference with +, and state the single change and the features to retain. Choose the available model, aspect ratio and resolution, generate, inspect, and download the accepted candidate under a new version name. The current Seedream 5.0 Pro guide documents that image workflow. Keep the old file alongside its record until its dependents have been checked.
For a video-level retry, the current Seedance 2.5 instructions describe AI Video, model selection, Omni reference, uploads through +, and @ references in the prompt. Choose the controls actually available in your account, identify the scene image's role, set the required format and duration, and check the displayed cost before generating. Review the result and download it before comparing it with the prior attempt. A newly selected model or mode is a changed condition, so record it instead of presenting the retry as the same setup.
Keep the retry brief small enough to judge. Write down the current file, the failed feature, the change requested and the acceptance condition. “Fix consistency” leaves the next reviewer guessing; “keep the scarf knot on the character's left throughout this frontal wave” identifies a visible outcome.
Close the issue with an actual decision
A repair is complete when the replacement meets the relevant design and shot requirements and still works in the sequence. Saving a new file or seeing one improved detail is not enough. Record one of three decisions: accepted replacement, accepted with a deliberately revised brief, or still unresolved.
For example, if a three-band master is eventually approved, note which scene stills were regenerated from it and which clips were replaced. Do not silently mix those clips with old two-band shots. If the team instead approves two bands, update the design record so later reviewers use the same requirement.
Leave the successful parts alone unless the correction affects them. A wrong scarf in one scene need not trigger a complete project restart; a changed master may affect several shots. That distinction is the point of tracing the error to its first visible stage.
Open the affected assets in Dreamina and your editor with one question in mind: what is the earliest file that fails the approved requirement? The answer tells you where to make the next change—and which results you must inspect before using it.