-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
ADetailer not functioning correctly #55
Comments
That's odd, I must have introduced an issue at some point. I haven't used ADetailer for txt2img in standard .prompts files since implementation so I'm actually not even 100% sure it ever worked properly, now that I think about it (I do all of my ADetailer work in batch via process .prompts files). Will look into it, but it may take a bit as I'm currently traveling! In the meantime, if you generate images normally without ADetailer, and then set aside images that need ADetailer face/hand/whatever replacement, you can use something like this .prompts file to process them all at once (this should definitely work for you as I've been using ADetailer via process files several times a week):
|
Had a chance to play with this today, and while ADetailer is definitely working, there is a strange bug with txt2img requests in the ADetailer extension itself. Any txt2img job that utilizes ADetailer executed via the API from Dream Factory will actually get executed twice - unfortunately this needs to be fixed by the people maintaining the ADetailer extension; the API request from Dream Factory is correct. My test .prompts file is below - I generate a standard txt2img image without ADetailer, and then ask for the same image with ADetailer enabled to replace the face (from a young woman's face to an old one). I end up with 3 images from Dream Factory, when I should obviously only get 2. I'm running the latest version of everything (Dream Factory, Auto1111, and the ADetailer extension). Dream Factory output from the .prompts file below: 1st ADetailer image (this matches what I get if I run this job directly via the Auto1111 UI): 2nd ADetailer image (appears to be the same ADetailer job run against the image above): My .prompts file:
|
When using the ADetailer, the system outputs the main image but then outputs a second low quality image, similar in composition but a different image. The ADetailer does not inpaint the main image and appears to have no impact on its generation.
The text was updated successfully, but these errors were encountered: