wkpark / uddetailer

μ DDetailer, DDetailer fork to support DDetailer as an extension
GNU Affero General Public License v3.0
63 stars 1 forks source link

Applying Reactor and/or InstantID on segs #94

Open InspectaGadget opened 3 months ago

InspectaGadget commented 3 months ago

Hi ! I'm trying to re-set in a1111 the workflow I usually apply in ComfyUI : Applying Reactor and InstantID on segs.

Your extension is awesome ! But dealing with a1111 architecture i feel a little bit lost about how to "link" different extensions. Do you think it could be possible via a script ?

In the case that isn't clear enough i precise i would like to :

My aim is to NOT have to do this things in a post-traitement (in img2img for example), but using the initial generated pic/latent/prompts/seed, etc

Big thanks by advance if you find so motivation to answer this question !

wkpark commented 3 months ago

the uddetailer currently does not support customizable workflows, support only specific workflow internally,


so you just want to use uddetailer as an bbox/segms detector and use the masks/segms of the detected results an inputs of the Reactor/InstantID?

InspectaGadget commented 3 months ago

Thanks for answer. Yes, as you said, using the masks/segms of the detected results as an inputs of the Reactor/InstantID is exactly my aim, like i'm doing in ComfyUI. Maybe this isn't really the aim of your extension, and if so i'm sorry to want to use it this way. The fact is i'm a bit new to a1111, and this is in your extension that i better had the feeling of finding my bearings about segmenting. Have you maybe some ideas about how i could achieve this aim (in a1111) ?