-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
Use refiner with SD1.5 models #13063
Comments
you're not supposed to be able to mix SD1.5 with XL refine |
someone seems to be interested in making this possible |
in original Fooocus latest release from Ilia, Fooocus_win64_2-1-754 based on CUDA 12 and Pytorch2.1, there is a possibility to use SDXL as base and SD1.5 as refiner so the opposite should be possible as well (technically)? not in fooocus thou but in 1111 or ComfyUI? |
In ComfyUI this is also possible through workflows or extensions (see links). It would be great to have this feature in A1111. Until supported, we will have to manually use img2img I guess, but thank you for looking into this. |
I knew about SD-Latent-Interposer |
I think what you are describing is what the sd-webui-refiner extension does. |
Is there an existing issue for this?
What happened?
Set VAE to Auto and sometimes it would work correctly but on a 2nd try after it would generate fried images similar to incorrect VAE selection which I think is what's happening. Was testing it while using Ultimate upscale and sometimes 1 tile would be fried while others were good. Subsequent tries led to all tiles being scrambled and continues to get worse.
May be related to this issue which is something to do with XL models somehow polluting the memory even after unloading and loading new checkpoints.
Settings: no caching of VAE, 2 checkpoints cached with 1 one on device selected
Steps to reproduce the problem
What should have happened?
Uncorrupted images
Sysinfo
Linux Ubuntu 22.04 6800XT 32GB ram
What browsers do you use to access the UI ?
No response
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: