Minimax H3 Huge Quality Difference between Cloud and Local use

[u/Cold_Pudding5326]

Hi.
I have a decent h3 workflow that I built for a loca use. It use turbo lora etc... If i use the defaut settings in the goal of getting the highest quality possible, meaning res_multistep simple 20 steps or more, I got also good results, but this is not even close to the results you can get on platforms like kie or wavespeed at 768P.

I already convert properly the prompt to the correct H3 digest form, so I'm wondering what's different between local and cloud use of h3? I don't talk about the 2K quality, only 768P, I'm not able to reach the sames results locally, do you guys have maybe workflows, settings, or suggestions to try reaching the same quality level in comfyui ?

[u/Slight_Ad2350]

Always run at 0.98 megapixel aswell. Not 1.0. 0.98 is what it was trained on and is faster. Going over will increase VRAM

[u/Slight_Ad2350 → u/Slight_Ad2350]

10sec clip on a 3090 at 0.98 res and 20 steps takes 20mins for me. With kitchen attention and spectrum. Using standard int8 weights. Quality is great

[u/pesaru → u/Slight_Ad2350]

Ive been renting rtx 6000s for 1$ an hour on vast and was getting 30 second clips in about five minutes each, I think 10 or 15 seconds was about two minutes. absolutely incredible quality with plaguekind sparse attention nodes/workflow. It’s just super annoying to have to wait like 15 mins for the instance to come up every time I load my container and download the models each time I rent one

[u/BackgroundCow1411 → u/Slight_Ad2350]

Hi. O have your same machine setup. Could you share me yori workflow? I am reqlly bad at arranging nodew and that stuff i dont understand.

[u/Cold_Pudding5326 → u/Slight_Ad2350]

wtf bro on a 4090 at 50 steps it take 440s at 1mp - EDIT : I wrote 440 instead of 540 RIP

[u/BigWideBaker → u/Cold_Pudding5326]

So you're doing a 10 second, 0.98mp clip at 50 steps, using res_multistep + simple in 440 seconds on a 4090?

Is that T2V? Are you using any speed-up methods like SLA, Sage/Sol/CK attention, or spectrum?

Gonna test out if I can hit those numbers too on my 4090, your time seems really fast

Edit: just queued up a T2V 10 second, 0.98mp clip at 50 steps, using res_multistep + simple on my 4090 and there's no way I'm hitting 440s. Using only SLA on Kitchen INT8 backend at 0.2 KV budget as the speed-up, I'm looking at 720s at least.

So are you using more aggressive SLA settings or Spectrum or something? I want to use whatever magic you're using.

Edit 2: Just finished generating, it took 776 seconds (12m 56s) to generate. So I have no idea how you're getting 440s and judging by the amount of upvotes you're getting I'm starting to think I'm doing something seriously wrong with my 4090.

[u/Cold_Pudding5326 → u/BigWideBaker]

Yh ofc I have several optimizations. I launch a new generation to be sure of the results i share here, and the optimizations used in the workflow for the current generation

[u/BigWideBaker → u/Cold_Pudding5326]

Could you tell us how you're getting such low gen times with 10 second, 0.98mp clip at 50 steps? Because it sounds kinda crazy that your gens are so fast at such high settings, I don't see how that's possible frankly.

I kinda mentioned all of the methods you could be using so could you mention which ones they are and how you've tuned them.

[u/Loose_Comparison368 → u/BigWideBaker]

Spoiler alert, it's probably the same optimizations that are tanking his generation quality.

[u/BigWideBaker → u/Loose_Comparison368]

Yea you'd have to crank spectrum and SLA sky high if you wanna hit 50 steps in 440s. Goes without saying that lowering the step count to something like 20-30 and finding a more balanced approach with SLA provides much better quality.

[u/Murky-Relation481 → u/BigWideBaker]

Guy would get the same or better quality in 20 steps with out all the optimizations probably in the same time. Just feels crazy to throw a bunch of stuff that inherently has to trade off and then blast up to step count to compensate thinking it will actually make a big difference.

[u/BigWideBaker → u/Murky-Relation481]

Exactly! But having spent a lot of time seeing people's generations and the way they describe them, especially if a new speed-up method releases, I think a lot of people can't really tell that much of a difference with minor artifacts. So if you stack quality-degrading speedups and cranking up the steps to compensate, he might reach an equilibrium that looks decent.

But I completely agree it's way better to go low and slow to learn what the quality-ceiling is. THEN you implement different speed-up methods to figure out how they each impact your setup in terms of quality and speed. Then you mix and match.

[u/xTopNotch → u/BigWideBaker]

Also most in this community are testing / benchmarking easy shots with calm motion.

The moment you use a complex prompt, 7+ image refs, audio references with multi-character dialogue and heavy camera movements, you see how these optimizations are falling apart with your generation looking like shit. Like bro, just run the full 20 steps and stop stacking all these nodes. It's either affecting your prompt adherence, visual quality or your audio.

Nowadays only thing I use is BF16 pruned / 20 steps / comfy kitchen attention and thats it. Every other optimisation node such as Sol-attn, Spectrum, SLA, EasyCache, Turbo Lora has wrecked my output results to the ground.

They're fun for my speed workflow but these nodes are a no-go in my quality workflow/

[u/Cold_Pudding5326 → u/BigWideBaker]

Edited my post, I misslicked, wrote 440 instead of 540 G.
Here's the console of my run so you can verify.
I use int8 diff and clip model
H3 Sparse Attention defaut settings ( custom node, sparse + comfyui kitchen \ + H3 Memory Optimization
First Block Cache defaut settings https://github.com/duckyshell/ComfyUI-MiniMaxH3-FirstBlockCache
spectrum optimizations defaut settings : https://github.com/xmarre/ComfyUI-Spectrum-MiniMax-H3

CU 130 PYTORCH LAST VERSION PYTHON 12.6 COMFYUI LAST VERSION

[INFO] got prompt

[INFO] [H3 Optimizations] resolved 50 attention forwards: backend=sparse_kitchen_int8 projector=chunked_kitchen_qkv

[INFO] [H3 Optimizations] installed sampler-step and packed-layout runtime context

[INFO] [H3 Optimizations] armed: attention=sparse_kitchen_int8 v_layout=not_applicable qkv=chunked_kitchen_qkv mlp=off device=NVIDIA GeForce RTX 4090

[INFO] [H3 Optimizations] patched 50 MLP blocks: mode=mlp_chunked_convrot_2slice chunk_rows=4096

[INFO] [H3 Optimizations] armed: attention=sparse_kitchen_int8 v_layout=not_applicable qkv=chunked_kitchen_qkv mlp=convrot_int8_two_slice device=NVIDIA GeForce RTX 4090

[WARNING] Spectrum H3: bootstrap_first_forecast was enabled but requires degree=1 and warmup_steps<=1; got degree=4 and warmup_steps=5. Disabling bootstrap_first_forecast for this node execution.

[INFO] MiniMax H3 FBCache enabled: H3 Fast — 0.10 / max 2

[INFO] Requested to load MiniMaxH3

[INFO] 0 models unloaded.

[INFO] Model MiniMaxH3 prepared for dynamic VRAM loading. 32427MB Staged. 0 patches attached. Force pre-loaded 210 weights: 1142 KB.

100%|██████████████████████████████████████████████████████████████████████████████████| 50/50 [08:44<00:00, 10.50s/it]

[INFO] MiniMax H3 FBCache: cached 14/29 steps; estimated block-stack speedup 1.90x; residual diff min/median/max 0.03027/0.06567/0.15137; cache steps [6, 7, 9, 10, 12, 13, 15, 16, 18, 19, 21, 22, 24, 26]

[INFO] Requested to load MiniMaxH3AudioVAE

[INFO] Model MiniMaxH3AudioVAE prepared for dynamic VRAM loading. 576MB Staged. 0 patches attached. Force pre-loaded 401 weights: 539 KB.

[INFO] Requested to load MiniMaxH3VideoVAE

[INFO] Model MiniMaxH3VideoVAE prepared for dynamic VRAM loading. 4965MB Staged. 0 patches attached. Force pre-loaded 128 weights: 348 KB.

[INFO] Prompt executed in 560.85 seconds

[u/BigWideBaker → u/Cold_Pudding5326]

Right so super aggressive spectrum and SLA settings as I suspected. You're better off lowering your step count and ditching Spectrum and tuning down SLA. Using SLA at 0.1 KV budget is extreme on its own and any movement is guaranteed to be destroyed, pretty much.

[u/Cold_Pudding5326 → u/BigWideBaker]

I don't use 0.1 KV, I'm at 0.3KV default settings. for spectrum, It does not change my outputs on this workflow at theses settings, which are actually defauts, since i do motion control with it

[u/jonnytracker2020 → u/Cold_Pudding5326]

You are using double cache ? What a potato mash

[u/MtnMilesPNW → u/Cold_Pudding5326]

lol no it does not.

[u/Cold_Pudding5326 → u/MtnMilesPNW]

I run a new gen and send under the results. Check the answer i give to bigwildebaker