Caption Desk

Works out whether a caption file can actually be delivered. CEA-608 rides two bytes per field on line 21, so one caption service gets two bytes a frame - 59.94 B/s at 29.97 - and a caption is typed onto the screen at two characters per frame: a full two-row 32-column pop-on is 84 bytes and 1.4 seconds of wire before it can be displayed. The wire is a QUEUE, so a caption that cannot finish in time delays the next one and the lateness accumulates; the first caption in a file usually fails because it has to start crossing the wire before the programme starts; and a second service on the same field halves the first one's rate. Paste the SRT or WebVTT unmodified and a free browser-side engine works out the byte budget, the queue cue by cue, the 32 by 15 grid and the reading speeds - keeping deliverability and readability apart, because a file can pass every reading rule a subtitle checker knows and still not reach the screen. Five lanes: plan, check, wire, grid and deliver. Derived from the baoyu-youtube-transcript skill in github.com/jimliu/baoyu-skills, which downloads transcripts and subtitle files with their timings. Not affiliated with or endorsed by the authors of that repository.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.