Files

21 lines
5.4 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# V3.9 Reference Images — usage and compatibility
V3.9 has a new Reference Images input. The V3.8 sampler and the V38X2 workflow are retained. Start with `examples/workflows/MiniMax_H3_Continuum_V39.json` as a separate workflow; the earlier `MiniMax_H3_Continuum_V39_Reference_Inline.json` remains a migration fixture. The unchanged default official workflow has not passed a real browser save/reload or GPU acceptance gate yet. Its image loaders 1–6 are wired but bypassed, slots 7–9 need user-added loaders, and Sequence Prompt is blank for the user to fill. The user-selected JSON is used without edits. Its saved size controls are First Image + Draft 0.30 MP and the First Image loader is enabled: select your own First Image file before Queue. For Reference-only, turn that loader off and choose Manual. Saved 480×640 applies only to Manual mode. The standard V38X2 ZIP contains both V38X2 and V3.9 JSONs; the two Templates remain separate.
1. Connect images to `H3 Continuum Reference Images V3.9`, slots `Reference Image 1` through `Reference Image 9`. Each number is fixed; an empty slot never shifts the later numbers.
2. Connect its one `reference_images` output to the V3.9 Sampler's `Reference Images (Optional)` input. The official V3.9 workflow has this wiring already.
3. Choose `Reference Use = All chunks` to use connected images in every chunk. For different images in each chunk, select `Per chunk` and tick the table inside the helper node. Switching to Per chunk for the first time starts with no ticks. The helper keeps its ticks if you return to All and then select Per chunk again.
4. The Sampler owns the chunk count. For six chunks you may tick Image 1 at chunks 1, 3 and 6. If you temporarily reduce Chunks to three, the saved tick at six remains and becomes active again when Chunks returns to six. New chunks are unticked in Per chunk mode.
5. In `Sequence Prompt`, use `@R1` for fixed Image 1, `@R4` for fixed Image 4, and so on. The actual `<Picture N>` may change by chunk and with First/Last Image connections. Inactive `@R` tags produce warnings; they do not block generation. An image can condition a chunk even without an explicit tag. Not assigning an image in a later chunk does not guarantee the subject disappears from continued video.
6. If an existing First/Last setup merges the final two logical chunks into one physical group, those two chunks must have the same effective reference set. The runtime reports a conflict before sampling if they differ. It never merges or changes the assignments automatically.
The helper table displays configured intent. The Sampler's Reference Plan reports observed group mappings and hashes after Queue. A saved workflow retains input connections and selection widgets, not a previous Queue's verified report. Use a new Run Name when switching from V3.8 or from an older V3.9 prototype. Previously accepted V3.8 Takes do not migrate automatically.
The new workflow is derived from the user-supplied `MiniMax_H3_Continuum_V38X2+Decode_Cache_Helper (1).json` (SHA-256 `0af34446b56381568d0fce7be5c96324cff5b02b30b753f9db8871efd90206c7`). It keeps its model, LoRA, sampler, seed, audio/video loaders, `Repeat Reference` video mode, Decode Cache Helper, and Image loader bypass state. The Sequence Prompt node remains connected but its value is intentionally empty. The V3.8 Sampler/4–9 helper and their Reference links are migrated to the V3.9 Sampler/nine-image helper. The saved Project ID is intentionally new so V3.9 does not reuse the V3.8 Run Storage folder. Check local media paths and enter a prompt before Queue. You can also build a Reference-only workflow with First/Last disconnected and `Size Source = Manual`, keeping a compatible model/LoRA combination.
Connected upstream image loaders may consume RAM even when their images are not assigned to a particular chunk. With many images, especially 7–9, resize the source images before loading and review `Reference Image Size` (the template uses `Match Output`); changing output MP alone is not a guarantee that source-image RAM shrinks. No speed gain or 16 GB VRAM safety margin is claimed for V3.9.
After updating node files, fully restart the ComfyUI backend and hard-refresh the browser so the new Python node and JavaScript panel register together. A browser refresh alone cannot replace Python node definitions already loaded by a running backend. Open this new V3.9 workflow rather than changing the node type inside an older V3.9 prototype: old serialized widget positions can be misread by the new schema. Verify that a newly added V3.9 Sampler has one `Reference Images (Optional)` socket and no direct Reference Image 1–3 sockets or Sampler-side `Reference Routing` / `R1–R9 Chunks` widgets. If a newly added node still shows those old fields after a full restart, inspect duplicate Continuum installations and the actual backend package path. Old V38X2 workflows continue to use `H3 Continuum Sampler V3.8` and the old 4–9 helper without rewiring.
If an earlier V3.9 prototype node is already saved on the canvas, the frontend removes only its unconnected obsolete direct Reference sockets on load. Connected obsolete sockets are preserved and visibly flagged; manually reconnect those images to the matching numbered inputs on `H3 Continuum Reference Images V3.9`. They are not silently treated as active V3.9 References. Reload the browser only after saving any unsaved workflows, or open the new official workflow in a separate tab.