AUTOMATIC1111
[Bug]: Error inpainting at full resolution
Is there an existing issue for this?
- [X] I have searched the existing issues and checked the recent builds/commits
What happened?
I just did a git pull to make sure I have the most up to date build, but it's still doing this. When I try to inpaint at full resolution I get the following error unless I use it on an image that is 512x512 or turn off inpainting at full resolution.
runtimeError: Expected size of input's dimension 1 to be divisible by the product of kernel_size, but got input.size(1)=174080 and kernel_size=(340, 340).
Steps to reproduce the problem
Try to inpaint at full resolution on an image that is 512x704
What should have happened?
It should generate the new image with inpainted section.
Commit where the problem happens
737eb28faca8be2bb996ee0930ec77d1f7ebd939
What platforms do you use to access UI ?
No response
What browsers do you use to access the UI ?
No response
Command Line Arguments
No response
Additional information, context and logs
No response
looks familiar, I assume you make output size 340 * 340? have you tried make output size 320 * 320 and see what happen? for some reason it only allow numbers that divisible by 64 in the two dimensions.
looks familiar, I assume you make output size 340 * 340? have you tried make output size 320 * 320 and see what happen? for some reason it only allow numbers that divisible by 64 in the two dimensions.
I'm not sure I understand. I'm trying to use it on an image that is 512x704, not 340x340 or 320x320. I was able to generate the image at that size, and can inpaint if I don't set it to "inpaint at full resolution".
not sure if this is the same issue, but any time i experience an error when trying to do inpainting at full res, is when i have a plugin enabled like sd upscale or outpainting or something. something to check anyway.
not sure if this is the same issue, but any time i experience an error when trying to do inpainting at full res, is when i have a plugin enabled like sd upscale or outpainting or something. something to check anyway.
Thanks for the suggestion. I checked, but there wasn't anything else enabled.
