How do I ensure kling-v1-6 is used when making a request?
Explicitly specify model=kling-v1-6 in video generation or talking photo requests rather than relying on the default selection when omitted. For standard videos, also choose text2video, image2video, or extend, and provide a prompt, first-frame image, or existing video ID according to the task.
How long a video can V1.6 generate?
The video generation endpoint supports selecting 5 or 10 seconds, and talking photos also offer these two durations. To continue creating, you can use extend to submit an existing video_id and a follow-up prompt; extension continues an existing clip and does not mean generating a video of any length in a single request.
Why can't the std mode use an end frame?
The std version of kling-v1-6 does not support end-frame constraints. When you need a specific ending image, use pro image2video and provide both start_image_url and end_image_url; providing only an end frame cannot complete this type of task, as a first frame is still required input.
Does talking photo mean V1.6 can generate sound?
No. V1.6 does not support native audio; talking photos use the audio you provide: the photo is first animated, then lip-synced to the audio. You need to submit image_url and audio_url. Prompts are mainly used for movements or expressions during the animation stage, not for generating speech content.
How should generation tasks be integrated into an application?
You can use async=true to obtain a task_id and then query the task status, or configure callback_url to receive the completed result. Applications should distinguish between a submitted task and a completed video, and read video_url after completion; if you later need to extend it, you should also save video_id and not use task_id as a substitute.