-
Notifications
You must be signed in to change notification settings - Fork 47
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
Do we need to do all those conversions for inpaining? #13
Comments
Thanks for your interest! @geekyayush
|
Hey just following up here ! This might be a newbie misconception but if we replace the unet here do we not loose the custom model in this case the Anything v3 . Or is it really just replacing the inpainting channels ? |
Thanks @haofanwang ! I have another question regarding this.
Here, for the pipe_control, I am using the same Thanks! |
Let me answer all you guys concerns here. @UglyStupidHonest You are right, for now, if you want to equip ControlNet with inpainting ability, you have to replace the whole base model, which means that you cannot use anything-v3 here. I did try to only replace the input layer and keep all other layers in anything-v3, but it works bad. @geekyayush If you inpainting model has the exact same layers as stable-diffusion-1.5, then it should work. You can just take ControlNet as a pluggable module that can insert into all stable-diffusion-1.5 based models. |
Is StableDiffusionControlNetInpaintPipeline currently operable? Trying the sample code in this repo with the provided input images, segmentation map, and specified models, gives the following result in my environment: ╭─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮ |
Hello
Do we need to do all those conversions mentioned under "ControlNet + Anything-v3" for inpainting?
Also, in the inpainting guide, there are these lines
Can anyone help understand what does the 2nd line means?
Also, for
pipe_inpaint
, do we pass the stable diffusion diffuser model path?The text was updated successfully, but these errors were encountered: