Restore Continuum image reference inputs

This commit is contained in:
2026-10-30 11:06:44 +00:00
parent d1e97eecc7
commit e6116df914
5 changed files with 43 additions and 226 deletions
+5 -8
View File
@@ -93,14 +93,11 @@ the chunk count, the shared chunk duration, and a per-chunk reference bundle.
Reference images are inserted as `@R1` through `@R9`; routing is based on the
shared directive, soundscape, music, and each chunk's full prompt text.
The builder exposes nine optional `H3_REF_MODS` sockets, labelled `RefMod 1`
through `RefMod 9`. Each connected socket occupies the matching `@R` slot in
socket order, so the chips and generated prompt definitions are deterministic;
there is no image-socket offset or chained-bundle ambiguity. Visual RefMods are
automatically described in the generated shared directive and emitted through
the `ref_mods` output for downstream RefMod handling. The typed
`reference_images` output remains as an empty compatibility bundle for older
workflows; this builder no longer accepts image sockets.
The builder exposes nine optional `IMAGE` sockets, labelled `Reference Image 1`
through `Reference Image 9`. Each connected socket occupies the matching `@R`
slot, and the generated Continuum reference bundle contains those images with
per-chunk routing. RefMod inputs and direct RefMod conditioning are deliberately
not part of this node.
The prompt builder intentionally uses the `ReferenceImagesV39Bundle` class
from the installed upstream H3 Continuum pack. Install that pack alongside