Set Value For MC V2V

Same job as its I2V sibling - a settings panel that takes a handful of fields and hands them straight back out as separate wires - but this one is built for a video-to-video ("V2V") pipeline, and it carries a detail the I2V version doesn't: a license_key field.

That's worth pausing on. Nothing in the node processes video itself; it's a pure pass-through. The license key comes in as a plain string and goes right back out as an output, unvalidated by this node. Its presence tells you that whatever actually consumes license_key downstream - a paid tool, a gated API, a separate template of huyl3-cpu's - is where the real gate lives, not here. This node is just carrying the credential along for the ride.

The inputs and outputs that matter

Five required fields:

• Đường dẫn video ("video path") - default /content/drive/MyDrive/audio/1.mp4. Yes, a video path defaulting into an audio folder - almost certainly a leftover from copy-pasting a template rather than a meaningful convention, so don't read anything into it.
• Thư mục audio ("audio folder") and Thư mục kết quả ("results folder") - source and destination directories.
• Prompt - multiline text field.
• license_key - a plain string, blank by default.

Outputs mirror the inputs one-to-one: path_origin, path_folder, save_videos, prompt, license_key. Nothing is transformed; this exists purely to give a Colab-style workflow one labeled block to configure instead of five loose primitives scattered across the graph.

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. As with the rest of this pack, the README doesn't mention this node - it documents exactly one node (a video segment cutter) that isn't part of this batch at all, and its install instructions assume Google Colab. There's nothing dependency-heavy about this specific node, though: it's five string/enum widgets with no processing logic, so a plain install should be enough to get it running.

Common issues & troubleshooting

If you don't have a license key for whatever this feeds into, leaving it blank is a real option as far as this node is concerned - it doesn't validate anything, so ComfyUI will happily run the graph with an empty string. Whether the node downstream accepts that is a separate question you can't answer from this node alone.

More generally: any custom node that carries a credential string through the graph is worth a quick look at the source before you trust it with anything real. That's not a knock on this specific author - it's true of every ComfyUI custom node, which runs as plain Python with full filesystem and network access and no sandboxing. A license_key field with nowhere obvious it's checked, in a pack with no public discussion anywhere that I could find, is exactly the kind of thing worth a five-minute read of the actual .py file before you paste in anything you'd mind leaking.

Compare against Set-Value-For-MC-V2V-V2: the next iteration of this same idea, which drops the license_key field entirely and, usefully, actually documents what its resolution enum resolves to - worth checking if you're starting a V2V workflow fresh rather than following an older tutorial that pins this exact node.