ltdrdata
commented
2 months ago The Image Receiver is fundamentally similar to the Load Image node. In addition to allowing users to load images by selecting them from the widget, it's a node that can receive results transmitted through the Image Sender.
This process essentially automates what would be equivalent to the Image Sender saving an image to a specific location and the Image Receiver selecting that file, just as the Load Image node would.
The Queue Trigger is designed to automate the conditional automatic execution of the next workflow once the current workflow ends. If the Queue Size is set to 2 or higher, normal operation cannot be guaranteed.
I'm working on a use case where I’m creating an infinite zoom. The image is rendered once and sent to the 'Image Sender' node, and 'Image Receiver' reinjects it into the loop. For it to work correctly, I have to wait until the queue is fully processed, otherwise, the 'Image Receiver' doesn’t get retriggered. This makes it nearly impossible to create this kind of animation. ComfyUI is up to date, though.
I have another question. What is the intended use of the 'image' widget in 'Image Receiver'? When clicked, it prompts a list of images from the disk. Ideally, we’d like to leave the image field empty, but currently, it seems we are forced to select a value.