Nodes/ComfyUI-IP-Composer/IP-Comp Save Concept Subspace
ComfyUI Node

IP-Comp Save Concept Subspace

IP-Comp Save Concept Subspace

By godmt·Created about a year ago·Updated about a year ago· 5
IP-Comp Save Concept Subspace
  • concept_subspace
    concept_nameconcept

    This is the "save your work" node of the pack, and it exists for a practical reason: you don't want to rebuild a concept every time you use it. IP-Comp Concept Subspace runs SVD over your descriptions each time it executes - cheap for a short list, but pointless to repeat. Run it once, save the result here, and every future workflow just loads the file with IP-Comp Load Concept Subspace.

    It's a one-job node, so this article is short. That's not a knock - caches are supposed to be boring.

    What it does

    It takes a CONCEPT_SUBSPACE and a name, and writes it to disk as a safetensors file:

    file_path = models/ip_concept_subspaces/{concept_name}.safetensors
    st.save_file({"concept_subspace": ...}, file_path, metadata=...)
    

    The name you give it becomes the filename, and the metadata - which rank was used and which CLIP model built the subspace - is embedded in the file itself. That metadata is what lets the load node (and you) tell later what this subspace is tied to.

    The inputs that matter

    Only two, and one is obvious:

    • concept_subspace - wire in the output of IP-Comp Concept Subspace (or even a loaded subspace you want to re-save under a new name).
    • concept_name - default "concept", but please don't leave it that way. This becomes the filename, so make it descriptive: fur, outfit_90s, golden_hour.

    There are no outputs - this is a terminal node that fires and disappears, which is why ComfyUI marks it as an output node.

    Installing it

    Standard for the pack:

    cd ComfyUI/custom_nodes
    git clone https://github.com/godmt/ComfyUI-IP-Composer
    

    restart, and let ComfyUI Manager handle the open-clip-torch dependency. The saved files land in ComfyUI/models/ip_concept_subspaces/, alongside the prebuilt ones from the ReadyON/IP-Composer-Concept-Subspaces collection on HuggingFace.

    Where people get burned

    • Filename collisions. The HF bundle already ships fur.safetensors, weather.safetensors, and friends. Save a custom concept as fur and you've overwritten the original, silently. Check the folder before you save with a generic name.
    • The dropdown doesn't update. IP-Comp Load Concept Subspace builds its file list once at startup. After saving here, refresh the node list or restart ComfyUI before expecting the new name to appear in the Load node's dropdown.
    • Don't save to the wrong path. If you run ComfyUI from a venv or a symlinked models folder, confirm where models/ip_concept_subspaces actually resolves - the node writes to the pack's resolved models root, and it's easy to end up with two copies in two places.

    One more thing worth knowing: the whole build → save → load loop only matters if you keep using the same concept. If you're experimenting and only need the subspace once, feed IP-Comp Concept Subspace straight into IP-Comp Concept Merge and skip this node entirely. Save when you'd rather not re-run the SVD tomorrow.

    Categoryip_composer

    Inputs (2)

    NameTypeDefaultDescription
    concept_subspaceCONCEPT_SUBSPACE
    concept_nameSTRINGconcept

    Outputs (0)

    No outputs