Split MP3 (7min segments)

This one does exactly what its display name says and nothing more: give it an MP3 path, it cuts the file into 7-minute segments and drops them in a folder. That's it - one input, one output, no configuration.

The use case is straightforward: you've got a long audio file - a narration track, a podcast, a song - and whatever consumes it next has a duration limit it can't exceed. A TTS pipeline, a per-segment video generation loop, a voice-cloning tool that chokes on long inputs. Splitting it into fixed chunks upstream sidesteps that limit entirely.

The inputs and outputs that matter

Just two things:

• mp3_path - the STRING path to your source MP3. That's the entire required input.
• Output: output_folder - the STRING path where the resulting segments were written.

The 7-minute chunk duration isn't a parameter; it's baked into the node's display name and, presumably, its code. There's no way to change it from the graph, no report of how many segments came out, and no per-segment output you can wire directly into something else - you get a folder path and have to look inside it yourself, or feed that path into something that globs it.

Installing it

ComfyUI Manager: search comfyui-huyl2-nodes, install, restart. Or by hand:

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

restart. The pack's README doesn't document this node's parameters - it covers a different node entirely - so there's no author guidance on what tools it uses under the hood to actually cut audio. Given the job, it's a safe bet this relies on ffmpeg or a Python audio library like pydub; if it errors out on first run with an import or "command not found" error, that's the first thing to check for.

Common issues & troubleshooting

The biggest practical gap is feedback: this node gives you no count and no report. If a run appears to succeed but you get fewer files than expected - or none - the node itself won't tell you why. Check output_folder directly on disk rather than trusting the graph to surface a problem.

If you need any of the things this node is missing - a configurable chunk length, a proper list output so downstream nodes can loop over each segment automatically, or a count you can actually check - reach for SplitMP3V2 instead. It's a clear superset of this node: same basic job, but with a max_minutes parameter (default 3, not a hardcoded 7), a genuine list output for the resulting file paths, and a count. Unless you're specifically maintaining an older workflow that's pinned to this exact node's fixed 7-minute behavior, there's no real reason to reach for SplitMP3 over the V2 version.