lipsync

Lipsync

Scope and input roles

submit_lipsync takes an existing project video and the final speech audio whose words should be heard in the output. It changes mouth motion to match that audio. It does not translate words, create a voice or derive a new performance from a photo. For a new presenter performance from a likeness, use digital-human.

For any translation request, first load video-translation. It owns the route choice and may call this skill with independently prepared final audio. Do not restart translation or voice selection here.

If the user supplies final audio, reuse it directly. For a wholly new script, use voice to generate final speech, then obtain approval of that actual audio and its measured duration before paid rendering, as described below. A cloning sample is not final dialogue. If no mouth synchronization is requested, use dialogue replacement instead of this tool. Integrated HeyGen translation includes its own mouth synchronization; do not lip-sync its output a second time by default.

When a generation tool returns FEATURE_NOT_INCLUDED for a generation.* feature, use its payer and access details. If the project owner needs Pro, explain that the owner pays and must upgrade; the member's own Pro does not unlock the project. Do not give the member a personal upgrade link or send them to their own billing menu. They can find the owner in the project's existing members view when available. Otherwise share the returned upgrade link, or ChatCut’s avatar menu → Upgrade. Existing credits are preserved and generation still consumes credits after upgrading. This rejection does not charge for generation; existing agent conversation fees are separate, so do not claim the whole conversation was free. Preserve the exact original tool input and project, then stop. Do not automatically search for or substitute stock media; offer alternatives only if the user explicitly asks.

When the user returns with “continue”, “继续”, “jixu”, or says they upgraded, recheck current payer eligibility and credits for the original input with estimate_generation when supported, otherwise the original tool’s precheck. If there is no separate precheck, one retry of the original tool lets its server check current access. If eligible, submit the original input once; if still blocked, explain the current blocker and stop. Do not ask the user to choose between the original generation and stock media again or state the old rejection as current status without checking. If a job was already accepted, track it instead of submitting again. Never switch generation tools, providers or services to bypass a gate.