Clarify LTXVImgToVideo's seeding for image_noise_scale
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 158
Description
### Feature Idea
Currently, it is unclear how seeding is done when using the `LTXVImgToVideo` node with `image_noise_scale` > `0.0`, which produces unexpected results in the final generation.
For example, using [your LTXV I2V workflow](https://comfyanonymous.github.io/ComfyUI_examples/ltxv/ltxv_image_to_video.json):
[LTXVNoiseIssue.zip](https://github.com/user-attachments/files/18244503/LTXVNoiseIssue.zip)
Using the enclosed files as examples, image 2 was generated using the exact workflow and seed as image 1. But because `image_noise_scale` is > `0.0`, there is some variance in the results that is neither immediately obvious nor reflected in the workflow. In this example, the cat in (1) appears to be almost squinting its eyes by the end. But in (2), the cat shuts its eyes and even lowers its head.
You may refer to the following issue for more details, using a different workflow but with the same underlying node, and even more variance in the results: https://github.com/mcmonkeyprojects/SwarmUI/issues/491#issuecomment-2561615150
On that note, would it be possible to implement something like `SamplerCustom`'s `noise_seed` and `control_after_generate` to give more control and provide more clarity on how `image_noise_scale` is being used?
Personally, at least from how I've been using it, having some noise is still desirable for LTXV to promote more motion in the final output for some images. But the randomness that goes with it when it's neither specified nor expected reduces the reliability, which in turn discourages its use.
### Existing Solutions
None. The alternative would be to zero out `image_noise_scale` to eliminate the randomness altogether, which may not be ideal in some cases.
### Other
https://github.com/mcmonkeyprojects/SwarmUI/issues/491#issuecomment-2561615150
Contributor guide
Assessment
This issue has not been assessed yet.