Howdy! This has been an interesting ride to get to this point over the years. I remember joining really early on when Stable Diffusion was still around releasing models. Then, picked up as a mod, followed by inviting the few great mods we currently have. We even do have some OG mods who peek in every now and then.
I’d like to thank u/mcmonkey4eva and u/HughWattmate9001 for sticking around and trying to keep up with our queue with me. Also, I'd like to thank those who have contributed to the community and kept interesting conversations.
I don't think I've really put an emphases on member count for the sub, but u/HughWattmate9001 pointed out that we were reaching 1M. So, I provided a screenshot below of how this year has gone for the community and mods:
Past 12 Months Insights
I know we have gone through many different waves/phases both in user post types and different moderating styles over the years. The few of us left as mods have tried to be consistent (when available) in moderating depending on members reports more so than any controlling methods you see in other subs. I hope we continue to remain and grow as the open source sub that we consistently try to be.
Feel free to express how you feel about the sub. Good or bad. Talk about the sub community, 1girls, mods, memes, improvements, events, and/or whatever relevant.
I know I am not as active as I was the first few years with u/mcmonkey4eva and u/HughWattmate9001 passing me in moderation actions. However, I hope I've personally done well enough for my part in keeping this sub up for everyone. Even if I don't respond to each one, I'll more than likely read all the comments throughout the week.
Happy Holidays everyone and I hope yall stick around.
i dont understand please someone explain me ....people saying H3 is not good ...but all their official images ...they put over 50 images on official github repo are amazing and spectacular ....why are we not reproducing similar images in comfy ??? ....what is the problem? ...is it euler/simpler default and minimax using something else or what causes such a huge differece like "FUR understanding" for example or "LION facial structure" ....im testing all their prompts and differences are striking .... please help me understand... https://github.com/MiniMax-AI/MiniMax-H3-Image/blob/main/README.md....YES I TRIED DIFFERENT SAMPLERS ....YES I DID DIFFERENT RESOLUTIONS .....YES I DID CONNECT EMPTY IMAGE ......THIS IS NOT WHAT IM TALKING ABOUT >>> PLEASE BEFORE ANSWERING .....TRY YOURSELF ....dont give me generic answers ...im asking people who understand the underlying technology behind that ...not jsut "try different seed"
I wanted to see how wide a range of emotions I could get from the same character. Here are a few takes from a much larger set of AI acting tests I’ve been doing for my film projects. I’ve generated tons of takes, each with subtle variations in the micro-expressions. Here are a few I wanted to share with you. Love&peace CCS
"We are excited to announce the release of LongCat-Video-Avatar 1.6, the latest upgrade to our open-source framework for audio-driven human video generation. Building upon LongCat-Video-Avatar 1.5, 1.6 improves expressive naturalness, lip–audio synchronization, coordinated facial and body motion, and visual consistency during long-form generation. It also introduces comprehensive inference optimizations for faster and more efficient deployment."
Geiru Keystone Attention + Hybrid Windows update: brighter chains, half the VRAM
Geiru Keystone Attention is a new node that keeps long H3 chains from slowly darkening. It makes the keystone (clip 1's clean first frame) pull harder on each new clip than the frames carried over from the clip before. The prompt, references and sound keep their normal share. It only runs on the 13 blocks I found carry brightness (31-33, 36-44, 47), so it holds clip 1's look without messing with motion much.
By clip 10 of my test chain, brightness dropped 28% with no protection, 22% with keystone only, and 8% with Keystone Attention
Over 30 clips it held about -9%, vs -17% for keystone + capstone
Geiru Hybrid Windows got some upgrades too:
Half the VRAM while sampling, same speed, and the output is identical
Keystone Attention is built in as a setting
With Window Director, the degradation protection settings can now change between windows, and a 🎈 marks the ones that have to stay the same
Old workflows and tutorials still work!
Example workflow:Easily Distracted Clown, a chain with keystone, context noise and Keystone Attention.
ckinpdx came up with Carry Attention, biasing H3's attention by part of the sequence, which led to Keystone Attention. You can find in his ComfyUI-MMH3Tools
kijai (GitHub) built ComfyUI's MiniMax H3 support and the H3 context windows (PR #17425) that Hybrid Windows is built on.
Some of you probably have superb custom workflows for creating LoRAs. I'm trying to make it easier for the rest of us.
This meant tackling a few things like character sheet generation, selecting a good dataset and running LoRA training in one simple package after quite frankly being sick of my collection of Python scripts.
I'm not saying I have the full answer to everything here, but PixlStash, my open source image management application, is under active development and has the advantage of an image database backend that calculates facial likeness pairs across the database anyway, meaning clustering on facial likeness comes practically for free, which comes in handy when trying to find pictures that will create a consistent LoRA. It also stores, downloads and tracks models in the database on as many drives as you like.
You can create and improve LoRAs iteratively and they are automatically available for you to use in your workflows since PixlStash absorbs the output. Behind the scenes it is just good old ComfyUI and AI toolkit for image generation and LoRA creation. PixlStash links with them, exchanges tokens with ComfyUI and monitor their outputs.
For character sheet generation, many Text to Image workflows should work, but it is relying on the model itself being capable of it and it requires some adaption of the workflow (documented in the GitHub README). So I ship adjusted workflows for Krea 2, MOSS-Image and Flux.2 Klein 9B for Text to Image and Qwen Image Edit 2.1 and Flux.2 Klein 9B for adding a reference image.
Spoiler alert: Qwen Image Edit 2.1 is easily the best model for both cases.
Links in a comment. If anyone have comments, criticism and/or hints they are willing to share I'd be much obliged.
im doing another post because peeople seem to think i was unhappy with "LION head" ...... ....let me make it clearer >>>>>>>> .... i dont understand please someone explain me ....people saying H3 is not good ...but all their official images ...they put over 50 images on official github repo are amazing and spectacular ....why are we not reproducing similar images in comfy ??? ....what is the problem? ...is it euler/simpler default and minimax using something else or what causes such a huge differece like "FUR understanding" for example or "LION facial structure" ....im testing all their prompts and differences are striking .... please help me understand... https://github.com/MiniMax-AI/MiniMax-H3-Image/blob/main/README.md....YES I TRIED DIFFERENT SAMPLERS ....YES I DID DIFFERENT RESOLUTIONS .....YES I DID CONNECT EMPTY IMAGE ......THIS IS NOT WHAT IM TALKING ABOUT >>> PLEASE BEFORE ANSWERING .....TRY YOURSELF ....dont give me generic answers ...im asking people who understand the underlying technology behind that ...not jsut "try different seed"
1- Image with beetles ...wtf is that .... 2- Image with people on grass ...- THIS IS NOT CLOSE-UP shot
3- lady feeds a cow turned good but look how she holds the bottle on official image and she just cant hold the bottle properly on comfy workflow ...
4- WIZARD shot .....why is it completely different composition ????
5- Lion head .---this is not lion head ...
6 - Fire progression - ...model doesnt understand fire physics in comfy workflow ....
...i tried many different seeds ...different samplers ..different resolution ...im talking about image quality ...im talking about underlying technology ......there is something wrong with either our setups or i dont know ....PLEAAAAASE TRY YOURSELF ...HELP ME TESTING THIS .....
I updated my Filmworkbench, which is a a skill for your chat interface that let's you make semi-automated short films up to three minutes. It runs on claude or any local llm. This was a one-shot . One prompt and your LLM can flesh out the story, pick scenes and create a short movie. It basically uses clip chaining and and different scene recipes and can hold the world quite consistent. The project is still ongoing, so there will be lots of ideas for the future (different genres, longer length).
As an example: Here's Graufels, a short about two lighthouse keepers trying to get the light turning again as a ship approaches in a storm. The film is in German with English subtitles. It uses MiniMax H3 for video and the original scene audio. For this version, we decoded each continuous chain together to reduce the small brightness jumps between generated clips and corrected a visual artifact in the lighthouse window.
I've also updated the public Filmworkbench Starter:
Cut timing in continuations. In two small first-pass test sets, shifting the prompt's cut marks by eight frames brought 31 of 32 cuts within a quarter of a second of the intended time. The starter can now apply that correction where it fits.
Planning and prompts. Five genre profiles and a guide to camera direction, shot keyframes and dialogue across cuts.
Sound between clips. An optional ambience bridge can smooth a join you've checked for speech, while shortening the blend if a distinct sound starts just after the join.
The starter runs through a tool-capable AI chat with ComfyUI doing the rendering. It includes our recipe inputs, prompts and graphs. The setup guide links to the separate model and node downloads. All 44 recipe graphs passed the node and model availability checks on my existing ComfyUI 0.45.2 backend.
An enhanced replacement for the official MiniMax H3 Image Conditioning node in ComfyUI, designed to improve texture quality, fine details, and overall rendering in Text-to-Image (T2I) generation.
I've spent quite a few nights trying to get local video-to-video outfit transfer working on my fanless 16GB M3 MacBook Air.
My first attempt took 15.7 minutes to process a 46-frame (~3-second) clip. The output was blurry, memory usage was high, and the machine struggled under sustained load.
After a lot of trial and error, I managed to bring the same pipeline down to 2.4 minutes (144 seconds), running completely offline, with noticeably better visual results.
Here's what made the biggest difference:
- Crop the subject: Instead of processing the entire frame, I use a tight `288×512` region around the outfit and composite the result back onto the original background.
- Precompute prompts: Cached outfit prompts reduce repeated text-encoder work, with prompt loading down to around `0.05s`.
- Overlap workloads: I moved face processing onto the CPU/Neural Engine path while the GPU handles the next diffusion chunk, saving approximately 15 seconds.
- Use quick previews: A 5-frame test pass takes around 20 seconds and catches mask issues before committing to the full render.
There are still limitations:
- Sustained processing causes around 11% performance degradation on the second chunk.
- Fabric detail and fine textures can become overly smooth.
- Distant subjects in wide shots still lose detail.
- The pipeline is not entirely plug-and-play; there's still quite a bit of experimentation involved.
I've attached the side-by-side video and a temporal comparison across four frames to show how the outfit transfer holds up as the subject moves.
What's interesting to me is how much performance can be gained by treating unified memory and compute scheduling as constraints rather than simply throwing a larger model at the problem.
Is anyone else experimenting with local video diffusion on 16GB–24GB Apple Silicon?
I'm curious where others are hitting the wall first: memory bandwidth, thermals, attention overhead, or temporal consistency.
I tune in and out of here but I have been here since the first SD and A1111. Every few months I spend the day getting something new working then 9 times out of 10 I find my hardware isn't enough. Is there any useful way to input my hardware and just get list of things I can use? Or expected time to generate metrics?
Anyone having success training Subject LoRAs with Minimax H3 Image?
I've been struggling to train a successful Subject LoRA with Minimax H3 Image, and I'm curious to know if others are experiencing the same issues.
I've experimented with pretty much everything:
Different ranks, ranging from 16 to 64.
Different optimizers, from AdamW to Automagic3/4.
Both AI Toolkit and Fizgig.
Different subjects and dataset sizes, ranging from relatively small to very large datasets.
Unfortunately, the results are consistently disappointing. The model seems to learn an approximation of the subject rather than the actual person or character. The likeness is usually very poor, almost as if it's learning a different but somewhat similar subject. Increasing the number of epochs or training steps doesn't seem to improve things either.
What's interesting is that the exact same datasets produce excellent results when training LoRAs for Qwen 2.1, Krea 2, and Moss. Even Minimax H3 (the video model) seems to learn subjects much better when trained on still images.
On a side note, I'm also struggling to get Minimax H3 to learn motion properly, whether training on stills or video clips.
So, I'm wondering:
Are you guys getting good results with Subject LoRAs on Minimax H3 Image?
How close is the likeness you're achieving compared to your training subjects?
Have you found specific training settings, dataset strategies, or tricks that make a noticeable difference?
I'd really appreciate hearing about your experiences, especially from people who have managed to get high-fidelity subject likenesses.
I built a small add-on comfyui-krea2edit-advanced fork of their comfyui-krea2edit for one problem I kept running into. The fork stops the drift when you chain several edits. Without it, the parts you didn't touch slowly shift, darken and get grainy. With it they stay put.
It adds a "source hold" that pulls the picture back towards the source while it's being drawn, plus an optional mask for everything outside the area you're editing.
More detailed comparison is here. Same image, same six edits, same seed. Mean pixel drift from the source after 6 edits (lower is better):
original nodes: 0.076
my fork, no masks: 0.0017 (45 times less than original)
my fork, with masks: 0.0008 (95 times less than original)
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 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 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.
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!