Hotel Lobby AI troubleshooting: subjects, motion and lost drafts
Start by separating a text-tool problem from a model-output problem. DuoFrame can validate and recover a draft; it cannot inspect your video or prove that a suggested prompt change will improve a model result. The examples below are diagnostic proposals, not tested render fixes.
Written and documentation checked
The two subjects swap sides or merge
First inspect the provider’s input order, then your reference map, then the edited prompt. Does one sentence place the adult on the left while another puts the cat there? Remove the contradiction before adding more descriptive words. In ordered-reference mode, confirm the actual Element mapping. In image-to-video mode, check whether the starting frame already contains the intended separation.
If the frame is ambiguous, revising the input may be a more useful experiment than adding repeated left/right commands. Record what you changed so the next output can be compared fairly.
A fixed shot moves, or the scene changes
Look for mixed directions such as “locked shot” plus “orbit”, “pan” or “push in”. Choose one camera intention for the first test. For motion-first input, use short, positive movement descriptions consistent with the first frame; do not treat every negative-prompt technique as transferable between models. The helper flags some English camera conflicts, but its checks are reminders rather than a full language or video analyzer.
The performance does not match a reference clip
A text prompt cannot contain the full motion record of a source video. Check whether the selected service supports the video-editing or motion-transfer input you actually need. Prepare an authorized clip and a preservation/replacement brief; verify the service’s current controls. Do not pay for repeated text-only attempts while assuming exact choreography or lip sync is guaranteed.
Copy, save or import failed
| Symptom | Safe next step |
|---|---|
| Clipboard unavailable | Use Select text and your device’s Copy command, or download TXT. |
| Storage blocked or full | Keep this tab open and export JSON; no account is required. |
| Invalid or unsupported JSON | Current work stays intact. Use a complete original export; do not change schema numbers to force an import. |
| Settings differ from the draft | Review your manual edits, then regenerate explicitly or export with the warning. |
| Changed the wrong draft | Undo the last replacement before doing another replacement. |
| Language transfer unavailable | Export JSON before navigating. The current tab keeps your draft when transfer fails. |
A shared link does not contain the draft
That is intentional. The setup link shares only workflow, camera and frame. It omits subject descriptions, reference labels, notes, checklist, history and edited text. The recipient adds their own material. For a complete collaboration handoff, review and deliberately send a JSON/TXT file yourself; the site does not send it for you. Links on a private preview still require access to that preview.
Decide what to try next
Choose one observable failure, note one input or instruction change, and keep the previous version. Download the brief to record the actual provider result later. If the issue is file rights, access, billing or unsupported inputs, resolve that at the relevant source before another render. Repeated clicking is not a recovery strategy for an uncertain paid request.
Sources and limits
Provider documentation supports the input distinctions. Practical checklists and example revisions here are original preparation advice. No real render, user study, success rate or cost result is claimed.