fix(flux2): apply BN normalization to latents for inpainting #8868
+22
−6
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
The FLUX.2 Klein transformer operates in BN-normalized latent space, but init_latents from VAE encode were not being normalized before being passed to the InpaintExtension. This caused a scale mismatch when merging intermediate_latents (normalized) with noised_init_latents (unnormalized), resulting in visible artifacts at mask blur boundaries.
Now normalize:
init_latents_packedbefore passing to InpaintExtensionnoise_packedfor correct interpolation in normalized spacex(starting latents) for img2img/inpainting workflowsRelated Issues / Discussions
Reported issue: Strange artifacts appearing on mask blur regions when using FLUX.2 Klein for inpainting, particularly visible when regenerating over the same region multiple times.
QA Instructions
Merge Plan
Standard merge, no special considerations needed.
Checklist
What's Newcopy (if doing a release after this PR)