Frame Count Passthrough

Let's be honest up front: this node does nothing except hand an integer back to you unchanged. value in, value out, that's the whole mechanism - the source is a forward that literally returns int(value). So why does it exist in a pack that's otherwise about stitching LTX video clips together?

Because it's a wiring utility, not a processing one. The LTX Director extender sampler is built as a subgraph, and subgraphs in ComfyUI work best when values enter as explicit inputs rather than as constants baked into the graph. A passthrough node gives you a named, reconnectable handle for a frame count that you can feed from anywhere upstream and thread into the sampler subgraph - the count arrives as a real input the subgraph can see, instead of you hunting through the workflow every time you change the duration. The category says it all: LTXDirector/memory, alongside the spill-to-directory node. These are plumbing for keeping a long multi-pass extension run coherent, not features you'll ever tune.

It's also a handy breadcrumb when you're debugging. Because it sits in the graph as a first-class node, you can see the exact integer flowing through at that point - which is more than you get from a bare wire - and you can use it to force the upstream computation that produces the count to actually run and stay uncached. For the price of one tiny node, that's not bad.

Inputs and outputs. One of each. value (INT) in, value (INT) out. Set it manually, or - more usefully - wire it from the frame_count output of LTXExtensionFrameLogic, and the passthrough becomes the stable feed into your sampler subgraph's duration input.

Install is the pack's one-liner:

cd ComfyUI/custom_nodes
git clone https://github.com/Yogurt1192/LTXDirector-Extender.git

Restart ComfyUI, and it shows up under LTXDirector/memory as "Frame Count Passthrough". Nothing to download, no dependencies beyond the ComfyUI you already have.

Troubleshooting. There's almost nothing to break here - the failure mode is conceptual, not technical. If your extension pass is landing at the wrong length, the passthrough isn't the problem; the mismatch is between the duration you set in the extender node and the duration set inside the sampler subgraph. This pack makes you keep those two in sync by hand, and no amount of pass-through nodes will fix a workflow where they disagree.