MiniMax H3 Legacy 0.4 Policy Adapter
Migrate a 0.4 Plan to 0.5 without re-deciding your audio
- chain_policy
- chain_policy
- status
Version 0.5 split the old single audio mode into three independent axes (final audio, source reference, generated continuity) plus an exact-target lock. If you're dragging a saved 0.4 workflow into the new world, this adapter is the bridge: it takes the legacy combined settings and translates them into the modern one-wire policy, so you don't have to re-derive your audio intent by hand. It's migration plumbing, not something you reach for in new graphs.
What it does
The adapter eats the four settings that used to live on the 0.4 Plan node:
- audio_mode -
source_track,generated_audio, orsource_plus_timeline. When a modernchain_policyis connected, this widget is ignored and the modern audio intent wins. - continuation_mode - the raw low-level implementation (guide, tone_carry_guide, latent_guide, masked_av, tapered_av, feathered_av, drift_control_av, color_stable_drift_av, and friends).
- context_length - the old global visual overlap (1, 5, 22, 39…).
- audio_context_length - the generated-audio overlap in 24 fps frames.
Its single output is a chain_policy - one wire carrying all the translated settings - plus a human-readable status summary so you can verify the translation did what you expected.
The exact mapping is: source_track → final=source, source reference=on, generated continuity=off; generated_audio → final=generated, source reference=off, generated continuity=on; source_plus_timeline → final=source, both on. If you're migrating a workflow and want the old behavior preserved precisely, that's what you're getting.
The optional chain_policy input is worth understanding: connect a modern Chain Policy and the adapter only overrides the raw 0.4 boundary fields while preserving the complete modern audio record. Standalone, it owns audio intent itself. Either way, the policy layer nearest Plan wins.
Install and gotchas
cd ComfyUI/custom_nodes
git clone https://github.com/ethanfel/ComfyUI-MiniMaxH3-Contex-Loop.git
Restart, or install via ComfyUI Manager under "MiniMax H3 Contex Loop". No pip dependencies; needs a current ComfyUI with native Add Guide (PR #15439). Models aren't bundled - see the MiniMax H3 Community License for the territory restriction.
The advice from the pack itself is blunt: new workflows should use Chain Policy and, when needed, Advanced Policy Override. Use this adapter only for a genuine 0.4 import, a raw implementation/context pair, or an independent numeric audio overlap. It's a compatibility shim, not a design goal.
Inputs (5)
| Name | Type | Default | Description |
|---|---|---|---|
| audio_mode | COMBO | generated_audio | Legacy 0.4 combined audio mode. The adapter translates it exactly into the independent 0.5 Audio Policy axes only when chain_policy is disconnected. A connected modern policy owns audio intent instead. |
| continuation_mode | COMBO | guide | Legacy 0.4 low-level continuation implementation. Prefer Chain Policy plus Advanced Policy for new workflows. |
| context_length | COMBO | 22 | Legacy 0.4 global visual overlap. This is paired with continuation_mode and translated into the one-wire 0.5 policy. |
| audio_context_length | INT | 220–240 | Legacy 0.4 generated-audio overlap in 24-fps video-frame units. Guide can use this independently of visual context. AV treats zero as disabled and any positive value as enabled for the exact shared video boundary. |
| chain_policyopt | H3_CHAIN_POLICY | Optional policy layer to preserve. When connected, its complete 0.5 audio intent is kept and the legacy audio_mode widget is ignored; only the raw 0.4 transition and audio-context fields override it. Leave this disconnected only when migrating a standalone 0.4 policy. |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| chain_policy | H3_CHAIN_POLICY | One-wire combined policy carrying all translated legacy settings. |
| status | STRING | Human-readable summary of the translated legacy settings. |