How about adding a Higres fix button to the options under the generated image?

[Juun625]

So I have a bit of frustration with the interface and I'm not sure if there is currently a better way of doing this. So basically I generate a batch of 4 images, then I choose the best one to do a highres fix on, what this involves is selecting the image, then enabling highres fix, setting batch count to 1, then clicking the reuse seed button, then click generate. so when that's finished I want to generate another 4 images, so I have to do all of those steps but in reverse, click random seed, disable highres fix, set batch count to 4, generate, rinse and repeat. Is there a better way of doing this?

[w-e-w]

hiresfix is just txt2img -> upscale -> img2img
so the way of doing this is to send the chosen image to img2img by clicking the send to img2img button under the gallery

---

I think they can be some improvements to this workflow

[Juun625]

I see, it is better this way, except I use different number of steps for highres fix, so I have to change the steps every time.

[Juun625]

Also I seem to get different results from highres fix, sometimes worse, sometimes better, even though I use the same settings. I gues it's because highres fix gets the latent image directly, but img2img has to convert the image back to latent?

[w-e-w]

like I said

I think they can be some improvements to this workflow

I'm currently working on extensions about hires fix
I might consider adding, I might try adding something to improve the workflow
no promises but keep an eye out if you're interested
https://github.com/w-e-w/sd-webui-hires-fix-tweaks
(still in development don't use it now unless you want trouble)

[Juun625]

Seems interesting,will definitely keep an eye on this, thanks. I just don't get why such a simple feature haven't been implemented yet.

[Soulreaver90]

You described my exact workflow and its ungodly annoying. I saw a discord post months ago where someone created a custom button that would do both a hireres and "extra" upscale all at once. I wish I was knowledgeable enough to do that, a hireres button under the photo that upscales based on a predefined setting.

[AUTOMATIC1111]

I added the button to the dev branch.

[stduhpf]

I'm just highjacking this discussion to ask if it would be realistically feasible to keep the last image batch latents in a temp cache, in case we want to use Hires. fix on them without re-doing the lowres steps?

[w-e-w]

the seed issue should be fix now #14598
note but they might be other potential issues, this is also still in dev branch so things might change and break in other words used with caution if you care about reproducibility

---

I'm just highjacking this discussion to ask if it would be realistically feasible to keep the last image batch latents in a temp cache, in case we want to use Hires. fix on them without re-doing the lowres steps?

I think the new button is is basically what you asked just not in latent
with the new button you can just generate first pass images, then select the image you wish then proceed with hires pass
it doesn't do the first pass again

or are you asking about something else

[stduhpf]

with the new button you can just generate first pass images, then select the image you wish then proceed with hires pass
it doesn't do the first pass again

So if I understand correctly what you are saying, the new button does:
first pass -> VAE decode -> lowres image -> Button press -> VAE encode -> upscale -> second pass -> VAE decode -> hires image
What I am talking about is something like:
first pass -> save latents -> VAE decode -> lowres image -> Button press -> upscale saved latents -> second pass -> VAE decode -> hires image
Unless that's already what the button does then nevermind.

[w-e-w]

note I'm currently very tired, I might recall things wrong

no the latent does not get saved and reused
the button is just a convenient button to use the same current configuration for the high-respass
basically it allows you to easily run the first pass on the highest pass separately in different jobs

in different jobs everything in between needs to say to storage as image the server does not remember that you did the job before
(the server can be restarted between the button press if you want)
the latent is re-encoded from image

---

also I'm pretty sure you have miswritten some of the hires fix pipeline sequence
but I'm too tired now so I don't care

[stduhpf]

the latent is re-encoded from image

At first I thought that would mean a loss of information, but after thinking about it for 2 seconds, I realized that if the image was already encoded byt the VAE, then this should not discard any information. So forget everything I said, the new button implementation is as good as it needs to be.

also I'm pretty sure you have miswritten some of the hires fix pipeline sequence

That's possible, I was kinda tired too