-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[enhancement]: Add High Resolution fix for SDXL in the Linear Flow #6618
Comments
I think there is no need for SDXL hires fix in Invoke linear UI. I too opened a feature request to change the Hires fix logic in Invoke for SD1.5, but later realized that hires fix can be done manually on any image by just sending the image to the global initial image layer and then regenerating it at the desired denoise value and resolution. This provides a better control over the parameters for hires fix than the automatic method in Invoke. More upscalers are also coming to Invoke that will give even more options to upscale the initial image before passing it to the initial image layer while the current hires fix only provides bilinear and ESRGAN option. |
When the new upscalers are available, they can simply be added to the hi-res fix option. I agree that there are many different ways to do hi-res upscaling, including workflows involving resharpening masks and latent upscaling. However, the point of the hi-res fix option in the linear flow is to provide a simple one-click method for conducting a hi-res fix procedure. If someone downloads a model from Civitai and the default instructions say "make sure to use hi-res fix," it will be easily accessible. Ex. |
Is there an existing issue for this?
Contact Details
[email protected]
What should this feature add?
This feature will allow the high resolution fix feature in the linear flow to be used for sdxl models and not just sd1.5
Alternatives
Alternatives are to not implement this and eep it in the workflows, however this would be inconcistent with the existance of the feature for sd1.5
Additional Content
No response
The text was updated successfully, but these errors were encountered: