[Question] controle_after_generate random2fixed seed, why ?
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 158
Description
I ask myself: why is that?
When I switch from random seed to fixed seed, exactly one queue remains and ruins my last image.
I have found a lot of workarounds, for example with "global seed node" from Inspire or ksampler from efficiency-nodes or even the temp folder or history.
but now from the product design point of view: when i switch to fixed, i assume that the seed is fixed at that moment or not? similar to the behavior as it is in a1111. you set the seed from random to fixed and the just generated image is shown again.
If I for example look at a model all the time via preview node, then found a great result, then set the seed to fixed to attach a save node, it would be expected that this image is then also saved and not another is created and the seed is perhaps lost.
do you know what i mean ? is this a per design question, so is this intentional or just technically not so easy to solve, or maybe even just a bug ?
i hope you can enlighten me on this
thank you and sorry for my maybe very stupid question.
Contributor guide
Assessment
This issue has not been assessed yet.