-
Notifications
You must be signed in to change notification settings - Fork 29
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
[FEATURE REQUEST] - Batch support on ComfyUI #13
Comments
Please submit issues related to the ComfyUI node version in the node version repo next time, thx. Actually, someone has already made exactly the same request to me before. The reason why the image loader cannot connect with the reader is that the image loader outputs the image itself, which is a bunch of pixels, and does not include any metadata. So even if they could connect, the reader wouldn’t be able to read anything. Of course, I’m very interested in the batch loading you mentioned. If possible, please post your batch loading workflow here. Since the reader itself is an image loader, perhaps features suported by other image loaders could also be implemented on the prompt reader. |
This feature seems to be feasible, I'll consider it. |
Just a +1 to say this node is exactly what I've been looking for to finish an A1111 based 1.5 to SDXL Upscale Workflow and literally the only thing missing is batch processing, would be perfect in that case. |
@Tirshea @PSVinrael Simply connect the |
Summary
First, thank you for the node suite. I've been playing with it the last few days and it screams "must-have batch tool for upscaling workflow from low-quality rushes/seed images".
The abilty to load images with their metadata is awesome, especially when - like me - you use wildcards a lot.
But when we design an upscaling workflow, we most likely want it to support batch loading.
I tried the obvious way with "convert image to input" on the reader but I couldn't find any node able to link to this "image" input.
Basic Example
Abillity to connect image loaders to SD_Prompt_Read node.
Reference Issues.
No response
The text was updated successfully, but these errors were encountered: