CombineParamDataLite

CombineParamDataLite is the smallest node in the mittimiLoadPresetLite pack, and honestly, it's the one you'll use last. It exists because this pack's generation data - checkpoint, prompts, size, steps, CFG, sampler, seed - travels down the graph as a single PDATA object, a list of dictionaries that SaveImageWithParamTextLite turns into the "parameters:" text in your saved image. This node simply joins two of those objects together.

Inputs: param1 (required) and param2 (optional). Output: parameters_data. If param2 is left unwired, you get param1 back unchanged; if both are present, the two bundles concatenate, so the image metadata ends up carrying both recipes.

When would you ever need it? The clearest case is a workflow that runs two LoadSetParametersLite hubs - say, one for the main model and one for a second pass or a side-by-side comparison - and wants both recipes recorded in the same saved image. Or you're building a graph where a parameter bundle gets split up and recombined elsewhere. If you only run one preset hub, this node never appears in your graph, and that's fine. It's plumbing for a custom data type, the ComfyUI equivalent of a two-input joiner for metadata.

The thing to keep in mind is that PDATA only means something inside this pack. It's not a standard ComfyUI type and no core node will accept it - so if you're not feeding SaveImageWithParamTextLite or SaveParamToPresetLite, a PDATA wire does nothing useful. Think of CombineParamDataLite as the joiner at the end of the pack's own little data pipeline, not something you'll reach for in an unrelated graph.

Install via ComfyUI Manager (search "ComfyUI_mittimiLoadPresetLite") or git clone https://github.com/mittimi/ComfyUI_mittimiLoadPresetLite into custom_nodes, then restart. It needs nothing beyond the pack's single toml dependency, and no models to download.