LTX Director (Koolook)

LTX 2.3 is a first-frame/last-frame model with time-windowed conditioning, and stock ComfyUI has no good way to say "this, then that, at this exact moment." That's the hole LTX Director fills: a timeline editor where you drag image, text, and audio segments around a canvas instead of fighting a single global prompt. LTXDirector__koolook is Koolook's namespaced fork of the WhatDreamsCost original, currently pinned to upstream v2.0.2, plus a few Koolook extras like ghost-reference images and keyframe easing. Same node you've seen praised on r/comfyui - just with a __koolook suffix so it doesn't collide with the upstream ID.

What it does

You get a visual timeline. Local prompts and segment lengths are edited as draggable blocks; the node translates that timeline into Prompt Relay conditioning, guide data, and latents that downstream LTX nodes understand. It's "Same as Prompt Relay Encode, but you point at blocks instead of typing arrays." One detail to internalize early: duration_frames only sets the timeline's pixel-space scale. The actual frame count still comes from the latent path - the tooltip is blunt about it.

How it works

A web extension renders the timeline editor and writes its state back into timeline_data, local_prompts, segment_lengths, and guide_strength - all auto-managed fields you should treat as generated, not hand-edited (except for debugging/recovery). The node then emits a Prompt Relay conditioning, an auto-generated LTXV empty latent (only when you don't connect your own optional_latent), an audio latent, and guide_data for the downstream LTXDirectorGuide. Because the brief only reaches the model via Director → guide_data → DirectorGuide, both stages of a two-stage pipeline usually consume the same Director output.

Inputs that matter

• global_prompt - conditions the whole video. This anchors persistent characters, objects, scene context. It's your insurance against identity drift.
• epsilon - Prompt Relay's penalty decay; the paper default is 0.001 and it gives sharp segment boundaries. Values below ~0.1 all look sharp; go 0.5+ for softer transitions.
• keyframe_ease / ease_falloff - Koolook additions that ease in and out of each hard keyframe with strength-ramped neighbor pins, killing the robotic stop/dissolve. 0 = off, 1–2 adds the eased neighbors. Costs extra guide frames, so it's real compute.
• reference_images / reference_strength - the Ghost Mask character-sheet reference: appended as guide frames just past the clean timeline so the model attends to identity but the ref never shows in the output. Lower reference_strength if the reference bleeds pose or lighting.
• snap_keyframes_to_grid - on by default; snaps each image keyframe to the center of its LTX latent-time bucket so hard pins land on one latent frame.

Worth mentioning: use_custom_audio, use_custom_motion, and inpaint_audio toggle whether the timeline's own audio/motion segments are used and whether empty audio gaps get inpainted. Outputs are the useful spread - model, positive (conditioning), video_latent, audio_latent, guide_data, motion_guide_data, frame_rate, combined_audio, plus clean_latent_frames/clean_pixel_frames so you can slice off any appended reference frames.

Installing it

It's in ComfyUI-Koolook. ComfyUI Manager → Install Custom Nodes → "ComfyUI-Koolook", restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/malkuthro/ComfyUI-Koolook.git

Restart after. Two things to know before you hit Run. First, this fork provides the Director, not its ecosystem - LTXDirectorGuide, LTXDirectorCropGuides, and the LTX/Prompt Relay nodes come from the WhatDreamsCost or Lightricks packs, and the workflow won't complete without them. Second, the one-install rule: Manager puts Koolook in custom_nodes/koolook/, so don't also clone it - two parallel copies load, both register the same nodes, and the workflow store can silently corrupt on restart.

A word of caution

Director-class nodes are exactly what a well-known r/comfyui thread called "convenience & overhaul nodes": they hide the parameters you need when output goes wrong, and some purists argue they sidestep the official Multimodal Guider nodes that improve prompt adherence for lipsync and motion. None of that means skip it - it means when a render goes sideways, unwrap the timeline and look at the fields before you blame the seed.