AD_LTX_MulGuide

Lightricks' LTX video models lean hard on IC-LoRAs - "in-context" LoRAs that take a control video or reference image and condition generation on it, covering things like pose, depth, canny edges, camera moves, and by the 2.3 line, more exotic stuff like water simulation and colorization. The official 13B release shipped pose/depth/canny control LoRAs, and LTX-2 added camera-control LoRAs and a "detailer" IC-LoRA on top. Feeding multiple guide references into a pipeline like that is exactly the kind of multi-node wiring chore Apt_Preset exists to simplify, and that's what AD_LTX_MulGuide does - the node's own one-line description calls it "LTX multi-guide simplified."

What it touches. This is a filter node, not a loader - it takes your existing positive/negative CONDITIONING, plus img_latent and img_vae, and hands back the same four types, modified. You splice it into an LTX pipeline between wherever you set up your base conditioning/VAE and the sampler, not in place of the LTX model loading itself - Lightricks' own ComfyUI-LTXVideo nodes still handle loading the actual LTX model and VAE; this node's job is specifically the multi-guide conditioning layer on top.

The one input that actually configures what the node does is num_guides, and its type - COMFY_DYNAMICCOMBO_V3 - is a dynamic combo widget, the kind of ComfyUI v3-schema control that lets a node's input count grow or shrink based on a setting rather than being fixed at build time. Practically, that means the node's canvas widget lets you add guide slots as you need them rather than presenting a fixed bank of four or five reference inputs whether you're using them or not - which is the actual simplification here: instead of manually wiring N separate guide/reference nodes into an LTX conditioning chain, one at a time, you add guides inside this single node as needed.

One thing worth knowing if you're mixing IC-LoRAs across LTX versions: Lightricks' own community has flagged that IC-LoRAs and training resources aren't always clearly labeled by which LTX generation they target - a 2.3-trained resource can end up looking indistinguishable from a 2-trained one if you're just browsing by name, and Lightricks itself has acknowledged the labeling confusion publicly. If a guide reference isn't behaving the way you expect through this node, it's worth double-checking that the IC-LoRA or control input you're using actually matches the LTX model revision you're running (2, 2.3, and so on) before assuming the node is misconfigured.

Outputs. positive, negative, img_latent, and img_vae - the same four types you fed in, now carrying the multi-guide conditioning, ready to continue into your LTX sampler.

Installing it. This node ships as part of ComfyUI-Apt_Preset itself - search "ComfyUI-Apt_Preset" in ComfyUI Manager, or clone it directly:

cd ComfyUI/custom_nodes
git clone https://github.com/cardenluo/ComfyUI-Apt_Preset.git

Run install.bat on Windows for dependencies, then restart. Note this node doesn't replace your LTX video setup - you still need Lightricks' own ComfyUI-LTXVideo nodes (or an equivalent) installed to actually load the LTX model, VAE, and text encoder in the first place; Apt_Preset's README doesn't list that as a hard dependency the way it does for GGUF or Nunchaku support, but functionally you need an LTX pipeline already working before this node has anything useful to operate on.

Troubleshooting. If the node errors on missing types, confirm your positive/negative conditioning and img_latent/img_vae are actually coming from an LTX-specific pipeline rather than a generic image workflow - this node's conditioning types are LTX-specific, not universal. If guides aren't producing the effect you expect, check the IC-LoRA/version-match issue above first. And if Apt_Preset fails to import at all, that's the pack-wide IMPORT FAILED issue documented on r/comfyui, traced to a missing dependency unrelated to this node - check your ComfyUI console log at startup and reinstall via Manager's "install missing custom nodes."