Preview Audio Compare ⚡🅡🅞🅣🅘

This is a pure output node - no downstream connections, nothing else in your graph depends on it - and it does one useful thing: it plays two audio clips side by side so you can A/B them without exporting either one first. If you're tweaking any of this pack's audio-processing nodes (a filter, a time stretch, dithering, or the mystery two-dial Knob node), this is the fastest way to actually hear what changed.

How it works

Wire in two AUDIO inputs, run the graph, and ComfyUI's preview panel gives you both clips to play. There's no processing here and no output socket - is_output_node is true and the outputs list is empty, meaning this node exists purely for its side effect (showing you a player), not to feed anything further down the graph.

The inputs and outputs that matter

• audio_a and audio_b (AUDIO, both required) - the two clips to compare. Nothing else to configure; there's no volume matching, no sync offset, no label field - it's deliberately minimal.
• No outputs. This is a dead end by design, meant to sit at the tip of a branch in your graph rather than in the middle of a pipeline.

How to install it

Via ComfyUI Manager: search "RyanOnTheInside," install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/ryanontheinside/ComfyUI_RyanOnTheInside.git
cd ComfyUI_RyanOnTheInside
pip install -r requirements.txt

then restart ComfyUI. Nothing to download - it's a UI/preview node.

Common issues & troubleshooting

One or both players don't appear after running the graph. Make sure both audio_a and audio_b are actually connected - they're both required, so a missing connection should stop the graph from queuing rather than silently showing one player, but it's the first thing to check if the preview looks incomplete.

You want to compare more than two clips at once. This node is fixed at two inputs by design - for more than an A/B, you'd need multiple Preview Audio Compare nodes side by side (A vs B, then A vs C), or the pack's regular audio preview node run multiple times if you just need to listen to each independently rather than directly compare pairs.

Best use case, genuinely: drop one right after any node whose effect you're not sure about - Frequency Filter Custom's output vs the dry signal, Audio Dither on vs off, the Knob node at different settings. It's a small node, but it turns "does this actually do anything?" from a guess into something you can just listen to.

It's a leaf, not a hub. Because it has no outputs, it's meant to sit at the end of a branch you split off specifically for listening - duplicate the audio you want to inspect into this node's two inputs (original vs processed) rather than trying to route your main signal chain through it. Nothing downstream of this node will ever see your audio; that's by design, and it's what makes it safe to sprinkle liberally through a graph while you're tuning something without worrying about accidentally changing your actual output path.