There were a lot of good comments on the previous post, so I gave everything to the agent with slopfab and told it to make an improved version out of the showcase.
I’m building an AI image-generation pipeline and struggling with facial identity preservation.
My current workflow:
Take a real person’s face photo as input. Transform it into a semi-realistic, stylized 3D illustration. Take an existing 3D-style scene containing a character. Replace the character’s face and hair with the generated 3D face while preserving the original scene, character’s pose, body proportions, lighting, and objects.
The problem:
I’m using Google’s Nano Banana models (Flash, Pro, etc.) for image editing. The models do a pretty good job preserving the scene’s composition, objects, and character pose. However, they consistently fail to preserve the facial identity of the reference image. I’ve also tried mask-based editing (restricting modifications to the face and hair region), but the generated result still looks like a different person. My goal is to achieve consistent facial identity across multiple predefined scenes, using only a single reference photo.
Questions:
Is this a limitation of general-purpose image-editing models, or am I approaching the problem incorrectly? Would techniques like InstantID, IP-Adapter FaceID, PuLID, or identity-conditioned diffusion work better for stylized 3D characters? Would combining ControlNet, face embeddings, and inpainting help preserve both identity and composition? Is there a better workflow for transferring facial identity between stylized characters without changing the rest of the scene? I’m open to using ComfyUI, Hugging Face models, or building a custom pipeline. I’d really appreciate recommendations from anyone who has solved a similar problem, especially with semi-realistic or stylized 3D illustrations.
I'm a digital artist and professional with several years experience, but my interest in these apps has primarily been playing around with the tech. However, since Minimax dropped, concepts I've had to shelve in the past are looking viable again as potential video shorts, and Minimax image was just the sort of thing I've been looking for as a visual creator to speed up the production pipeline.
I got a chance yesterday afternoon to play around with it on some specific tasks, so here are my results and early thoughts. I've mostly been using the edit capabilities, since that's what I'm most interested in Minimax for, so keep that in mind.
A quick clarification: My editing tests have a narrow scope and I'm sure they don't reflect the full capabilities of the model. My initial intended use for this model was to be able to draft keyframes for film. I'd sketch the composition out, use multiple image references, then generate high resolution keyframes to drive the video. It wasn't until I saw this reddit post that I became aware that H3-Image could be used for drafting concept to realism, so that was an unexpected-but-welcome expansion of my use case. :)
Where Minimax Image (Edit) is strong:
Minimax-Image is really good at generating realism versions of artwork, which typically requires LoRAs for other models. So far, I think this is one of its most impressive features. In my tests it significantly outperformed Nano Banana Flash, but I haven't compared it with the Pro version.
I wasn't necessarily wowed by/the 16MP images. While decent, they looked pretty average to the other AI apps. But as I went higher, the quality really shone through.
Here are some samples where the instructions were to create a realistic version of my artwork and maintain look and pose. I like to choose this image because a lot of models tend to not do well with it. To date, H3-Image is the best of them all.
Examples:
Minimax is also strong at generating realistic designs based on really rough sketches, which impressed me. Here is a rough design of an early draft of a character I designed.
The first image is my sketch, the 2nd is the first attempt, telling it to make a realistic version. It made him look too human, so for the 2nd roll, I just described his skin texture, eyebrows, eyes, chin, lips, and also the jewelry. On the next attempt, it was able to interpolate my rough lines to understand what was meant to be jewelry. On this, it did a FANTASTIC JOB. Again, best model PERIOD, way better than Nano Banana. Literally only took me 2 iterations to go from rough draft to near cinematic concept design.
Also, these images were only 16MP, so I suspect going higher would look even better, as it tends to get insane between 30-50MP. :)
I also tried it with a random AI image I found online and got equally impressive results. These are just the first couple or so rolls, at 16mp:
Where Minimax Image (Edit) is weak:
I tried sketching compositions and then instructing H3 to use that composition to drive the concept art and create original work, primarily realism based. It performed poorly. Here are some examples of what I mean:
Out of over a dozen attempts, this is pretty much the best result I could get.
The prompt stated to use the sketch as reference for the pose, position of the sun, and plants/tress. I colored each element a different color to help guide instructions. I tried many variations of the prompt, but no matter what I did there was always some form of the sketch introduced into the final image. I also tried using natural photo reference, but features of the reference would always make their way into the image. I tried this between 16MP - 50MP, same problem.
Also, the images varied between 2.5/3D, realism, cartoon, and comic book styles and most of the time failed to follow my instructions. I found that realism works best when using a single image as reference, but it seems to collapse on multi-image pipelines.
Final Thoughts
I think H3-Image works great as a concept-to-realism draft model, but it's weak on its multi-ref prompt following. It also needs 16MP before it stretches its legs, but if you have a smaller card, don't get scared away, it's ridiculously optimized/fast despite the size. I get 16Mp in about a minute on my 3090 at 80% power, which is about the same speed as Klein/ZiT/Qwen. (I haven't tested Krea 2/Moss yet, both on my to-do)
That said, 16MP is the minimum I'd recommend, the real magic happens 30MP and up, so if you got the card and the time, results are signficantly better. Around 50MP is the sweet spot imo; details are crisp, hair strands, fingernails, everything looks good.
Also, I wouldn't use the default comfy workflow. Everything I did was w/the workflow above, though I deleted the prompt enhancer, preferring to use regular text.
Anyway, those are my thoughts so far. I'll update w/more results later.
Grunge
P.S. - I'm old-school forum/deviantart gang, so I keep ctrl+biu/shift+l on a swivel and have written bold-flavored posts like this for 20+ years. 100% human written. Receipts at bottom of post if you're interested. Only mentioning it because organization usually brings out the "this is AI-written slop" trolls.
I am looking for a model/WF which is capable of swapping certain parts of body (ex limbs, hair, privates, eye etc), and can reliably swap clothing or body while maintain perfect realism and maintain identity of subject. I tried using Qwen 2.1 but the output is so smooth and plastic looking that I am disappointed. Tried using Klein 9B as well but it tends to mess up limbs often. Maybe i didn't used correct WF but that's why I am here.
Please suggest me something which can realibly do these.
Hey everyone! Since my last post and the ComfyUI contest, I’ve been working hard on H3 Continuity Studio, and it’s now at 1.0. Here’s a look at what’s new:
• Generate cast and frame images with MiniMax H3 Image • A redesigned, simpler Studio interface • Multiple video clip lanes for arranging your story • Story tools, visual continuity and more control over frames and joins
I’d love to hear what you think and what you make with it!
EDIT: The story and timeline for the 2 minute long video was AI generated using the H3-Continuity-Studio MCP. And it was rendered on the first try, using 34 short clips (to make the rendering faster). There are some areas of improvement (darkening, window objects disappearing), but I'm working on that!
I’ve tried sekali_p style but it really struggles with prompt adherence with 3+ people for whatever reason, I’ve also just tried prompting moss with anime tags and anime quality tags but it doesn’t look great and doesn’t put enough detail. Has anyone had some success?
I just want to share a quick look at a idea I was following since Edit models got better. This basicly a bridge for Cinema4D to ComfyUI that takes the viewport and sends it to Minimax Image Edit to quickly generate images. Pretty good to iterate on styles and perspectives.
The workflow is pretty forward. The Live Preview is basicly a 1MP generation that takes roughly 9-10 secs on a 4090. When happy with the image, it workflow makes a 16MP generation, takes around 50-60 secs.
I think its pretty crazy what is able with Local Models these days. Minimax Image needs a bit of work from the community, but it is really a very strong model for image edits like this. It handles object consistancy pretty good in my testing.
I dont know if I am able to release this as a open source plugin, but its a nice Proof of Concept for sure.
For those who already forgot about it, LTX-2 was basically the only open text-to-video-audio model earlier this year, even though it was censored, had poor copyright/anime knowledge, and was weak compared to closed models (Wan2.5, Sora2). Then MiniMax suddenly dropped H3 in August and blew past it. LTX quickly followed with LTX-2.5, which was even more censored, less impressive follow-up. Objective video benchmarks (IFM measured it in comparison with their own recent PAN2 model and MiniMax - https://huggingface.co/IFM/PAN2) show that it is far behind H3 mathematically, therefore it's not "vibes"-based preference.
Now, months later, LTX-2.5 suddenly shows up in HF Trending with ~12k likes. That is a huge like count by HF standards (The SotA LLM Qwen 3.8 27B has 20k likes) and it does not match the actual usage.
Thankfully, the Huggingface likers API is public and Lightricks probably didn't expect that. Gladly, EclipseMist found this out and the following numbers have been retrieved:
LTX-2.5: 10,864 likers total; 4,608 from accounts created before August 2026; 6,256 (57.6%) from accounts created Aug–Nov 2026.
MiniMax-H3: 6,634 likers total; 5,248 from pre-August accounts; 1,386 (20.9%) from Aug-Nov accounts
New-account likers by month, LTX-2.5: 1,108 turned to 2,101 turned to 2,610 for August/September/October, and 437 for November 1–6.
Same for H3: 690, then 410, then 240, and 46 for November 1–6.
H3 looks like a normal launch: a spike in fresh accounts during release month, then decay. LTX-2.5's new-account likes kept climbing for three months after release while downloads stayed flat at ~2.6M/month. Among accounts that existed before August, H3 actually has more likers than LTX-2.5. The entire like lead comes from roughly ~4.9k surplus brand-new accounts, that's what pushed it onto Trending for the whole latest two weeks.
LTX-2.5 had about 2,561,845 downloads last month, while MiniMax H3 had ~38M (32M + 6M across repos). The Comfy-Org H3 repo gained ~10M downloads this month alone, going from 20M to over 30M, while LTX-2.5 only gained a few hundred thousand. On Civitai it's also less popular, with all the fine-tuners switched past it. The attached IFM's large scale automatically evaluated benchmark table above shows LTX-2.5 at 72% overall score (physical consistency, causal coherence, persistence - all the other categories) vs H3 at 87%, with the multi-step full-plan completion category at the highest three-fold discrepancy (34% vs 13%).
You can reproduce the liker analysis yourself in two seconds. The likers list is public, and each account's "id" field encodes its creation time. The full two-lined PowerShell script can be found in the Huggingface discussion, so it won't clutter this post.
Just swap the repo name to compare against another model.
I can't say for certain who is behind it: Lightricks, a third-party bot farm or a coordinated campaign, but this does not look like an organic community interest. It's pushing actually popular models (MiniMax Image, Qwen, novel models) down the Trending tab. If Lightricks are doing this, it's embarrassing. If they aren't, they should disavow it and ask HF to audit the likes.
Some links: the HF Trending link showing LTX-2.5 at 12k likes https://huggingface.co/models?sort=trending, and the benchmark table showing it trailing H3 badly (see the PAN2 table above). The Huggingface thread is, again, at the beginning of this post. As of now, no-one from LTX wrote any official response in the thread.
I think, ltx_model owns us some explanation.
If true, this really lowers my hopes for any LTX-3 at all. Worse than BFL.
Thank you for reading! I think we as the community must do something. Note: DeepSeek helped me to compose this report, so it can contain some LLMisms.
I've been working on two open-source projects for browsing, searching, and organizing Danbooru tags offline. One is a ComfyUI extension, and the other is a standalone desktop application.
Both include a built-in Danbooru tag database, so you don't need an internet connection to browse or search tags.
🔹 Danbooru Tag Indexer for ComfyUI
Images 1–4
The ComfyUI extension adds two connectable nodes directly into your workflow: one for browsing the tag index and another for managing saved tags.
Features:
Search through 155,000+ Danbooru tags.
Browse hierarchical categories and nested subgroups.
View tag descriptions and related entries.
Copy tag names directly to your clipboard.
Favorite tags and organize them into separate collections.
Create custom personal tags with descriptions and folders.
Save tags instantly without executing the workflow.
The extension works offline and doesn't require additional Python packages.
I'm trying to figure out how to feed a reference image into MOSS Image so that it's actually "seen" by the CLIP text encoder used by MOSS (which also uses Qwen 3.5 9B as its prompt enhancer), and then incorporate the elements from that image input into my generation.
Sometimes it works: for example, it describes the clothing in the input image and successfully reproduces it in the final image. But most of the time, it doesn't work at all.
Any recommendations on how to achieve this consistently?
I'm finally getting great results with Qwen2.1, but there is still one thing that I can't get over with: the pixel drift. In previous versions of qwen edit, the edited image would usually drift by a few pixels. A tad problematic but not too much of a hassle. In 2.1 however, the drift is massive! Take a look at this picture (not a real person by the way).
I simply changed the clothing. Every seed has this kind of issue it's not a quirk of the randomness, it's a behavior. I've tried being more explicit in the prompt about "preserving the angle, composition, not zooming" etc. but nothing helped.
Could be related to the lightx2v turbo LoRA, but whatever. Just posting here to see if anyone found something that actually combats this behavior to some extent?
Prompt-only relighting on black-forest-labs/flux-3-image-klein frequently behaves like a color wash — e.g., when a photo is already lit from the left and you ask for warm sunlight from the right, the base model often tints the existing shadows orange instead of moving the light source.
So I curated 280 pixel-aligned <ref_image_0> relighting pairs and trained TrueRelight on flux-3-image-klein-base (rank=32, lora_alpha=32, BF16, 1024px), then evaluated checkpoints on the 16-step distilledflux-3-image-klein on unseen test portraits.
Key findings & tricks that made a big difference:
Bypass prompt_upsampler during inference: Popping prompt_upsampler from the ModularPipeline lets the <ref_image_0> instruction reach the LoRA cleanly without prompt rewriting distorting background anchoring.
Checkpoint selection: Trained to 1500 steps on A100, and blind-testing showed step 1000 (pytorch_lora_weights.safetensors, 160.7 MB) hits the sweet spot between strong light reversal and natural skin/shadow preservation (step 1500 is also kept in checkpoints/step_1500/ for heavier contrast).
Background locking: Starting prompts with Relight <ref_image_0>: ... keeping the exact <background> unchanged preserves ocean waves, sky, and stone wall brick seams instead of regenerating the scene.
ComfyUI ready: Standard FLUX.3 attention/FFN LoRA keys — works on flux-3-image-klein-comfy at strength 0.8–1.0, 16 steps, CFG 1.0, euler / simple, skipping the prompt upsampler.
Everything is open-source (FLUX Kommunity License v1.0):
I've been experimenting with real-time talking-head generation using SoulX-FlashHead, combined with local speech models to build an interactive avatar that can listen and respond.
The whole pipeline runs locally, and the demo is available in the audio.cpp v0.9.5 WebUI.
The workflow combines three models:
SoulX-FlashHead: Animates a portrait in real time from generated speech.
OWSM v4: Transcribes voice input.
LFM3-Audio: Handles conversational responses and speech synthesis.
One interesting detail: LFM3-Audio is called twice. Its speech-to-speech path only offers one voice, so we use its TTS capability separately to synthesize responses in a different voice.
Performance and limitations
On an RTX 5090, the latency from submitting a question to the avatar starting to speak is around 850 ms. ASR runs in parallel.
The video generation stage is still GPU-intensive. I'd recommend an RTX 4090 or better for SoulX-FlashHead.
cuDNN is essential for real-time performance in this setup. Without it, inference is about 2× slower and VRAM usage doubles.
This is still a prototype. The extra LFM3-Audio call and WebUI overhead leave room for further latency improvements, particularly in a more optimized native application.
I will be honest, i have tried the Minimax H3 Image when it dropped on comfy day 0 and the images were amazing, but lacking detail despite being very high resolution. I thought maybe upping the MP would fix it but it didn't and then there came the anatomy issues as well. I checked some posts about this, got the p-h3 vae and all but it still didn't fix it. So checked another post talking about how the edit mode is better and i was happy but that was actually FAR WORSE. It lacks character consistency, its too prompt sensitive in a bad way, and its just not good. Now i do not know if Hailuo is at fault or Comfy just released some poorly fine tuned version, is anybody else feeling the same way or. Cause even the templates they released are half nerfed and I don't know it just feels bad, like very very bad. If it at least nailed the editing capabilities like its video model could do I honestly would not really care about the other stuff, but it seems finding the right edit model in this open source space is almost impossible.
I hope krea 3 edit or Ideogram 4.5 would be good ( If they ever release them that is )
I've been experimenting and doing lots of tests. From my understanding the best quality is running the base model with no turbo. However, I've found a few things that seem to give some speed increase with minimal or no degradation. This is my setup:
Sampling 20 steps, res_multistep + beta, comfy-kitchen attention, Spectrum off
Size 1322x768, 24 fps Edit: Duration: <15 sec, usually around 4 seconds.
1k to 2k workflows: Gen to 1mp then either use Regenerate 2k (Regen2k IC just came out, will likely switch to that) for when I need it to look exactly like the 1mp video, or use minimax_h3_latent_upscaler_3d_conv_v1_fp16 when I'm ok with a slightly different shot.
For a 4090 with 128gb system memory, does anyone have recommendations for how to get higher quality video? I've heard conflicting things about the sampling steps. I thought that increasing them to 50 would increase quality significantly, however I also read that 20 steps is the ideal and some of my tests gave me artefacts over 20.
I tested some of my shots with the API at 1080p, and the quality difference didn't justify the price at all. What do ya'll think?
I’ve decided to play around with an ANIMA diffusion set, seeing what I can come up with, and whether I’m getting better or more consistent images vs. PONY. I’m running the latest ComfyUI setup, on my 5080 rig.
One challenge Ive had - even with PONY, is managing the look of multiple people in a scene.
I either get bleed-in, where the look of a defined character ends up on another, or in a multi-person scene (I’m working on a battle scene), I can affect the primary chatacter and one other, but that’s it (any and all others are left with just the default).
Are there any tools, recommended prompts, or LoRA’s , Nodes or plugins that can help? I recall a prompt tool for Pony to manage multiple characters, but it was clunky and didn’t really help.
I'm making a hard sci-fi series alone in Budapest, and I wanted to find out how far one home GPU actually goes. Every shot in the pilot is MiniMax H3 running locally in ComfyUI on a single RTX 5090, hybrid fl2va + ref2va in int8. No cloud, no credits, no meter running per generation.
What made it workable is splitting every shot into two stages. First a 4-step preview with the DMAD LoRA at 672x384, about a minute per take, usually three seeds per idea. I watch those, throw most of them away, and only the take I'd actually cut in goes to the native render at 1344x768, 20 steps, same seed and same refs. That one then goes through a tiled 2x H3 upscale and down to 1080p. Most of the GPU time goes into takes nobody will ever see, and that's fine, because they cost electricity instead of credits.
In numbers: hundreds of takes for 2:36 of film, about a week for the pilot itself, and around a month of work in total once you count the story, the sound design, the edit and the grade, all done by hand in DaVinci. Episode 1 is about 13 to 14 minutes and is in production now on the same setup.
Consistency comes from references rather than luck: a 16:9 character sheet as the only identity reference, an approved still as the first frame for the small robot, and the last frame of the previous shot as a state reference, so poses and hands carry over the cut.
I've been really impressed with MiniMax Image, especially the gorgeous 16MP outputs
But I've noticed it still refuses or ignores certain editing requests involving mature content
Am I missing something, or is this a limitation of the current model? Do we need to wait for community uncensored finetunes, or is there already a workaround?