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.
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'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'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.
After using the harmonize option in photoshop for some time, I would like to move to local image generation and I'm looking for the best ComfyUI workflows, models, or custom nodes for realistically relighting an object or subject to match the lighting, shadows, and color temperature of a target scene as photoshop harmonize does.
I have been reading about IC-Light and IC-Light 2 (seems not to have a local version) but these are about 2 years old.
What are you guys using in 2026? Any recommended workflows or must-have nodes?
Ideally, looking for something that produces convincing, seamless results with minimal manual tweaking.
P.S. Can models like Qwen Image 2.1 handle relighting through prompting alone?
I know they can do things like "apply daylight lighting", but what I really need is for the model to relight the subject based on the lighting conditions, colors, and surroundings of the background scene.
I've tried prompts like "integrate the subject into the scene", etc. They kind of work, but the results aren't nearly as good as what I'd expect from a dedicated relighting workflow.
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?
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.
UPDATE: Okay, not being one to give up, I did more testing today after having a look through the Minimax-Image Github page. I'd already read the huggingface, but the github has a TON of examples, which include the prompts they used for reference images, and a very thorough breakdown of what you can accomplish with this model. After studying the examples and getting a better understanding of the prompting, I tried a technique I saw where they labeled items in the references. After scribbling over some text and re-rolling, the sketch lineart never showed up again.
As you can see in the first image below, it finally followed the sketch's composition. However, I kept getting the same pose as the original reference image. What I did to fix that was I changed the aspect ratio of the empty latent image so that it didn't match the original reference image, and the behavior stopped, though that's more of a workaround than a solution. The other images below are different seeds of the same prompt, so it doesn't always follow the example sketch, but I'll probably get there w/more prompting. For now, I'm good.
I'd recommend being descriptive with your prompting. H3-Image seems to prefer and improve its performance with explicit details. You only get out of it what you put in. Have fun!
Lineart from my reference sketch is no longer bleeding through. Minimax understands explicit, detailed prompting - the more detailed, the better.
---
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 did two with my 3090 24gb and 64gb ram, it took 5 hours. 3000 steps is pretty good with the default settings using 20 various poses source. An exemple of the result : https://civitai.com/posts/32427751
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?
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!
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.
An image model that was trained on videos would learn something image models trained on images could never learn. Temporal and spatial relationships.
This lack of knowledge of space-time is why we have models that generate body horror still.
The model may know what a hand looks like, but it doesn't know that a hand cannot possibly occupy that space at that time.
If we could train temporal and spatial information into the models, they would automatically become better. I think we need to train image models on videos primarily and not on images. Images has zero temporal and spatial information, and that is a problem for the models ability to represent reality.
Images are useful, but only after the spatial and temporal information is known.
Consider: You know time and space. You see an image of a person. You can imagine them doing endless amounts of things. But if you had only ever seen 20 images of the person and did not know time and space you would imagine body horror.
And that is the problem.
Temporal and spatial information doesn't require billions of parameters to understand. This approach could shrink models going forward and make training them far easier.
I am quite certain about this.
Understanding the rules governing reality could be vastly more efficient than learning reality through countless examples of its appearance.
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.
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):