Video Dir Combiner PRO++ ULTRA (Image Only)

Functionally, this is the same job as the plain video_dir_combiner: point it at a directory of clips, give it an order via video_list, and it stitches them into one output file. What's actually changed is the packaging - no license_key field this time, and a display name ("PRO++ ULTRA") that's peak scrappy-personal-project branding for what is, mechanically, still just a video concatenation node. Worth a small smile, not a signal of a genuinely different tier of capability.

The one part of the name that does seem to matter is the (Image Only) qualifier, and it's exactly the part with zero explanation anywhere in the schema. My best read, and it's a guess rather than confirmed behavior: this variant is scoped to clips that originated from an image source (an image-to-video batch, say) rather than arbitrary pre-existing video files, which would explain why image stays a required input here too, same as on the base combiner. Take that as an educated read, not documented fact - there's no tooltip or description backing it up.

The inputs and outputs that matter

• image - required, same unexplained-purpose caveat as video_dir_combiner's version of this field.
• video_list - STRING, the list of clips to combine, in order.
• directory_path - source directory.
• output_filename - default output_ultra.mp4.

One output: output_path.

Installing it

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

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

restart. Not documented in the pack's README, which covers one unrelated node. Same assumption as the base combiner: expect an ffmpeg dependency under the hood for the actual video joining, and make sure it's on PATH if you're not on the author's Colab setup.

Common issues & troubleshooting

Same ordering advice as video_dir_combiner: nothing here sorts video_list for you, so run it through this pack's own sort_list_string first if your source folder's natural order doesn't match what you want combined.

If you're choosing between this and the plain video_dir_combiner, the practical difference boils down to the missing license_key requirement - if you don't have one, this is the version that'll actually run for you without that field. Beyond that, without a documented explanation of what "(Image Only)" actually restricts or changes, the safest approach is to test both on a small sample and compare the outputs directly rather than assume which one better fits your source material.

And if output_path comes back pointing at a file that doesn't play, or plays with only part of your source clips included, check video_list and directory_path line up exactly - a filename typo or a path that doesn't resolve inside directory_path is a far more likely explanation than the node itself misbehaving, especially given how little validation this whole family of combiner nodes appears to do on its inputs.