Set Bailian TTS Connector 🐑

This one's easy to mix up with its sibling, Set Bailian LLM Service Connector, because they share a name, a provider, and half a config layout. The difference is the wire they put out: this node produces a TTSConnector, not an LLMServiceConnector, and it's built for whatever text-to-speech node in the pack consumes that type rather than a chat model. If you're doing voice generation, dubbing, or any speech synthesis step, this is the credentials node you drop in front of it - not the LLM connector.

Alibaba Cloud's Bailian (百炼) platform bundles a lot under one roof: Qwen and third-party chat models, but also speech services. That's why this node exists as its own connector instead of being a mode toggle on the LLM one - different endpoint, different billing line, and critically, a different output type so ComfyUI's wire-typing stops you from accidentally plugging a TTS connector into a text-generation node and vice versa. That type separation is doing real work for you here; it's the thing that turns "wrong node" into an immediate red wire instead of a confusing runtime error two nodes downstream.

Inputs, and there aren't many. api_token is required - your Bailian key from the Alibaba Cloud console. There's no model or voice picker on this node at all; that selection lives on whatever downstream TTS node actually calls the API. This connector's entire job is: take a credential, wrap it, hand it off.

The shared-key detail worth knowing. Look at the default config_key: it's "bailian" - the exact same slot the LLM connector reads from in mie_llm_keys.json. That's not a coincidence or a copy-paste leftover; Alibaba Cloud issues one API key per account that covers the whole Bailian platform, chat and speech both. So if you've already set up the LLM connector with a working key in your config file, this node can piggyback on the same entry with zero extra setup - just drop it in and leave config_key at its default. You only need to touch config_key if you're deliberately running two separate Bailian accounts (say, one for testing, one for production) and want each service pointed at a different key.

prefer_local_config behaves exactly like every other connector in this pack: true by default, meaning the JSON file's key wins over whatever you typed into api_token on the node itself. If you're testing a fresh key and the node stubbornly keeps using an old one, that's this setting - either update the file or flip it off.

Install. Same as the rest of the pack: search "ComfyUI_MieNodes" in ComfyUI Manager, or clone https://github.com/MieMieeeee/ComfyUI-MieNodes into ComfyUI/custom_nodes and restart. Copy mie_llm_keys.json.example to mie_llm_keys.json next to the README if you haven't already, and fill in the bailian entry. Nothing to download - this is pure API plumbing, no local model weights involved.

Troubleshooting. The most common failure mode isn't this node at all - it's forgetting the actual TTS-generating node downstream that consumes tts_connector. This node alone produces a typed handle, not audio. If your wire refuses to connect to a node you expected it to work with, check the output/input types match (TTSConnector isn't interchangeable with LLMServiceConnector, even though both ultimately trace back to the same Bailian account). And if calls fail with an auth error despite a valid-looking key typed into the node, check mie_llm_keys.json first - the config-file precedence above is the single most common gotcha across every connector in this pack, and this node inherits it in full.