Nodes/comfyui_cv/CV Install Example Inputs
ComfyUI Node

CV Install Example Inputs

Copies the sample media this pack ships in its 'example_inputs' folder into ComfyUI's 'input' folder, so the LoadImage / LoadVideo / Load3D dropdowns in the example workflows actually find their files. Run it once after installing the pack, then reload the page (the combos are built when the node definitions are fetched). 3D models go to 'input/3d' because that is the only place core's Load3D nodes look; everything else lands in 'input' itself. Nothing outside 'input' is touched and nothing is deleted. Failure tolerant: a missing source folder or an unreadable file is reported with ok=false instead of halting the run.

By bmad4ever·Created 3 months ago·Updated 2 days ago· 0
CV Install Example Inputs
    • report
    • copied
    • would_copy
    • skipped
    • ok
    ◄mode▾►
    ◄existing_files▾►
    Categoryimage/CV

    Inputs (2)

    NameTypeDefaultDescription
    modeCOMBO'copy the files' writes them. The dry run touches nothing and reports exactly what a real run would do - use it first if the input folder is shared with other packs or holds your own work.
    existing_filesCOMBOWhat to do when a file of the same name is already in the input folder. Keeping it is safe (your own file wins, and a second run of this node is then a no-op); overwrite is for repairing a sample you edited in place. Only names that collide with a packaged file are ever considered.

    Outputs (5)

    NameTypeDescription
    reportSTRINGMulti-line summary: the counts and one line per file that failed. Wire it into core 'Preview as Text' to read it. Destinations are named RELATIVE to the ComfyUI folder and any error text is passed through the same path redaction as 'CV Build Information', so the report can go straight into a bug report.
    copiedINTHow many files were written (always 0 in dry-run mode, where 'would_copy' carries the number instead).
    would_copyINTHow many files a real run would write with these settings - the dry run's answer, and equal to 'copied' after a successful real run.
    skippedINTFiles already present that were left alone. Everything is skipped on the second run of an unchanged install, which is how you tell the copy took.
    okBOOLEANFalse when the source folder is missing or any single file failed to copy - the run still finishes and the report names what went wrong. Gate a follow-up branch on it with 'If/Else Switch'.