Verify FPS

Conversions lie sometimes. The command runs, the file appears, and nobody checks whether the output is actually 25 fps or just labeled that way. Verify FPS is the checkbox at the end of the pipeline in the Framerate Converter pack (Trope Tools, TropeMedia): it probes the output file and tells you, in plain terms, whether the framerate matches what you asked for.

It belongs to the "Verify" group - the pack's built-in quality control stage. One string input, a target, and it hands back a boolean verdict plus the measured number, so you don't have to trust anyone's header.

Inputs

• video_path - the file to check, usually the output_path from Run FFmpeg.
• target_fps - the fps you wanted, default 25.
• tolerance - how close is close enough, default 0.001 fps. The default is tight but fair: for a clean conversion, 25.000 is 25.000. Crank it up only if you're checking a source that's known to be sloppy.

The outputs

• passed (BOOLEAN) - the verdict.
• actual_fps (FLOAT) - what ffprobe actually measures.
• message (STRING) - human-readable PASS/FAIL, e.g.:

PASS: 25.000fps matches target 25.000fps (diff=0.000000)

It reads r_frame_rate from the output stream, which for a freshly converted CFR file is exactly the rate it should be. That's the thing to remember about this node: it verifies the container's declared rate, which is precisely the property that matters for a deliverable - editors, platforms, and players all trust that header.

Install

Pack install as always: ComfyUI Manager → Trope Tools - Framerate Converter, or git clone https://github.com/LaserDog80/ComfyUI-FramerateConverter into custom_nodes/ and restart. It shells out to the system ffprobe (part of FFmpeg), so that binary needs to be present.

Realistically, this node is for two kinds of people: the one who wants an automated "did it work?" gate in their workflow (wire passed into a conditional that only proceeds when true), and the one who's troubleshooting a conversion that feels wrong. A quick Verify FPS run after a 24→25 conversion tells you in one output whether the problem is your settings or your eyes. That's a pretty good trade for dragging one node onto a canvas.