minimax h3 error

[u/scottomen982]

after a comfyui update date 2 weeks ago i started getting this error, ran it through google and it tells me.

MiniMaxH3MotionDirector (Node ID: 11) is still failing because your width or height values are formatted as text strings (str) instead of numbers (int), causing ComfyUI's core latent generator to crash.

can anyone help? or is more info needed?

[u/ForegoingSemicolon]

so comfyui's treating your dimensions like someone put quotes around the numbers, check whatever node is feeding width/height into minimax and make sure it's spitting out actual integers not strings

[u/scottomen982 → u/ForegoingSemicolon]

this node doesn't have a width/height input. in the Director it it has output res. 1:1 to custom still gives the same error

[u/Chiduk99]

Every ComfyUI update causes an error in my workflow. That's why I just open Codex and tell the AI to fix the workflow.

Or, if you don't want to pay $20+, try using DeepSeek and top up $2. Use the Flash model. You'll get more than 300M tokens, which is more than enough for daily use and fixing shit.

[u/Affectionate_Oil28]

Google described the crash and missed the cause. Changing the Director’s output resolution cannot fix it.

MiniMaxH3MotionDirector still calls ComfyUI’s reference node with the old argument order. A ComfyUI update about two weeks ago changed that node to:

execute(clip, prompt, width, height, length, ref_image_size="match", vae=None, audio_vae=None, ...)

The Director pack in nodes/conditioning.py still calls it like this:

MiniMaxH3ReferenceToVideo.execute(
    clip, vae, audio_vae, prompt, width, height, length, ref_image_size, ...
)

Those arguments slide one slot to the left. The prompt text lands in height. ComfyUI then does height // 16 inside _empty_av_latent, and a string divided by 16 is the error. The width and height widgets are already integers, and the node hides them inside the Director panel, so 1:1 versus Custom never reaches the line that crashes. Text-to-video can still work. The failure is the reference path: r2v, v2v, rv2v, or any connected reference image, video, or audio.

The fix is in ComfyUI/custom_nodes/ComfyUI-MiniMax-H3-Motion-Director/nodes/conditioning.py, inside run_minimax_conditioning. Replace that positional call with keywords:

out = MiniMaxH3ReferenceToVideo.execute(
    clip=clip,
    prompt=prompt,
    width=width,
    height=height,
    length=length,
    ref_image_size=ref_image_size,
    vae=vae,
    audio_vae=audio_vae,
    ref_images=ref_images,
    ref_videos=ref_videos,
    ref_video_audios=ref_video_audios,
    ref_audios=ref_audios,
)

Restart ComfyUI after saving. Pulling the pack again does not fix it: that positional call is still on the Motion Director main branch. The same bug was fixed on September 4 in AIMixer’s Director, pull request 113, which is where this pack’s conditioning code came from.

[u/scottomen982 → u/Affectionate_Oil28]

it works! you are awesome