hi-res for txt2img and i don't like it #7059
Replies: 5 comments 4 replies
-
I mean, for me it does exactly what it says, it gives a higher res image and it fixes it. Some models and styles really need and benefit from a second pass to fix wonky details, and the highres pass does that. That's usually more than enough for me 99% of the time to produce a good image. For more control or harder generations there's always img2img and inpainting. |
Beta Was this translation helpful? Give feedback.
-
Wouldn't be able to make this in txt2img without it |
Beta Was this translation helpful? Give feedback.
-
See also "Bring back old Hire.Fix": #6725 |
Beta Was this translation helpful? Give feedback.
-
@dominikmau You're right that it could be designed differently, but we have at least a couple of more options now. I use Hires fix. maybe a bit differently. I have been using Hires. fix for almost every image since SD2 launched. I mostly generate images in 1024x768 with DPM++ SDE Karras (30 Steps, 7.5 - 9 CFG).
The fidelity and quality that I'm getting as a result is something I have not been able to reproduce otherwise. This means the Hires. fix image is my actual real resulting image and not the 1st pass without it. |
Beta Was this translation helpful? Give feedback.
-
<On the other hand i can't see a real advantage of txt2img hi-res over img2img.> I'm glad I read this post. If I did a txt2img at 768x768. The image takes around 4-7 seconds to render, depending on sampler. If I turn on highres.fix, and punch that to 1536*1536, the damn thing takes around 1 minute 17 seconds. If I use the same seed, take the original 768x768 and popping it into img2img, and adjust the res to 1536x1536, use Heun at 30 steps -> I get an image back in around 22 seconds. If you compare the highres.fix image and the img2img.....i get a BETTER quality image with img2img than highres, at almost 3x the speed! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I had a brief conversation about the hi-res feature and I've been bothered by it for a while.
First of all, I like the new design and functionality of hi-res - but what do I want with it in txt2img, I need the crap in img2img. (with all its functions - sexy latent antialiased)
So far i generate batch e.g. 100 images 512x768, look through them if there is an image i like and worth to upscale - then i send it back to txt2img and generate the same image with hi-res 1024x1536. (after that i usually scale it again with ultimate sd upscaler in img2img etc.)
In img2img there are so many more possibilities:
Of course img2img is nice even now, but it could be a nicer.
On the other hand i can't see a real advantage of txt2img hi-res over img2img.
a) generate 20 images with hi-res without knowing if the images are without errors/deformations or if you like the image at all, etc.
(you eat what you get)
b) 100 images and you pick the handful you like from the appearance and scale them up yourself with a hi-res function in img2img which has the same functionality as in txt2img.
(you eat what you choose)
Is my thought that far-fetched?
I really celebrated when latent upscaler came for img2img because that's where it belongs for me. Hope the rest comes soon too.
(may be i am just imagining it, but for the first upscale i find the hi-res function in txt2img almost always generates better results than img2img)
Beta Was this translation helpful? Give feedback.
All reactions