🔊AGSoft Load Audio

🔊AGSoft Load Audio is the front door to the audio side of the comfyui-AGSoft pack. It's a deliberately simple node, but the design decision underneath it is the whole point: it always hands you a real file path, not just an in-memory blob. That matters more than it sounds like it should, because the pack's audio tools (Audio Split, Audio Concatenate Plus, Replace Audio To Video) all hand your file to FFmpeg, and FFmpeg wants a path it can open.

The simplest way to think of it: three ways to get audio in, one way out.

How it works

The node checks its inputs in a strict priority order:

1. input_audio - an AUDIO socket from another node. Highest priority.
2. custom_path - an absolute path to a file on disk.
3. audio - a dropdown listing files in your ComfyUI/input folder, plus an upload button.

There's a fourth trick that's easy to miss: you can drag-and-drop an audio file straight from your OS file explorer onto the node. No browsing, no typing paths. The pack ships a small JS extension to make the whole node a drop target, with a highlight ring and double-drop protection.

Here's the subtle part worth knowing. When audio comes in through the input_audio socket, it arrives as decoded PCM - not your original MP3. The node writes that PCM out to a temporary WAV so that audio_path is always a real, absolute path. That's what makes chaining work: feed Load Audio into Audio Concatenate Plus and the concatenator gets a genuine file to mux, not a phantom. The flip side is that downstream "keep the source format" logic sees a WAV. If preserving the exact source codec matters to you, skip the socket and type the file path into custom_path (or the dropdown) instead.

The inputs and outputs that matter

For a beginner, only two things matter here: pick your file, and remember that you get two outputs:

• audio (AUDIO) - the decoded audio object, wire this into any other node's AUDIO input.
• audio_path (STRING) - the absolute path to a real file on disk. This is the one the FFmpeg-backed nodes want, and it's also handy as a plain string you can pipe into any text display node.

Installing it

Install the whole pack once - this node ships inside comfyui-AGSoft. Easiest: ComfyUI Manager → search "comfyui-AGSoft" → Install → restart. Or, by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/Art-xmaster/comfyui-AGSoft

then restart ComfyUI. There are no model downloads and nothing heavy in requirements.txt (the video/audio nodes lean on the FFmpeg binary ComfyUI already bundles via imageio-ffmpeg). The translators package in the requirements file is only used by the pack's separate Translate node, so you can ignore it for audio work.

Where people get tripped up

The one real gotcha is the socket-versus-path thing above. If you load an MP3 through the input_audio socket and then tell a downstream split node to keep the source format, you'll get a WAV back - not an MP3 - because by the time it reaches you it is WAV. It's not a bug, it's the decode pipeline, and the fix is to give the downstream node the path instead of the audio object.

Other than that, if you get an "ffmpeg not found" style error anywhere in this pack, that's the environment, not this node: make sure a system ffmpeg is on your PATH or that ComfyUI's bundled binary is available.