Replies: 3 comments 1 reply
-
Now that I think about it, there are probably some other parameters for which this would be useful, e.g. Denoising Strength in img2img. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
well, i did write a script for... something similar... and a little bit more. additionally, i built in a "blind-folder"-option. and: there is the checkbox, which includes your init pic into your series of rendered pictures. and: there is the "Use Lexica" checkbox. Lexica recently opened up an api and provides a set of 50 items per call.
finally, the debug checkbox is just for my testing, making some things visible. that's it, basically. that said, i am no real programmer, so, expect spaghetti-code. on that point: i have not managed to avoid the seed being +1 on each image count. finally: any ideas? maybe i could just paste the code into this comment-text-field, and you generate your own python-file and place it into the scripts-folder of your own local installation? what do you think? |
Beta Was this translation helpful? Give feedback.
-
I'd like to be able to one-click start a job that runs a prompt over multiple scale values.
One option is to allow a single interval of scale values, e.g. using a two-node slider bar. But there's also a use case for allowing more complex sets. In one of my experiments, I noticed that the best results happen at scale values 9, 11, 13, 13.5, and 14. (Very random, I have no idea why.) So I could imagine having an option in Settings to toggle between several modes of specifying scale. Maybe one option is a one-node slider, and the other option is a text box that allows notation like
9, 11, 13-14
If implemented, to me the most intuitive behavior would be processing the batch size and batch count for each scale value in the specified set, so that the total number of generated images would be (batch size) * (batch count) * | scale values |.
Beta Was this translation helpful? Give feedback.
All reactions