Nodes/DIGIT Nodes/DIGIT SRT Preview
ComfyUI Node

DIGIT SRT Preview

A QA pass for your subtitles before the client sees them

By thedepartmentofexternalservices·Created 6 months ago·Updated 26 days ago· 0
DIGIT SRT Preview
    • summary
    • entry_count
    • warnings
    srt_input
    srt_filepath
    max_chars_per_line42
    max_cps20.0

    Subtitle files are easy to generate and easy to ship, and the gap between those two things is where DIGIT SRT Preview lives. It doesn't make captions - the other DIGIT SRT nodes do that - it checks the ones you already have and tells you what's wrong before you deliver. Paste SRT text or point it at a file, and it runs the standard broadcast QA checks and hands you a summary plus a list of warnings.

    This is the node you drop in the pipeline after SRT Maker or SRT From Video (or after any tool, honestly), exactly the way you'd put a QC gate before a render leaves the farm. It's a ten-second sanity check that catches the embarrassing stuff.

    What it checks

    • Overlapping timestamps - an entry that starts before the previous one ends. The classic machine-transcription bug.
    • Long lines - entries exceeding max_chars_per_line, default 42, which is the Netflix/broadcast standard.
    • Too many lines - more than two lines of text in a single entry.
    • Reading speed - characters per second above max_cps, default 20 (Netflix's adult standard; children's content should be 17). A subtitle that's on screen too briefly to read is a subtitle that fails its only job.
    • Bad timing - entries with zero or negative duration.

    Each check can be disabled by setting its threshold to 0.

    The inputs

    • srt_input - paste the SRT text directly.
    • srt_filepath - a path to an SRT file instead; overrides the pasted text if both are set.
    • max_chars_per_line and max_cps - the two thresholds above.

    Outputs: summary (a formatted block like Entries: 47 / Duration: 2m 34s / Warnings: 3), entry_count (the integer, handy for a workflow counter or a conditional), and warnings (one per line, empty when the file is clean).

    How it works and where it fits

    It's a pure parser - no API calls, no credentials, no network. It reads the SRT, walks every entry, applies the checks, and counts. Because it's deterministic and offline, it also makes a nice non-destructive check node: leave it wired up at the end of a captioning workflow and it'll flag problems on every run without touching anything. If it finds issues, fix them with SRT Tools (which can merge, renumber, re-time, and re-post-process) and re-run Preview to confirm.

    Install is just the pack: ComfyUI Manager, search comfyui-digit, restart. No model downloads, no API keys, no GCP setup - this is one of the rare DIGIT nodes that works completely offline. If you do subtitle work in ComfyUI at all, this is the cheapest QC you'll ever add.

    CategoryDIGIT

    Inputs (4)

    NameTypeDefaultDescription
    srt_inputSTRING
    srt_filepathoptSTRINGPath to an SRT file. Overrides srt_input if provided.
    max_chars_per_lineoptINT420–80Flag lines exceeding this length. 0 = no check.
    max_cpsoptFLOAT20.00–40Max characters per second reading speed. Flag entries exceeding this. 0 = no check.

    Outputs (3)

    NameTypeDescription
    summarySTRING
    entry_countINT
    warningsSTRING