-
Notifications
You must be signed in to change notification settings - Fork 27.1k
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
[Bug]: Bug in AUTOMATIC1111 when running ControlNet and Inpaint in "Only masked" and "Mask blur" > 0 #12428
Comments
I can replicate it but I'm not fully convinced it's a webui issue yet.
Can you provide the commit hash for your backed up webui version? As well as the old ControlNet version? If so I can do a bisect of this to see if this is true or not. |
Actually, I see what the problem is now... it is, however, not the webui's fault per se. I'll open a PR upstream soon for the extension. |
My backup has a hash 22bcc7b I was also able to update it to cf28aed |
Thanks -- as I mentioned though I actually did figure this out now. I made a PR (#12470) that is available on the |
Is there an existing issue for this?
What happened?
When working with Inpaint in the "Only masked" mode and "Mask blur" greater than zero, ControlNet returns an enlarged image (by the amount of Mask blur), as a result of which the area under the mask increases:
These settings were used:
These settings gave the same result.:
my software version Windows 10
I use a 12Gb RTX3060 graphics card, 16Gb RAM
This is definitely a mistake, since mask blur should lead to an increase in the width of the mixing zone between the embedded image (drawn in Inpaint) and the source, and not to an increase in the image inside the mask. I repeat, everything worked correctly before and I have a backup copy of AUTOMATIC1111 that has not been updated for several months and everything works correctly there!!! And it seems to me that the problem is in AUTOMATIC 1111, since updating ControlNet to the latest version in my backup did not lead to an error, but updating AUTOMATIC1111 led to its occurrence.
Steps to reproduce the problem
Upgrade AUTOMATIC 1111 to version 1.5.1
Go to Image To Image -> Inpaint put your picture in the Inpaint window and draw a mask. Set Mask Blur > 0 (for example 16).
What should have happened?
This is definitely a mistake, since mask blur should lead to an increase in the width of the mixing zone between the embedded image (drawn in Inpaint) and the source, and not to an increase in the image inside the mask.
Here is another example with another picture:
If Mask blur=0 then everything is correct:
Version or Commit where the problem happens
v1.5.1
What Python version are you running on ?
Python 3.10.x
What platforms do you use to access the UI ?
Windows
What device are you running WebUI on?
Nvidia GPUs (RTX 20 above)
Cross attention optimization
sdp-no-mem
What browsers do you use to access the UI ?
No response
Command Line Arguments
List of extensions
Вut I also checked for this bug in the new clean install of AUTOMATIC 1111+ ControlNet only
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: