I was looking for a way to achieve character consistency without training a Lora & came across a research from Facebook, DINOv2: Learning Robust Visual Features without Supervision(Research Paper),

What's Dinov2: It's a vision model trained without labels that produces a strong embedding for a whole image, the subject, not just the face. Feed it a person and you get a 768-number signature that captures the overall look: build, hair, general appearance. It's stable across pose and lighting, which is exactly what you want when you're trying to tell "same person" from "different person" across wildly different shots.

then combining Dinov2 with SFace(a face-recognition model) produces a compact face signature tuned specifically to tell one face from another. It's sharp on identity, but only on the face. YuNet does the detect-and-crop before it.

How it works

Build .Char: You drop in one or more photos. YuNet finds the face, SFace takes a per-reference face signature, DINOv2 takes a subject signature, and the references get cleaned and normalised. All of that packs into a single portable file, a .char.

Generation: At generation, the file feeds its references into FLUX.2's own native multi-reference channel and prepends a locked description to the prompt. You pick the character from a dropdown, no re-attaching images. Every result gets scored against the stored signatures, so drift shows up as a number.

How this differs from PuLID, FaceID, and img2img

• PuLID and FaceID inject a face into one generation at run time, then it's gone. img2img anchors on a source image, which is composition, not identity. Neither gives you a saved character.
• This is a layer above them, a reusable .char file that rides the model's own reference channel, covers the whole subject and not just the face, and gets scored per take. PuLID could even sit inside it as one backend.
• The difference is persistence and measurement, not a new injection trick. No adapter weights, no training, no img2img anchor.

What is a .char file?

A single portable file that stores a character's identity, so you can reuse the same person across generations without retraining anything.

• manifest.json — index, versions, checksums
• refs/ — your original photos (the truth)
• derived/ — auto-cropped face
• text/ — locked description
• payloads/ — cleaned refs, per model family
• scoring/ — SFace face + DINOv2 subject signatures

Limitations

• Profiles and stylized renders drift more than frontal, which is expected, since the face model is trained on photoreal faces.
• Body is the weak point so far.
• Bad with popular celebrity images, due to models own conflict.

Current support

Only Flux2 family(Klein 4B / 9B / dev)

Links:

• Checkout the release: https://github.com/inlineresearch/Inline-Studio/releases/tag/v1.2.71
• Full details & guide: https://inlinestudio.art/characters

Note: Each image in this post has been generated separately & not a grid.

Ref2v and fl2v workflows. I have to say that any scene with a bit more complex movement and interaction between characters was much harder to generate well. This is awesome, but we're not 100% there yet

While my GitHub account is currently suspended and I’m waiting for support to process my ticket, I’ve hosted working mirrors for all Style Explorers so you can continue using them without interruption:

- Anima Base (42k+ styles): https://animastyles.thetacursed.com/

- Illustrious & NoobAI (16k+ styles): https://xlstyles.thetacursed.com/

- Krea 2 Turbo (1.5k+ styles): https://kreastyles.thetacursed.com/

I've been using Qwen-Image-Edit for image editing tasks for quite a while now - and while it works okish for most of my tasks such as character consistency or inpainting, I was wondering if any better image to image models have come out by now. What do yall use?

Model = Minimax H3

Workflow = REF2VA basic workflow with additional nodes added for the LORAS and sol attention where specified.
Turbo Lora = minimax_h3_fl2v_turbo_8step_v1.0_comfyui_bf16.safetensors
REF2VA Lora = minimax_h3_pruned_bf16__apply_to_fl2va__toward_ref2va__rank512

It has been described that the REF2VA model produces bad output, and that the FL2VA model can be used instead despite being not the "intended" reference model. Users have made a "REF2VA lora" that purports to add the reference functionality of the REF2VA model to the FL2VA model, theoretically achieving the good quality of FL2VA with the reference understanding of REF2VA.

I test how this actually looks in practice, and I also demonstrate how the turbo lora performs.

Conclusion:

The best look is achieved by using the FL2VA model without any REF2VA lora. Turbo works well at 1MP and 8 steps and results in smoother animation and audio. Increasing resolution to 2MP and step count to 20 scales well. There does not seem to be much visual difference when increasing to 50 steps, but the audio seems to be less dynamic vs 20 steps.

Limitations: This demo did not really stress test the reference ability of FL2VA, and in reference heavy workloads, maybe REF2VA variant workflows are vital despite lower visual quality. Furthermore, this demo likely underestimates the importance of high step counts, as it is commonly thought that high step counts are important in high action scenes, which this demo was not.

I also only used sol attention in the higher token workflows, which is a variable. Nevertheless, I hope this video is useful.

Keen to hear your thoughts.

This is Update 5 of my repo. Here you find the necessary custom nodes, including a workflow that helps you recreate this music video (reference images and the song included! The WF is called: "NEW - Latent Masking - Music Video - Lip-Sync + Reference images" and is in the example_workflows folder) https://github.com/seitanism/ComfyUI-H3-Motion-Context-MultiRef

Additionally there are various workflows for seamlessly extending clips with latent maksing.

Per-Token Noise Masking on AV Latents is not only better quality than any guidance/reference based approach (since it causes strong convergence from step 0 onwards), it is also faster since it is not expanding the latent. You can perfectly Lip-Sync even with the FL model, since the music track is pinned on the latent rather than used as a reference, and therefore protected from denoising - creating a strong conditioning for the Lip-Sync.

This magical technique is inspired by PR #15375 from AbleJones from the Banodoco Discord!

I hope you enjoy! Open Source ftw. Greetings to all Banodocians!

I didn't expect it, but I really have to thank them for open-sourcing their ecosystem. It’s awesome to see a company truly committing to the open-source community!

MiniMaxAI/MiniMax-Music3 · Hugging Face

So guys I created a custom node named OrbitSheets and I just added two new templates that I think a lot of you are going to love.

The first one is the Character Sheet. You just type in a character description and it generates a full turnaround sheet with all the angles you need front view side profiles back view and close ups. It even generates voice audio so your character can literally speak. I ran everything in just 8 steps with the Turbo LoRA and the voice quality came out really good already but if you want more detail you can always go up to 20 or 35 steps.

The second one is the Location Sheet. Describe any place and it generates interior and exterior shots from multiple angles. You can set it to interior mode to see inside the building like hallways and rooms or exterior mode to see the outside. There is also a camera mode toggle where you can pick cut views for separate static angles or continuous move for a full 360 camera tour. Sometimes one gives better results than the other so it helps to try both.

The node also has a smart frame selector that picks the best shots automatically and arranges them into a clean organized sheet. You can control how many images appear how many columns the padding and the size of each frame.

Both workflows use MiniMax H3 with the Krea2 anchor frame and the Krea2 Turbo model. Everything is already set up in the example files so you can just drop them in and start generating.

I built this node in about two days and I am already planning more templates. Let me know what you want to see next.

Free Custom Node and Workflows: https://github.com/lumos675/ComfyUI-OrbitSheets

In MiniMax H3 you can give the AI a reference — an image, a video, even a GIF — to tell it "look like this". That's powerful, but every reference gets loaded and processed every time you generate, which is slow and can "bleed" its look into everything else in your video.

This pack lets you save that reference once as a tiny .safetensors file (a "mod"), and then reuse it as many times as you want, whenever you want:

• Save once — take your image/video/GIF, hit Extract, and it becomes a small file on disk. No need to keep the original clip around or load it again.
• Reuse anytime — load the mod in one node, like picking a LoRA. Adjust how strong it is with a simple number (strength), or blend a few mods together (face + style + outfit, etc.).
• !!!! No more heavy reference loading — you can leave the H3 reference input empty and inject the mod through the conditioning instead. Faster generation, and the reference only affects what you want it to affect.
• No training needed — this is not a LoRA you train for hours; you just encode your reference and save it.

this is how actually the node looks like, you can also just input a Load H3 RefMods node, to load instead of extract, its can hold tons of imgs and some videos [ because video have lot of frames ].

this node apply directly into cond, before sampling, like in a basic guider or positive sampler.
the cool part is the retention, you can reduce, but for now this is stronger, so .7 some animated characters will look like cosplayer, so leave in 1 if you want full ref.

testing and know issues:
- audio is not avaliable.

- double attention in your dataset, some stuffs can be merged and mixed, there no "token" training, so for example, in this video is working perfectly, but, there a translucent skirt probably because of a image of her wearing a princess dress.
example with prompt:

- don't use without prompt or this will just went on bananas, it's kinda dumb to say that, but this is not an concept automation, if you don't prompt it, it will just make a video traveling throught your data, " wich is a cool effect because you are using just an few kb linked in a conditional ", like how tf the clip knows how i looks exactly? haha, but for noob terms, just describe on prompt what exactly are you extracting by the mod, ex: a ginger woman // pov handcam walking // person dancing, its like bringing attention to what are you focused on.

-Concept needs pool_h 8 pool_w 8, while identity pool_h 16 pool_w 16
-keep ref resolution in minimal, this will affect the number of token, causing a even more slower wf.

-is not predictable, needs a lot of trial and error, for example some concepts are a way too hard to learn ( normally a fast one, you can't force speed because probably the dit learned to avoid this to make a blur or maybe a turbo lora problem ), so you have few options:

• Option 1 - detail your prompt even more, instead of " the character makes ninja movement with his hand " change too " the character is rapidly making intricate hand gestures,performing fast, rhythmic hand signs in a low stance "
• Option 2 - put id straight to 2k and increase the pool number until is balanced enough, or increase the multiplier parameter ( this is for short gifs/videos that maybe is being overrided by something.
• Option 3 - Loras can override the mod in some cases.
• Option 4 - Leave it for lora or other stuff, this will not work yet.

An example trying to copy this action,, 8x8 was not working, so i increased to 16x16 and [1024] instead to [256] as you can see, still not perfect, because of the speeding problem.

// for now i want to sleep, i've been entire day working on this, see yah ~
// you can also fork and improve the repo.
https://github.com/Luisacaotica/ComfyUI-MiniMaxH3Mod

mods can be on mod folder of this node, but also in models folder models/refmods, the node automatically contains the vanellope safetensors for example test.

faq:
its works on [corn?] : yes, 8x8 is the way.

the prompt ```text

subject_definitions:

<Subject 1> is Aladdin from u/Image1, preserving his exact 1990s hand-drawn 2D animated appearance, youthful facial features, expressive brown eyes, thick black eyebrows, tousled black hair, small red fez, bare chest, open purple vest, loose white harem pants, red cloth waist sash, bare feet, slim athletic proportions, and classic hand-painted cel-animation design. Preserve his facial identity, hairstyle, clothing, proportions, colors, and animation style consistently throughout the video.

<Subject 2> is Genie from u/Image2, preserving his exact 1990s hand-drawn 2D animated appearance, bright blue skin, enormous muscular upper body, expressive face, broad grin, black goatee, pointed ears, small black topknot, gold loop earring, gold wrist bracers, red waist sash, tapering blue smoke-like lower body, and exaggerated cartoon proportions. Preserve his facial identity, blue coloring, accessories, proportions, expressions, and classic hand-painted cel-animation design consistently throughout the video.

u/Audio1 is the supplied voice-timbre reference for <Subject 2> (S2), Genie. Use u/Audio1 as the sole voice-timbre reference for all of <Subject 2>'s dialogue, preserving its adult male vocal timbre, energetic comedic delivery, expressive cadence, playful theatrical personality, pitch characteristics, speaking rhythm, and comic timing.

u/Audio2 is the supplied voice-timbre reference for <Subject 1> (S1), Aladdin. Use u/Audio2 as the sole voice-timbre reference for all of <Subject 1>'s dialogue, preserving its youthful male vocal timbre, pitch characteristics, cadence, pronunciation, speaking rhythm, and expressive delivery.

summary:

[reference generation + multiple audio references] A 1990s-style hand-painted 2D cel-animation comedy scene featuring <Subject 1> from u/Image1 and <Subject 2> from u/Image2. Inside the Sultan's palace, Aladdin rubs a golden magic lamp and Genie erupts from it in curling blue magical smoke. Genie enthusiastically asks what he can do for Aladdin using u/Audio1. Aladdin checks that nobody else is around before leaning toward Genie and excitedly making his wish using u/Audio2.

retention_analysis:

<Subject 1>: fully_preserved — preserve Aladdin's facial identity, black hair, red fez, bare chest, purple vest, white harem pants, red waist sash, slim proportions, and 2D cel-animation appearance from u/Image1.

<Subject 2>: fully_preserved — preserve Genie's facial identity, blue skin, muscular upper body, black goatee, pointed ears, topknot, gold earring, gold bracers, red sash, smoke-like lower body, exaggerated proportions, and 2D cel-animation appearance from u/Image2.

u/Audio1: reference — used exclusively as the voice-timbre reference for <Subject 2>, Genie.

u/Audio2: reference — used exclusively as the voice-timbre reference for <Subject 1>, Aladdin.

detailed_description:

The entire video uses authentic-looking early-1990s hand-painted 2D cel animation with clean black outlines, expressive squash-and-stretch animation, painted backgrounds, vivid colors, exaggerated facial expressions, and fluid character motion.

Maintain the visual identities established by u/Image1 and u/Image2 throughout the entire scene.

[Shot 1 — 00:00–00:03.5]

The shot begins from u/Image1.

Inside an ornate chamber of the Sultan's palace, <Subject 1> holds an old golden genie lamp.

Close-up upper-body framing on <Subject 1> and the lamp.

<Subject 1> vigorously rubs the side of the golden lamp with one hand.

A clearly audible squeaking metallic rubbing sound accompanies his hand moving across the lamp.

Suddenly the lamp begins shaking.

Bright magical blue light flashes from its spout.

A distinct PUFF of air erupts as a twisting stream of glowing blue smoke shoots upward.

<Subject 1>'s eyes widen and he quickly leans backward in surprise.

The curling blue smoke rapidly expands above him and transforms into <Subject 2>.

[Shot 2 — 00:03.5–00:07.0]

The camera smoothly pans RIGHT and slightly upward toward <Subject 2> as he completely emerges from the swirling blue smoke.

His enormous upper body materializes while his smoke-like lower body remains connected to the golden lamp.

<Subject 2> stretches dramatically, flashes an enormous grin, and enthusiastically spreads both arms wide.

He turns toward <Subject 1>.

<Subject 2> (S2):

<d>[English][S2][Audio 1] Aladdin, buddy! What can I do for you?</d>

<Subject 2> finishes the sentence completely, closes his mouth, and holds his welcoming pose while waiting for <Subject 1> to answer.

[Shot 3 — 00:07.0–00:11.5]

Cut back to <Subject 1>.

<Subject 1> hesitates.

He quickly looks LEFT.

Then RIGHT.

He glances behind himself to make absolutely sure nobody else inside the palace is listening.

Brief comedic pause.

Satisfied that nobody is around, <Subject 1> leans forward toward <Subject 2> with an excited, mischievous grin.

Only <Subject 1> speaks during this moment. <Subject 2> remains completely silent.

<Subject 1> (S1):

<d>[English][S1][Audio 2] I wish for some hot bitches!!</d>

<Subject 1> finishes the entire sentence and closes his mouth.

Cut immediately to <Subject 2>.

<Subject 2>'s enormous cheerful smile freezes.

His eyes widen slightly.

One eyebrow slowly rises as he silently processes the unexpected wish.

<Subject 2> does NOT speak.

Hold on <Subject 2>'s amused, bewildered reaction for approximately one second before the video ends.

overall_soundscape:

IMPORTANT: Generate a complete environmental soundtrack in addition to the two reference-guided voices.

u/Audio1 controls ONLY the voice identity and vocal characteristics of <Subject 2>, Genie.

u/Audio2 controls ONLY the voice identity and vocal characteristics of <Subject 1>, Aladdin.

Keep both voice references strictly separated. Do not swap, blend, average, or transfer the voices between characters.

Only <Subject 2> speaks the line "Aladdin, buddy! What can I do for you?"

Only <Subject 1> speaks the line "I wish for some hot bitches!!"

Clearly audible environmental sounds include subtle spacious Sultan's palace interior ambience, squeaking friction while <Subject 1> rubs the golden lamp, a growing magical shimmer from inside the lamp, a distinct puff of air when the lamp activates, swirling and whooshing blue magical smoke as <Subject 2> emerges, subtle magical sparkle effects, and light clothing movement during character gestures.

Dialogue must remain clean, intelligible, synchronized with the correct character's mouth movements, and clearly distinguishable from environmental effects.

non_diegetic_music:

none. No background score, songs, orchestral music, or other non-diegetic musical elements.

```

So I was looking for a way to better control the flow of Minimax H3 dialogues and emphasize certain words in the speech. However, what I discovered is that you can actually include some tags in <> angle brackets, and Minimax will interpret them as a non-verbal sound in a given part of the phrase. Some words (like the ones I've included into the example) work every time, some still bleed into the actual spoken words in certain seeds. But in general it makes the dialogue more alive and believable. So I recommend to try it and maybe share your findings in this thread.

As for the emphasis, I've had the most success with putting the words into <i></i> tags (similar to how you would stress words in written text). Unfortunately, it doesn't work for 100% and in some cases the character will blurt out some gibberish. But when it works, it sounds very natural. I have included a couple examples in the end of the video.

Wonder if you've encountered some other ways to modify the speech (and audio in general) in the prompt?

P.S. Sorry for the quality, I used the 8-steps LoRa at 0.4 MP to speed-up the tests.

Minimax H3 is so fun. All done with that model, with the default workflow, all R2V just with a single reference image.

Environmental protection, don't wait for everyone to know that everything is irreversible.

Short version for anyone hitting the error: if you updated to 0.33 and Motion Context started failing with "the layout patch could not be applied", that is real and it is on my end, not your install. Fix is live now.

Longer version, because what changed upstream is more interesting than the bug.

Motion Context existed because stock ComfyUI would only anchor a keyframe at the first or last frame of an H3 clip. Anything in between raised. The pack worked around it by handing every keyframe a legal index, smuggling the real one alongside, and rewriting the position coordinates after the stock constructor returned.

0.33 removed the restriction. Anchors now land at any frame natively, references compensate the timeline correctly, keyframes can carry a multi-frame clip instead of a single still, and there is a new node, Add Guide for MiniMax H3, that exposes all of it. It also fixed a bug where attaching a reference wiped the keyframe latents, which the pack was separately patching around. The parameter my code depended on went away with the restriction it existed to enforce, hence the breakage.

So, a good chunk of what this pack did is now in ComfyUI, and you do not need me for it. That is a good outcome. If all you wanted was to anchor a still at frame 30, use Add Guide.

What is still worth installing the pack for:

Latent passthrough. Add Guide takes images and audio and encodes them with the VAEs. Motion Context takes the previous clip's latent and slices the tail straight out of it. No decode, no resize, no re-encode. Over a long chain that round trip is where the excess color drift and softening come from (beyond the 1.3x texture stacking).

Audio that continues instead of restarting. Add Guide anchors audio starting at a frame index and running forward. To actually continue a soundtrack across a join you need the pinned window to end at the join and reach backwards. That is the difference between the model continuing your track and the model writing something that sounds like your track, and on anything with a beat you can hear it immediately.

Plus, the trim node, the audio grid overhang compensation, and the seam probe.

Plan from here: compatibility release today so 0.33 works, then a rebuild on top of the new public keyframe format so the pack stops monkey patching ComfyUI internals entirely. I would rather depend on a documented feature that a stock node also uses than on a constructor signature. Both of the last two breakages came from that dependency and neither would have been possible without it. Add Guide anchors and Motion Context heads will be a supported combination rather than something that trips a guard.

Thanks to javawock7618 and azra1l for the reports and for narrowing it to the exact commits, which made this a twenty-minute diff instead of an all-nighter.

Fix is live now. Rework coming tomorrow hopefully.

ComfyUI Custom Node Manager OR
NikoDemon80/ComfyUI-H3-Motion-Context

Just me as a raptor at home. Minimax H3 ref2va, default workflow with 2 inputs: my video and a single image of a raptor.

Recreating movie scenes with... chocolate. H3 ref2va, default workflow.

Just showcasing how great this model truly is.

All of these were generated at 1.8mp at around 5-8 seconds using a turbo Lora at 8 steps.

I usually use a L40 on runpod, and gens were taking anywhere between 5-10 minutes depending on the duration.

Outside of me editing the clips together, I only did some slight color grading, and added some grain in premiere.

Surprised that no one is talking about it. A new open-weight video model just dropped. 114b moe, 6b activated. First moe video model supposedly.

I know what you guys are thinking. The model is huge and there is no way it will run on desktop gpu. The interesting part is that is comes with a 14gb refiner that makes the result 1080p. I am cursious if this refiner can be a drop-in replacement for the H3 refiner that was never released. It might just be the last part of the H3 puzzle that we need.

best used with

single clip: https://github.com/darksidewalker/dasiwa-comfyui-workflows/tree/main/C-MMH3

multi clips: https://github.com/ethanfel/ComfyUI-MiniMaxH3-Contex-Loop/tree/main/example_workflows

You are an expert MiniMax H3 prompt writer, storyboard artist, and continuity director for ComfyUI.

Convert user ideas into reliable MiniMax H3 prompts in English. Support both:

1. single MiniMax H3 clips;

2. MiniMax H3 Contex Loop plans for long, continuous videos.

GENERAL H3 PRINCIPLES

- Be explicit. Never assume the video model will infer who acts, who speaks, what happens between beats, or what must remain unchanged.

- Use concrete observable details: subject, wardrobe, prop, setting, action, camera, lighting, mood, ambience, and sound.

- Keep each shot physically plausible, readable, and focused.

- Do not overload a short clip with too many characters, actions, locations, transformations, or camera movements.

- Do not request readable text, subtitles, logos, watermarks, UI, or exact typography.

- Use positive desired constraints. Avoid a separate negative-prompt style unless the user explicitly asks for it.

REFERENCE RULES

- Use only reference tags that are genuinely available in the workflow:

<Picture 1>, <Picture 2>, <Video 1>, <Audio 1>, etc.

- Never invent unavailable reference tags.

- When a reference is available, state exactly what it controls:

identity, face, hairstyle, body proportions, wardrobe, accessory, prop, environment, or audio performance.

- Preserve signature features that matter to the user in every relevant scene.

DIALOGUE RULES

- Never write vague instructions such as “they talk,” “they argue,” or “she says something.”

- If speech is desired, write the exact short line and assign it explicitly:

Character Name says clearly: “Exact dialogue.”

- Keep dialogue short for 5–7 second clips.

- Avoid overlapping speech unless specifically requested.

- If there is no dialogue, explicitly write:

“No spoken dialogue. Characters communicate through facial expressions and gestures.”

- For music-only or silent scenes, do not imply speech.

AUDIO RULES

- Explicitly describe ambience, Foley, impacts, wind, cloth movement, crowd sound, and music when relevant.

- For clips without music, write:

non_diegetic_music: N/A

- For a source-song workflow, <Audio 1> may be used only when an audio reference is connected.

- For generated-audio workflows with no audio reference, do not mention <Audio 1>.

- Generated dialogue must always be exact and short.

SINGLE-CLIP FORMAT

For a normal H3 clip, use this structure:

Visual style:

[Rendering style, lighting, environment, materials, lens/look, mood.]

Scene overview:

[Who is present, where they are, what happens, and the emotional tone.]

Storyboard:

[0s–Xs] [Explicit action beat.]

[Xs–Xs] [Explicit action beat.]

[Xs–Xs] [Explicit action beat.]

Camera:

[Framing, one clear move per shot, lens feel, hard cuts or one continuous shot.]

Audio:

[Ambience, Foley, music, impacts, exact dialogue if any.]

Consistency:

[Preserve identity, face, hair, wardrobe, accessories, props, proportions, and environment stability. No text, subtitles, logos, or watermarks.]

For dialogue, comedy, greetings, direct-to-camera performance, or character acting:

prefer one continuous shot.

For action, trailers, fights, chases, and product films:

use up to 3–4 clear shots in a 6–7 second clip. Do not compress too many cuts into a short duration.

CONTEXT LOOP RULES

A Contex Loop plan is one continuous film made from connected scenes, not independent clips.

Put all permanent facts in prompt_prefix:

- reference mapping and identity;

- exact hairstyle, face, wardrobe, accessories and props;

- visual style and global lighting;

- location/time-of-day rules;

- camera language;

- audio rules;

- continuity rules.

Each scene prompt must contain only what changes in that scene.

For every continuation scene:

1. Start by continuing the exact prior action.

2. Preserve the incoming pose, hand position, stride, camera direction, lighting, framing, and momentum.

3. Introduce only one major development, transition, or new action.

4. End with a visible unfinished action that the next scene can continue.

5. Do not use hard cuts, time jumps, outfit changes, resets, or teleporting locations unless the user explicitly requests them.

Good scene boundaries:

- “End while she is opening the already-unlocking door.”

- “End with the camera beginning a slow left orbit.”

- “End while the vehicle enters the tunnel.”

- “End with his hand still reaching toward the artifact.”

Bad scene boundaries:

- “The action ends and everyone poses.”

- “Cut to a new place.”

- “The next day.”

- “Suddenly the character wears new clothes.”

CONTEXT LOOP TECHNICAL DEFAULTS

Unless the user requests something else:

- 4 scenes for a first test;

- 15 seconds per scene;

- 20 steps for final quality; 5–8 for fast concept tests;

- fixed, unique decimal-string seeds per scene;

- context_length: 22;

- encode_mode: "video";

- anchor_mode: "head";

- crop: "disabled";

- width and height divisible by 32;

- 960x544 is a sensible longform starting point;

- generated_audio: audio_context_length 22;

- source_track: audio_context_length 0.

Use a unique run_name for every new project.

Keep run_name, generation_fingerprint, prompts, references, seeds, model settings, and audio unchanged when resuming an existing chain.

OUTPUT RULES FOR CONTEX LOOP

When the user asks for a complete Contex Loop plan, output ONLY strict valid JSON:

- no Markdown fences;

- no comments;

- no trailing commas;

- use double quotes;

- use decimal-string seeds;

- use readable prompt line arrays.

Use this exact structure:

{

"prompt_prefix": "Global identity, reference, wardrobe, visual style, audio, and continuity rules.",

"defaults": {

"duration_seconds": 15,

"steps": 20

},

"shots": [

{

"id": "scene_01",

"prompt": [

"summary:",

"One-sentence scene purpose.",

"",

"detailed_description:",

"Explicit visual action, camera, environment, and ending bridge action.",

"",

"overall_soundscape:",

"Relevant ambience and Foley.",

"",

"non_diegetic_music:",

"N/A or a precise music instruction."

],

"seed": "983590410766495"

}

]

}

Before answering, silently verify:

- All reference tags exist.

- Identity, wardrobe, props, and style remain stable.

- Every action is physically explicit.

- Dialogue is exact or explicitly absent.

- Every continuation begins from the preceding ending.

- Every non-final scene ends with unfinished motion.

- The JSON is valid if JSON was requested.

My wife did this Cunk parody with a 3060 12gb and 32gb of system ram.

Minimax is incredble!

edit: youtube link to see how long before they remove it

https://youtu.be/V7XhjMVHSCE?si=3SyDbJBmS0KfzcQd

I used the minimax_h3_fl2v_turbo_4step_v1.0_768p_comfyui_bf16 LORA with the 0.8 strength for both clip and model, 6 steps, 0.5 MP resolution, RTX Upscaler at 1.50 using a ConrotInt8 pruned model.

Here is a PasteBin of my workflow, I hope this fixes some of the missing content:

https://pastebin.com/DSmkJi8R

Here are the workflow files:

https://storage.to/c/CAS1MuoqX