<h2 id="updated-v1.6-yogurt-ltxdirector_extender-workflow-(inspired-by-wan-svi-notoriously-missing-for-ltx)">Updated v1.6 Yogurt LTXDirector_Extender Workflow (Inspired by WAN SVI, notoriously missing for LTX)</h2> What Changed<h3 id="1.-guide-attention-accounting-fix">1. Guide attention accounting fix</h3>The LTX Director guide node now appends the guide attention metadata that ComfyUI expects for each inserted guide latent. This resolves the failure:<code>ValueError: guide pre_filter_counts != keyframe grid mask length</code><h3 id="2.-overlap-aware-guide-timing">2. Overlap-aware guide timing</h3>Extension latents can start with preserved overlap/reference frames from the previous generation pass. The timeline guide positions are extension-relative, so the guide node now detects that front prefix and shifts guide insert positions forward into the newly generated region.<h3 id="3.-overlap-aware-promptrelay-timing">3. Overlap-aware PromptRelay timing</h3>The PromptRelay timing logic now detects when the runtime latent is longer than the schedule-configured latent. When that happens, it treats the extra leading frames as overlap/reference context and shifts the local prompt schedule forward.That shift is applied to:<ul><li>the normal video cross-attention path</li><li>the scaled attention path used by LTX audio conditioning</li></ul>This matters for extension passes where video and audio conditioning must align to the new section instead of the preserved overlap prefix.<h3 id="4.-transition-and-seam-fixes-for-the-extender-path">4. Transition and seam fixes for the extender path</h3>The extender workflow now includes a validated transition path for continuing rendered clips without the hard one-frame cut that earlier workflow variants could fall into.The working <code>v1.6</code> workflow uses direct embedded-subgraph inputs for overlap and seam controls instead of relying on the older virtual <code>SetNode</code>/<code>GetNode</code> bridge inside the extender subgraphs.Specific node updates used by the working path:<ul><li><code>AlignedOverlapCutTransition</code> in <code>frame_transition_nodes.py</code><ul><li>adds automatic seam scoring across the overlap window</li><li>exposes <code>blend_frames</code> to soften the splice on both sides of the seam</li><li>exposes <code>seam_shift</code> so the cut can be moved earlier or later inside the overlap region</li><li>infers a usable overlap window from the actual frame batches when the workflow resolves the overlap control incorrectly</li><li>keeps <code>IS_CHANGED</code> forcing recomputation so transition tuning is not hidden by prompt/subgraph caching</li></ul></li><li><code>AlignedAudioCutTransition</code> in <code>frame_transition_nodes.py</code><ul><li>uses the image seam index to keep the audio splice aligned with the chosen visual seam</li></ul></li><li><code>LTXExtensionFrameLogic</code> in <code>frame_transition_nodes.py</code><ul><li>remains the overlap/frame reference utility node used by the extender sampler subgraphs</li><li>its outputs are now consumed through the corrected <code>v1.6</code> subgraph wiring instead of the broken overlap bus that previously collapsed to a one-frame cut</li></ul></li></ul>The <code>v1.6</code> workflow is the release workflow to use when you want the smoother transition behavior that was validated during testing. Use <code>example_workflows/Yogurt_LTXDirector_extender_v1.6.app.json</code> as the current tested template workflow. Files under <code>example_workflows/</code> are exposed through ComfyUI's workflow template system.Before loading the <code>v1.6</code> workflow, update the custom node itself from this repo. The workflow depends on the current transition and patch behavior in <code>__init__.py</code>, <code>frame_transition_nodes.py</code>, and <code>patches.py</code>; older installed node files can load the workflow but still miss the seam, overlap, and audio-alignment fixes it expects.Custom nodes now available via comfy registry: via cli "comfy node install LTXDirector-Extender" or just search the manager for LTXDirector-ExtenderWorkflow file:- <code>example_workflows/Yogurt_LTXDirector_extender.json</code><code>**If the workflow opens as an app, just select graph -&gt; exit app mode</code> <img src="https://image.civitai.com/xG1nkqKTMzGDvpLrqFT7WA/adf86d3e-539c-4de6-8914-20fcdce3f4d2/original=true/adf86d3e-539c-4de6-8914-20fcdce3f4d2.jpeg" />The Yogurt LTXDirector_Extender workflow: generate the first clip with the standard LTX Director path, then continue with the extender path using prior video and audio context.Primary nodes in this fork:- <code>LTX Director Extender</code>- <code>LTX Director Guide Extender</code>- <code>LTX Prompt Relay Encode + Temporal LoRA</code><img src="https://image.civitai.com/xG1nkqKTMzGDvpLrqFT7WA/068a3228-3a17-4c58-b4d5-5044ff0c76ec/original=true/068a3228-3a17-4c58-b4d5-5044ff0c76ec.jpeg" /> The standalone LTX Prompt Relay Encode + Temporal LoRA node included in this fork. This is kept separate from the tested LTX Director extension path until the combined workflow is validated.This node allows you to apply specific lora weights to segments within the prompt. This is useful when using a lora without a trigger word, and you don't want it influencing part of the generation. for example, under the lora segment weights you put 0.0,1.0,1.0,0.5 if you want that particular lora to have no effect during the first segment, 1.0 during the second and third segments, and 0.5 for the last segment. <h3 id="what-the-workflow-does">What The Workflow Does</h3>The intended flow is:1. Generate the first clip with the standard LTX Director node.2. Use the Yogurt LTXDirector_Extender flow to append new segments.3. Feed the extender sampler subgraph with the previous clip's video and audio context so the next section continues from what was already generated.This lets the user keep extending a sequence while preserving context from the earlier result instead of treating each segment as a fresh standalone generation.<h3 id="cut-vs-blend-in-the-sampler-subgraph">Cut vs Blend In The Sampler Subgraph</h3>Inside the sampler subgraph, there is a choice between cutting frames or blending them depending on the effect you want.- Use cut when you want a harder transition.- Use blend when you want a softer overlap transition.If you swap this behavior, change the output connector from cut to blend on that node and reconnect it to the following node in the subgraph.<h3 id="duration-must-match-manually">Duration Must Match Manually</h3>The duration configured in LTX Director Extender must match the duration configured inside the sampler subgraph.This is manual for now. A <code>GetNode</code> attempt was not reliable enough in this workflow, so both places should be set by hand until that is improved.If those durations do not match, the extension path can drift away from the intended overlap and continuation timing. <h3 id="extending-from-a-previously-created-video">Extending From A Previously Created Video</h3>If you want to extend from a video that already exists:1. Use a Load Video node to bring the previous clip into the workflow.2. Disable the standard LTX Director generation path for the initial clip.3. Connect the loaded video's frame output and audio output into the extender sampler subgraph.That lets the extender path continue from an already rendered clip instead of requiring the first section to be regenerated inside the same workflow.<h3 id="practical-runtime-notes">Practical Runtime Notes</h3>Tested results so far:- Up to about 150 seconds of generation on 16 GB VRAM- Occasional 64 GB system RAM exhaustion on the final step for very long runs- 10 to 15 second extension durations tend to work consistentlyFor stability, shorter extension chunks are the safer default. Long chained runs are possible, but they are more likely to hit RAM limits near the end.<h3 id="ui-notethe-extender-workflow-is-intended-to-use-the-renamed-fork-specific-nodes:">UI Note The extender workflow is intended to use the renamed fork-specific nodes:</h3>- <code>LTX Director Extender</code>- <code>LTX Director Guide Extender</code>- <code>LTX Prompt Relay Encode + Temporal LoRA</code>If a workflow still references the original <code>LTXDirector</code> or <code>LTXDirectorGuide</code> node types, it will bind to the upstream WhatDreamsCost nodes instead of the forked extender versions.Workflow V 1.1 corrects an issue so that the nodes show up as needed in comfyui manager.<h3 id="download-the-nodes:">Download the nodes:</h3><a target="_blank" rel="ugc" href="https://github.com/Yogurt1192/LTXDirector-Extender.git">https://github.com/Yogurt1192/LTXDirector-Extender.git</a> or search the manager for LTXDirector-Extender ## Install1. Clone this repo into your ComfyUI <code>custom_nodes</code> folder.2. Restart ComfyUI.3. Re-open your LTX Director extension workflow and reconnect any nodes if your local workflow still points at an older custom-node install.Example:```bashcd /path/to/ComfyUI/custom_nodesgit clone <a target="_blank" rel="ugc" href="https://github.com/Yogurt1192/LTXDirector-Extender.git">https://github.com/Yogurt1192/LTXDirector-Extender.git</a>```The included workflow is designed for the extender node names in this fork. If you install both the upstream repo and this fork side by side, use the extender-named nodes when building or updating workflows.

v1.6 Yogurt LTXDirector_Extender & Workflow

Updated nodes and workflow for better seam transitions

yogurtLtxdirector_v10.json

yogurtLtxdirector_v11.json

Files with SHA256: 110d71883cce4d59b8e4e3fef4ed8837e6be1076487c1745fcaea8a9ee6a0487