This is development at its most dynamic (thus: epic!!). ComfyUI has become my daily goto for creating. I haven't explored a tenth of what's on offer, either - although subgraph I found immediately irresistible. Strong work, very impressed!!
I thought they were at first. But what is the benefit if they weren't, since we already have the old Node Templates feature and the new Add Subgraph to Library option? The only difference I can see is that the published subgraphs are searchable; it would be nice if the already created instances were all synchronized.
"blueprint" seems to imply these work rather as matrixes that spit out whatever saved copies, than getting parsed as regular nodes. in fact as such they would exist almost like "in between" workflows and nodes somehow. i guess having them under nodes may feel confusing at first, but personally i'm used to it as that's how the analogous "hdas" work in houdini eg. anyways i still gotta try em out
This is development at its most dynamic (thus: epic!!). ComfyUI has become my daily goto for creating. I haven't explored a tenth of what's on offer, either - although subgraph I found immediately irresistible. Strong work, very impressed!!
Impressive job! Bravo 👏🏻👏🏻👏🏻
Keep up the great work 💪🏻
Nice work !!! It'll help a lot. Your tool is magic ;)
I use comfy embedded with Python how the hell do I update without creating an absolute nightmare for myself? Thanks
This is very useful, Thank you
If I change the subgraph, does it also change all its used instances?
No, they aren't linked.
I thought they were at first. But what is the benefit if they weren't, since we already have the old Node Templates feature and the new Add Subgraph to Library option? The only difference I can see is that the published subgraphs are searchable; it would be nice if the already created instances were all synchronized.
Ok. Do you already know when that will be supported?
"blueprint" seems to imply these work rather as matrixes that spit out whatever saved copies, than getting parsed as regular nodes. in fact as such they would exist almost like "in between" workflows and nodes somehow. i guess having them under nodes may feel confusing at first, but personally i'm used to it as that's how the analogous "hdas" work in houdini eg. anyways i still gotta try em out