callback postprocess_image_after_composite#14657
Merged
AUTOMATIC1111 merged 1 commit intodevfrom Jan 20, 2024
Merged
Conversation
This was referenced Jan 16, 2024
AUTOMATIC1111
approved these changes
Jan 20, 2024
Closed
Closed
This file contains hidden or 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
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
new callback callback
postprocess_image_after_compositesame as
postprocess_imagebut afterimage = apply_overlay(image, p.paste_to, overlay_image)this allows it to operate on the whole image as opposed to only the crop region when performing
inpaint_full_resbackground I got a issue post on one of my extensions
because the image region that it can operate in
postprocess_imageis cropped, the extension performs suboptimallyso I decided to add this call back after the composite result
this callback could be used for the other extensions if they need to operate on the entire image or for whatever reason they need to operate after most other post-processing extentions
actual usage pending merge to my extensions assuming that this PR is acceptable
I'm bad at naming
postprocess_image_after_compositeif anyone has better name it can be changed
Checklist: