Audio Notify Clip

Audio Notify Clip is the passthrough node in ComfyUI-Audio-Notifier that takes a CLIP, plays a sound, and returns it unchanged. It's the sibling of Audio Notify Model, but for the text side of the house: a way to hear when the CLIP model has loaded and is ready to encode your prompt.

CLIP loading is part of that same cold-start wall as the main model - on first run, the checkpoint's CLIP weights get read off disk before any conditioning can happen. This node slots into the CLIP wire between your loader and the CLIP Text Encode node, so the chime fires when the CLIP object is ready. And since the object flows through the node, the text encode can't start until loading is actually done.

The honest caveat applies just like with Audio Notify Model: once the CLIP weights are cached, the loader returns near-instantly, so the sound ends up firing at the top of the prompt with the rest of the load-milestone chimes. If you're not doing cold starts, this is the node you'll use once, find you don't need, and leave in the pack anyway. Where it genuinely helps: first render of a session on a slow disk, or diagnosing "is it loading or is it hung?" - a chime that fires means the load path completed and execution moved on.

Inputs and output

• clip - the CLIP to pass through.
• notification_enabled - mute the node.
• delay_seconds - hold the chime.
• repeat - 1–100 plays.
• blocking_playback - off by default (background thread); on to wait for the sound before forwarding.
• enable_sound_path / sound_path and enable_sound_name / sound_name - sound source: absolute path, or a file in the pack's sounds/ folder.
• fallback_to_system_beep - beep if nothing resolves, on by default.

One output: the unchanged CLIP.

The timing caveat

A CLIP object being ready is a very early milestone in a workflow - it says nothing about prompt encoding, sampling, or saving. If you want completion, use Audio Notify Latent or Audio Notify Image downstream instead. This node is purely for "the text model is loaded and execution is moving," which is a fine thing to know on cold starts and a mostly useless thing to know every prompt after that.

Install and gotchas

No dependencies, no models to fetch. Clone and restart:

cd ComfyUI/custom_nodes
git clone https://github.com/uni-miao/ComfyUI-Audio-Notifier.git

Restart the ComfyUI backend process, not just the browser tab. Pack-wide gotchas: the sounds/ folder ships empty, so add files (or use an absolute sound_path) and restart before the dropdown is useful; audio plays on the machine running the backend, so if ComfyUI is remote, that's where the sound comes out; and .wav is the most reliable format if a file plays silently.