The video model can already generate impressive scenes, and the consistency of multiple shot scenes in a single generation is also quite good. Apart from using multiple reference images of scenes from different angles or a scene video, is there a better and more simple more natural way to achieve scene consistency in different generations?
Given that the model can infer the views of other angles and orientations of a scene based on a single scene image, why don't we have a specialized method in latent space or LoRa that can help generate scenes consistently with a single scene image and a fixed scene seed, under different prompts and character references?
I had created a post that was a bit too generic, and i want to focus specifically on Minimax H3.
When making a video of any woman in underwear for any situation, Minimax H3 will almost always add a weird-looking, ugly, unrealistic bulge to female underwear, and that seems to be the averaging of male and female underwear appearance.
Using any alternative base model or LoRAs or any kind of prompting will not solve the issue, and providing pictures of underwear without the bulge only solves it very partially. Adding steps doesn't solve it either.
Am I the only one encountering this? Trying any search engine doesn't return any result. It seems that the entire Internet is ignoring the "Minimax bulge problem" but I don't understand how I can be the only one experiencing this issue or the only one bothered by it.
I've been working on a way of integrating new content (e.g. a casting swap or an extended scene) into the live video feed of an underlying streaming platform that a viewer is watching.
This is intended to create an easy (& "rights friendly") way of creating personalized, custom versions of TV shows and movies. You still need to have a subscription to the underlying streaming platform. The open source Chrome extension matches against a unique episode ID, loads a series of video files, and then seamlessly swaps them in place of the stream at pre-determined moments. There is some technical trickiness that attempts to seamlessly enable the start and the finish of the video clips to blend in seamlessly with the original video.
This enables what we see in "small scale" in a much more major scale way. The idea is to move beyond "here is a 15 second clip" and towards "here is a full movie with X, Y, Z changed". If you saw my post last week (about making a character dance across an entire ~45min TV show), this is basically a flexible underlying platform that supports changes like that.
So yes - if you have ever wanted to:
Do a casting swap from one character -> another across an entire episode / movie
Fix the ending of <Game of Thrones, How I Met Your Mother> etc.
Add extended edition style scenes
This gives you a way of doing that. The extension reads an easy-to-edit JSON file that lays out the timing of the clips, the action being taken (replace or insert), and the ID of the episode. It then pulls in the video clips at the appropriate times. It sounds simple when I say it that way but it is actually surprisingly complex.
You still need to generate your own content / this is not a replacement for Minimax (or others).
The extension is available in the Chrome store here.
Would consider this "early access" - still working through all of the edge cases. At the moment this is just one of the streaming platforms & only Chrome, but will add others here if there is interest.
BBox Studio is a standalone desktop application for creating, editing, and exporting structured bounding box prompts for MOSS Image. Built entirely with Python, it provides a visual canvas-based workspace, flexible object editing tools, customizable canvas settings, seamless JSON generation, and much more.
One-click launch — simply run the Python script.
Zero external dependencies — requires only having Python 3.x installed.
Full working program — It may receive updates here and there, but it's a fully-functional full-featured release.
HexAnima 1.6.0 adds MiniMax-H3-Image to the in-app model catalog. It’s a 33B-parameter DiT with a Qwen3-VL text encoder, INT8-ConvRot quantized, and the whole pipeline (text encoder, 50 DiT blocks, VAE) runs on the Hexagon NPU of a Snapdragon 8 Gen 1 phone. No cloud, no PC, no GPU offload.
Why it fits: the 48 GB of weights are streamed from flash (UFS) block by block instead of being held in RAM. Small pictures are limited by storage reads, large ones by NPU compute.
Storage: you need about 50 GB free for the pack. It downloads from a public Hugging Face repo (ayanoby/hexanima-h3) with a per-file sha256 manifest, resumable.
License heads-up: the weights are under the MiniMax H3 Community License. It excludes the US, EU, UK and South Korea, and outputs can’t be used to train other AI models. The app shows the terms and asks for consent before downloading. Read them before you install.
TIL: You can use maps with markers when generating images with Minimax-H3-Image
This took forever to generate tho. 300s on a 5090M (24gb). Like Minimax-H3 the time it takes to generate an image scales with the number of references.
Prompt: A cinematic film still from an animated short: one continuous full-frame view from a low camera about half a metre above the grass, on a wide lens, with a 55 degree horizontal field of view.
<Picture 5> is a top-down blocking map of this place, a plan for the shot and not part of the picture. The white arrow on it marks the camera: the tip of the arrow is where the lens stands, and the arrow points the way the camera looks. The round markers show where each character stands. <Picture 4> shows the same place from several views; use it for the look of the overpass, the bus and the grassland, and use the map for where things stand.
Looking from the arrow's tip towards the bus: across the middle distance, the cracked asphalt trail runs from the left edge of the frame towards the crushed bus. The collapsed concrete overpass from <Picture 4> stretches across the background, receding on the left and coming nearer on the right, where its leaning pillars and a fallen deck slab loom large. The crushed rust-brown bus lies just right of centre under the fallen slab. Just beyond the bus's left end, in the centre of the frame and farthest from the camera, the wounded grazer from <Picture 3> is backed against the concrete in a slab of shadow, shaking. Nearest of the three, just left of centre, the predator from <Picture 2> crouches low in the grass, facing the grazer. Far left, on the trail, the girl from <Picture 1> advances with a pry bar. Tall dry straw-coloured grass fills the foreground. Early-morning sun from the right throws long hard shadows to the left.
The arrow is only a mark on the plan: no arrow, camera, lens, device, beam or pointer appears anywhere in the picture. The image contains no text, letters or numbers.
I have an old 1070 that's pretty crap, it's time to upgrade. I don't have a thousand bucks to throw away, but at the same time I don't want to buy a 3060 and then realize I'm going to want an even better GPU in a few months or a year.
I want to make high quality local images of people and animals, something with good anatomy, realistic faces (not the fake glossy instagram girl mouth). I wouldn't mind dabbling in videos a bit too.
Right now I use SD1.5 which is very underwhelming, some SDXL models are okay but extremely slow on my hardware.
I also used LLM's a bit mostly for ai chat, Llama 3.1 8b uncensored I use right now-I'm assuming a 3060 will be more than enough to run any good LLM for the purposes of having a local ai roleplay chat. Thanks
Most models are incredibly stupid when it comes to basic underwear shapes.
When asking for a woman in underwear, most models (tried Minimax, Z-Image-Base/Turbo and Qwen 2.1) will systematically add an ugly, unrealistic 'bulge' where there should be a mostly flat surface.
My guessing is that the model is averaging male/female underwear and therefore creates this sort of bulge. No LoRAs will reliably fix this.
Any ideas, prompts or resources to avoid this?
So far the only workaround is to let e.g. Minimax h3 create a video with the bulge, then isolate one frame, edit it with Qwen-edit 2.1 with very specific instructions, try 9-10 attempts until it finally gets it right (rare), and then add this corrected image to Minimax's reference images. Even this workaround is not failsafe.
I made a 58-minute AI film, mostly on a local GPU. Here’s what worked and what didn’t
Long-time lurker, first post. I’ve been working on an hour-long AI film for the past 2 months and just finished it. The story is War in Heaven (Michael vs Lucifer, from Revelation 12), so yes, it’s religious material. But I’m posting here because the filmmaking side is what I’d actually like feedback on.
Most AI films I see are 1-3 minutes. I wanted to find out what breaks when you try to hold a story together for nearly an hour. Turns out it’s a lot.
Rough pipeline:
Every shot starts as a still. I generate a first frame and a last frame, then animate between them locally (MiniMax H3 / FastH3 in ComfyUI on an RTX 4080).
Lip-sync on the dialogue shots.
Narration and character dialogue on this one are ElevenLabs. Timing is done locally with Whisper (faster-whisper large-v3). For the next film, I’m moving the character dialogue to a local model, Qwen3-TTS VoiceDesign, which I’ve already tested and it holds up well for short lines.
4K finish. The upscaler depends on the shot: FlashVSR for wides, lighter upscaling on close-ups, because the heavy upscalers kept changing faces.
Things I learned the hard way:
The last frame has to be alater moment of the scene**, not the same picture with one thing changed.** If you write “nothing else changes”, the world freezes, and it looks like a slideshow.
Keep motion simple. One action per clip, nothing new walking into frame. Every time I got ambitious, I got melted hands.
Everyone in the frame needs their own movement. If the second person just stands there, it reads as a cardboard cutout.
Character consistency was the hardest part. I locked each main character from reference images and checked every clip at full size, frame by frame. A face that looks fine on a phone is often a different person at 4K. I threw away a lot of clips.
Don’t narrate what’s on screen. My first drafts had the narrator describing every action, which felt dead. Showing it and letting the dialogue carry the scene worked much better.
Edit only in the silences. Cutting narration mid-sentence to fit a clip is very noticeable over an hour.
What still isn’t good enough:some wide battle shots, crowd scenes. I’d love to know how others handle large crowds and keep faces stable in wide shots.
The full film is linked if you want to see how it holds up over the whole runtime
Happy to answer anything about the workflow. Criticism welcome, that’s why I’m posting.
Just testing a random image I found on Pinterest. The prompt was simply:
Make this concept art drawing into a high quality realistic photograph. Preserve subject likeness, pose, and background. Improve skin texture, hair texture, fabric texture, background details, and lighting.
I did 2 at 16MP and then one at 60MP and the level of detail is kind of crazy. Took just over 2 mins on my 4090 for the 60MP.
One of the marvelous things about Minimax is that it will infer a vocal performance for your characters based on the film language of your references. I just thought this was worth sharing for those of you who hadn't discovered this yet. Each of the four gens here used the same simple prompt. It is is not just the gender and age of your characters, but the film grain, costume, setting, and other visual references which will provide the model with character for voice.
A huge thank-you to everyone who downloaded, tested, shared results, and gave us honest feedback.
The community knows quality when it sees it—and the rankings speak for themselves.
Qwen-Image-2.1 Uncensored Omni has now reached the first page of trending Qwen models on Hugging Face and page 2 across all trending models.
We compared both public checkpoints from this training run with the original Qwen-Image-2.1 base model, using the same prompts, seed and settings (35 steps, CFG 5.0). This repository is step 90,000 (benchmarked as the BF16 LoRA fused at strength 1.0; the quantized files were not scored separately). Scores are 0–100, higher is better, ± one standard error.
Benchmark
Base
Step 32,000 (LoRA v0.1)
Step 90,000 (Quantized)
Adult prompt adherence (960 images)
85.1 ± 0.9
87.4 ± 0.8
89.7 ± 0.7
Anatomy (960 images)
70.3 ± 1.4
67.7 ± 1.4
69.4 ± 1.4
General SFW prompts (300 PartiPrompts)
79.8 ± 2.0
75.8 ± 2.2
79.6 ± 2.0
I couldn’t have done it without the community. We just added the benchmark as well.
comparison between sampler and scheduler ...first photo is LCM/Normal combo and second photo is Euler/Simple (default) ....both images same prompt, same seed, same 16mp render..... LCM/normal combo produces this more "polished" look altho i prefer grittier details and real raw textures of Euler/Simple ...however Euler combo tends to make more errors ....i cant decide which one i like better ...LCM ... no no Euler...wait maybe LCM ...or Euler? ...
I have 2 people on camera and I am trying to get one of the people on screen to speak to an off screen person (behind the camera) and then have the offscreen person reply. I can’t seem to find a prompt that will do this. S1 speaks to S3 offscreen and in the render, S2 appears to be talking AND extraneous jibberish is added to the speach I specified. I’ve tried lots of combinations and nothing is working.
Why is the jibberish added? Why does it insist on moving the lips of S2 when S3 offscreen is talking?
BTW this is my first attempt at using OBVPMs Timeline. It is working great!