H3-metal – Native MiniMax-H3 inference for Apple Silicon
1–10 of 108 posts
Re: H3-metal – Native MiniMax-H3 inference for Apple Silicon
#2This still requires 128Gb of memory, right? Me and my lowly 96Gb, like a commoner; missing out on the fun.
Re: H3-metal – Native MiniMax-H3 inference for Apple Silicon
#3This still requires 128Gb of memory, right? Me and my lowly 96Gb, like a commoner; missing out on the fun.
From README:
> On the 128 GB M5 Max, clean end-to-end image+audio and embedded-video+audio renders completed in 74.58 and 76.99 seconds respectively, each with about a 40.1 GB peak physical footprint and zero swaps.
Looks like it uses 40GB? So your 96GB mac setup should work fine i guess (Model itself is 33B)
Re: H3-metal – Native MiniMax-H3 inference for Apple Silicon
#4How similar are Jeff Dean and Salvatore Sanfilippo?
Re: H3-metal – Native MiniMax-H3 inference for Apple Silicon
#5How similar are Jeff Dean and Salvatore Sanfilippo?
My favorite Jeff Dean fact is that he’s also antirez. Which reminds me of my favorite Salvatore Sanfilippo fact. He’s also Jeff Dean
Re: H3-metal – Native MiniMax-H3 inference for Apple Silicon
#6I've been using MiniMax H3 on my M5 Pro 64GB MacBook Pro through ComfyUI. It works extremely well.
I had to modify the default ComfyUI workflows to use a GGUF quant (city96's ComfyUI-GGUF custom node, UnetLoaderGGUF in place of the stock loader) [0].
I use the model labeled Q5_K_M. There is Q8_0 available as well, which is 34GB and fits fine in 64GB unified memory if you keep resolution modest.
The main issue is speed, a ~9-second 480x864 clip at 20 steps takes me a bit over an hour. So this will be cool to try for the speed up alone.
There's a lot of great information and workflows available to follow on the r/StableDiffusion subreddit.
[0] https://huggingface.co/Abiray/MiniMax-H3-GGUF/tree/main/unet
Re: H3-metal – Native MiniMax-H3 inference for Apple Silicon
#7wow antirez does not sleep
Re: H3-metal – Native MiniMax-H3 inference for Apple Silicon
#8This still requires 128Gb of memory, right? Me and my lowly 96Gb, like a commoner; missing out on the fun.
From README: > On the 128 GB M5 Max, clean end-to-end image+audio and embedded-video+audio renders completed in 74.58 and 76.99 seconds respectively, each with about a 40.1 GB peak physical footprint and zero swaps. Looks like it uses 40GB? So your 96GB mac setup should work fine i guess (Model itself is 33B)
This repo looks neat, but I hope they add some more clear benchmarks because that time (74.58s) is pretty meaningless given that the it/s (and total time) is highly dependent on mode (T2V vs I2V vs REF2V), resolution (0.4, 0.6mp, etc), duration (5-15 seconds), etc.
Re: H3-metal – Native MiniMax-H3 inference for Apple Silicon
#9This is where the DGX spark makes up a bit of the ground it loses on llm work, diffusion and cuda go together like peanut butter and jelly.