Open
Conversation
…nector embeddings
… suggested params for the LTX-2.3 model
…eline to LTX2HDRPipeline
…preserved positional arg ordering
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
yiyixuxu
reviewed
May 6, 2026
|
|
||
| # Adapted from ltx_pipelines.utils.media_io.save_exr_tensor | ||
| # https://github.com/Lightricks/LTX-2/blob/41d924371612b692c0fd1e4d9d94c3dfb3c02cb3/packages/ltx-pipelines/src/ltx_pipelines/utils/media_io.py#L609 | ||
| def save_exr_tensor( |
Collaborator
There was a problem hiding this comment.
I think with this PR, encode_hdr_tensor_to_mp4 is enough, no?
can we remove all the other functions here?
yiyixuxu
reviewed
May 6, 2026
| num_frames: int = 121, | ||
| frame_rate: float = 24.0, | ||
| num_inference_steps: int = 40, | ||
| num_inference_steps: int = 30, |
Collaborator
There was a problem hiding this comment.
did they change the default since the release? 🤯
Collaborator
Author
There was a problem hiding this comment.
I ended up changing the LTX2ConditionPipeline.__call__ defaults to the LTX-2.3 defaults (since the implementation now follows the newest behavior rather than the original LTX-2.0 behavior); num_inference_steps=30 is the default for LTX-2.3, while num_inference_steps=40 is the default for LTX-2.0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
This PR adds two new LTX-2.X pipelines:
LTX2InContextPipeline, which supports in-context (IC) conditioning (used for example by some IC LoRAs) andLTX2HDRPipeline, which supports the newly released high dynamic range (HDR) pipeline (and HDR IC-LoRA) introduced in the LTX LumiVid paper.This PR also updates
LTX2ConditionPipelineto follow the LTX-2 repo's current image conditioning strategy, which overwrites the noisy latents only for first-frame (I2V) conditions and treats non-first-frame as keyframe conditions which are appended to the noisy latents. (Previously, the pipeline overwrote the noisy latents at all latent indices.)Here is an example of using
LTX2InContextPipelinewith theLightricks/LTX-2-19b-LoRA-Camera-Control-Dolly-InIC LoRA, which biases the generated video toward panning in on the subject:LTX-2.3 IC LoRA Example Script
ltx2_ic_lora_output.mp4
And here is an example of using
LTX2HDRPipelinewith theLightricks/LTX-2.3-22b-IC-LoRA-HDRHDR IC-LoRA, using the video above as the reference:LTX-2.3 HDR IC LoRA Example Script
ltx2_hdr_lora_output.mp4
This uses the default tone-mapper that simply clips HDR values to
[0, 1], which is also used by the original LTX-2 code.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.
@yiyixuxu
@sayakpaul
@linoytsaban