You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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: mcmonkeyprojects/SwarmUI#491 (comment)
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.
Feature Idea
Currently, it is unclear how seeding is done when using the
LTXVImgToVideo
node withimage_noise_scale
>0.0
, which produces unexpected results in the final generation.For example, using your LTXV I2V workflow:
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: mcmonkeyprojects/SwarmUI#491 (comment)
On that note, would it be possible to implement something like
SamplerCustom
'snoise_seed
andcontrol_after_generate
to give more control and provide more clarity on howimage_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
mcmonkeyprojects/SwarmUI#491 (comment)
The text was updated successfully, but these errors were encountered: