Instructions to use Lightricks/LTX-2.5 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Diffusion Single File
How to use Lightricks/LTX-2.5 with Diffusion Single File:
# No code snippets available yet for this library. # To use this model, check the repository files and the library's documentation. # Want to help? PRs adding snippets are welcome at: # https://github.com/huggingface/huggingface.js
- Notebooks
- Google Colab
- Kaggle
Gemma 4
After some comparisons I can tell that something is wrong with LTX 2.5. The technical report says that has a bigger improvement, but sometimes the model performs worse than LTX 2.3. The model training by itself looks great, but looks like the model is having issues with its text encoder (unfortunately). I wonder, what if LTX 2.5 used Qwen3-vl-8B-it instead Gemma 4-12B-it? Could the model work better as Minimax-H3? Note this is just my opinion, from someone who likes LTX and believe in its potential.
Are you using the one of those text encoders?
Since the model and the encoder were trained together, using the model with any other encoder produces sub optimal results.
If you are using the text encode API - then the new encoder is not supported there yet and we are working on adding support for it.
Are you using the one of those text encoders?
Since the model and the encoder were trained together, using the model with any other encoder produces sub optimal results.
If you are using the text encode API - then the new encoder is not supported there yet and we are working on adding support for it.
Of course. I also tested the model online on Civitai with its "full" capacity, and the results is still the same as I had said. I'm not taking about the visual thing (the video is clean, I can see it), but the generation quality, such bad motion and very noticeable inconsistency, like a character losing its initial appearance or disappearing in the background. Then I'm wondering, what if the text encoder was different?...
- You should not train the text encoder together with the model – LLMs have all the world knowledge/internal world model you already need.
- Do not train it, you will break post-training/alignment, the original team was so much time creating, and it will also result in a broken model
- Gemma is an absolutely fine model, with a lot of anatomical / cultural knowledge, but...
- Make it BIGGER. Imagen/Waver papers, Minimax community text encoder replacement experiments have shown that precise world knowledge (sparse entities) is lost when you downsize the encoder. Gemma 4 31B or a very budget Gemma 4 26B A6 would have been awesome for knowledge / extrapolation / encoding
Thank you
- You should not train the text encoder together with the model – LLMs have all the world knowledge/internal world model you already need.
- Do not train it, you will break post-training/alignment, the original team was so much time creating, and it will also result in a broken model
- Gemma is an absolutely fine model, with a lot of anatomical / cultural knowledge, but...
- Make it BIGGER. Imagen/Waver papers, Minimax community text encoder replacement experiments have shown that precise world knowledge (sparse entities) is lost when you downsize the encoder. Gemma 4 31B or a very budget Gemma 4 26B A6 would have been awesome for knowledge / extrapolation / encoding
Thank you
You reply like bro will delete everything and really do something after my feedback, lmao. I mean, it's just a hypothetical idea. Qwen 3 VL series are fully multimodal and easy to finetune or adapt. I would like to see LTX 2.5 do things like Minimax-H3 do, you know?
If anything, Gemma4 12B might have better representations for visual stuff, since it's built on a unified architecture with a single model natively processing the text and the images in the same latent space.
Yes, but it's much smaller in size than Gemma 4 26B A6 or Gemma 4 31B and scaling of the encoder is much important for encoding as it embeds world knowledge and allows for (up to some extent) extrapolation of visual data-missing concepts.
And it's visual-language too, though not unified, but still vision-language
If anything, Gemma4 12B might have better representations for visual stuff, since it's built on a unified architecture with a single model natively processing the text and the images in the same latent space.
Maybe, but I think that LTX 2.5 can't handle it very well, it's hard to adapt Gemma 4 as a video text encoder.