Nodes/ComfyUI/ModelMergeLTXV
ComfyUI Node Runs on cloud

ModelMergeLTXV

Technically yes, practically eh

By Comfy-Org·Created 4 years ago·Updated 37 minutes ago· 129,963
ModelMergeLTXV
  • model1
  • model2
  • MODEL
patchify_proj.1.00
adaln_single.1.00
caption_projection.1.00
transformer_blocks.0.1.00
transformer_blocks.1.1.00
transformer_blocks.2.1.00
transformer_blocks.3.1.00
transformer_blocks.4.1.00
transformer_blocks.5.1.00
transformer_blocks.6.1.00
transformer_blocks.7.1.00
transformer_blocks.8.1.00
transformer_blocks.9.1.00
transformer_blocks.10.1.00
transformer_blocks.11.1.00
transformer_blocks.12.1.00
transformer_blocks.13.1.00
transformer_blocks.14.1.00
transformer_blocks.15.1.00
transformer_blocks.16.1.00
transformer_blocks.17.1.00
transformer_blocks.18.1.00
transformer_blocks.19.1.00
transformer_blocks.20.1.00
transformer_blocks.21.1.00
transformer_blocks.22.1.00
transformer_blocks.23.1.00
transformer_blocks.24.1.00
transformer_blocks.25.1.00
transformer_blocks.26.1.00
transformer_blocks.27.1.00
scale_shift_table1.00
proj_out.1.00

LTX Video is the speed tier of local video generation - Lightricks' family that drafts clips in seconds where Wan takes minutes. The community's relationship with it is the draft-in-LTX, refine-in-Wan workflow, not "let me blend two LTX fine-tunes together." So this node, honestly, is an edge case of an edge case: merging video models is rare, and merging LTX models is rarer. But it's here, it ships with core, and if you've got two LTX checkpoints you love it's the tool.

How it works

The family engine again: clone model1, mix model2's weights in per-block with ratio as the fraction of model2, longest-prefix matching on the weight keys. LTX's transformer is a DiT with adaLN conditioning, which is why the sliders read the way they do:

  • patchify_proj. - the patch embedding that turns video tokens into the transformer's input space
  • adaln_single. - the adapted layer-norm modulation, where timestep conditioning gets injected
  • caption_projection. - the text-conditioning projection
  • transformer_blocks.0.transformer_blocks.27. - the 28 attention blocks themselves
  • scale_shift_table and proj_out. - the output side

And the usual trap: every slider defaults to 1.0, meaning "take model2." Run without touching anything and you get model2 wholesale, not a blend. Put your base in model1, the flavor in model2, and lower the sliders you actually want to mix.

The gotchas that matter for video

Both inputs must be the same LTX variant with the same block layout - this node was written for the original 2B LTX-Video architecture (it landed November 2024, before the 13B and LTX-2). Feed it mismatched variants and the weight keys won't line up, the merge matches nothing, and you silently get model1 back. Same for the "must be the same architecture" rule that runs through the whole merge family.

The output is a MODEL that feeds the usual video sampler pipeline - VAE encode, sample, VAE decode - and it behaves exactly like either input would, because only weights changed.

Should you?

If you're on this page, you've probably already got the two LTX models and a reason. Fine. Start with small merges (0.3–0.5 on the transformer blocks), test on a short clip, and expect the video-model version of the universal merge truth: blending similar-aesthetic models is consistent, blending opposites is a coin flip. And if you were hoping this would let you merge LTX with Wan - it won't. Different architectures entirely. Merging across video families isn't a thing.

Categorymodel/merging/model specific

Inputs (35)

NameTypeDefaultDescription
model1MODEL
model2MODEL
patchify_proj.FLOAT1.000–1
adaln_single.FLOAT1.000–1
caption_projection.FLOAT1.000–1
transformer_blocks.0.FLOAT1.000–1
transformer_blocks.1.FLOAT1.000–1
transformer_blocks.2.FLOAT1.000–1
transformer_blocks.3.FLOAT1.000–1
transformer_blocks.4.FLOAT1.000–1
transformer_blocks.5.FLOAT1.000–1
transformer_blocks.6.FLOAT1.000–1
transformer_blocks.7.FLOAT1.000–1
transformer_blocks.8.FLOAT1.000–1
transformer_blocks.9.FLOAT1.000–1
transformer_blocks.10.FLOAT1.000–1
transformer_blocks.11.FLOAT1.000–1
transformer_blocks.12.FLOAT1.000–1
transformer_blocks.13.FLOAT1.000–1
transformer_blocks.14.FLOAT1.000–1
transformer_blocks.15.FLOAT1.000–1
transformer_blocks.16.FLOAT1.000–1
transformer_blocks.17.FLOAT1.000–1
transformer_blocks.18.FLOAT1.000–1
transformer_blocks.19.FLOAT1.000–1
transformer_blocks.20.FLOAT1.000–1
transformer_blocks.21.FLOAT1.000–1
transformer_blocks.22.FLOAT1.000–1
transformer_blocks.23.FLOAT1.000–1
transformer_blocks.24.FLOAT1.000–1
transformer_blocks.25.FLOAT1.000–1
transformer_blocks.26.FLOAT1.000–1
transformer_blocks.27.FLOAT1.000–1
scale_shift_tableFLOAT1.000–1
proj_out.FLOAT1.000–1

Outputs (1)

NameTypeDescription
MODELMODEL