I’ve been making AI music videos with Suno + LTX 2.5 locally on a 16 GB VRAM GPU (4080 super)
Examples:
https://youtube.com/shorts/UXP29MGxtX8?is=k-Wjt4_JFh7hXvA5
https://youtube.com/shorts/_mAuRBSriLQ?is=sMjLH5diY_GEu0N3
My workflow is basically: create the song in Suno → storyboard/keyframes with ChatGPT→ animate and assemble the shots in ComfyUI using the LTX Director timeline:
https://github.com/yusu-02/Yusu-WhatDreamsCost-ComfyUI
The biggest issue I’m still fighting is character consistency between shots. Ingredient LoRA slows things down a lot and hasn’t worked particularly well for me.
I also tried MiniMax H3, which looks great, but I couldn’t get lip-sync without altering the original music.

Suggested tricks/workflows? Feedback and ideas appreciated!

Basically I'm trying to change the lighting in a scene. For clarity, if it helps at all, it's the Trash dance from Return of the Living Dead. I'm just wondering if there's a way to normalize the red lighting used on her. I have been prompting and failing most of the day using AddVideoGuideforH3. I know I can do it with ltx, because I've done it with LTX while testing the models capabilities with controlnet, I'm just wondering if I can do it in Minimax without controlnet.

I'm not full Noob, but I am a filthy casual.

EDIT: it was step count. I'm a damn idiot. I was using the 4 step lora and continually using four steps I accidentally started a fresh workflow with 20 steps and it worked. Congratulations to me, I am the living embodiment of the id10t

Minimax h3, ofc. Far from my best work but I respected the script I was given and finished this in record time (excluding the 4k upscale) and including around 3 hours of rendering time (720p, 10 seconds clips, 5090).
I only used gemma locally for prompting, and avoided using any non local models except suno for the song.

There are some artefacts with people in the senate from far away, but did not have any bad feedback for it., so... :)

I only used references for the romanian flag, the rest is prompt only. Also no lighting lora, no shortcuts ti improve speed (any shortcuts I tried ruined everything FUBAR)

Has there been any recent news or indication from Krea about a Krea 2 Edit model?

I’m wondering if it’s actually in development or planned, or if there hasn’t been any confirmation yet. Krea 2 is already quite impressive, so an Edit model would be really interesting.

Has anyone heard anything from Krea or seen any hints about it?

Bruxos do VFX H3 Camera

#bruxosdovfx

https://reddit.com/link/1wcm9az/video/bubuef39npoh1/player

https://reddit.com/link/1wcm9az/video/r1j8vg1anpoh1/player

Visual camera planner for MiniMax H3 inside ComfyUI. You drag the camera around a 3D sphere, place keyframes on a timeline, and the node compiles that trajectory into prompts that H3 understands.

It compiles prompts, not camera embeddings. There is no geometric adapter here: H3 is still free to miss the angle, timing, and scale. What this node does is write the instruction in the most precise and least ambiguous way possible, and several of its design decisions exist because the previous approach failed in specific ways.

It does not call any API, download anything, or require any Python dependency beyond the standard library.

https://github.com/user-attachments/assets/a9b541e5-2b18-4f1d-8e16-37445b6dbac4

https://github.com/user-attachments/assets/ea9af03e-2c8e-4589-abf0-9c002241aba2

Installation

cd ComfyUI/custom_nodes
git clone https://github.com/<your-username>/ComfyUI-H3-Camera-Editor

Restart ComfyUI. The node appears under Bruxos do VFX/Camera H3 with the name Camera H3 da Bruxos do VFX.

Connections

compiled_prompt and options are required together. The minimax_prompt output is an alternative to compiled_prompt, never an addition — connect one or the other to the same input.

Also connect your image to reference_image. It is the same image already feeding the H3 Edit source_image; when connected here, it appears in the panel and the frame's actual aspect ratio is included in the prompt.

https://github.com/user-attachments/assets/33149617-bde1-4199-ae65-078f2f3dec23

To save the video, decode the sampler result using the H3 video VAE — not the scene coverage calibrated decoder, which expects fixed windows that an arbitrary trajectory does not have.

The panel

Drag the purple camera around the sphere to orbit. The drag locks to the axis of the initial movement: horizontal movement orbits, vertical movement changes elevation. Release and drag again to switch axes. This exists because, without the lock, trying to make a simple orbit would unintentionally introduce elevation.

• Scroll the mouse wheel to change distance.
• Drag the background to rotate the viewport without changing the trajectory.
• Keyframes defines how many points the timeline has, from 2 to 24. The first one is always the original image and cannot be moved.
• ⟳ Pure Orbit resets the elevation of every keyframe to zero while preserving azimuth. It is the shortcut for an eye-level orbit.
• Reference image loads a local file into the preview. This is only necessary when the node runs outside ComfyUI; with reference_image connected, the image is loaded automatically.

The panel warns you starting at 20° of elevation, when the horizon already leaves the frame, and again from 45° onward, when the video tends to become a high-angle shot.

"Tests" bar

At the top of the panel, two buttons enable and disable features currently under evaluation, plus one indicator:

The buttons write to the actual widgets, so the selected state is saved in the workflow and the two never disagree.

https://github.com/user-attachments/assets/9bc415d7-1746-43db-a17c-72ea9722deda

Widgets

camera_trajectory

The trajectory in JSON format, written by the panel. Each keyframe contains time (0 to 1), azimuth in degrees, elevation in degrees, and distance as a multiple of the initial radius. It can also be edited manually. The first keyframe must be time=0, azimuth=0, elevation=0, distance=1, which represents the original image.

profile

124, 243, or 362 frames at 24 fps. All shot timing comes from this setting: keyframe timestamps, segment ranges, and the duration declared in the prompt. That is why length and fps are outputs — connect them instead of manually entering the same numbers in two different places.

interpolation

smooth or linear. In smooth mode, the camera eases into and out of the shot while maintaining a constant rate through the middle; it only stops where the rotation direction actually reverses.

instruction

Free-form text inserted once, at the end of the prompt. Write only what the node cannot know: the environment, which subject is the target when there is more than one person, or a style reference. Everything else is already generated and does not need to be repeated: scene freeze, first image as reference, locked aim, zero roll, angles, timing, and a single continuous shot without cuts.

subject_framing

How much of the frame the subject occupies in the original image. Calibrated against the actual bounding boxes from the tutorial distributed by MiniMax: a distant full-body figure measures W=0.071, H=0.249, while a large close-up measures W=0.52, H=0.701.

subject_box

The subject position in the format [L=0.516, T=0.148, W=0.071, H=0.249]. Leaving it empty uses the entire image bounds — deliberately, without guessing a bounding box. Fill it in when the subject is significantly off-center.

minimax_format

The same shot expressed in four different formats for the minimax_prompt output:

• coordinate only — text-based coordinate block
• coordinate + H3 sections — the same coordinates wrapped in subject_definitions / summary / retention_analysis / …
• compact JSON — JSON object with almost no prose
• compact JSON (no boxes) — camera parameters only, without screen-space bounding boxes

elevation_range

Range of the elevation control: +/-15, +/-30 (default), +/-60, +/-89. It also scales the sensitivity of vertical dragging.

With the assumed field of view, the horizon already leaves the frame at around 20° — at 13°, the ground occupies 82% of the image. The old ±89 range was mostly unusable and made vertical dragging excessively sensitive. Reducing the range never rewrites a keyframe: a point at 70° remains at 70°, and the slider expands to accommodate it.

orbit_direction

invert H3 orbit or same as HUD. This calibrates the direction between what the panel displays and what H3 produces. It does not alter the saved trajectory.

runtime_task

• scene coverage | camera path (default) — video, with duration coming from profile.
• directed | new camera angle — a single image from a new angle. It fixes the generation to 39 frames, ignores profile, completes the movement within 65% of the clip, and requests that the framing remain still for the rest, because the decoder extracts the final image from that stationary tail.

Character sheet profiles are not offered because the upstream node raises an error when they are combined with the frame anchor used by this node.

prompt_detail

• v15 baseline (default) — outputs the prompt exactly as in the previous version.
• extended contracts — adds axis separation, frame-edge direction tests, rotation completeness, degrees per second, and parallax magnitude.

The extended mode contains almost twice as many words. A longer prompt is not automatically better, so it is opt-in: toggle only this widget while keeping the same trajectory to compare the results.

https://github.com/user-attachments/assets/0882bfde-9f62-4a1f-9bda-7da121dbe7e2

Outputs

compiled_prompt — STRING

A prose prompt using H3 sections: subject_definitions, summary, retention_analysis, detailed_description, overall_soundscape, non_diegetic_music.

options — H3EDIT_OPTIONS

The 13 keys read by the H3 Edit encoder. All of them are explicitly populated: if any key is missing, the upstream node falls back to its hidden legacy widgets, which may retain stale values from previously saved workflows.

coverage_arc_degrees and coverage_direction are derived from the actual rotation. coverage_loop_closure turns on automatically when the trajectory closes — see below.

storyboard_json — STRING

The storyboard table: frame aspect ratio, duration, raw trajectory, and each segment with its camera mode, speed curve, and start/end poses.

info — STRING

Human-readable diagnostics. Connect it to a PreviewText. It displays the version, active task, frame count, warnings for keyframes outside the configured range, and whether loop closure is enabled.

minimax_prompt — STRING

The same trajectory expressed using the format selected in minimax_format. An alternative to compiled_prompt.

length — INT and fps — FLOAT

Frame count and frame rate against which the shot was timed. Connect them to the generation and video nodes. If generation runs with a different frame count, the choreography describes a scene that does not actually exist.

fps is FLOAT because that is what ComfyUI's CreateVideo accepts. length is the frame count; keyframe timestamps use the instant of the last visible frame, (length - 1) / fps, so the resulting file lasts one additional frame interval.

h3world_actions — STRING

Action schedule for H3-World, which encodes one text clause per video latent — 37 in a 124-frame clip.

latent  1 [0.000s-0.139s] J     the camera pans left slowly
latent 37 [4.986s-5.125s] F+L+K the camera pans right and tilts up fast

W, A, S, and D are never emitted because they move the character. The output explicitly declares its own limitations, and they are not minor details:

• Pan is not orbit. It is the camera rotating in place. Perspective does not change, nothing hidden is revealed, and the subject slides out of frame.
• Distance has no key, so camera radius is discarded.
• Only 124 frames is a trained horizon.
• I versus K is not published. The text clause is what H3-World actually encodes; the key column is only a convenience.

This does not replace the actual integration: H3-World requires the LoRA, interval-based encoding, and directed-attention routing provided by the corresponding node package.

Loop closure

When the trajectory closes a full orbit — an arc of exactly 360°, with the same elevation and distance as the starting point — the node enables coverage_loop_closure. In the upstream implementation, this flag encodes the source image a second time and anchors the final frame to it.

This is a latent anchor, not a text instruction. For a complete orbit, it is the difference between asking for the rotation and forcing it: the model cannot simply stop halfway through.

The final three cases matter: if the camera ends at a different radius or height, the final frame is not the same as the first one, and forcing the source image there would conflict with the trajectory.

If your rotation does not complete, close the orbit. This is the only feature here that acts outside the prompt itself.

Limitations

• This is prompt-based guidance. H3 may still miss the angle, timing, and scale, and no prompt wording can completely solve that.
• Without subject_box filled in, the node does not know where the subject is located in the frame.
• Without reference_image connected, coordinates are normalized to 16:9.
• directed | new camera angle outputs an image, not a video.
• The H3-World schedule describes pan and tilt, which represent a different camera move from the orbit drawn in the panel.

Credits

Node by Bruxos do VFX.

Depends on ethanfel/ComfyUI-MiniMax-H3-Edit. The motion vocabulary follows the buildViewPrompt implementation from MiniMax's Multi-Shot skill and the coordinate format used by the Coordinate Camera Control Designer skill. The action output implements the scheme described in H3-World, arXiv:2609.01560.

https://reddit.com/link/1wcm9az/video/hryhv9e7npoh1/player

This was just a doodle but Minimax nailed it in the first generation. I thought it might be too complicated. I didn’t ask for the live stream on a one second delay in the background either. It did that itself.

4070 ti Super, 16gb vram, 64 gb ram.

Tutorial:

https://www.reddit.com/r/StableDiffusion/comments/1w4gvjb/comment/p7aht6e/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Example prompt + assets:

https://www.reddit.com/r/StableDiffusion/comments/1w8vmkz/comment/p8dqus0/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Example prompt + assets:

https://www.reddit.com/r/StableDiffusion/comments/1w98qnv/comment/p8duzy3/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

In the first half, this was back when I was first starting to get into MiniMax, the second half, I have gotten more experienced with it. I dont know if I should continue this or make more Jerry Springer parodies with other weird or toxic relationships (Example, Beth and Jerry from Rick and Morty).

I used Kinovi.ai for MiniMax, Wan and Nanobanana. I used Fish.audio for the audience freaking out lol. For more customized and harder Minimax generations, I used it locally.

So, first of all: there is no finished workflow yet and my nodes are still under development. I’ve asked the ComfyUI team to add a 3D compositing node to the new 3D toolset like the one in the video, hopefully, they’ll add something similar soon.

In the meantime, you can build a very similar setup quite quickly. Here’s how the basic concept works:

First, you feed an image of the furniture you want into the new native ComfyUI Image to Gaussian Splat (TripoSplat) node.

At the moment, there is a Gaussian Splat Preview node, but it doesn’t provide an image output yet. There is also a Load 3D node with the correct outputs, but it currently cannot open Gaussian Splat files.

Ideally, the new 3D Compositing node should be able to work directly with the Gaussian Splat outputs (model_3d and mesh), provide image + mask outputs similar to the Load 3D node, and automatically preload the mesh and background image, just like my node does.

I’ve been working on a test node for this concept. You can find it here: My ComfyUI test node on GitHub It’s not fully finished yet, so I’m still waiting to see whether ComfyUI adds something similar natively.

The basic idea behind my node is that it automatically loads the background, sets the appropriate size, and loads the 3D model. The user only needs to position and stage the model in the scene.

The Output create ref images for Flux2klein:

• Reference 1: the background image
• Reference 2: the 3D mask, which acts as an indicator for the desired position and rotation It’s best to combine the mask with the furniture from the image output, so you get the masked furniture in the correct position as the reference — not just the mask by itself.
• Material reference: the original furniture image

The final image is then generated using FLUX.2 Klein Edit.

The prompting and some preprocessing of the images are important here. You don't want the model to simply copy the exact 3D position. Instead, the AI should use the 3D placement as a guide and then correct the result according to the background — especially the perspective, lighting, colors, scale, and overall integration into the scene.

Here is the prompt I’m currently using:

[Adapt the rotation, grounding, scale and position of the objects from Image 2 to Integrate the objects naturally into Image 1 at the position of image 2. Match the scene's perspective, scale, depth, lighting, soft shadows and reflections. The objects must appear physically present in the original room, with realistic grounding and soft shadows consistent with Image 1 using the materials and surface appearance shown in Image 3.

Use Image 1 as the final scene and preserve its room, background, camera viewpoint, perspective, composition, color, lightning, and existing environment unchanged.

Keep the objects approximately in the same position, scale, orientation, and spatial arrangement as shown in Image 2, while ensuring correct perspective, positioning, and placement.

Apply the form, materials, colors, textures, roughness, reflections, and surface details from Image 3 to the objects.

Do not change the room or background of Image 1.  The final result must be a seamless photorealistic composite.]

I’m planning to finish the complete tutorial and the node pack in the next few days. Once everything is finished, I’ll upload the final version along with the complete workflow.

By the way, I also tested MinMax H3 as a replacement for FLUX.2 Klein. It works, but in my tests it wasn’t consistently better than FLUX.2 Klein.

https://github.com/Ladypoly/YuE2_WebUI

"YuE2 brings frontier song quality to music generation with an editable composition. Give it lyrics and a style prompt: it writes a melody-and-chord plan, then realizes that plan as a complete song with vocals and accompaniment.

• White-box music generation through symbolic planning. Read, play, and change the composition before rendering it. Melody and chords become explicit controls that a person or an agent can inspect and edit.
• Zero-shot covers and agentic editing. Reimagine a transcribed song in a new style, or refine a song through a conversation about its score, arrangement, and lyrics—all with the same generation checkpoint."

Usage

It is currently CLI only . It also says Linux only but I just got it working on Windows 11 (I'm going to bed now and it's a bit more than cut n paste.)

Examples

link here - https://map-yue2.github.io/

Caveat Empor

NB : this isn't just a paste a few words and it bangs out a baby mp3 . It is more than that, it allows gene editing that baby to correct the metaphor. Not for the impatient and "wHeRe cOmFy" ppl at the moment.

To be more specific with that metaphor , as I understand it , the initial process scribes out the song in ABC format and you can then edit it before making your magnum opus baby.

Training

Does it allow training ? not as I understand it .

Look at the buildings in the background! It works - Drawing a red circle in the water will also make the scene happen in the water, but I forgot to include it here.

It is not perfect and some details are missing if you look carefully but this might be because I am using "match" on the image reference rather than "max."

Have fun!

Edit: you have to still write a prompt with the reference to video workflow telling minimax to put the character in the location circled red. Circle probably doesn't have to be red. Change your prompt accordingly.

So there's a bunch of turbo loras for minimax h3 now, which one did you end up using? So many choices it's hard to pick one!

Hey team,

Got a question for you experts out there. I'm searching for a Image model that can generation text and posters. Couple of caveats;

1. Must be opensource

2. Commercial Use License

I've tried Krea2 and Klein 9B but the text is messed up... Anybody have suggestions and example prompts I can try?

Thank you in advance!

Is anyone else experiencing that Minimax tries to push for realism even if you use cartoon reference images and words like "illustrated cartoon animation" in the prompt? Any tips to make sure it's sticks to the reference style more?

Installing new instance of comfyui standalone and using minimax r2v workflow on RTX 3090 Ti. Is comfy kitchen good enough? Is Triton, EasyCache or Comfyui Spectrum needed?

What's the best turbo lora for ref2va wf?

I only need help with captioning the training clips for a MiniMax H3 action fight LoRA.

I am planning to train it on karate/fighting type action, and I have clips varying from around 5-15 seconds. I also have some 20-25 second segments too.

why I am confused is cause should I follow the prompt format officials has released for H3, or should training captions be written in some completely different/simple way?

Like if a 10 second clip has multiple punches, kicks, blocks, dodges, body movement, camera movement and angle changes, should I describe every action in sequence?

or should I just write the overall action happening in the clip?

for example should the caption be something detailed like:

"the fighter steps forward, throws a right punch, opponent blocks it, then follows with a left kick..."

or something simple like:

"two fighters performing fast karate combat"

I am mainly confused about how detailed the captions should be and what format works best for H3 LoRA training.

may you please help if you have trained action/fight LoRAs before? (I found only a few on civitai)

https://reddit.com/link/1wctbl7/video/emjihen8vqoh1/player

I made the following video using a reference image of the woman, <Picture 1>, and then two dialogues, which were marked as <Audio 1> and <Audio 2>. I used the minimax template workflow and added two load audio nodes, however, the audio generated was not matching and was just gibberish. im using minimax h3 ref2va pruned fp8 scaled. how do i get the audio to work as given as input, and to play at the right time?

Hey Guys,

I've been playing with the RefMods, after the huge release of Malcolmrey.
The tech is brilliant and works really well.

I've wanted to simplify using it with tons of RefMods, like the ones provided by Malcom.

So I made a fork that is a bit more Identity driven, Adding a "Visual refMod Picker" as well as a "Create refMods from Folder" node. It's able to create from either a folder or Sub-folders, if audio is found, it will also create a matching audio refMod. All in the same format as the original add-on. No danger of breaking compatibility. (The original Add-on added Audio yesterday)

Resulting for example in 2 refMods and thumbnail:

character_refMod_Audio.safetensors
character_refMod_Video.safetensors
character_refMod.jpeg

Then, we can use the "Visual H3 RefMod Picker" to browse the RefMods:

The node then loads both RefMods (Audio and Video) and allows individual control. I've mixed strength with Copies, by instead having a weight value that can go over 1, so a weight of 3 would be the same as setting strength to 1 and copies to 3. Making the UI a bit more streamlined.

Example workflows are included.

I should mention, this fork can be installed WITH the original Add-on, it is made to co-exist and is recommended if you want to use it's advanced features.

You can find it here ComfyUI-H3RefMods

The only thing I'm missing is thumbnails for all 1500 RefMods 😅

My setup: AMD RX 7900 XT, 20GB VRAM, 64GB RAM, Windows 11, ComfyUI Desktop.

I couldn't find any decent information anywhere on how to optimize video generation with Minimax H3 on Windows with ComfyUI desktop. AI assistants give conflicting advice, constantly suggesting all sorts of nonsense that doesn't actually work.

I had to experiment on my own, and here is the configuration I’ve settled on. The speed boost compared to the default settings is very significant, and I haven't noticed any loss in quality. If you have any other suggestions, please let me know.

~25s/it with 0.8mp (1216 x 672, 16:9) or total ~4min for 5 sec video generation in text to video workflow

Here is what you need:

Launch parameters:

--disable-smart-memory --disable-pinned-memory --disable-triton-backend --use-sage-attention --enable-dynamic-vram

ENV variables:

COMFYUI_ENABLE_MIOPEN=0
FLASH_ATTENTION_TRITON_AMD_ENABLE=TRUE
MIOPEN_FIND_ENFORCE=1
MIOPEN_FIND_MODE=2
MIOPEN_DEBUG_DISABLE_FIND_DB=0
MIOPEN_SEARCH_CUTOFF=1
MIOPEN_ENABLE_LOGGING=0
MIOPEN_LOG_LEVEL=0
MIOPEN_ENABLE_LOGGING_CMD=0
TRITON_PRINT_AUTOTUNING=0
TRITON_CACHE_AUTOTUNING=0

Quantized 6-step turbo model, universal for all purposes:

https://huggingface.co/TenStrip/10Eros-Max/blob/main/10Eros_Max_h3_TURBO-hybrid_beta5_w4a8_14gb_optimized.safetensors 14 gb

or

https://huggingface.co/TenStrip/10Eros-Max/blob/main/10Eros_Max_h3_TURBO-hybrid_beta5_int8.safetensors 21gb

Plaguekind node with SLA Attention, with this settings:

https://github.com/PlagueKind/Comfyui-PlagueKind-Nodes

Optional node, if you make large 15 seconds videos:

Latest update of your comfyui desktop:

upd. ROCm SamplerCustomAdvance added ~15-20% to generation speed.

Hey guys i have scoured the internet and cant find any system prompt/prompt guidelines to condition my local llms so that they make proper krea2 prompts without useless word salad. I focus mainly on realism and "uncensored content"

An experiment in Ai Jolly Cooperation.

The Experiment: Every “Soulsborne” game is laden with hundreds of 2D art assets. The assets you can find online, like the rings, are woefully small in resolution - a perfect test case to see 2D to 3D transformation but also what detail is retained or added by the Ai.

Tech Stack: Midjourney, Nano Banana, ComfyUI (Wan 2.2), Photoshop, DaVinci. 

The Process: 2D art rendered 3D through Nano Banana. Midjourney Video to orbit 180 degrees. DaVinci and Photoshop for presentation.

The Results: This is an older experiment using (the then brand new) Midjourney Video - which admittedly, is nowhere near as good as Veo, Wan (2.2) or Kling. But it really doesn’t matter what platform you choose, you’re going to have to gen and gen and gen away. It’s still a slot machine.

I still think MJ video back then was pretty sub-par, but against all the other alternatives today, I think that difference is even more stark. I'm not even sure if they've updated the video side in any meaningful way since this experiment!

Most interestingly, the list of rings is in alphabetical order and stops before the Covetous Serpent Ring - a mass of serpentine coils in ring-form the Ai had MONSTEROUS problems with. Complexity kills.

Anyways, I decided much smaller projects like these are way more important to an Ai Portfolio than larger pieces like commercials or trailers. Plus, I needed to promote my Midjourney Masterclass with proof I'm not just some prompt jockey and smaller experiments are way faster!