H3 Continuum Reference Images V3.9:
This node packages up to nine optional reference images into one fixed reference-image collection for the H3 Continuum workflow. Each image keeps a stable slot number, so the image connected to Reference Image 1 remains @R1, the image connected to Reference Image 2 remains @R2, and so on, even when some other slots are empty. You can apply the connected images to every chunk, or use the per-image chunk assignment fields to control exactly which chunks receive each reference. This provides a consistent way to organize multiple visual references and to reuse the same image-to-reference numbering throughout a workflow.
H3 Continuum Reference Images V3.9 Input Parameters:
reference_use
This setting determines how the connected reference images are applied across chunks. The available options are All chunks and Per chunk, and the default is All chunks. With All chunks, each connected reference image is made available throughout the workflow rather than being limited by the individual chunk assignment fields. With Per chunk, the reference_r1_chunks through reference_r9_chunks values are used to decide where each reference image applies, allowing different images to be assigned to different chunks. The value must be one of the two listed options; any other value causes the node to stop with the error Reference Use must be All chunks or Per chunk.
reference_r1_chunks
This advanced string stores the chunk assignment for Reference Image 1. Its default value is off, which means that no chunk assignment is selected for this slot when per-chunk mode is used. In Per chunk mode, enter the chunk selection using the format supported by the node’s in-node assignment table; the node canonicalizes valid selections before packaging them. This setting has no assignment effect when reference_use is All chunks, although its stored value is retained in the resulting reference bundle. No numeric minimum or maximum is specified by the node; valid values depend on the available chunk-selection syntax, and invalid selections produce an error describing the invalid V3.9 Reference chunk selection.
reference_r2_chunks
This advanced string stores the chunk assignment for Reference Image 2. Its default value is off, so this image is not assigned to any chunk in Per chunk mode unless you change the value. A valid assignment determines which chunks can use the second fixed reference slot, while the image itself remains identified as Reference Image 2 or @R2. When reference_use is All chunks, this field is not used to limit image availability. No numeric minimum or maximum is specified; use the chunk-selection format provided by the node’s in-node table.
reference_r3_chunks
This advanced string stores the chunk assignment for Reference Image 3. The default is off, meaning no per-chunk assignment is selected. In Per chunk mode, the value controls which chunks receive access to the image connected to Reference Image 3. The setting is preserved even if the corresponding image is not connected, but an unconnected slot does not provide an image to downstream processing. No numeric minimum or maximum is defined; enter a valid chunk selection from the node’s assignment interface.
reference_r4_chunks
This advanced string stores the chunk assignment for Reference Image 4. It defaults to off, which leaves the fourth reference slot unassigned in Per chunk mode. Changing it to a valid chunk selection controls where the connected fourth image is used, without changing its fixed identity as Reference Image 4 or @R4. The setting is ignored for assignment purposes when reference_use is All chunks. No numeric minimum or maximum is specified by the node; invalid selection text causes validation to fail.
reference_r5_chunks
This advanced string stores the chunk assignment for Reference Image 5. Its default is off, so the fifth reference image is not assigned to chunks when per-chunk routing is active. Use a valid selection from the in-node table to make this image available only to the desired chunks. The slot number remains fixed regardless of other connected or disconnected images. No numeric minimum or maximum is specified; the accepted values are determined by the node’s chunk-selection rules.
reference_r6_chunks
This advanced string stores the chunk assignment for Reference Image 6. It defaults to off and therefore does not select any chunks in Per chunk mode until configured. A valid value determines the chunks associated with the sixth reference slot, while All chunks mode makes the connected image available throughout instead of applying this restriction. No numeric minimum or maximum is provided by the node; use the assignment syntax shown in the node interface.
reference_r7_chunks
This advanced string stores the chunk assignment for Reference Image 7. The default value is off, indicating that no chunks are selected for this slot in Per chunk mode. When configured with a valid selection, it routes the connected seventh reference image to the specified chunks and keeps its stable identity as Reference Image 7 or @R7. No numeric minimum or maximum is specified; invalid chunk-selection text results in a validation error.
reference_r8_chunks
This advanced string stores the chunk assignment for Reference Image 8. Its default value is off, so the eighth slot has no per-chunk assignment by default. In Per chunk mode, a valid chunk selection controls where the connected eighth image is available; in All chunks mode, this field does not restrict its use. No numeric minimum or maximum is specified by the node, and the value must follow the selection format supported by the in-node table.
reference_r9_chunks
This advanced string stores the chunk assignment for Reference Image 9. It defaults to off, leaving the ninth reference slot unassigned in Per chunk mode. A valid assignment selects the chunks that can use the connected ninth image, while the image retains its fixed identity as Reference Image 9 or @R9. No numeric minimum or maximum is specified; use only valid chunk-selection values recognized by the node.
reference_image_1
This optional IMAGE input accepts the image for fixed Reference Image 1, also identified as @R1. It has no default image value and may be left unconnected. When connected, the image is stored in the first reference slot and is either available across all chunks or routed according to reference_r1_chunks, depending on reference_use. Its slot number does not change when other reference inputs are empty.
reference_image_2
This optional IMAGE input accepts the image for fixed Reference Image 2, also identified as @R2. It has no default image value and can remain unconnected. A connected image is stored in the second slot and is made available to all chunks or only the selected chunks according to the reference-use mode and reference_r2_chunks assignment.
reference_image_3
This optional IMAGE input accepts the image for fixed Reference Image 3, also identified as @R3. It has no default image value. When connected, it occupies the third stable reference slot; when disconnected, that slot contains no image. Its availability is governed by All chunks or, in Per chunk mode, the selection stored in reference_r3_chunks.
reference_image_4
This optional IMAGE input accepts the image for fixed Reference Image 4, also identified as @R4. It is optional and has no default image. The connected image remains in slot four regardless of whether any other image slots are connected, and its chunk availability follows the selected reference-use mode and reference_r4_chunks.
reference_image_5
This optional IMAGE input accepts the image for fixed Reference Image 5, also identified as @R5. It may be left empty because there is no default image. If connected, it is stored in the fifth slot and can be used across all chunks or assigned to selected chunks through reference_r5_chunks when Per chunk is selected.
reference_image_6
This optional IMAGE input accepts the image for fixed Reference Image 6, also identified as @R6. It has no default value and is not required for the node to create the reference bundle. A connected image is kept in the sixth stable slot and follows the global or per-chunk routing behavior selected by reference_use.
reference_image_7
This optional IMAGE input accepts the image for fixed Reference Image 7, also identified as @R7. It has no default image and may be left unconnected. When supplied, it is packaged in slot seven and is available to all chunks or only the chunks selected in reference_r7_chunks, depending on the selected mode.
reference_image_8
This optional IMAGE input accepts the image for fixed Reference Image 8, also identified as @R8. It has no default image value. Connecting an image places it in the eighth fixed slot, while the reference_use setting determines whether its use is global or limited by reference_r8_chunks.
reference_image_9
This optional IMAGE input accepts the image for fixed Reference Image 9, also identified as @R9. It is optional and has no default image. If connected, it is stored in the ninth slot and follows the selected all-chunk or per-chunk routing behavior; leaving it empty does not renumber any of the other reference images.
H3 Continuum Reference Images V3.9 Output Parameters:
reference_images
This output provides one H3_CONTINUUM_REFERENCE_IMAGES_V39 reference-image bundle for downstream H3 Continuum nodes. The bundle contains nine ordered image slots, where each slot contains the connected image or an empty value, the selected reference_use mode, and the nine corresponding chunk selectors. The stable ordering is important: slot 1 always represents Reference Image 1, slot 2 always represents Reference Image 2, and so forth, even when some slots are disconnected. Downstream nodes use this bundle to determine which reference images are available and, in per-chunk mode, which chunks each image is assigned to.
H3 Continuum Reference Images V3.9 Usage Tips:
- Leave
reference_useset toAll chunkswhen the same visual references should remain available throughout the entire sequence or workflow. - Select
Per chunkwhen different chunks need different reference images, then configure the matchingreference_r1_chunksthroughreference_r9_chunksfields using the node’s in-node assignment table. - Connect images to the numbered slots that match their intended identity. Empty slots are preserved, so connecting an image to
reference_image_3identifies it as@R3rather than renumbering it to the first available slot. - Keep unused chunk assignment fields set to
offto make the routing easier to inspect and avoid unintended assignments inPer chunkmode. - Use the same reference slot consistently across related nodes and workflow stages when you need a particular subject, character, object, or visual source to retain a stable reference identity.
- For per-chunk routing, review each image’s assignment separately. A reference image can be connected correctly but still be unavailable in a chunk if its corresponding selector is left as
offor does not include that chunk.
H3 Continuum Reference Images V3.9 Common Errors and Solutions:
Reference Use must be All chunks or Per chunk
- Explanation: The
reference_usevalue is not one of the two supported choices. The node only acceptsAll chunksorPer chunk. - Solution: Open the
Reference Usecontrol and select eitherAll chunksorPer chunk. Avoid manually entering another spelling or variation.
invalid V3.9 Reference chunk selection
- Explanation: One of the
reference_r1_chunksthroughreference_r9_chunksfields contains a chunk selection that the node cannot parse. The full error normally includes details explaining which part of the selection is invalid. - Solution: In
Per chunkmode, use the node’s in-node table to create the assignment, or restore the affected field tooffand configure it again. Check the spelling, separators, and chunk numbers against the available chunk choices.
Image slot is empty
- Explanation: A chunk assignment may refer to a reference slot whose corresponding
reference_image_1throughreference_image_9input is not connected. The node still preserves the slot and selector, but there is no image available in that slot for downstream processing. - Solution: Connect an image to the matching numbered input, or set that slot’s chunk selector to
offif the assignment is not needed.
Reference image is not used in the expected chunk
- Explanation: In
Per chunkmode, the image may be connected to the wrong numbered slot, its matching selector may beoff, or the selector may not include the chunk you are checking. InAll chunksmode, the per-image selectors do not control routing. - Solution: Confirm the image input number, select the correct
reference_usemode, and review the correspondingreference_rN_chunksfield for that exact slot.
Reference images have unexpected numbering
- Explanation: Reference numbers are fixed by the input names and do not shift when earlier slots are empty. For example, an image connected only to
reference_image_4remains@R4, not@R1. - Solution: Connect each image to the numbered slot intended for its identity and update downstream references to use that same slot number. Do not rely on automatic renumbering.
