Honestly just looking for a brief dialogue on this with a mod. I feel like it would help them as much as us, since people tend to assume the worst when there is a total vacuum of information.

Summary from https://www.reddit.com/r/StableDiffusion/comments/1vh9rtw/ama_minimax_h3_team_ask_us_anything_about_our/

This summary was compiled with AI but cross-checked manually by me for accuracy. I hope this helps for people who don't want to manually parse that 400+ comment AMA.

Things they said they'll actually ship

A real 2K stage (H3-Regenerate-2K). Right now the open weights top out at 768p short side, and cranking the resolution locally just eats VRAM without getting sharper. This is a separate model that takes your finished 768p video plus the original prompt and references, and re-generates it at high resolution — so it can actually redraw text, faces, and fine texture instead of guessing at them like a normal upscaler. What it's good for: getting genuinely deliverable-quality output locally instead of bolting a generic upscaler on the end. Coming, no date.

Sparse attention code. Attention is what makes long/high-res generations slow and memory-hungry, and the released weights don't use the faster path the model was trained with. They're releasing a deliberately cautious version — the goal is "free speed with no visible quality drop," not a big headline number, and squeezing more out of specific GPUs is left to the community. What it's good for: the same generations, cheaper and faster, on the hardware you already have. "Near term."

A dedicated image model (text-to-image + image editing). Built from the same family as H3, sharing its encoder, with a new decoder made for stills. People are already hacking this by generating 5 frames and grabbing frame one — this replaces that hack properly. What it's good for: making and editing your first frame at real image quality, then feeding it to H3 to animate. That's the workflow they recommend, since H3 can't preview a frame and continue mid-generation.

A full technical report. Architecture, training stages, data construction. What it's good for: people training LoRAs and fine-tunes currently guessing at how the model works.

Problems they've admitted are theirs and are fixing

• Faces and objects go to mush when they're far from the camera. Confirmed, not your settings, not fixable by adding steps or resolution. It's tangled up in several parts of the model at once and they're still isolating why. Named as a top priority.
• Grainy, smeary fine detail compared to closed models. Same story — not the VAE, not one training stage.
• Reference-to-video looks softer than image-to-video. Confirmed real, caused by the two checkpoints getting different post-training. Being worked on. For now: feed it the highest-quality reference material you have.
• Stitched clips don't join cleanly. Continuing a shot via reference drifts and shows seams. They think training on long sequences (made affordable by the sparse attention work) is the fix, but that's a future model, not a patch.

Maybe, no promises

A 4-or-8-step fast version — they're "actively considering" it, possibly as an optional Turbo with slightly worse quality, but won't commit to timing. The current model already has some low-step ability baked in, just not tuned for it. Also: switching to a proper Apache-2.0 license once the legal paperwork clears, and keeping future models open in general.

Not happening soon

• A smaller, lighter H3. They're telling the community to prune the existing weights instead.
• Drafting at low res then re-rolling the same seed at high res. Won't match — the noise changes with the frame size, and the model's low-res quality actually got worse during training as they pushed high-res.

I'd vote for Leon since I'm a sucker for an origin story, but I haven't played many of the games so I'm not sure what cool shit I'm missing; I'm sure there's a lot.

I keep seeing these "I'd give anything to be back in the 90s again" posts. Yeah sure there was lots of great stuff, but also a lot of not-so-great. I was born in '83 and had all of my coming-of-age experiences in the 90s. The stuff that I can personally attest to sucking that I don't miss whatsoever:

1. If you missed a few episodes of your favorite show you were screwed. Maybe it will come out on DVD some day...
2. Getting lost constantly; GPS might be the biggest thing we've all taken for granted. You're hanging out at a schoolmate's house for the first time this weekend? Get ready to write down a 20-step play-by-play of all the random landmarks and streets you need to be on the lookout for so you can maybe find your way there.
3. Having to choose between hanging out and staying home to watch something you were excited about.
4. Misinformation and wives tales couldn't be readily checked. I remember one of my teachers confidently telling the class that "the sky is blue because the Earth is mostly covered by oceans, which reflect up and that's why the sky is blue."
5. Going to the video rental store only to find that the movie/game you wanted had all FOUR of their copies rented out already. Oh well, maybe try again in 3 weeks when it's less popular.
6. If all the kids in your neighborhood sucked, or they all didn't like you, or there just weren't any kids around: You're fucked. No other option. No real way to socialize or build a friend group outside of the people you were incidentally located near.
7. Mail order stuff. Fill out a form, send in money, wait 4 weeks to get something back.
8. Weather forecasts had maybe a 50% average of being correct.
9. Most music media had a crappy shelf life. Tapes would get all warbly sounding if you listened to them a lot; CDs would get scratched and skip all the time.
10. Soooo many albums with literally only one good song. And no choice but to buy the whole damn thing.

As the title says...looking for a ComfyUI workflow for this. The only one I've found doesn't seem to work at all and destroys any outputs into a garbled mess.

My use case is simply to have the generation follow a reference image and replicate the pose.

Thanks!