この技術ドキュメントは英語で提供されています。インターフェースは選択した言語に従います。
Five tips and common fixes
Start with a short video and keep notes about the results you like. The template, model and environment all affect what you can produce.
1. Templates are code you can adapt
Within the package license, replace text, images, audio and parameters, or discuss changes to code, motion and style. What is possible depends on the template and runtime. Agree on concrete changes, save a new version and preserve approved work.
Check the package and asset licenses before redistributing templates, fonts, music or examples. Editing content does not change the original permissions.
2. Check updates before starting
Ask the assistant to check the official source, explain changes and preserve the original package and project. Assess the effect on existing work before upgrading. New projects may benefit from a suitable newer version; ongoing work should not lose its revisions.
3. Keep each production in its own session
Keep inputs, decisions and revisions in one project. Use separate working folders for concurrent projects and consider memory, rendering load and usage quotas. Avoid having multiple sessions edit the same file.
Save preferences such as caption length, preview approval and music choices in project notes. Transfer those notes and sources when changing assistants, while checking each new video's requirements.
4. Choose a capable model for complex changes
Verify file and execution tools first. For complex motion or code work, choose an available model suited to coding and multi-step tasks; increase reasoning effort where useful. Product names and settings differ. Higher effort can cost more time or money and does not guarantee success.
Use a short preview for simple changes and staged review for complex work. A model version or authoring attribution in an example is not a requirement for every template.
5. Expect first-time setup
The first run may require runtime tools, a browser, fonts and dependencies. Ask what is being prepared, whether it succeeded and what is missing. Reuse a working environment. Diagnose download, permission or resource failures before repeatedly reinstalling or overwriting projects.
Common problems
The assistant does not recognize .motion
Explain that it is a MotionGit template package. Have a local tool inspect it and read its instructions. Chat-only clients can use the README and parameter requirements to prepare a handoff; changing an extension does not create rendering tools.
Matching assets, captions and narration
Map each asset to a line or shot. Use real audio to check timing, sentence coverage, numbers and negations. Review generated text and transcription. Confirm rights and costs before using portraits, cloned voices or paid media generation.
The export differs from the preview
Play the actual output, record the problem timestamp, dimensions and audio behavior, and retain logs and the latest successful version. Fix a copy and verify a new export. “Exported” in chat is not file acceptance.
Switching assistants or making larger changes
Save sources, assets, preferences and revision history. Explain what is approved and what remains to change so the next assistant can continue from the current state.
Getting help or sharing your work
Use the help center or an existing author community. Include the template and version, operating system, assistant client, reproduction steps, error and relevant timestamps. Use community links published by the author or website. Remove keys, personal information and private assets from public materials. Check publishing rights before sharing finished work.