DucHaiten Highway V1 — INT8 Video + Audio

⚠️ READ THE SETUP GUIDE FIRST — THIS MODEL REQUIRES THE HIGHWAY INTEGRATION

Highway V1 will not run with standard MiniMax H3 loaders. You must install the Highway ComfyUI integration and use the supplied workflows. Follow the setup guide before clicking Generate.

→ Open the setup guide and follow every step

Hey everyone! Meet Highway V1, my INT8 video-and-audio model built on MiniMax H3. Create from a text prompt, guide scenes with multiple reference images, or connect first and last frames using one Highway checkpoint. I’m excited to share it with you.

In my evaluated comparisons, Highway’s native C20 schedule (20 evaluations) matched the quality of MiniMax H3 at 50 steps.

I built Highway on MiniMax H3 through DaSiWa Hybrid v2 INT8, with its own saved generation policy and resource management. Text-only, multiple references and first/last-frame control use one Highway checkpoint. You can see the actual videos, prompts and reference images on my HF page.

✦ What changes from MiniMax H3?

Comparison MiniMax H3 Highway V1 INT8 Quality in my evaluated comparisons 50-step reference Matched at 20 evaluations Published / demonstrated resolution Released recipe targets a 768-pixel short edge 1344×768, 1792×1024 and 2688×1536 demonstrated Checkpoint coverage FL2VA and Ref2VA partitions One checkpoint tested across text, image references and first/last frames Generation controls Configurable sampling recipes Native C20 policy saved with Highway; no Steps slider to configure

Quality is my visual assessment; the other rows compare the published H3 recipe with my demonstrations. That 768p target is not H3’s proven maximum. A normal H3 sampler set to 20 steps does not reproduce Highway’s policy.

⚡ The 15-second case: reported OOM → a completed Highway video

At 1344×768 / 362 frames on RTX 4090, the H3 INT8 community guide by yume-arasaki reports OOM. Highway’s demonstration at those dimensions and frame count completed with four image references and stereo audio.

1344×768 · 362 frames Reported H3 INT8 setup Highway V1 INT8 — my run Outcome Author-reported OOM Completed · 15.08 seconds · four references Full request time No completed result reported for this case 24m 33.58s Host configuration 32 GB RAM; 8-step res_multistep; NVFP4 encoder 128 GB RAM; native C20; BF16 layer-50 encoder

Reported OOM in that community setup; completed in mine. Software, conditioning and host RAM differ, and the source supplies no matching allocation log. This eight-step report provides OOM context only; it is excluded from original-H3 speed/memory comparisons.

✓ Five completed runs — here are my timings and memory figures

RTX 4090 · INT8 · 24 fps · 32 kHz stereo audio. Full request time includes preparation, generation and output work.

Input Output Full request Peak process RAM¹ Worker GPU memory² allocated / reserved Text only 1344×768 · 5.17s 5m 59.34s 29.81 GiB 3.31 / 3.78 GiB Four references 1344×768 · 5.17s 8m 44.24s 31.11 GiB 3.81 / 4.41 GiB Four references 1344×768 · 15.08s 24m 33.58s 34.00 GiB 7.36 / 9.72 GiB First + last frames 1792×1024 · 5.17s 11m 11.34s 32.58 GiB 4.97 / 6.62 GiB Text only 2688×1536 · 5.17s 32m 52.19s 36.29 GiB 9.03 / 11.97 GiB

¹ RAM covers Highway’s recorded process tree, excluding unrelated apps; shared resident pages can be counted more than once.

² These VRAM figures cover the generation worker’s PyTorch allocator, not total Highway GPU memory. They exclude the separate reference reader and allocations outside that allocator. Reserved includes allocated; do not add them. These are observed peaks, not minimum hardware requirements.

Full timings, historical builds and memory definitions are on HF. Matching original-H3 measurements are unavailable for these five runs, so I’m showing measured usage rather than a claimed saving percentage.

2688×1536 is four times the pixel count of 1344×768 — generated directly. I pushed that setting for the showcase; motion can look strained there. Start at 1344×768. For higher-resolution experiments, I’d try 2560×1440; that setting is a suggestion, not a measured row above.

I used quickly drafted test prompts. Watch the outputs and judge for yourself — there’s also compatible LoRA inference through the supplied controls.

◇ Why Civitai says “Merge” and “H3”

These are Civitai’s available labels. “Merge” means integrating Highway V1’s architecture and saved policy into this H3-derived model, not blending several checkpoints’ learned knowledge. “H3” identifies its lineage, not standard-loader compatibility.

⚙ Before you hit Generate

Use the Highway ComfyUI integration and supplied workflows. Standard H3/generic checkpoint loaders will not run it; a workflow JSON alone does not install the software.

1. Download the RC.3.7 integration ZIP and extract it.

2. Close ComfyUI, run INSTALL_WINDOWS.bat, and select your ComfyUI folder if asked.

3. Restart ComfyUI and drag in 01 - Start Here.json.

4. Click Prepare / download models on Asset Profile. Let it verify/reuse existing files or download what’s missing, then enter your prompt and run.

The setup uses the RC.3.1 Safetensors checkpoint, matching runtime, Qwen encoder and video/audio VAEs. Required model files total 78.30 GB on disk, plus software/caches/outputs. Optional automatic-reference assistance adds 8.89 GB; basic references work without it. Highway downloads are open on HF; any access requirements for separately hosted components still apply. Unused reference upload slots can stay connected in RC.3.7.

→ Get Highway V1 and show me what you make

Highway V1 on Hugging Face → · Installation guide

The source/component terms still apply; keep the included notices. This is my project, not an official MiniMax release.

I’d love to see your results! If you hit an error, include your setup and the message so it’s easier to help.