4 ms·
You can always reproduce the exact image by using the same prompt, seed value, and config info (assuming you've created the image with SD to start with).
by bitshiftfaced 4y ago
You can always reproduce the exact image by using the same prompt, seed value, and config info (assuming you've created the image with SD to start with).
- dr_dshiv 4y agoIs there a unique image identifier system that might facilitate the preservation of this metadata?
- WheelsAtLarge 4y agoYou would think but there seems to be some kind of randomization added to the image creation. You can use the same prompt over and over again and get different images.
- bitshiftfaced 4y agoWhen I use the same seed and same prompt, I get the same image.
- astrange 4y agoCompression algorithms using floating point have always been flaky though. Need a fixed-point image model.
- WheelsAtLarge 4y agoYou are correct. My mistake.
- nextaccountic 4y agoSame seed, same prompt and same hardware perhaps, if the GPU concurrency doesn't introduce nondeterminism. Otherwise you might have the same problem of this: https://github.com/EmbarkStudios/texture-synthesis#notes https://github.com/EmbarkStudios/texture-synthesis#notes > When using multiple threads for generation, the output image is not guaranteed to be deterministic with the same inputs. To have 100% determinism, you must use a thread count of one, which can by done via > CLI - texture-synthesis --threads 1 > API - SessionBuilder::max_thread_count(1)
- Agentlien 4y agoI've played a lot with this and I get the same image using the same prompt and seed. I've also played a lot with slight variations on the same prompt and it's really fascinating seeing how similar the images are outside of the specific detail changed. I would say this diffusion model is very... stable.