sexual situations

physical violence

disturbing

male nudity

extremist

hanging

hate symbols

nazi party

revealing clothes

graphic female nudity

corpses

wide hips

oral invitation

exposed female nipple

female nudity

suggestive

undressed

male underwear

female swimwear

genitals

female underwear

thick thighs

breasts out

strapless leotard

vore

bestiality

breast out

one breast out

huge breasts

gigantic breasts

huge butt

covered nipples

hair over breasts

no panties

sitting on face

anal

dildo riding

downblouse

oral

porn

futanari

hentai

nude

lingerie

sexy

nsfw

partial nudity

white supremacy

adult toys

graphic male nudity

illustrated explicit nudity

nudity

self injury

convenient censoring

sexual activity

sexual intent

weapon violence

female swimwear or underwear

male swimwear or underwear

graphic violence or gore

peeing

emaciated bodies

blowjob

bukkake

cumshot

cumdrip

cum in pussy

cum on face

cum on hair

cum on body

cum on tongue

cum on hands

cum in mouth

cum on pussy

eat_cum

fellatio

implied fellatio

after fellatio

triple fellatio

autofellatio

pov fellatio

fucked silly

presenting ass

presenting pussy

spreading legs

spread legs

swimwear

TRPCError

For inpainting that leaves a face and changes the whole background and character, Alimama works way better. Alimama also works better for LoRas. Alimama is terrible at outpainting and Flux Fill is amazing. You should test both. My comfyUI OOM or crashes when switching from one to the other, so you might want to restart in those cases.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.<img src="https://image.civitai.com/xG1nkqKTMzGDvpLrqFT7WA/35407313-ebd1-424a-b1fe-efead4e2a374/width=525/35407313-ebd1-424a-b1fe-efead4e2a374.jpeg" />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 -the normal fill, like Auto1111- (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 degradationI added LoRa support and Daemon Detailer support (both are optional)

Sorry, there was a big mistake on previous v5.1! If you used the node to resize your image (for example, a big 2k image to 1024), the mask and the context mask would not be resized. Now it will resize the masks accordingly to the image size, resized or not.

v5.2

So I decided NOT to RESIZE by default the image to a divisible by 8 resolution because as pointed out by <a target="_blank" rel="ugc" href="https://www.reddit.com/r/StableDiffusion/comments/1gy87u4/comment/lzqqawm/">Jeffu here</a> 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.

v5.1

This is kind of a big important update.1- I decided to add "fill" (automatic1111 fill) to the outpainted area. It makes no sense to have it black or gray, specially because you might use a lower denoise.2- I added "Differential Diffusion" to any model chosen. It is supposed to help any inpainting model, not only Flux Fill. Thanks to @cenor for pointing it out.3- I Decided to change how the image is loaded to the workflow. It won't "allow" and will change any image that is not dividable by 8. Why? The ksampler/Vae Encoder would "fix" any image that is not dividable by 8 anyway, which in the end means that compositing would make it misalign/mismatched by some pixels. I don't like that, so it's better to fix the image in the beginning of the workflow. Keep in mind that this will probably change your original image resolution, but not by much, just the closest number divisible by 8. This is all automatic.4- So I had to fix outpatining calculation so it will output a final image that is dividable by 8.5- I added an option to resize the initial image if you want. Sometimes you want to inpaint an image that is of a HIGH resolution and prefer it resized to a more friendly resolution. (!!!) Keep in mind that if you want to inpaint only a part of a giant res image, you CAN. Just DO NOT resize and click on the "localized area inpaitning" on the Control-room. This will make use of the "inpainting crop and stitch nodes". 6- I added the option to not composite in the end. Keep in mind this is not proper and it's not advisable at all! You should ALWAYS composite at the risk of degrading your whole image if you don't. BUT sometimes you don't care and the image blends does better without it, so here it's the option. It is not in the control-room, you need to do it on the red group.7- Added labels and more notes to help understand the workflow

v5.0

Very few changes.1- People had trouble loading the Unet models with "checkpoint selector" so I went back to normal Unet Loader with "Load Diffusion Model" and getting the name with "Widget To String". It should work the same way. But "Widget To String" needs to have the node number correct there pointing to the "Load Diffusion Model"2- Finally removed the last LogicUtils node "text replacer" to a "was nodes" with the same function. So now people should not have any issues with missing nodes. Please let me know.Edit 4.11: Fill image was not connected to the wrkflow, sorry.

v4.11

I'm very glad to say that this can now OUTPAINT and inpaint at the same time if you want! Or just oupaint alone. Or just inpaint. =D

v4.01 With Outpainting

I cleaned up some necessary custom nodes. Mainly the Logic-utils that had a bunch installation problems with some people. No more animatedif or video nodes (some of their nodes were being used for simple tasks, but I replaced them.) Also, "fixed" the view. I lower all nodes to fit the default view. Some people were not seeing any nodes because of that.I hope that people will experience fewer issues now with the installation.

v3.12

Added "Flux Dev Fill" inpainting model support. If used, Alimama control-net won't be used (yes I've tried both, they don't work toguether). If normal Dev or GGUF is chosen, Flux Fill inpainting won't be used.

v3.01 flux fill

Small fixes. I messed up some details. Now I left the default example.png on the load image nodes and no LoRA on the LoRA stacker nodes, so no errors should happen.Tried to explain better what is the purpose of the second mask (the context mask) on the notes.Also, I forgot to explain that you can use keyboard shortcuts 1 or 2 to navigate to the control room or the comparison part of the workflow (you can customize this as you wish, is the bookmark node).

v2.2

Again another version. I fixed the negative conditioning that was connected wrong in one of the nodes.I added the denoise control to the CONTROL ROOM. I fixed the "very fainted aura mask". It should be controllable now, you can make it very fainted or very bright. This is different from just using a "grow" and blur mask node.

v2.15

I decided to ad Daemon Detailer as well. Sometimes it's better, but you'll have the option to use it or not. I changed the way the image saver retrieves the prompt to a simpler method, should work now for everyone.Added a guidance control as well. Some other small changes like you can DISABLE the aura mask if you want. Read the notes on the green group.

v2.0

I added LoRa support because why not. It's not necessary but if you want to inpaint a face, it makes totally sense to have a lora. It's very simple, but the metada saver is a little bit more complex and people don't seam to know hot to do it, so I thought that sharing a worklow with it is a good idea.

v1.6

Added Civitai Metadata saver to the image so it can be shared with metadata here

v1.5

v1.0

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

Type	Workflows
Stats	452
Reviews	Positive (32)
Published	Dec 3, 2024
Base Model	Flux.1 D
Hash	AutoV2 ADBF8F7C3F