ITL Multi Audio Loader Advanced

The Advanced version of ITL's Multi Audio Loader is the basic one - drop up to 8 audio files on a single node, each on its own audio_N output socket - plus one addition: a filename_N output for every file.

That one addition is easy to dismiss and surprisingly easy to justify. Load several clips onto one node and you lose track of which is which the moment the graph gets busy. With the filenames exposed as strings, you can wire filename_1 into a label, a filename-save node, or a text-display node so the workflow tells you what's playing where. It also makes downstream saves sane: name your output track after its input source instead of audio_00001.wav.

Everything it inherits

Same mechanics as the basic node, worth a quick recap since they don't change:

• audio_N keeps each file's native sample rate - no resampling, ever. If a downstream node needs a specific rate, do that conversion explicitly.
• output_slots - auto follows the file list (sockets appear/vanish as you edit); a pinned 1–8 keeps sockets and wires in place while you swap files. Extra pinned sockets with no file behind them output None.
• The row on/off toggle keeps the socket position but outputs None for audio_N and filename_N. Safe for unplugged OPTIONAL inputs downstream; fatal for REQUIRED ones. Toggle is "skip this run," not "remove."
• count - enabled files actually emitted, not row count.

Reordering files shifts what each socket carries, and the node warns in its status line whenever a change touches a wired socket. When you see that warning, check your connections.

Outputs & install

Outputs: count (INT), then per file audio_N (AUDIO) followed by filename_N (STRING) - 17 sockets at full capacity, so if you're only loading two files, auto output slots keep the node compact.

Install via ComfyUI Manager (search "ComfyUI-IntoTheLatent-Utils") or:

cd ComfyUI/custom_nodes
git clone https://github.com/Into-The-Latent/ComfyUI-IntoTheLatent-Utils

then restart. No extra dependencies beyond what ComfyUI already ships.

When do you pick Advanced over basic? If you're building anything that saves, labels, or logs audio - or you want to audit which clip fed which socket - Advanced earns its keep. If you just need several clips on separate sockets with nothing downstream that cares about names, the basic node is all you need. Both are the same pack, so it's a five-second swap if you change your mind.