Closed rockerBOO closed 2 years ago
So I think if you use the frozen seed option it will freeze the seed for each slice of the gobig operation, however the way that PRS slices up the images and rediffuses them, it is going to try to create everything you put in the prompt into each slice. If you want coherence, you should create images, then use them as an init image for gobig with a different prompt. Possibly adjusting the prompt for each individual slice manually.
Currently there are no automated processes to do such a thing. The closest was the JAX/HUEMIN Collab notebook, but I never even got that working properly.
If you want it to do a new image and go big for each image, you can try using the from_file option to specify a text file.
For each line in the text file it will run N batches and N iters, as well as run GOBig after each one. (At least I think that's how it works. I don't know that I've tested it but it's how I expected it to work when writing the GUI.)
Thanks for the feedback @KnoBuddy . Some of these could be workarounds but not sure if any of them actually would work. Even doing 1 batch and 1 iters it still recalculates the prompt (im using placeholders).
Keeping a static prompt or using a init_image could work to make it bigger with 1.0 init_strength could work for now. But could just use the realesrgan (set scale) separately to do something like that?
I was considering how gobig was working and I can somewhat see how the seed wouldn't be a big deal but I think changing the prompt (when using randomizer) is a mistake.
The batches/iter only do gobig on the last one or an additional run (I'd have to clarify) and not for each created image. I feel this makes it difficult to work with both. I can probably look into the logic and resolve this factor if it's desired.
Use from_file to perform gobig at the end of each prompt. Each batch is run n_iter times for each line of the file specified in from_file in the json
I feel this is all probably as intended, and there's a large section of the README that details some of these concerns at this current time. I will consider some of these changes to workaround, as well as possibly making it more flexible and more consistent in how it works.
Big fan of this repo and with the new memory changes added I was able to create 1024x1024 images with the image creation. Thanks for adding this, as the many features of this repo have been very fun to play with.
I was starting to play with the gobig thing with the realesrgan option. But when making the big image, it creates odd images. It seems to re-evaluate the prompt and also increment the seed. This doesn't seem like what it should be doing.
My expectation is when making a gobig image, it should freeze the seed and the prompt. Also, it only seems to make a gobig version for the last image in a batch/iter, but would be cool if it did it for each one.
No worries if this is not ideal or otherwise not desired to do.
Partial output
Another example