Two-subject reference checklist: rights, order and framing
A useful reference checklist prevents avoidable input mistakes. It cannot certify legal rights or predict whether a model will preserve a face. Keep the actual permission documents separately; checking a box only records your own preparation.
Written and documentation checked
1. Record the source of every input
For each portrait, pet photo, starting frame, source clip and audio track, note where it came from and why you can use it for this project. A public download button is not a rights record. Permission for a photograph does not automatically establish permission for an unrelated video or song. If the scope is uncertain, leave that input out until it is clarified. This is a planning checklist, not legal advice or a license assessment.
| Record | Example field, not verified evidence |
|---|---|
| Input label | portrait-left.jpg |
| Owner / permission location | Your own record, stored outside the helper |
| Intended use | Private draft, public post, or a separately approved use |
| Limitations to check | Editing, synthetic use, audio and redistribution |
2. Prepare for the selected input type
For separate-reference workflows, use clearly distinguishable subjects and label each role before visiting the provider. For image-to-video, inspect the whole starting frame: are both subjects visible, separate and correctly positioned? Do not assume a provider accepts the same image formats, dimensions or number of references as another. Check its current documentation.
For a person and a pet, describe the species and intended pose plainly. Seated cats, hands and paws near a microphone are useful review points, not guaranteed model strengths. Pet examples in DuoFrame are writing and visual concepts, not proof of a generated result.
3. Keep a simple reference map
Use the left reference label and right reference label as reminders for yourself. The helper does not open those files. In a Kling O1 reference workflow, check the provider’s ordered Element controls against your map before submitting. If you swap sides, swap each subject’s action as well. Re-read any manually edited prompt because the helper intentionally preserves it when settings change.
4. Check the frame and the cost outside the helper
The intended frame in a brief is a note, not a remote setting. Select the same frame and a currently supported duration at the provider. Read its actual quote before submitting; we do not maintain a universal price or success-rate table. A failed render may still have a cost under that service’s terms.
5. Export a handoff that can be checked
Mark preparation items only after checking them. Save a named local version, then download TXT for the production brief or JSON to continue editing later. Those files contain your text and checklist; review them before sending them to anyone. The safe setup link carries only three choices, so it is suitable when another person should begin with the same workflow without receiving your private draft.
After a real run, keep the output location, model/version, date, input permission record and observed limitations together. Until then, label the case “not render-tested”. A checked checklist or a generated prompt is not a successful video.
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.