🌀 BV Regional Anima Adapter

Here's a genuinely weird situation, and the node exists because of it: the pack that made regional authoring pleasant for Anima is not the pack that applies the attention patch. The BV Regional Anima Adapter is the compatibility layer that lets your BV-authored document feed the external Anima regional-conditioning node pack (Sen-sou's ComfyUI-Anima-Regional-Conditioning, the MIT-licensed origin of BV's own Anima patch) without you hand-building a per-region node chain.

If you're using BV Regional Anima Conditioning - the built-in backend - you don't need this node at all. The Adapter only matters for the edge case where you've already built a workflow around the external Sen-sou nodes, or where you specifically want its node chain's particular controls rather than BV's compiled version.

What it does

It takes two inputs: regional (your BV document) and clip. It compiles the document into the external pack's expected chain format and outputs four things: positive and negative (CONDITIONING), regions (the external pack's ANIMA_CONDITIONING_REGIONS type), and background (CONDITIONING). Those regions output plugs into the external pack's patcher node, and the background supplies the uncovered-pixels context.

The README's framing is precise: it compiles BV Regional "without a per-region node chain." In the external pack, a regional workflow normally means a node per region - each with its own prompt and mask - chained together. The Adapter collapses all of that authoring into the BV document and emits the equivalent chain format in one step. You draw in the BV editor, the Adapter produces the chain, the external patcher applies it.

When to use it (and when not to)

Use it: you already run the external pack and don't want to rebuild your sampling graph to try BV's editor. Not use it: anything where you're starting fresh. For new workflows, the built-in BV Regional Anima Conditioning is strictly less plumbing - one node, no second pack, no chain format to reason about. The Adapter is a migration path and a compatibility nicety, not a better way to do the same thing.

There's also a practical note: because it targets the external pack, the external pack's Anima backend must be installed and compatible with your ComfyUI build. The error you'd see if it isn't is the usual "missing node / type not found" style failure when you load the workflow, which is your cue that the Sen-sou pack isn't present.

Install

Search BV Node Pack in ComfyUI Manager, or:

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

Restart, hard-refresh with Ctrl + F5. No extra dependencies for the BV side; the external Anima pack is a separate install you choose to make.

The honest take

This is a niche node, and it's fine that it's niche. Compatibility bridges like this are how regional-authoring ecosystems avoid fracturing into incompatible islands - the BV editor is the nice authoring surface, and the adapter means adopting it doesn't strand your existing Sen-sou graph. If you're not in that situation, skip it. But if you've got a pile of Anima workflows built on the external pack, this is the on-ramp that doesn't require burning them down.