32 KiB
ComfyUI-H3-Continuum 2.1.7
Native long-form MiniMax H3 video and audio continuation for ComfyUI.
H3 Continuum Sampler generates 1 to 16 H3 chunks as one sequence. It carries the previous raw video and audio latent into the next chunk, keeps accepted chunk latents on CPU, and defers VAE decoding until sampling is complete.
Spectrum-aware continuation
A key difference in H3 Continuum is its explicit interoperability contract with compatible builds of ComfyUI Spectrum MiniMax H3.
For continuation chunks, Continuum requests Actual Prefix 2 through H3 Continuum Interop API v1. Spectrum can then keep the first two solver steps after inherited Context on Actual Transformer evaluation before continuing with its normal forecast schedule.
Chunk 1
-> normal sampling
Chunk 2+
-> previous raw AV latent Context
-> Actual Transformer prefix (minimum 2 steps)
-> normal Spectrum acceleration
-> next chunk
This is more than simply placing Spectrum before the sampler: Continuum explicitly tells a compatible Spectrum receiver that the current branch is a continuation chunk and requests the protected Actual prefix for the new Context.
Among the public MiniMax H3 continuation implementations reviewed, Continuum is the only one found with an explicit Spectrum interoperability contract that requests Actual Prefix 2 for continuation chunks. This is deliberately a scoped comparison, not a claim about every H3 implementation.
Older or unsupported Spectrum builds ignore the hint and continue normally. The Spectrum H3: accepted H3 Continuum API v1, actual prefix=2 log confirms that a compatible receiver accepted it.
Important: Turbo LoRA + Spectrum
When using a Turbo LoRA, disabling Spectrum is strongly recommended. Local testing found that Turbo + Spectrum was more prone to visible artifacts.
Recommended starting profiles:
Quality
Standard ~20-step sampling
+ Spectrum ON
+ Continuum Actual Prefix 2
Fast
Turbo / 8-step profile
+ Spectrum OFF <- strongly recommended
Experimental
Turbo
+ Spectrum ON
-> may produce artifacts
Spectrum remains optional. Continuum does not require Spectrum for continuation.
Key features
- Raw AV latent continuation — carries native MiniMax H3 video and audio latent Context directly into the next chunk without decode/re-encode between chunks.
- Spectrum-aware continuation — emits H3 Continuum Interop API v1 and requests Actual Prefix 2 for continuation chunks.
- 1 to 16 chunks in one sequence — one sampler coordinates prompts, seeds, Context, sampling, and final assembly.
- CPU-backed accepted chunks — completed full chunk latents leave the active VRAM sampling path.
- Deferred VAE decoding — video/audio VAE decoding is postponed until sampling is complete.
- Fixed, List, and Timeline prompts — one Sequence Prompt can control the complete multi-chunk sequence.
- State, Session, and reroll support — advanced workflows can save continuation state, resume compatible sessions, and regenerate from a selected chunk.
- Composable accelerator chain — SageAttention, Sol-Attn, LoRA, and Spectrum stay external to Continuum and can be connected through the normal ComfyUI MODEL chain.
Chunk auto-resume (V3.1B+)
For long generations, enable Run Storage and let Continuum save each completed chunk in order. For normal automatic resume, use:
Run Storage:Save + Auto ResumeRegenerate From:Autoreroll_nonce:0
With Run Storage set to Save + Auto Resume and Regenerate From set to Auto, Continuum checks the saved Manifest and resumes from the first chunk that is not continuously available and valid.
If generation stops, simply Queue the same workflow again.
Chunk 1 saved
Chunk 2 saved
Chunk 3 saved
Chunk 4 interrupted while generating
Chunk 5 not generated
On the next Queue, Continuum resumes from Chunk 4. Chunks 1-3 are reused and are not sampled again.
If no saved chunks are available, generation starts from Chunk 1. If the Prompt, Seed, model/patch chain, resolution, Reference images, or other sampling-contract inputs change, incompatible saved chunks are not automatically reused and the affected generation is treated as a new compatible revision.
Regenerate from a specific chunk
To intentionally try a different result from partway through a sequence, select the starting chunk in Regenerate From.
Regenerate From = Chunk 3
Chunk 1-2 are reused and Chunk 3 onward is regenerated. Changing reroll_nonce allows another random result from the same regeneration point; keep it at 0 for normal automatic resume.
Important: Prompt Format controls how Sequence Prompt is parsed (Fixed, List, or Timeline). It does not select the resume position. Resume and regeneration position are controlled by Regenerate From.
Standard workflow
Download the standard H3 Continuum V2 template bundle (recommended).
Download the workflow JSON only.
The ZIP contains the workflow, its reference image, and a short setup guide. Extract it, copy H3_Continuum_V2_reference.webp into ComfyUI/input/, then drag H3_Continuum_V2.json onto the ComfyUI canvas.
It is a practical 3 x 5-second starting point for compatible MiniMax H3 ComfyUI systems. The bundled profile was validated on an RTX 5060 Ti 16GB system with 64GB of system RAM, but the workflow is not limited to that GPU. Adjust chunks, chunk_seconds, resolution, seed, prompts, and optional accelerators to suit the available hardware. The graph uses the stable facade nodes and keeps session, reroll, and report wiring optional.
Related projects:
- ComfyUI Spectrum MiniMax H3 is the optional sampling accelerator used by the bundled graph.
Models referenced by the workflow
All model URLs stored in the JSON point to the Comfy-Org/MiniMax-H3 distribution used for ComfyUI workflows. No third-party checkpoint host is referenced:
diffusion_models/minimax/minimax_h3_fl2va_pruned_int8_convrot.safetensorstext_encoders/qwen3vl_32b_minimax_h3_nvfp4_awq.safetensorsvae/minimax_h3_video_vae_fp16.safetensorsvae/minimax_h3_audio_vae_fp32.safetensors
No model weights are bundled in this repository. The workflow also contains optional/custom helper nodes from Spectrum, KJNodes (Sage Attention), rgthree, and ComfyUI-Easy-Use. Install those packages or replace/bypass their helper nodes.
Why H3 Continuum exists
H3 Continuum Sampler is an integrated sampler that includes H3 sampling, deferred Video/Audio VAE decoding, Context trimming, and automatic multi-chunk assembly. The VAE model weights are not bundled or loaded internally; connect externally loaded video_vae and audio_vae inputs.
Continuum was created to make SVI-style long-form continuation practical with native MiniMax H3: generate several manageable chunks, carry motion and audio context forward, and assemble one result without manually rebuilding the graph for every clip.
The main benefit is not only continuity. A native monolithic 15-second H3 generation can put substantial pressure on VRAM. Continuum samples shorter chunks separately, carries only the required raw AV latent context, stores completed chunk data outside the active sampling path, and defers decoding until sampling is complete. This can make a 3 x 5-second sequence less likely to run out of VRAM on a 16GB GPU, although resolution, model precision, accelerators, offload settings, and available system RAM still determine the actual limit.
The standard workflow uses the INT8 ConvRot H3 checkpoint, SageAttention CUDA++, and optional Spectrum acceleration as the validated reference profile. On different GPUs or software stacks, start with SageAttention Auto or bypass optional accelerators and confirm compatibility locally. Spectrum is not required for continuity and should be disabled for native-trajectory quality comparisons. When using a Turbo LoRA, disabling Spectrum is strongly recommended because local testing showed a higher risk of visible artifacts with the combined Turbo + Spectrum path.
Continuum was developed independently around its integrated multi-chunk workflow, AV timeline validation, and compatibility requirements. Other H3 continuation approaches are discussed only where their workflow and implementation differences are relevant.
Recommended quality-first profile
Continuum targets a useful reduction in long-form generation time while retaining comparatively high quality. It does not select every available accelerator for maximum speed.
| Component | Bundled RTX 5060 Ti profile | General recommendation |
|---|---|---|
| MiniMax H3 model | minimax_h3_fl2va_pruned_int8_convrot.safetensors |
Use a compatible official H3 model; the INT8 ConvRot build is the tested 16GB profile. |
| SageAttention | sageattn_qk_int8_pv_fp8_cuda++, compile off |
Use Auto when the installed SageAttention build and GPU-specific backend are unknown. |
| Spectrum | Enabled with the settings below | Recommended for the standard non-Turbo profile. Disable it for a native-trajectory reference and strongly prefer OFF when using a Turbo LoRA. |
| Sol-Attn | Disabled | Currently not recommended in the standard continuity profile. Local A/B runs showed more visible boundary artifacts in some outputs; this is not a universal incompatibility claim. |
| Turbo LoRA | Disabled in the quality profile | For a fast Turbo/8-step profile, use Spectrum OFF. Turbo + Spectrum is experimental because local testing showed a higher risk of visible artifacts. |
| Seam Correction | Auto |
Safe general starting point. In the current local A/B sample, Off produced the least noticeable visual boundary. Compare Auto and Off first. |
Recommended Spectrum values used by this profile:
blend_weight = 0.50
warmup_steps = 1
offline_smoothing_replay = true
bootstrap_first_forecast = true
audio_blend_weight = 0.00
Continuum automatically requests Actual Prefix 2 for continuation chunks. This is not an extra user-facing Spectrum setting and does not increase the configured solver-step count.
Seam Correction A/B note
The bundled workflow keeps Auto as a conservative general default. In the current 3 x 5-second local comparison, however, Off gave the most natural-looking join. Auto may apply a measured color adjustment or short blend that improves its numeric seam score but is not always preferred by visual inspection.
For a new model, prompt, resolution, or accelerator combination, render the same seed with Auto and Off. Prefer Off when Native Continuity already produces a clean boundary; use Auto when it visibly reduces a remaining luminance, color, or audio discontinuity.
Quick start
- Install the custom node and restart ComfyUI.
- Add H3 Continuum Sampler.
- Connect the normal H3 model, CLIP, VAEs, sampler, and sigmas.
- Connect one Text (Multiline) node to Sequence Prompt.
- For image-to-video, connect the source image to first_frame.
- Connect images and audio to your normal video output node.
- Start with two 5-second chunks and the settings shown below.
Most users only need H3 Continuum Sampler. The helper nodes are optional.
Installation
Git installation
From the ComfyUI custom_nodes directory:
git clone https://github.com/ukr8b3g-cmyk/ComfyUI-H3-Continuum.git
Restart ComfyUI, then search for H3 Continuum Sampler.
For Stability Matrix, the destination is normally similar to:
D:\StabilityMatrix\Data\Packages\<ComfyUI package>\custom_nodes\
ZIP or Windows installer
- Extract the repository as ComfyUI-H3-Continuum.
- Place it in ComfyUI/custom_nodes/.
- Run install_windows.bat if you want the included Windows installer to copy and validate the package.
- Restart ComfyUI.
If an older ComfyUI-H3-Continuum-Join folder exists, remove or rename it before starting ComfyUI. Do not load both folders at the same time.
No additional pip packages are required beyond the normal ComfyUI MiniMax H3 environment.
Standard connection
H3 MODEL loader
|
+-> optional SageAttention
+-> optional Sol-Attn
+-> optional LoRA
+-> optional Spectrum
|
v
H3 Continuum Sampler.model
CLIP loader -----------------------> clip
MiniMax H3 Video VAE -------------> video_vae
MiniMax H3 Audio VAE -------------> audio_vae
Sampler --------------------------> sampler
Sigmas ---------------------------> sigmas
Text (Multiline) -----------------> Sequence Prompt
Load Image -----------------------> first_frame
H3 Continuum Sampler.images ------> Create Video.images
H3 Continuum Sampler.audio -------> Create Video.audio
The accelerator chain is optional. A typical accelerated order is:
H3 MODEL -> SageAttention -> Sol-Attn -> LoRA -> Spectrum
When troubleshooting, start with fewer accelerators and add them back one at a time.
Main inputs
| Input | Connect |
|---|---|
| model | The final MODEL from the normal H3 model or accelerator chain |
| clip | MiniMax H3 text encoder / CLIP output |
| video_vae | MiniMax H3 Video VAE |
| audio_vae | MiniMax H3 Audio VAE |
| sampler | The sampler used by the normal H3 workflow |
| sigmas | The corresponding sigma schedule |
| Sequence Prompt | One external Text (Multiline) STRING |
| first_frame | Source image for image-to-video |
| prompt_overrides | Optional H3 Continuum Clip Overrides pack |
| advanced | Optional H3 Continuum Advanced pack |
Main outputs
| Output | Use |
|---|---|
| images | Connect directly to the image/video frames input of the output node |
| audio | Connect directly to the audio input of the output node |
| result | Optional packed State, Session, and report data |
Sampler and Advanced controls
Input image scaling
The bundled workflow uses Scale Image to Total Pixels before first_frame:
upscale_method: areais appropriate for reducing a larger source image with stable averaging.megapixels: 0.50preserves the source aspect ratio while targeting approximately 0.5 million pixels.resolution_steps: 32rounds width and height to model-friendly multiples of 32.- The bundled portrait is reduced from 848 x 1264 to approximately 576 x 864; the exact rounded size is supplied to the Continuum sampler through the image-size nodes.
- If a 16GB GPU runs out of VRAM, reduce this first to
0.30 MP, which is approximately 448 x 672 for the same portrait.
This node changes generation resolution, not the Continuum context length. Increasing megapixels raises VRAM use and generation time for every chunk.
The screenshot shows the same control at 0.60 MP for illustration. The current bundled JSON uses 0.50 MP.
The main sampler is sufficient for a normal first run:
Sequence Prompt: one fixed prompt, a----separated list, or a timeline prompt.Prompt Format:Autois the recommended default.chunks: number of generated clips.chunk_seconds: requested duration of each clip.width/height: inherited from the connected image-size path when linked.continuity:Balanced - 22 framesis the general-purpose default.base_seedandcontrol after generate: define the chunk seed sequence.seam_correction:Autois the safe default; it keeps the legacy video seam when correction does not improve the measured boundary.prompt_overrides: optional sparse per-clip replacement pack.advanced: optional settings pack. Leave it disconnected to use normal defaults.
Use H3 Continuum Advanced only when the basic node is not enough:
last_frame: optional final-frame anchor.session: resumes or reuses a Continuum session.initial_state: begins from a saved Continuum state.prompt_plan: accepts an externally prepared prompt plan.audio_continuity: keeps audio context across chunk boundaries.exact_total_duration: trims or pads the assembled result to the requested duration.Report Detail:Basicis the standard default. Use Detailed Report only for troubleshooting.reroll_from_chunk: regenerates from a selected chunk;0disables reroll.reroll_nonce: changes a reroll without replacing the main seed.strict_compatibility: fails closed when the native H3 layout contract is incompatible.debug: enables additional diagnostic logging.show_preview: enables the sampling preview.
Wiring reminder
For a standard graph, connect the patched MODEL path to model, the MiniMax H3 text encoder to clip, the video/audio VAEs to their matching inputs, the sampler and sigmas, a multiline text node to Sequence Prompt, and the scaled source image to first_frame. Connect images and audio to Create Video or Save Video.
prompt_overrides, advanced, and the Result helper are optional. Use H3 Continuum Result only when you need last_state, session, or the text report.
Recommended first run
| Setting | Recommended value |
|---|---|
| Prompt Format | Auto |
| chunks | 2 |
| chunk_seconds | 5.0 |
| width / height | Match the intended H3 generation resolution |
| continuity | Balanced - 22 frames |
| base_seed | Fixed while comparing settings |
| control after generate | fixed for A/B testing |
| seam_correction | Auto for normal use |
This produces approximately 10 seconds.
For a native-continuity comparison, use the same prompt and seed and compare:
Seam Correction = Off
Seam Correction = Auto
Auto is the normal recommendation. It keeps the native seam unless the guarded correction produces a safely measurable improvement.
Seam Correction modes
- Auto: Native-first mode. Applies post-decode correction only when the guarded candidate improves the measured seam.
- Off: No post-decode seam correction. Use this to inspect Native Continuity directly.
- Basic: Runs the V2.1 seam-correction path directly.
Continuity profiles
- Auto - conservative: Chooses a conservative context profile from the previous state.
- Fast - 5 frames: Lowest overlap and lowest continuity cost.
- Balanced - 22 frames: Recommended starting point.
- Strong - 39 frames: More context, with higher cost and a greater risk of over-constraining motion.
Sequence Prompt
Connect a single Text (Multiline) node to Sequence Prompt.
Auto
Auto detects Fixed, List, or Timeline syntax. This is recommended for normal use.
Fixed
One prompt is used for every chunk.
A single continuous cinematic performance. Preserve the same person,
lighting, camera direction, motion, voice, and music across every chunk.
List
Separate one prompt per chunk with a line containing three hyphens.
The woman begins singing while the camera slowly pushes in.
---
She continues the same phrase without a cut, reset, or pose jump.
---
She resolves the final note naturally and releases a soft breath.
If fewer List sections are supplied than the configured chunk count, the last section is reused.
Timeline
Use time or chunk sections in one multiline prompt.
[0-5s]
The woman begins singing. The piano phrase remains unresolved.
[5-10s]
Continue from the exact preceding breath, pose, camera movement, and melody.
[10-15s]
Complete the melody naturally during the final second.
Chunk headers are also accepted:
[Chunk 1]
Opening action.
[Chunk 2]
Continuous middle action.
[Chunk 3]
Natural ending.
How continuation works
For every continuation chunk, Continuum:
- Reads the accepted previous raw H3 video and audio latent.
- Extracts a phase-valid video and audio context window.
- Adds that context as fixed reference rows.
- Keeps new target audio and video rows separate and writable.
- Clones the workflow MODEL once for the current chunk.
- Samples the next chunk without decoding and re-encoding the prior result.
- Stores the accepted full chunk latent on CPU.
- Decodes and assembles all accepted chunks after sampling finishes.
The workflow input MODEL is not modified. Each chunk clone has its own Spectrum runtime/history.
When valid continuation context exists, Continuum emits Spectrum Interop API v1 with an Actual Prefix request of 2. Older or unsupported Spectrum versions ignore the hint and continue normally.
Optional helper nodes
These nodes are not needed for the basic workflow.
H3 Continuum Clip Overrides
Use this only when selected clips need prompts different from the main Sequence Prompt.
Connect one Text (Multiline) to Override Script and use explicit sparse sections:
[Clip 2]
Move to a closer shot while preserving the same motion and voice.
[Clip 5]
Finish the song naturally and hold the final note.
Only Clip 2 and Clip 5 are replaced. All unspecified clips continue using the main Sequence Prompt.
[Chunk N] is also accepted. Duplicate clip numbers and clip numbers outside the configured chunk count are rejected.
Connect the pack output to H3 Continuum Sampler.prompt_overrides.
H3 Continuum Advanced
Use this node for resume data and infrequent controls. Connect its output to H3 Continuum Sampler.advanced.
Important controls include:
- last_frame: Optional final-frame anchor for the final chunk.
- session: Continue or reroll from a prior V2 Session.
- initial_state: Start from a compatible saved State. Do not connect both Session and Initial State.
- prompt_plan: Advanced or compatibility prompt-plan input.
- audio_continuity: Continue the prior raw audio latent.
- exact_total_duration: Correct the assembled output to the requested total duration.
- diagnostics: Basic, Detailed Report, or Off.
- reroll_from_chunk: Keep accepted earlier chunks and regenerate from this one-based chunk number.
- reroll_nonce: Derive a different reroll seed without changing the base seed.
- strict_compatibility: Stop on unknown or unsafe H3 layout contracts.
- debug: Enable internal diagnostic logging.
- show_preview: Enable the normal sampling preview.
H3 Continuum Result
Connect the Sampler result output when you need to expose:
- last_state
- session
- report
For ordinary final video generation, this node is unnecessary.
Sessions and rerolling
A Session stores accepted CPU latents, prompts, seeds, dimensions, and continuation metadata.
Typical advanced use:
H3 Continuum Sampler.result
-> H3 Continuum Result.session
-> H3 Continuum Save Session
Later:
H3 Continuum Load Session
-> H3 Continuum Advanced.session
-> H3 Continuum Sampler.advanced
Resolution changes are rejected rather than silently resizing State or Session data.
Diagnostics and debugging
Use Basic diagnostics for normal testing. Use Detailed Report when inspecting seam scores, selected cuts, audio correlation, correction fallback, and per-chunk context.
Set debug=true only when deeper runtime information is needed. The single-clone implementation reports object IDs without retaining the objects:
Continuum model lifetime: input=<id> chunk=<id> parent=<id> base=<id>
For the expected single-clone path, every chunk parent should be the same workflow input MODEL:
chunk1.parent -> input MODEL
chunk2.parent -> input MODEL
chunk3.parent -> input MODEL
With a compatible Spectrum version, continuation chunks should also log:
Spectrum H3: accepted H3 Continuum API v1, actual prefix=2
0 models unloaded by itself is normal model-management information. The relevant leak warnings are:
Potential memory leak detected with model MiniMaxH3
WARNING, memory leak with model MiniMaxH3
If those warnings occur, compare identical one-chunk and two-chunk runs, then test Spectrum, Sol-Attn, and Sage individually.
Special and compatibility nodes
The following nodes remain available for advanced workflows or saved-workflow compatibility:
- H3 Continuum Sampler V2: Legacy/Core identifier used by older V2 workflows.
- H3 Continuum Prompt Plan: Explicit prompt-plan construction and inspection.
- H3 Continuum Save Session
- H3 Continuum Load Session
- H3 Continuum Session Info
- V1 Join, Finish, Assemble, Save State, and Load State nodes.
New workflows should normally use the compact H3 Continuum Sampler facade.
Compatibility and safety
- Native H3 PackedLayout is preserved.
- layout.position_ids identity is preserved when MM-RoPE coordinates are adjusted.
- State and Session schema remain compatible.
- V1 node identifiers remain registered.
- Video and audio VAEs are not run between H3 chunks.
- Full accepted chunk latents are stored on CPU.
- SageAttention, Sol-Attn, LoRA, and Spectrum remain external packages.
- Unknown H3 layout contracts fail clearly instead of producing a subtly incorrect continuation.
Related projects and implementation scope
| Project | Primary purpose | Workflow model | Main technical difference |
|---|---|---|---|
| H3 Continuum | Generate and assemble 1-16 H3 chunks | One integrated sampler with optional facade packs | Carries raw paired AV latent context, manages prompts/seeds/session/reroll, defers decode, and can apply post-decode seam correction. |
| H3 Motion Context | Continue motion and sound from one clip into another | Explicit context, trim, and optional save/load nodes across runs | Pins prior video/audio context into the next native H3 generation and trims the repeated context from the delivered clip. |
| Spectrum MiniMax H3 | Reduce H3 sampling time | MODEL wrapper before the guider/sampler | Forecasts selected post-transformer hidden features. It is an approximate accelerator, not a clip-continuity system, and may change the generated result. |
Continuum does not copy, vendor, or bundle source code from Spectrum or H3 Motion Context. Compatibility uses ComfyUI's MODEL/payload behavior. For a supported Spectrum build, Continuum emits a small API v1 metadata hint requesting at least two actual solver steps at the start of a continuation chunk; unsupported builds ignore it and continue normally.
Spectrum Actual Prefix 2 interoperability
Spectrum accelerates sampling by forecasting selected post-transformer hidden features from Actual H3 evaluations. A continuation chunk introduces a new AV Context and Packed Layout. Forecasting immediately after that transition could start before Spectrum has enough Actual features for the new context.
Continuum avoids that conflict without disabling or modifying Spectrum:
Stable input MODEL
-> call-local MODEL clone for the chunk
-> build and validate the continuation AV Context
-> freeze the branch-specific Packed Layout signature
-> Actual solver step 0
-> Actual solver step 1
-> allow the normal Spectrum forecast schedule
- The input MODEL is not mutated; every chunk receives an isolated clone and Spectrum runtime.
- The read-only
h3_continuumAPI v1 hint is emitted only when valid previous Context exists. - The effective prefix is the larger of Spectrum's own warmup and Continuum's requested prefix, clamped to the configured solver-step count.
- Context rows and generated Target rows remain separate in the native H3 Packed Layout.
- The Packed Layout is checked per logical branch and must remain structurally stable during Native Actual calls.
- Chunk 1 emits no hint and follows the normal Spectrum path.
- Offline Replay reuses the recorded Actual anchors and does not apply the prefix a second time.
- Older or unsupported Spectrum builds ignore the metadata and continue normally.
Actual Prefix 2 does not add two solver steps and does not run the whole sample twice. With a 20-step schedule, the result still uses 20 solver steps. Under the standard Spectrum warmup_steps=1 profile, it normally replaces one early forecast with one additional Actual Transformer evaluation. If the configured warmup is already two or more, it adds no evaluation.
This design gives Spectrum two Context-specific Actual anchors before forecasting. It trades a small amount of the maximum possible acceleration for more stable continuation behavior.
Report output and optional Detailed Report
The bundled workflow uses Basic reporting and leaves H3 Continuum Result.report unconnected. No additional report-display extension is required for the standard workflow.
The screenshot above is an optional troubleshooting example using Detailed Report and an external text display node. That display node is not included in the bundled template.
Continuum report:
interop=emitted actual_prefix=2 consumer=not_observable
Spectrum log:
Spectrum H3: accepted H3 Continuum API v1, actual prefix=2
consumer=not_observable is not an error. Interop API v1 is deliberately a one-way, read-only hint without an acknowledgement side channel. Spectrum's accepted log confirms that the hint was consumed.
Independently developed scope
The general idea of continuing one clip from another is not claimed as unique. Continuum's AV timeline validation, branch-local Packed Layout guard, call-local MODEL isolation, Spectrum Actual Prefix 2 contract, integrated multi-chunk orchestration, and seam-correction pipeline were developed independently for this project. No Spectrum or H3 Motion Context source code is copied or bundled.
License and external-content boundaries
- This repository is licensed under GPL-3.0.
- Spectrum MiniMax H3 is GPL-3.0.
- H3 Motion Context is GPL-3.0.
- The separate ComfyUI workflow templates repository is MIT-licensed.
- Model files, model cards, and other custom-node packages remain external and keep their own licenses and usage terms.
The MIT license of the template repository does not change the licenses of model weights or third-party custom nodes. This project does not redistribute MiniMax H3 weights.
Tested environment
- GPU: NVIDIA GeForce RTX 5060 Ti 16GB.
- System memory: 64GB RAM.
- Runtime: Python 3.13.12, PyTorch 2.13.0+cu130, CUDA 13.0.
- SageAttention: 2.2.0+cu130, using KJNodes FP8 CUDA++ with compile disabled.
- Verified baseline environment: 3 x 5-second runs at approximately 448 x 672 (0.3 MP), using the INT8 ConvRot checkpoint and SageAttention CUDA++.
- Bundled template profile: 3 x 5 seconds at 0.5 MP. Treat this higher-resolution profile as a starting point and monitor VRAM on the first run.
- Longer-than-15-second chains are supported by the node design but have not yet been validated in this environment.
- OOM avoidance is not guaranteed; peak usage depends on resolution, precision, model patches, Spectrum settings, ComfyUI offload behavior, and other loaded nodes.
Development checks
Use the same Python environment as ComfyUI:
python -m compileall -q .
pytest -q
Current local validation for this change:
74 passed
GPU validation should compare identical prompts, seeds, resolutions, samplers, and sigmas across:
Native
Sage
Sage + Sol-Attn
Sage + Spectrum
Sage + Sol-Attn + Spectrum
License
GPL-3.0-or-later. External accelerator source code is not bundled.




