You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently hires fix runs an initial image job at the number of input steps. If the user requests 30 steps, the worker generates a 30 step image latent with the resolution of the smallest side pinned to 512 (and the longer side, if the sizes don't match, is set so the aspect ratio is respected). The worker then runs that image latent using the same number of steps (e.g., 30 as in this example) at the final resolution.
Some thoughts on improvements:
The starting resolution and ending resolution could be API input options.
The hires steps could/should be separate, and probably should default to a small fraction of the input steps.
An option could be included to do non-latent upscales (which is to say, use a upscale model like ESRGAN) as in this comfy example.
The text was updated successfully, but these errors were encountered:
Currently hires fix runs an initial image job at the number of input steps. If the user requests 30 steps, the worker generates a 30 step image latent with the resolution of the smallest side pinned to 512 (and the longer side, if the sizes don't match, is set so the aspect ratio is respected). The worker then runs that image latent using the same number of steps (e.g., 30 as in this example) at the final resolution.
Some thoughts on improvements:
The text was updated successfully, but these errors were encountered: