adetailer VS sd-webui-regional-prompter

https://github.com/Bing-su/adetailer works very well on faces and hands.

This is a good solution for all the use cases I’ve dealt with.

Are there widespread use cases where, knowing a deformity exists is required than just fixing the deformities?

Ive found using ADetailer (https://github.com/Bing-su/adetailer, using their reccomended advanced settings and face_yolov8n.pt) and Dynamic Thresholding (CFG set to 12 and Mimic to 7) has vastly improved my face renders. (https://github.com/mcmonkeyprojects/sd-dynamic-thresholding) GL!

ADetailer: https://github.com/Bing-su/adetailer

After Detailer will give each of their faces a facelift

this is amazing and easy workflow for production, but the lora part of adetailer never works for me, i don't know why

So I'm using the Regional Prompter extension https://github.com/hako-mikan/sd-webui-regional-prompter

But using Automatic1111, this extension can define a region of the image where the prompt should apply: https://github.com/hako-mikan/sd-webui-regional-prompter

Second, install regional prompter and adetailer to automatic1111 webui.Next, go to setting>adetailer and change the "sort bounding boxes" from "none" to "left and right". This means that adetailer will inpaint our subjects starting from the very left to the right, allowing for greater control of what we want.

You can use ControlNets to control composition in various ways. You can use extensions like multidiffusion upscaler and regional prompter to control the layout of a scene. You can also inpaint details into a scene with the arrangement you want.