Skip to content
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

[Bug]: Batch img2img with SD Upscale not working correctly #14114

Closed
1 task done
Stibo opened this issue Nov 26, 2023 · 3 comments
Closed
1 task done

[Bug]: Batch img2img with SD Upscale not working correctly #14114

Stibo opened this issue Nov 26, 2023 · 3 comments
Labels
bug-report Report of a bug, yet to be confirmed

Comments

@Stibo
Copy link

Stibo commented Nov 26, 2023

Is there an existing issue for this?

  • I have searched the existing issues and checked the recent builds/commits

What happened?

Looks like there's a bug if you use the batch img2img functionality together with the script "SD upscale". The file will be saved as usual in the general output folder, but not in the directory that was defined in the batch settings "Output directory". It only occures if you use a script (tested with "SD upscale" and "Ultimate SD upscale"). Looks like then the file is not written in the "Output directory". If you don't use any scripts, the file is correctly generated in this output directory.

I even created a whole new automatic1111 installation without settings, extensions and custom models, it does not work even then.

Steps to reproduce the problem

  1. Go to img2img tab
  2. Select "Batch"
  3. Set an "Input directory" and an "Output directory"
  4. Move any image to the "Input directory"
  5. Use any settings you like
  6. Enable the script "SD upscale" and use any settings you like
  7. Press generate
  8. The output directory of step 3 should be empty

What should have happened?

There should be the upscaled image in the output directory defined above in step 3.

Sysinfo

sysinfo-2023-11-26-16-02.txt

What browsers do you use to access the UI ?

Google Chrome

Console logs

Nothing

Additional information

No response

@Stibo Stibo added the bug-report Report of a bug, yet to be confirmed label Nov 26, 2023
@w-e-w
Copy link
Collaborator

w-e-w commented Nov 26, 2023

I see you ar using webui 1.6.1
I believe this issue has already been fixed in dev branch
see #13170

@w-e-w w-e-w linked a pull request Nov 26, 2023 that will close this issue
4 tasks
@w-e-w w-e-w removed a link to a pull request Nov 26, 2023
4 tasks
@w-e-w w-e-w closed this as completed Nov 26, 2023
@Stibo
Copy link
Author

Stibo commented Nov 26, 2023

So this is only available in the dev branch, not in the master one? Because thats the one I used in all installations

@w-e-w
Copy link
Collaborator

w-e-w commented Nov 26, 2023

yeah the fix it's currently only in dev
not sure when will AUTO release webui 1.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-report Report of a bug, yet to be confirmed
Projects
None yet
Development

No branches or pull requests

2 participants