-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Save Image KJ (batch) #169
Comments
How are you repeating it exactly? If you use the ComfyUI queue feature and just queue 100 times, it should save the image on each run. If you are doing a huge batch instead, then the results are indeed only saved when the whole batch is done, that's just how batches work. |
At first I did it wrong, comfy-ui is very incomprehensible to me. Now I have built such a structure, it seems to do the job as I wanted, except for a few nuances. File with prompts, I do not know the size of its lines and it is not output, what queue should I set? What will happen if the counter exceeds the number of lines in the file, will it go in a circle? |
I'm not familiar with that particular "Text Load Line From File" -node, but if I were to guess it would indeed either loop or just error out. |
Oh no, batch can't be set to more than 100. I like comfy-ui less and less. |
I think you can still just click Queue multiple times, and each click would add 100? |
I tried this, it starts again from 0, not from 101, 201, 301... |
And also about Save Image KJ |
Hello.
I have a problem. For example, I need to repeat generation 100 times.
And at some point I don't want to wait any longer and press cancel.
At the same time, for example, 50 iterations have already been processed, but after pressing cancel, comfy-ui does not save anything, it deletes everything.
The output folder is empty, 50 iterations were processed, but lost.
Why is that?
Unlike FORGE, which during batch processing throws each new result into the output folder, and does not wait until they are all processed.
How can I fix this behavior, it is very inconvenient?
The text was updated successfully, but these errors were encountered: