Inpaint destroys the quality of the original image.

[Aper-TON]

Expected Behavior

When I gradually inpaint the image, changing one detail after another, the quality of the details not affected by the mask does not change.

Actual Behavior

Step-by-step deep image inpaint destroys the quality of the original image.

Steps to Reproduce

1. Upload any photo in acceptable quality.
2. Mask a small part of the image and regenerate the contents of the mask. (Inpaint | Flux Fill in)
3. Replace the original image with the result of your generation.
4. Go back to step 2 and run 5-7 such cycles.
5. The parts of the image that were never affected by the mask have been destroyed. (Contains a huge amount of noise and distortions)

Other

Please fix this as it is preventing me from working properly.
I think here, a person has managed to deal with exactly the same problem:
ahrm/UnstableFusion#23

[ltdrdata]

Unlike how it may seem at first glance, the VAE encoding/decoding process is inherently lossy. Regardless of whether a mask is used, converting a pixel image to a latent representation for i2i processing inevitably results in some loss.

Therefore, nodes like Detailer perform partial inpainting by re-synthesizing only the masked area on the pixel image.

[Aper-TON]

Unlike how it may seem at first glance, the VAE encoding/decoding process is inherently lossy. Regardless of whether a mask is used, converting a pixel image to a latent representation for i2i processing inevitably results in some loss.

Therefore, nodes like Detailer perform partial inpainting by re-synthesizing only the masked area on the pixel image.

I wrote my own node that combine two images together - the new generated image below, the original image with the alpha channel masked above. This solves the quality loss problem, but is a crutch.
I don't need help, I'd just like you to consider fixing this natively, at the ComfyUI base.
If you don't consider it a bug, then ok, you can do nothing.

[ltdrdata]

If the image degradation situation you are mentioning is due to multiple VAE Decode/Encode processes, as mentioned above, then it is not a bug.