Proper Flux Control-Net inpainting and/or outpainting with batch size - ComfyUI (Alimama) or Flux Fill

v5.1
diogod
10 months ago

I try my best to avoid hiding the workflow flow, while balancing keeping it clean and user-friendly.

It does use a lot of custom nodes to make life easier and workflow cleaner. Use manager to install the missing ones.

This is a proper inpainting with alimama control-net + Flux Fill support on V3.

Supports loading of an external mask (need to match the image size) or doing the inpainting within the right-click "Open MaskEditor" on the image itself.

Supports FILL (use FastBypasser - black node)

Supports area inpaiting x full image inpaiting (use FastBypasser - black node)

Supports variable denoise (Change denoise on the CONTROL ROOM)

Supports Negative (use FastBypasser - black node)

Proper composite so no VAE degradation

I added LoRa support and Daemon Detailer support (both are optional)

Read more...
Download (396 Bytes) Download available on desktop only

Popularity

890 ~10

Info

Base model: Flux.1 D

Version v5.1: 1 File

To download these files, please visit this page from a desktop computer.

About this version: v5.1

So I decided to NOT to RESIZE by default the image to a divisible by 8 resolution because as pointed out by Jeffu here resizing brings quality loss as well. So a solution I came up with is to crop the sides of the image to a divisible by 8 and then, after inpainting, composite it back to restore those pixels so you get in the end the same image resolution you started with (of course, that is if you did not turn the resize node option).

This is not going to be the case for outpainting since outpainting will always result in a bigger image and the resolution will always be deviable by 8. I did not change that.

This final/second composite has a problem that if you inpaint the whole image, or the right side of the image, it will restore those cropped original pixels back to the right side or bottom side. That might look weird. Because of that, you can bypass the final composite if you want. In that case, you will end up with an image that is divisible by 8 (this is better anyway, but it's not the default)

Finally, another note, if anyone is reading. Flux does not like some resolutions, so a divisible by 32 or 64 should work better. Some images get a weird black bar on the corners that remain there no matter what seed you use. That is because of the uncommon resolution. But since it's not mandatory, I decided to stick with 8. But you can reflect on that when inpainting and outpainitng.

27 Versions

😥 There are no Proper Flux Control-Net inpainting and/or outpainting with batch size - ComfyUI (Alimama) or Flux Fill v5.1 prompts yet!

Go ahead and upload yours!

No results

Your query returned no results – please try removing some filters or trying a different term.