zero01101 / openOutpaint

local offline javascript and html canvas outpainting gizmo for stable diffusion webUI API 🐠
MIT License
507 stars 44 forks source link

I'm having a problem using ControlNet In/Outpainting #291

Closed marc2608 closed 2 months ago

marc2608 commented 2 months ago

Hello, I've reproduced the steps in the "outpainting" video, which shows how to use ControlNet In/Outpainting with inpaint_only+lama pre processor and the control_v11p_sd15_inpaint model [ebff9138]. There's probably a detail or a little thing I can't figure out because I can't get outpainting. Every time I get random images that have nothing to do with the background image. (It could be a woman, a car, a house, an animal etc...) Can you tell me if I'm missing something, an important detail or something else? Here's photos of my session. Thank you in advance. Capture d'écran 2024-08-07 170105 Capture d'écran 2024-08-07 170049

Nacho-sh commented 2 months ago

Same problem here. I had this problem a year ago, the issue was that I hadn't installed the .yaml settings file for controlnet. However, I've reinstalled this and I can't get it to work. Check out if you've downloaded that file anyways.

zero01101 commented 2 months ago

hey, so it looks like controlnet deprecated the input_image parameter a while ago and i'm a terrible project maintainer and didn't notice :/ should be updated and fixed now, sorry about that

Nacho-sh commented 2 months ago

Now, this is good service. Works perfectly now, thank you so much!

marc2608 commented 2 months ago

Hi, I get this message in the CMD window (see photo). Can you tell me if there is a file in OpenOutpaint or in Controlnet that I can modify myself to make it work? Capture d'écran 2024-08-09 181001

zero01101 commented 2 months ago

Hi, I get this message in the CMD window (see photo). Can you tell me if there is a file in OpenOutpaint or in Controlnet that I can modify myself to make it work? Capture d'écran 2024-08-09 181001

yeah, that's precisely what the update is supposed to fix- i'm guessing you've pulled in the most recent updates? you can also go to the debug info section and check the version, if it's not reporting v20240808.001 then make sure you're fully up-to-date and try force-refreshing (shift? ctrl? one of them)+f5

marc2608 commented 2 months ago

Sorry, it was a mistake on my part, a wrong reinstallation of the extension. With many thanks for having worked on and succeeded with such a well-made and powerful tool!