Compatibility and Migration

Compatibility and migration

Current runtime

Version 0.5 expects a ComfyUI build with native Add Guide for MiniMax H3 from PR #15439.

Guide, Latent Guide, and Detail Guide prefer that native path. AV-prefix and masked-editing operations use the per-token video/audio mask API merged from PR #15375.

Older supported builds receive scoped compatibility only when the relevant operation executes. Ordinary Guide workflows do not activate AV-mask fallback code.

Coexisting packs

• NikoDemon80's H3 Motion Context pack may be installed beside this one. Public node IDs are distinct.
• Known H3-Multishot payload hooks are retained.
• Known SolAttn layout wrappers are retained.
• Unknown H3 layout or payload wrappers produce a clear error instead of being silently replaced.
• Patch Priority is for a recognized legacy load-order conflict, not a general performance or quality setting.

Moving from 0.4 to 0.5

Opening or resuming a 0.4 workflow does not require migration. Version 0.5 retains node IDs, existing positional input/output order, legacy Plan widgets, manifests, checkpoints, and generic hash fallback.

Migration is recommended because it makes policies and Preflight explicit.

Audio mapping

0.4 mode	Final	Source reference	Generated continuity
generated_audio	Generated	Off	On
source_track	Source	On	Off
source_plus_timeline	Source	On	On

Transition mapping

0.4 setting	0.5 preset
Guide with zero context	Cut
guide	Guide
masked_av	Hard AV
audio_feathered_av	Soft AV
feathered_av	Expert compatibility override

Tone Carry Guide, Latent Guide, Detail Guide, and Detail AV are new opt-in choices and do not alter a migrated workflow automatically.

Migration tool

Back up a custom workflow, then run from the custom-node repository:

python tools/migrate_v05_workflows.py --check /path/to/workflow.json
python tools/migrate_v05_workflows.py /path/to/workflow.json

With no path, the tool checks or migrates maintained active examples. It is idempotent and does not renumber existing nodes or replace node types.

Source-media rewiring

Version 0.4 often repeated a complete AUDIO value into several nodes. Version 0.5 registers it once:

Load Video / Load Audio → Source Timeline → Loop Start → Current Shot
                              └───────────→ Preflight / Plan Studio

Loop End manifest → Assemble

The descriptor travels through state and manifests; path-backed media stays lazy. Legacy full-AUDIO fan-out and direct media paths remain accepted.

Platform notes

• FFmpeg is preferred, with PyAV fallback for review and assembly.
• Release-versioned web modules reduce stale frontend code after updates.
• If UI code still appears stale, reload the browser before clearing all site data.

See Troubleshooting for symptoms and corrective actions.