Nodes/BV Nodes/πŸŒ€ BV Vector to String List
ComfyUI Node

πŸŒ€ BV Vector to String List

One string per value β€” split a block-weight vector into loose wires

By BlackVortexAIΒ·Created 2 years agoΒ·Updated 11 months agoΒ· 3
πŸŒ€ BV Vector to String List
  • vector
  • STRING_LIST

Where BV Vector to String collapses a vector into one line of text, BV Vector to String List goes the other way conceptually: it splits the vector into a list of strings, one per value. Same data, different packaging - a list you can index into, wire item-by-item, or feed to consumers that want individual string values rather than a serialized blob.

If you've ever needed "the third block weight, as a string, by itself," this is the node that gets you there. It's the plumbing between the vector world and the string world, and it's most useful when a downstream node wants each value as its own string instead of a formatted preset. Think of it as turning a tight bundle into a rack of individual wires - you lose the neatness of the single line, but you can now route each value wherever it needs to go.

Inputs

  • vector (required) - the list of floats to unpack.

Output

  • STRING_LIST (STRING, list) - one string per vector entry, in order. A 58-long FLUX vector in, 58 strings out, index-aligned with the original.

Where it fits in the family

The vector family covers the full lifecycle: BV Vector of Length-n constructs, the edit nodes (numeric, range, and the FLUX named/checkbox variants) modify, and then you choose your export format - one string from BV Vector to String, or per-value strings from this node. Which one you want depends entirely on what's consuming the data: a text field that reads a whole preset wants the single string; anything that addresses values individually wants the list.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/BlackVortexAI/ComfyUI-BVortexNodes.git

or ComfyUI Manager β†’ "BV Nodes", then restart. No dependencies, no models.

The honest caveat

This node does no conversion of format - "0.5" stays "0.5", precision and all. And since it's a pure repackaging, it's the kind of utility you'll use exactly when a specific consumer demands it, not one you reach for by default. Keep it in the toolbox next to its single-string sibling; the day a node wants per-value strings, you'll be glad it's there.

CategoryπŸŒ€ BVortex Nodes/Vectors

Inputs (1)

NameTypeDefaultDescription
vectorLISTβ€”

Outputs (1)

NameTypeDescription
STRING_LISTSTRINGβ€”