MP3 Path → Audio

This one's a loader, plain and simple: give it a path to an audio file sitting on disk, it hands you back ComfyUI's native AUDIO type plus the clip's duration in seconds. If you've ever wondered how you get from "I have a folder of MP3s" to "I have something I can actually wire into an audio-consuming node," this is that step.

It pairs naturally with Audio File Scanner, another node in the same pack - that one crawls a folder and gives you back a list of file paths, this one turns each of those paths into a usable AUDIO object. Scan, then load, is the pattern.

Inputs and outputs. One required field, file_path (a plain string, default empty). Two outputs: audio (the AUDIO type ComfyUI's audio nodes expect) and duration (a float, the clip length in seconds). That's the whole node - there's no format picker, no sample-rate override, nothing else to configure.

A quick note on the name: despite being called "MP3 Path To Audio," there's nothing in the schema that restricts it to .mp3 files specifically. It's almost certainly built on a general-purpose audio decoding library under the hood, but the pack doesn't document which one, so if you're feeding it something less common - .opus, .wma, whatever - test it before you build a long pipeline around the assumption that it'll open cleanly. Its sibling Audio File Scanner explicitly knows about a whole list of formats beyond MP3 (wav, flac, aac, m4a, ogg, opus, wma, aiff, ac3), so it'd be a little odd if this loader genuinely only handled MP3s - but "odd" isn't the same as "documented," so verify rather than assume.

Installing it. This ships as part of comfyui-sortlist, a small pack from a single GitHub author (huyl3-cpu, published under the title comfyui-huyl2-nodes). Search for that title in ComfyUI Manager and install from there, or clone it directly if Manager's registry doesn't have it indexed:

cd ComfyUI/custom_nodes
git clone https://github.com/huyl3-cpu/comfyui-sortlist

Restart ComfyUI afterward either way.

Troubleshooting. The README for this pack documents exactly one node in detail (the video segmenter), and this isn't it - so there's no author guidance beyond the schema. A couple of practical things worth checking if it's not behaving:

If you get an empty AUDIO output or an outright crash, the first suspect is file_path pointing somewhere the ComfyUI process can't actually see. This pack was clearly built with Google Colab in mind (its README's install instructions target /content/ComfyUI/custom_nodes), and a very common Colab failure mode is referencing a Google Drive path before the drive has finished mounting - the path looks correct in your notebook cell but doesn't exist yet when the node runs.

If duration comes back as 0, that usually means the file failed to decode silently rather than loudly - worth opening the same file in a normal audio player to confirm it isn't corrupted or an unsupported container before assuming the node is at fault.