Home

h3-hip.c wiki

HIP port of antirez/h3.c for AMD GPUs. One tree, two HIP ISAs — pass HIP_ARCH (gfx1151 Strix Halo, gfx90a MI210). The GPU backend is pure HIP so the same MiniMax-H3 CLI and model stack run on ROCm.

Project ident — 864×480, 56 frames, --steps 20 --layers 50 --reuse 1. Click for the MP4.

Project page: alexhegit.github.io/h3-hip.c
Code: alexhegit/h3-hip.c · Release: v0.10.1
Weights: MiniMaxAI/MiniMax-H3
Upstream: antirez/h3.c · CUDA sibling: alexhegit/h3-spark.c

Current tagged line: v0.10.1 (same kernels as v0.10.0).

Where it stands (v0.10.1)

Preset	gfx1151	gfx90a
fox-s2 E2E	83–87 s	~10.5 s
fox-fast E2E	~95 s	~18 s
15 s cinematic E2E	45.0 min	12 min 33 s

gfx1151 fox-s2 md5 is unchanged from v0.9.0: 1731f95c4aa582597cf83d57f46b8f9e. Details: Performance.

Clips generated on gfx1151

Every clip below came out of this HIP build on a Strix Halo iGPU. Click a poster for the MP4. H3 cannot render readable captions, so any on-screen title was added with ffmpeg after generate.

T2VA fox — 512² · 22f · --layers 50 --reuse 1	Linux 35 tribute — 864×480 · 56f · untitled
Ident draft — 512×288 · 56f · untitled	AMD developer community — Ref2VA · 864×480 · untitled

Knobs and full prompts: Showcase. Long T2VA: Long video.

Try it

git clone https://github.com/alexhegit/h3-hip.c.git
cd h3-hip.c
git checkout v0.10.1
make HIP_ARCH=gfx1151 -j$(nproc) h3   # or HIP_ARCH=gfx90a

./h3 --profile -d /path/to/MiniMax-H3 \
  -p "A red fox walks through fresh snow." \
  --width 512 --height 512 --frames 22 \
  --steps 20 --layers 50 --reuse 1 \
  -o outputs/fox.mp4

Full setup: Getting started.

Pages

• Getting started — HIP_ARCH, build, generate, tests
• T2VA pipeline — models and dtypes
• Showcase — gfx1151 clips and reproduce commands
• Long video — 10 s / 15 s cinematic
• Performance — fox-s2 / fox-fast / long T2VA scoreboard
• Known issues — HIP gaps that do not block default T2VA
• CLI — flags that matter on this port

README stays the short front door. This wiki is the longer user guide. Engineering KEEP/REJECT logs stay in-tree under docs/perf/ and are not mirrored here.