Fix Flux Kontext ReferenceLatent and ControlNet shape mismatch #9180
Conversation
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
1 participant
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.
Summary
Allows to use Flux ControlNet with Flux Kontext ReferenceLatent
Description
Currently there's a shape mismatch in the forward_orig method due to conditioning concatentation for Flux Kontext.
Sources
Error
Kontext conditioning concat
This PR introduces a fix that pads img with zeroes along the 1st dim to match the shape.
This change is local but potentially can cause issues if the input shapes mismatch due to different reason than kontext conditioing, e.g. due to some errors.
Example workflow to reproduce behaviour
FLUX_KONTEXT_REFERENCE_PR.json
Links
ComfUI Patches II Pull Request