H3-Metal: antirez's native C/Metal port of MiniMax's H3 video model for Apple Silicon

The most striking part of h3.c's launch isn't the code itself, it's who's cheering for it. MiniMax, the company that trained and owns the underlying H3 model, used its own official X account to publicly praise antirez's unofficial port, calling him one of the best programmers on Earth and framing the whole episode as proof that open weights mean 'anyone can bring H3 to any hardware.' That's not a routine developer-relations post, it's a model vendor conceding that a single outside contributor built the Apple Silicon story it hadn't built itself.

The reaction on X reinforced that framing. The dominant narrative among commentators, especially in Chinese-language posts responding to the release, was that h3.c is 'not a wrapper, written from scratch' - pure C plus Metal shaders, with no Python, no PyTorch, and no ComfyUI dependency chain. That distinction matters to the audience it's aimed at: people who had been running H3 through heavier Python/ComfyUI stacks on Mac hardware and hitting friction. The project also incorporated code from liuliu, creator of the Draw Things app, with antirez explicitly inviting him to take back whatever pieces are useful for Draw Things's own H3 plans - a small but telling sign of how thin and informally connected the pool of people building serious native Apple Silicon AI tooling actually is.

h3.c's real engineering contribution is a set of three tunable tradeoffs layered on top of the base H3 architecture. Layer reduction drops the number of active transformer blocks from the model's full 50 down to 45 or 40, denoising-step reuse cuts the number of fresh DiT (diffusion transformer) evaluations from 20 steps down to 11 or 8, and SSD streaming keeps just two DiT blocks resident in memory while reading the rest from disk, shrinking the model's storage footprint from roughly 36.5 GiB down to 2.0-2.1 GiB at 512x512 resolution ^[1].

Each lever has a documented cost. SSD streaming's memory savings come with a 26-84% performance overhead, and on an M5 Max the same 512x512/22-frame/20-step generation ranges from about 16.69 seconds by default down to roughly 6.47 seconds under the aggressive 40-layer/3x-reuse configuration, or as fast as 3.5 seconds for a stripped-down 4-step render ^[1]. That spread turns h3.c into less a single benchmark number and more a dial: users on memory-constrained Macs can trade fidelity and time for the ability to run a 33-billion-parameter omni-modal model at all, while users with more headroom can push for speed.

There's a real tension buried in this release that the enthusiasm mostly glossed over. MiniMax's H3 license reportedly excludes local deployment in the United States, the European Union, the United Kingdom, and South Korea, and separately imposes attribution requirements, a $20 million yearly revenue ceiling before separate authorization is required, and a ban on distillation ^[3]. antirez's h3.c, by contrast, is released under a permissive MIT license with no such geographic gate, meaning the tool that makes local, cloud-free H3 execution trivial is now freely available in exactly the markets where running the underlying model locally is restricted by MiniMax's own terms ^[3].

That gap isn't a bug in h3.c so much as a structural mismatch between how open-weights releases are licensed and how independent tooling built on top of those weights actually gets distributed. Nothing in a permissively licensed inference engine enforces a model vendor's separate usage restrictions, and h3.c's popularity is itself evidence of how little practical friction that mismatch creates for end users.

For all the excitement, Hacker News skeptics pushed back on treating h3.c as a genuine leapfrog over dedicated GPU hardware. embedding-shape argued that diffusion-model video generation is fundamentally compute-bound, which structurally disadvantages Macs relative to NVIDIA GPUs no matter how well-optimized the software layer is ^[2]. Real-world numbers backed that up: one commenter reported a 128GB M4 Max Mac Studio taking roughly 90 minutes to generate a 15-second 480p video via MiniMax H3 in ComfyUI, versus 2-3 minutes on an RTX Pro 6000 ^[2].

Other commenters flagged rougher edges beyond raw speed - thehamkercat wanted clearer benchmark methodology given how many variables (mode, resolution, duration) shift the numbers, and separate community reports describe model load failures on 8-16GB Macs due to unified memory limits, Metal shader compile failures on older Xcode/macOS Sonoma builds, and segfaults when the binary runs under Rosetta 2 rather than natively ^[4]. h3.c narrows the gap for Mac users who have no GPU alternative and closes the Python/ComfyUI tooling gap specifically, but it doesn't erase the underlying hardware disadvantage for compute-bound diffusion workloads.