This is a merged LTX-2 checkpoint from the same author who did the Wan-era merges, now with the Adapter LoRA update folded in. The claim is better video quality as well as uncensored output, and the episode packages four graphs - text-to-video, image-to-video, first/last frame, and lip-sync - into one image. The notes are practical: what each widget does, which ones are inert in which mode, and how long a 1080p / 121-frame run takes.

Evidence note: this episode ships no workflow JSON. Every claim below comes from the episode subtitles/description and the published page; no node-level parameter is invented.

When this is useful

  • You want an LTX-2 merge that runs from one deployable image instead of hand-assembling nodes.
  • You need both an SFW and an uncensored checkpoint available without switching images.
  • You are deploying LTX-2 on a consumer GPU and want the author's known-good settings.

What is in the image

Four graphs, fully localised

The image ships four workflows: text-to-video, image-to-video, first/last-frame, and image-to-video lip-sync. The UI strings are translated to Chinese.

Two checkpoints are bundled - an SFW and an NSFW build - so you switch model rather than switching image.

The author recommends renting a consumer-grade GPU: ComfyUI's LTX-2 optimisation is good enough that a datacentre card is not required.

Settings that matter in text-to-video

Width, height, source frame rate, and output frame rate set to 48 - because the graph interpolates 2x afterwards. Then the frame count and the output directory (default is fine).

First-frame and last-frame strength are exposed; the last frame is what the first/last-frame mode uses. In pure text-to-video both strengths are inert.

Output frame range 0:-1 means no crop. The range exists so you can trim a strange head or tail frame when a run produces one.

Cost reference from the author: a 1080p, 121-frame generation takes a bit over 70 seconds.

Image-to-video and the compression-artifact dial

Image-to-video adds an image loader, and now the first-frame strength actually applies.

A compression-artifact setting becomes active: raise it for a blurry, noisy source, lower it for a clean one. ComfyUI's default is 33; this flow ships 28.

First/last frame is the same graph with a second image slot.

Lip-sync

The lip-sync graph is the earlier RunningHub distilled lip-sync flow adapted to this merged model.

You set width, height and frame rate; the frame count is computed from the audio. The author's example audio is 18 seconds - extract the vocals, trim to the section you want (his example uses 5 seconds), and the graph derives a sensible length from it.

How to run it

  1. Register on the compute platform (the episode says registration grants some free hours), find the LTX2-Rapid-Merges image, and deploy an instance on a consumer GPU.
  2. Copy the startup command from the image page, paste it into JupyterLab, and wait for ComfyUI.
  3. Open the workflow panel and choose text-to-video, image-to-video, first/last frame or lip-sync.
  4. Set width, height and source fps; set output fps to 48 because the graph interpolates 2x.
  5. Set the frame count and keep the output range at 0:-1 unless a bad head or tail frame needs trimming.
  6. For image-to-video, load the image and set the compression-artifact value - 28 in this flow, 33 is the ComfyUI default; raise it for noisy sources.

Parameter basis

No workflow JSON in this episode. No node-level parameters are claimed; the description is limited to what the video and the published page state.

No JSON ships with this episode, so no sampler values are quoted. The numbers above (output fps 48, frame range 0:-1, compression artifact 28 vs 33, 121 frames / 1080p / ~70 s) are the values the author states in the video.

Honest limits

  • No workflow JSON and no mirror URL were recorded for this episode - the deployment pointer lives only in the video description, so this write-up documents behaviour, not a redistributable file.
  • The 70-second figure is the author's observation for 1080p / 121 frames on his rented card, not a benchmark.
  • First/last-frame strengths are inert in text-to-video; setting them there does nothing.
  • The merge's quality claims are the author's; no side-by-side against the upstream LTX-2 build is shown.
  • Uncensored output shifts responsibility to the user - local rules and platform terms still apply.

Episode resources