Instructions to use RuneXX/LTX-2.3-Workflows with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- LTX.io
How to use RuneXX/LTX-2.3-Workflows with LTX.io:
# Install the LTX-2 pipelines git clone https://github.com/Lightricks/LTX-2.git cd LTX-2 uv sync --frozen
# Download the weights from this repo, plus the Gemma text encoder hf download RuneXX/LTX-2.3-Workflows --local-dir models/LTX-2.3-Workflows hf download google/gemma-3-12b-it-qat-q4_0-unquantized --local-dir models/gemma-3-12b
# Fast pipeline (distilled model, no distilled LoRA needed) uv run python -m ltx_pipelines.distilled \ --distilled-checkpoint-path models/LTX-2.3-Workflows/<distilled-checkpoint>.safetensors \ --spatial-upsampler-path models/LTX-2.3-Workflows/<spatial-upsampler>.safetensors \ --gemma-root models/gemma-3-12b \ --prompt "A beautiful sunset over the ocean" \ --output-path output.mp4 # For image-to-video, add: --image path/to/image.jpg 0 0.8# HQ pipeline (two-stage, higher quality) uv run python -m ltx_pipelines.ti2vid_two_stages_hq \ --checkpoint-path models/LTX-2.3-Workflows/<checkpoint>.safetensors \ --distilled-lora models/LTX-2.3-Workflows/<distilled-lora>.safetensors 0.8 \ --spatial-upsampler-path models/LTX-2.3-Workflows/<spatial-upsampler>.safetensors \ --gemma-root models/gemma-3-12b \ --prompt "A beautiful sunset over the ocean" \ --output-path output.mp4 # For image-to-video, add: --image path/to/image.jpg 0 0.8 - Notebooks
- Google Colab
- Kaggle
Regarding those "bad outputs, worse quality issues" pls check ur piplines. Here is an overview like dos and donts
Those are mostly for the DEV workflows ;-)
only one workflow here that uses DEV model
and the dev workflow is for sure open for experimental tweaks .. with cfg multi modal nodes (independent CFG for audio and video), and try out different samplers.
Personally i think res_2s give a bit too "overbaked" looks, but on the flip side it works with less steps (so in the chart above, only 15 steps with dev model, res_2s would be the choice for sure).
Alternatively do more steps 20-30 ish or more... and use euler or similar. Speed wise they might end up using same time, since res_2s can be a bit slow.
But yes, dev workflow is a bit less set in stone, than using distilled model "click and go" and get decent results ;-)
One interesting part of the chart above is perhaps the "balanced" middle one with DEV model and no distilled lora at stage 1, and very low cfg for audio.
Havent tried that combo before, audio cfg 1 only looks a bit strange (usually its 7.0 with dev workflow), but maybe its all ok ;-)
