Pass Audio

Pass Audio is exactly what it says: an AUDIO object goes in, the same AUDIO object comes out, and nothing in between touches it. It's a straight wire with a name tag. If you've only ever built image workflows this might look pointless, but once you start stringing video-plus-audio pipelines together - where an audio track has to survive a gauntlet of loaders, trims, and conditioning while you edit around it - a deliberate pass-through point is quietly useful.

The practical reasons are the same ones the rest of the pack's passers exist for. First, they were built to sit in front of nodes that break when you bypass what feeds them. Bypassing (Ctrl+B) a node is the standard way to A/B a section without deleting it, but ComfyUI can drop the connection to the bypassed node's inputs and your queue starts failing for reasons that are hard to spot. A passer anchored between the audio source and the fragile consumer keeps that link alive. Second, passers are great managed-group citizens: a group needs at least two nodes, and a collapsed passer is a clean second node that also gives you a tidy spot to fan one audio stream out to several destinations.

The interface

• audio (AUDIO, required) - from an audio loader or whatever produces the AUDIO type in your pipeline (commonly the VideoHelperSuite family of nodes).
• Output AUDIO - carries on to the next audio consumer.

No controls, no settings, no way to screw it up. That's the appeal.

Installing it

Ships in ComfyUI-RvTools_v2:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI-RvTools_v2

Restart ComfyUI, or install via ComfyUI Manager by searching "RvTools". No model downloads, no audio-specific dependencies - the pack's requirements are the usual torch/numpy/Pillow plus opencv-python, pilgram, pynvml and piexif, all handled on install.

What to keep in mind

The pack's README declares it no longer maintained and points to ComfyUI_Eclipse as the successor (same author, carries most of the nodes forward). The v2 pack still runs; just know it's the legacy line.

One honest caveat about the AUDIO type specifically: whether you'll even use this node depends on what's generating your audio. The AUDIO data type isn't universal across packs - it's the convention from VHS and friends - so confirm your audio producer emits AUDIO before wiring this in. If it does, this is a boring, dependable node that saves you a headache later. If it doesn't, you'd be connecting it to nothing, which is the one thing a passer can't fix.