Skip to content
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: ControlNet and Pose - Load order #36

Open
NamelessButler opened this issue Apr 20, 2023 · 0 comments
Open

Bug: ControlNet and Pose - Load order #36

NamelessButler opened this issue Apr 20, 2023 · 0 comments

Comments

@NamelessButler
Copy link

NamelessButler commented Apr 20, 2023

Overview

Alright found out a funny interaction with ControlNet and Pose.
It's related to folder named and load order between these two.

What's happening?

I have both my extension folders named, Control-Net and Posex respectively.
• So what happening?
I was always having an issue related to Control-Net saying it was active but no image was used.
After a couple trial and errors, switching back and forth between Posex commits, I decided to a quick test.
Namely making pose "load" before control net by renaming their folders to 00-Posex and 01-Control-net.
For my surprise it worked, no longer those errors.

Commit where this happens:

233daf8e1460c90d24a0f8c21bc5ec712ee258df

And prior.

Additional Notes:

Could we have a retro-compatibility for gradio 3.16 ?
After most recent Posex updates starting from commit a1cdda Posex stopped working with gradio 3.16.
It shows up in WEBUI, but it doesn't launch when clicked in [ ] send to controlnet.

Automatic1111 was having too much issues, so I switched anapnoe fork.

• Thanks for your amazing work •

@NamelessButler NamelessButler changed the title [Bug]: ControlNet and Pose - Load order Bug: ControlNet and Pose - Load order Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant