Closed nodegraphics closed 1 month ago
There are some tricks, but it's correct to assume that it's not fundamentally guaranteed. (Especially since the workflow execution method is going to change drastically next week's update, it's unpredictable.)
The important question is: why do you need the execution order?
Got it, then it's worth waiting for now. We can revisit this question after I work with next week's update maybe ? at least for tricks that might be worth to explore.
To answer your question: The reason I asked is that I sometimes have more than 3-4 different setups in single workflow, and it sometimes starts with the slowest and most time-consuming one. If I could determine the order, I would always have an initial fast version as a preview to check if everything is good before letting the queue move forward to complex / hires setups.
I added Execution Order Controller
node.
You can control execution order via this node.
Thank you so much 🙏 you are awesome !! @ltdrdata just to understand better. I would like to ask couple of questions about the node:
1) i add this node to whichever setup i want as initial run right ? and Signal
can be a latent or image depending on the setup ?
2) Can i chain them up and take the signal from each other ? (image attached)
workflow
screenshot for 2
Signal and value can be arbitrary types.
They are passed to output without any touch. It's just a trick node.
I love it !! Thank you
Hello,
I would like to know if it is possible to determine the order of iterative upscale elements. I sometimes use more than one, and I notice that instead of starting from the beginning, it seems to go randomly, or perhaps it follows an order that I am not aware of. Is there a way to determine which one to go through first, second, and so on?