search

ltdrdata / ComfyUI-Workflow-Component

This is a side project to experiment with using workflows as components.
GNU General Public License v3.0
219 stars 9 forks source link

[feature req] Can't do Different Controlnet Loader Inputs #22

Open roop03988 opened 1 year ago

roop03988 commented 1 year ago

The components work great! I dunno why the description says otherwise as I never gotten into any bug so far, but was just wondering, is it possible to have separate naming for input variables, e.g. for Controlnet, they're all controlnets and when I tried to stack inpaint + others, it isn't working because the component only recognizes the controlnet as one variable and when I use it as a component there is only one input socket even though I created 2 different input nodes inside the component.

roop03988 commented 1 year ago

Oh wait, I can just use a stacker, but still, if I have a complicated workflow with multiple controlnet stacks it's the same problem, hope you can consider! :)

ltdrdata commented 1 year ago

The current workflow component is undergoing a complete overhaul to address many of the issues that have arisen from the current structure. This includes changes to the component's input/output nodes as well as the internal logic nodes.

roop03988 commented 1 year ago

got it, will wait for that! thanks :)

roop03988 commented 1 year ago

Sorry, just another question, is it possible right now to run this via the API?

I got this error always:

KeyError: 'extra_pnginfo'

ltdrdata commented 1 year ago

Sorry, just another question, is it possible right now to run this via the API?

I got this error always:

KeyError: 'extra_pnginfo'

Are you using the latest versions of both ComfyUI and Workflow Component?

Furthermore, if you update both of them to the latest versions, you'll also need to update other custom nodes used in the component to the latest versions. There have been recent changes to the node structures, so the component has been patched for compatibility with those changes.

ltdrdata commented 1 year ago

Ah, you're looking for usage through an API. That's a bit different. Currently, there's no consideration for usage via an API.