Best Practices

Handling Unknown Video Length

When your workflow generates a video clip and you need to use its duration downstream — for example, to sync audio, set a caption duration, or trim another element — you can't hardcode a number because the output length varies between runs.

The solution is to measure the duration dynamically and pass it as an input to the nodes that need it.

Pattern

1. After your video generation node, add a Get Media Info utility node

2. Connect the video output to it — it returns metadata including the exact duration in seconds

3. Make the duration field in your downstream node dynamic (lightning bolt icon)

4. In Collections or via node mapping, connect the duration output to that field

A Get Media Info node extracting duration from a generated clip and passing it to a Captions node.

This pattern is especially useful when:

• Adding captions to a clip of variable length

• Syncing a voiceover to a generated video

• Setting Editor placeholder duration dynamically based on actual output

---

Long Continuous Video — Extract Frame + 10-Second Segments

Kling (the video generation model) produces the best lip-sync quality for clips of 10 seconds or under. Beyond 10 seconds, lip-sync accuracy starts to degrade noticeably.

If you need a longer video — say 25–30 seconds — don't try to generate it in one clip. Instead, chain multiple 10-second segments together using the Extract Frame pattern.

Pattern

1. Generate your first clip (10 seconds) from a starting image

2. Add an Extract Frame node — set it to Last Frame

3. Connect the first clip's output to Extract Frame

4. Use the extracted frame as the Start Image for your second clip

5. Repeat for as many segments as you need

6. Assemble all clips in the Editor using placeholders

Three Image to Video nodes chained together with Extract Frame nodes between them for seamless continuation.

This produces a seamless result because each new clip starts exactly where the previous one ended — same lighting, same character position, same background.

Recommended segment lengths

---

Redubbing AI-Generated Voice

When you generate a video with AI-generated speech, you may want to redub it into another language — or replace the voice entirely — while keeping the lip-sync intact.

Tala's 11 Labs integration handles this through a dedicated redubbing flow.

Pattern

1. Generate your video with audio using an Image to Video node (Generate Audio: on)

2. Add an 11 Labs node — select Dubbing

3. Connect the video output to the Dubbing node

4. Configure the target language and voice settings

5. The output is a new video with the audio replaced and lip-sync adjusted to match

An Image to Video node connected to an 11 Labs Dubbing node for language redubbing.

Additional voice options in 11 Labs

Beyond dubbing, the 11 Labs integration supports:

• Text to Speech — generate a voiceover from a text prompt, then layer it over video in the Editor

• Voice Cloning — use a reference audio sample to match a specific voice style

• Voice Changer — transform an existing audio track into a different voice

---

General Tips

Test nodes individually before running the full workflow. Use the Run button on individual nodes while building. Catch bad prompts and misconfigured settings early — before they waste credits on downstream generations.

Save prompts that work. When a prompt produces a great result, copy it somewhere safe. Prompts are easy to accidentally overwrite, and good ones are hard to recreate from scratch.

Use Assets for reusable media. Logos, watermarks, end cards, and brand elements should be uploaded to Assets once and reused across workflows — not re-uploaded each time.

Name your workflows clearly. As your library grows, descriptive names like Product Launch - Vertical 9:16 - EN are much easier to navigate than Workflow 7.

Use Revert as a safety net. Before making major changes to a working workflow, run it once so a snapshot exists in history. If your edits break something, you can always revert.

---

What's Next?

• Your First Workflow — put these patterns into practice

• Editor — dynamic durations and timeline assembly

• Collections — batch runs for multilingual and multi-variant campaigns