-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[V3] convert nodes_controlnet.py to V3 schema #10202
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
[V3] convert nodes_controlnet.py to V3 schema #10202
Conversation
+label: Core |
To avoid code duplication, we should probably extract the contents of controlnet nodes into their own functions, and then we can reference it from all controlnet nodes. It should not break any custom nodes that are importing the nodes from nodes.py as well. |
f3bd8b5
to
d0b4966
Compare
I have force pushed g the new version without duplicating or extracting code, where we simply call the old node without inheritance. What do you think of the new version? |
it looks ok. the nodes inside node.py will be the last to be converted (and at an unknown time), so this should do for now. in the long term we'd probably want to extract the controlnet function and make it generalizable for 'n' amount of conditioning. i'll start sending out notices to node authors for nodes_controlnet.py |
d0b4966
to
d3e43bc
Compare
added |
Node authors notified, will merge on Friday October 17th. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The time has come.
Node
ControlNetInpaintingAliMamaApply
was tested after conversion:Link to the sources of the
ControlNetApplyAdvanced
node that was copy-pasted intoControlNetInpaintingAliMamaApply
node:ComfyUI/nodes.py
Lines 874 to 900 in bbd6830
Objects git diff: