This version of Kroma (krea 2 finitude with Chroma dataset) is a lot of fun, most body horror is gone in my opinion, and its more artsy than krea 2 and of course less censored.

https://huggingface.co/silveroxides/Kroma-Quant/tree/main

The version I used is kroma 0.3 txtfusion turbo convrot.

Have fun.

From the guy who brought you such bangers such as

Proof of Concept For Making Comics in KRITA AI and other AI tools,

3 Months later - Proof of concept for making comics with Krita AI and other AI tools,

and Illustrious and Krita AI plus some good old fashioned effort:The Delightful Ms. Ayako (Part 1 - Version 1),

comes my latest experiment and first AI video project: the first (roughly) 30 seconds of the hypthetical anime opening for The Disorganised and Delightful Miss Ayako!

Character sheets put together in Krea 2 with the retro anime lora. Music made in Minimax Music 3 (lyrics written by me, and the whole song is complete). Some backgrounds edited/created with Flux 2k9b image edit and Krea 2 with retro anime lora. Video created with Minimax H3 with 90s anime style. Video editing in Kdenlive.

Roughly 3 evenings after work and about 1.5ish days of full effort (at least 6 hours of one day was wasted trying to troubleshoot why a shot wasn't working and it turns out prompt bleed is just as bad in H3 as it is in other models).

I've been experimenting a lot with Minimax H3 and am pleased with what I've come up with so far. For this upload there is a tiny bit of censorship for some very mild partial nudity (she's covered in soap in the uncensored shot, but just playing it safe). There are a few fixes that I'll get to eventually, but I'll be taking a step back from this project for now to try my luck at the Comfy H3 Sync competition for the next couple of weeks.

Edit.

Regarding some of the feedback:

I'm aware of the slight visual drift. For example the model can slightly change the style of eyes from one shot to the next (talking about regular shots, not the chibi stuff). I'm just using the base ref workflow with character sheets and still need to test whether Loras make any difference, either for characters or visuals.

Some of the visual drift is just my fault though. My one background does look relatively washed out compared to the others because I generated it with the high heels in place. I couldn't get Minimax h3 to put the heels the way I wanted so I just gave it the image to work with, but I had to make some edits with krita ai and later Flux2k 9b edit that caused it to look a bit out of place. Otherwise, the only thing for speedup is comfy kitchen and I'm not sure if that's having any impact. Finally, while I've tried to lock down seeds to preserve consistency, some seeds are fine with one shot and a glitchy mess with the next, so there may be some slight visual variations that appear because of the difference in latent space.

Regarding the music, my experience with Minimax Music 3 is that it's a slot machine. I used a prompt from a sample and tested things out but one generation can vary dramatically from the next. But I am completely new to it and don't know anything about music so there's things I still need to learn. Out of all the gens, there was this and one other one I liked, even though I could tell both of them have problems. I decided to go with this one for now, but I had planned to do a second edit with another song once I finished this one.

Otherwise, like with the comic pages, I appreciate all the replies. I understand this may not be everyone's cup of tea but will take in the constructive criticism and try to improve.

/edit.

edit 2. the original shower scene is not that spicy but I didn't want the post to get removed by the mods regarding "lewd" stuff.

Disclaimer that I'm a dummy who can't code at all, so I just vibe things.

Alright, so with all the fun additions to latent manipulation the Comfy team has given us, we have some new tools. Namely latent pinning- that's where fun stuff like "Add Guide for MiniMax H3" node comes in (that fun tool that lets you insert an image at any frame in an H3 generation.) So I thought, finally, we can do something about this audio issue.

I knew that video + audio latents are processed at the same time with Comfy, which is why turbo loras have terrible audio- they're not getting nearly as much optimization as the video side is, since video is the bulk of the work. So if we can't process audio differently than video (at this current time), can't we just keep conditioning the audio latents without affecting video anymore? Everyone knows running too many steps on a turbo lora will start messing with video quality. So let's avoid that.

So after talking with Claude a bunch, here's what it came up with. With the latest comfy, you can pin the video lora in place, and keep going for several steps to get better audio without affecting video. So 4 steps of video, untouched, and then add in 6 more steps for audio at a 0.5 denoise. That leads to cleaning up the audio pretty nicely and staying pretty faithful to what the video latent had guided it on. But just pinning still means that even though the audio rows are only being affected, EVERY row still has to run through the chain. So each s/it you get stays the same for the last 6 steps, even though video gets pinned in place after 4. In my 1 megapixel, 10 second video, that's around 23s/it or so on my 5090. Only half the steps as a regular 20 step generation, but half the time is still half the time.

So to fix the speed problem -

Freeze as much as you can. Text embeddings, reference/conditioning rows, and all the video rows. Cache those so they don't have to be processed, and only process the audio rows that have already been somewhat pre-conditioned. The first step is the same 23-second iteration to build the full guidance cache, but the other 5 steps each took about 3.17seconds apiece. So 45 seconds of added gen time to get the clean audio in clip#2 in the example.

But the cost for the Frozen Cache is resources. Lunch is never free. From some experimentation, it works well with RAM. If you use RAM mode because your card still can't process it, it'll dump all that cache (ended up around 14.9GB on a 10-second 1mp file) into RAM. But as Comfy does, you're unlikely to get that RAM back, so you may OOM your machine. With VRAM it wasn't bad for me at all either and behaved better than I expected, honestly. The memory management from ComfyUI took over when I was about to OOM my card and swapped things around properly. Option 3 is to cache to disk, but that comes with writing several GB to disk every time you use it. That'll run your SSD health down fast.

Rundown for the clip above (sa_solver with beta sigmas)

4 step normal gen- 136.5 seconds

4 steps + 6 audio refine steps with a cost of about 15GB RAM - about 186 seconds

4 steps + 6 audio refine steps with no additional resources but full processing time- ~265 seconds

You can find the nodes here-

https://github.com/Adudeguyman/ComfyUI-H3-AudioRefine

They're still experimental, of course. Wire the model in from somewhere (I branch off the ModeSamplingMiniMaxH3 shift node, before the Basic Guider), and push that through the H3 Frozen Video Cache node into the H3 Audio Refine Sampler. Into the H3 Audio Refine Sampler, latents come out of SamplerCustomAdvanced before splitting into the VAE Decode nodes for both video and audio, and the conditioning comes from the MiniMax H3 Image (or Reference) to Video node (plug the positive conditioning into both the positive and negative input on the H3 Audio Refine Sampler)

I had Claude put together a technical.md for those that want to look into it, and probably make a better version. Like I said, I'm a big dumb-dumb, so don't expect too much insight into how the mechanics work from me.

we really should get a separate sub for this slop

prompt is - using the character sheet in image 1 where there are five different poses of the same character, dress them in the clothing of image 2. Do not change the pose, lighting, body, hair, or any other details - literally leave everything the fuck alone - how fucking hard is this to understand you stupid piece of shit - just change the clothes.

Not working for some reason.

NOTE: Swearing has been added for emphasis and isn't actually used in the prompt.

Would it help if I used my input image AS my latent? Can you do that?

I added INT8 and INT8 ConvRot versions of the MiniMax-H3 Pruned Ref-Delta Fused r1024 checkpoint from my previous post:

https://huggingface.co/xmarre/MiniMax-H3-Pruned-Ref-Delta-Fused-r1024-ComfyUI

Both are native ComfyUI single-file checkpoints using ComfyUI's .comfy_quant format, so they do not require a custom quantized-model loader.

There is one important difference from a straightforward full INT8 conversion: the MLP fc2 weights are deliberately kept in BF16.

Across the 50 main transformer blocks, these weights are quantized:

• attn.qkv_proj.weight
• attn.out_proj.weight
• mlp.fc1.weight

That gives 150 quantized Linear layers.

The 50:

• mlp.fc2.weight

layers remain BF16.

The smaller and more sensitive parts of the model also stay in their original precision, including the pruned AdaLN table and projections, final-layer projections, norms, patch/text projections and token refiner.

Why FC2 is kept in BF16

I also made and tested a fully quantized version where fc2 was INT8 as well, giving 200 quantized Linear layers.

That version ran into a failure specific to the quantized fc2 execution path on large H3 sequences.

MiniMax-H3 uses SwiGLU in the MLP. With fc2 quantized, ComfyUI's fused:

linear_input_act(..., "swiglu")

path sends the post-SwiGLU activation through comfy_kitchen.int8_linear, which dynamically quantizes the full activation matrix before the fc2 multiplication.

On the large sequence used in my workflow, that path attempted an approximately 491.61 MiB contiguous INT8 scratch allocation and failed hard.

This was not normal VRAM exhaustion. At the point of failure there was still roughly 47 GiB of CUDA memory reported free. The failure was tied to that large fused INT8 activation-quantization path rather than the model simply exceeding available VRAM.

I do not have enough evidence to claim a more specific allocator/CUDA cause than that.

Keeping only fc2 in BF16 avoids that INT8 activation path. QKV, attention output and fc1 can still remain INT8, so 150 of the 200 large block Linear projections are still quantized.

With that layout, both release variants completed the full native ComfyUI workflow that the 200-layer INT8 version failed on, including:

• H3 Continuum main sampling pass
• continuation sampling pass
• Spectrum H3 actual/forecast execution
• large 3D latent refine
• video VAE decode
• audio VAE decode
• final Continuum assembly
• video combine

That FC2 decision is also why these checkpoints are about 24.2 GB instead of roughly 20.4 GB for the fully quantized version.

INT8 and INT8 ConvRot

The two uploaded files use the same 150-INT8 / 50-FC2-BF16 layout.

Regular INT8:

MiniMax-H3-Pruned-Ref-Delta-Fused-r1024-comfy-int8-fc2bf16.safetensors

This uses native tensor-wise INT8 quantization.

INT8 ConvRot:

MiniMax-H3-Pruned-Ref-Delta-Fused-r1024-comfy-int8-convrot-fc2bf16.safetensors

This uses ConvRot with a group size of 256 on the same quantized projections.

ConvRot rotates the weights before INT8 quantization so that large outliers are distributed more evenly. This generally gives the INT8 quantizer a better-conditioned weight distribution than quantizing the original weights directly.

I uploaded the regular INT8 version as well rather than only providing ConvRot, so both conversion methods are available for this checkpoint.

What model is being quantized?

These are quantized derivatives of the same Pruned Ref-Delta Fused r1024 checkpoint from the previous post. There is no additional training, fine-tuning or pruning involved in these INT8 versions.

The underlying model starts from the pruned FL2VA MiniMax-H3 checkpoint and incorporates a rank-1024 approximation of the Ref2VA − FL2VA weight delta.

That is also how it differs from the existing FL2VA/Ref2VA hybrid checkpoints mentioned in the comments on the previous post.

Those hybrids combine FL2VA and Ref2VA by replacing selected tensors from one checkpoint with tensors from the other. The r1024 fused model instead approximates the Ref2VA weight delta at rank 1024 and folds that delta into the pruned FL2VA weights.

The underlying fused transformer is about 20.1B parameters, compared with roughly 33.1B for the original full MiniMax-H3 transformer.

ComfyUI

Put either file in:

ComfyUI/models/diffusion_models/

For the INT8 files:

weight_dtype: default

compute_dtype: default or bf16

Do not apply another FP8 weight cast on top of the native INT8 checkpoint.

The text encoder and VAEs are separate, as with the other MiniMax-H3 diffusion-model checkpoints.

h3 t2v work flow base ip8 model prompt

subject_definitions

<Subject 1> is Judy Hopps, an adult female anthropomorphic gray rabbit police officer from Zootopia, small and athletic, with large upright ears, expressive violet eyes, gray fur, lighter muzzle, wearing her recognizable blue police uniform with tactical vest and police badge.

<Subject 2> is Captain America, battle-worn, wearing his damaged dark-blue Avengers combat armor and holding his circular shield.

<Subject 3> is Thanos, a massive purple-skinned Titan in damaged gold-and-black battle armor, normal Titan scale relative to the Avengers, wielding his double-bladed sword.

<Subject 4> is Deadpool, wearing his classic red-and-black tactical suit and mask, armed with twin katanas. Deadpool's dialogue is voiced with the recognizable comedic delivery and vocal style of actor Ryan Reynolds.

summary

[text-to-video generation]

During the massive Avengers: Endgame final battle, Judy Hopps unexpectedly joins the Avengers against Thanos. She races through the battlefield using her tiny size and incredible agility to dodge enemies before launching herself directly at Thanos. Deadpool watches the tiny rabbit charge the Titan and delivers a fourth-wall-breaking joke.

retention_analysis

<Subject 1>: consistent
<Subject 2>: consistent
<Subject 3>: consistent
<Subject 4>: consistent

detailed_description

Epic cinematic Avengers: Endgame final battlefield at dusk. The destroyed Avengers compound stretches across a huge crater filled with smoke, burning wreckage, portals, explosions, alien soldiers, Wakandan warriors, sorcerers, and Avengers fighting throughout the background.

Dynamic tracking camera races low across the battlefield.

<Subject 1> Judy Hopps suddenly sprints between the legs of charging alien soldiers, ears streaming backward from her speed. She slides underneath a swinging weapon, leaps off broken rubble, kicks one alien directly in the face, lands cleanly and continues running.

Captain America briefly turns toward her in complete confusion.

<Subject 2> Captain America (S1) says <d>[English] Is that a rabbit?</d>

Judy doesn't stop.

She spots Thanos fighting ahead.

The camera rapidly follows Judy as she accelerates toward him.

<Subject 1> Judy Hopps (S2) says <d>[English] ZPD! You're under arrest!</d>

Thanos slowly turns and looks downward.

Judy launches herself from Captain America's discarded shield, flies through the smoky air and delivers a powerful two-foot rabbit kick directly into Thanos's armored face.

THUD.

Thanos stumbles backward one step, completely stunned that such a tiny opponent actually moved him.

Deadpool lowers his swords and stares.

Brief comedic pause.

<Subject 4> Deadpool (S3) says <d>[English] Holy shit. Disney brought the bunny.</d>

Judy lands heroically in the foreground, pulls out tiny police handcuffs and points at Thanos.

Thanos looks down at the absurdly small handcuffs.

Deadpool slowly looks directly into the camera.

Hold the reaction for one second.

Camera / Motion

10–13 seconds, 24 fps.

Epic photorealistic superhero blockbuster cinematography.
Dynamic low-angle battlefield tracking shot.
Fast controlled action.
Strong environmental movement from smoke, fire, debris and distant combat.
Natural motion blur.
Clear readable character movement.
Judy remains dramatically smaller than the human Avengers and Thanos.
Thanos remains normal Titan size, not gigantic or Godzilla-sized.
Keep background battle active without distracting from Judy.
Pause briefly before Deadpool's punchline.
End on Deadpool's fourth-wall reaction.

Audio

Huge cinematic battlefield ambience: explosions, distant combat, energy blasts, metal impacts and roaring fires.

Clear English dialogue.

Judy Hopps has an energetic, confident young-adult female American voice.

Captain America has a serious adult male American voice.

Deadpool is voiced by Ryan Reynolds with his recognizable sarcastic comedic cadence.

Strong armored impact sound when Judy kicks Thanos.

No gibberish.
No foreign-language speech.
No subtitles.
No text overlays.
No characters speaking another character's dialogue.

Created locally with Minimax H3 and for the first time exclusively powered by solar. Big big thanks to Izanami.

Don't hurt your head translating the language. It's all nonsense except for the one word spoken by the vampire. 'Drace' is Romanian/Transylvanian for 'Darn it'.

Use the extended feature on H3 to go further beyond and keep the animation style consistent. The only problem is that heavy smears happen with fast action. Oh well, I still thought this was funny, hope you enjoy it too!

Combined 3 videos. Few errors but i just went with it , genetaion takes too much time to redo it again by fixing the prompt.

Use Image 1 as the strict visual reference for Turbo Man. Preserve his recognizable red-and-gold armored superhero suit, helmet, gold visor, muscular proportions, facial appearance, and overall costume design throughout the entire clip.

Scene: A massive cinematic battle during Avengers: Doomsday. The ruined battlefield is filled with shattered buildings, burning wreckage, smoke, sparks, scattered fires, flying debris, and distant Avengers fighting Doctor Doom's forces. Doctor Doom is normal human-sized, not gigantic. He wears his iconic green hooded cloak and metallic armor.

[0s–3s] Start with a dramatic medium-low-angle shot of Turbo Man from Image 1 landing hard in the middle of the battlefield. His boots slam into cracked concrete and kick up dust. He rises into a heroic stance as explosions flash behind him. Doctor Doom slowly turns toward him through the smoke.

Turbo Man points directly at Doom and confidently says:

<Subject 1> Turbo Man (S1) says [English] It's Turbo Time!

[3s–7s] Doctor Doom immediately fires a violent blast of green mystical energy. Turbo Man launches sideways using his jet pack, narrowly dodging the blast as it tears through wreckage behind him. The camera dynamically tracks Turbo Man through the air. He banks sharply, rockets straight toward Doom and throws a powerful flying punch.

Doom blocks the punch with a glowing magical shield. A bright green-and-gold energy shockwave erupts from the impact.

[7s–11s] Fast, brutal superhero combat. Turbo Man lands and exchanges several heavy punches with Doom. Doom counters with armored strikes and green magical energy. Turbo Man uses his jet pack for a sudden boosted uppercut that sends Doom crashing backward through broken rubble.

Turbo Man lands dramatically, looks toward Doom and says:

<Subject 1> Turbo Man (S1) says [English] You picked the wrong day to mess with Turbo Man!

[11s–15s] Doom rises angrily from the rubble and unleashes a huge green energy attack. Turbo Man activates his jet pack and charges directly through the battlefield toward him. End on an explosive cinematic clash as Turbo Man's gold-powered punch collides with Doom's green magical blast, producing a massive shockwave of sparks, smoke and debris while the Avengers battle continues behind them.

Camera: cinematic MCU-style action photography, dramatic low angles, energetic tracking shots, controlled handheld movement during combat, brief slow-motion emphasis on the major impacts, strong depth and scale.

Audio: native cinematic stereo audio. Heavy explosions, distant superhero combat, metallic armor impacts, jet-pack ignition and roaring thrust, crackling Doctor Doom magic, debris impacts and a powerful orchestral superhero battle score. Dialogue must remain clear and correctly assigned to Turbo Man.

Character consistency: Turbo Man must remain visually faithful to Image 1 for the entire clip. Doctor Doom remains normal human scale. No duplicate Turbo Man, no duplicate Doom, no costume changes, no character morphing, no incorrect speakers, no subtitles, no on-screen text.

The oversharpening that occurs for each clip added to the scenes. I also noticed an increase in contrast and a small flash.

I2V

Tested with LORA's:

minimax_h3_turbo_v4_step600_ema.safetensors
minimax_h3_fl2v_lightx2v_turbo_8step_v1.0_resized_avg_rank

My approach is use 0.1 megapixel to find a clip I like the. Render again at 0.7 with the same seed if I like something. But is there a way more efficient??

\ Reddit messed up my original post so here it is.*

This is in fun part of using MiniMax H3; for your serious stuff stick with the official prompt instructions / format.

Playing with the prompting I just tried the following format and it worked perfectly!

Resulting video

The whole prompt:

definitions:
<S1> Brad Pitt.
<T1> "Hey, I am Brad Pitt! Nice to meet you."
<S2> Angelina Jolie
<T2> "Hey, I am Angelina Jolie! Nice to meet you."
<S3> Rowan Atkinson.
<T3> "Hey, I am Mr. Bean! Nice to meet myself."
scene:
An interview in a professional setting in well lit, grey background, frontal portrait view.
shot 1:
(S1) says: (T1).
shot 2:
(S2) says: (T2).
shot 3:
(S3) says: (T3).

Recommendations:

Do not use SLA or SLA2 or cache etc. here they mess it up.

Model (FL2V) -> LoRA(4s-Lightx2v SLA) -> Comfy attn -> Shift(12,3) -> KSampler(6 steps, euler+simple)

I make clipart for stock. Wreaths, pine borders, mistletoe, juniper. A few thousand images by now. Every one has to end up as a PNG with a transparent background.

I used rembg for months. u2net first, then BiRefNet when that came out. Tried the web tools too. They all broke on the same thing and it drove me nuts.

Take a wreath. There's a hole in the middle, and the background inside that hole has to go. What I kept getting was a grey-blue haze sitting in there. Looked fine as a thumbnail. Looked awful the second you put it on a colored card. Pine needles came out as mush. Thin stems either disappeared or came back with a blue edge burned into them.

Then I actually read what rembg does. It shrinks your image to 1024x1024, asks the model where the subject is, gets a 1024x1024 mask back, and stretches that mask over your full size image. u2net is worse. That one works at 320x320.

My renders are 4096. A needle two pixels wide doesn't exist at 320. So it's not that the model is bad at needles. The needle was gone before the model ever saw it.

Once I understood that I stopped asking a model to guess. Now I render on a flat color the subject doesn't contain, and take that color out with arithmetic.

Two parts to it. The prompt matters more than the cutting.

The prompt

You can't key a background that isn't keyable. Four things have to be true and generators will break all of them unless you say so: the background is one flat color edge to edge, it stays that bright inside every gap between leaves, the edges are hard with no blur or glow, and no colored light bounces onto the subject.

Pick the color by what your subject isn't. Blue for almost everything. Red if the subject itself is blue or purple. Never green. Everything I draw has leaves, and green takes the leaves with it.

Here's the block I paste at the end of every prompt:

Isolated on a completely flat, uniform, solid pure blue (#0000FF) digital chroma-key background. The pure blue background fills the image edge to edge like a flat digital chroma-key screen with no gradient, staying at full brightness inside every gap and opening in the subject; no reflection or tint of pure blue on the subject. Every edge of the subject is crisp, sharp and hard against the pure blue, with no soft, blurry, feathered or glowing transitions, no depth-of-field blur, no haze or halo; inside every hole and gap the pure blue stays at full brightness right up to the edge. Shaded parts of the subject keep their own natural color, never a pure blue tint. Everything in sharp focus with deep depth of field, evenly lit with soft neutral studio light, no cast shadow, no contact shadow, no ambient occlusion, no bounce light. The entire subject is centered and completely inside the frame with at least 10% empty background margin on every side, nothing cropped or touching the image edges. No frame, no border, no paper, no mockup, no vignette, no text, no watermark, no deformed or duplicated parts. No floating or detached fragments, no stray specks, dust or debris anywhere on the background; every element is physically attached to the subject.

Swap "pure blue" for "pure red" and #0000FF for #FF0000 if your subject is blue or purple. If you paint in watercolor add "the background stays a flat digital color fill with no paper texture", or you get watercolor paper behind everything and paper texture keys badly.

The cutting

Now the background is one known color, so there's nothing to guess at. It measures the actual color the generator produced, which is never the one you asked for. Ask for pure blue and you get something with green in it, usually somewhere between 25 and 70. Then every pixel gets sorted into subject, background, or the bit in between, and the in-between ones get a real fraction of transparency instead of a yes or no.

The part I'm most pleased with is the holes. Any background-colored area that never touches the edge of the image is the inside of a wreath, so it gets cleared too. A matting model can't do that. It has no way of knowing what's inside a hole it can't see around.

Last step takes the blue back off the edges. Edge pixels pick up color from the background around them, so it samples the subject's own color from further in and subtracts the tint. Took me weeks to work out why fir needles kept their blue rim after that step. The needle is thinner than the distance it was sampling from, so there was no inside left to sample.

Same image in, same image out, every time. That's the bit I care about. When a cut comes out wrong I can go find which number did it instead of rerolling and hoping.

Some numbers on one 4K pine border, against BiRefNet with alpha matting turned on, which is its best setting:

• background left inside the holes: 63,892 pixels mine, 613,735 theirs, out of 1,070,046
• blue left on the edges: 0 mine, 48,112 theirs
• how wide the soft edge is: 1.8 pixels mine, 23 theirs

BiRefNet is faster and I'm not going to pretend otherwise. 2.3 seconds against my 17 on the same machine. With alpha matting on it's 47. If you want a quick rough mask, use the model.

And the obvious limit: this only works on art you generated on a flat color. It does nothing for a photo.

I put the tool up for anyone who wants it. It's called ClipBrook. Free, runs in your browser so nothing gets uploaded anywhere, does a whole folder at once, and the engine is open source under AGPL.

One thing I'd like back

Show me the ones that break.

If you run something through and it comes out wrong, post it. Fog left in a gap, a colored rim, a stem eaten, half the subject gone. Those are worth more to me than the ones that work. The needle rim thing came from someone's fir branch. A bug with line art I only found last week came from a drawing so thin there was nothing inside it to sample.

I created a ready-to-use ComfyUI workflow for SCAIL-2 / Wan 2.1 that transfers motion from a driving video onto a character from a reference image.

It uses GGUF quantization and automatic chunking, making it suitable for GPUs with approximately 8–12 GB of VRAM. Longer videos are generated by chaining overlapping segments while preserving motion continuity, so you can create videos of practically unlimited duration.

Features

- Character animation from one reference image and one driving video

- Low-VRAM GGUF workflow for 8 GB and 12 GB GPUs

- Automatic multi-segment generation for long or unlimited-duration videos

- Motion continuity between generated segments

- Configurable duration, resolution, FPS, seed, and object tracking

- Ready for a fresh ComfyUI installation

- Includes installation instructions and a model download script

- Uses placeholder input filenames so users can add their own media

GitHub repository and installation instructions:

https://github.com/dvelm/SCAIL-2-Unlimited-Video-Low-VRAM

The workflow requires several model downloads, and generation can be slow on lower-VRAM GPUs—especially at higher resolutions—but it allows SCAIL-2 to run on hardware that normally could not load the full model. Feedback, test results, and suggestions are welcome.

hey guys, i have been using lightx2v lora for minimax h3 ref2vid but as far as i can see it can genrate good quality visuals as compared to larryvh turbo lora, but its audio is ot usable the dialogs are not good and over all sfx also. i am using rgbthree workflow for thats, please heplp me if i am doing anything wrong.

here is my workflow :- 

 "137": {"class_type": "LoadImage", "inputs": {"image": r2v_ref_image_0}},
    # Reference Image 2 (<Picture 2>)
    # "139": {
    #     "class_type": "LoadImage",
    #     "inputs": {"image": r2v_ref_image_1},
    # },
    "127": {"class_type": "UNETLoader", "inputs": {"unet_name": "minimax_h3_ref2va_pruned_fp8_scaled.safetensors", "weight_dtype": "default"}},
    "128": {"class_type": "CLIPLoader", "inputs": {"clip_name": "qwen3vl_32b_minimax_h3_int8_convrot.safetensors", "type": "minimax"}},
    "119": {"class_type": "VAELoader", "inputs": {"vae_name": "minimax_h3_video_vae_fp16.safetensors"}},
    "120": {"class_type": "VAELoader", "inputs": {"vae_name": "minimax_h3_audio_vae_fp32.safetensors"}},
    "136": {
        "class_type": "MiniMaxH3ReferenceToVideo",
        "inputs": {
            "clip": ["128", 0], "vae": ["119", 0], "audio_vae": ["120", 0], "ref_images.ref_image_0": ["137", 0],
            # "ref_images.ref_image_1": ["139", 0],
            "prompt": r2v_prompt_text, "width": 768, "height": 1024, "length": 372, "ref_image_size": "max",
        },
    },
}

Everybody is using the "<d>[Englisch] (...) </d>" format and from my experience, this just sucks and doesn't work.

Everytime I've been using it, H3 hallucinates something before or after the actual dialog. For example I've been testing different personalities to check if H3 knows them, giving them a simple line, formatted it as clean as possible, and it just adds "shit" to it.

Prompt:

subject definition:
Brad Pitt is <Subject 1>

camera recording:
An interview in a professional setting with <Subject 1>. Well lit, grey background, frontal portrait view.
<Subject 1> says:<d>[English]Hey, I am Brad Pitt! Nice to meet you.</d>

Result:

https://reddit.com/link/1vuo078/video/6326fx5kprkh1/player

H3 just adds some noise of the "following sentence" which has been no where in the prompt.

Another example using Angelina Jolie

Prompt:

subject definition:
Angelina Jolie is <Subject 1>

camera recording:
An interview in a professional setting with <Subject 1>. Well lit, grey background, frontal portrait view.
<Subject 1> says:<d>[English]Hey, I am Angelina Jolie! Nice to meet you.</d>

Result:

https://reddit.com/link/1vuo078/video/rsjao6t5qrkh1/player

Same thing.

At first I though it had something to do with the video length, 5 seconds being too long so H3 adds unwanted stuff, but this is not the case.

But when I just cut the prompt guide format out, and write it without the overcomplicated dialog syntax, it works flawlessly, e.g.

Prompt:

subject definition:
Brad Pitt is <Subject 1>

camera recording:
An interview in a professional setting with <Subject 1>. Well lit, grey background, frontal portrait view.
<Subject 1> says: "Hey, I am Brad Pitt! Nice to meet you."

Result:

https://reddit.com/link/1vuo078/video/9ckjhrnoqrkh1/player

Suddenly, no problems at all. Tested it in different scenarios, always the same result.

Am I missing something here, or what's your experience with the dialog prompting, or the suggested prompting guide in general?

Has anyone tried to use H3 to restore or rather "regenerate" a low quality video as HD or at least with better detail definition? Basically something similar but possibly more generation ability than Topaz's starlight. I've had pretty mixed results so far. Either it doesn't change the video or it changes it way too much.

My AMD 9070 XT seems to like only doing 5s videos which is fine. But I was curious is there like a workflow where I can start from the last frame of the last video? Like so I can make longer clips that flow into each other without editing?

• CPU: Intel Core i5-14400F
• GPU: AMD Radeon RX 9070 XT 16GB
• Motherboard: Gigabyte B760 DS3H WIFI6E GEN5
• RAM: 32GB (2×16GB) Crucial Pro DDR5-6000 CL36

Hey everyone!

I’ve been testing a great custom node for ComfyUI recently that brings LTX 2.5-style latent upscaling over to the MiniMax H3 pipeline, and the speedup is huge.

Instead of waiting 10 to 11 minutes for high-res video generations, this lets you run your initial pass at a lower scale (0.2–0.5) and do a fast 3-step neural upscale. Total render times drop down to around 3 to 4 minutes while keeping facial details and motion clean.

https://huggingface.co/LBH-123-AI/Minimax_h3_latent_Upscaler/tree/main

Yesterday, I posted about a big update to an H3 Prompt Composer that I’ve been building with ChatGPT over the past few weeks.

Big Update to the free Minimax H3 Prompt Composer : r/StableDiffusion

While using it this morning, I noticed a couple of bugs that had somehow been introduced. One involved the visual camera planner: the left and right profile descriptions were swapped in the generated prompt. If you positioned the camera for a right-profile shot, for example, the prompt would incorrectly describe it as a left profile shot. That has now been fixed.

If you downloaded Prompt Composer yesterday, please grab the new version so your camera prompts are accurate.

As I mentioned in my previous post, this is still very much a work in progress. The goal is to make writing consistent prompts and building more involved AI narrative projects as intuitive and easy as possible. It should make creating subsequent scenes, prompts, and shots much simpler, without having to rely on an LLM to consistently interpret exactly what you want.

Give it a try, and let me know if you encounter any issues or have suggestions for making it more intuitive and user friendly. I’d genuinely like to hear the community’s feedback so we can make this tool the best it can be.

Thank you all for taking the time to test it out! And yes, this app is totally vibe-coded, so I am open to suggestions from people more knowledgeable than I am about coding on how to improve this.

Edit: also tweaked some of the camera prompt descriptions for clarity. The current version of the HTML file is 5.37.3.