interrupt upscale #15380
Merged
interrupt upscale #15380
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
light-and-ray
force-pushed
the
interrupt_upscale
branch
from
3cfefea to
c321680
Compare
AUTOMATIC1111
approved these changes
Mar 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
after pressing "interrupt" button, for example inside inpaint tab, upscaling with ai still will be used, if
opts.upscaler_for_img2imgis overridden. It takes a ton of time for upscaling e.g. 512p -> 4k, especially for DAT upscalers. It can be stopped only is server is stoppedI've added two checks for interruption flag inside
do_upscaleandupscale. It still upscales images, but with LanczosChecklist: