ComfyUI Node: Unbundle (obvpm)

Unbundle (obvpm):

The Unbundle (obvpm) node is designed to deconstruct a bundle into its individual components, allowing each field within the bundle to be accessed separately. A bundle is essentially an ordered mapping, where each key corresponds to a field name as initially packed. This node is particularly useful when you need to extract specific values from a bundle that has been transmitted through a single wire, enabling you to work with each component independently. The node automatically aligns with the bundle's structure, ensuring that the outputs are consistent with the original packing order. Additionally, the node's configuration dialog allows you to reorder outputs or hide unnecessary ones, providing flexibility in managing the data flow. If a field name specified in the configuration is not present in the bundle, the node will output None for that field, ensuring that the process is robust and adaptable to varying bundle contents.

Unbundle (obvpm) Input Parameters:

in

This parameter represents the input bundle that you want to unpack. It is expected to be a dictionary-like structure where each key-value pair corresponds to a field name and its associated value. The bundle should be connected to the output of a Bundle node to ensure proper functionality. There are no specific minimum, maximum, or default values for this parameter, as it depends on the structure of the bundle being processed.

names

This optional parameter allows you to specify a list of field names to be extracted from the bundle. If provided, the node will output the fields in the order specified by this list. If a field name in this list is not present in the bundle, the corresponding output will be None. This parameter provides flexibility in selecting and ordering the fields you wish to work with, but it is not mandatory. If not specified, the node will default to using the order of fields as they appear in the bundle.

Unbundle (obvpm) Output Parameters:

out_1, out_2, ..., out_16

These outputs correspond to the individual fields extracted from the input bundle. Each output is labeled with its respective field name, as determined by the bundle or the optional names list. The node can handle up to 16 fields, with each output providing the value associated with a specific field name. If a field name is not present in the bundle, the corresponding output will be None. This setup allows you to access and utilize each component of the bundle separately, facilitating more granular control over the data flow in your workflow.

Unbundle (obvpm) Usage Tips:

• Use the configuration dialog to reorder or hide outputs based on your workflow needs, ensuring that only relevant fields are processed.
• If you only need a single field from the bundle, use the names parameter to specify that field, which will simplify the output and reduce unnecessary data handling.

Unbundle (obvpm) Common Errors and Solutions:

ValueError: expected a bundle (a name/value mapping) but got <type>

• Explanation: This error occurs when the input provided to the in parameter is not a valid bundle. The node expects a dictionary-like structure with name-value pairs.
• Solution: Ensure that the input is connected to the output of a Bundle node, which guarantees the correct structure for processing.

Unbundle: <field_name> not in the bundle (has <available_fields>); those outputs are None

• Explanation: This message indicates that a field name specified in the names parameter is not present in the input bundle.
• Solution: Verify the field names in the names parameter and ensure they match the keys in the input bundle. If certain fields are optional, be prepared to handle None outputs for missing fields.