Video Mute (Remove Audio) from URL

This node strips the audio track from a video and writes a new, silent copy. The "from URL" in the name is a bit of a misnomer in the sense that matters most: it's really "from a path or URL string" - a local file path works exactly the same way.

Why you'd want this

There are a few common reasons to mute a clip before further processing: feeding it into a video model that doesn't expect or use audio, re-muxing a different soundtrack on top afterward, or simply cutting file size for a downstream step that doesn't need the audio stream at all. Rather than shell out to ffmpeg yourself between graph runs, this wraps it as a node.

How it works

The schema doesn't expose any implementation detail beyond its three inputs, but dropping the audio stream while leaving video intact is textbook ffmpeg territory (a one-flag operation, -an), and it lines up with the rest of this pack's video tooling - the README's one documented node explicitly talks about GPU-to-CPU encoding fallback, which is ffmpeg behavior through and through. Treat that as the most likely mechanism, not a confirmed implementation detail.

Inputs and outputs

• video_path (STRING, required) - the source clip.
• output_dir (STRING, required) - where the muted copy goes.
• output_filename (STRING, required) - what to name it.
• Output: muted_video_path (STRING) - the resulting path, ready for the next node.

All three inputs default to an empty string - there's no sensible fallback if you leave one blank.

Installing it

The README documents the pack's install via git clone for Colab; nothing about extra Python packages or ffmpeg is mentioned as a prerequisite anywhere in it:

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

Restart ComfyUI afterward. Given that this node (and the rest of this pack's video tooling) almost certainly leans on ffmpeg, make sure it's actually on your machine's PATH - that's the realistic gap the README leaves undocumented, not a missing pip package.

Common issues and troubleshooting

If it errors immediately, check for ffmpeg first. This is the single most likely dependency the README doesn't mention, and it's shared across this pack's video-processing nodes generally. A missing or unreachable ffmpeg binary is the most probable cause of an outright failure.

Fill in all three fields explicitly. Because video_path, output_dir, and output_filename all default to empty strings with no fallback described, leaving any of them blank is more likely to produce a path error than a "same folder, auto name" behavior.

No documented behavior for a video with no audio track. If your source is already silent, what this node does isn't specified - it may pass through cleanly, or it may error trying to strip a stream that isn't there. Test on a short clip before chaining this into a longer automated pipeline you're not watching closely.