easydiffusion icon indicating copy to clipboard operation
easydiffusion copied to clipboard

Upscale incorrect in batch mode with euler_a sampler

Open MrManny opened this issue 2 years ago • 1 comments

Describe the bug When using the euler_a sampler and running images in batches, using the "Upscale" button will produce a different image.

To Reproduce Steps to reproduce the behavior:

  1. Create images with any prompt in batches, e.g. 9 images total with 3 in a batch.
  2. Click on 'Upscale'
  3. See that a different image is created

Expected behavior The same image, just fed through the upscaler.

Screenshots image

Here, a batch of images was generated (using batch mode). Of the three depicted here, the middle one was enqueued for upscaling. The seeds match, but the images do not.

Desktop (please complete the following information):

  • OS: Windows 11 2H22
  • Browser: Brave v1.44.112, based on Chromium 106.0.5249.119
  • Version: Stable Diffusion UI v2.23 (beta)

Additional context Likely related to #311.

MrManny avatar Oct 15 '22 14:10 MrManny

I have a feeling that at some point this got fixed, but then as the Double size was removed, this issue returned. This is due to a-samplers' results being dependent on batch size, and I certainly recall that for some time the image buttons such as Upscale were fixing it by launching the job with proper batch to reproduce exact image, but then it reverted back to old behavior.

Seedmanc avatar Oct 29 '22 16:10 Seedmanc

This is a typical behaviour of ancestral sampler. Since this can not be fixed, it was added to the user documentation. https://github.com/cmdr2/stable-diffusion-ui/wiki/How-to-Use

JeLuF avatar May 05 '23 17:05 JeLuF

What prevents you from just launching upscale with the same batch params as the image to be upscaled had? Yes, that's extra work, but that's in no way "can not be fixed", especially when it the other popular UI ancestral samplers don't depend on batch size.

As I mentioned before, doubling also used to work properly for a while exactly that way - it was launching the whole batch to get the correct ancestral configuration.

Seedmanc avatar May 07 '23 02:05 Seedmanc