[LTXPipeline] Update latents dtype to match VAE dtype #11533
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
The LTX Video HuggingFace Documentation states:
This implies that the VAE dtype can be different than the rest of the pipeline. e.g. the VAE could be in fp32 while the transformer is in fp16.
However, when running with fp32 VAE and fp16 transformer, I hit the following error.
I believe the proper fix should be to ensure that the latents tensor (input) is the same dtype as the VAE (bias?). We can ensure this by casting the latents tensor to the proper dtype before the VAE decoder is run.
Before submitting
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.