Encoder Nodes Guide

This pack's center of gravity is its encoder family - a stack of nodes that build conditioning for Qwen3-VL, Krea 2, MiniMax H3, and the other LLM-encoded models, with visual fusion, consensus blending, and reference-latent options layered on top. It's powerful and genuinely confusing, because the family has overlapping members: UC_AdvancedVisualConditioningEncode, UC_AdvancedVisConEncoder, UC_AdvancedMiniMaxH3ImageToVideo, UC_MiniMaxH3FirstFrameReferences, and half a dozen configurator nodes that only mean something if you understand the pipeline. UC_EncoderNodesGuide is the pack's answer to that confusion: a documentation node that returns the manual as Markdown.

The topic dropdown is the interface. node_catalog alone is worth the install - it's a plain-language map of the whole encoder family that tells you which node to reach for, starting with the blunt advice that UC_AdvancedVisualConditioningEncode is "the recommended encoder for nearly all conditioning workflows," and that UC_AdvancedVisConEncoder is not a replacement for it but a specialized tool for when you need the additional consensus stage. From there the topics go deep: prompt_templates_and_weighting, image_inputs_and_placeholders, resolution_and_reference_latents, visual_fusion, consensus_settings, formulas_and_alignment, embedding_export, and compatibility_nodes.

Output is a single markdown string - wire it into any markdown preview node (the pack ships UC_MarkdownPreview) and read while you build. It's static text, safe to call repeatedly, no state.

Why this node matters more than it looks: the encoder family is where this pack stops being a grab bag and starts having opinions you need to learn once. The README's own framing - spatial fusion and consensus "are not alternatives and are never crossfaded," the consensus stage works on complete conditionings, block_size is specific to block-interleave while dither_ratio is specific to random-dither - is exactly the kind of detail that only makes sense when you can read the structured explanation next to the node. The compatibility_nodes topic is also the map to the deprecated aliases the pack keeps registering so old workflows keep loading, which saves you from thinking a node is missing.

There's a sibling UC_CompositeNodesGuide for the compositor family, and the two together are the pack's built-in onboarding - which is worth remembering next time you're tempted to ask a community forum what UC_AdvancedConsensusConfiguration does. The answer is already in your graph.

Install is pack-standard: Manager search "ComfyUI-UtilsCollection" or git clone into custom_nodes. No models needed to read the docs. If you're touching any of the encoder or MiniMax H3 nodes, open the catalog topic first - it'll save you an hour of node archaeology.