Skip to content

Fix stale latent_length in LTXVAddGuideMulti and LTXVAddGuidesFromBatch - #614

Open
stuttlepress wants to merge 1 commit into
kijai:mainfrom
stuttlepress:fix/addguide-latent-length
Open

Fix stale latent_length in LTXVAddGuideMulti and LTXVAddGuidesFromBatch#614
stuttlepress wants to merge 1 commit into
kijai:mainfrom
stuttlepress:fix/addguide-latent-length

Conversation

@stuttlepress

Copy link
Copy Markdown
Contributor

latent_length is not updated across multiple append_keyframe calls,
resulting in incorrect resolution of negative frame indices.

Fix: read latent_length from latent_image.shape[2] at the top of
each loop iteration, matching the behaviour of chained single-guide nodes.

…read

Both nodes captured latent_length once before the guide loop. After each
append_keyframe call the latent grows by the guide's frame count, but
latent_length stayed frozen. get_latent_index uses
latent_count = latent_length - num_keyframes to resolve negative frame
indices, so latent_count shrank with each iteration causing subsequent
guides with negative frame_idx to resolve to wrong (earlier) positions.

Fix: read latent_length from latent_image.shape[2] at the top of each
loop iteration, matching the behaviour of chained single-guide nodes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant