Skip to content

[LTX-2] conditioning_frame_rate (fix branch, not to be merged) - #6

Open
christopher5106 wants to merge 1 commit into
mainfrom
fix_ltx2_conditioning_frame_rate
Open

christopher5106 wants to merge 1 commit into
mainfrom
fix_ltx2_conditioning_frame_rate

Conversation

@christopher5106

Copy link
Copy Markdown

Tracking PR for fix_ltx2_conditioning_frame_rate, opened against main (the upstream mirror). It is never merged here. The commit is cherry-picked onto scenario until upstream merges it.

Upstream PR: huggingface#14967

Adds an optional conditioning_frame_rate to the LTX-2 classic pipelines and modular blocks. It sets the time base of the positional embeddings separately from frame_rate, the playback rate, which keeps driving the audio length, the duration head and the output. It is needed for Lightricks/LTX-2.5-22b-LoRA-Slow-Motion-Control, which conditions on frame_rate / speed. The default (None → frame_rate) leaves current behavior bit-identical.

Tests: test_conditioning_frame_rate_rescales_only_the_video_time_axis in tests/pipelines/ltx2/test_ltx2.py and tests/modular_pipelines/ltx2/test_modular_pipeline_ltx25.py.

When upstream merges it: delete this branch, close this PR, sync main, and rebase scenario dropping the cherry-pick.

… base from the playback frame rate

LTX-2 places video tokens on a time axis in seconds (`pixel_frame / fps`
in the RoPE coordinates), derived from `frame_rate`. Adapters such as the
LTX-2.5 Slow-Motion-Control LoRA are conditioned on a different rate
(`fps / speed`) than the video plays at. Add an optional
`conditioning_frame_rate` to the LTX-2 classic pipelines and modular
blocks: it drives the video, keyframe and reference coordinates and the
transformer's `fps`, while the audio length, the duration head and the
returned video keep following `frame_rate`. `None` resolves to
`frame_rate`, leaving current outputs unchanged.
@christopher5106
christopher5106 force-pushed the fix_ltx2_conditioning_frame_rate branch from 446cbaf to 05f0e34 Compare October 7, 2026 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant