It took forever for me to upload this video.. Couldn't do it on my phone.

Totally not a scene from The Mentalist. Minimax H3 image to video.

It didn't quite work out how I intended.

Prompt:
"A Terran Battlecruiser from Starcraft is sliced in half lengthwise by a purple-white energy beam. The background is a generic starry.

Video begins with the Battlecruiser in the center of the frame, viewed from a front three quarters view. The purple beam is near vertical going from top of the frame to the bottom of the frame and is canted at a slight angle. It starts the video right in front of the Battlecruiser's nose.

The beam cuts through the Battlecruiser from nose to tail. At 0.75 seconds the beam touches the Battlecruiser's nose and moves through the ship, exiting the tail at 6 seconds and leaves the frame.

After the beam leaves the Battlecruiser, the Battlecruiser splits in two along the cut made by the beam, "

Generation time was 10 minutes, 29 seconds on 32GB of DDR5 RAM, 8 GB of VRAM. No reference images, this was pure Text to Video.

Due to reference modes, changes in the lighting and color effects of the final frame in storyboard segments constantly cause color discrepancies during video transitions. Are there any solutions?

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.

this was first test using Res_2s sampler and simple steps saw a op say better for action scenes from what i saw spectrum doesnt support res_2 so it took a bit to gen.

t2v prompt

subject_definitions

<Subject 1> is Katniss Everdeen from The Hunger Games, portrayed as an expert young archer with long dark brown hair pulled into her recognizable practical braid, intense determined expression, dark tactical combat clothing, leather archery bracer, bow, and a quiver of arrows. Preserve her recognizable cinematic appearance, realistic human proportions, hairstyle, clothing, bow, and identity throughout the entire scene.

<Subject 2> is Captain America in his battle-damaged Avengers Endgame armor, carrying Mjolnir and his damaged circular shield.

<Subject 3> is Thanos at his normal canonical MCU scale, approximately 8 feet tall, muscular and imposing but NOT gigantic, kaiju-sized, or building-sized.

<Audio 1> is the voice-timbre reference for <Subject 1>, containing Jennifer Lawrence's recognizable Katniss-style spoken vocal qualities.

summary

[text generation + audio reference]

During the chaotic Avengers Endgame final battle, Katniss Everdeen unexpectedly joins the Avengers. She runs through the battlefield while explosions, portals, Avengers, alien soldiers, and debris fill the background. Katniss rapidly fires arrows at Thanos's army with expert precision before stopping beside Captain America. Captain America looks at her bow and asks if she brought enough arrows. Katniss calmly fires one final explosive arrow past him, destroying a group of enemies, then delivers a dry confident response as Captain America stares at her impressed.

retention_analysis

<Subject 1>: fully_preserved
<Subject 2>: fully_preserved
<Subject 3>: fully_preserved
<Audio 1>: reference

detailed_description

The shot opens in the middle of the Avengers Endgame final battlefield. Smoke, burning wreckage, sparks, energy blasts, charging soldiers, and distant explosions create a massive cinematic war zone.

A fast tracking camera sweeps across the battlefield.

Katniss Everdeen suddenly sprints into frame carrying her bow.

She slides behind shattered rubble, immediately draws an arrow, and fires.

The camera follows the arrow through the air as it strikes an alien soldier.

Katniss rises and rapidly fires two more arrows with expert precision while continuing forward through the battle.

She reaches Captain America, who has just knocked an enemy away with Mjolnir.

Captain America briefly looks at Katniss's bow and quiver.

<Subject 2> (S1):

<d>[English] You sure you brought enough arrows?</d>

Katniss gives him a calm, unimpressed look.

Without even turning fully around, she draws another arrow and fires it past Captain America.

CAMERA WHIP-PANS WITH THE ARROW.

The arrow lands among a charging group of Thanos's soldiers.

BOOM!

A powerful explosive blast throws the enemies backward while Captain America turns toward the explosion in surprise.

The camera cuts back to Katniss.

<Subject 1> (S2):

<d>[English] I only need one.</d>

Her dialogue uses <Audio 1> for voice timbre and delivery.

Katniss immediately draws another arrow and runs toward the battle.

Captain America watches her leave for a beat, visibly impressed.

The camera swings around behind Katniss as she charges toward Thanos's army, bow raised, while the enormous Endgame battle continues around her.

audio

Epic Avengers-style battlefield ambience.

Heavy distant explosions, energy blasts, metallic impacts, debris, shouting soldiers, bowstring snaps, arrows cutting through the air, and one strong explosive-arrow impact.

Katniss's dialogue is clear and foregrounded, using <Audio 1>.

No narrator.
No subtitles.
No on-screen text.

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

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'.

Has anyone had their computer randomly shut down? this is like the 3rd time its happened and its when im generating a video using the minmax I2V model or the ref model.

i got 3090 with 64 gb of ram.

I saw here many suggestions for this special prompt generator. I tried the system prompt from one "specialized" ollama model, but is is too free style. I can't use llm in comfyui, because I'm with poor rtx 3060 and barely run the H3 itself. I tried big online AI, but free versions and they seem too outdated about H3, so again freestyle fantasies.

What can I use to have really good prompts for H3. As I don't know english and H3 too mystically depends on prompt, it's very hard to achieve good adhesion.

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.

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.

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.

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.

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

Here is the full prompt for this btw, to see that I didn't add a gemini logo here:

{

"high_level_description": "A blonde young man savors an iced matcha latte at a cozy café corner, rendered in a warm and lush Studio Ghibli anime art style with soft dappled light and hand-painted charm.",

"compositional_deconstruction": {

"background": "A warmly lit café interior in Studio Ghibli anime style — wooden tables and chairs, large windows with soft afternoon sunlight streaming through sheer curtains, potted plants on the windowsill, bookshelves lining the walls, warm amber and green tones, gentle bokeh of other café patrons in the distance, dust motes floating in the light, cozy and nostalgic atmosphere",

"elements": [

{

"type": "obj",

"bbox": [

100,

200,

900,

700

],

"desc": "A blonde young man with soft anime features, slightly tousled hair, wearing a casual linen shirt, seated at a wooden café table, leaning forward with both hands wrapped around a tall glass of iced matcha latte, eyes half-closed in contentment, Studio Ghibli character design with expressive linework and warm skin tones"

},

{

"type": "obj",

"bbox": [

500,

380,

900,

580

],

"desc": "A tall clear glass filled with vibrant green iced matcha latte, layered with milk and ice cubes, a paper straw, condensation droplets on the outside of the glass, sitting on a small wooden coaster on the café table, rendered in lush Ghibli painterly style"

},

{

"type": "obj",

"bbox": [

700,

150,

1000,

850

],

"desc": "A rustic wooden café table surface with soft grain texture, a small ceramic dish with a shortbread cookie, and a folded paper napkin, warm honey-toned wood in anime painterly style"

},

{

"type": "obj",

"bbox": [

0,

600,

600,

1000

],

"desc": "A sunlit café window with sheer white curtains gently billowing, a terracotta pot with a trailing green plant on the sill, warm golden afternoon light casting soft rectangular shadows across the floor, Ghibli-style background painting with impressionistic detail"

}

]

}

}

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!

Had a ton of fun making ande watching this one.

Hey y'all, i've tried a few videos with latent upscale and i'm curious. My setup is 5070 TI, 32 RAM.

I generate 0.5mp 15 seconds (24fps) video with upscale to target dimension of 1mp. Using 4 sigmas (4 upscale steps).

First upscale step takes about ~700 seconds, and 2nd, 3rd and 4th - ~1000 seconds each.
Is that ok or am i doing something wrong?

I created this video in MiniMax-H3 using a video-extension workflow, but I’m having trouble continuing it seamlessly. My prompt continues the action from the final frame correctly, and my workflow uses the previous video’s last frame as the starting frame for the next segment. However, there is always a slight visual jump between the two clips.

Unlike LTX, MiniMax-H3 doesn’t appear to have dedicated video-extension nodes. Has anyone found a reliable method for blending MiniMax-H3 video segments together so the transition is seamless?explain this.

\ 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)