AI video guide · ComfyUI · LTX 2.3

LTX Director in ComfyUI: Detailed LTX 2.3 Timeline, Prompt Relay, Keyframe, and Audio Guide

Use WhatDreamsCost’s free open-source LTX Director node as a practical timeline editor for local LTX 2.3 video work: install the node, load the example workflows, control timing with Prompt Relay, place images as guide keyframes, add custom audio for lip sync, and troubleshoot common prompt and setup issues.

Difficulty: IntermediateUpdated: May 22, 2026Primary source: What Dreams Cost tutorialWorkflow: local ComfyUI video generation
1

What this guide helps you build

LTX Director is a ComfyUI custom node that turns LTX 2.3 video generation into a timeline-driven directing workflow. Instead of writing one large prompt and hoping events happen in the right order, you create time segments, drop images or audio onto the timeline, assign prompts to specific spans, and use guide images as keyframes that the model tries to reach.

Use it for

  • Short local AI video clips.
  • Image-to-video experiments.
  • Timed actions and camera moves.
  • Multi-keyframe cinematic shots.
  • Custom-audio lip-sync tests.

Core idea

Each timeline item becomes direction for the model: when the action happens, which image should guide the frame, whether audio should drive movement, and what persistent atmosphere should apply to the whole video.

Best first target

Start with a short 4–7 second clip at a conservative resolution. Once installation, workflow loading, and basic prompting work, increase length, resolution, or keyframe complexity.

Plain-English summary: install the node, open an example workflow, drag in an image, type one simple action prompt, run a low-resolution test, then add more timeline segments for timed actions, keyframes, or audio.
2

Quick start checklist

  1. Confirm ComfyUI works first. Open your ComfyUI instance and run any known-good workflow before adding new custom nodes.
  2. Install WhatDreamsCost-ComfyUI. Use ComfyUI Manager and search for What Dreams Cost, or clone the GitHub repo into ComfyUI/custom_nodes/.
  3. Choose the nightly/latest build if needed. The tutorial and README both emphasize using the latest/nightly version when the standard Manager listing lags behind.
  4. Update dependencies. Update ComfyUI-LTXVideo and ComfyUI-KJNodes. The repo README states ComfyUI-LTXVideo must be updated for LTX Director to work.
  5. Restart ComfyUI. Custom node changes usually require a restart or full refresh.
  6. Load an LTX Director workflow. In ComfyUI templates, search LTX Director, or import one of the example workflows from the GitHub repo.
  7. Run a conservative test. Use a short duration, low resolution, and one simple prompt before building a complex scene.
3

Install and update the required nodes

Manager method

  1. Open ComfyUI Manager.
  2. Search for What Dreams Cost.
  3. Install WhatDreamsCost-ComfyUI.
  4. If the newest version is not visible, fetch updates or choose the nightly version.
  5. Update ComfyUI-LTXVideo and ComfyUI-KJNodes.
  6. Restart ComfyUI.

Manual Git method

cd /path/to/ComfyUI/custom_nodes
git clone https://github.com/WhatDreamsCost/WhatDreamsCost-ComfyUI

After cloning, restart ComfyUI. If a workflow reports missing nodes, install/update the missing dependencies through Manager or their GitHub repos.

Version note: the GitHub README observed during drafting identifies version v1.3.9 and says recent Manager visibility issues were fixed, but the safest habit remains: update the node list, install the current/nightly package if the release lags, and keep LTXVideo/KJNodes current.
4

Understand the LTX Director controls

The node is designed to behave like a compact video editor inside ComfyUI. These are the controls the tutorial calls out.

Project length and size

  • Duration frames / duration seconds: change either one and the other updates to match.
  • Frame rate: determines how duration in seconds maps to total frames.
  • Custom width / custom height: output dimensions. If set to 0, the node uses the source image dimensions.

Timeline editing

  • Add images/audio with toolbar buttons or drag images and audio directly onto the timeline.
  • Use the plus button to create a segment that fills an empty area.
  • Resize the timeline with bottom/side handles; adjust audio/image track widths with the middle bar.

Settings and playback

  • Switch display mode between seconds and frames.
  • Use playback controls to preview timing.
  • Use zoom controls to work on dense timelines.

Prompting controls

  • Each segment has its own prompt area.
  • Global prompt: optional prompt applied across the whole timeline.
  • Custom audio toggle: tells the workflow whether to use imported audio.
  • Guide strength: controls how strongly an image affects generation.
5

Create your first image-to-video test

  1. Load a starting image. Drag an image onto the image track. The tutorial demonstrates with an image made in Z-Image, but any suitable source image can be used.
  2. Add one simple prompt. Keep the first prompt easy to evaluate. Example: the woman raises her hand and waves it.
  3. Lower the resolution for the first run. This makes setup errors cheaper and faster to diagnose.
  4. Run the workflow. Confirm that the image influences the output and that the prompted motion appears at least generally.
  5. Only then add complexity. Once the basic path works, add more segments, audio, or keyframes.
Good first result: the output does not need to be production quality. It only needs to prove that the workflow loads, the node can read your image, LTX 2.3 generates video, and your prompt affects the motion.
6

Use Prompt Relay for timed actions

Normal LTX prompting can describe a sequence, but it may not perform each event at the exact moment you intended. Prompt Relay solves that by letting you distribute instructions across the timeline.

0:00–0:03 Establish the subject, posture, and setting.

0:03–0:05 Introduce a timed action such as lightning in the background, a character walking forward, or a facial reaction.

0:05–0:07 Add speech, a gesture, or a final beat.

Segment 1: the woman stands in the rain, looking toward the camera
Segment 2: lightning strikes in the background, lighting her face
Segment 3: the woman walks toward the camera and says in a sad voice, "I'm sorry"
Why it matters: shorter, timed prompts let you direct the scene. They also make it easier to diagnose failures because you know which segment was supposed to cause which motion.
7

Prompting rules that prevent ignored actions

The tutorial highlights two major reasons outputs fail to follow prompts.

1. The prompt is not written in a way LTX understands

Simple prompts can work for simple actions. For complex camera moves, action scenes, or changes across frames, describe the subject, action, camera, environment, and timing more explicitly.

Weak: action scene with robot
Better: a heavy robot bends down, grips the small car with both hands, lifts it slowly, then turns toward the glass office building

2. Too much happens in too little time

If a segment is only two seconds long, do not ask for a chain of actions that would take much longer. Either extend the segment or split the action across multiple segments.

Too much: the robot picks up the car and throws it at the building in 2 seconds
Better: Segment 1 lifts car; Segment 2 turns body; Segment 3 throws car
Use the official LTX 2.3 prompting guide: the video recommends the official guide for prompt structure, do/don’t patterns, and common mistakes. Treat that guide as the reference when an output looks random or under-directed.
8

Use images as guide keyframes

In LTX Director, every image on the timeline is a guide image. That means it can be used as a keyframe at the beginning, middle, or end of a shot. You are not limited to classic image-to-video where the image must be the first frame.

  1. Start with the frame you care about. Example: a hero walking toward camera while an explosion fills the background.
  2. Place that image where the moment should happen. If the explosion should occur at second 4, slide the image later on the timeline.
  3. Prompt what happens before it. The model is guided toward the keyframe, so the preceding segment can describe the build-up.
  4. Add more images for a longer shot. The tutorial shows that multiple guide images can flow together into a longer camera move.
  5. Adjust guide strength. Increase it when the image is not respected enough; reduce it if the output feels too rigid or cannot move naturally.
Director mindset: keyframes let you specify important moments instead of hoping the model invents them. Use them for composition, important reveals, impact frames, and scene continuity.
9

Add custom audio and improve lip sync

LTX Director can import your own audio and use it to drive the video. This is useful for dialogue, reactions, or physical movement that should align with a sound cue.

  1. Drag or load the audio clip onto the audio track.
  2. Trim it to the part you need. Keep the first test short and audible.
  3. Toggle custom audio on. If this setting is off, the workflow may ignore the imported audio path.
  4. Write a prompt that explicitly describes speech. Avoid only writing person speaks.
  5. If lip sync fails, include the actual words. The tutorial says typing what is being said can make the lip-sync behavior much more reliable.
Better lip-sync prompt pattern:
A close-up of the tired man speaking clearly, his mouth forming the words: "Here I am, old and tired and fat." He looks exhausted and pats his stomach on the final phrase.
Advanced timing idea: combine audio with Prompt Relay. Put a gesture prompt in the middle of the timeline so a character reacts at the exact spoken phrase or sound effect.
10

Use text-to-video and global prompts

Text-to-video

For text-to-video, use text segments instead of image segments. The rest of the LTX Director features still apply, including Prompt Relay and custom audio. Set the output size with custom width and custom height.

Global prompts

Use a global prompt for persistent information that should apply through the whole shot: weather, mood, lighting, background alarm, wind, rain, film stock, or overall camera style.

Global prompt examples:
continuous heavy rain, wet pavement reflections, handheld documentary camera
constant red emergency alarm light pulses in the background
wind blows through the character's hair throughout the entire shot
Rule of thumb: put persistent atmosphere in the global prompt and time-specific actions in individual timeline segments.
11

Verify that your setup works

  • The LTX Director node appears in ComfyUI and the example workflows load without missing-node errors.
  • Duration seconds and frames update together.
  • Dragging an image or audio file onto the timeline creates the expected media item.
  • A low-resolution image-to-video test completes without crashing.
  • Changing custom width/height changes the output size.
  • A later prompt segment changes what happens later in the clip.
  • Moving a guide image later in the timeline changes the generated build-up to that frame.
  • Custom audio only affects generation after the custom-audio toggle is enabled.
Production-readiness check: before making a long or high-resolution render, confirm the same scene works as a short, low-resolution draft. Then scale one variable at a time: resolution, duration, keyframe count, or prompt complexity.
12

Troubleshooting

Node or workflow is missing

Update ComfyUI Manager’s node list, install the nightly/latest WhatDreamsCost-ComfyUI package, update ComfyUI-LTXVideo and ComfyUI-KJNodes, then restart ComfyUI.

Workflow loads but generation fails

Check that your LTX 2.3 model files and dependency nodes are installed where the workflow expects. Start from the official example workflow before modifying the graph.

Prompted action is ignored

Split the action into shorter segments, extend the segment length, and make the prompt more concrete. Do not ask for too much action in two seconds.

Keyframe is not respected

Move the image to the exact target time, raise guide strength gradually, and simplify competing text prompts that contradict the image.

Lip sync is weak

Use clear audio, toggle custom audio on, describe the person speaking, and include the exact words in the prompt when needed.

VRAM errors or very slow renders

Lower resolution, shorten duration, reduce frame rate, test fewer keyframes, and only increase quality after the low-resolution draft succeeds. The creator notes using a 12 GB RTX 3060 required lower-quality model settings and lower resolution.

13

Sources and related links