Video transcoding

VideoTranscoding is the workhorse of this pack: hand it a video and an FFMpegSettings object, and it re-encodes or remuxes the file into whatever you configured, writing the result into ComfyUI's output/ folder. If you've generated a video in ComfyUI and want it in a specific container or codec - say, H.265 to halve the size, or a format your editor actually imports - this saves you the usual copy-paste-into-a-terminal dance.

The workflow shape is simple: FFMpegSettings → VideoTranscoding. Set your container, codec, and quality once in the settings node, feed video_path and a filename_prefix, and read the returned output_path (STRING) to see where the file landed.

What the settings actually do

The behavior mirrors the rest of the pack, and the same rule applies:

• codec copy = remux. The stream is copied with no re-encoding - instant, lossless, but also the reason resolution/framerate/preset/CRF do nothing (you can't scale or re-encode while copying). If your output looks identical no matter what you set, you're still on copy.
• Any real codec (libx264, libx265, libvpx-vp9, prores_ks, the NVENC/videotoolbox hardware encoders, …) re-encodes, and then resolution, framerate, preset, and CRF actually apply.
• audio_codec / audio_bitrate follow the same copy-vs-encode logic, and additional_params lets you inject raw flags for anything not exposed.

The filename gotcha you'll hit on run one

With the default video/transcoded prefix, the output filename comes out as <prefix>_<video_name><format> - missing the dot before the extension. So you get output/video/transcoded_myvideo_mp4 (or ...mkv), a perfectly valid file with a mangled, extension-less name. It plays fine - players sniff the content - but it's ugly and confusing when you go looking for it. The workaround: leave filename_prefix empty, and you get a clean <video_name>.<format>. Just don't expect the fixed name until the pack does.

Troubleshooting

• File not found error in the log - video_path is a typed string, not a file picker; make sure you're using an absolute path or one relative to where ComfyUI runs.
• No FFmpeg on PATH - the node shells out to ffmpeg, so without it you'll get failures immediately. It's the pack's one real dependency (there are no Python packages, no models).
• Trust but verify - the README itself flags video transcoding as "not tested," and the node returns output_path even on failure. Give the console log a glance after your first run, and open the output file before you build a workflow on top of it.

Installing

Part of ComfyUI-ASSSSA: install from ComfyUI Manager (search "ComfyUI-ASSSSA") or:

cd ComfyUI/custom_nodes
git clone https://github.com/HighDoping/ComfyUI_ASSSSA

Restart ComfyUI and you're done - just make sure FFmpeg is on your PATH.