-
Notifications
You must be signed in to change notification settings - Fork 86
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
[Feature Request]: Use Refiner, if given #164
Comments
This extension uses the refiner. If you specify both the base model and the refiner in the Web UI, it will use both for face modification as well as for source image generation, and if you specify the refiner model instead of the base model, it will use the refiner model for face modification. |
I can't quite follow you. I want to use both the base model and the refiner in the image generation, but only the refiner in the extension. I don't see any option to only use the refiner, so the extension makes the face worse as my base model is worse than the refiner. That is my problem. |
Okay, I understand. You want to use only the refiner. In that case, I think it would be effective to specify refiner instead of base model in img2img, set denoising strength to 0, and use Face Editor to modify the face. Have you tried this? |
The only reason why I want this is to automatically inpaint after generation not to extra send it from text2img to img2img. |
@ElPrudi It can be used in the following workflow:. {
"face_detector": "RetinaFace",
"rules": {
"then": {
"face_processor": {
"name": "img2img",
"params": {
"use_refiner_model_only": true
}
},
"mask_generator": {
"name": "BiSeNet",
"params": {
"fallback_ratio": 0.1
}
}
}
}
} Please try it out. |
Thank you! The faces look much better now! |
It came to my attention that this extension does not use the refiner, if I specified one. Since it's a inpaint extension, I would love the option to use the refiner instead of the base model for the whole process.
The text was updated successfully, but these errors were encountered: